Intrusion Detection and Prevention Systems Security Requirements Guide V3R4

b

The IPS must enforce approved authorizations by restricting or blocking the flow of harmful or suspicious communications traffic within the network.

AC-4 - Medium - CCI-001368 - V-206864 - SV-206864r1137714_rule

RMF Control

AC-4

Severity

M

CCI

CCI-001368

Version

SRG-NET-000018-IDPS-00018

Vuln IDs

V-206864
V-34484

Rule IDs

SV-206864r1137714_rule
SV-45260

Restricting the flow of communications traffic, also known as information flow control, helps prevent unauthorized access. Upon detecting malicious traffic or an anomaly, the IPS must be configured to drop, block, or redirect this traffic based on organization-defined actions in the site's security plan and the device's capabilities. This requirement also applies to Zero Trust initiatives.

Checks: C-7118r1137712_chk

If the device being reviewed is an IDS, this is not applicable. Verify the IPS enforces approved authorizations by restricting or blocking the flow of harmful or suspicious communications traffic within the network. If the IPS does not enforce approved authorizations by restricting or blocking the flow of harmful or suspicious communications traffic within the network, this is a finding.

Fix: F-7118r1137713_fix

Configure the IPS to enforce approved authorizations by restricting or blocking the flow of harmful or suspicious communications traffic within the network.

b

The IPS 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.

AC-4 - Medium - CCI-001414 - V-206865 - SV-206865r1137717_rule

RMF Control

AC-4

Severity

M

CCI

CCI-001414

Version

SRG-NET-000019-IDPS-00019

Vuln IDs

V-206865
V-34485

Rule IDs

SV-206865r1137717_rule
SV-45262

Restricting the communications traffic as it crosses external/perimeter boundaries, also known as information flow control, helps prevent malicious or suspicious access. The IPS must be configured to leverage policy filters, rules, signatures, and/or behavior analysis algorithms that inspects and restricts traffic based on the characteristics of the information and/or the information path. Inspection is based on attribute- and content-based inspection of the source, destination, headers, and/or content of the communications traffic. DOD has defined the actions required upon the detection of harmful or suspicious traffic is to restrict, redirect, drop, or block the traffic. Specific actions taken depends on the site's security plan and the device's capabilities. This requirement also applies to Zero Trust initiatives.

Checks: C-7119r1137715_chk

If the device being reviews is an IDS, this is not applicable. Verify the IPS enforces approved authorizations by restricting or blocking the flow of harmful or suspicious communications traffic for controlling the flow of information between interconnected networks. If the IPS does not enforce approved authorizations by restricting or blocking the flow of harmful or suspicious communications traffic for controlling the flow of information between interconnected networks, this is a finding.

Fix: F-7119r1137716_fix

Configure the IPS to enforce approved authorizations by restricting or blocking the flow of harmful or suspicious communications traffic for controlling the flow of information between interconnected networks.

b

The IDPS must immediately use updates made to policy filters, rules, signatures, and anomaly analysis algorithms for traffic detection and prevention functions.

AC-4 - Medium - CCI-001414 - V-206866 - SV-206866r1137718_rule

RMF Control

AC-4

Severity

M

CCI

CCI-001414

Version

SRG-NET-000019-IDPS-00187

Vuln IDs

V-206866
V-55317

Rule IDs

SV-206866r1137718_rule
SV-69563

Information flow policies regarding dynamic information flow control include, for example, allowing or disallowing information flows based on changes to vulnerability assessments or mission conditions. Changing conditions include changes in the threat environment and detection of potentially harmful or adverse events. Changes to the IDPS must take effect when made by an authorized administrator and the new configuration is put in place or committed, including upon restart or the application or reboot of the system. With some devices, the changes take effect as the configuration is changed, while with others, the new configuration must be submitted to the device. In any case, the behavior of the IDPS must immediately be affected to reflect the configuration change. This requirement also applies to Zero Trust initiatives.

Checks: C-7120r298110_chk

Verify the IDPS immediately uses updates made to policy filters, rules, signatures, and anomaly analysis algorithms for traffic detection and prevention functions. If the IDPS does not immediately use updates made to policy filters, rules, signatures, and anomaly analysis algorithms to traffic detection and prevention functions, this is a finding.

Fix: F-7120r298111_fix

Configure the IDPS to immediately use updates made to policy filters, rules, signatures, and anomaly analysis algorithms for traffic detection and prevention functions.

b

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.

AU-3 - Medium - CCI-000130 - V-206867 - SV-206867r382855_rule

RMF Control

AU-3

Severity

M

CCI

CCI-000130

Version

SRG-NET-000074-IDPS-00059

Vuln IDs

V-206867
V-34540

Rule IDs

SV-206867r382855_rule
SV-45382

Without establishing what type of event occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack. Associating an event type with each event log entry provides a means of investigating an attack or identifying an improperly configured IDPS. While auditing and logging are closely related, they are not the same. Logging is recording data about events that take place in a system, while auditing is the use of log records to identify security-relevant information such as system or user accesses. In short, log records are audited to establish an accurate history. Without logging, it would be impossible to establish an audit trail.

Checks: C-7121r298113_chk

Verify the entries sent to the audit log include, at a minimum, event descriptions, policy filter, rule or signature invoked, port, protocol, criticality level/alert code or description. If the audit log event records does not include, at a minimum, event descriptions, policy filter, rule signature invoked, port, protocol, and criticality level/alert code or description, this is a finding.

Fix: F-7121r298114_fix

Configure the IDPS components to ensure entries sent to the audit log include sufficient information to determine the type or category for each audit event recorded in the audit log, including, at a minimum, event descriptions, policy filter, rule or signature invoked, port, protocol, and criticality level/alert code or description.

b

The IDPS must produce audit records containing information to establish when (date and time) the events occurred.

AU-3 - Medium - CCI-000131 - V-206868 - SV-206868r382858_rule

RMF Control

AU-3

Severity

M

CCI

CCI-000131

Version

SRG-NET-000075-IDPS-00060

Vuln IDs

V-206868
V-34541

Rule IDs

SV-206868r382858_rule
SV-45383

Without establishing the time (date/time) an event occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack. Associating the date and time the event occurred with each event log entry provides a means of investigating an attack or identifying an improperly configured IDPS. While auditing and logging are closely related, they are not the same. Logging is recording data about events that take place in a system, while auditing is the use of log records to identify security-relevant information such as system or user accesses. In short, log records are audited to establish an accurate history. Without logging, it would be impossible to establish an audit trail.

Checks: C-7122r298116_chk

Verify the entries sent to the audit log include the date and time of each event. If the audit log event records do not include the date and time the events occurred, this is a finding.

Fix: F-7122r298117_fix

Configure the IDPS components to include the date time stamp of events in log messages.

b

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.

AU-3 - Medium - CCI-000132 - V-206869 - SV-206869r382861_rule

RMF Control

AU-3

Severity

M

CCI

CCI-000132

Version

SRG-NET-000076-IDPS-00061

Vuln IDs

V-206869
V-34542

Rule IDs

SV-206869r382861_rule
SV-45384

Associating where the event was detected with the event log entries provides a means of investigating an attack or identifying an improperly configured IDPS. This information can be used to determine what systems may have been affected. While auditing and logging are closely related, they are not the same. Logging is recording data about events that take place in a system, while auditing is the use of log records to identify security-relevant information such as system or user accesses. In short, log records are audited to establish an accurate history. Without logging, it would be impossible to establish an audit trail.

Checks: C-7123r298119_chk

Verify the IDPS produces 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. If the audit log events do not include information which establishes where the event was detected, including, at a minimum, network segment, destination address, and IDPS component which detected the event, this is a finding.

Fix: F-7123r298120_fix

Configure the IDPS to 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.

b

The IDPS must produce audit records containing information to establish the source of the event, including, at a minimum, originating source address.

AU-3 - Medium - CCI-000133 - V-206870 - SV-206870r382864_rule

RMF Control

AU-3

Severity

M

CCI

CCI-000133

Version

SRG-NET-000077-IDPS-00062

Vuln IDs

V-206870
V-34543

Rule IDs

SV-206870r382864_rule
SV-45385

Associating the source of the event with detected events in the logs provides a means of investigating an attack or suspected attack. While auditing and logging are closely related, they are not the same. Logging is recording data about events that take place in a system, while auditing is the use of log records to identify security-relevant information such as system or user accesses. In short, log records are audited to establish an accurate history. Without logging, it would be impossible to establish an audit trail.

Checks: C-7124r298122_chk

Verify configuration produces audit records containing information to establish the source of the event, including, at a minimum, originating source address. If the IDPS does not produce audit records containing information to establish the source of the event, including, at a minimum, originating source address, this is a finding.

Fix: F-7124r298123_fix

Configure the IDPS to produce audit records containing information to establish the source of the event, including, at a minimum, originating source address.

b

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.

AU-3 - Medium - CCI-000134 - V-206871 - SV-206871r382867_rule

RMF Control

AU-3

Severity

M

CCI

CCI-000134

Version

SRG-NET-000078-IDPS-00063

Vuln IDs

V-206871
V-34544

Rule IDs

SV-206871r382867_rule
SV-45386

Associating event outcome with detected events in the log provides a means of investigating an attack or suspected attack. While auditing and logging are closely related, they are not the same. Logging is recording data about events that take place in a system, while auditing is the use of log records to identify security-relevant information such as system or user accesses. In short, log records are audited to establish an accurate history. Without logging, it would be impossible to establish an audit trail. The logs should identify what servers, destination addresses, applications, or databases were potentially attacked by logging communications traffic between the target and the attacker. All commands that were entered by the attacker (such as account creations, changes in permissions, files accessed, etc.) during the session should also be logged.

Checks: C-7125r298125_chk

Verify the entries sent to the audit log include, at a minimum, capturing all associated communications traffic. If the audit log event records do not include, at a minimum, capturing all associated communications traffic, this is a finding.

Fix: F-7125r298126_fix

Configure the IDPS components to ensure entries sent to the audit log include, at a minimum, capturing all associated communications traffic.

b

The IDPS must provide log information in a format that can be extracted and used by centralized analysis tools.

AU-6 - Medium - CCI-000154 - V-206874 - SV-206874r382879_rule

RMF Control

AU-6

Severity

M

CCI

CCI-000154

Version

SRG-NET-000091-IDPS-00193

Vuln IDs

V-206874
V-55335

Rule IDs

SV-206874r382879_rule
SV-69581

Centralized review and analysis of log records from multiple IDPS components gives the organization the capability to better detect distributed attacks and provides increased data points for behavior analysis techniques. These techniques are invaluable in monitoring for indicators of complex attack patterns. To support the centralized analysis capability, the IDPS components must be able to provide the information in a format (e.g., Syslog) that can be extracted and used, allowing the application to effectively review and analyze the log records.

