Title

The UEM server must fail to a secure state if system initialization fails, shutdown fails, or aborts fail. (Cat II impact)

Discussion

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. Applications or systems that fail suddenly and with no incorporated failure state planning may leave the hosting system available but with a reduced security protection capability. Preserving information system state information also facilitates system restart and return to the operational mode of the organization with less disruption of mission-essential processes. In general, application security mechanisms should be designed so that a failure will follow the same execution path as disallowing the operation. For example, security methods, such as isAuthorized(), isAuthenticated(), and validate(), should all return false if there is an exception during processing. If security controls can throw exceptions, they must be very clear about exactly what that condition means. Abort refers to stopping a program or function before it has finished naturally. The term abort refers to both requested and unexpected terminations. Satisfies:FPT_TST_EXT.1.2

Check Content

Verify the UEM server fails to a secure state if system initialization fails, shutdown fails, or aborts fail. If the UEM server does not fail to a secure state if system initialization fails, shutdown fails, or aborts fail, this is a finding.

Fix Text

Configure the UEM server to fail to a secure state if system initialization fails, shutdown fails, or aborts fail.

Additional Identifiers

Rule ID: SV-234409r961122_rule

Vulnerability ID: V-234409

Group Title: SRG-APP-000225

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.