<?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>article PSM - Why does PSM Server require Network Level Authentication (NLA) to be disabled? in PAM SaaS Articles</title>
    <link>https://live.paloaltonetworks.com/t5/pam-saas-articles/psm-why-does-psm-server-require-network-level-authentication-nla/ta-p/1427942</link>
    <description>&lt;H3&gt;Question&lt;/H3&gt;
&lt;DIV&gt;Why does PSM Server require Network Level Authentication (NLA) to be disabled?&lt;/DIV&gt;
&lt;H3&gt;Answer&lt;/H3&gt;
&lt;DIV&gt;Using PSM as a jump server eliminates much of the need for NLA.&lt;BR /&gt;&lt;BR /&gt;First, it is important to distinguish between enabling NLA on the PSM server itself and enabling NLA on the target servers. We fully support enabling NLA on the target servers.&lt;BR /&gt;&lt;BR /&gt;On the PSM server we require the NLA to be disabled to allow the PSM to provide full isolation and protection of the sensitive credentials from the end-users and their potentially compromised desktops. The PSM ensures that no privileged passwords or keys are ever getting to the end-users' desktops or browsers and thus ensures that they cannot be compromised or hijacked by keyloggers or other tools. In order to be able to do that, no real user/password are passed between the end-user and the PSM server when connecting through the PVWA portal, instead we are using a temporary secured token to establish the session and retrieve the needed credentials from the Vault. Since no real user/password are actually passed to the PSM, the NLA, if not disabled, will fail the connection. Therefore, the NLA needs to be disabled in order to establish a fully isolated and secured connection to a target server without exposing the credentials for its access.&lt;BR /&gt;&lt;BR /&gt;Note: when users are connecting with PSM not through the PVWA portal but directly from their desktop through standard RDP clients, the NLA on the PSM server can be enabled.&lt;BR /&gt;&lt;BR /&gt;Man-In-the-Middle is a vulnerability that's often cited for using NLA. Deploying SSL/TLS certificates that are issued by a trusted Certificate Authority will enable the client to identify the server’s identity and protect against MITM attacks. NLA is also designed to protect against Denial of Service (DOS) attacks on the server. However, the PSM server is usually placed in a DMZ or an internal network and is not directly exposed to the outside world. This reduces the risk for DOS attacks significantly.&lt;/DIV&gt;
&lt;H3&gt;Issue&lt;/H3&gt;
Hello Support Team

Our Customer is Yuanta Life Insurance.
Cyberark PAS version : v10.8

On the PSM server, we require the NLA to be disabled.
But after the routine weakness scan, the third-party audit unit always points out the network-level authentication setting on the PSM server is improper. 

The report makes our customers confused and hopes we can provide the official document or suggestion to prove why is it okay to disable NLA on the PSM Server.

Could you do me a favor to provide the documentation or have any other suggestions?

Best Regards
Kerr
Sep.28,2020

&lt;H3&gt;Environment&lt;/H3&gt;
PSM Security</description>
    <pubDate>Tue, 11 Nov 2025 05:00:39 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2025-11-11T05:00:39Z</dc:date>
    <item>
      <title>PSM - Why does PSM Server require Network Level Authentication (NLA) to be disabled?</title>
      <link>https://live.paloaltonetworks.com/t5/pam-saas-articles/psm-why-does-psm-server-require-network-level-authentication-nla/ta-p/1427942</link>
      <description>&lt;H3&gt;Question&lt;/H3&gt;
&lt;DIV&gt;Why does PSM Server require Network Level Authentication (NLA) to be disabled?&lt;/DIV&gt;
&lt;H3&gt;Answer&lt;/H3&gt;
&lt;DIV&gt;Using PSM as a jump server eliminates much of the need for NLA.&lt;BR /&gt;&lt;BR /&gt;First, it is important to distinguish between enabling NLA on the PSM server itself and enabling NLA on the target servers. We fully support enabling NLA on the target servers.&lt;BR /&gt;&lt;BR /&gt;On the PSM server we require the NLA to be disabled to allow the PSM to provide full isolation and protection of the sensitive credentials from the end-users and their potentially compromised desktops. The PSM ensures that no privileged passwords or keys are ever getting to the end-users' desktops or browsers and thus ensures that they cannot be compromised or hijacked by keyloggers or other tools. In order to be able to do that, no real user/password are passed between the end-user and the PSM server when connecting through the PVWA portal, instead we are using a temporary secured token to establish the session and retrieve the needed credentials from the Vault. Since no real user/password are actually passed to the PSM, the NLA, if not disabled, will fail the connection. Therefore, the NLA needs to be disabled in order to establish a fully isolated and secured connection to a target server without exposing the credentials for its access.&lt;BR /&gt;&lt;BR /&gt;Note: when users are connecting with PSM not through the PVWA portal but directly from their desktop through standard RDP clients, the NLA on the PSM server can be enabled.&lt;BR /&gt;&lt;BR /&gt;Man-In-the-Middle is a vulnerability that's often cited for using NLA. Deploying SSL/TLS certificates that are issued by a trusted Certificate Authority will enable the client to identify the server’s identity and protect against MITM attacks. NLA is also designed to protect against Denial of Service (DOS) attacks on the server. However, the PSM server is usually placed in a DMZ or an internal network and is not directly exposed to the outside world. This reduces the risk for DOS attacks significantly.&lt;/DIV&gt;
&lt;H3&gt;Issue&lt;/H3&gt;
Hello Support Team

Our Customer is Yuanta Life Insurance.
Cyberark PAS version : v10.8

On the PSM server, we require the NLA to be disabled.
But after the routine weakness scan, the third-party audit unit always points out the network-level authentication setting on the PSM server is improper. 

The report makes our customers confused and hopes we can provide the official document or suggestion to prove why is it okay to disable NLA on the PSM Server.

Could you do me a favor to provide the documentation or have any other suggestions?

Best Regards
Kerr
Sep.28,2020

&lt;H3&gt;Environment&lt;/H3&gt;
PSM Security</description>
      <pubDate>Tue, 11 Nov 2025 05:00:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-saas-articles/psm-why-does-psm-server-require-network-level-authentication-nla/ta-p/1427942</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-11-11T05:00:39Z</dc:date>
    </item>
  </channel>
</rss>