Checks: C-7128r298134_chk

Verify the IDPS provides log information in a format that can be extracted and used by centralized analysis tools. If the IDPS does not provide log information in a format that can be extracted and used by centralized analysis tools, this is a finding.

Fix: F-7128r298135_fix

Configure the IDPS to provide log information in a format that can be extracted and used by centralized analysis tools.

b

The IDPS must provide audit record generation capability for detection events based on implementation of policy filters, rules, signatures, and anomaly analysis.

AU-12 - Medium - CCI-000169 - V-206875 - SV-206875r382900_rule

RMF Control

AU-12

Severity

M

CCI

CCI-000169

Version

SRG-NET-000113-IDPS-00013

Vuln IDs

V-206875
V-55319

Rule IDs

SV-206875r382900_rule
SV-69565

Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one. While auditing and logging are closely related, they are not the same. Logging is recording data about events that take place in a system, while auditing is the use of log records to identify security-relevant information such as system or user accesses. In short, log records are audited to establish an accurate history. Without logging, it would be impossible to establish an audit trail. The IDPS must have the capability to capture and log detected security violations and potential security violations.

Checks: C-7129r298137_chk

Verify the configuration provides audit record generation capability for detection events based on implementation of policy filters, rules, signatures, and anomaly analysis. If the IDPS does not provide audit record generation capability for detection events based on implementation of policy filters, rules, signatures, and anomaly analysis, this is a finding.

Fix: F-7129r298138_fix

Configure the IDPS to provide audit record generation capability for detection events based on implementation of policy filters, rules, signatures, and anomaly analysis.

b

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.

AU-12 - Medium - CCI-000169 - V-206876 - SV-206876r382900_rule

RMF Control

AU-12

Severity

M

CCI

CCI-000169

Version

SRG-NET-000113-IDPS-00082

Vuln IDs

V-206876
V-34594

Rule IDs

SV-206876r382900_rule
SV-45458

Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one. While auditing and logging are closely related, they are not the same. Logging is recording data about events that take place in a system, while auditing is the use of log records to identify security-relevant information such as system or user accesses. In short, log records are audited to establish an accurate history. Without logging, it would be impossible to establish an audit trail. The IDPS must have the capability to capture and log events where communications traffic was blocked or restricted because of a security violation or potential security violations.

Checks: C-7130r298140_chk

Verify the configuration provides audit record generation capability for events where communication traffic is blocked or restricted based on policy filters, rules, signatures, and anomaly analysis algorithms. If the IDPS does not provide audit record generation capability for events where communication traffic is blocked or restricted based on policy filters, rules, signatures, and anomaly analysis, this is a finding.

Fix: F-7130r298141_fix

Configure the IDPS to provide audit record generation capability for events where communication traffic is blocked or restricted based on policy filters, rules, signatures, and anomaly analysis algorithms.

b

The IDPS must provide audit record generation with a configurable severity and escalation level capability.

AU-12 - Medium - CCI-000169 - V-206877 - SV-206877r382900_rule

RMF Control

AU-12

Severity

M

CCI

CCI-000169

Version

SRG-NET-000113-IDPS-00189

Vuln IDs

V-206877
V-55321

Rule IDs

SV-206877r382900_rule
SV-69567

Without the capability to generate audit records with a severity code it is difficult to track and handle detection events. While auditing and logging are closely related, they are not the same. Logging is recording data about events that take place in a system, while auditing is the use of log records to identify security-relevant information such as system or user accesses. In short, log records are audited to establish an accurate history. Without logging, it would be impossible to establish an audit trail. The IDPS must have the capability to collect and log the severity associated with the policy, rule, or signature. IDPS products often have either pre-configured and/or a configurable method for associating an impact indicator or severity code with signatures and rules, at a minimum.

Checks: C-7131r298143_chk

Verify the configuration provides audit record generation with a configurable severity and escalation level capability. If the IDPS does not provide audit record generation with a configurable severity and escalation level capability, this is a finding.

Fix: F-7131r298144_fix

Configure the IDPS to provide audit record generation with a configurable severity and escalation level capability.

b

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).

CM-7 - Medium - CCI-000381 - V-206878 - SV-206878r382903_rule

RMF Control

CM-7

Severity

M

CCI

CCI-000381

Version

SRG-NET-000131-IDPS-00011

Vuln IDs

V-206878
V-55339

Rule IDs

SV-206878r382903_rule
SV-69585

An IDPS can be capable of providing a wide variety of capabilities. Not all of these capabilities are necessary. Unnecessary services, functions, and applications increase the attack surface (sum of attack vectors) of a system. These unnecessary capabilities are often overlooked and therefore may remain unsecured.

Checks: C-7132r298146_chk

Have the SCA display the services running on the IDPS components. Review the IDPS configuration to determine if non-essential capabilities not required for operation, or not related to IDPS functionality (e.g., DNS, email client or server, FTP server, or web server) are enabled. If the IDPS is not 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), this is a finding.

Fix: F-7132r298147_fix

Remove or disable non-essential capabilities from the IDPS. Removal is recommended since the service or function may be inadvertently enabled. However, if removal is not possible, disable the service or function. Document all necessary services.

b

The IDPS must be configured to remove or disable non-essential features, functions, and services of the IDPS application.

CM-7 - Medium - CCI-000381 - V-206879 - SV-206879r382903_rule

RMF Control

CM-7

Severity

M

CCI

CCI-000381

Version

SRG-NET-000131-IDPS-00097

Vuln IDs

V-206879
V-34625

Rule IDs

SV-206879r382903_rule
SV-45500

An IDPS can be capable of providing a wide variety of capabilities. Not all of these capabilities are necessary. Unnecessary services, functions, and applications increase the attack surface (sum of attack vectors) of a system. These unnecessary capabilities are often overlooked and therefore may remain unsecured. This requirement applies to unnecessary features of the IDPS application itself.

Checks: C-7133r298149_chk

Verify the IDPS is configured to remove or disable non-essential features, functions, and services of the IDPS application. If the IDPS is not configured to remove or disable non-essential features, functions, and services of the IDPS application, this is a finding.

Fix: F-7133r298150_fix

Configure the IDPS to remove or disable non-essential features, functions, and services of the IDPS application.

b

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.

CM-7 - Medium - CCI-000382 - V-206880 - SV-206880r552959_rule

RMF Control

CM-7

Severity

M

CCI

CCI-000382

Version

SRG-NET-000132-IDPS-00195

Vuln IDs

V-206880
V-55341

Rule IDs

SV-206880r552959_rule
SV-69587

Some ports, protocols, or services have known exploits or security weaknesses. These ports, protocols, and services must be prohibited or restricted in the IDPS configuration in accordance with DoD policy. Policy filters restrict traffic destined to the enclave perimeter in accordance with the guidelines contained in DoD Instruction 8551.1 for all ports, protocols, and functions. System administrators will review the vulnerability assessment for each port allowed into the enclave and apply all appropriate mitigations defined in the Vulnerability Assessment report. Only ports, protocols, and functions allowed into the enclave should be registered in the PPSM database. It is the responsibility of the enclave owner to have the applications the enclave uses registered in the PPSM database.

Checks: C-7134r298152_chk

Verify the IDPS is configured to prohibit or restrict the use of functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments. If the IDPS is not configured to prohibit or restrict the use of functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments, this is a finding.

Fix: F-7134r298153_fix

Configure the IDPS to prohibit or restrict the use of functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments.

b

The IPS must block outbound traffic containing known and unknown denial-of-service (DoS) attacks by ensuring that security policies, signatures, rules, and anomaly detection techniques are applied to outbound communications traffic.

SC-5 - Medium - CCI-001095 - V-206881 - SV-206881r1140706_rule

RMF Control

SC-5

Severity

M

CCI

CCI-001095

Version

SRG-NET-000192-IDPS-00140

Vuln IDs

V-206881
V-34707

Rule IDs

SV-206881r1140706_rule
SV-45593

The IPS must include protection against DoS attacks originating from inside the enclave that can affect either internal or external systems. These attacks may use legitimate or rogue endpoints from inside the enclave. Installation of IPS detection and prevention components (i.e., sensors) at key boundaries in the architecture mitigates the risk of DoS attacks. These attacks can be detected by matching observed communications traffic with patterns of known attacks and monitoring for anomalies in traffic volume/type. To comply with this requirement, the IPS must inspect outbound traffic for indications of known and unknown DoS attacks. Sensor log capacity management, along with techniques that prevent the logging of redundant information during an attack, also guard against DoS attacks. This requirement is used in conjunction with other requirements that require configuration of security policies, signatures, rules, and anomaly detection techniques and are applicable to both inbound and outbound traffic.

Checks: C-7135r1137726_chk

If the device being reviews is an IDS, this is not applicable. Verify the IPS blocks 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. If the IPS does not 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, this is a finding.

Fix: F-7135r1137727_fix

Configure the IPS to 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.

b

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.

SC-18 - Medium - CCI-001166 - V-206882 - SV-206882r383101_rule

RMF Control

SC-18

Severity

M

CCI

CCI-001166

Version

SRG-NET-000228-IDPS-00196

Vuln IDs

V-206882
V-55343

Rule IDs

SV-206882r383101_rule
SV-69589

Mobile code is defined as software modules obtained from remote systems, transferred across a network, and then downloaded and executed on a local system without explicit installation or execution by the recipient. Examples of mobile code include JavaScript, VBScript, Java applets, ActiveX controls, Flash animations, Shockwave videos, and macros embedded within Microsoft Office documents. Mobile code can be exploited to attack a host. It can be sent as an e-mail attachment or embedded in other file formats not traditionally associated with executable code. While the IDPS cannot replace the anti-virus and host-based IDS (HIDS) protection installed on the network's endpoints, vendor or locally created sensor rules can be implemented, which provide preemptive defense against both known and zero-day vulnerabilities. Many of the protections may provide defenses before vulnerabilities are discovered and rules or blacklist updates are distributed by anti-virus or malicious code solution vendors. To monitor for and detect known prohibited mobile code or approved mobile code that violates permitted usage requirements, the IDPS must implement policy filters, rules, signatures, and anomaly analysis.

Checks: C-7136r298158_chk

Verify the IDPS detects, 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. If the IDPS does not 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, this is a finding.

Fix: F-7136r298159_fix

Configure the IDPS to detects, at a minimum, mobile code that is unsigned or exhibiting unusual behavior, has not undergone a risk assessment, or are prohibited for use based on a risk assessment.

b

The IPS must block any prohibited mobile code at the enclave boundary when it is detected.

SC-18 - Medium - CCI-001662 - V-206883 - SV-206883r1137731_rule

RMF Control

SC-18

Severity

M

CCI

CCI-001662

Version

SRG-NET-000229-IDPS-00163

