From Juniper SRX SG IDPS Security Technical Implementation Guide
Part of SRG-NET-000113-IDPS-00189
Associated with: CCI-000169
Without the capability to generate audit records with a severity code it is difficult to track and handle detection events.
Use the following command to view the IDP rules: [edit] show security idp status The IDP traffic log can also be inspected to verify that IDP detection events contain a severity level in the log record. If active IDP rules exist that do not include a severity level, this is a finding.
Example configuration to set the severity level on the IDP rules: Define an attack as match criteria. [edit security idp idp-policy base-policy rulebase-ips rule R1] set match attacks predefined-attack-groups "TELNET-Critical" Specify an action for the rule. [edit security idp idp-policy base-policy rulebase-ips rule R1] set then action drop-connection Specify notification and logging options for the rule. [edit security idp idp-policy base-policy rulebase-ips rule R1] set then notification log-attacks alert Set the severity level for the rule. [edit security idp idp-policy base-policy rulebase-ips rule R1] set then severity critical
Lavender hyperlinks in small type off to the right (of CSS
class id
, if you view the page source) point to
globally unique URIs for each document and item. Copy the
link location and paste anywhere you need to talk
unambiguously about these things.
You can obtain data about documents and items in other
formats. Simply provide an HTTP header Accept:
text/turtle
or
Accept: application/rdf+xml
.
Powered by sagemincer