OpenControls Logo

STIG Viewer

STIGViewer Support

The Palo Alto Networks security platform must detect and deny any prohibited mobile or otherwise malicious code at the enclave boundary.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-207693PANW-IP-000020SV-207693r768712_ruleCCI-001662medium
Description
Mobile code is defined as software modules obtained from remote systems, transferred across a network, and then downloaded and executed on a local system without explicit installation or execution by the recipient. Examples of mobile code include JavaScript, VBScript, Java applets, ActiveX controls, Flash animations, Shockwave videos, and macros embedded within Microsoft Office documents. Mobile code can be exploited to attack a host. It can be sent as an e-mail attachment or embedded in other file formats not traditionally associated with executable code. While the IDPS cannot replace the anti-virus and host-based IDS (HIDS) protection installed on the network's endpoints, vendor or locally created sensor rules can be implemented, which provide preemptive defense against both known and zero-day vulnerabilities. Many of the protections may provide defenses before vulnerabilities are discovered and rules or blacklist updates are distributed by anti-virus or malicious code solution vendors.
STIGDate
Palo Alto Networks IDPS Security Technical Implementation Guide2024-12-19

Related Frameworks

1 mapping across 4 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (3) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

END-10Mobile Code
0.50
VPM-02Vulnerability Remediation Process
0.50
VPM-04Continuous Vulnerability Remediation Activities
0.50
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (4) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

CM-7Least Functionality
1.00
SC-18(1)Identify Unacceptable Code and Take Corrective Actions
1.00
SC-18(3)Prevent Downloading and Execution
1.00
SC-18(4)Prevent Automatic Execution
1.00
CCI1 mapping
CCI-001662
1.00
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 4 hops (2) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

ID.RA-08
0.50
PR.PS-02
0.50

Details

Check Text (C-207693r768712_chk)

Go to Objects >> Security Profiles >> Antivirus. If no Antivirus Profiles are configured other than the default, this is a finding. View the configured Antivirus Profiles for each protocol decoder (SMTP, IMAP, POP3, FTP, HTTP, SMB). If the "Action" is anything other than "drop" or "reset-both", this is a finding. Go to Policies >> Security. Review each of the configured security policies in turn. For any Security Policy that affects traffic from an outside (untrusted) zone, view the "Profile" column. If the "Profile" column does not display the “Antivirus Profile” symbol, this is a finding.

Fix Text (F-7947r768710_fix)

To create an Antivirus Profile: Go to Objects >> Security Profiles >> Antivirus. Select "Add". In the "Antivirus Profile" window, complete the required fields. Complete the "Name" and "Description" fields. In the "Antivirus" tab, for all Decoders (SMTP, IMAP, POP3, FTP, HTTP, SMB protocols), set the “Action” to "deny", or “reset-both”. Select "OK". Use the Profile in a Security Policy: Go to Policies >> Security. Select an existing policy rule or select "Add" to create a new one. In the "Actions” tab in the "Profile Setting" section; in the "Profile Type" field, select "Profiles". The window will change to display the different categories of Profiles. In the "Actions" tab in the "Profile Setting" section; in the "Antivirus" field, select the configured Antivirus Profile. Select "OK". Use the Antivirus Profile in a Security Policy applied to traffic from an outside (untrusted) zone. Go to Policies >> Security. Select an existing policy rule or select "Add" to create a new one. In the "Actions” tab in the Profile Setting section: In the "Profile Type" field, select "Profiles". The window will change to display the different categories of Profiles. In the "Antivirus" field, select the configured Antivirus Profile. In the "Anti-Spyware" field, select the configured Anti-Spyware Profile. In the "Vulnerability Protection" field, select the configured “Vulnerability Protection Profile”. Select "OK". Commit changes by selecting "Commit" in the upper-right corner of the screen. Select "OK" when the confirmation dialog appears.