Vuln IDs

V-206883
V-34743

Rule IDs

SV-206883r1137731_rule
SV-45652

Mobile code is defined as software modules obtained from remote systems, transferred across a network, and then downloaded and executed on a local system without explicit installation or execution by the recipient. Examples of mobile code include JavaScript, VBScript, Java applets, ActiveX controls, Flash animations, Shockwave videos, and macros embedded within Microsoft Office documents. Mobile code can be exploited to attack a host. It can be sent as an e-mail attachment or embedded in other file formats not traditionally associated with executable code. While the IPS cannot replace the antivirus and host-based IDS (HIDS) protection installed on the network's endpoints, vendor or locally created sensor rules can be implemented that provide preemptive defense against both known and zero-day vulnerabilities. Many of the protections may provide defenses before vulnerabilities are discovered and rules or blacklist updates are distributed by antivirus or malicious code solution vendors. To block known prohibited mobile code or approved mobile code that violates permitted usage requirements, the IPS must implement policy filters, rules, signatures, and anomaly analysis.

Checks: C-7137r1137729_chk

If the device being reviewed is an IDS, this is not applicable. Verify the IPS blocks any prohibited mobile code at the enclave boundary when it is detected. If the IPS does not block any prohibited mobile code at the enclave boundary when it is detected, this is a finding.

Fix: F-7137r1137730_fix

Configure the IPS to block any prohibited mobile code at the enclave boundary when it is detected.

b

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.

SC-24 - Medium - CCI-001190 - V-206884 - SV-206884r383119_rule

RMF Control

SC-24

Severity

M

CCI

CCI-001190

Version

SRG-NET-000235-IDPS-00169

Vuln IDs

V-206884
V-34749

Rule IDs

SV-206884r383119_rule
SV-45659

Failure to a known safe state helps prevent systems from failing to a state that may cause loss of data or unauthorized access to system resources. Preserving information system state information also facilitates system restart and return to the operational mode of the organization with less disruption to mission-essential processes. This requirement applies to the device itself, not the network traffic. Abort refers to stopping a program or function before it has finished naturally. The term abort refers to both requested and unexpected terminations. Since it is usually not possible to test this capability in a production environment, systems should either be validated in a testing environment or prior to installation. This requirement is usually a function of the design of the IDPS component. Compliance can be verified by acceptance/validation processes or vendor attestation.

Checks: C-7138r298164_chk

Verify the IDPS fails 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. If the IDPS does not 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, this is a finding.

Fix: F-7138r298165_fix

Configure the IDPS to 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.

b

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.

SC-24 - Medium - CCI-001665 - V-206885 - SV-206885r383122_rule

RMF Control

SC-24

Severity

M

CCI

CCI-001665

Version

SRG-NET-000236-IDPS-00170

Vuln IDs

V-206885
V-34750

Rule IDs

SV-206885r383122_rule
SV-45660

Failure in a secure state address safety or security in accordance with the mission needs of the organization. Failure to a secure state helps prevent a loss of confidentiality, integrity, or availability in the event of a failure of the information system or a component of the system. Preserving state information helps to facilitate the restart of the IDPS application and a return to operation with minimum disruption. This requirement applies to a failure of the IDPS function rather than the device or operating system as a whole which is addressed in the Network Device Management SRG. Since it is usually not possible to test this capability in a production environment, systems should either be validated in a testing environment or prior to installation. This requirement is usually a function of the design of the IDPS component. Compliance can be verified by acceptance/validation processes or vendor attestation.

Checks: C-7139r298167_chk

Verify the IDPS, upon failure of the IDPS function, saves diagnostic information, logs system messages, and loads the most current security policies, rules, and signatures when restarted. If IDPS function, upon system failure, does not save diagnostic information, log system messages, and load the most current security policies, rules, and signatures when restarted, this is a finding.

Fix: F-7139r298168_fix

Configure the IDPS to, upon failure of the IDPS function, save diagnostic information, log system messages, and load the most current security policies, rules, and signatures when restarted.

b

The IDPS must automatically update malicious code protection mechanisms as new releases are available in accordance with organizational configuration management procedures.

Medium - CCI-004965 - V-206887 - SV-206887r982258_rule

RMF Control

Severity

M

CCI

CCI-004965

Version

SRG-NET-000246-IDPS-00205

Vuln IDs

V-206887
V-55357

Rule IDs

SV-206887r982258_rule
SV-69603

Failing to update malicious code protection mechanisms, including application software files, signature definitions, and vendor-provided rules, leaves the system vulnerable to exploitation by recently developed attack methods and programs. The IDPS is a key malicious code protection mechanism in the enclave infrastructure. To ensure this protection is responsive to changes in malicious code threats, IDPS components must be updated, including application software files, antivirus signatures, detection heuristics, vendor-provided rules, and vendor-provided signatures. Updates must be installed in accordance with the CCB procedures for the local organization. However, at a minimum: 1. Updates designated as critical security updates by the vendor must be installed immediately. 2. Updates for signature definitions, detection heuristics, and vendor-provided rules must be installed immediately. 3. Updates for application software are installed in accordance with the CCB procedures. 4. Prior to automatically installing updates, either manual or automated integrity and authentication checking is required, at a minimum, for application software updates.

Checks: C-7141r298173_chk

Verify the IDPS installs updates for application software files, signature definitions, detection heuristics, and vendor-provided rules when new releases are available in accordance with organizational configuration management policy and procedures. If the IDPS does not install updates for application software files, signature definitions, detection heuristics, and vendor-provided rules when new releases are available in accordance with organizational configuration management policy and procedures, this is a finding.

Fix: F-7141r298174_fix

Configure the IDPS to install updates for application software files, signature definitions, detection heuristics, and vendor-provided rules when new releases are available in accordance with organizational configuration management policy and procedures.

b

The IDPS must perform real-time monitoring of files from external sources at network entry/exit points.

SI-3 - Medium - CCI-002624 - V-206888 - SV-206888r982259_rule

RMF Control

SI-3

Severity

M

CCI

CCI-002624

Version

SRG-NET-000248-IDPS-00206

Vuln IDs

V-206888
V-55359

Rule IDs

SV-206888r982259_rule
SV-69605

Real-time monitoring of files from external sources at network entry/exit points helps to detect covert malicious code before it is downloaded to or executed by internal and external endpoints. Using malicious code, such as viruses, worms, Trojan horses, and spyware, an attacker may gain access to sensitive data and systems. IDPSs innately meet this requirement for real-time scanning for malicious code when properly configured to meet the requirements of this SRG. However, most products perform communications traffic inspection at the packet level.

Checks: C-7142r298176_chk

Verify the IDPS performs real-time monitoring of files from external sources at network entry/exit points. If the IDPS does not perform real-time monitoring of files from external sources at network entry/exit points, this is a finding.

Fix: F-7142r298177_fix

Configure the IDPS to perform real-time monitoring of files from external sources at network entry/exit points.

b

The IPS must block malicious code.

SI-3 - Medium - CCI-001243 - V-206889 - SV-206889r1137734_rule

RMF Control

SI-3

Severity

M

CCI

CCI-001243

Version

SRG-NET-000249-IDPS-00176

Vuln IDs

V-206889
V-34762

Rule IDs

SV-206889r1137734_rule
SV-45686

Configuring the IPS to blocks, drops, and/or quarantine based on local organizational incident handling procedures minimizes the impact of this code on the network.

Checks: C-7143r1137732_chk

If the device being reviewed is an IDS, this is not applicable. Verify the IPS blocks malicious code. If the IPS does not block malicious code, this is a finding.

Fix: F-7143r1137733_fix

Configure the IPS to block malicious code.

b

The IPS must quarantine or block malicious code.

SI-3 - Medium - CCI-001243 - V-206890 - SV-206890r1137737_rule

RMF Control

SI-3

Severity

M

CCI

CCI-001243

Version

SRG-NET-000249-IDPS-00221

Vuln IDs

V-206890
V-55361

Rule IDs

SV-206890r1137737_rule
SV-69607

Configuring the network element to block, drop, and/or quarantine based on local organizational incident handling procedures minimizes the impact of this code on the network. Malicious code includes, but is not limited to, viruses, worms, Trojan horses, and spyware. The code provides the ability for a malicious user to read from and write to files and folders on a computer's hard drive. Malicious code could run and attach programs, which may allow the unauthorized distribution of malicious mobile code. Sometimes it is necessary to generate a log event and then automatically drop or block the malicious code; however, for critical attacks or where forensic evidence is deemed necessary, the preferred action is for the file to be quarantined for further investigation. This requirement is limited to network elements that perform security functions, such as ALG and IPS.

Checks: C-7144r1137735_chk

If the device being reviewed is an IDS, this is not applicable. Verify the IPS quarantines blocks malicious code. If the IPS does not quarantine or blocks malicious code, this is a finding.

Fix: F-7144r1137736_fix

Configure the IPS to quarantine or block malicious code.

b

The IDPS must send an immediate (within seconds) alert to, at a minimum, the system administrator when malicious code is detected.

SI-3 - Medium - CCI-001243 - V-206891 - SV-206891r383131_rule

RMF Control

SI-3

Severity

M

CCI

CCI-001243

Version

SRG-NET-000249-IDPS-00222

Vuln IDs

V-206891
V-55363

Rule IDs

SV-206891r383131_rule
SV-69609

Without an alert, security personnel may be unaware of an impending failure of the audit capability, and the ability to perform forensic analysis and detect rate-based and other anomalies will be impeded. The IDPS generates an immediate (within seconds) alert which notifies designated personnel of the incident. Sending a message to an unattended log or console does not meet this requirement since that will not be seen immediately. These messages should include a severity level indicator or code as an indicator of the criticality of the incident.

Checks: C-7145r298185_chk

Verify the IDPS sends an immediate (within seconds) alert to, at a minimum, the system administrator when malicious code is detected. If the IDPS does not send an immediate (within seconds) alert to, at a minimum, the system administrator when malicious code is detected, this is a finding.

Fix: F-7145r298186_fix

Configure the IDPS to send an immediate (within seconds) alert to, at a minimum, the system administrator when malicious code is detected.

b

The IDPS must automatically update malicious code protection mechanisms as new releases are available in accordance with organizational configuration management policy.

Medium - CCI-004964 - V-206892 - SV-206892r982260_rule

RMF Control

Severity

M

CCI

CCI-004964

Version

SRG-NET-000251-IDPS-00178

Vuln IDs

V-206892
V-55597

Rule IDs

SV-206892r982260_rule
SV-69843

