a. Develop, document, and disseminate to {{ insert: param, sc-1_prm_1 }}: 1. {{ insert: param, sc-01_odp.03 }} system and communications protection policy that: (a) Addresses purpose, s...

Separate user functionality, including user interface services, from system management functionality.

Prevent the presentation of system management functionality at interfaces to non-privileged users.

Store state information from applications and software separately.

Isolate security functions from nonsecurity functions.

Employ hardware separation mechanisms to implement security function isolation.

Isolate security functions enforcing access and information flow control from nonsecurity functions and from other security functions.

Minimize the number of nonsecurity functions included within the isolation boundary containing security functions.

Implement security functions as largely independent modules that maximize internal cohesiveness within modules and minimize coupling between modules.

Implement security functions as a layered structure minimizing interactions between layers of the design and avoiding any dependence by lower layers on the functionality or correctness of higher la...

Prevent unauthorized and unintended information transfer via shared system resources.

Prevent unauthorized information transfer via shared resources in accordance with {{ insert: param, sc-04.02_odp }} when system processing explicitly switches between different information classifi...

a. {{ insert: param, sc-05_odp.02 }} the effects of the following types of denial-of-service events: {{ insert: param, sc-05_odp.01 }} ; and b. Employ the following controls to achieve the deni...

Restrict the ability of individuals to launch the following denial-of-service attacks against other systems: {{ insert: param, sc-05.01_odp }}.

Manage capacity, bandwidth, or other redundancy to limit the effects of information flooding denial-of-service attacks.

(a) Employ the following monitoring tools to detect indicators of denial-of-service attacks against, or launched from, the system: {{ insert: param, sc-05.03_odp.01 }} ; and (b) Monitor the fol...

Protect the availability of resources by allocating {{ insert: param, sc-06_odp.01 }} by {{ insert: param, sc-06_odp.02 }}.

a. Monitor and control communications at the external managed interfaces to the system and at key internal managed interfaces within the system; b. Implement subnetworks for publicly accessible...

Limit the number of external network connections to the system.

(a) Implement a managed interface for each external telecommunication service; (b) Establish a traffic flow policy for each managed interface; (c) Protect the confidentiality and integrity of...

Deny network communications traffic by default and allow network communications traffic by exception {{ insert: param, sc-07.05_odp.01 }}.

Prevent split tunneling for remote devices connecting to organizational systems unless the split tunnel is securely provisioned using {{ insert: param, sc-07.07_odp }}.

Route {{ insert: param, sc-07.08_odp.01 }} to {{ insert: param, sc-07.08_odp.02 }} through authenticated proxy servers at managed interfaces.

(a) Detect and deny outgoing communications traffic posing a threat to external systems; and (b) Audit the identity of internal users associated with denied communications.

(a) Prevent the exfiltration of information; and (b) Conduct exfiltration tests {{ insert: param, sc-07.10_odp }}.

Only allow incoming communications from {{ insert: param, sc-07.11_odp.01 }} to be routed to {{ insert: param, sc-07.11_odp.02 }}.

Implement {{ insert: param, sc-07.12_odp.01 }} at {{ insert: param, sc-07.12_odp.02 }}.

Isolate {{ insert: param, sc-07.13_odp }} from other internal system components by implementing physically separate subnetworks with managed interfaces to other components of the system.

Protect against unauthorized physical connections at {{ insert: param, sc-07.14_odp }}.

Route networked, privileged accesses through a dedicated, managed interface for purposes of access control and auditing.

Prevent the discovery of specific system components that represent a managed interface.

Enforce adherence to protocol formats.

Prevent systems from entering unsecure states in the event of an operational failure of a boundary protection device.

Block inbound and outbound communications traffic between {{ insert: param, sc-07.19_odp }} that are independently configured by end users and external service providers.

Provide the capability to dynamically isolate {{ insert: param, sc-07.20_odp }} from other system components.

Employ boundary protection mechanisms to isolate {{ insert: param, sc-07.21_odp.01 }} supporting {{ insert: param, sc-07.21_odp.02 }}.

Implement separate network addresses to connect to systems in different security domains.

Disable feedback to senders on protocol format validation failure.

For systems that process personally identifiable information: (a) Apply the following processing rules to data elements of personally identifiable information: {{ insert: param, sc-07.24_odp }}; ...

