SC-11 Trusted Path
All changes in this version
Title
Trusted Path
Control
a. Provide a [Selection: physically; logically] isolated trusted communications path for communications between the user and the trusted components of the system; and
b. Permit users to invoke the trusted communications path for communications between the user and the following security functions of the system, including at a minimum, authentication and re-authentication: [Assignment: security functions].
Discussion
Trusted paths are mechanisms by which users can communicate (using input devices such as keyboards) directly with the security functions of systems with the requisite assurance to support security policies. Trusted path mechanisms can only be activated by users or the security functions of organizational systems. User responses that occur via trusted paths are protected from modification by and disclosure to untrusted applications. Organizations employ trusted paths for trustworthy, high-assurance connections between security functions of systems and users, including during system logons. The original implementations of trusted paths employed an out-of-band signal to initiate the path, such as using the <BREAK> key, which does not transmit characters that can be spoofed. In later implementations, a key combination that could not be hijacked was used (e.g., the <CTRL> + <ALT> + <DEL> keys). Such key combinations, however, are platform-specific and may not provide a trusted path implementation in every case. The enforcement of trusted communications paths is provided by a specific implementation that meets the reference monitor concept.
Parameters
sc-11_odp.01: [physically; logically]
sc-11_odp.02: security functions
Related controls
ac-16, ac-25, sc-12, sc-23
STIG rules that implement this control 18
Apple macOS 15 (Sequoia) V1R8
- APPL-15-004022 CAT II The macOS system must require users to reauthenticate for privilege escalation when using the "sudo" command.
- APPL-15-004060 CAT II The macOS system must configure sudoers timestamp type.
Application Security and Development V6R5
- APSC-DV-001520 CAT II The application must require users to reauthenticate when organization-defined circumstances or situations require reauthentication.
Canonical Ubuntu 22.04 LTS V2R10
- UBTU-22-432010 CAT II Ubuntu 22.04 LTS must require users to reauthenticate for privilege escalation or when changing roles.
- UBTU-22-432011 CAT II Ubuntu 22.04 LTS must require users to provide a password for privilege escalation.
- UBTU-22-654224 CAT II The operating system must restrict privilege elevation to authorized personnel.
Canonical Ubuntu 24.04 LTS V1R7
- UBTU-24-300019 CAT II Ubuntu 24.04 LTS must restrict privilege elevation to authorized personnel.
Microsoft Windows Server 2025 V1R4
- WN25-CC-000340 CAT II Windows Server 2025 must not save passwords in the Remote Desktop Client.
- WN25-CC-000360 CAT II Windows Server 2025 Remote Desktop Services must always prompt a client for passwords upon connection.
- WN25-CC-000520 CAT II Windows Server 2025 Windows Remote Management (WinRM) service must not store RunAs credentials.
- WN25-SO-000380 CAT II Windows Server 2025 User Account Control (UAC) approval mode for the built-in Administrator must be enabled.
- WN25-SO-000410 CAT II Windows Server 2025 User Account Control (UAC) must automatically deny standard user requests for elevation.
- WN25-SO-000440 CAT II Windows Server 2025 User Account Control (UAC) must run all administrators in Admin Approval Mode, enabling UAC.
Red Hat Enterprise Linux 9 V2R10
- RHEL-09-432015 CAT II RHEL 9 must require reauthentication when using the "sudo" command.
- RHEL-09-432025 CAT II RHEL 9 must require users to reauthenticate for privilege escalation.
- RHEL-09-432035 CAT II RHEL 9 must restrict the use of the "su" command.
- RHEL-09-611085 CAT II RHEL 9 must require users to provide a password for privilege escalation.
- RHEL-09-611145 CAT II RHEL 9 must not be configured to bypass password requirements for privilege escalation.