Capacity
CCI-001665
Preserve organization-defined system state information in the event of a system failure.
Choose one
29
Rule
Severity: Medium
Enable systemd-journald Service
15
Rule
Severity: Medium
Disable KDump Kernel Crash Analyzer (kdump)
2
Rule
Severity: Medium
In the event of a system failure of the ALG function, the ALG must save diagnostic information, log system messages, and load the most current security policies, rules, and signatures when restarted.
2
Rule
Severity: Medium
In the event of a system failure, applications must preserve any information necessary to determine cause of failure and any information necessary to return to operations with least disruption to mission processes.
2
Rule
Severity: Low
A BIND 9.x server implementation must be configured to allow DNS administrators to audit all DNS server components, based on selectable event criteria, and produce audit records within all DNS server components that contain information for failed security verification tests, information to establish the outcome and source of the events, any information necessary to determine cause of failure, and any information necessary to return to operations with least disruption to mission processes.
2
Rule
Severity: Low
IDMS executing in a local mode batch environment must be able to manually recover or restore database areas affected by failed transactions.
2
Rule
Severity: Medium
In the event of a system failure, the DNS server implementation must preserve any information necessary to determine cause of failure and any information necessary to return to operations with least disruption to mission processes.
2
Rule
Severity: Medium
In the event of a system failure of the firewall function, the firewall must be configured to save diagnostic information, log system messages, and load the most current security policies, rules, and signatures when restarted.
1
Rule
Severity: Medium
In the event of a system failure, the Infoblox system must preserve any information necessary to determine cause of failure and any information necessary to return to operations with least disruption to mission processes.
1
Rule
Severity: Medium
In the event of a system failure of the DataPower Gateway function, the DataPower Gateway must save diagnostic information, log system messages, and load the most current security policies, rules, and signatures when restarted.
1
Rule
Severity: Medium
In the event of a system failure, DB2 must preserve any information necessary to determine cause of failure and any information necessary to return to operations with least disruption to mission processes.
2
Rule
Severity: Medium
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.
1
Rule
Severity: Medium
In the event of a system failure, The Infoblox system must preserve any information necessary to determine cause of failure and any information necessary to return to operations with least disruption to mission processes.
2
Rule
Severity: Medium
In the event of application failure, Mainframe Products must preserve any information necessary to determine the cause of failure and any information necessary to return to operations with the least disruption to mission processes.
1
Rule
Severity: Medium
In the event of a system failure, SQL Server must preserve any information necessary to return to operations with least disruption to mission processes.
2
Rule
Severity: Medium
The SDN controllers must be configured as a cluster in active/active or active/passive mode to preserve any information necessary to determine cause of a system failure and to maintain network operations with least disruption to workload processes and flows.
1
Rule
Severity: Medium
Tanium must be configured in a High-Availability (HA) setup to ensure minimal loss of data and minimal disruption to mission processes in the event of a system failure.
4
Rule
Severity: Medium
The Tanium Server and Client applications must have logging enabled.
1
Rule
Severity: Medium
The Tanium application must be configured in a High-Availability (HA) setup to ensure minimal loss of data and minimal disruption to mission processes in the event of a system failure.
2
Rule
Severity: Medium
In the event of a system failure, the UEM server must preserve any information necessary to determine cause of failure and any information necessary to return to operations with least disruption to mission processes.
1
Rule
Severity: Low
The NSX-T Distributed Firewall must deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception).
1
Rule
Severity: Medium
The NSX-T Controller must be configured as a cluster in active/active mode to preserve any information necessary to determine cause of a system failure and to maintain network operations with least disruption to workload processes and flows.
2
Rule
Severity: Medium
The NSX-T Tier-1 Gateway Firewall must deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception).
3
Rule
Severity: Medium
The Ubuntu operating system must be configured to preserve log records from failure events.
2
Rule
Severity: Medium
The container platform must preserve any information necessary to determine the cause of the disruption or failure.
3
Rule
Severity: Medium
In the event of a system failure, the DBMS must preserve any information necessary to determine cause of failure and any information necessary to return to operations with least disruption to mission processes.
2
Rule
Severity: Medium
In the event of a system failure, the operating system must preserve any information necessary to determine cause of failure and any information necessary to return to operations with least disruption to mission processes.
2
Rule
Severity: Medium
In the event of a system failure, AIX must preserve any information necessary to determine cause of failure and any information necessary to return to operations with least disruption to mission processes.
4
Rule
Severity: Medium
IBM z/OS must specify SMF data options to assure appropriate activation.
2
Rule
Severity: Medium
IBM z/OS must specify SMF data options to ensure appropriate activation.
2
Rule
Severity: Medium
In the event of a system failure, MariaDB must preserve any information necessary to determine cause of failure and any information necessary to return to operations with least disruption to mission processes.
2
Rule
Severity: Medium
MongoDB must fail to a secure state if system initialization fails, shutdown fails, or aborts fail.
2
Rule
Severity: Medium
In the event of a system failure, hardware loss or disk failure, SQL Server must be able to restore necessary databases with least disruption to mission processes.
3
Rule
Severity: Medium
The DBMS must preserve any organization-defined system state information in the event of a system failure.
2
Rule
Severity: Medium
OL 8 must disable kernel dumps unless needed.
2
Rule
Severity: Medium
In the event of a system failure, Redis Enterprise DBMS must preserve any information necessary to determine cause of failure and any information necessary to return to operations with least disruption to mission processes.
2
Rule
Severity: Medium
RHEL 9 systemd-journald service must be enabled.
2
Rule
Severity: Medium
In the event of a system failure, the VMM must preserve any information necessary to determine cause of failure and any information necessary to return to operations with least disruption to mission processes.
1
Rule
Severity: Medium
VMware Postgres must write log entries to disk prior to returning operation success or failure.
3
Rule
Severity: Medium
The vCenter PostgreSQL service must write log entries to disk prior to returning operation success or failure.
2
Rule
Severity: Medium
In the event of a system failure, the Windows DNS Server must preserve any information necessary to determine cause of failure and any information necessary to return to operations with least disruption to mission processes.
1
Rule
Severity: Medium
Ubuntu 22.04 LTS must be configured to preserve log records from failure events.
1
Rule
Severity: Medium
In the event of a device failure, Enterprise Voice, Video, and Messaging Endpoints must preserve any information necessary to determine cause of failure and return to operations with least disruption to service.
1
Rule
Severity: Medium
In the event of a system failure, Enterprise Voice, Video, and Messaging Session Managers must be configured to preserve any information necessary to determine cause of failure and any information necessary to return to operations with least disruption to mission processes.
1
Rule
Severity: Medium
MKE must preserve any information necessary to determine the cause of the disruption or failure.
1
Rule
Severity: Medium
The TOSS operating system must be configured to preserve log records from failure events.
Patternfly
PatternFly elements
The content of the drawer really is up to you. It could have form fields, definition lists, text lists, labels, charts, progress bars, etc. Spacing recommendation is 24px margins. You can put tabs in here, and can also make the drawer scrollable.
Modules
66%