| Checked | Name | Title |
|---|
| ☐ | SV-228832r557387_rule | The Palo Alto Networks security platform, if used to provide intermediary services for remote access communications traffic (TLS or SSL decryption), must ensure inbound and outbound traffic is monitored for compliance with remote access security policies. |
| ☐ | SV-228833r557387_rule | The Palo Alto Networks security platform, if used as a TLS gateway/decryption point or VPN concentrator, must use encryption services that implement NIST FIPS-validated cryptography to protect the confidentiality of remote access sessions. |
| ☐ | SV-228834r557387_rule | The Palo Alto Networks security platform that stores secret or private keys must use FIPS-approved key management technology and processes in the production and control of private/secret cryptographic keys. |
| ☐ | SV-228835r557387_rule | The Palo Alto Networks security platform, if used as a TLS gateway/decryption point or VPN concentrator, must use NIST FIPS-validated cryptography to protect the integrity of remote access sessions. |
| ☐ | SV-228836r557387_rule | The Palo Alto Networks security platform must log violations of security policies. |
| ☐ | SV-228837r557387_rule | The Palo Alto Networks security platform must only enable User-ID on trusted zones. |
| ☐ | SV-228838r557387_rule | The Palo Alto Networks security platform must disable WMI probing if it is not used. |
| ☐ | SV-228839r557387_rule | The Palo Alto Networks security platform must not enable the DNS proxy. |
| ☐ | SV-228840r557387_rule | The Palo Alto Networks security platform must be configured to prohibit or restrict the use of functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments. |
| ☐ | SV-228841r557387_rule | The Palo Alto Networks security platform that provides intermediary services for TLS must validate certificates used for TLS functions by performing RFC 5280-compliant certification path validation. |
| ☐ | SV-228842r557387_rule | The Palo Alto Networks security platform must protect against the use of internal systems from launching Denial of Service (DoS) attacks against other networks or endpoints. |
| ☐ | SV-228843r557387_rule | The Palo Alto Networks security platform must block phone home traffic. |
| ☐ | SV-228844r557387_rule | The Palo Alto Networks security platform must deny outbound IP packets that contain an illegitimate address in the source address field. |
| ☐ | SV-228845r557387_rule | The Palo Alto Networks security platform must deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception). |
| ☐ | SV-228846r557387_rule | The Palo Alto Networks security platform must terminate communications sessions after 15 minutes of inactivity. |
| ☐ | SV-228847r557387_rule | The Palo Alto Networks security platform must update malicious code protection mechanisms and signature definitions whenever new releases are available in accordance with organizational configuration management policy and procedures. |
| ☐ | SV-228848r559740_rule | The Palo Alto Networks security platform must drop malicious code upon detection. |
| ☐ | SV-228849r559739_rule | The Palo Alto Networks security platform must delete or quarantine malicious code in response to malicious code detection. |
| ☐ | SV-228850r557387_rule | The Palo Alto Networks security platform must send an immediate (within seconds) alert to the system administrator, at a minimum, in response to malicious code detection. |
| ☐ | SV-228851r557387_rule | The Palo Alto Networks security platform must automatically update malicious code protection mechanisms. |
| ☐ | SV-228852r559734_rule | The Palo Alto Networks security platform must deny or restrict detected prohibited mobile code. |
| ☐ | SV-228853r559712_rule | The Palo Alto Networks security platform must prevent the download of prohibited mobile code. |
| ☐ | SV-228854r557387_rule | The Palo Alto Networks security platform, if used as a TLS gateway/decryption point or VPN concentrator, must control remote access methods (inspect and filter traffic). |
| ☐ | SV-228855r557387_rule | 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. |
| ☐ | SV-228856r557387_rule | To protect against data mining, the Palo Alto Networks security platform must detect and prevent SQL and other code injection attacks launched against data storage objects, including, at a minimum, databases, database records, queries, and fields. |
| ☐ | SV-228857r557387_rule | To protect against data mining, the Palo Alto Networks security platform must detect and prevent code injection attacks launched against application objects including, at a minimum, application URLs and application code. |
| ☐ | SV-228858r557387_rule | The Palo Alto Networks security platform must off-load audit records onto a different system or media than the system being audited. |
| ☐ | SV-228859r557387_rule | The Palo Alto Networks security platform being used for TLS/SSL decryption using PKI-based user authentication must only accept end entity certificates issued by DoD PKI or DoD-approved PKI Certificate Authorities (CAs) for the establishment of protected sessions. |
| ☐ | SV-228860r557387_rule | The Palo Alto Networks security platform must protect against Denial of Service (DoS) attacks by employing rate-based attack prevention behavior analysis (traffic thresholds). |
| ☐ | SV-228861r557387_rule | The Palo Alto Networks security platform must use a Vulnerability Protection Profile that blocks any critical, high, or medium threats. |
| ☐ | SV-228862r557387_rule | The Palo Alto Networks security platform must only allow incoming communications from organization-defined authorized sources forwarded to organization-defined authorized destinations. |
| ☐ | SV-228863r557387_rule | The Palo Alto Networks security platform must identify and log internal users associated with prohibited outgoing communications traffic. |
| ☐ | SV-228864r557387_rule | The Palo Alto Networks security platform must be configured to integrate with a system-wide intrusion detection system. |
| ☐ | SV-228865r557387_rule | The Palo Alto Networks security platform must detect use of network services that have not been authorized or approved by the ISSM and ISSO, at a minimum. |
| ☐ | SV-228866r557387_rule | The Palo Alto Networks security platform must generate a log record when unauthorized network services are detected. |
| ☐ | SV-228867r557387_rule | The Palo Alto Networks security platform must generate an alert to, at a minimum, the ISSO and ISSM when unauthorized network services are detected. |
| ☐ | SV-228868r557387_rule | The Palo Alto Networks security platform must continuously monitor inbound communications traffic crossing internal security boundaries. |
| ☐ | SV-228869r557387_rule | The Palo Alto Networks security platform must continuously monitor outbound communications traffic crossing internal security boundaries. |
| ☐ | SV-228870r557387_rule | The Palo Alto Networks security platform must generate an alert to, at a minimum, the ISSO and ISSM when threats identified by authoritative sources (e.g., IAVMs or CTOs) are detected. |
| ☐ | SV-228871r557387_rule | The Palo Alto Networks security platform must generate an alert to, at a minimum, the ISSO and ISSM when rootkits or other malicious software which allows unauthorized privileged access is detected. |
| ☐ | SV-228872r557387_rule | The Palo Alto Networks security platform must generate an alert to, at a minimum, the ISSO and ISSM when rootkits or other malicious software which allows unauthorized non-privileged access is detected. |
| ☐ | SV-228873r557387_rule | The Palo Alto Networks security platform must generate an alert to, at a minimum, the ISSO and ISSM when denial of service incidents are detected. |
| ☐ | SV-228874r557387_rule | The Palo Alto Networks security platform must generate an alert to, at a minimum, the ISSO and ISSM when new active propagation of malware infecting DoD systems or malicious code adversely affecting the operations and/or security of DoD systems is detected. |
| ☐ | SV-228875r557387_rule | The Palo Alto Networks security platform must block traceroutes and ICMP probes originating from untrusted networks (e.g., ISP and other non-DoD networks). |
| ☐ | SV-228876r557387_rule | The Palo Alto Networks security platform providing encryption intermediary services must implement NIST FIPS-validated cryptography to generate cryptographic hashes. |
| ☐ | SV-228877r557387_rule | The Palo Alto Networks security platform, if used for TLS/SSL decryption, must use NIST FIPS-validated cryptography to implement encryption. |
| ☐ | SV-228878r557387_rule | The Palo Alto Networks security platform must, at a minimum, off-load threat and traffic log records onto a centralized log server in real time. |
| ☐ | SV-228879r557387_rule | The Palo Alto Networks security platform must inspect inbound and outbound SMTP and Extended SMTP communications traffic (if authorized) for protocol compliance and protocol anomalies. |
| ☐ | SV-228880r557387_rule | The Palo Alto Networks security platform must inspect inbound and outbound FTP and FTPS communications traffic (if authorized) for protocol compliance and protocol anomalies. |
| ☐ | SV-228881r557387_rule | The Palo Alto Networks security platform must inspect inbound and outbound HTTP traffic (if authorized) for protocol compliance and protocol anomalies. |
STIGQter: STIG Summary: