Intrusion Detection and Prevention Systems Security Requirements Guide
Rules, Groups, and Values defined within the XCCDF Benchmark
-
SRG-NET-000113
<GroupDescription></GroupDescription>Group -
SRG-NET-000228
<GroupDescription></GroupDescription>Group -
SRG-NET-000018
<GroupDescription></GroupDescription>Group -
The 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.
<VulnDiscussion>The flow of all communications traffic must be monitored and controlled so it does not introduce any unacceptable risk to the...Rule Medium Severity -
SRG-NET-000019
<GroupDescription></GroupDescription>Group -
The 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.
<VulnDiscussion>The IDPS enforces approved authorizations by controlling the flow of information between interconnected networks to prevent h...Rule Medium Severity -
SRG-NET-000019
<GroupDescription></GroupDescription>Group -
The IDPS must immediately use updates made to policy filters, rules, signatures, and anomaly analysis algorithms for traffic detection and prevention functions.
<VulnDiscussion>Information flow policies regarding dynamic information flow control include, for example, allowing or disallowing informatio...Rule Medium Severity -
SRG-NET-000074
<GroupDescription></GroupDescription>Group -
The IDPS must produce audit records containing sufficient information to establish what type of event occurred, including, at a minimum, event descriptions, policy filter, rule or signature invoked, port, protocol, and criticality level/alert code or description.
<VulnDiscussion>Without establishing what type of event occurred, it would be difficult to establish, correlate, and investigate the events l...Rule Medium Severity -
SRG-NET-000075
<GroupDescription></GroupDescription>Group -
The IDPS must produce audit records containing information to establish when (date and time) the events occurred.
<VulnDiscussion>Without establishing the time (date/time) an event occurred, it would be difficult to establish, correlate, and investigate t...Rule Medium Severity -
SRG-NET-000076
<GroupDescription></GroupDescription>Group -
The IDPS must produce audit records containing information to establish where the event was detected, including, at a minimum, network segment, destination address, and IDPS component which detected the event.
<VulnDiscussion>Associating where the event was detected with the event log entries provides a means of investigating an attack or identifyin...Rule Medium Severity -
SRG-NET-000077
<GroupDescription></GroupDescription>Group -
The IDPS must produce audit records containing information to establish the source of the event, including, at a minimum, originating source address.
<VulnDiscussion>Associating the source of the event with detected events in the logs provides a means of investigating an attack or suspected...Rule Medium Severity -
SRG-NET-000078
<GroupDescription></GroupDescription>Group -
The IDPS must produce audit records containing information to establish the outcome of events associated with detected harmful or potentially harmful traffic, including, at a minimum, capturing all associated communications traffic.
<VulnDiscussion>Associating event outcome with detected events in the log provides a means of investigating an attack or suspected attack. W...Rule Medium Severity -
SRG-NET-000089
<GroupDescription></GroupDescription>Group -
The IDPS must automatically update malicious code protection mechanisms as new releases are available in accordance with organizational configuration management policy.
<VulnDiscussion>Failing to automatically update malicious code protection mechanisms, including application software files, signature definit...Rule Medium Severity -
SRG-NET-000273
<GroupDescription></GroupDescription>Group -
In the event of a logging failure, caused by loss of communications with the central logging server, the IDPS must queue audit records locally until communication is restored or until the audit records are retrieved manually or using automated synchronization tools.
<VulnDiscussion>It is critical that when the IDPS is at risk of failing to process audit logs as required, it take action to mitigate the fai...Rule Medium Severity -
SRG-NET-000089
<GroupDescription></GroupDescription>Group -
In the event of a logging failure caused by the lack of audit record storage capacity, the IDPS must continue generating and storing audit records if possible, overwriting the oldest audit records in a first-in-first-out manner.
<VulnDiscussion>It is critical that when the IDPS is at risk of failing to process audit logs as required, it takes action to mitigate the fa...Rule Medium Severity -
SRG-NET-000091
<GroupDescription></GroupDescription>Group -
The IDPS must provide log information in a format that can be extracted and used by centralized analysis tools.
<VulnDiscussion>Centralized review and analysis of log records from multiple IDPS components gives the organization the capability to better ...Rule Medium Severity -
SRG-NET-000113
<GroupDescription></GroupDescription>Group -
The IDPS must provide audit record generation capability for detection events based on implementation of policy filters, rules, signatures, and anomaly analysis.
<VulnDiscussion>Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events r...Rule Medium Severity -
SRG-NET-000113
<GroupDescription></GroupDescription>Group -
The IDPS must provide audit record generation capability for events where communication traffic is blocked or restricted based on policy filters, rules, signatures, and anomaly analysis.
<VulnDiscussion>Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events r...Rule Medium Severity -
The IDPS must provide audit record generation with a configurable severity and escalation level capability.
<VulnDiscussion>Without the capability to generate audit records with a severity code it is difficult to track and handle detection events. ...Rule Medium Severity -
SRG-NET-000131
<GroupDescription></GroupDescription>Group -
The IDPS must be configured to remove or disable non-essential capabilities which are not required for operation or not related to IDPS functionality (e.g., DNS, email client or server, FTP server, or web server).
<VulnDiscussion>An IDPS can be capable of providing a wide variety of capabilities. Not all of these capabilities are necessary. Unnecessary ...Rule Medium Severity -
SRG-NET-000131
<GroupDescription></GroupDescription>Group -
The IDPS must be configured to remove or disable non-essential features, functions, and services of the IDPS application.
<VulnDiscussion>An IDPS can be capable of providing a wide variety of capabilities. Not all of these capabilities are necessary. Unnecessary ...Rule Medium Severity -
SRG-NET-000132
<GroupDescription></GroupDescription>Group -
The IDPS 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.
<VulnDiscussion>Some ports, protocols, or services have known exploits or security weaknesses. These ports, protocols, and services must be p...Rule Medium Severity -
SRG-NET-000192
<GroupDescription></GroupDescription>Group -
The IDPS must block outbound traffic containing known and unknown DoS attacks by ensuring that security policies, signatures, rules, and anomaly detection techniques are applied to outbound communications traffic.
<VulnDiscussion>The IDPS must include protection against DoS attacks that originate from inside the enclave which can affect either internal ...Rule Medium Severity -
The 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.
<VulnDiscussion>Mobile code is defined as software modules obtained from remote systems, transferred across a network, and then downloaded an...Rule Medium Severity -
SRG-NET-000229
<GroupDescription></GroupDescription>Group -
The IDPS must block any prohibited mobile code at the enclave boundary when it is detected.
<VulnDiscussion>Mobile code is defined as software modules obtained from remote systems, transferred across a network, and then downloaded an...Rule Medium Severity -
SRG-NET-000235
<GroupDescription></GroupDescription>Group -
The IDPS must fail to a secure state which maintains access control mechanisms when the IDPS hardware, software, or firmware fails on initialization/shutdown or experiences a sudden abort during normal operation.
<VulnDiscussion>Failure to a known safe state helps prevent systems from failing to a state that may cause loss of data or unauthorized acces...Rule Medium Severity -
SRG-NET-000236
<GroupDescription></GroupDescription>Group -
In the event of a failure of the IDPS function, the IDPS must save diagnostic information, log system messages, and load the most current security policies, rules, and signatures when restarted.
<VulnDiscussion>Failure in a secure state address safety or security in accordance with the mission needs of the organization. Failure to a s...Rule Medium Severity -
SRG-NET-000246
<GroupDescription></GroupDescription>Group -
The IDPS must automatically update malicious code protection mechanisms as new releases are available in accordance with organizational configuration management procedures.
<VulnDiscussion>Failing to update malicious code protection mechanisms, including application software files, signature definitions, and vend...Rule Medium Severity -
SRG-NET-000248
<GroupDescription></GroupDescription>Group -
The IDPS must perform real-time monitoring of files from external sources at network entry/exit points.
<VulnDiscussion>Real-time monitoring of files from external sources at network entry/exit points helps to detect covert malicious code before...Rule Medium Severity
Node 2
The content of the drawer really is up to you. It could have form fields, definition lists, text lists, labels, charts, progress bars, etc. Spacing recommendation is 24px margins. You can put tabs in here, and can also make the drawer scrollable.