Prohibit the direct connection of {{ insert: param, sc-07.25_odp.01 }} to an external network without the use of {{ insert: param, sc-07.25_odp.02 }}.

Prohibit the direct connection of a classified national security system to an external network without the use of {{ insert: param, sc-07.26_odp }}.

Prohibit the direct connection of {{ insert: param, sc-07.27_odp.01 }} to an external network without the use of {{ insert: param, sc-07.27_odp.02 }}.

Prohibit the direct connection of {{ insert: param, sc-07.28_odp }} to a public network.

Implement {{ insert: param, sc-07.29_odp.01 }} separate subnetworks to isolate the following critical system components and functions: {{ insert: param, sc-07.29_odp.02 }}.

Protect the {{ insert: param, sc-08_odp }} of transmitted information.

Implement cryptographic mechanisms to {{ insert: param, sc-08.01_odp }} during transmission.

Maintain the {{ insert: param, sc-08.02_odp }} of information during preparation for transmission and during reception.

Implement cryptographic mechanisms to protect message externals unless otherwise protected by {{ insert: param, sc-08.03_odp }}.

Implement cryptographic mechanisms to conceal or randomize communication patterns unless otherwise protected by {{ insert: param, sc-08.04_odp }}.

Implement {{ insert: param, sc-08.05_odp.01 }} to {{ insert: param, sc-08.05_odp.02 }} during transmission.

Terminate the network connection associated with a communications session at the end of the session or after {{ insert: param, sc-10_odp }} of inactivity.

a. Provide a {{ insert: param, sc-11_odp.01 }} isolated trusted communications path for communications between the user and the trusted components of the system; and b. Permit users to invoke t...

