Skip to content

SC-11 Trusted Path

Guidance: nonePolicy clause: noneWhat these mean

BaselinesImplementation levelEnhancements
Not in a baselineSystem1 (0 in a baseline)

Related controls: AC-16, AC-25, SC-12, SC-23

  • 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: organization-defined security functions].
NIST 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.

Baselines: Not in a baseline

  • (a) Provide a trusted communications path that is irrefutably distinguishable from other communications paths; and
  • (b) Initiate the trusted communications path for communications between the [Assignment: organization-defined security functions] of the system and the user.
Discussion and assessment objectives for SC-11(1)

An irrefutable communications path permits the system to initiate a trusted path, which necessitates that the user can unmistakably recognize the source of the communication as a trusted system component. For example, the trusted path may appear in an area of the display that other applications cannot access or be based on the presence of an identifier that cannot be spoofed.

Determine if:

  • SC-11(01)(a) a trusted communication path that is irrefutably distinguishable from other communication paths is provided;
  • SC-11(01)(b) the trusted communication path for communications between the [Assignment: organization-defined security functions] of the system and the user is initiated.

Examine: System and communications protection policy; procedures addressing trusted communication paths; security plan; system design documentation; system configuration settings and associated documentation; assessment results from independent, testing organizations; system audit records; system security plan; other relevant documents or records.

Interview: System/network administrators; organizational personnel with information security responsibilities; system developer.

Test: Mechanisms supporting and/or implementing trusted communication paths.

Objectives and methods for SC-11

Determine if:

  • SC-11a. a [Selection: physically; logically] isolated trusted communication path is provided for communications between the user and the trusted components of the system;
  • SC-11b. users are permitted to invoke the trusted communication path for communications between the user and the [Assignment: organization-defined security functions] of the system, including authentication and re-authentication, at a minimum.

Examine: System and communications protection policy; procedures addressing trusted communication paths; security plan; system design documentation; system configuration settings and associated documentation; assessment results from independent, testing organizations; system audit records; system security plan; other relevant documents or records.

Interview: System/network administrators; organizational personnel with information security responsibilities; system developer.

Test: Mechanisms supporting and/or implementing trusted communication paths.

Independent guidance, not an official NIST publication. Control text is from NIST SP 800-53 Rev. 5 and SP 800-53A (public domain). Original content is licensed CC BY 4.0; program templates and the downloadable kit are dedicated to the public domain under CC0 1.0.