Failing to automatically update malicious code protection mechanisms, including application software files, signature definitions, and vendor-provided rules, leaves the system vulnerable to exploitation by recently developed attack methods and programs. An automatic update process ensures this important task is performed without the need for system administrator intervention. The IDPS is a key malicious code protection mechanism in the enclave infrastructure. To ensure this protection is responsive to changes in malicious code threats, IDPS components must be automatically updated, including anti-virus signatures, detection heuristics, vendor-provided rules, and vendor-provided signatures. If a DOD patch management server or update repository having the tested/verified updates is available for the IDPS component, the components must be configured to automatically check this server/site for updates and install new updates. If a DOD server/site is not available, the component must be configured to automatically check a trusted vendor site for updates. A trusted vendor is either commonly used by DOD, specifically approved by DOD, the vendor from which the equipment was purchased, or approved by the local program's CCB.

Checks: C-7146r298188_chk

Verify the IDPS automatically installs updates to signature definitions, detection heuristics, and vendor-provided rules. If the IDPS does not automatically install updates to signature definitions, detection heuristics, and vendor-provided rules, this is a finding.

Fix: F-7146r298189_fix

Configure the IDPS to automatically install updates to signature definitions, detection heuristics, and vendor-provided rules.

b

The IPS must block outbound Internet Control Message Protocol (ICMP) Destination Unreachable, Redirect, and Address Mask reply messages.

SI-11 - Medium - CCI-001312 - V-206893 - SV-206893r1137740_rule

RMF Control

SI-11

Severity

M

CCI

CCI-001312

Version

SRG-NET-000273-IDPS-00198

Vuln IDs

V-206893
V-34788

Rule IDs

SV-206893r1137740_rule
SV-45716

ICMP messages are used to provide feedback about problems in the network. These messages are sent back to the sender to support diagnostics; however, some messages can also provide host information and network topology that may be exploited by an attacker. An IPS must be configured to "silently drop" the packet and not send an ICMP control message back to the source. In some cases, it may be necessary to direct the traffic to a null interface. Three ICMP messages are commonly used by attackers for network mapping: Destination Unreachable, Redirect, and Address Mask Reply. These responses must be blocked on external interfaces; however, blocking the Destination Unreachable response will prevent Path Maximum Transmission Unit Discovery (PMTUD), which relies on the response "ICMP Destination Unreachable--Fragmentation Needed but DF Bit Set". PMTUD is a useful function and should only be "broken" after careful consideration. An acceptable alternative to blocking all Destination Unreachable responses is to filter Destination Unreachable messages generated by the IPS to allow ICMP Destination Unreachable--Fragmentation Needed but DF Bit Set (Type 3, Code 4) and apply this filter to the external interfaces.

Checks: C-7147r1137738_chk

If the device being reviewed is an IDS, this is not applicable. Verify the IPS blocks outbound ICMP Destination Unreachable, Redirect, and Address Mask reply messages. If the IPS does not block outbound ICMP Destination Unreachable, Redirect, and Address Mask reply messages, this is a finding.

Fix: F-7147r1137739_fix

Configure the IPS to block outbound ICMP Destination Unreachable, Redirect, and Address Mask reply messages. An acceptable alternative to blocking all Destination Unreachable responses is to filter Destination Unreachable messages generated by the firewall implementation to allow ICMP Destination Unreachable-- Fragmentation Needed but DF Bit Set (Type 3, Code 4) and apply this filter to the external interfaces.

b

The IPS must block malicious Internet Control Message Protocol (ICMP) packets by properly configuring ICMP signatures and rules.

SI-11 - Medium - CCI-001312 - V-206894 - SV-206894r1137743_rule

RMF Control

SI-11

Severity

M

CCI

CCI-001312

Version

SRG-NET-000273-IDPS-00204

Vuln IDs

V-206894
V-55355

Rule IDs

SV-206894r1137743_rule
SV-69601

ICMP messages are used to provide feedback about problems in the network. These messages are sent back to the sender to support diagnostics; however, some messages can also provide host information, network topology, and a covert channel that may be exploited by an attacker. Given the prevalence of ICMP traffic on the network, monitoring for malicious ICMP traffic would be cumbersome. Vendors provide signatures and rules which filter for known ICMP traffic exploits.

Checks: C-7148r1137741_chk

If the device being reviewed is an IDS, this is not applicable. Verify the IPS blocks malicious ICMP packets by properly configuring ICMP signatures and rules. If the IPS does not block malicious ICMP packets by properly configuring ICMP signatures and rules, this is a finding.

Fix: F-7148r1137742_fix

Configure the IPS to block malicious ICMP packets by properly configuring ICMP signatures and rules.

b

To protect against unauthorized data mining, the IPS must prevent code injection attacks launched against data storage objects, including, at a minimum, databases, database records, queries, and fields.

AC-23 - Medium - CCI-002346 - V-206895 - SV-206895r1137746_rule

RMF Control

AC-23

Severity

M

CCI

CCI-002346

Version

SRG-NET-000318-IDPS-00068

Vuln IDs

V-206895
V-55397

Rule IDs

SV-206895r1137746_rule
SV-69643

Data mining is the analysis of large quantities of data to discover patterns and is used in intelligence gathering. Failure to detect attacks that use unauthorized data mining techniques to attack databases may result in the compromise of information. Injection attacks allow an attacker to inject code into a program or query or inject malware onto a computer to execute remote commands that can read or modify a database, or change data on a website. Web applications frequently access databases to store, retrieve, and update information. An attacker can construct inputs that the database will execute. This is most commonly referred to as a code injection attack. This type of attack includes XPath and LDAP injections. IPS component(s) with the capability to prevent code injections must be included in the IPS implementation to protect against unauthorized data mining. These components must include rules and anomaly detection algorithms to monitor for atypical database queries or accesses.

Checks: C-7149r1137744_chk

If the device being reviewed is an IDS, this is not applicable. Verify the IPS prevents code injection attacks launched against data storage objects, including, at a minimum, databases, database records, queries, and fields. If the IPS does not prevent code injection attacks launched against data storage objects, including, at a minimum, databases, database records, queries, and fields, this is a finding.

Fix: F-7149r1137745_fix

Configure the IPS components to prevent code injection attacks launched against data storage objects, including, at a minimum, databases, database records, queries, and fields.

b

To protect against unauthorized data mining, the IPS must prevent code injection attacks launched against application objects including, at a minimum, application URLs and application code.

AC-23 - Medium - CCI-002346 - V-206896 - SV-206896r1137749_rule

RMF Control

AC-23

Severity

M

CCI

CCI-002346

Version

SRG-NET-000318-IDPS-00182

Vuln IDs

V-206896
V-55399

Rule IDs

SV-206896r1137749_rule
SV-69645

Data mining is the analysis of large quantities of data to discover patterns and is used in intelligence gathering. Failure to detect attacks that use unauthorized data mining techniques to attack applications may result in the compromise of information. Injection attacks allow an attacker to inject code into a program or query or inject malware onto a computer to execute remote commands that can read or modify a database, or change data on a website. These attacks include buffer overrun, XML, JavaScript, and HTML injections. IPS component(s) with the capability to prevent code injections must be included in the IPS implementation to protect against unauthorized data mining. These components must include rules and anomaly detection algorithms to monitor for atypical database queries or accesses.

Checks: C-7150r1137747_chk

If the device being reviewed is an IDS, this is not applicable. Verify the IPS prevents code injection attacks launched against application objects including, at a minimum, application URLs and application code. If the IPS does not prevent code injection attacks launched against application objects including, at a minimum, application URLs and application code, this is a finding.

Fix: F-7150r1137748_fix

Configure the IPS to prevent code injection attacks launched against application objects including, at a minimum, application URLs and application code.

b

To protect against unauthorized data mining, the IPS must prevent SQL injection attacks launched against data storage objects, including, at a minimum, databases, database records, and database fields.

AC-23 - Medium - CCI-002346 - V-206897 - SV-206897r1137752_rule

RMF Control

AC-23

Severity

M

CCI

CCI-002346

Version

SRG-NET-000318-IDPS-00183

Vuln IDs

V-206897
V-55401

Rule IDs

SV-206897r1137752_rule
SV-69647

Data mining is the analysis of large quantities of data to discover patterns and is used in intelligence gathering. Failure to detect attacks that use unauthorized data mining techniques to attack databases may result in the compromise of information. SQL injection attacks are the most prevalent attacks against web applications and databases. These attacks inject SQL commands that can read, modify, or compromise the meaning of the original SQL query. An attacker can spoof identity; expose, tamper, destroy, or make existing data unavailable; or gain unauthorized privileges on the database server. IPS component(s) with the capability to prevent SQL code injections must be included in the IPS implementation to protect against unauthorized data mining. These components must include rules and anomaly detection algorithms to monitor for SQL injection attacks.

Checks: C-7151r1137750_chk

If the device being reviewed is an IDS, this is not applicable. Verify the IPS prevents SQL injection attacks launched against data storage objects, including, at a minimum, databases, database records, and database fields. If the IPS does not prevent SQL injection attacks launched against data storage objects, including, at a minimum, databases, database records, and database fields, this is a finding.

Fix: F-7151r1137751_fix

Configure the IPS to prevent SQL injection attacks launched against data storage objects, including, at a minimum, databases, database records, and database fields.

b

To protect against unauthorized data mining, the IDPS must detect code injection attacks launched against data storage objects, including, at a minimum, databases, database records, queries, and fields.

AC-23 - Medium - CCI-002347 - V-206898 - SV-206898r856536_rule

RMF Control

AC-23

Severity

M

CCI

CCI-002347

Version

SRG-NET-000319-IDPS-00184

Vuln IDs

V-206898
V-55403

Rule IDs

SV-206898r856536_rule
SV-69649

Data mining is the analysis of large quantities of data to discover patterns and is used in intelligence gathering. Failure to detect attacks that use unauthorized data mining techniques to attack databases may result in the compromise of information. Injection attacks allow an attacker to inject code into a program or query or inject malware onto a computer to execute remote commands that can read or modify a database, or change data on a website. Web applications frequently access databases to store, retrieve, and update information. An attacker can construct inputs that the database will execute. This is most commonly referred to as a code injection attack. This type of attack includes XPath and LDAP injections. IDPS component(s) with anomaly detection must be included in the IDPS implementation to protect against unauthorized data mining. These components must include rules and anomaly detection algorithms to monitor for atypical database queries or accesses.

Checks: C-7152r298206_chk

Verify the IDPS detects code injection attacks launched against data storage objects, including, at a minimum, databases, database records, queries, and fields. If the IDPS does not detect code injection attacks launched against data storage objects, including, at a minimum, databases, database records, queries, and fields, this is a finding.

Fix: F-7152r298207_fix

Configure the IDPS components to detect code injection attacks launched against data storage objects, including, at a minimum, databases, database records, queries, and fields.

b

To protect against unauthorized data mining, the IDPS must detect code injection attacks launched against application objects including, at a minimum, application URLs and application code.

AC-23 - Medium - CCI-002347 - V-206899 - SV-206899r856537_rule

RMF Control

AC-23

Severity

M

CCI

CCI-002347

Version

SRG-NET-000319-IDPS-00185

Vuln IDs

V-206899
V-55407

Rule IDs

SV-206899r856537_rule
SV-69653

Data mining is the analysis of large quantities of data to discover patterns and is used in intelligence gathering. Failure to detect attacks that use unauthorized data mining techniques to attack applications may result in the compromise of information. Injection attacks allow an attacker to inject code into a program or query or inject malware onto a computer to execute remote commands that can read or modify a database, or change data on a website. These attacks include buffer overrun, XML, JavaScript, and HTML injections. IDPS component(s) with anomaly detection must be included in the IDPS implementation. These components must include rules and anomaly detection algorithms to monitor for atypical application behavior, commands, and accesses.

Checks: C-7153r298209_chk

Verify the IDPS detects code injection attacks launched against application objects including, at a minimum, application URLs and application code. If the IDPS does not detect code injection attacks launched against application objects including, at a minimum, application URLs and application code, this is a finding.

Fix: F-7153r298210_fix

Configure the IDPS to detect code injection attacks launched against application objects including, at a minimum, application URLs and application code.

b

To protect against unauthorized data mining, the IDPS must detect SQL injection attacks launched against data storage objects, including, at a minimum, databases, database records, and database fields.

AC-23 - Medium - CCI-002347 - V-206900 - SV-206900r856538_rule

RMF Control

AC-23

Severity

M

CCI

CCI-002347

Version

SRG-NET-000319-IDPS-00186

Vuln IDs

V-206900
V-55409

Rule IDs

SV-206900r856538_rule
SV-69655

Data mining is the analysis of large quantities of data to discover patterns and is used in intelligence gathering. Failure to detect attacks that use unauthorized data mining techniques to attack databases may result in the compromise of information. SQL injection attacks are the most prevalent attacks against web applications and databases. These attacks inject SQL commands that can read, modify, or compromise the meaning of the original SQL query. An attacker can spoof identity; expose, tamper, destroy, or make existing data unavailable; or gain unauthorized privileges on the database server. IDPS component(s) with anomaly detection must be included in the IDPS implementation to monitor for and detect unauthorized data mining. These components must include rules and anomaly detection algorithms to monitor for SQL injection attacks.

Checks: C-7154r298212_chk

Verify the IDPS detects SQL injection attacks launched against data storage objects, including, at a minimum, databases, database records, and database fields. If the IDPS does not detect SQL injection attacks launched against data storage objects, including, at a minimum, databases, database records, and database fields, this is a finding.

Fix: F-7154r298213_fix

Configure the IDPS to detect SQL injection attacks launched against data storage objects, including, at a minimum, databases, database records, and database fields.

b

The IDPS must off-load log records to a centralized log server.

AU-4 - Medium - CCI-001851 - V-206902 - SV-206902r856540_rule

RMF Control

AU-4

Severity

M

CCI

CCI-001851

Version

SRG-NET-000334-IDPS-00191

Vuln IDs

V-206902
V-55325

Rule IDs

SV-206902r856540_rule
SV-69571

Information stored in one location is vulnerable to accidental or incidental deletion or alteration. Off-loading ensures audit information does not get overwritten if the limited audit storage capacity is reached and also protects the audit record in case the system/component being audited is compromised. This also prevents the log records from being lost if the logs stored locally are accidentally or intentionally deleted, altered, or corrupted.

Checks: C-7156r298218_chk

Verify the IDPS off-loads log records to a centralized log server. If the IDPS does not off-load log records to a centralized log server, this is a finding.

Fix: F-7156r298219_fix

Configure the IDPS to off-load log records to a centralized log server.

b

The IDPS must provide an alert to, at a minimum, the system administrator and ISSO when any audit failure events occur.

AU-5 - Medium - CCI-001858 - V-206903 - SV-206903r856541_rule

RMF Control

AU-5

Severity

M

CCI

CCI-001858

Version

SRG-NET-000335-IDPS-00014

Vuln IDs

V-206903
V-55331

Rule IDs

SV-206903r856541_rule
SV-69577

Without an alert, security personnel may be unaware of an impending failure of the audit capability, and the ability to perform forensic analysis may be impeded. This requirement includes, but is not limited to, failures where the detection and/or prevention function is unable to write events to either local storage or the centralized server. The IDPS must generate an alert which will notify designated personnel of the logging failure. Alerts provide organizations with urgent messages. The alert must provide these messages immediately (i.e., the time from event detection to alert occurs in seconds or less). Alert messages must include the severity level. The IDPS must either send the alert to a management console that is actively monitored by authorized personnel or use a messaging capability to send the alert directly to designated personnel. The ISSM or ISSO may designate the system administrator or other authorized personnel to receive the alert within the specified time, validate the alert, then forward only validated alerts to the ISSO.

Checks: C-7157r298221_chk

Verify the IDPS provides an alert to, at a minimum, the system administrator and ISSO when any audit failure events occur. If the IDPS does not provide an alert to, at a minimum, the system administrator and ISSO when any audit failure events occur, this is a finding.

Fix: F-7157r298222_fix

Configure the IDPS to provide an alert to, at a minimum, the system administrator and ISSO when any audit failure events occur.

b

The IDPS must assign a critical severity level to all audit processing failures.

AU-5 - Medium - CCI-001858 - V-206904 - SV-206904r856542_rule

RMF Control

AU-5

Severity

M

CCI

CCI-001858

Version

SRG-NET-000335-IDPS-00223

Vuln IDs

V-206904
V-55329

Rule IDs

SV-206904r856542_rule
SV-69575

It is critical that when the IDPS is at risk of failing to process audit logs as required, it takes action to mitigate the failure Audit processing failures include: software/hardware errors; failures in the audit capturing mechanisms; and audit storage capacity being reached or exceeded. Since action must be taken immediately, these messages will be designated as a critical severity level and this level must be sent as part of the alert message.

Checks: C-7158r298224_chk

Verify the IDPS provides assign a critical severity level to all audit processing failures. If the IDPS does not assign a critical severity level to all audit processing failures, this is a finding.

Fix: F-7158r298225_fix

Configure the IDPS to assign a critical severity level to all audit processing failures.

b

The IPS 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.

SC-5 - Medium - CCI-002385 - V-206905 - SV-206905r1137755_rule

RMF Control

SC-5

Severity

M

CCI

CCI-002385

Version

SRG-NET-000362-IDPS-00196

Vuln IDs

V-206905
V-55345

Rule IDs

SV-206905r1137755_rule
SV-69591

If the network does not provide safeguards against DoS attacks, network resources will be unavailable to users. Installation of IPS detection and prevention components (i.e., sensors) at key boundaries in the architecture mitigates the risk of DoS attacks. These attacks can be detected by matching observed communications traffic with patterns of known attacks and monitoring for anomalies in traffic volume/type. Detection components that use rate-based behavior analysis can detect attacks when signatures for the attack do not exist or are not installed. These attacks include zero-day attacks, which are new attacks for which vendors have not yet developed signatures. Rate-based behavior analysis can detect sophisticated, distributed DoS (DDoS) attacks by correlating traffic information from multiple network segments or components. This requirement applies to the communications traffic functionality of the IPS as it pertains to handling communications traffic, rather than to the IPS device itself.

Checks: C-7159r1137753_chk

If the device being reviewed is an IDS, this is not applicable. Verify the IPS protects against or limits the effects of known and unknown types of DoS attacks by employing rate-based attack prevention behavior analysis. If the device does not protect against or limit the effects of known and unknown types of DoS attacks by employing rate-based attack prevention behavior analysis, this is a finding.

Fix: F-7159r1137754_fix

Configure the IPS to protect against or limit the effects of known and unknown types of DoS attacks by employing rate-based attack prevention behavior analysis.

b

The IPS must protect against or limit the effects of known and unknown types of denial-of-service (DoS) attacks by employing anomaly-based attack detection.

SC-5 - Medium - CCI-002385 - V-206906 - SV-206906r1137758_rule

RMF Control

SC-5

Severity

M

CCI

CCI-002385

Version

SRG-NET-000362-IDPS-00197

Vuln IDs

V-206906
V-55347

Rule IDs

SV-206906r1137758_rule
SV-69593

If the network does not provide safeguards against DoS attacks, network resources will be unavailable to users. Installation of IPS detection and prevention components (i.e., sensors) at key boundaries in the architecture mitigates the risk of DoS attacks. These attacks can be detected by matching observed communications traffic with patterns of known attacks. Detection components that use anomaly-based attack detection can detect attacks when signatures for the attack do not exist or are not installed. These attacks include zero-day attacks, new attacks for which vendors have not yet developed signatures. This requirement applies to the communications traffic functionality of the IPS as it pertains to handling communications traffic, rather than to the IPS device itself.

Checks: C-7160r1137756_chk

If the device being reviewed is an IDS, this is not applicable. Verify the IPS protect against or limits the effects of known and unknown types of DoS attacks by employing, also known as anomaly-based detection. If the device does not protect against or limit the effects of known and unknown types of DoS attacks by employing anomaly-based detection, this is a finding.

Fix: F-7160r1137757_fix

Configure the IPS to protect against or limit the effects of known and unknown types of DoS attacks by employing anomaly-based detection.

b

The IPS must protect against or limit the effects of known types of denial-of-service (DoS) attacks by employing signatures.

SC-5 - Medium - CCI-002385 - V-206907 - SV-206907r1137761_rule

RMF Control

SC-5

Severity

M

CCI

CCI-002385

Version

SRG-NET-000362-IDPS-00198

Vuln IDs

V-206907
V-55349

Rule IDs

SV-206907r1137761_rule
SV-69595

If the network does not provide safeguards against DoS attacks, network resources will be unavailable to users. Installation of IPS detection and prevention components (i.e., sensors) at key boundaries in the architecture mitigates the risk of DoS attacks. These attacks can be detected by matching observed communications traffic with patterns of known attacks and monitoring for anomalies in traffic volume, type, or protocol usage. Detection components that use signatures can detect known attacks by using known attack signatures. Signatures are usually obtained from and updated by the IPS component vendor. These attacks include SYN-flood, ICMP-flood, and Land Attacks. This requirement applies to the communications traffic functionality of the IPS as it pertains to handling communications traffic, rather than to the IPS device itself.

Checks: C-7161r1137759_chk

If the device being reviewed is an IDS, this is not applicable. Verify the IPS protects against or limits the effects of known types of DoS attacks by employing signatures. If the device does not protect against or limit the effects of known types of DoS attacks by employing signatures, this is a finding.

Fix: F-7161r1137760_fix

Configure the IPS to protect against or limit the effects of known types of DoS attacks by employing signatures.

b

