CCI-001190
Fail to an organization-defined known-system state for the following failures on the indicated components while preserving organization-defined system state information in failure.
The FortiGate firewall must fail to a secure state if the firewall filtering functions fail unexpectedly.
1 rule found Severity: Medium
1 rule found Severity: Medium
The WebSphere Application Server must be configured to perform complete application deployments when using A/B clusters.
1 rule found Severity: Low
The WebSphere Application servers with an RMF categorization of high must be in a high-availability (HA) cluster.
1 rule found Severity: Low
1 rule found Severity: Medium
Symantec ProxySG must fail to a secure state upon failure of initialization, shutdown, or abort actions.
1 rule found Severity: Medium
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 found Severity: Low
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).
2 rules found Severity: Medium
2 rules found Severity: Medium
Windows Defender Firewall with Advanced Security local firewall rules must not be merged with Group Policy settings when connected to a public network.
1 rule found Severity: Medium
Windows Defender Firewall with Advanced Security local connection rules must not be merged with Group Policy settings when connected to a public network.
1 rule found Severity: Medium
IDMS executing in a local mode batch environment must be able to manually recover or restore database areas affected by failed transactions.
1 rule found Severity: Low
The Ubuntu operating system must disable kernel core dumps so that it can fail to a secure state if system initialization fails, shutdown fails or aborts fail.
1 rule found Severity: Medium
The DNS server implementation must fail to a secure state if system initialization fails, shutdown fails, or aborts fail.
1 rule found Severity: Medium
The Enterprise Voice, Video, and Messaging Session Manager must fail to a secure state if system initialization fails, shutdown fails, or aborts fail.
1 rule found Severity: Medium
1 rule found Severity: Medium
Redis Enterprise DBMS must fail to a secure state if system initialization fails, shutdown fails, or aborts fail.
1 rule found Severity: Medium
Automation Controller must be configured to fail over to another system in the event of log subsystem failure.
1 rule found Severity: Medium
The router must be configured to stop forwarding traffic upon the failure of the following actions: system initialization, shutdown, or system abort.
1 rule found Severity: Medium
The TPS 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 (also known as "Fail closed").
1 rule found Severity: Medium
1 rule found Severity: Medium
The web server must be built to fail to a known safe state if system initialization fails, shutdown fails, or aborts fail.
1 rule found Severity: Medium
The Apache web server must be built to fail to a known safe state if system initialization fails, shutdown fails, or aborts fail.
2 rules found Severity: Medium
2 rules found Severity: Medium
1 rule found Severity: Medium
The application server must be capable of reverting to the last known good configuration in the event of failed installations and upgrades.
1 rule found Severity: Medium
1 rule found Severity: Medium
The application server must fail to a secure state if system initialization fails, shutdown fails, or aborts fail.
1 rule found Severity: Medium
Ubuntu 22.04 LTS must disable kernel core dumps so that it can fail to a secure state if system initialization fails, shutdown fails or aborts fail.
1 rule found Severity: Medium
The application must fail to a secure state if system initialization fails, shutdown fails, or aborts fail.
1 rule found Severity: High
The container platform runtime must fail to a secure state if system initialization fails, shutdown fails, or aborts fail.
1 rule found Severity: Medium
The DBMS must fail to a secure state if system initialization fails, shutdown fails, or aborts fail.
1 rule found Severity: Medium
The firewall must fail to a secure state upon the failure of the following: system initialization, shutdown, or system abort.
1 rule found Severity: Medium
The operating system must fail to a secure state if system initialization fails, shutdown fails, or aborts fail.
1 rule found Severity: Medium
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.
1 rule found Severity: Medium
The Mainframe Product must fail to a secure state if system initialization fails, shutdown fails, or aborts fail.
1 rule found Severity: Medium
1 rule found Severity: Medium
The UEM server must fail to a secure state if system initialization fails, shutdown fails, or aborts fail.
1 rule found Severity: Medium
1 rule found Severity: Medium
The NSX Tier-0 Gateway Firewall must deny network communications traffic by default and allow network communications traffic by exception.
1 rule found Severity: Medium
The NSX Tier-1 Gateway firewall must deny network communications traffic by default and allow network communications traffic by exception.
1 rule found Severity: Medium
ESX Agent Manager must fail to a known safe state if system initialization fails, shutdown fails, or aborts fail.
1 rule found Severity: Medium
The NSX Distributed Firewall must deny network communications traffic by default and allow network communications traffic by exception.
1 rule found Severity: Medium
Lookup Service must fail to a known safe state if system initialization fails, shutdown fails, or aborts fail.
1 rule found Severity: Medium
Performance Charts must fail to a known safe state if system initialization fails, shutdown fails, or aborts fail.
1 rule found Severity: Medium
The vCenter ESX Agent Manager service must be configured to fail to a known safe state if system initialization fails.
2 rules found Severity: Medium
The Security Token Service must fail to a known safe state if system initialization fails, shutdown fails, or aborts fail.
1 rule found Severity: Medium
The vCenter Lookup service must be configured to fail to a known safe state if system initialization fails.
2 rules found Severity: Medium
vSphere UI must fail to a known safe state if system initialization fails, shutdown fails, or aborts fail.
1 rule found Severity: Medium
The vCenter Perfcharts service must be configured to fail to a known safe state if system initialization fails.
2 rules found Severity: Medium
The VPN Gateway must fail to a secure state if system initialization fails, shutdown fails, or aborts fail.
1 rule found Severity: Medium
The vCenter STS service must be configured to fail to a known safe state if system initialization fails.
2 rules found Severity: Medium