Detections
Analytics

PANW-AG-000079 - The Palo Alto Networks security, if used as a TLS gateway/decryption point or VPN concentrator, must provide the capability to immediately disconnect or disable remote access to the information system.

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version

Information

Without the ability to immediately disconnect or disable remote access, an attack or other compromise taking place would not be immediately stopped.

Remote access functionality must have the capability to immediately disconnect current users remotely accessing the information system and/or disable further remote access. The remote access functionality may implement features such as automatic disconnect (or user-initiated disconnect) in case of adverse information based on an indicator of compromise or attack.

If the Palo Alto Networks security platform is used as a TLS gateway/decryption point or VPN concentrator, configure the device to deny decrypted traffic that violates the enclave or system policies. For each type of SSL/TLS traffic that is decrypted, the resulting traffic must be inspected and filtered.

NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.

Solution

These instructions explain the steps involved but do not provide specific details since the exact policies and expected traffic are not known.

Go to Policies >> Security
Select 'Add'.
In the 'Security Policy Rule' window, complete the required fields.
Configure the Security Policy in accordance with the enclave's or system's policy for the resulting decrypted traffic.
For any traffic that violates the enclave policy, configure the Security Policy rule to deny the traffic.
In the 'Security Policy Rule' window, in the 'Actions' tab, in the 'Action Setting' section, select 'deny'.
For any traffic that is allowed, configure the Security Policy Rule to allow the traffic and apply Antivirus and Vulnerability Protection Profiles.
In the 'Security Policy Rule' window, in the 'Actions' tab, in the 'Action Setting' section, select 'allow'.
In the 'Security Policy Rule' window, in the 'Actions' tab, in the 'Profiles Setting' section, select the necessary Profiles.
Commit changes by selecting 'Commit' in the upper-right corner of the screen.
Select 'OK' when the confirmation dialog appears.

See Also

https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_PAN_Y22M04_STIG.zip

Item Details

References: CAT|II, CCI|CCI-002322, Rule-ID|SV-228855r557387_rule, STIG-ID|PANW-AG-000079, STIG-Legacy|SV-77081, STIG-Legacy|V-62591, Vuln-ID|V-228855

Plugin: Palo_Alto

Control ID: 3dfca02123c0d965d25cdaa3b2e5ad34dc0d401786d8a4f6f60f844120c83c1d