IDPS components, including sensors, event databases, and management consoles must integrate with a network-wide monitoring capability.

SI-4 - Medium - CCI-002656 - V-206909 - SV-206909r856546_rule

RMF Control

SI-4

Severity

M

CCI

CCI-002656

Version

SRG-NET-000383-IDPS-00208

Vuln IDs

V-206909
V-55365

Rule IDs

SV-206909r856546_rule
SV-69611

An integrated, network-wide intrusion detection capability increases the ability to detect and prevent sophisticated distributed attacks based on access patterns and characteristics of access. Integration is more than centralized logging and a centralized management console. The enclave's monitoring capability may include multiple sensors, IPS, sensor event databases, behavior-based monitoring devices, application-level content inspection systems, malicious code protection software, scanning tools, audit record monitoring software, and network monitoring software. Some tools may monitor external traffic while others monitor internal traffic at key boundaries. These capabilities may be implemented using different devices and therefore can have different security policies and severity-level schema. This is valuable because content filtering, monitoring, and prevention can become a bottleneck on the network if not carefully configured.

Checks: C-7163r298239_chk

Verify the IDPS integrates with a network-wide monitoring capability which includes sensors, event databases, and management consoles. If the IDPS does not integrate with a network-wide monitoring capability which includes sensors, event databases, and management consoles, this is a finding.

Fix: F-7163r298240_fix

Configure the IDPS components, including sensors, event databases, and management consoles to integrate with a network-wide monitoring capability.

b

The IDPS must detect network services that have not been authorized or approved by the ISSO or ISSM, at a minimum.

SI-4 - Medium - CCI-002683 - V-206910 - SV-206910r856547_rule

RMF Control

SI-4

Severity

M

CCI

CCI-002683

Version

SRG-NET-000384-IDPS-00209

Vuln IDs

V-206910
V-55375

Rule IDs

SV-206910r856547_rule
SV-69621

Unauthorized or unapproved network services lack organizational verification or validation and therefore may be unreliable or serve as malicious rogues for valid services. Examples of network services include service-oriented architectures (SOAs), cloud-based services (e.g., infrastructure as a service, platform as a service, or software as a service), cross-domain, Voice Over Internet Protocol, Instant Messaging, auto-execute, and file sharing. To comply with this requirement, the IDPS may be configured to detect services either directly or indirectly (i.e., by detecting traffic associated with a service).

Checks: C-7164r298242_chk

Verify the IDPS detects network services that have not been authorized or approved by the ISSO or ISSM, at a minimum. If the IDPS does not detect network services that have not been authorized or approved by the ISSO or ISSM, at a minimum, this is a finding.

Fix: F-7164r298243_fix

Configure the IDPS to detect network services that have not been authorized or approved by the ISSO or ISSM, at a minimum.

b

The IDPS must generate a log record when unauthorized network services are detected.

SI-4 - Medium - CCI-002684 - V-206911 - SV-206911r856548_rule

RMF Control

SI-4

Severity

M

CCI

CCI-002684

Version

SRG-NET-000385-IDPS-00210

Vuln IDs

V-206911
V-55377

Rule IDs

SV-206911r856548_rule
SV-69623

Unauthorized or unapproved network services lack organizational verification or validation and therefore may be unreliable or serve as malicious rogues for valid services. Examples of network services include service-oriented architectures (SOAs), cloud-based services (e.g., infrastructure as a service, platform as a service, or software as a service), cross-domain, Voice Over Internet Protocol, Instant Messaging, auto-execute, and file sharing.

Checks: C-7165r298245_chk

Verify the IDPS generates a log record when unauthorized network services are detected. If the IDPS does not generate a log record when unauthorized network services are detected, this is a finding.

Fix: F-7165r298246_fix

Configure the IDPS to generate a log record when unauthorized network services are detected.

b

The IDPS must generate an alert to the ISSM and ISSO, at a minimum, when unauthorized network services are detected.

SI-4 - Medium - CCI-002684 - V-206912 - SV-206912r856549_rule

RMF Control

SI-4

Severity

M

CCI

CCI-002684

Version

SRG-NET-000385-IDPS-00211

Vuln IDs

V-206912
V-55379

Rule IDs

SV-206912r856549_rule
SV-69625

Unauthorized or unapproved network services lack organizational verification or validation and therefore may be unreliable or serve as malicious rogues for valid services. Automated mechanisms can be used to send automatic alerts or notifications. Such automatic alerts or notifications can be conveyed in a variety of ways (e.g., telephonically, via electronic mail, via text message, or via websites). The IDPS must either send the alert to a management console that is actively monitored by authorized personnel or use a messaging capability to send the alert directly to designated personnel. The ISSM or ISSO may designate the system administrator or other authorized personnel to receive the alert within the specified time, validate the alert, then forward only validated alerts to the ISSO to the vulnerability discussion.

Checks: C-7166r298248_chk

Verify the IDPS generates an alert to the ISSM and ISSO, at a minimum, when unauthorized network services are detected. If the IDPS does not generate an alert to the ISSM and ISSO, at a minimum, when unauthorized network services are detected, this is a finding.

Fix: F-7166r298249_fix

Configure the IDPS to generate an alert to the ISSM and ISSo, at a minimum, when unauthorized network services are detected.

b

The IDPS must continuously monitor inbound communications traffic for unusual/unauthorized activities or conditions.

SI-4 - Medium - CCI-002661 - V-206913 - SV-206913r856550_rule

RMF Control

SI-4

Severity

M

CCI

CCI-002661

Version

SRG-NET-000390-IDPS-00212

Vuln IDs

V-206913
V-55381

Rule IDs

SV-206913r856550_rule
SV-69627

If inbound communications traffic is not continuously monitored for unusual/unauthorized activities or conditions, there will be times when hostile activity may not be noticed and defended against. Although some of the components in the site's content scanning solution may be used for periodic scanning assessment, the IDPS sensors and other components must provide continuous, 24 hours a day, 7 days a week monitoring. Unusual/unauthorized activities or conditions related to information system inbound communications traffic include, for example, internal traffic that indicates the presence of malicious code within organizational information systems or propagating among system components, the unauthorized exporting of information, or signaling to external information systems. Anomalies within organizational information systems include, for example, large file transfers, long-time persistent connections, use of unusual protocols and ports, and communications with suspected or known malicious external entities.

Checks: C-7167r298251_chk

Verify the IDPS continuously monitors inbound communications traffic for unusual/unauthorized activities or conditions. If the IDPS does not continuously monitor inbound communications traffic for unusual/unauthorized activities or conditions, this is a finding.

Fix: F-7167r298252_fix

Configure the IDPS to continuously monitor inbound communications traffic for unusual/unauthorized activities or conditions.

b

The IDPS must continuously monitor outbound communications traffic for unusual/unauthorized activities or conditions.

SI-4 - Medium - CCI-002662 - V-206914 - SV-206914r856551_rule

RMF Control

SI-4

Severity

M

CCI

CCI-002662

Version

SRG-NET-000391-IDPS-00213

Vuln IDs

V-206914
V-55383

Rule IDs

SV-206914r856551_rule
SV-69629

If outbound communications traffic is not continuously monitored for unusual/unauthorized activities or conditions, there will be times when hostile activity may not be noticed and defended against. Although some of the components in the site's content scanning solution may be used for periodic scanning assessment, the IDPS sensors and other components must provide continuous, 24 hours a day, 7 days a week monitoring. Unusual/unauthorized activities or conditions related to information system outbound communications traffic include, for example, internal traffic that indicates the presence of malicious code within organizational information systems or propagating among system components, the unauthorized exporting of information, or signaling to external information systems. Anomalies within organizational information systems include, for example, large file transfers, long-time persistent connections, use of unusual protocols and ports, and communications with suspected or known malicious external entities.

Checks: C-7168r298254_chk

Verify the IDPS continuously monitors outbound communications traffic for unusual/unauthorized activities or conditions. If the IDPS does not continuously monitor outbound communications traffic for unusual/unauthorized activities or conditions, this is a finding.

Fix: F-7168r298255_fix

Configure the IDPS to continuously monitor outbound communications traffic for unusual/unauthorized activities or conditions.

b

The IDPS must send an alert to, at a minimum, the information system security manager (ISSM) and information system security officer (ISSO) when intrusion detection events are detected which indicate a compromise or potential for compromise.

SI-4 - Medium - CCI-002664 - V-206915 - SV-206915r1107640_rule

RMF Control

SI-4

Severity

M

CCI

CCI-002664

Version

SRG-NET-000392-IDPS-00214

Vuln IDs

V-206915
V-55385

Rule IDs

SV-206915r1107640_rule
SV-69631

Without an alert, security personnel may be unaware of intrusion detection incidents that require immediate action and this delay may result in the loss or compromise of information. In accordance with CCI-001242, the IDPS is a real-time intrusion detection system. These systems must generate an alert when detection events from real-time monitoring occur. Alerts may be transmitted, for example, telephonically, by electronic mail messages, or by text messaging. The IDPS must either send the alert to a management console that is actively monitored by authorized personnel or use a messaging capability to send the alert directly to designated personnel. The ISSM or ISSO may designate the system administrator or other authorized personnel to receive the alert within the specified time, validate the alert, then forward only validated alerts to the ISSM and ISSO.

Checks: C-7169r1107638_chk

Verify the IDPS sends an alert to, at a minimum, the ISSM and ISSO when intrusion detection events are detected which indicate a compromise or potential for compromise. If the IDPS does not send an alert to, at a minimum, the ISSO and ISSM when intrusion detection events are detected which indicate a compromise or potential for compromise, this is a finding.

Fix: F-7169r1107639_fix

Configure the IDPS to send an alert to, at a minimum, the ISSO and ISSM when intrusion detection events are detected which indicate a compromise or potential for compromise.

b

The IDPS must send an alert to, at a minimum, the ISSM and ISSO when threats identified by authoritative sources (e.g., IAVMs or CTOs) are detected which indicate a compromise or potential for compromise.

SI-4 - Medium - CCI-002664 - V-206916 - SV-206916r971533_rule

RMF Control

SI-4

Severity

M

CCI

CCI-002664

Version

SRG-NET-000392-IDPS-00215

Vuln IDs

V-206916
V-55387

Rule IDs

SV-206916r971533_rule
SV-69633

Without an alert, security personnel may be unaware of an impending failure of the audit capability, and the ability to perform forensic analysis and detect rate-based and other anomalies will be impeded. Alerts may be transmitted, for example, telephonically, by electronic mail messages, or by text messaging. The IDPS must either send the alert to a management console that is actively monitored by authorized personnel or use a messaging capability to send the alert directly to designated personnel. The ISSM or ISSO may designate the system administrator or other authorized personnel to receive the alert within the specified time, validate the alert, then forward only validated alerts to the ISSM and ISSO.