(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 {{...

Establish and manage cryptographic keys when cryptography is employed within the system in accordance with the following key management requirements: {{ insert: param, sc-12_odp }}.

Maintain availability of information in the event of the loss of cryptographic keys by users.

Produce, control, and distribute symmetric cryptographic keys using {{ insert: param, sc-12.02_odp }} key management technology and processes.

Produce, control, and distribute asymmetric cryptographic keys using {{ insert: param, sc-12.03_odp }}.

Maintain physical control of cryptographic keys when stored information is encrypted by external service providers.

a. Determine the {{ insert: param, sc-13_odp.01 }} ; and b. Implement the following types of cryptography required for each specified cryptographic use: {{ insert: param, sc-13_odp.02 }}.

a. Prohibit remote activation of collaborative computing devices and applications with the following exceptions: {{ insert: param, sc-15_odp }} ; and b. Provide an explicit indication of use to...

Provide {{ insert: param, sc-15.01_odp }} disconnect of collaborative computing devices in a manner that supports ease of use.

Disable or remove collaborative computing devices and applications from {{ insert: param, sc-15.03_odp.01 }} in {{ insert: param, sc-15.03_odp.02 }}.

Provide an explicit indication of current participants in {{ insert: param, sc-15.04_odp }}.

Associate {{ insert: param, sc-16_prm_1 }} with information exchanged between systems and between system components.

Verify the integrity of transmitted security and privacy attributes.

Implement anti-spoofing mechanisms to prevent adversaries from falsifying the security attributes indicating the successful application of the security process.

Implement {{ insert: param, sc-16.03_odp }} to bind security and privacy attributes to transmitted information.

a. Issue public key certificates under an {{ insert: param, sc-17_odp }} or obtain public key certificates from an approved service provider; and b. Include only approved trust anchors in trust...

a. Define acceptable and unacceptable mobile code and mobile code technologies; and b. Authorize, monitor, and control the use of mobile code within the system.

Identify {{ insert: param, sc-18.01_odp.01 }} and take {{ insert: param, sc-18.01_odp.02 }}.

Verify that the acquisition, development, and use of mobile code to be deployed in the system meets {{ insert: param, sc-18.02_odp }}.

Prevent the download and execution of {{ insert: param, sc-18.03_odp }}.

Prevent the automatic execution of mobile code in {{ insert: param, sc-18.04_odp.01 }} and enforce {{ insert: param, sc-18.04_odp.02 }} prior to executing the code.

Allow execution of permitted mobile code only in confined virtual machine environments.

Technology-specific; addressed as any other technology or protocol.

a. Provide additional data origin authentication and integrity verification artifacts along with the authoritative name resolution data the system returns in response to external name/address res...

Provide data origin and integrity protection artifacts for internal name/address resolution queries.

Request and perform data origin authentication and data integrity verification on the name/address resolution responses the system receives from authoritative sources.

Ensure the systems that collectively provide name/address resolution service for an organization are fault-tolerant and implement internal and external role separation.

Protect the authenticity of communications sessions.

Invalidate session identifiers upon user logout or other session termination.

Generate a unique session identifier for each session with {{ insert: param, sc-23.03_odp }} and recognize only session identifiers that are system-generated.

Only allow the use of {{ insert: param, sc-23.05_odp }} for verification of the establishment of protected sessions.

Fail to a {{ insert: param, sc-24_odp.02 }} for the following failures on the indicated components while preserving {{ insert: param, sc-24_odp.03 }} in failure: {{ insert: param, sc-24_odp.01 }}.

Employ minimal functionality and information storage on the following system components: {{ insert: param, sc-25_odp }}.

Include components within organizational systems specifically designed to be the target of malicious attacks for detecting, deflecting, and analyzing such attacks.

Include within organizational systems the following platform independent applications: {{ insert: param, sc-27_odp }}.

Protect the {{ insert: param, sc-28_odp.01 }} of the following information at rest: {{ insert: param, sc-28_odp.02 }}.

Implement cryptographic mechanisms to prevent unauthorized disclosure and modification of the following information at rest on {{ insert: param, sc-28.01_odp.02 }}: {{ insert: param, sc-28.01_odp.0...

Remove the following information from online storage and store offline in a secure location: {{ insert: param, sc-28.02_odp }}.

Provide protected storage for cryptographic keys {{ insert: param, sc-28.03_odp.01 }}.

Employ a diverse set of information technologies for the following system components in the implementation of the system: {{ insert: param, sc-29_odp }}.

Employ virtualization techniques to support the deployment of a diversity of operating systems and applications that are changed {{ insert: param, sc-29.01_odp }}.

Employ the following concealment and misdirection techniques for {{ insert: param, sc-30_odp.02 }} at {{ insert: param, sc-30_odp.03 }} to confuse and mislead adversaries: {{ insert: param, sc-30_o...

Employ {{ insert: param, sc-30.02_odp }} to introduce randomness into organizational operations and assets.

Change the location of {{ insert: param, sc-30.03_odp.01 }} {{ insert: param, sc-30.03_odp.02 }}].

Employ realistic, but misleading information in {{ insert: param, sc-30.04_odp }} about its security state or posture.

Employ the following techniques to hide or conceal {{ insert: param, sc-30.05_odp.02 }}: {{ insert: param, sc-30.05_odp.01 }}.

a. Perform a covert channel analysis to identify those aspects of communications within the system that are potential avenues for covert {{ insert: param, sc-31_odp }} channels; and b. Estimate...

Test a subset of the identified covert channels to determine the channels that are exploitable.

Reduce the maximum bandwidth for identified covert {{ insert: param, sc-31.02_odp.01 }} channels to {{ insert: param, sc-31.02_odp.02 }}.

Measure the bandwidth of {{ insert: param, sc-31.03_odp }} in the operational environment of the system.

Partition the system into {{ insert: param, sc-32_odp.01 }} residing in separate {{ insert: param, sc-32_odp.02 }} domains or environments based on {{ insert: param, sc-32_odp.03 }}.

Partition privileged functions into separate physical domains.

For {{ insert: param, sc-34_odp.01 }} , load and execute: a. The operating environment from hardware-enforced, read-only media; and b. The following applications from hardware-enforced, read-on...

Employ {{ insert: param, sc-34.01_odp }} with no writeable storage that is persistent across component restart or power on/off.

Protect the integrity of information prior to storage on read-only media and control the media after such information has been recorded onto the media.

Include system components that proactively seek to identify network-based malicious code or malicious websites.

Distribute the following processing and storage components across multiple {{ insert: param, sc-36_prm_1 }}: {{ insert: param, sc-36_prm_2 }}.

(a) Employ polling techniques to identify potential faults, errors, or compromises to the following processing and storage components: {{ insert: param, sc-36.01_odp.01 }} ; and (b) Take the fo...

Synchronize the following duplicate systems or system components: {{ insert: param, sc-36.02_odp }}.

Employ the following out-of-band channels for the physical delivery or electronic transmission of {{ insert: param, sc-37_odp.02 }} to {{ insert: param, sc-37_odp.03 }}: {{ insert: param, sc-37_odp...

Employ {{ insert: param, sc-37.01_odp.01 }} to ensure that only {{ insert: param, sc-37.01_odp.02 }} receive the following information, system components, or devices: {{ insert: param, sc-37.01_odp...

Employ the following operations security controls to protect key organizational information throughout the system development life cycle: {{ insert: param, sc-38_odp }}.

Maintain a separate execution domain for each executing system process.

Implement hardware separation mechanisms to facilitate process isolation.

Maintain a separate execution domain for each thread in {{ insert: param, sc-39.02_odp }}.

Protect external and internal {{ insert: param, sc-40_prm_1 }} from the following signal parameter attacks: {{ insert: param, sc-40_prm_2 }}.

Implement cryptographic mechanisms that achieve {{ insert: param, sc-40.01_odp }} against the effects of intentional electromagnetic interference.

Implement cryptographic mechanisms to reduce the detection potential of wireless links to {{ insert: param, sc-40.02_odp }}.

Implement cryptographic mechanisms to identify and reject wireless transmissions that are deliberate attempts to achieve imitative or manipulative communications deception based on signal parameters.

Implement cryptographic mechanisms to prevent the identification of {{ insert: param, sc-40.04_odp }} by using the transmitter signal parameters.

{{ insert: param, sc-41_odp.02 }} disable or remove {{ insert: param, sc-41_odp.01 }} on the following systems or system components: {{ insert: param, sc-41_odp.03 }}.

a. Prohibit {{ insert: param, sc-42_odp.01 }} ; and b. Provide an explicit indication of sensor use to {{ insert: param, sc-42_odp.05 }}.

Verify that the system is configured so that data or information collected by the {{ insert: param, sc-42.01_odp }} is only reported to authorized individuals or roles.

Employ the following measures so that data or information collected by {{ insert: param, sc-42.01_odp }} is only used for authorized purposes: {{ insert: param, sc-42.02_odp }}.

Employ the following measures to facilitate an individual’s awareness that personally identifiable information is being collected by {{ insert: param, sc-42.04_odp.02 }}: {{ insert: param, sc-42.04...

Employ {{ insert: param, sc-42.05_odp }} that are configured to minimize the collection of information about individuals that is not needed.

a. Establish usage restrictions and implementation guidelines for the following system components: {{ insert: param, sc-43_odp }} ; and b. Authorize, monitor, and control the use of such compon...

Employ a detonation chamber capability within {{ insert: param, sc-44_odp }}.

Synchronize system clocks within and between systems and system components.

(a) Compare the internal system clocks {{ insert: param, sc-45.01_odp.01 }} with {{ insert: param, sc-45.01_odp.02 }} ; and (b) Synchronize the internal system clocks to the authoritative time ...

(a) Identify a secondary authoritative time source that is in a different geographic region than the primary authoritative time source; and (b) Synchronize the internal system clocks to the sec...

Implement a policy enforcement mechanism {{ insert: param, sc-46_odp }} between the physical and/or network interfaces for the connecting security domains.

Establish {{ insert: param, sc-47_odp }} for system operations organizational command and control.

Relocate {{ insert: param, sc-48_odp.01 }} to {{ insert: param, sc-48_odp.02 }} under the following conditions or circumstances: {{ insert: param, sc-48_odp.03 }}.

Dynamically relocate {{ insert: param, sc-48.01_odp.01 }} to {{ insert: param, sc-48.01_odp.02 }} under the following conditions or circumstances: {{ insert: param, sc-48.01_odp.03 }}.

Implement hardware-enforced separation and policy enforcement mechanisms between {{ insert: param, sc-49_odp }}.

Implement software-enforced separation and policy enforcement mechanisms between {{ insert: param, sc-50_odp }}.

a. Employ hardware-based, write-protect for {{ insert: param, sc-51_odp.01 }} ; and b. Implement specific procedures for {{ insert: param, sc-51_odp.02 }} to manually disable hardware write-pro...