<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Hi, is it possible to stop server access directly via RDP client and make Cyberark the only way you can access the server in Remote Access Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/remote-access-discussions/hi-is-it-possible-to-stop-server-access-directly-via-rdp-client/m-p/1416556#M1215</link>
    <description>&lt;P&gt;You can change the password and then not allow the users to view it - only access it via PSM. If they don't have the password, they can't log in. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is something like this possible in your environment?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;-Matt&lt;/P&gt;</description>
    <pubDate>Tue, 07 Jan 2025 17:17:23 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2025-01-07T17:17:23Z</dc:date>
    <item>
      <title>Hi, is it possible to stop server access directly via RDP client and make Cyberark the only way you can access the server</title>
      <link>https://live.paloaltonetworks.com/t5/remote-access-discussions/hi-is-it-possible-to-stop-server-access-directly-via-rdp-client/m-p/1416554#M1213</link>
      <description>&lt;P&gt;Just to explain more, we have Cyberark PAM setup and remote access to servers goes through that. However, some of our servers are still accessible directly via the RDP client from a workstation. Any idea how i can stop this so Cyberark is the only way through which a server&amp;nbsp;can be accessed. I have tried using GPO to block the use of the RDP client but that ended up affecting the server access through cyberark. Anyone with ideas please or a documentation out that i can follow? Thanks in advance&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jan 2025 16:42:20 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/remote-access-discussions/hi-is-it-possible-to-stop-server-access-directly-via-rdp-client/m-p/1416554#M1213</guid>
      <dc:creator>Ovurevu</dc:creator>
      <dc:date>2025-01-07T16:42:20Z</dc:date>
    </item>
    <item>
      <title>Re: Hi, is it possible to stop server access directly via RDP client and make Cyberark the only way you can access the server</title>
      <link>https://live.paloaltonetworks.com/t5/remote-access-discussions/hi-is-it-possible-to-stop-server-access-directly-via-rdp-client/m-p/1416555#M1214</link>
      <description>&lt;P&gt;Hi @Hamid Ovurevu​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can restrict the access to those servers using Firewall rules. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Allow only PSMs to connect to those servers via Firewall by allowing RDP connection. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Other option is to implement Micro-segmentation tool in your organisation using it. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope it helps !&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jan 2025 16:49:05 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/remote-access-discussions/hi-is-it-possible-to-stop-server-access-directly-via-rdp-client/m-p/1416555#M1214</guid>
      <dc:creator>M.Vora780263</dc:creator>
      <dc:date>2025-01-07T16:49:05Z</dc:date>
    </item>
    <item>
      <title>Re: Hi, is it possible to stop server access directly via RDP client and make Cyberark the only way you can access the server</title>
      <link>https://live.paloaltonetworks.com/t5/remote-access-discussions/hi-is-it-possible-to-stop-server-access-directly-via-rdp-client/m-p/1416556#M1215</link>
      <description>&lt;P&gt;You can change the password and then not allow the users to view it - only access it via PSM. If they don't have the password, they can't log in. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is something like this possible in your environment?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;-Matt&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jan 2025 17:17:23 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/remote-access-discussions/hi-is-it-possible-to-stop-server-access-directly-via-rdp-client/m-p/1416556#M1215</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-01-07T17:17:23Z</dc:date>
    </item>
    <item>
      <title>Re: Hi, is it possible to stop server access directly via RDP client and make Cyberark the only way you can access the server</title>
      <link>https://live.paloaltonetworks.com/t5/remote-access-discussions/hi-is-it-possible-to-stop-server-access-directly-via-rdp-client/m-p/1416557#M1216</link>
      <description>&lt;P&gt;You can restrict access via the enterprise firewall.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;B&gt;Rule number 1 : Source IP: psm ip , destination ip: targets servers, src_port: any,dst_port: native port you want to allow (rdp,ssh,https...), action: allow&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;B&gt;Rule number X : source : any, destination ip: target servers, src_port: any, dst_port:any, action:deny&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;B&gt;but you have to allow required communication before denying on rule number X and make sure your PAM is stable before doing this.&lt;/B&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jan 2025 18:54:15 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/remote-access-discussions/hi-is-it-possible-to-stop-server-access-directly-via-rdp-client/m-p/1416557#M1216</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-01-07T18:54:15Z</dc:date>
    </item>
    <item>
      <title>Re: Hi, is it possible to stop server access directly via RDP client and make Cyberark the only way you can access the server</title>
      <link>https://live.paloaltonetworks.com/t5/remote-access-discussions/hi-is-it-possible-to-stop-server-access-directly-via-rdp-client/m-p/1416558#M1217</link>
      <description>&lt;P&gt;By using Windows Firewall and/Or GPO --&amp;gt; Below is a **step-by-step guide** on how to use **Windows Firewall** to allow **RDP (TCP/3389)** connections **only** from the **CyberArk PSM** server(s). You can do this either:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1. **Individually** on each server (via the local Windows Firewall with Advanced Security), or&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2. **Centrally** via a **Group Policy Object (GPO)** applied to an OU containing your servers.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The key idea is to **restrict the inbound Remote Desktop rule’s “Scope”** to only the PSM’s IP address or subnet, thereby **blocking** all other RDP connections.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;---&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;## 1. Identify Your PSM IP/Subnet&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- For example, if your PSM server has IP address `10.10.10.50`, you’ll need that exact address (or a subnet, e.g., `10.10.10.0/24` if you have multiple PSM servers).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;---&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;## 2. Option A: Configure on a Single Server (Local Windows Firewall)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1. **Open Windows Firewall with Advanced Security**&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;- Log on to the Windows server.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;- Press **Win+R**, type **wf.msc**, and press **Enter**.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2. **Locate the Inbound RDP Rule**&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;- In the left pane, select **Inbound Rules**.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;- Look for rules named **“Remote Desktop - User Mode (TCP-In)”** or **“Remote Desktop (TCP-In)”**.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;- You may see multiple entries (for different firewall profiles: Domain, Private, Public). Use the domain profile if the server is domain-joined.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;3. **Edit the Rule to Restrict the Scope**&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;- Right-click the **Remote Desktop** inbound rule that is **Enabled**.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;- Select **Properties**.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;- Go to the **Scope** tab.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;- Under **Remote IP address**, remove “Any IP address” and click **Add**.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;- Enter the **PSM IP** (e.g. `10.10.10.50`) or subnet (e.g. `10.10.10.0/24`).&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;- Click **OK**.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;4. **(Optional) Disable or Remove Default RDP Rules**&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;- Some default rules might still allow RDP from any address. If you see multiple RDP inbound rules, disable or modify them in the same manner so that only the custom-scoped rule remains active.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;5. **Test**&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;- From the PSM server, initiate an RDP session to confirm it works.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;- From any other workstation, confirm that RDP is **blocked**.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;---&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;## 3. Option B: Configure via Group Policy (Recommended for Multiple Servers)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you have **many servers**, use a GPO to manage firewall rules centrally.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1. **Open Group Policy Management**&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;- On your domain controller (or management workstation with RSAT), open **Group Policy Management** (`gpmc.msc`).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2. **Create (or Edit) a GPO**&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;- Right-click your desired **OU** containing the servers.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;- Select **Create a GPO in this domain…** (or **Edit** an existing one if you have a dedicated firewall policy GPO).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;3. **Navigate to Windows Firewall with Advanced Security**&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;- In the GPO Editor:&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;- **Computer Configuration**&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;- **Policies**&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;- **Windows Settings**&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;- **Security Settings**&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;- **Windows Defender Firewall with Advanced Security**&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;- **Inbound Rules** (right-click **Inbound Rules** and select **New Rule…**)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;4. **Create a New Custom Rule**&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;1. **Rule Type**: Select **Port** or **Custom** (either works, but “Port” is simpler for 3389).&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;2. **Protocol and Ports**:&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;- Protocol: **TCP**&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;- Local Port: **3389**&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;3. **Scope**:&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;- **Remote IP addresses**: Select **These IP addresses** and click **Add**. Enter your PSM IP or subnet.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;- Local IP addresses: Usually **Any** (leave default) unless you have a specific local IP.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;4. **Action**: **Allow the connection**.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;5. **Profile**: Select **Domain** (assuming domain-joined servers).&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;6. **Name**: Give it a descriptive name, e.g., “Allow RDP from CyberArk PSM Only.”&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;5. **Optionally: Block All Other RDP**&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;- You can either **disable** or **delete** the default RDP inbound rule from the same GPO.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;- Alternatively, create a **Deny rule** for RDP from any other IP addresses, but usually removing or disabling the default “allow RDP” rule is enough.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;6. **Link the GPO to the OU**&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;- Make sure the GPO is **linked** to the OU where the target servers reside, and that the servers are within that OU or a child OU.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;- Confirm **gpupdate** or wait for the next policy refresh.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;7. **Test**&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;- On any server in that OU, run **gpresult /r** or check Windows Firewall with Advanced Security to confirm the new rule is present.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;- Validate RDP from the PSM server works.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;- Validate RDP from anywhere else is blocked.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;---&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;## 4. Verify RDP Remains Enabled for PSM&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- **Important**: Do **not** disable RDP entirely in “System Properties” or via a GPO that says “Do not allow Remote Desktop.” CyberArk PSM **needs** RDP to be enabled on the OS level to broker the session.&lt;/P&gt;&lt;P&gt;- By restricting inbound connections to **only** the PSM IP(s), you effectively **force** all RDP connections to come from CyberArk.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;---&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;## 5. (Optional) Check via Command Line (netsh)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you prefer scripting or command-line, you can use **netsh** on the server directly (or within a startup script), for example:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;```powershell&lt;/P&gt;&lt;P&gt;netsh advfirewall firewall add rule name="Allow RDP from CyberArk PSM" ^&lt;/P&gt;&lt;P&gt;&amp;nbsp;dir=in action=allow protocol=TCP localport=3389 ^&lt;/P&gt;&lt;P&gt;&amp;nbsp;remoteip=10.10.10.50 enable=yes&lt;/P&gt;&lt;P&gt;```&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You would then **disable** or **remove** any existing RDP allow rules that have `remoteip=any`.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;---&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;## Final Tips&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1. **Document your firewall rules**: Note which IPs or subnets are allowed and keep them up to date if PSM addresses change.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2. **Watch out for multiple RDP firewall rules**: If you have multiple “Remote Desktop” inbound rules, ensure only your new restricted-scope rule is **enabled**.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;3. **Test thoroughly**: Verify from the PSM (should succeed) and from a non-PSM workstation (should fail).&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;4. **Apply to all relevant servers**: If done via GPO, ensure those servers are indeed in the scope of the GPO link.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;By following the above steps, you will **enforce** that **all RDP connections** come **only** from your CyberArk PSM servers, effectively blocking direct RDP from any other source.&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jan 2025 20:30:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/remote-access-discussions/hi-is-it-possible-to-stop-server-access-directly-via-rdp-client/m-p/1416558#M1217</guid>
      <dc:creator>ernesto_vignes</dc:creator>
      <dc:date>2025-01-07T20:30:29Z</dc:date>
    </item>
    <item>
      <title>Re: Hi, is it possible to stop server access directly via RDP client and make Cyberark the only way you can access the server</title>
      <link>https://live.paloaltonetworks.com/t5/remote-access-discussions/hi-is-it-possible-to-stop-server-access-directly-via-rdp-client/m-p/1416559#M1218</link>
      <description>&lt;P&gt;also refer to https://learn.microsoft.com/en-us/answers/questions/235264/how-to-restrict-rdp-connection-to-specific-source&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jan 2025 20:31:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/remote-access-discussions/hi-is-it-possible-to-stop-server-access-directly-via-rdp-client/m-p/1416559#M1218</guid>
      <dc:creator>ernesto_vignes</dc:creator>
      <dc:date>2025-01-07T20:31:33Z</dc:date>
    </item>
    <item>
      <title>Re: Hi, is it possible to stop server access directly via RDP client and make Cyberark the only way you can access the server</title>
      <link>https://live.paloaltonetworks.com/t5/remote-access-discussions/hi-is-it-possible-to-stop-server-access-directly-via-rdp-client/m-p/1416560#M1219</link>
      <description>&lt;P&gt;Hi @Hamid Ovurevu​&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Since several community members answered your question, please let us know if these solutions addressed your query.&lt;/P&gt;&lt;P&gt;If so, it would be great if you could mark the most helpful response as 'Select as Best' to assist other community members with similar questions.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you, Liad.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Jan 2025 08:14:01 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/remote-access-discussions/hi-is-it-possible-to-stop-server-access-directly-via-rdp-client/m-p/1416560#M1219</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-01-13T08:14:01Z</dc:date>
    </item>
    <item>
      <title>Re: Hi, is it possible to stop server access directly via RDP client and make Cyberark the only way you can access the server</title>
      <link>https://live.paloaltonetworks.com/t5/remote-access-discussions/hi-is-it-possible-to-stop-server-access-directly-via-rdp-client/m-p/1416561#M1220</link>
      <description>&lt;P&gt;@Hamid Ovurevu​&amp;nbsp; You can allow the below connections for Enterprise firewall .&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Source IP to PSM Server Over required port and PSM to Endpoint Servers.&lt;/P&gt;&lt;P&gt;Also you can block the direct firewall connections for endpoints from Source IP.&lt;/P&gt;</description>
      <pubDate>Tue, 14 Jan 2025 10:30:18 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/remote-access-discussions/hi-is-it-possible-to-stop-server-access-directly-via-rdp-client/m-p/1416561#M1220</guid>
      <dc:creator>P.Ahuja806570</dc:creator>
      <dc:date>2025-01-14T10:30:18Z</dc:date>
    </item>
  </channel>
</rss>

