OpenControls Logo

STIG Viewer

STIGViewer Support

The Palo Alto Networks security platform must automatically update malicious code protection mechanisms.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-228851PANW-AG-000065SV-228851r1018773_ruleCCI-004964medium
Description
Remote access is access to DOD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include broadband and wireless connections. Remote access methods include, for example, proxied remote encrypted traffic (e.g., TLS gateways, web content filters, and webmail proxies).
STIGDate
Palo Alto Networks ALG Security Technical Implementation Guide2025-03-12

Related Frameworks

2 mappings across 5 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (15) 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.

CFG-02Secure Baseline Configurations
1.00
CRY-01Use of Cryptographic Controls
1.00
CRY-01.1Alternate Physical Protection
1.00
CRY-03Transmission Confidentiality
1.00
CRY-04Transmission Integrity
1.00
CRY-05Encrypting Data At Rest
1.00
DCH-01Data Protection
1.00
IAC-21Least Privilege
1.00
END-04Malicious Code Protection (Anti-Malware)
0.50
END-04.1Automatic Antimalware Signature Updates
0.50

+5 more (top 10 by confidence shown)

NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 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.

SI-3Malicious Code Protection
1.00
SI-3(2)Automatic Updates
1.00
NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (5) 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.

3.14.1
1.00
3.14.2
1.00
3.14.3
1.00
3.14.4
1.00
3.14.5
1.00
CCI2 mappings
CCI-001247
1.00
CCI-004964
1.00
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (7) 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.

PR.DS-01
1.00
PR.DS-02
1.00
PR.DS-10
1.00
DE.CM-09
0.50
ID.RA-01
0.50
ID.RA-08
0.50
PR.PS-02
0.50

Who does this work

8 NICE work roles and 7 EC-Council certifications.

This is an inference across published mappings, not a single claim by anyone. This check maps to a control, which maps to a Cybersecurity Framework outcome, which NIST assigns to the work roles below. EC-Council separately maps its certifications to those same roles.

A certification prepares someone for a role. It is not evidence that a holder is qualified, and neither NIST nor EC-Council has stated that any certification here addresses this check.

Work-role assignments published by NIST (NICE Framework Components 2.2.0 and the CSF 2.0 OLIR crosswalk). Certification mappings published by EC-Council.

Details

Check Text (C-228851r1018773_chk)

Go to Device >> Dynamic Updates. If no entries for Applications and Threats are present, this is a finding. If the Applications and Threats entry states Download Only, this is a finding. This can be downgraded if a manual process is used. If a manual process is used, compare the Applications and Threats database for the most recent version. Go to Dashboard >> General Information, if the application, threat, and URL filtering definition versions are not the most current ones listed on the vendor support site, this is a finding.

Fix Text (F-31063r997596_fix)

Go to Device >> Dynamic Updates; select "Check Now" at the bottom of the page to retrieve the latest signatures. To schedule automatic signature updates. Note: The steps provided below do not account for local change management policies. Go to Device >> Dynamic Updates; select the text to the right of Schedule. In the "Applications and Threat Updates Schedule" window; complete the required information. In the "Recurrence" field, select Daily. In the "Time" field, enter the time at which you want the device to check for updates. For the Action, select "Download and Install". Select "OK". Commit changes by selecting "Commit" in the upper-right corner of the screen. Select "OK" when the confirmation dialog appears. If using Dynamic Updates is not possible due to mission requirements, implement a manual process.