CCI|CCI-001665

Title

The information system preserves organization-defined system state information in the event of a system failure.

Reference Item Details

Category: 2010

Audit Items

View all Reference Audit Items

NamePluginAudit Name
AIX7-00-003109 - 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.UnixDISA STIG AIX 7.x v2r6
Big Sur - Configure System to Fail to a Known Safe State if System Initialization, Shutdown, or Abort FailsUnixNIST macOS Big Sur v1.4.0 - 800-53r4 High
Big Sur - Configure System to Fail to a Known Safe State if System Initialization, Shutdown, or Abort FailsUnixNIST macOS Big Sur v1.4.0 - 800-53r5 High
Big Sur - Configure System to Fail to a Known Safe State if System Initialization, Shutdown, or Abort FailsUnixNIST macOS Big Sur v1.4.0 - All Profiles
BIND-9X-001010 - 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 - categoryUnixDISA BIND 9.x STIG v2r2
BIND-9X-001010 - 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 - channelUnixDISA BIND 9.x STIG v2r2
BIND-9X-001010 - 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 - loggingUnixDISA BIND 9.x STIG v2r2
Catalina - Configure System to Fail to a Known Safe State if System Initialization, Shutdown, or Abort FailsUnixNIST macOS Catalina v1.5.0 - 800-53r5 High
Catalina - Configure System to Fail to a Known Safe State if System Initialization, Shutdown, or Abort FailsUnixNIST macOS Catalina v1.5.0 - 800-53r4 High
Catalina - Configure System to Fail to a Known Safe State if System Initialization, Shutdown, or Abort FailsUnixNIST macOS Catalina v1.5.0 - All Profiles
DB2X-00-005300 - 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 - HistoryUnixDISA STIG IBM DB2 v10.5 LUW v1r4 OS Linux
DB2X-00-005300 - 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 - HistoryWindowsDISA STIG IBM DB2 v10.5 LUW v1r4 OS Windows
DB2X-00-005300 - 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 - Recovery PlanUnixDISA STIG IBM DB2 v10.5 LUW v1r4 OS Linux
DB2X-00-005300 - 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 - Recovery PlanWindowsDISA STIG IBM DB2 v10.5 LUW v1r4 OS Windows
DB2X-00-005300 - 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 - Roll forwardUnixDISA STIG IBM DB2 v10.5 LUW v1r4 OS Linux
DB2X-00-005300 - 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 - Roll forwardWindowsDISA STIG IBM DB2 v10.5 LUW v1r4 OS Windows
DB2X-00-005300 - 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 - TestedUnixDISA STIG IBM DB2 v10.5 LUW v1r4 OS Linux
DB2X-00-005300 - 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 - TestedWindowsDISA STIG IBM DB2 v10.5 LUW v1r4 OS Windows
ESXI-06-000044 - The system must enable kernel core dumps.UnixDISA STIG VMware vSphere 6.x ESXi OS v1r5
ESXI-65-000044 - The ESXi host must enable kernel core dumps.UnixDISA STIG VMware vSphere ESXi OS 6.5 v2r3
ESXI-67-000044 - The ESXi host must enable kernel core dumps.UnixDISA STIG VMware vSphere 6.7 ESXi OS v1r2
MD3X-00-000420 - MongoDB must fail to a secure state if system initialization fails, shutdown fails, or aborts fail.UnixDISA STIG MongoDB Enterprise Advanced 3.x v2r1 OS
MD4X-00-000800 - MongoDB must fail to a secure state if system initialization fails, shutdown fails, or aborts fail.UnixDISA STIG MongoDB Enterprise Advanced 4.x v1r1 OS
Monterey - Configure System to Fail to a Known Safe State if System Initialization, Shutdown, or Abort FailsUnixNIST macOS Monterey v1.0.0 - 800-53r5 High
Monterey - Configure System to Fail to a Known Safe State if System Initialization, Shutdown, or Abort FailsUnixNIST macOS Monterey v1.0.0 - 800-53r4 High
Monterey - Configure System to Fail to a Known Safe State if System Initialization, Shutdown, or Abort FailsUnixNIST macOS Monterey v1.0.0 - All Profiles
OL08-00-010670 - OL 8 must disable kernel dumps unless needed.UnixDISA Oracle Linux 8 STIG v1r4
OL08-00-010670 - OL 8 must disable kernel dumps unless needed.UnixDISA Oracle Linux 8 STIG v1r2
UBTU-18-010022 - The Ubuntu operating system must be configured to preserve log records from failure events - activeUnixDISA STIG Ubuntu 18.04 LTS v2r8
UBTU-18-010022 - The Ubuntu operating system must be configured to preserve log records from failure events - enabledUnixDISA STIG Ubuntu 18.04 LTS v2r8
UBTU-18-010022 - The Ubuntu operating system must be configured to preserve log records from failure events - installedUnixDISA STIG Ubuntu 18.04 LTS v2r8
UBTU-20-010432 - The Ubuntu operating system must be configured to preserve log records from failure events - activeUnixDISA STIG Ubuntu 20.04 LTS v1r5
UBTU-20-010432 - The Ubuntu operating system must be configured to preserve log records from failure events - enabledUnixDISA STIG Ubuntu 20.04 LTS v1r5
UBTU-20-010432 - The Ubuntu operating system must be configured to preserve log records from failure events - rsyslogUnixDISA STIG Ubuntu 20.04 LTS v1r5
VCPG-67-000016 - VMware Postgres must write log entries to disk prior to returning operation success or failure - fsyncUnixDISA STIG VMware vSphere 6.7 PostgreSQL v1r1
VCPG-67-000016 - VMware Postgres must write log entries to disk prior to returning operation success or failure - full_page_writesUnixDISA STIG VMware vSphere 6.7 PostgreSQL v1r1
VCPG-67-000016 - VMware Postgres must write log entries to disk prior to returning operation success or failure - synchronous_commitUnixDISA STIG VMware vSphere 6.7 PostgreSQL v1r1