Checks: C-7170r298260_chk

Verify the IDPS sends an alert to, at a minimum, the ISSM and ISSO when threats identified by authoritative sources (e.g., IAVMs or CTOs) are detected which indicate a compromise or potential for compromise. If the IDPS does not send an alert to, at a minimum, the ISSM and ISSO when threats identified by authoritative sources (e.g., IAVMs or CTOs) are detected which indicate a compromise or potential for compromise, this is a finding.

Fix: F-7170r298261_fix

Configure the IDPS to send an alert to, at a minimum, the ISSM and ISSO when threats identified by authoritative sources (e.g., IAVMs or CTOs) are detected which indicate a compromise or potential for compromise.

b

The IDPS must generate an alert to, at a minimum, the ISSM and ISSO when root level intrusion events which provide unauthorized privileged access are detected.

SI-4 - Medium - CCI-002664 - V-206917 - SV-206917r971533_rule

RMF Control

SI-4

Severity

M

CCI

CCI-002664

Version

SRG-NET-000392-IDPS-00216

Vuln IDs

V-206917
V-55389

Rule IDs

SV-206917r971533_rule
SV-69635

Without an alert, security personnel may be unaware of major detection incidents that require immediate action and this delay may result in the loss or compromise of information. CJCSM 6510.01B, "Cyber Incident Handling Program", lists nine Cyber Incident and Reportable Event Categories. DoD has determined that categories identified by CJCSM 6510.01B Major Indicators (category I, II, IV, and VII detection events) will require an alert when an event is detected. Alerts messages must include a severity level indicator or code as an indicator of the criticality of the incident. Since these incidents require immediate action, these messages are assigned a critical or level 1 priority/severity, depending on the system's priority schema. Alerts may be transmitted, for example, telephonically, by electronic mail messages, or by text messaging. The IDPS must either send the alert to a management console that is actively monitored by authorized personnel or use a messaging capability to send the alert directly to designated personnel. The ISSM or ISSO may designate the system administrator or other authorized personnel to receive the alert within the specified time, validate the alert, then forward only validated alerts to the ISSM and ISSO.

Checks: C-7171r298263_chk

Verify the IDPS sends an alert to, at a minimum, the ISSM and ISSO when root level intrusion events which provide unauthorized privileged access are detected. If the IDPS does not send an alert to, at a minimum, the ISSM and ISSO when root level intrusion events which provide unauthorized privileged access are detected, this is a finding.

Fix: F-7171r298264_fix

Configure the IDPS to send an alert to, at a minimum, the ISSM and ISSO when root level intrusion events which provide unauthorized privileged access are detected.

b

The IDPS must send an alert to, at a minimum, the ISSM and ISSO when user level intrusions which provide non-privileged access are detected.

SI-4 - Medium - CCI-002664 - V-206918 - SV-206918r971533_rule

RMF Control

SI-4

Severity

M

CCI

CCI-002664

Version

SRG-NET-000392-IDPS-00217

Vuln IDs

V-206918
V-55391

Rule IDs

SV-206918r971533_rule
SV-69637

Without an alert, security personnel may be unaware of major detection incidents that require immediate action and this delay may result in the loss or compromise of information. CJCSM 6510.01B, "Cyber Incident Handling Program", lists nine Cyber Incident and Reportable Event Categories. DoD has determined that categories identified by CJCSM 6510.01B Major Indicators (category I, II, IV, and VII detection events) will require an alert when an event is detected. Alerts messages must include a severity level indicator or code as an indicator of the criticality of the incident. Since these incidents require immediate action, these messages are assigned a critical or level 1 priority/severity, depending on the system's priority schema. Alerts may be transmitted, for example, telephonically, by electronic mail messages, or by text messaging. The IDPS must either send the alert to a management console that is actively monitored by authorized personnel or use a messaging capability to send the alert directly to designated personnel. The ISSM or ISSO may designate the system administrator or other authorized personnel to receive the alert within the specified time, validate the alert, then forward only validated alerts to the ISSM and ISSO.

Checks: C-7172r298266_chk

Verify the IDPS sends an alert to, at a minimum, the ISSM and ISSO when user level intrusions which provide non-privileged access are detected. If the IDPS does not send an alert to, at a minimum, the ISSM and ISSO when root level intrusion events when user level intrusions which provide non-privileged access are detected, this is a finding.

Fix: F-7172r298267_fix

Configure the IDPS to send an alert to, at a minimum, the ISSM and ISSO when user level intrusions which provide non-privileged access are detected.

b

The IDPS must send an alert to, at a minimum, the ISSM and ISSO when denial of service incidents are detected.

SI-4 - Medium - CCI-002664 - V-206919 - SV-206919r971533_rule

RMF Control

SI-4

Severity

M

CCI

CCI-002664

Version

SRG-NET-000392-IDPS-00218

Vuln IDs

V-206919
V-55393

Rule IDs

SV-206919r971533_rule
SV-69639

Without an alert, security personnel may be unaware of major detection incidents that require immediate action and this delay may result in the loss or compromise of information. CJCSM 6510.01B, "Cyber Incident Handling Program", lists nine Cyber Incident and Reportable Event Categories. DoD has determined that categories identified by CJCSM 6510.01B Major Indicators (category I, II, IV, and VII detection events) will require an alert when an event is detected. Alerts messages must include a severity level indicator or code as an indicator of the criticality of the incident. Since these incidents require immediate action, these messages are assigned a critical or level 1 priority/severity, depending on the system's priority schema. Alerts may be transmitted, for example, telephonically, by electronic mail messages, or by text messaging. The IDPS must either send the alert to a management console that is actively monitored by authorized personnel or use a messaging capability to send the alert directly to designated personnel. The ISSM or ISSO may designate the system administrator or other authorized personnel to receive the alert within the specified time, validate the alert, then forward only validated alerts to the ISSM and ISSO.

Checks: C-7173r298269_chk

Verify the IDPS sends an alert to, at a minimum, the ISSM and ISSO when denial of service incidents are detected. If the IDPS does not send an alert to, at a minimum, the ISSM and ISSO when root level intrusion events when denial of service incidents are detected, this is a finding.

Fix: F-7173r298270_fix

Configure the IDPS to send an alert to, at a minimum, the IAM and IAO when denial of service incidents are detected.

b

The IDPS must generate an alert to, at a minimum, the ISSM and ISSO when new active propagation of malware infecting DoD systems or malicious code adversely affecting the operations and/or security of DoD systems is detected.

SI-4 - Medium - CCI-002664 - V-206920 - SV-206920r971533_rule

RMF Control

SI-4

Severity

M

CCI

CCI-002664

Version

SRG-NET-000392-IDPS-00219

Vuln IDs

V-206920
V-55395

Rule IDs

SV-206920r971533_rule
SV-69641

Without an alert, security personnel may be unaware of major detection incidents that require immediate action and this delay may result in the loss or compromise of information. CJCSM 6510.01B, "Cyber Incident Handling Program", lists nine Cyber Incident and Reportable Event Categories. DoD has determined that categories identified by CJCSM 6510.01B Major Indicators (category I, II, IV, and VII detection events) will require an alert when an event is detected. Alerts messages must include a severity level indicator or code as an indicator of the criticality of the incident. Since these incidents require immediate action, these messages are assigned a critical or level 1 priority/severity, depending on the system's priority schema. Alerts may be transmitted, for example, telephonically, by electronic mail messages, or by text messaging. The IDPS must either send the alert to a management console that is actively monitored by authorized personnel or use a messaging capability to send the alert directly to designated personnel.

Checks: C-7174r298272_chk

Verify the IDPS sends an alert to, at a minimum, the ISSM and ISSO when new active propagation of malware infecting DoD systems or malicious code adversely affecting the operations and/or security of DoD systems is detected. If the IDPS does not send an alert to, at a minimum, the ISSM and ISSO when new active propagation of malware infecting DoD systems or malicious code adversely affecting the operations and/or security of DoD systems is detected, this is a finding.

Fix: F-7174r298273_fix

Configure the IDPS to send an alert to, at a minimum, the ISSM and ISSO when new active propagation of malware infecting DoD systems or malicious code adversely affecting the operations and/or security of DoD systems is detected.

b

The IDPS must, for fragmented packets, either block the packets or properly reassemble the packets before inspecting and forwarding.

SI-10 - Medium - CCI-001310 - V-206921 - SV-206921r383821_rule

RMF Control

SI-10

Severity

M

CCI

CCI-001310

Version

SRG-NET-000401-IDPS-00203

Vuln IDs

V-206921
V-55351

Rule IDs

SV-206921r383821_rule
SV-69597

Packet fragmentation is allowed by the TCP/IP specifications and is encouraged in situations where it is needed. However, packet fragmentation has been used to make some attacks harder to detect (by placing them within fragmented packets), and unusual fragmentation has also been used as a form of attack. For example, some network-based attacks have used packets that should not exist in normal communications, such as sending some fragments of a packet but not the first fragment, or sending packet fragments that overlap each other. These, and other types of packet fragmentation, aim to evade the IDPS. Since it is usually not possible to test this capability in a production environment, systems should either be validated in a testing environment or prior to installation. This requirement is usually a function of the design of the IDPS component. Compliance can be verified by acceptance/validation processes or vendor attestation.

Checks: C-7175r298275_chk

Verify the IDPS, for fragmented packets, either blocks the packets or properly reassembles the packets before inspecting and forwarding. For fragmented packets, if the IDPS does not either block the packets or properly reassemble the packets before inspecting and forwarding, this is a finding.

Fix: F-7175r298276_fix

Configure the IDPS to, for fragmented packets, either block the packets or properly reassemble the packets before inspecting and forwarding.

b

The IDPS must off-load log records to a centralized log server in real-time.

AU-4 - Medium - CCI-001851 - V-206922 - SV-206922r856558_rule

RMF Control

AU-4

Severity

M

CCI

CCI-001851

Version

SRG-NET-000511-IDPS-00012

Vuln IDs

V-206922
V-55327

Rule IDs

SV-206922r856558_rule
SV-69573

Off-loading ensures audit information does not get overwritten if the limited audit storage capacity is reached and also protects the audit record in case the system/component being audited is compromised. Off-loading is a common process in information systems with limited audit storage capacity. The audit storage on the IDPS is used only in a transitory fashion until the system can communicate with the centralized log server designated for storing the audit records, at which point the information is transferred. However, DoD requires that the log be transferred in real-time which indicates that the time from event detection to off-loading is seconds or less. This does not apply to audit logs generated on behalf of the device itself (management).

Checks: C-7176r298278_chk

Verify the IDPS off-loads log records to a centralized log server in real-time. If the IDPS does not off-load log records to a centralized log server in real-time, this is a finding.

Fix: F-7176r298279_fix

Configure the IDPS to off-load log records to a centralized log server in real-time.

b

The IDPS must be configured in accordance with the security configuration settings based on DoD security policy and technology-specific security best practices.

CM-6 - Medium - CCI-000366 - V-206923 - SV-206923r385561_rule

RMF Control

CM-6

Severity

M

CCI

CCI-000366

Version

SRG-NET-000512-IDPS-00194

Vuln IDs

V-206923
V-55337

Rule IDs

SV-206923r385561_rule
SV-69583

Configuring the IDPS to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements. Configuration settings are the set of parameters that can be changed that affect the security posture and/or functionality of the network element. Security-related parameters are those parameters impacting the security state of the network element, including the parameters required to satisfy other security control requirements. For the network element, security-related parameters include settings for communications traffic management configurations.

Checks: C-7177r298281_chk

Verify the IDPS is configured in accordance with the security configuration settings based on DoD security policy and technology-specific security best practices. If the IDPS is not configured in accordance with the security configuration settings based on DoD security policy and technology-specific security best practices, this is a finding.

Fix: F-7177r298282_fix

Configure the IDPS to comply with the security configuration settings based on DoD security policy and technology-specific security best practices.

b

The IDPS must employ organization-defined controls by type of denial-of-service (DoS) to achieve the DoS objective.

Medium - CCI-004866 - V-263663 - SV-263663r991597_rule

RMF Control

Severity

M

CCI

CCI-004866

Version

SRG-NET-000705-IDPS-00110

Vuln IDs

V-263663

Rule IDs

SV-263663r991597_rule

DoS events may occur due to a variety of internal and external causes, such as an attack by an adversary or a lack of planning to support organizational needs with respect to capacity and bandwidth. Such attacks can occur across a wide range of network protocols (e.g., IPv4, IPv6). A variety of technologies are available to limit or eliminate the origination and effects of DoS events. For example, boundary protection devices can filter certain types of packets to protect system components on internal networks from being directly affected by or the source of DoS attacks. Employing increased network capacity and bandwidth combined with service redundancy also reduces the susceptibility to DoS events.

Checks: C-67576r982262_chk

Verify the IDPS is configured to employ organization-defined controls by type of DoS to achieve the denial-of-service objective. If the IDPS is not configured to employ organization-defined controls by type of DoS to achieve the DoS objective, this is a finding.

Fix: F-67484r982263_fix

Configure the IDPS to employ organization-defined controls by type of DoS to achieve the DoS objective.

b

The IDPS must implement physically or logically separate subnetworks to isolate organization-defined critical system components and functions.

Medium - CCI-004891 - V-263664 - SV-263664r1137722_rule

RMF Control

Severity

M

CCI

CCI-004891

Version

SRG-NET-000715-IDPS-00120

Vuln IDs

V-263664

Rule IDs

SV-263664r1137722_rule

Separating critical system components and functions from other noncritical system components and functions through separate subnetworks may be necessary to reduce susceptibility to a catastrophic or debilitating breach or compromise that results in system failure. For example, physically separating the command and control function from the in-flight entertainment function through separate subnetworks in a commercial aircraft provides an increased level of assurance in the trustworthiness of critical system functions. This requirement also applies to Zero Trust initiatives.

Checks: C-67577r982570_chk

Verify the IDPS is configured to implement physically or logically separate subnetworks to isolate organization-defined critical system components and functions. If the IDPS is not configured to implement physically or logically separate subnetworks to isolate organization-defined critical system components and functions, this is a finding.

Fix: F-67485r982266_fix

Configure the IDPS to implement physically or logically separate subnetworks to isolate organization-defined critical system components and functions.

b

The IDPS must establish organization-defined alternate communications paths for system operations organizational command and control.

Medium - CCI-004931 - V-263665 - SV-263665r991599_rule

RMF Control

Severity

M

CCI

CCI-004931

Version

SRG-NET-000760-IDPS-00160

Vuln IDs

V-263665

Rule IDs

SV-263665r991599_rule

An incident, whether adversarial- or nonadversarial-based, can disrupt established communications paths used for system operations and organizational command and control. Alternate communications paths reduce the risk of all communications paths being affected by the same incident. To compound the problem, the inability of organizational officials to obtain timely information about disruptions or to provide timely direction to operational elements after a communications path incident, can impact the ability of the organization to respond to such incidents in a timely manner. Establishing alternate communications paths for command and control purposes, including designating alternative decision makers if primary decision makers are unavailable and establishing the extent and limitations of their actions, can greatly facilitate the organization's ability to continue to operate and take appropriate actions during an incident.

Checks: C-67578r982268_chk

Verify the IDPS is configured to establish organization-defined alternate communications paths for system operations organizational command and control. If the IDPS is not configured to establish organization-defined alternate communications paths for system operations organizational command and control, this is a finding.

Fix: F-67486r982269_fix

Configure the IDPS to establish organization-defined alternate communications paths for system operations organizational command and control.

b

The IDPS must use organization-defined security attributes associated with organization-defined information, source, and destination objects to enforce organization-defined information flow control policies as a basis for flow control decisions.

AC-4 - Medium - CCI-002190 - V-278978 - SV-278978r1137721_rule

RMF Control

AC-4

Severity

M

CCI

CCI-002190

Version

SRG-NET-000323-IDPS-00188

Vuln IDs

V-278978

Rule IDs

SV-278978r1137721_rule

A mechanism to detect and prevent unauthorized communication flow must be configured or provided as part of the system design. If information flow is not enforced based on approved authorizations, the system may become compromised. Information flow control regulates where information is allowed to travel within a system and between interconnected systems. Security attributes may be used to manage information flow control. Information flow enforcement mechanisms compare security attributes associated with information (data content and data structure) and source/destination objects, and respond appropriately (e.g., block, quarantine, alert administrator) when the mechanisms encounter information flows not allowed by information flow policies. For example, an information object labeled Secret would be allowed to flow to a destination object labeled Secret, but an information object labeled Top Secret would not be allowed to flow to a destination object labeled Secret. Security attributes can also include, for example, source and destination addresses employed in traffic filter firewalls. Flow enforcement using security attributes can be used, for example, to control the release of certain types of information. This requirement also applies to Zero Trust initiatives.

Checks: C-83526r1137719_chk

Verify that the IDPS is configured to use organization-defined security attributes associated with organization-defined information, source, and destination objects to enforce organization-defined information flow control policies as a basis for flow control decisions. If the IDPS does not use organization-defined security attributes associated with organization-defined information, source, and destination objects to enforce organization-defined information flow control policies as a basis for flow control decisions, this is a finding.

Fix: F-83431r1137720_fix

Configure the IDPS to use organization-defined security attributes associated with organization-defined information, source, and destination objects to enforce organization-defined information flow control policies as a basis for flow control decisions.

b

The IDPS must provide visibility into network traffic at external and key internal system interfaces to optimize the effectiveness of monitoring devices.

Medium - CCI-004982 - V-278979 - SV-278979r1137725_rule

RMF Control

Severity

M

CCI

CCI-004982

Version

SRG-NET-000775-IDPS-00170

Vuln IDs

V-278979

Rule IDs

SV-278979r1137725_rule

Encrypted traffic, asymmetric routing architectures, capacity and latency limitations, and transitioning from older to newer technologies (e.g., IPv4 to IPv6 network protocol transition) may result in blind spots for organizations when analyzing network traffic. Collecting, decrypting, pre-processing, and distributing only relevant traffic to monitoring devices can streamline the efficiency and use of devices and optimize traffic analysis. This requirement also applies to Zero Trust initiatives.

Checks: C-83527r1137723_chk

Verify the IDPS is configured to provide visibility into network traffic at external and key internal system interfaces to optimize the effectiveness of monitoring devices. If the IDPS does not provide visibility into network traffic at external and key internal system interfaces to optimize the effectiveness of monitoring devices, this is a finding.

Fix: F-83432r1137724_fix

Configure the IDPS to provide visibility into network traffic at external and key internal system interfaces to optimize the effectiveness of monitoring devices.

Added rules 2

Content changes 16

Checks: C-7118r1137712_chk

Fix: F-7118r1137713_fix

Generate Mitigation Statement:

Checks: C-7119r1137715_chk

Fix: F-7119r1137716_fix

Generate Mitigation Statement:

Checks: C-7120r298110_chk

Fix: F-7120r298111_fix

Generate Mitigation Statement:

Checks: C-7121r298113_chk

Fix: F-7121r298114_fix

Generate Mitigation Statement:

Checks: C-7122r298116_chk

Fix: F-7122r298117_fix

Generate Mitigation Statement:

Checks: C-7123r298119_chk

Fix: F-7123r298120_fix

Generate Mitigation Statement:

Checks: C-7124r298122_chk

Fix: F-7124r298123_fix

Generate Mitigation Statement:

Checks: C-7125r298125_chk

Fix: F-7125r298126_fix

Generate Mitigation Statement:

Checks: C-7128r298134_chk

Fix: F-7128r298135_fix

Generate Mitigation Statement:

Checks: C-7129r298137_chk

Fix: F-7129r298138_fix

Generate Mitigation Statement:

Checks: C-7130r298140_chk

Fix: F-7130r298141_fix

Generate Mitigation Statement:

Checks: C-7131r298143_chk

Fix: F-7131r298144_fix

Generate Mitigation Statement:

Checks: C-7132r298146_chk

Fix: F-7132r298147_fix

Generate Mitigation Statement:

Checks: C-7133r298149_chk

Fix: F-7133r298150_fix

Generate Mitigation Statement:

Checks: C-7134r298152_chk

Fix: F-7134r298153_fix

Generate Mitigation Statement:

Checks: C-7135r1137726_chk

Fix: F-7135r1137727_fix

Generate Mitigation Statement:

Checks: C-7136r298158_chk

Fix: F-7136r298159_fix

Generate Mitigation Statement:

Checks: C-7137r1137729_chk

Fix: F-7137r1137730_fix

Generate Mitigation Statement:

Checks: C-7138r298164_chk

Fix: F-7138r298165_fix

Generate Mitigation Statement:

Checks: C-7139r298167_chk

Fix: F-7139r298168_fix

Generate Mitigation Statement:

Checks: C-7141r298173_chk

Fix: F-7141r298174_fix

Generate Mitigation Statement:

Checks: C-7142r298176_chk

Fix: F-7142r298177_fix

Generate Mitigation Statement:

Checks: C-7143r1137732_chk

Fix: F-7143r1137733_fix

Generate Mitigation Statement:

Checks: C-7144r1137735_chk

Fix: F-7144r1137736_fix

Generate Mitigation Statement:

Checks: C-7145r298185_chk

Fix: F-7145r298186_fix

Generate Mitigation Statement:

Checks: C-7146r298188_chk

Fix: F-7146r298189_fix

Generate Mitigation Statement: