| Checked | Name | Title |
|---|
| ☐ | SV-214610r382900_rule | The Juniper Networks SRX Series Gateway IDPS must provide audit record generation capability for detecting events based on implementation of policy filters, rules, and signatures. |
| ☐ | SV-214611r382732_rule | The Juniper Networks SRX Series Gateway IDPS must enforce approved authorizations by restricting or blocking the flow of harmful or suspicious communications traffic within the network as defined in the PPSM CAL and vulnerability assessments. |
| ☐ | SV-214612r382735_rule | The Juniper Networks SRX Series Gateway IDPS must restrict or block harmful or suspicious communications traffic between interconnected networks based on attribute- and content-based inspection of the source, destination, headers, and/or content of the communications traffic. |
| ☐ | SV-214613r382900_rule | The Juniper Networks SRX Series Gateway IDPS must provide audit record generation with a configurable severity and escalation level capability. |
| ☐ | SV-214614r997693_rule | The Juniper Networks SRX Series Gateway IDPS must block outbound traffic containing known and unknown DoS attacks by ensuring that rules are applied to outbound communications traffic. |
| ☐ | SV-214615r997694_rule | The Juniper Networks SRX Series Gateway IDPS must block outbound traffic containing known and unknown DoS attacks by ensuring that signature-based objects are applied to outbound communications traffic. |
| ☐ | SV-214616r385531_rule | The Juniper Networks SRX Series Gateway IDPS must block outbound traffic containing known and unknown DoS attacks by ensuring that anomaly-based attack objects are applied to outbound communications traffic. |
| ☐ | SV-214617r383101_rule | The Juniper Networks SRX Series Gateway IDPS must detect, at a minimum, mobile code that is unsigned or exhibiting unusual behavior, has not undergone a risk assessment, or is prohibited for use based on a risk assessment. |
| ☐ | SV-214618r383104_rule | The Juniper Networks SRX Series Gateway IDPS must block any prohibited mobile code at the enclave boundary when it is detected. |
| ☐ | SV-214619r997695_rule | The Juniper Networks SRX Series Gateway IDPS must install updates for predefined signature objects, applications signatures, IDPS policy templates, and device software when new releases are available in accordance with organizational configuration management policy and procedures. |
| ☐ | SV-214620r856559_rule | To protect against unauthorized data mining, the Juniper Networks SRX Series Gateway IDPS must prevent code injection attacks launched against data storage objects, including, at a minimum, databases, database records, queries, and fields. |
| ☐ | SV-214621r856560_rule | To protect against unauthorized data mining, the Juniper Networks SRX Series Gateway IDPS must prevent code injection attacks launched against application objects, including, at a minimum, application URLs and application code. |
| ☐ | SV-214622r856561_rule | To protect against unauthorized data mining, the Juniper Networks SRX Series Gateway IDPS must prevent SQL injection attacks launched against data storage objects, including, at a minimum, databases, database records, and database fields. |
| ☐ | SV-214623r856562_rule | To protect against unauthorized data mining, the Juniper Networks SRX Series Gateway IDPS must detect code injection attacks launched against data storage objects, including, at a minimum, databases, database records, queries, and fields. |
| ☐ | SV-214624r856563_rule | To protect against unauthorized data mining, the Juniper Networks SRX Series Gateway IDPS must detect code injection attacks launched against application objects, including, at a minimum, application URLs and application code. |
| ☐ | SV-214625r856564_rule | To protect against unauthorized data mining, the Juniper Networks SRX Series Gateway IDPS must detect SQL injection attacks launched against data storage objects, including, at a minimum, databases, database records, and database fields. |
| ☐ | SV-214626r997696_rule | The Juniper Networks SRX Series Gateway IDPS must protect against or limit the effects of known and unknown types of Denial of Service (DoS) attacks by employing rate-based attack prevention behavior analysis. |
| ☐ | SV-214627r997697_rule | The Juniper Networks SRX Series Gateway IDPS must protect against or limit the effects of known and unknown types of Denial of Service (DoS) attacks by employing anomaly-based detection. |
| ☐ | SV-214628r997698_rule | The Juniper Networks SRX Series Gateway IDPS must protect against or limit the effects of known types of Denial of Service (DoS) attacks by employing signatures. |
| ☐ | SV-214629r971533_rule | The IDPS must send an alert to, at a minimum, the ISSO and ISSM when intrusion detection events are detected that indicate a compromise or potential for compromise. |
| ☐ | SV-214630r971533_rule | The Juniper Networks SRX Series Gateway IDPS must generate an alert to, at a minimum, the ISSO and ISSM when root-level intrusion events that provide unauthorized privileged access are detected. |
| ☐ | SV-214631r971533_rule | The IDPS must send an alert to, at a minimum, the ISSO and ISSM when DoS incidents are detected. |
| ☐ | SV-214632r997699_rule | The Juniper Networks SRX Series Gateway IDPS must automatically install updates to signature definitions. |
| ☐ | SV-214633r997700_rule | The Juniper Networks SRX Series Gateway IDPS must perform real-time monitoring of files from external sources at network entry/exit points. |
| ☐ | SV-214634r383131_rule | The Juniper Networks SRX Series Gateway IDPS must drop packets or disconnect the connection when malicious code is detected. |
| ☐ | SV-214635r383131_rule | The Juniper Networks SRX Series Gateway IDPS must send an immediate alert to, at a minimum, the Security Control Auditor (SCA) when malicious code is detected. |
| ☐ | SV-214636r385561_rule | The Juniper Networks SRX Series Gateway IDPS must have only active Juniper Networks licenses. |
| ☐ | SV-214637r393761_rule | The Juniper Networks SRX Series Gateway IDPS must either forward the traffic from inbound connections to be more deeply inspected for malicious code and Layer 7 threats, or the Antivirus and Unified Threat Management (UTM) license must be installed, active, and policies and rules configured. |
STIGQter: STIG Summary: