nist-800-53-rev5.yaml

name: NIST-800-53 rev5
AC-1:
  family: AC
  name: Policy and Procedures
  description: |2
     - a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]:
       - 1. [Selection (one or more): organization-level, mission/business process-level, system-level] access control policy that:
         - (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
         - (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
       - 2. Procedures to facilitate the implementation of the access control policy and the associated access controls;
     - b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the access control policy and procedures; and
     - c. Review and update the current access control:
       - 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and
       - 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events].
AC-2:
  family: AC
  name: Account Management
  description: |2
     - a. Define and document the types of accounts allowed and specifically prohibited for use within the system;
     - b. Assign account managers;
     - c. Require [Assignment: organization-defined prerequisites and criteria] for group and role membership;
     - d. Specify:
       - 1. Authorized users of the system;
       - 2. Group and role membership; and
       - 3. Access authorizations (i.e., privileges) and [Assignment: organization-defined attributes (as required)] for each account;
     - e. Require approvals by [Assignment: organization-defined personnel or roles] for requests to create accounts;
     - f. Create, enable, modify, disable, and remove accounts in accordance with [Assignment: organization-defined policy, procedures, prerequisites, and criteria];
     - g. Monitor the use of accounts;
     - h. Notify account managers and [Assignment: organization-defined personnel or roles] within:
       - 1. [Assignment: organization-defined time period] when accounts are no longer required;
       - 2. [Assignment: organization-defined time period] when users are terminated or transferred; and
       - 3. [Assignment: organization-defined time period] when system usage or need-to-know changes for an individual;
     - i. Authorize access to the system based on:
       - 1. A valid access authorization;
       - 2. Intended system usage; and
       - 3. [Assignment: organization-defined attributes (as required)];
     - j. Review accounts for compliance with account management requirements [Assignment: organization-defined frequency];
     - k. Establish and implement a process for changing shared or group account authenticators (if deployed) when individuals are removed from the group; and
     - l. Align account management processes with personnel termination and transfer processes.
AC-2 (1):
  family: AC
  name: Automated System Account Management
  description: |
    Support the management of system accounts using [Assignment: organization-defined automated mechanisms].
AC-2 (2):
  family: AC
  name: Automated Temporary and Emergency Account Management
  description: |
    Automatically [Selection: remove, disable] temporary and emergency accounts after [Assignment: organization-defined time period for each type of account].
AC-2 (3):
  family: AC
  name: Disable Accounts
  description: |
    Disable accounts within [Assignment: organization-defined time period] when the accounts:
     - (a) Have expired;
     - (b) Are no longer associated with a user or individual;
     - (c) Are in violation of organizational policy; or
     - (d) Have been inactive for [Assignment: organization-defined time period].
AC-2 (4):
  family: AC
  name: Automated Audit Actions
  description: |
    Automatically audit account creation, modification, enabling, disabling, and removal actions.
AC-2 (5):
  family: AC
  name: Inactivity Logout
  description: |
    Require that users log out when [Assignment: organization-defined time period of expected inactivity or description of when to log out].
AC-2 (6):
  family: AC
  name: Dynamic Privilege Management
  description: |
    Implement [Assignment: organization-defined dynamic privilege management capabilities].
AC-2 (7):
  family: AC
  name: Privileged User Accounts
  description: |2
     - (a) Establish and administer privileged user accounts in accordance with [Selection: a role-based access scheme, an attribute-based access scheme];
     - (b) Monitor privileged role or attribute assignments;
     - (c) Monitor changes to roles or attributes; and
     - (d) Revoke access when privileged role or attribute assignments are no longer appropriate.
AC-2 (8):
  family: AC
  name: Dynamic Account Management
  description: |
    Create, activate, manage, and deactivate [Assignment: organization-defined system accounts] dynamically.
AC-2 (9):
  family: AC
  name: Restrictions on Use of Shared and Group Accounts
  description: |
    Only permit the use of shared and group accounts that meet [Assignment: organization-defined conditions for establishing shared and group accounts].
AC-2 (10):
  family: AC
  name: Shared and Group Account Credential Change
  description: ""
AC-2 (11):
  family: AC
  name: Usage Conditions
  description: |
    Enforce [Assignment: organization-defined circumstances and/or usage conditions] for  [Assignment: organization-defined system accounts].
AC-2 (12):
  family: AC
  name: Account Monitoring for Atypical Usage
  description: |2
     - (a) Monitor system accounts for [Assignment: organization-defined atypical usage]; and
     - (b) Report atypical usage of system accounts to [Assignment: organization-defined personnel or roles].
AC-2 (13):
  family: AC
  name: Disable Accounts for High-risk Individuals
  description: |
    Disable accounts of individuals within [Assignment: organization-defined time period] of discovery of [Assignment: organization-defined significant risks].
AC-3:
  family: AC
  name: Access Enforcement
  description: |
    Enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.
AC-3 (1):
  family: AC
  name: Restricted Access to Privileged Functions
  description: ""
AC-3 (2):
  family: AC
  name: Dual Authorization
  description: |
    Enforce dual authorization for [Assignment: organization-defined privileged commands and/or other organization-defined actions].
AC-3 (3):
  family: AC
  name: Mandatory Access Control
  description: |
    Enforce [Assignment: organization-defined mandatory access control policy] over the set of covered subjects and objects specified in the policy, and where the policy:
     - (a) Is uniformly enforced across the covered subjects and objects within the system;
     - (b) Specifies that a subject that has been granted access to information is constrained from doing any of the following;
       - (1) Passing the information to unauthorized subjects or objects;
       - (2) Granting its privileges to other subjects;
       - (3) Changing one or more security attributes (specified by the policy) on subjects, objects, the system, or system components;
       - (4) Choosing the security attributes and attribute values (specified by the policy) to be associated with newly created or modified objects; and
       - (5) Changing the rules governing access control; and
     - (c) Specifies that [Assignment: organization-defined subjects] may explicitly be granted [Assignment: organization-defined privileges] such that they are not limited by any defined subset (or all) of the above constraints.
AC-3 (4):
  family: AC
  name: Discretionary Access Control
  description: |
    Enforce [Assignment: organization-defined discretionary access control policy] over the set of covered subjects and objects specified in the policy, and where the policy specifies that a subject that has been granted access to information can do one or more of the following:
     - (a) Pass the information to any other subjects or objects;
     - (b) Grant its privileges to other subjects;
     - (c) Change security attributes on subjects, objects, the system, or the system’s components;
     - (d) Choose the security attributes to be associated with newly created or revised objects; or
     - (e) Change the rules governing access control.
AC-3 (5):
  family: AC
  name: Security-relevant Information
  description: |
    Prevent access to [Assignment: organization-defined security-relevant information] except during secure, non-operable system states.
AC-3 (6):
  family: AC
  name: Protection of User and System Information
  description: ""
AC-3 (7):
  family: AC
  name: Role-based Access Control
  description: |
    Enforce a role-based access control policy over defined subjects and objects and control access based upon [Assignment: organization-defined roles and users authorized to assume such roles].
AC-3 (8):
  family: AC
  name: Revocation of Access Authorizations
  description: |
    Enforce the revocation of access authorizations resulting from changes to the security attributes of subjects and objects based on [Assignment: organization-defined rules governing the timing of revocations of access authorizations].
AC-3 (9):
  family: AC
  name: Controlled Release
  description: |
    Release information outside of the system only if:
     - (a) The receiving [Assignment: organization-defined system or system component] provides [Assignment: organization-defined controls]; and
     - (b) [Assignment: organization-defined controls] are used to validate the appropriateness of the information designated for release.
AC-3 (10):
  family: AC
  name: Audited Override of Access Control Mechanisms
  description: |
    Employ an audited override of automated access control mechanisms under [Assignment: organization-defined conditions] by [Assignment: organization-defined roles].
AC-3 (11):
  family: AC
  name: Restrict Access to Specific Information Types
  description: |
    Restrict access to data repositories containing [Assignment: organization-defined information types].
AC-3 (12):
  family: AC
  name: Assert and Enforce Application Access
  description: |2
     - (a) Require applications to assert, as part of the installation process, the access needed to the following system applications and functions: [Assignment: organization-defined system applications and functions];
     - (b) Provide an enforcement mechanism to prevent unauthorized access; and
     - (c) Approve access changes after initial installation of the application.
AC-3 (13):
  family: AC
  name: Attribute-based Access Control
  description: |
    Enforce attribute-based access control policy over defined subjects and objects and control access based upon [Assignment: organization-defined attributes to assume access permissions].
AC-3 (14):
  family: AC
  name: Individual Access
  description: |
    Provide [Assignment: organization-defined mechanisms] to enable individuals to have access to the following elements of their personally identifiable information: [Assignment: organization-defined elements].
AC-3 (15):
  family: AC
  name: Discretionary and Mandatory Access Control
  description: |2
     - (a) Enforce [Assignment: organization-defined mandatory access control policy] over the set of covered subjects and objects specified in the policy; and
     - (b) Enforce [Assignment: organization-defined discretionary access control policy] over the set of covered subjects and objects specified in the policy.
AC-4:
  family: AC
  name: Information Flow Enforcement
  description: |
    Enforce approved authorizations for controlling the flow of information within the system and between connected systems based on [Assignment: organization-defined information flow control policies].
AC-4 (1):
  family: AC
  name: Object Security and Privacy Attributes
  description: |
    Use [Assignment: organization-defined security and privacy attributes] associated with [Assignment: organization-defined information, source, and destination objects] to enforce [Assignment: organization-defined information flow control policies] as a basis for flow control decisions.
AC-4 (2):
  family: AC
  name: Processing Domains
  description: |
    Use protected processing domains to enforce [Assignment: organization-defined information flow control policies] as a basis for flow control decisions.
AC-4 (3):
  family: AC
  name: Dynamic Information Flow Control
  description: |
    Enforce [Assignment: organization-defined information flow control policies].
AC-4 (4):
  family: AC
  name: Flow Control of Encrypted Information
  description: |
    Prevent encrypted information from bypassing [Assignment: organization-defined information flow control mechanisms] by [Selection (one or more): decrypting the information, blocking the flow of the encrypted information, terminating communications sessions attempting to pass encrypted information, [Assignment: organization-defined procedure or method]].
AC-4 (5):
  family: AC
  name: Embedded Data Types
  description: |
    Enforce [Assignment: organization-defined limitations] on embedding data types within other data types.
AC-4 (6):
  family: AC
  name: Metadata
  description: |
    Enforce information flow control based on [Assignment: organization-defined metadata].
AC-4 (7):
  family: AC
  name: One-way Flow Mechanisms
  description: |
    Enforce one-way information flows through hardware-based flow control mechanisms.
AC-4 (8):
  family: AC
  name: Security and Privacy Policy Filters
  description: |2
     - (a) Enforce information flow control using [Assignment: organization-defined security or privacy policy filters] as a basis for flow control decisions for [Assignment: organization-defined information flows]; and
     - (b) [Selection (one or more): Block, Strip, Modify, Quarantine] data after a filter processing failure in accordance with [Assignment: organization-defined security or privacy policy].
AC-4 (9):
  family: AC
  name: Human Reviews
  description: |
    Enforce the use of human reviews for [Assignment: organization-defined information flows] under the following conditions: [Assignment: organization-defined conditions].
AC-4 (10):
  family: AC
  name: Enable and Disable Security or Privacy Policy Filters
  description: |
    Provide the capability for privileged administrators to enable and disable [Assignment: organization-defined security or privacy policy filters] under the following conditions: [Assignment: organization-defined conditions].
AC-4 (11):
  family: AC
  name: Configuration of Security or Privacy Policy Filters
  description: |
    Provide the capability for privileged administrators to configure [Assignment: organization-defined security or privacy policy filters] to support different security or privacy policies.
AC-4 (12):
  family: AC
  name: Data Type Identifiers
  description: |
    When transferring information between different security domains, use [Assignment: organization-defined data type identifiers] to validate data essential for information flow decisions.
AC-4 (13):
  family: AC
  name: Decomposition into Policy-relevant Subcomponents
  description: |
    When transferring information between different security domains, decompose information into [Assignment: organization-defined policy-relevant subcomponents] for submission to policy enforcement mechanisms.
AC-4 (14):
  family: AC
  name: Security or Privacy Policy Filter Constraints
  description: |
    When transferring information between different security domains, implement [Assignment: organization-defined security or privacy policy filters] requiring fully enumerated formats that restrict data structure and content.
AC-4 (15):
  family: AC
  name: Detection of Unsanctioned Information
  description: |
    When transferring information between different security domains, examine the information for the presence of [Assignment: organization-defined unsanctioned information] and prohibit the transfer of such information in accordance with the [Assignment: organization-defined security or privacy policy].
AC-4 (16):
  family: AC
  name: Information Transfers on Interconnected Systems
  description: ""
AC-4 (17):
  family: AC
  name: Domain Authentication
  description: |
    Uniquely identify and authenticate source and destination points by [Selection (one or more): organization, system, application, service, individual] for information transfer.
AC-4 (18):
  family: AC
  name: Security Attribute Binding
  description: ""
AC-4 (19):
  family: AC
  name: Validation of Metadata
  description: |
    When transferring information between different security domains, implement [Assignment: organization-defined security or privacy policy filters] on metadata.
AC-4 (20):
  family: AC
  name: Approved Solutions
  description: |
    Employ [Assignment: organization-defined solutions in approved configurations] to control the flow of [Assignment: organization-defined information] across security domains.
AC-4 (21):
  family: AC
  name: Physical or Logical Separation of Information Flows
  description: |
    Separate information flows logically or physically using [Assignment: organization-defined mechanisms and/or techniques] to accomplish [Assignment: organization-defined required separations by types of information].
AC-4 (22):
  family: AC
  name: Access Only
  description: |
    Provide access from a single device to computing platforms, applications, or data residing in multiple different security domains, while preventing information flow between the different security domains.
AC-4 (23):
  family: AC
  name: Modify Non-releasable Information
  description: |
    When transferring information between different security domains, modify non-releasable information by implementing [Assignment: organization-defined modification action].
AC-4 (24):
  family: AC
  name: Internal Normalized Format
  description: |
    When transferring information between different security domains, parse incoming data into an internal normalized format and regenerate the data to be consistent with its intended specification.
AC-4 (25):
  family: AC
  name: Data Sanitization
  description: |
    When transferring information between different security domains, sanitize data to minimize [Selection (one or more): delivery of malicious content, command and control of malicious code, malicious code augmentation, and steganography encoded data, spillage of sensitive information] in accordance with [Assignment: organization-defined policy]].
AC-4 (26):
  family: AC
  name: Audit Filtering Actions
  description: |
    When transferring information between different security domains, record and audit content filtering actions and results for the information being filtered.
AC-4 (27):
  family: AC
  name: Redundant/independent Filtering Mechanisms
  description: |
    When transferring information between different security domains, implement content filtering solutions that provide redundant and independent filtering mechanisms for each data type.
AC-4 (28):
  family: AC
  name: Linear Filter Pipelines
  description: |
    When transferring information between different security domains, implement a linear content filter pipeline that is enforced with discretionary and mandatory access controls.
AC-4 (29):
  family: AC
  name: Filter Orchestration Engines
  description: |
    When transferring information between different security domains, employ content filter orchestration engines to ensure that:
     - (a) Content filtering mechanisms successfully complete execution without errors; and
     - (b) Content filtering actions occur in the correct order and comply with [Assignment: organization-defined policy].
AC-4 (30):
  family: AC
  name: Filter Mechanisms Using Multiple Processes
  description: |
    When transferring information between different security domains, implement content filtering mechanisms using multiple processes.
AC-4 (31):
  family: AC
  name: Failed Content Transfer Prevention
  description: |
    When transferring information between different security domains, prevent the transfer of failed content to the receiving domain.
AC-4 (32):
  family: AC
  name: Process Requirements for Information Transfer
  description: |
    When transferring information between different security domains, the process that transfers information between filter pipelines:
     - (a) Does not filter message content;
     - (b) Validates filtering metadata;
     - (c) Ensures the content associated with the filtering metadata has successfully completed filtering; and
     - (d) Transfers the content to the destination filter pipeline.
AC-5:
  family: AC
  name: Separation of Duties
  description: |2
     - a. Identify and document [Assignment: organization-defined duties of individuals requiring separation]; and
     - b. Define system access authorizations to support separation of duties.
AC-6:
  family: AC
  name: Least Privilege
  description: |
    Employ the principle of least privilege, allowing only authorized accesses for users (or processes acting on behalf of users) that are necessary to accomplish assigned organizational tasks.
AC-6 (1):
  family: AC
  name: Authorize Access to Security Functions
  description: |
    Authorize access for [Assignment: organization-defined individuals or roles] to:
     - (a) [Assignment: organization-defined security functions (deployed in hardware, software, and firmware)]; and
     - (b) [Assignment: organization-defined security-relevant information].
AC-6 (2):
  family: AC
  name: Non-privileged Access for Nonsecurity Functions
  description: |
    Require that users of system accounts (or roles) with access to [Assignment: organization-defined security functions or security-relevant information] use non-privileged accounts or roles, when accessing nonsecurity functions.
AC-6 (3):
  family: AC
  name: Network Access to Privileged Commands
  description: |
    Authorize network access to [Assignment: organization-defined privileged commands] only for [Assignment: organization-defined compelling operational needs] and document the rationale for such access in the security plan for the system.
AC-6 (4):
  family: AC
  name: Separate Processing Domains
  description: |
    Provide separate processing domains to enable finer-grained allocation of user privileges.
AC-6 (5):
  family: AC
  name: Privileged Accounts
  description: |
    Restrict privileged accounts on the system to [Assignment: organization-defined personnel or roles].
AC-6 (6):
  family: AC
  name: Privileged Access by Non-organizational Users
  description: |
    Prohibit privileged access to the system by non-organizational users.
AC-6 (7):
  family: AC
  name: Review of User Privileges
  description: |2
     - (a) Review [Assignment: organization-defined frequency] the privileges assigned to [Assignment: organization-defined roles or classes of users] to validate the need for such privileges; and
     - (b) Reassign or remove privileges, if necessary, to correctly reflect organizational mission and business needs.
AC-6 (8):
  family: AC
  name: Privilege Levels for Code Execution
  description: |
    Prevent the following software from executing at higher privilege levels than users executing the software: [Assignment: organization-defined software].
AC-6 (9):
  family: AC
  name: Log Use of Privileged Functions
  description: |
    Log the execution of privileged functions.
AC-6 (10):
  family: AC
  name: Prohibit Non-privileged Users from Executing Privileged Functions
  description: |
    Prevent non-privileged users from executing privileged functions.
AC-7:
  family: AC
  name: Unsuccessful Logon Attempts
  description: |2
     - a. Enforce a limit of [Assignment: organization-defined number] consecutive invalid logon attempts by a user during a [Assignment: organization-defined time period]; and
     - b. Automatically [Selection (one or more): lock the account or node for an [Assignment: organization-defined time period], lock the account or node until released by an administrator, delay next logon prompt per [Assignment: organization-defined delay algorithm], notify system administrator, take other [Assignment: organization-defined action]] when the maximum number of unsuccessful attempts is exceeded.
AC-7 (1):
  family: AC
  name: Automatic Account Lock
  description: ""
AC-7 (2):
  family: AC
  name: Purge or Wipe Mobile Device
  description: |
    Purge or wipe information from [Assignment: organization-defined mobile devices] based on [Assignment: organization-defined purging or wiping requirements and techniques] after [Assignment: organization-defined number] consecutive, unsuccessful device logon attempts.
AC-7 (3):
  family: AC
  name: Biometric Attempt Limiting
  description: |
    Limit the number of unsuccessful biometric logon attempts to [Assignment: organization-defined number].
AC-7 (4):
  family: AC
  name: Use of Alternate Authentication Factor
  description: |2
     - (a) Allow the use of [Assignment: organization-defined authentication factors] that are different from the primary authentication factors after the number of organization-defined consecutive invalid logon attempts have been exceeded; and
     - (b) Enforce a limit of [Assignment: organization-defined number] consecutive invalid logon attempts through use of the alternative factors by a user during a [Assignment: organization-defined time period].
AC-8:
  family: AC
  name: System Use Notification
  description: |2
     - a. Display [Assignment: organization-defined system use notification message or banner] to users before granting access to the system that provides privacy and security notices consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines and state that:
       - 1. Users are accessing a U.S. Government system;
       - 2. System usage may be monitored, recorded, and subject to audit;
       - 3. Unauthorized use of the system is prohibited and subject to criminal and civil penalties; and
       - 4. Use of the system indicates consent to monitoring and recording;
     - b. Retain the notification message or banner on the screen until users acknowledge the usage conditions and take explicit actions to log on to or further access the system; and
     - c. For publicly accessible systems:
       - 1. Display system use information [Assignment: organization-defined conditions], before granting further access to the publicly accessible system;
       - 2. Display references, if any, to monitoring, recording, or auditing that are consistent with privacy accommodations for such systems that generally prohibit those activities; and
       - 3. Include a description of the authorized uses of the system.
AC-9:
  family: AC
  name: Previous Logon Notification
  description: |
    Notify the user, upon successful logon to the system, of the date and time of the last logon.
AC-9 (1):
  family: AC
  name: Unsuccessful Logons
  description: |
    Notify the user, upon successful logon, of the number of unsuccessful logon attempts since the last successful logon.
AC-9 (2):
  family: AC
  name: Successful and Unsuccessful Logons
  description: |
    Notify the user, upon successful logon, of the number of [Selection: successful logons, unsuccessful logon attempts, both] during [Assignment: organization-defined time period].
AC-9 (3):
  family: AC
  name: Notification of Account Changes
  description: |
    Notify the user, upon successful logon, of changes to [Assignment: organization-defined security-related characteristics or parameters of the user’s account] during [Assignment: organization-defined time period].
AC-9 (4):
  family: AC
  name: Additional Logon Information
  description: |
    Notify the user, upon successful logon, of the following additional information: [Assignment: organization-defined additional information].
AC-10:
  family: AC
  name: Concurrent Session Control
  description: |
    Limit the number of concurrent sessions for each [Assignment: organization-defined account and/or account type] to [Assignment: organization-defined number].
AC-11:
  family: AC
  name: Device Lock
  description: |2
     - a. Prevent further access to the system by [Selection (one or more): initiating a device lock after [Assignment: organization-defined time period] of inactivity, requiring the user to initiate a device lock before leaving the system unattended]; and
     - b. Retain the device lock until the user reestablishes access using established identification and authentication procedures.
AC-11 (1):
  family: AC
  name: Pattern-hiding Displays
  description: |
    Conceal, via the device lock, information previously visible on the display with a publicly viewable image.
AC-12:
  family: AC
  name: Session Termination
  description: |
    Automatically terminate a user session after [Assignment: organization-defined conditions, or trigger events requiring session disconnect].
AC-12 (1):
  family: AC
  name: User-initiated Logouts
  description: |
    Provide a logout capability for user-initiated communications sessions whenever authentication is used to gain access to [Assignment: organization-defined information resources].
AC-12 (2):
  family: AC
  name: Termination Message
  description: |
    Display an explicit logout message to users indicating the termination of authenticated communications sessions.
AC-12 (3):
  family: AC
  name: Timeout Warning Message
  description: |
    Display an explicit message to users indicating that the session will end in [Assignment: organization-defined time until end of session].
AC-13:
  family: AC
  name: Supervision and Review — Access Control
  description: ""
AC-14:
  family: AC
  name: Permitted Actions Without Identification or Authentication
  description: |2
     - a. Identify [Assignment: organization-defined user actions] that can be performed on the system without identification or authentication consistent with organizational mission and business functions; and
     - b. Document and provide supporting rationale in the security plan for the system, user actions not requiring identification or authentication.
AC-14 (1):
  family: AC
  name: Necessary Uses
  description: ""
AC-15:
  family: AC
  name: Automated Marking
  description: ""
AC-16:
  family: AC
  name: Security and Privacy Attributes
  description: |2
     - a. Provide the means to associate [Assignment: organization-defined types of security and privacy attributes] with [Assignment: organization-defined security and privacy attribute values] for information in storage, in process, and/or in transmission;
     - b. Ensure that the attribute associations are made and retained with the information;
     - c. Establish the following permitted security and privacy attributes from the attributes defined in AC-16a for [Assignment: organization-defined systems]: [Assignment: organization-defined security and privacy attributes];
     - d. Determine the following permitted attribute values or ranges for each of the established attributes: [Assignment: organization-defined attribute values or ranges for established attributes];
     - e. Audit changes to attributes; and
     - f. Review [Assignment: organization-defined security and privacy attributes] for applicability [Assignment: organization-defined frequency].
AC-16 (1):
  family: AC
  name: Dynamic Attribute Association
  description: |
    Dynamically associate security and privacy attributes with [Assignment: organization-defined subjects and objects] in accordance with the following security and privacy policies as information is created and combined: [Assignment: organization-defined security and privacy policies].
AC-16 (2):
  family: AC
  name: Attribute Value Changes by Authorized Individuals
  description: |
    Provide authorized individuals (or processes acting on behalf of individuals) the capability to define or change the value of associated security and privacy attributes.
AC-16 (3):
  family: AC
  name: Maintenance of Attribute Associations by System
  description: |
    Maintain the association and integrity of [Assignment: organization-defined security and privacy attributes] to [Assignment: organization-defined subjects and objects].
AC-16 (4):
  family: AC
  name: Association of Attributes by Authorized Individuals
  description: |
    Provide the capability to associate [Assignment: organization-defined security and privacy attributes] with [Assignment: organization-defined subjects and objects] by authorized individuals (or processes acting on behalf of individuals).
AC-16 (5):
  family: AC
  name: Attribute Displays on Objects to Be Output
  description: |
    Display security and privacy attributes in human-readable form on each object that the system transmits to output devices to identify [Assignment: organization-defined special dissemination, handling, or distribution instructions] using [Assignment: organization-defined human-readable, standard naming conventions].
AC-16 (6):
  family: AC
  name: Maintenance of Attribute Association
  description: |
    Require personnel to associate and maintain the association of [Assignment: organization-defined security and privacy attributes] with [Assignment: organization-defined subjects and objects] in accordance with [Assignment: organization-defined security and privacy policies].
AC-16 (7):
  family: AC
  name: Consistent Attribute Interpretation
  description: |
    Provide a consistent interpretation of security and privacy attributes transmitted between distributed system components.
AC-16 (8):
  family: AC
  name: Association Techniques and Technologies
  description: |
    Implement [Assignment: organization-defined techniques and technologies] in associating security and privacy attributes to information.
AC-16 (9):
  family: AC
  name: Attribute Reassignment — Regrading Mechanisms
  description: |
    Change security and privacy attributes associated with information only via regrading mechanisms validated using [Assignment: organization-defined techniques or procedures].
AC-16 (10):
  family: AC
  name: Attribute Configuration by Authorized Individuals
  description: |
    Provide authorized individuals the capability to define or change the type and value of security and privacy attributes available for association with subjects and objects.
AC-17:
  family: AC
  name: Remote Access
  description: |2
     - a. Establish and document usage restrictions, configuration/connection requirements, and implementation guidance for each type of remote access allowed; and
     - b. Authorize each type of remote access to the system prior to allowing such connections.
AC-17 (1):
  family: AC
  name: Monitoring and Control
  description: |
    Employ automated mechanisms to monitor and control remote access methods.
AC-17 (2):
  family: AC
  name: Protection of Confidentiality and Integrity Using Encryption
  description: |
    Implement cryptographic mechanisms to protect the confidentiality and integrity of remote access sessions.
AC-17 (3):
  family: AC
  name: Managed Access Control Points
  description: |
    Route remote accesses through authorized and managed network access control points.
AC-17 (4):
  family: AC
  name: Privileged Commands and Access
  description: |2
     - (a) Authorize the execution of privileged commands and access to security-relevant information via remote access only in a format that provides assessable evidence and for the following needs: [Assignment: organization-defined needs]; and
     - (b) Document the rationale for remote access in the security plan for the system.
AC-17 (5):
  family: AC
  name: Monitoring for Unauthorized Connections
  description: ""
AC-17 (6):
  family: AC
  name: Protection of Mechanism Information
  description: |
    Protect information about remote access mechanisms from unauthorized use and disclosure.
AC-17 (7):
  family: AC
  name: Additional Protection for Security Function Access
  description: ""
AC-17 (8):
  family: AC
  name: Disable Nonsecure Network Protocols
  description: ""
AC-17 (9):
  family: AC
  name: Disconnect or Disable Access
  description: |
    Provide the capability to disconnect or disable remote access to the system within [Assignment: organization-defined time period].
AC-17 (10):
  family: AC
  name: Authenticate Remote Commands
  description: |
    Implement [Assignment: organization-defined mechanisms] to authenticate [Assignment: organization-defined remote commands].
AC-18:
  family: AC
  name: Wireless Access
  description: |2
     - a. Establish configuration requirements, connection requirements, and implementation guidance for each type of wireless access; and
     - b. Authorize each type of wireless access to the system prior to allowing such connections.
AC-18 (1):
  family: AC
  name: Authentication and Encryption
  description: |
    Protect wireless access to the system using authentication of [Selection (one or more): users, devices] and encryption.
AC-18 (2):
  family: AC
  name: Monitoring Unauthorized Connections
  description: ""
AC-18 (3):
  family: AC
  name: Disable Wireless Networking
  description: |
    Disable, when not intended for use, wireless networking capabilities embedded within system components prior to issuance and deployment.
AC-18 (4):
  family: AC
  name: Restrict Configurations by Users
  description: |
    Identify and explicitly authorize users allowed to independently configure wireless networking capabilities.
AC-18 (5):
  family: AC
  name: Antennas and Transmission Power Levels
  description: |
    Select radio antennas and calibrate transmission power levels to reduce the probability that signals from wireless access points can be received outside of organization-controlled boundaries.
AC-19:
  family: AC
  name: Access Control for Mobile Devices
  description: |2
     - a. Establish configuration requirements, connection requirements, and implementation guidance for organization-controlled mobile devices, to include when such devices are outside of controlled areas; and
     - b. Authorize the connection of mobile devices to organizational systems.
AC-19 (1):
  family: AC
  name: Use of Writable and Portable Storage Devices
  description: ""
AC-19 (2):
  family: AC
  name: Use of Personally Owned Portable Storage Devices
  description: ""
AC-19 (3):
  family: AC
  name: Use of Portable Storage Devices with No Identifiable Owner
  description: ""
AC-19 (4):
  family: AC
  name: Restrictions for Classified Information
  description: |2
     - (a) Prohibit the use of unclassified mobile devices in facilities containing systems processing, storing, or transmitting classified information unless specifically permitted by the authorizing official; and
     - (b) Enforce the following restrictions on individuals permitted by the authorizing official to use unclassified mobile devices in facilities containing systems processing, storing, or transmitting classified information:
       - (1) Connection of unclassified mobile devices to classified systems is prohibited;
       - (2) Connection of unclassified mobile devices to unclassified systems requires approval from the authorizing official;
       - (3) Use of internal or external modems or wireless interfaces within the unclassified mobile devices is prohibited; and
       - (4) Unclassified mobile devices and the information stored on those devices are subject to random reviews and inspections by [Assignment: organization-defined security officials], and if classified information is found, the incident handling policy is followed.
     - (c) Restrict the connection of classified mobile devices to classified systems in accordance with [Assignment: organization-defined security policies].
AC-19 (5):
  family: AC
  name: Full Device or Container-based Encryption
  description: |
    Employ [Selection: full-device encryption, container-based encryption] to protect the confidentiality and integrity of information on [Assignment: organization-defined mobile devices].
AC-20:
  family: AC
  name: Use of External Systems
  description: |2
     - a. [Selection (one or more): Establish [Assignment: organization-defined terms and conditions], Identify [Assignment: organization-defined controls asserted to be implemented on external systems]], consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems, allowing authorized individuals to:
       - 1. Access the system from external systems; and
       - 2. Process, store, or transmit organization-controlled information using external systems; or
     - b. Prohibit the use of [Assignment: organizationally-defined types of external systems].
AC-20 (1):
  family: AC
  name: Limits on Authorized Use
  description: |
    Permit authorized individuals to use an external system to access the system or to process, store, or transmit organization-controlled information only after:
     - (a) Verification of the implementation of controls on the external system as specified in the organization’s security and privacy policies and security and privacy plans; or
     - (b) Retention of approved system connection or processing agreements with the organizational entity hosting the external system.
AC-20 (2):
  family: AC
  name: Portable Storage Devices — Restricted Use
  description: |
    Restrict the use of organization-controlled portable storage devices by authorized individuals on external systems using [Assignment: organization-defined restrictions].
AC-20 (3):
  family: AC
  name: Non-organizationally Owned Systems  — Restricted Use
  description: |
    Restrict the use of non-organizationally owned systems or system components to process, store, or transmit organizational information using [Assignment: organization-defined restrictions].
AC-20 (4):
  family: AC
  name: Network Accessible Storage Devices — Prohibited Use
  description: |
    Prohibit the use of [Assignment: organization-defined network accessible storage devices] in external systems.
AC-20 (5):
  family: AC
  name: Portable Storage Devices — Prohibited Use
  description: |
    Prohibit the use of organization-controlled portable storage devices by authorized individuals on external systems.
AC-21:
  family: AC
  name: Information Sharing
  description: |2
     - a. Enable authorized users to determine whether access authorizations assigned to a sharing partner match the information’s access and use restrictions for [Assignment: organization-defined information sharing circumstances where user discretion is required]; and
     - b. Employ [Assignment: organization-defined automated mechanisms or manual processes] to assist users in making information sharing and collaboration decisions.
AC-21 (1):
  family: AC
  name: Automated Decision Support
  description: |
    Employ [Assignment: organization-defined automated mechanisms] to enforce information-sharing decisions by authorized users based on access authorizations of sharing partners and access restrictions on information to be shared.
AC-21 (2):
  family: AC
  name: Information Search and Retrieval
  description: |
    Implement information search and retrieval services that enforce [Assignment: organization-defined information sharing restrictions].
AC-22:
  family: AC
  name: Publicly Accessible Content
  description: |2
     - a. Designate individuals authorized to make information publicly accessible;
     - b. Train authorized individuals to ensure that publicly accessible information does not contain nonpublic information;
     - c. Review the proposed content of information prior to posting onto the publicly accessible system to ensure that nonpublic information is not included; and
     - d. Review the content on the publicly accessible system for nonpublic information [Assignment: organization-defined frequency] and remove such information, if discovered.
AC-23:
  family: AC
  name: Data Mining Protection
  description: |
    Employ [Assignment: organization-defined data mining prevention and detection techniques] for [Assignment: organization-defined data storage objects] to detect and protect against unauthorized data mining.
AC-24:
  family: AC
  name: Access Control Decisions
  description: |
    [Selection: Establish procedures, Implement mechanisms] to ensure [Assignment: organization-defined access control decisions] are applied to each access request prior to access enforcement.
AC-24 (1):
  family: AC
  name: Transmit Access Authorization Information
  description: |
    Transmit [Assignment: organization-defined access authorization information] using [Assignment: organization-defined controls] to [Assignment: organization-defined systems] that enforce access control decisions.
AC-24 (2):
  family: AC
  name: No User or Process Identity
  description: |
    Enforce access control decisions based on [Assignment: organization-defined security or privacy attributes] that do not include the identity of the user or process acting on behalf of the user.
AC-25:
  family: AC
  name: Reference Monitor
  description: |
    Implement a reference monitor for [Assignment: organization-defined access control policies] that is tamperproof, always invoked, and small enough to be subject to analysis and testing, the completeness of which can be assured.
AT-1:
  family: AT
  name: Policy and Procedures
  description: |2
     - a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]:
       - 1. [Selection (one or more): organization-level, mission/business process-level, system-level] awareness and training policy that:
         - (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
         - (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
       - 2. Procedures to facilitate the implementation of the awareness and training policy and the associated awareness and training controls;
     - b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the awareness and training policy and procedures; and
     - c. Review and update the current awareness and training:
       - 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and
       - 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events].
AT-2:
  family: AT
  name: Literacy Training and Awareness
  description: |2
     - a. Provide security and privacy literacy training to system users (including managers, senior executives, and contractors):
       - 1. As part of initial training for new users and [Assignment: organization-defined frequency] thereafter; and
       - 2. When required by system changes or following [Assignment: organization-defined events];
     - b. Employ the following techniques to increase the security and privacy awareness of system users [Assignment: organization-defined awareness techniques];
     - c. Update literacy training and awareness content [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and
     - d. Incorporate lessons learned from internal or external security or privacy incidents into literacy training and awareness techniques.
AT-2 (1):
  family: AT
  name: Practical Exercises
  description: |
    Provide practical exercises in literacy training that simulate events and incidents.
AT-2 (2):
  family: AT
  name: Insider Threat
  description: |
    Provide literacy training on recognizing and reporting potential indicators of insider threat.
AT-2 (3):
  family: AT
  name: Social Engineering and Mining
  description: |
    Provide literacy training on recognizing and reporting potential and actual instances of social engineering and social mining.
AT-2 (4):
  family: AT
  name: Suspicious Communications and Anomalous System Behavior
  description: |
    Provide literacy training on recognizing suspicious communications and anomalous behavior in organizational systems using [Assignment: organization-defined indicators of malicious code].
AT-2 (5):
  family: AT
  name: Advanced Persistent Threat
  description: |
    Provide literacy training on the advanced persistent threat.
AT-2 (6):
  family: AT
  name: Cyber Threat Environment
  description: |2
     - (a) Provide literacy training on the cyber threat environment; and
     - (b) Reflect current cyber threat information in system operations.
AT-3:
  family: AT
  name: Role-based Training
  description: |2
     - a. Provide role-based security and privacy training to personnel with the following roles and responsibilities: [Assignment: organization-defined roles and responsibilities]:
       - 1. Before authorizing access to the system, information, or performing assigned duties, and [Assignment: organization-defined frequency] thereafter; and
       - 2. When required by system changes;
     - b. Update role-based training content [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and
     - c. Incorporate lessons learned from internal or external security or privacy incidents into role-based training.
AT-3 (1):
  family: AT
  name: Environmental Controls
  description: |
    Provide [Assignment: organization-defined personnel or roles] with initial and [Assignment: organization-defined frequency] training in the employment and operation of environmental controls.
AT-3 (2):
  family: AT
  name: Physical Security Controls
  description: |
    Provide [Assignment: organization-defined personnel or roles] with initial and [Assignment: organization-defined frequency] training in the employment and operation of physical security controls.
AT-3 (3):
  family: AT
  name: Practical Exercises
  description: |
    Provide practical exercises in security and privacy training that reinforce training objectives.
AT-3 (4):
  family: AT
  name: Suspicious Communications and Anomalous System Behavior
  description: ""
AT-3 (5):
  family: AT
  name: Processing Personally Identifiable Information
  description: |
    Provide [Assignment: organization-defined personnel or roles] with initial and [Assignment: organization-defined frequency] training in the employment and operation of personally identifiable information processing and transparency controls.
AT-4:
  family: AT
  name: Training Records
  description: |2
     - a. Document and monitor information security and privacy training activities, including security and privacy awareness training and specific role-based security and privacy training; and
     - b. Retain individual training records for [Assignment: organization-defined time period].
AT-5:
  family: AT
  name: Contacts with Security Groups and Associations
  description: ""
AT-6:
  family: AT
  name: Training Feedback
  description: |
    Provide feedback on organizational training results to the following personnel [Assignment: organization-defined frequency]: [Assignment: organization-defined personnel].
AU-1:
  family: AU
  name: Policy and Procedures
  description: |2
     - a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]:
       - 1. [Selection (one or more): organization-level, mission/business process-level, system-level] audit and accountability policy that:
         - (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
         - (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
       - 2. Procedures to facilitate the implementation of the audit and accountability policy and the associated audit and accountability controls;
     - b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the audit and accountability policy and procedures; and
     - c. Review and update the current audit and accountability:
       - 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and
       - 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events].
AU-2:
  family: AU
  name: Event Logging
  description: |2
     - a. Identify the types of events that the system is capable of logging in support of the audit function: [Assignment: organization-defined event types that the system is capable of logging];
     - b. Coordinate the event logging function with other organizational entities requiring audit-related information to guide and inform the selection criteria for events to be logged;
     - c. Specify the following event types for logging within the system: [Assignment: organization-defined event types (subset of the event types defined in AU-2a.) along with the frequency of (or situation requiring) logging for each identified event type];
     - d. Provide a rationale for why the event types selected for logging are deemed to be adequate to support after-the-fact investigations of incidents; and
     - e. Review and update the event types selected for logging [Assignment: organization-defined frequency].
AU-2 (1):
  family: AU
  name: Compilation of Audit Records from Multiple Sources
  description: ""
AU-2 (2):
  family: AU
  name: Selection of Audit Events by Component
  description: ""
AU-2 (3):
  family: AU
  name: Reviews and Updates
  description: ""
AU-2 (4):
  family: AU
  name: Privileged Functions
  description: ""
AU-3:
  family: AU
  name: Content of Audit Records
  description: |
    Ensure that audit records contain information that establishes the following:
     - a. What type of event occurred;
     - b. When the event occurred;
     - c. Where the event occurred;
     - d. Source of the event;
     - e. Outcome of the event; and
     - f. Identity of any individuals, subjects, or objects/entities associated with the event.
AU-3 (1):
  family: AU
  name: Additional Audit Information
  description: |
    Generate audit records containing the following additional information: [Assignment: organization-defined additional information].
AU-3 (2):
  family: AU
  name: Centralized Management of Planned Audit Record Content
  description: ""
AU-3 (3):
  family: AU
  name: Limit Personally Identifiable Information Elements
  description: |
    Limit personally identifiable information contained in audit records to the following elements identified in the privacy risk assessment: [Assignment: organization-defined elements].
AU-4:
  family: AU
  name: Audit Log Storage Capacity
  description: |
    Allocate audit log storage capacity to accommodate [Assignment: organization-defined audit log retention requirements].
AU-4 (1):
  family: AU
  name: Transfer to Alternate Storage
  description: |
    Transfer audit logs [Assignment: organization-defined frequency] to a different system, system component, or media other than the system or system component conducting the logging.
AU-5:
  family: AU
  name: Response to Audit Logging Process Failures
  description: |2
     - a. Alert [Assignment: organization-defined personnel or roles] within [Assignment: organization-defined time period] in the event of an audit logging process failure; and
     - b. Take the following additional actions: [Assignment: organization-defined additional actions].
AU-5 (1):
  family: AU
  name: Storage Capacity Warning
  description: |
    Provide a warning to [Assignment: organization-defined personnel, roles, and/or locations] within [Assignment: organization-defined time period] when allocated audit log storage volume reaches [Assignment: organization-defined percentage] of repository maximum audit log storage capacity.
AU-5 (2):
  family: AU
  name: Real-time Alerts
  description: |
    Provide an alert within [Assignment: organization-defined real-time period] to [Assignment: organization-defined personnel, roles, and/or locations] when the following audit failure events occur: [Assignment: organization-defined audit logging failure events requiring real-time alerts].
AU-5 (3):
  family: AU
  name: Configurable Traffic Volume Thresholds
  description: |
    Enforce configurable network communications traffic volume thresholds reflecting limits on audit log storage capacity and [Selection: reject, delay] network traffic above those thresholds.
AU-5 (4):
  family: AU
  name: Shutdown on Failure
  description: |
    Invoke a [Selection: full system shutdown, partial system shutdown, degraded operational mode with limited mission or business functionality available] in the event of [Assignment: organization-defined audit logging failures], unless an alternate audit logging capability exists.
AU-5 (5):
  family: AU
  name: Alternate Audit Logging Capability
  description: |
    Provide an alternate audit logging capability in the event of a failure in primary audit logging capability that implements [Assignment: organization-defined alternate audit logging functionality].
AU-6:
  family: AU
  name: Audit Record Review, Analysis, and Reporting
  description: |2
     - a. Review and analyze system audit records [Assignment: organization-defined frequency] for indications of [Assignment: organization-defined inappropriate or unusual activity] and the potential impact of the inappropriate or unusual activity;
     - b. Report findings to [Assignment: organization-defined personnel or roles]; and
     - c. Adjust the level of audit record review, analysis, and reporting within the system when there is a change in risk based on law enforcement information, intelligence information, or other credible sources of information.
AU-6 (1):
  family: AU
  name: Automated Process Integration
  description: |
    Integrate audit record review, analysis, and reporting processes using [Assignment: organization-defined automated mechanisms].
AU-6 (2):
  family: AU
  name: Automated Security Alerts
  description: ""
AU-6 (3):
  family: AU
  name: Correlate Audit Record Repositories
  description: |
    Analyze and correlate audit records across different repositories to gain organization-wide situational awareness.
AU-6 (4):
  family: AU
  name: Central Review and Analysis
  description: |
    Provide and implement the capability to centrally review and analyze audit records from multiple components within the system.
AU-6 (5):
  family: AU
  name: Integrated Analysis of Audit Records
  description: |
    Integrate analysis of audit records with analysis of [Selection (one or more): vulnerability scanning information, performance data, system monitoring information, [Assignment: organization-defined data/information collected from other sources]] to further enhance the ability to identify inappropriate or unusual activity.
AU-6 (6):
  family: AU
  name: Correlation with Physical Monitoring
  description: |
    Correlate information from audit records with information obtained from monitoring physical access to further enhance the ability to identify suspicious, inappropriate, unusual, or malevolent activity.
AU-6 (7):
  family: AU
  name: Permitted Actions
  description: |
    Specify the permitted actions for each [Selection (one or more): system process, role, user] associated with the review, analysis, and reporting of audit record information.
AU-6 (8):
  family: AU
  name: Full Text Analysis of Privileged Commands
  description: |
    Perform a full text analysis of logged privileged commands in a physically distinct component or subsystem of the system, or other system that is dedicated to that analysis.
AU-6 (9):
  family: AU
  name: Correlation with Information from Nontechnical Sources
  description: |
    Correlate information from nontechnical sources with audit record information to enhance organization-wide situational awareness.
AU-6 (10):
  family: AU
  name: Audit Level Adjustment
  description: ""
AU-7:
  family: AU
  name: Audit Record Reduction and Report Generation
  description: |
    Provide and implement an audit record reduction and report generation capability that:
     - a. Supports on-demand audit record review, analysis, and reporting requirements and after-the-fact investigations of incidents; and
     - b. Does not alter the original content or time ordering of audit records.
AU-7 (1):
  family: AU
  name: Automatic Processing
  description: |
    Provide and implement the capability to process, sort, and search audit records for events of interest based on the following content: [Assignment: organization-defined fields within audit records].
AU-7 (2):
  family: AU
  name: Automatic Sort and Search
  description: ""
AU-8:
  family: AU
  name: Time Stamps
  description: |2
     - a. Use internal system clocks to generate time stamps for audit records; and
     - b. Record time stamps for audit records that meet [Assignment: organization-defined granularity of time measurement] and that use Coordinated Universal Time, have a fixed local time offset from Coordinated Universal Time, or that include the local time offset as part of the time stamp.
AU-8 (1):
  family: AU
  name: Synchronization with Authoritative Time Source
  description: ""
AU-8 (2):
  family: AU
  name: Secondary Authoritative Time Source
  description: ""
AU-9:
  family: AU
  name: Protection of Audit Information
  description: |2
     - a. Protect audit information and audit logging tools from unauthorized access, modification, and deletion; and
     - b. Alert [Assignment: organization-defined personnel or roles] upon detection of unauthorized access, modification, or deletion of audit information.
AU-9 (1):
  family: AU
  name: Hardware Write-once Media
  description: |
    Write audit trails to hardware-enforced, write-once media.
AU-9 (2):
  family: AU
  name: Store on Separate Physical Systems or Components
  description: |
    Store audit records [Assignment: organization-defined frequency] in a repository that is part of a physically different system or system component than the system or component being audited.
AU-9 (3):
  family: AU
  name: Cryptographic Protection
  description: |
    Implement cryptographic mechanisms to protect the integrity of audit information and audit tools.
AU-9 (4):
  family: AU
  name: Access by Subset of Privileged Users
  description: |
    Authorize access to management of audit logging functionality to only [Assignment: organization-defined subset of privileged users or roles].
AU-9 (5):
  family: AU
  name: Dual Authorization
  description: |
    Enforce dual authorization for [Selection (one or more): movement, deletion] of [Assignment: organization-defined audit information].
AU-9 (6):
  family: AU
  name: Read-only Access
  description: |
    Authorize read-only access to audit information to [Assignment: organization-defined subset of privileged users or roles].
AU-9 (7):
  family: AU
  name: Store on Component with Different Operating System
  description: |
    Store audit information on a component running a different operating system than the system or component being audited.
AU-10:
  family: AU
  name: Non-repudiation
  description: |
    Provide irrefutable evidence that an individual (or process acting on behalf of an individual) has performed [Assignment: organization-defined actions to be covered by non-repudiation].
AU-10 (1):
  family: AU
  name: Association of Identities
  description: |2
     - (a) Bind the identity of the information producer with the information to [Assignment: organization-defined strength of binding]; and
     - (b) Provide the means for authorized individuals to determine the identity of the producer of the information.
AU-10 (2):
  family: AU
  name: Validate Binding of Information Producer Identity
  description: |2
     - (a) Validate the binding of the information producer identity to the information at [Assignment: organization-defined frequency]; and
     - (b) Perform [Assignment: organization-defined actions] in the event of a validation error.
AU-10 (3):
  family: AU
  name: Chain of Custody
  description: |
    Maintain reviewer or releaser credentials within the established chain of custody for information reviewed or released.
AU-10 (4):
  family: AU
  name: Validate Binding of Information Reviewer Identity
  description: |2
     - (a) Validate the binding of the information reviewer identity to the information at the transfer or release points prior to release or transfer between [Assignment: organization-defined security domains]; and
     - (b) Perform [Assignment: organization-defined actions] in the event of a validation error.
AU-10 (5):
  family: AU
  name: Digital Signatures
  description: ""
AU-11:
  family: AU
  name: Audit Record Retention
  description: |
    Retain audit records for [Assignment: organization-defined time period consistent with records retention policy] to provide support for after-the-fact investigations of incidents and to meet regulatory and organizational information retention requirements.
AU-11 (1):
  family: AU
  name: Long-term Retrieval Capability
  description: |
    Employ [Assignment: organization-defined measures] to ensure that long-term audit records generated by the system can be retrieved.
AU-12:
  family: AU
  name: Audit Record Generation
  description: |2
     - a. Provide audit record generation capability for the event types the system is capable of auditing as defined in AU-2a on [Assignment: organization-defined system components];
     - b. Allow [Assignment: organization-defined personnel or roles] to select the event types that are to be logged by specific components of the system; and
     - c. Generate audit records for the event types defined in AU-2c that include the audit record content defined in AU-3.
AU-12 (1):
  family: AU
  name: System-wide and Time-correlated Audit Trail
  description: |
    Compile audit records from [Assignment: organization-defined system components] into a system-wide (logical or physical) audit trail that is time-correlated to within [Assignment: organization-defined level of tolerance for the relationship between time stamps of individual records in the audit trail].
AU-12 (2):
  family: AU
  name: Standardized Formats
  description: |
    Produce a system-wide (logical or physical) audit trail composed of audit records in a standardized format.
AU-12 (3):
  family: AU
  name: Changes by Authorized Individuals
  description: |
    Provide and implement the capability for [Assignment: organization-defined individuals or roles] to change the logging to be performed on [Assignment: organization-defined system components] based on [Assignment: organization-defined selectable event criteria] within [Assignment: organization-defined time thresholds].
AU-12 (4):
  family: AU
  name: Query Parameter Audits of Personally Identifiable Information
  description: |
    Provide and implement the capability for auditing the parameters of user query events for data sets containing personally identifiable information.
AU-13:
  family: AU
  name: Monitoring for Information Disclosure
  description: |2
     - a. Monitor [Assignment: organization-defined open-source information and/or information sites]
                      [Assignment: organization-defined frequency] for evidence of unauthorized disclosure of organizational information; and
     - b. If an information disclosure is discovered:
       - 1. Notify [Assignment: organization-defined personnel or roles]; and
       - 2. Take the following additional actions: [Assignment: organization-defined additional actions].
AU-13 (1):
  family: AU
  name: Use of Automated Tools
  description: |
    Monitor open-source information and information sites using [Assignment: organization-defined automated mechanisms].
AU-13 (2):
  family: AU
  name: Review of Monitored Sites
  description: |
    Review the list of open-source information sites being monitored [Assignment: organization-defined frequency].
AU-13 (3):
  family: AU
  name: Unauthorized Replication of Information
  description: |
    Employ discovery techniques, processes, and tools to determine if external entities are replicating organizational information in an unauthorized manner.
AU-14:
  family: AU
  name: Session Audit
  description: |2
     - a. Provide and implement the capability for [Assignment: organization-defined users or roles] to [Selection (one or more): record, view, hear, log] the content of a user session under [Assignment: organization-defined circumstances]; and
     - b. Develop, integrate, and use session auditing activities in consultation with legal counsel and in accordance with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines.
AU-14 (1):
  family: AU
  name: System Start-up
  description: |
    Initiate session audits automatically at system start-up.
AU-14 (2):
  family: AU
  name: Capture and Record Content
  description: ""
AU-14 (3):
  family: AU
  name: Remote Viewing and Listening
  description: |
    Provide and implement the capability for authorized users to remotely view and hear content related to an established user session in real time.
AU-15:
  family: AU
  name: Alternate Audit Logging Capability
  description: ""
AU-16:
  family: AU
  name: Cross-organizational Audit Logging
  description: |
    Employ [Assignment: organization-defined methods] for coordinating [Assignment: organization-defined audit information] among external organizations when audit information is transmitted across organizational boundaries.
AU-16 (1):
  family: AU
  name: Identity Preservation
  description: |
    Preserve the identity of individuals in cross-organizational audit trails.
AU-16 (2):
  family: AU
  name: Sharing of Audit Information
  description: |
    Provide cross-organizational audit information to [Assignment: organization-defined organizations] based on [Assignment: organization-defined cross-organizational sharing agreements].
AU-16 (3):
  family: AU
  name: Disassociability
  description: |
    Implement [Assignment: organization-defined measures] to disassociate individuals from audit information transmitted across organizational boundaries.
CA-1:
  family: CA
  name: Policy and Procedures
  description: |2
     - a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]:
       - 1. [Selection (one or more): organization-level, mission/business process-level, system-level] assessment, authorization, and monitoring policy that:
         - (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
         - (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
       - 2. Procedures to facilitate the implementation of the assessment, authorization, and monitoring policy and the associated assessment, authorization, and monitoring controls;
     - b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the assessment, authorization, and monitoring policy and procedures; and
     - c. Review and update the current assessment, authorization, and monitoring:
       - 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and
       - 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events].
CA-2:
  family: CA
  name: Control Assessments
  description: |2
     - a. Select the appropriate assessor or assessment team for the type of assessment to be conducted;
     - b. Develop a control assessment plan that describes the scope of the assessment including:
       - 1. Controls and control enhancements under assessment;
       - 2. Assessment procedures to be used to determine control effectiveness; and
       - 3. Assessment environment, assessment team, and assessment roles and responsibilities;
     - c. Ensure the control assessment plan is reviewed and approved by the authorizing official or designated representative prior to conducting the assessment;
     - d. Assess the controls in the system and its environment of operation [Assignment: organization-defined frequency] to determine the extent to which the controls are implemented correctly, operating as intended, and producing the desired outcome with respect to meeting established security and privacy requirements;
     - e. Produce a control assessment report that document the results of the assessment; and
     - f. Provide the results of the control assessment to [Assignment: organization-defined individuals or roles].
CA-2 (1):
  family: CA
  name: Independent Assessors
  description: |
    Employ independent assessors or assessment teams to conduct control assessments.
CA-2 (2):
  family: CA
  name: Specialized Assessments
  description: |
    Include as part of control assessments, [Assignment: organization-defined frequency], [Selection: announced, unannounced], [Selection (one or more): in-depth monitoring, security instrumentation, automated security test cases, vulnerability scanning, malicious user testing, insider threat assessment, performance and load testing, data leakage or data loss assessment [Assignment: organization-defined other forms of assessment]].
CA-2 (3):
  family: CA
  name: Leveraging Results from External Organizations
  description: |
    Leverage the results of control assessments performed by [Assignment: organization-defined external organization] on [Assignment: organization-defined system] when the assessment meets [Assignment: organization-defined requirements].
CA-3:
  family: CA
  name: Information Exchange
  description: |2
     - a. Approve and manage the exchange of information between the system and other systems using [Selection (one or more): interconnection security agreements, information exchange security agreements, memoranda of understanding or agreement, service level agreements, user agreements, nondisclosure agreements, [Assignment: organization-defined type of agreement]];
     - b. Document, as part of each exchange agreement, the interface characteristics, security and privacy requirements, controls, and responsibilities for each system, and the impact level of the information communicated; and
     - c. Review and update the agreements [Assignment: organization-defined frequency].
CA-3 (1):
  family: CA
  name: Unclassified National Security System Connections
  description: ""
CA-3 (2):
  family: CA
  name: Classified National Security System Connections
  description: ""
CA-3 (3):
  family: CA
  name: Unclassified Non-national Security System Connections
  description: ""
CA-3 (4):
  family: CA
  name: Connections to Public Networks
  description: ""
CA-3 (5):
  family: CA
  name: Restrictions on External System Connections
  description: ""
CA-3 (6):
  family: CA
  name: Transfer Authorizations
  description: |
    Verify that individuals or systems transferring data between interconnecting systems have the requisite authorizations (i.e., write permissions or privileges) prior to accepting such data.
CA-3 (7):
  family: CA
  name: Transitive Information Exchanges
  description: |2
     - (a) Identify transitive (downstream) information exchanges with other systems through the systems identified in CA-3a; and
     - (b) Take measures to ensure that transitive (downstream) information exchanges cease when the controls on identified transitive (downstream) systems cannot be verified or validated.
CA-4:
  family: CA
  name: Security Certification
  description: ""
CA-5:
  family: CA
  name: Plan of Action and Milestones
  description: |2
     - a. Develop a plan of action and milestones for the system to document the planned remediation actions of the organization to correct weaknesses or deficiencies noted during the assessment of the controls and to reduce or eliminate known vulnerabilities in the system; and
     - b. Update existing plan of action and milestones [Assignment: organization-defined frequency] based on the findings from control assessments, independent audits or reviews, and continuous monitoring activities.
CA-5 (1):
  family: CA
  name: Automation Support for Accuracy and Currency
  description: |
    Ensure the accuracy, currency, and availability of the plan of action and milestones for the system using [Assignment: organization-defined automated mechanisms].
CA-6:
  family: CA
  name: Authorization
  description: |2
     - a. Assign a senior official as the authorizing official for the system;
     - b. Assign a senior official as the authorizing official for common controls available for inheritance by organizational systems;
     - c. Ensure that the authorizing official for the system, before commencing operations:
       - 1. Accepts the use of common controls inherited by the system; and
       - 2. Authorizes the system to operate;
     - d. Ensure that the authorizing official for common controls authorizes the use of those controls for inheritance by organizational systems;
     - e. Update the authorizations [Assignment: organization-defined frequency].
CA-6 (1):
  family: CA
  name: Joint Authorization — Intra-organization
  description: |
    Employ a joint authorization process for the system that includes multiple authorizing officials from the same organization conducting the authorization.
CA-6 (2):
  family: CA
  name: Joint Authorization — Inter-organization
  description: |
    Employ a joint authorization process for the system that includes multiple authorizing officials with at least one authorizing official from an organization external to the organization conducting the authorization.
CA-7:
  family: CA
  name: Continuous Monitoring
  description: |
    Develop a system-level continuous monitoring strategy and implement continuous monitoring in accordance with the organization-level continuous monitoring strategy that includes:
     - a. Establishing the following system-level metrics to be monitored: [Assignment: organization-defined system-level metrics];
     - b. Establishing [Assignment: organization-defined frequencies] for monitoring and [Assignment: organization-defined frequencies] for assessment of control effectiveness;
     - c. Ongoing control assessments in accordance with the continuous monitoring strategy;
     - d. Ongoing monitoring of system and organization-defined metrics in accordance with the continuous monitoring strategy;
     - e. Correlation and analysis of information generated by control assessments and monitoring;
     - f. Response actions to address results of the analysis of control assessment and monitoring information; and
     - g. Reporting the security and privacy status of the system to [Assignment: organization-defined personnel or roles]
                      [Assignment: organization-defined frequency].
CA-7 (1):
  family: CA
  name: Independent Assessment
  description: |
    Employ independent assessors or assessment teams to monitor the controls in the system on an ongoing basis.
CA-7 (2):
  family: CA
  name: Types of Assessments
  description: ""
CA-7 (3):
  family: CA
  name: Trend Analyses
  description: |
    Employ trend analyses to determine if control implementations, the frequency of continuous monitoring activities, and the types of activities used in the continuous monitoring process need to be modified based on empirical data.
CA-7 (4):
  family: CA
  name: Risk Monitoring
  description: |
    Ensure risk monitoring is an integral part of the continuous monitoring strategy that includes the following:
     - (a) Effectiveness monitoring;
     - (b) Compliance monitoring; and
     - (c) Change monitoring.
CA-7 (5):
  family: CA
  name: Consistency Analysis
  description: |
    Employ the following actions to validate that policies are established and implemented controls are operating in a consistent manner: [Assignment: organization-defined actions].
CA-7 (6):
  family: CA
  name: Automation Support for Monitoring
  description: |
    Ensure the accuracy, currency, and availability of monitoring results for the system using [Assignment: organization-defined automated mechanisms].
CA-8:
  family: CA
  name: Penetration Testing
  description: |
    Conduct penetration testing [Assignment: organization-defined frequency] on [Assignment: organization-defined systems or system components].
CA-8 (1):
  family: CA
  name: Independent Penetration Testing Agent or Team
  description: |
    Employ an independent penetration testing agent or team to perform penetration testing on the system or system components.
CA-8 (2):
  family: CA
  name: Red Team Exercises
  description: |
    Employ the following red-team exercises to simulate attempts by adversaries to compromise organizational systems in accordance with applicable rules of engagement: [Assignment: organization-defined red team exercises].
CA-8 (3):
  family: CA
  name: Facility Penetration Testing
  description: |
    Employ a penetration testing process that includes [Assignment: organization-defined frequency]
                      [Selection: announced, unannounced] attempts to bypass or circumvent controls associated with physical access points to the facility.
CA-9:
  family: CA
  name: Internal System Connections
  description: |2
     - a. Authorize internal connections of [Assignment: organization-defined system components or classes of components] to the system;
     - b. Document, for each internal connection, the interface characteristics, security and privacy requirements, and the nature of the information communicated;
     - c. Terminate internal system connections after [Assignment: organization-defined conditions]; and
     - d. Review [Assignment: organization-defined frequency] the continued need for each internal connection.
CA-9 (1):
  family: CA
  name: Compliance Checks
  description: |
    Perform security and privacy compliance checks on constituent system components prior to the establishment of the internal connection.
CM-1:
  family: CM
  name: Policy and Procedures
  description: |2
     - a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]:
       - 1. [Selection (one or more): organization-level, mission/business process-level, system-level] configuration management policy that:
         - (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
         - (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
       - 2. Procedures to facilitate the implementation of the configuration management policy and the associated configuration management controls;
     - b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the configuration management policy and procedures; and
     - c. Review and update the current configuration management:
       - 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and
       - 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events].
CM-2:
  family: CM
  name: Baseline Configuration
  description: |2
     - a. Develop, document, and maintain under configuration control, a current baseline configuration of the system; and
     - b. Review and update the baseline configuration of the system:
       - 1. [Assignment: organization-defined frequency];
       - 2. When required due to [Assignment: Assignment organization-defined circumstances]; and
       - 3. When system components are installed or upgraded.
CM-2 (1):
  family: CM
  name: Reviews and Updates
  description: ""
CM-2 (2):
  family: CM
  name: Automation Support for Accuracy and Currency
  description: |
    Maintain the currency, completeness, accuracy, and availability of the baseline configuration of the system using [Assignment: organization-defined automated mechanisms].
CM-2 (3):
  family: CM
  name: Retention of Previous Configurations
  description: |
    Retain [Assignment: organization-defined number] of previous versions of baseline configurations of the system to support rollback.
CM-2 (4):
  family: CM
  name: Unauthorized Software
  description: ""
CM-2 (5):
  family: CM
  name: Authorized Software
  description: ""
CM-2 (6):
  family: CM
  name: Development and Test Environments
  description: |
    Maintain a baseline configuration for system development and test environments that is managed separately from the operational baseline configuration.
CM-2 (7):
  family: CM
  name: Configure Systems and Components for High-risk Areas
  description: |2
     - (a) Issue [Assignment: organization-defined systems or system components] with [Assignment: organization-defined configurations] to individuals traveling to locations that the organization deems to be of significant risk; and
     - (b) Apply the following controls to the systems or components when the individuals return from travel: [Assignment: organization-defined controls].
CM-3:
  family: CM
  name: Configuration Change Control
  description: |2
     - a. Determine and document the types of changes to the system that are configuration-controlled;
     - b. Review proposed configuration-controlled changes to the system and approve or disapprove such changes with explicit consideration for security and privacy impact analyses;
     - c. Document configuration change decisions associated with the system;
     - d. Implement approved configuration-controlled changes to the system;
     - e. Retain records of configuration-controlled changes to the system for [Assignment: organization-defined time period];
     - f. Monitor and review activities associated with configuration-controlled changes to the system; and
     - g. Coordinate and provide oversight for configuration change control activities through [Assignment: organization-defined configuration change control element] that convenes [Selection (one or more): [Assignment: organization-defined frequency], when [Assignment: organization-defined configuration change conditions]].
CM-3 (1):
  family: CM
  name: Automated Documentation, Notification, and Prohibition of Changes
  description: |
    Use [Assignment: organization-defined automated mechanisms] to:
     - (a) Document proposed changes to the system;
     - (b) Notify [Assignment: organization-defined approval authorities] of proposed changes to the system and request change approval;
     - (c) Highlight proposed changes to the system that have not been approved or disapproved within [Assignment: organization-defined time period];
     - (d) Prohibit changes to the system until designated approvals are received;
     - (e) Document all changes to the system; and
     - (f) Notify [Assignment: organization-defined personnel] when approved changes to the system are completed.
CM-3 (2):
  family: CM
  name: Testing, Validation, and Documentation of Changes
  description: |
    Test, validate, and document changes to the system before finalizing the implementation of the changes.
CM-3 (3):
  family: CM
  name: Automated Change Implementation
  description: |
    Implement changes to the current system baseline and deploy the updated baseline across the installed base using [Assignment: organization-defined automated mechanisms].
CM-3 (4):
  family: CM
  name: Security and Privacy Representatives
  description: |
    Require [Assignment: organization-defined security and privacy representatives] to be members of the [Assignment: organization-defined configuration change control element].
CM-3 (5):
  family: CM
  name: Automated Security Response
  description: |
    Implement the following security responses automatically if baseline configurations are changed in an unauthorized manner: [Assignment: organization-defined security responses].
CM-3 (6):
  family: CM
  name: Cryptography Management
  description: |
    Ensure that cryptographic mechanisms used to provide the following controls are under configuration management: [Assignment: organization-defined controls].
CM-3 (7):
  family: CM
  name: Review System Changes
  description: |
    Review changes to the system [Assignment: organization-defined frequency] or when [Assignment: organization-defined circumstances] to determine whether unauthorized changes have occurred.
CM-3 (8):
  family: CM
  name: Prevent or Restrict Configuration Changes
  description: |
    Prevent or restrict changes to the configuration of the system under the following circumstances: [Assignment: organization-defined circumstances].
CM-4:
  family: CM
  name: Impact Analyses
  description: |
    Analyze changes to the system to determine potential security and privacy impacts prior to change implementation.
CM-4 (1):
  family: CM
  name: Separate Test Environments
  description: |
    Analyze changes to the system in a separate test environment before implementation in an operational environment, looking for security and privacy impacts due to flaws, weaknesses, incompatibility, or intentional malice.
CM-4 (2):
  family: CM
  name: Verification of Controls
  description: |
    After system changes, verify that the impacted controls are implemented correctly, operating as intended, and producing the desired outcome with regard to meeting the security and privacy requirements for the system.
CM-5:
  family: CM
  name: Access Restrictions for Change
  description: |
    Define, document, approve, and enforce physical and logical access restrictions associated with changes to the system.
CM-5 (1):
  family: CM
  name: Automated Access Enforcement and Audit Records
  description: |2
     - (a) Enforce access restrictions using [Assignment: organization-defined automated mechanisms]; and
     - (b) Automatically generate audit records of the enforcement actions.
CM-5 (2):
  family: CM
  name: Review System Changes
  description: ""
CM-5 (3):
  family: CM
  name: Signed Components
  description: ""
CM-5 (4):
  family: CM
  name: Dual Authorization
  description: |
    Enforce dual authorization for implementing changes to [Assignment: organization-defined system components and system-level information].
CM-5 (5):
  family: CM
  name: Privilege Limitation for Production and Operation
  description: |2
     - (a) Limit privileges to change system components and system-related information within a production or operational environment; and
     - (b) Review and reevaluate privileges [Assignment: organization-defined frequency].
CM-5 (6):
  family: CM
  name: Limit Library Privileges
  description: |
    Limit privileges to change software resident within software libraries.
CM-5 (7):
  family: CM
  name: Automatic Implementation of Security Safeguards
  description: ""
CM-6:
  family: CM
  name: Configuration Settings
  description: |2
     - a. Establish and document configuration settings for components employed within the system that reflect the most restrictive mode consistent with operational requirements using [Assignment: organization-defined common secure configurations];
     - b. Implement the configuration settings;
     - c. Identify, document, and approve any deviations from established configuration settings for [Assignment: organization-defined system components] based on [Assignment: organization-defined operational requirements]; and
     - d. Monitor and control changes to the configuration settings in accordance with organizational policies and procedures.
CM-6 (1):
  family: CM
  name: Automated Management, Application, and Verification
  description: |
    Manage, apply, and verify configuration settings for [Assignment: organization-defined system components] using [Assignment: organization-defined automated mechanisms].
CM-6 (2):
  family: CM
  name: Respond to Unauthorized Changes
  description: |
    Take the following actions in response to unauthorized changes to [Assignment: organization-defined configuration settings]: [Assignment: organization-defined actions].
CM-6 (3):
  family: CM
  name: Unauthorized Change Detection
  description: ""
CM-6 (4):
  family: CM
  name: Conformance Demonstration
  description: ""
CM-7:
  family: CM
  name: Least Functionality
  description: |2
     - a. Configure the system to provide only [Assignment: organization-defined mission essential capabilities]; and
     - b. Prohibit or restrict the use of the following functions, ports, protocols, software, and/or services: [Assignment: organization-defined prohibited or restricted functions, system ports, protocols, software, and/or services].
CM-7 (1):
  family: CM
  name: Periodic Review
  description: |2
     - (a) Review the system [Assignment: organization-defined frequency] to identify unnecessary and/or nonsecure functions, ports, protocols, software, and services; and
     - (b) Disable or remove [Assignment: organization-defined functions, ports, protocols, software, and services within the system deemed to be unnecessary and/or nonsecure].
CM-7 (2):
  family: CM
  name: Prevent Program Execution
  description: |
    Prevent program execution in accordance with [Selection (one or more): [Assignment: organization-defined policies, rules of behavior, and/or access agreements regarding software program usage and restrictions], rules authorizing the terms and conditions of software program usage].
CM-7 (3):
  family: CM
  name: Registration Compliance
  description: |
    Ensure compliance with [Assignment: organization-defined registration requirements for functions, ports, protocols, and services].
CM-7 (4):
  family: CM
  name: Unauthorized Software
  description: |2
     - (a) Identify [Assignment: organization-defined software programs not authorized to execute on the system];
     - (b) Employ an allow-all, deny-by-exception policy to prohibit the execution of unauthorized software programs on the system; and
     - (c) Review and update the list of unauthorized software programs [Assignment: organization-defined frequency].
CM-7 (5):
  family: CM
  name: Authorized Software
  description: |2
     - (a) Identify [Assignment: organization-defined software programs authorized to execute on the system];
     - (b) Employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs on the system; and
     - (c) Review and update the list of authorized software programs [Assignment: organization-defined frequency].
CM-7 (6):
  family: CM
  name: Confined Environments with Limited Privileges
  description: |
    Require that the following user-installed software execute in a confined physical or virtual machine environment with limited privileges: [Assignment: organization-defined user-installed software].
CM-7 (7):
  family: CM
  name: Code Execution in Protected Environments
  description: |
    Allow execution of binary or machine-executable code only in confined physical or virtual machine environments and with the explicit approval of [Assignment: organization-defined personnel or roles] when such code is:
     - (a) Obtained from sources with limited or no warranty; and/or
     - (b) Without the provision of source code.
CM-7 (8):
  family: CM
  name: Binary or Machine Executable Code
  description: |2
     - (a) Prohibit the use of binary or machine-executable code from sources with limited or no warranty or without the provision of source code; and
     - (b) Allow exceptions only for compelling mission or operational requirements and with the approval of the authorizing official.
CM-7 (9):
  family: CM
  name: Prohibiting The Use of Unauthorized Hardware
  description: |2
     - (a) Identify [Assignment: organization-defined hardware components authorized for system use];
     - (b) Prohibit the use or connection of unauthorized hardware components;
     - (c) Review and update the list of authorized hardware components [Assignment: organization-defined frequency].
CM-8:
  family: CM
  name: System Component Inventory
  description: |2
     - a. Develop and document an inventory of system components that:
       - 1. Accurately reflects the system;
       - 2. Includes all components within the system;
       - 3. Does not include duplicate accounting of components or components assigned to any other system;
       - 4. Is at the level of granularity deemed necessary for tracking and reporting; and
       - 5. Includes the following information to achieve system component accountability: [Assignment: organization-defined information deemed necessary to achieve effective system component accountability]; and
     - b. Review and update the system component inventory [Assignment: organization-defined frequency].
CM-8 (1):
  family: CM
  name: Updates During Installation and Removal
  description: |
    Update the inventory of system components as part of component installations, removals, and system updates.
CM-8 (2):
  family: CM
  name: Automated Maintenance
  description: |
    Maintain the currency, completeness, accuracy, and availability of the inventory of system components using [Assignment: organization-defined automated mechanisms].
CM-8 (3):
  family: CM
  name: Automated Unauthorized Component Detection
  description: |2
     - (a) Detect the presence of unauthorized hardware, software, and firmware components within the system using [Assignment: organization-defined automated mechanisms]
                         [Assignment: organization-defined frequency]; and
     - (b) Take the following actions when unauthorized components are detected: [Selection (one or more): disable network access by such components, isolate the components, notify [Assignment: organization-defined personnel or roles]].
CM-8 (4):
  family: CM
  name: Accountability Information
  description: |
    Include in the system component inventory information, a means for identifying by [Selection (one or more): name, position, role], individuals responsible and accountable for administering those components.
CM-8 (5):
  family: CM
  name: No Duplicate Accounting of Components
  description: ""
CM-8 (6):
  family: CM
  name: Assessed Configurations and Approved Deviations
  description: |
    Include assessed component configurations and any approved deviations to current deployed configurations in the system component inventory.
CM-8 (7):
  family: CM
  name: Centralized Repository
  description: |
    Provide a centralized repository for the inventory of system components.
CM-8 (8):
  family: CM
  name: Automated Location Tracking
  description: |
    Support the tracking of system components by geographic location using [Assignment: organization-defined automated mechanisms].
CM-8 (9):
  family: CM
  name: Assignment of Components to Systems
  description: |2
     - (a) Assign system components to a system; and
     - (b) Receive an acknowledgement from [Assignment: organization-defined personnel or roles] of this assignment.
CM-9:
  family: CM
  name: Configuration Management Plan
  description: |
    Develop, document, and implement a configuration management plan for the system that:
     - a. Addresses roles, responsibilities, and configuration management processes and procedures;
     - b. Establishes a process for identifying configuration items throughout the system development life cycle and for managing the configuration of the configuration items;
     - c. Defines the configuration items for the system and places the configuration items under configuration management;
     - d. Is reviewed and approved by [Assignment: organization-defined personnel or roles]; and
     - e. Protects the configuration management plan from unauthorized disclosure and modification.
CM-9 (1):
  family: CM
  name: Assignment of Responsibility
  description: |
    Assign responsibility for developing the configuration management process to organizational personnel that are not directly involved in system development.
CM-10:
  family: CM
  name: Software Usage Restrictions
  description: |2
     - a. Use software and associated documentation in accordance with contract agreements and copyright laws;
     - b. Track the use of software and associated documentation protected by quantity licenses to control copying and distribution; and
     - c. Control and document the use of peer-to-peer file sharing technology to ensure that this capability is not used for the unauthorized distribution, display, performance, or reproduction of copyrighted work.
CM-10 (1):
  family: CM
  name: Open-source Software
  description: |
    Establish the following restrictions on the use of open-source software: [Assignment: organization-defined restrictions].
CM-11:
  family: CM
  name: User-installed Software
  description: |2
     - a. Establish [Assignment: organization-defined policies] governing the installation of software by users;
     - b. Enforce software installation policies through the following methods: [Assignment: organization-defined methods]; and
     - c. Monitor policy compliance [Assignment: organization-defined frequency].
CM-11 (1):
  family: CM
  name: Alerts for Unauthorized Installations
  description: ""
CM-11 (2):
  family: CM
  name: Software Installation with Privileged Status
  description: |
    Allow user installation of software only with explicit privileged status.
CM-11 (3):
  family: CM
  name: Automated Enforcement and Monitoring
  description: |
    Enforce and monitor compliance with software installation policies using [Assignment: organization-defined automated mechanisms].
CM-12:
  family: CM
  name: Information Location
  description: |2
     - a. Identify and document the location of [Assignment: organization-defined information] and the specific system components on which the information is processed and stored;
     - b. Identify and document the users who have access to the system and system components where the information is processed and stored; and
     - c. Document changes to the location (i.e., system or system components) where the information is processed and stored.
CM-12 (1):
  family: CM
  name: Automated Tools to Support Information Location
  description: |
    Use automated tools to identify [Assignment: organization-defined information by information type] on [Assignment: organization-defined system components] to ensure controls are in place to protect organizational information and individual privacy.
CM-13:
  family: CM
  name: Data Action Mapping
  description: |
    Develop and document a map of system data actions.
CM-14:
  family: CM
  name: Signed Components
  description: |
    Prevent the installation of [Assignment: organization-defined software and firmware components] without verification that the component has been digitally signed using a certificate that is recognized and approved by the organization.
CP-1:
  family: CP
  name: Policy and Procedures
  description: |2
     - a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]:
       - 1. [Selection (one or more): organization-level, mission/business process-level, system-level] contingency planning policy that:
         - (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
         - (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
       - 2. Procedures to facilitate the implementation of the contingency planning policy and the associated contingency planning controls;
     - b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the contingency planning policy and procedures; and
     - c. Review and update the current contingency planning:
       - 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and
       - 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events].
CP-2:
  family: CP
  name: Contingency Plan
  description: |2
     - a. Develop a contingency plan for the system that:
       - 1. Identifies essential mission and business functions and associated contingency requirements;
       - 2. Provides recovery objectives, restoration priorities, and metrics;
       - 3. Addresses contingency roles, responsibilities, assigned individuals with contact information;
       - 4. Addresses maintaining essential mission and business functions despite a system disruption, compromise, or failure;
       - 5. Addresses eventual, full system restoration without deterioration of the controls originally planned and implemented;
       - 6. Addresses the sharing of contingency information; and
       - 7. Is reviewed and approved by [Assignment: organization-defined personnel or roles];
     - b. Distribute copies of the contingency plan to [Assignment: organization-defined key contingency personnel (identified by name and/or by role) and organizational elements];
     - c. Coordinate contingency planning activities with incident handling activities;
     - d. Review the contingency plan for the system [Assignment: organization-defined frequency];
     - e. Update the contingency plan to address changes to the organization, system, or environment of operation and problems encountered during contingency plan implementation, execution, or testing;
     - f. Communicate contingency plan changes to [Assignment: organization-defined key contingency personnel (identified by name and/or by role) and organizational elements];
     - g. Incorporate lessons learned from contingency plan testing, training, or actual contingency activities into contingency testing and training; and
     - h. Protect the contingency plan from unauthorized disclosure and modification.
CP-2 (1):
  family: CP
  name: Coordinate with Related Plans
  description: |
    Coordinate contingency plan development with organizational elements responsible for related plans.
CP-2 (2):
  family: CP
  name: Capacity Planning
  description: |
    Conduct capacity planning so that necessary capacity for information processing, telecommunications, and environmental support exists during contingency operations.
CP-2 (3):
  family: CP
  name: Resume Mission and Business Functions
  description: |
    Plan for the resumption of [Selection: all, essential] mission and business functions within [Assignment: organization-defined time period] of contingency plan activation.
CP-2 (4):
  family: CP
  name: Resume All Mission and Business Functions
  description: ""
CP-2 (5):
  family: CP
  name: Continue Mission and Business Functions
  description: |
    Plan for the continuance of [Selection: all, essential] mission and business functions with minimal or no loss of operational continuity and sustains that continuity until full system restoration at primary processing and/or storage sites.
CP-2 (6):
  family: CP
  name: Alternate Processing and Storage Sites
  description: |
    Plan for the transfer of [Selection: all, essential] mission and business functions to alternate processing and/or storage sites with minimal or no loss of operational continuity and sustain that continuity through system restoration to primary processing and/or storage sites.
CP-2 (7):
  family: CP
  name: Coordinate with External Service Providers
  description: |
    Coordinate the contingency plan with the contingency plans of external service providers to ensure that contingency requirements can be satisfied.
CP-2 (8):
  family: CP
  name: Identify Critical Assets
  description: |
    Identify critical system assets supporting [Selection: all, essential] mission and business functions.
CP-3:
  family: CP
  name: Contingency Training
  description: |2
     - a. Provide contingency training to system users consistent with assigned roles and responsibilities:
       - 1. Within [Assignment: organization-defined time period] of assuming a contingency role or responsibility;
       - 2. When required by system changes; and
       - 3. [Assignment: organization-defined frequency] thereafter; and
     - b. Review and update contingency training content [Assignment: organization-defined frequency] and following [Assignment: organization-defined events].
CP-3 (1):
  family: CP
  name: Simulated Events
  description: |
    Incorporate simulated events into contingency training to facilitate effective response by personnel in crisis situations.
CP-3 (2):
  family: CP
  name: Mechanisms Used in Training Environments
  description: |
    Employ mechanisms used in operations to provide a more thorough and realistic contingency training environment.
CP-4:
  family: CP
  name: Contingency Plan Testing
  description: |2
     - a. Test the contingency plan for the system [Assignment: organization-defined frequency] using  the following tests to determine the effectiveness of the plan and the readiness to execute the plan: [Assignment: organization-defined tests].
     - b. Review the contingency plan test results; and
     - c. Initiate corrective actions, if needed.
CP-4 (1):
  family: CP
  name: Coordinate with Related Plans
  description: |
    Coordinate contingency plan testing with organizational elements responsible for related plans.
CP-4 (2):
  family: CP
  name: Alternate Processing Site
  description: |
    Test the contingency plan at the alternate processing site:
     - (a) To familiarize contingency personnel with the facility and available resources; and
     - (b) To evaluate the capabilities of the alternate processing site to support contingency operations.
CP-4 (3):
  family: CP
  name: Automated Testing
  description: |
    Test the contingency plan using [Assignment: organization-defined automated mechanisms].
CP-4 (4):
  family: CP
  name: Full Recovery and Reconstitution
  description: |
    Include a full recovery and reconstitution of the system to a known state as part of contingency plan testing.
CP-4 (5):
  family: CP
  name: Self-challenge
  description: |
    Employ [Assignment: organization-defined mechanisms] to [Assignment: organization-defined system or system component] to disrupt and adversely affect the system or system component.
CP-5:
  family: CP
  name: Contingency Plan Update
  description: ""
CP-6:
  family: CP
  name: Alternate Storage Site
  description: |2
     - a. Establish an alternate storage site, including necessary agreements to permit the storage and retrieval of system backup information; and
     - b. Ensure that the alternate storage site provides controls equivalent to that of the primary site.
CP-6 (1):
  family: CP
  name: Separation from Primary Site
  description: |
    Identify an alternate storage site that is sufficiently separated from the primary storage site to reduce susceptibility to the same threats.
CP-6 (2):
  family: CP
  name: Recovery Time and Recovery Point Objectives
  description: |
    Configure the alternate storage site to facilitate recovery operations in accordance with recovery time and recovery point objectives.
CP-6 (3):
  family: CP
  name: Accessibility
  description: |
    Identify potential accessibility problems to the alternate storage site in the event of an area-wide disruption or disaster and outline explicit mitigation actions.
CP-7:
  family: CP
  name: Alternate Processing Site
  description: |2
     - a. Establish an alternate processing site, including necessary agreements to permit the transfer and resumption of [Assignment: organization-defined system operations] for essential mission and business functions within [Assignment: organization-defined time period consistent with recovery time and recovery point objectives] when the primary processing capabilities are unavailable;
     - b. Make available at the alternate processing site, the equipment and supplies required to transfer and resume operations or put contracts in place to support delivery to the site within the organization-defined time period for transfer and resumption; and
     - c. Provide controls at the alternate processing site that are equivalent to those at the primary site.
CP-7 (1):
  family: CP
  name: Separation from Primary Site
  description: |
    Identify an alternate processing site that is sufficiently separated from the primary processing site to reduce susceptibility to the same threats.
CP-7 (2):
  family: CP
  name: Accessibility
  description: |
    Identify potential accessibility problems to alternate processing sites in the event of an area-wide disruption or disaster and outlines explicit mitigation actions.
CP-7 (3):
  family: CP
  name: Priority of Service
  description: |
    Develop alternate processing site agreements that contain priority-of-service provisions in accordance with availability requirements (including recovery time objectives).
CP-7 (4):
  family: CP
  name: Preparation for Use
  description: |
    Prepare the alternate processing site so that the site can serve as the operational site supporting essential mission and business functions.
CP-7 (5):
  family: CP
  name: Equivalent Information Security Safeguards
  description: ""
CP-7 (6):
  family: CP
  name: Inability to Return to Primary Site
  description: |
    Plan and prepare for circumstances that preclude returning to the primary processing site.
CP-8:
  family: CP
  name: Telecommunications Services
  description: |
    Establish alternate telecommunications services, including necessary agreements to permit the resumption of [Assignment: organization-defined system operations] for essential mission and business functions within [Assignment: organization-defined time period] when the primary telecommunications capabilities are unavailable at either the primary or alternate processing or storage sites.
CP-8 (1):
  family: CP
  name: Priority of Service Provisions
  description: |2
     - (a) Develop primary and alternate telecommunications service agreements that contain priority-of-service provisions in accordance with availability requirements (including recovery time objectives); and
     - (b) Request Telecommunications Service Priority for all telecommunications services used for national security emergency preparedness if the primary and/or alternate telecommunications services are provided by a common carrier.
CP-8 (2):
  family: CP
  name: Single Points of Failure
  description: |
    Obtain alternate telecommunications services to reduce the likelihood of sharing a single point of failure with primary telecommunications services.
CP-8 (3):
  family: CP
  name: Separation of Primary and Alternate Providers
  description: |
    Obtain alternate telecommunications services from providers that are separated from primary service providers to reduce susceptibility to the same threats.
CP-8 (4):
  family: CP
  name: Provider Contingency Plan
  description: |2
     - (a) Require primary and alternate telecommunications service providers to have contingency plans;
     - (b) Review provider contingency plans to ensure that the plans meet organizational contingency requirements; and
     - (c) Obtain evidence of contingency testing and training by providers [Assignment: organization-defined frequency].
CP-8 (5):
  family: CP
  name: Alternate Telecommunication Service Testing
  description: |
    Test alternate telecommunication services [Assignment: organization-defined frequency].
CP-9:
  family: CP
  name: System Backup
  description: |2
     - a. Conduct backups of user-level information contained in [Assignment: organization-defined system components]
                      [Assignment: organization-defined frequency consistent with recovery time and recovery point objectives];
     - b. Conduct backups of system-level information contained in the system [Assignment: organization-defined frequency consistent with recovery time and recovery point objectives];
     - c. Conduct backups of system documentation, including security- and privacy-related documentation [Assignment: organization-defined frequency consistent with recovery time and recovery point objectives]; and
     - d. Protect the confidentiality, integrity, and availability of backup information.
CP-9 (1):
  family: CP
  name: Testing for Reliability and Integrity
  description: |
    Test backup information [Assignment: organization-defined frequency] to verify media reliability and information integrity.
CP-9 (2):
  family: CP
  name: Test Restoration Using Sampling
  description: |
    Use a sample of backup information in the restoration of selected system functions as part of contingency plan testing.
CP-9 (3):
  family: CP
  name: Separate Storage for Critical Information
  description: |
    Store backup copies of [Assignment: organization-defined critical system software and other security-related information] in a separate facility or in a fire rated container that is not collocated with the operational system.
CP-9 (4):
  family: CP
  name: Protection from Unauthorized Modification
  description: ""
CP-9 (5):
  family: CP
  name: Transfer to Alternate Storage Site
  description: |
    Transfer system backup information to the alternate storage site [Assignment: organization-defined time period and transfer rate consistent with the recovery time and recovery point objectives].
CP-9 (6):
  family: CP
  name: Redundant Secondary System
  description: |
    Conduct system backup by maintaining a redundant secondary system that is not collocated with the primary system and that can be activated without loss of information or disruption to operations.
CP-9 (7):
  family: CP
  name: Dual Authorization
  description: |
    Enforce dual authorization for the deletion or destruction of [Assignment: organization-defined backup information].
CP-9 (8):
  family: CP
  name: Cryptographic Protection
  description: |
    Implement cryptographic mechanisms to prevent unauthorized disclosure and modification of [Assignment: organization-defined backup information].
CP-10:
  family: CP
  name: System Recovery and Reconstitution
  description: |
    Provide for the recovery and reconstitution of the system to a known state within [Assignment: organization-defined time period consistent with recovery time and recovery point objectives] after a disruption, compromise, or failure.
CP-10 (1):
  family: CP
  name: Contingency Plan Testing
  description: ""
CP-10 (2):
  family: CP
  name: Transaction Recovery
  description: |
    Implement transaction recovery for systems that are transaction-based.
CP-10 (3):
  family: CP
  name: Compensating Security Controls
  description: |
    <em>Addressed through tailoring procedures.</em>
CP-10 (4):
  family: CP
  name: Restore Within Time Period
  description: |
    Provide the capability to restore system components within [Assignment: organization-defined restoration time periods] from configuration-controlled and integrity-protected information representing a known, operational state for the components.
CP-10 (5):
  family: CP
  name: Failover Capability
  description: ""
CP-10 (6):
  family: CP
  name: Component Protection
  description: |
    Protect system components used for recovery and reconstitution.
CP-11:
  family: CP
  name: Alternate Communications Protocols
  description: |
    Provide the capability to employ [Assignment: organization-defined alternative communications protocols] in support of maintaining continuity of operations.
CP-12:
  family: CP
  name: Safe Mode
  description: |
    When [Assignment: organization-defined conditions] are detected, enter a safe mode of operation with [Assignment: organization-defined restrictions of safe mode of operation].
CP-13:
  family: CP
  name: Alternative Security Mechanisms
  description: |
    Employ [Assignment: organization-defined alternative or supplemental security mechanisms] for satisfying [Assignment: organization-defined security functions] when the primary means of implementing the security function is unavailable or compromised.
IA-1:
  family: IA
  name: Policy and Procedures
  description: |2
     - a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]:
       - 1. [Selection (one or more): organization-level, mission/business process-level, system-level] identification and authentication policy that:
         - (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
         - (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
       - 2. Procedures to facilitate the implementation of the identification and authentication policy and the associated identification and authentication controls;
     - b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the identification and authentication policy and procedures; and
     - c. Review and update the current identification and authentication:
       - 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and
       - 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events].
IA-2:
  family: IA
  name: Identification and Authentication (organizational Users)
  description: |
    Uniquely identify and authenticate organizational users and associate that unique identification with processes acting on behalf of those users.
IA-2 (1):
  family: IA
  name: Multi-factor Authentication to Privileged Accounts
  description: |
    Implement multi-factor authentication for access to privileged accounts.
IA-2 (2):
  family: IA
  name: Multi-factor Authentication to Non-privileged Accounts
  description: |
    Implement multi-factor authentication for access to non-privileged accounts.
IA-2 (3):
  family: IA
  name: Local Access to Privileged Accounts
  description: ""
IA-2 (4):
  family: IA
  name: Local Access to Non-privileged Accounts
  description: ""
IA-2 (5):
  family: IA
  name: Individual Authentication with Group Authentication
  description: |
    When shared accounts or authenticators are employed, require users to be individually authenticated before granting access to the shared accounts or resources.
IA-2 (6):
  family: IA
  name: Access to Accounts — Separate Device
  description: |
    Implement multi-factor authentication for [Selection (one or more): local, network, remote] access to [Selection (one or more): privileged accounts, non-privileged accounts] such that:
     - (a) One of the factors is provided by a device separate from the system gaining access; and
     - (b) The device meets [Assignment: organization-defined strength of mechanism requirements].
IA-2 (7):
  family: IA
  name: Access to Non-privileged Accounts — Separate Device
  description: ""
IA-2 (8):
  family: IA
  name: Access to Accounts — Replay Resistant
  description: |
    Implement replay-resistant authentication mechanisms for access to [Selection (one or more): privileged accounts, non-privileged accounts].
IA-2 (9):
  family: IA
  name: Network Access to Non-privileged Accounts — Replay Resistant
  description: ""
IA-2 (10):
  family: IA
  name: Single Sign-on
  description: |
    Provide a single sign-on capability for [Assignment: organization-defined system accounts and services].
IA-2 (11):
  family: IA
  name: Remote Access — Separate Device
  description: ""
IA-2 (12):
  family: IA
  name: Acceptance of PIV Credentials
  description: |
    Accept and electronically verify Personal Identity Verification-compliant credentials.
IA-2 (13):
  family: IA
  name: Out-of-band Authentication
  description: |
    Implement the following out-of-band authentication mechanisms under [Assignment: organization-defined conditions]: [Assignment: organization-defined out-of-band authentication].
IA-3:
  family: IA
  name: Device Identification and Authentication
  description: |
    Uniquely identify and authenticate [Assignment: organization-defined devices and/or types of devices] before establishing a [Selection (one or more): local, remote, network] connection.
IA-3 (1):
  family: IA
  name: Cryptographic Bidirectional Authentication
  description: |
    Authenticate [Assignment: organization-defined devices and/or types of devices] before establishing [Selection (one or more): local, remote, network] connection using bidirectional authentication that is cryptographically based.
IA-3 (2):
  family: IA
  name: Cryptographic Bidirectional Network Authentication
  description: ""
IA-3 (3):
  family: IA
  name: Dynamic Address Allocation
  description: |2
     - (a) Where addresses are allocated dynamically, standardize dynamic address allocation lease information and the lease duration assigned to devices in accordance with [Assignment: organization-defined lease information and lease duration]; and
     - (b) Audit lease information when assigned to a device.
IA-3 (4):
  family: IA
  name: Device Attestation
  description: |
    Handle device identification and authentication based on attestation by [Assignment: organization-defined configuration management process].
IA-4:
  family: IA
  name: Identifier Management
  description: |
    Manage system identifiers by:
     - a. Receiving authorization from [Assignment: organization-defined personnel or roles] to assign an individual, group, role, service, or device identifier;
     - b. Selecting an identifier that identifies an individual, group, role, service, or device;
     - c. Assigning the identifier to the intended individual, group, role, service, or device; and
     - d. Preventing reuse of identifiers for [Assignment: organization-defined time period].
IA-4 (1):
  family: IA
  name: Prohibit Account Identifiers as Public Identifiers
  description: |
    Prohibit the use of system account identifiers that are the same as public identifiers for individual accounts.
IA-4 (2):
  family: IA
  name: Supervisor Authorization
  description: ""
IA-4 (3):
  family: IA
  name: Multiple Forms of Certification
  description: ""
IA-4 (4):
  family: IA
  name: Identify User Status
  description: |
    Manage individual identifiers by uniquely identifying each individual as [Assignment: organization-defined characteristic identifying individual status].
IA-4 (5):
  family: IA
  name: Dynamic Management
  description: |
    Manage individual identifiers dynamically in accordance with [Assignment: organization-defined dynamic identifier policy].
IA-4 (6):
  family: IA
  name: Cross-organization Management
  description: |
    Coordinate with the following external organizations for cross-organization management of identifiers: [Assignment: organization-defined external organizations].
IA-4 (7):
  family: IA
  name: In-person Registration
  description: ""
IA-4 (8):
  family: IA
  name: Pairwise Pseudonymous Identifiers
  description: |
    Generate pairwise pseudonymous identifiers.
IA-4 (9):
  family: IA
  name: Attribute Maintenance and Protection
  description: |
    Maintain the attributes for each uniquely identified individual, device, or service in [Assignment: organization-defined protected central storage].
IA-5:
  family: IA
  name: Authenticator Management
  description: |
    Manage system authenticators by:
     - a. Verifying, as part of the initial authenticator distribution, the identity of the individual, group, role, service, or device receiving the authenticator;
     - b. Establishing initial authenticator content for any authenticators issued by the organization;
     - c. Ensuring that authenticators have sufficient strength of mechanism for their intended use;
     - d. Establishing and implementing administrative procedures for initial authenticator distribution, for lost or compromised or damaged authenticators, and for revoking authenticators;
     - e. Changing default authenticators prior to first use;
     - f. Changing or refreshing authenticators [Assignment: organization-defined time period by authenticator type] or when [Assignment: organization-defined events] occur;
     - g. Protecting authenticator content from unauthorized disclosure and modification;
     - h. Requiring individuals to take, and having devices implement, specific controls to protect authenticators; and
     - i. Changing authenticators for group or role accounts when membership to those accounts changes.
IA-5 (1):
  family: IA
  name: Password-based Authentication
  description: |
    For password-based authentication:
     - (a) Maintain a list of commonly-used, expected, or compromised passwords and update the list [Assignment: organization-defined frequency] and when organizational passwords are suspected to have been compromised directly or indirectly;
     - (b) Verify, when users create or update passwords, that the passwords are not found on the list of commonly-used, expected, or compromised passwords in IA-5(1)(a);
     - (c) Transmit passwords only over cryptographically-protected channels;
     - (d) Store passwords using an approved salted key derivation function, preferably using a keyed hash;
     - (e) Require immediate selection of a new password upon account recovery;
     - (f) Allow user selection of long passwords and passphrases, including spaces and all printable characters;
     - (g) Employ automated tools to assist the user in selecting strong password authenticators; and
     - (h) Enforce the following composition and complexity rules: [Assignment: organization-defined composition and complexity rules].
IA-5 (2):
  family: IA
  name: Public Key-based Authentication
  description: |2
     - (a) For public key-based authentication:
       - (1) Enforce authorized access to the corresponding private key; and
       - (2) Map the authenticated identity to the account of the individual or group; and
     - (b) When public key infrastructure (PKI) is used:
       - (1) Validate certificates by constructing and verifying a certification path to an accepted trust anchor, including checking certificate status information; and
       - (2) Implement a local cache of revocation data to support path discovery and validation.
IA-5 (3):
  family: IA
  name: In-person or Trusted External Party Registration
  description: ""
IA-5 (4):
  family: IA
  name: Automated Support for Password Strength Determination
  description: ""
IA-5 (5):
  family: IA
  name: Change Authenticators Prior to Delivery
  description: |
    Require developers and installers of system components to provide unique authenticators or change default authenticators prior to delivery and installation.
IA-5 (6):
  family: IA
  name: Protection of Authenticators
  description: |
    Protect authenticators commensurate with the security category of the information to which use of the authenticator permits access.
IA-5 (7):
  family: IA
  name: No Embedded Unencrypted Static Authenticators
  description: |
    Ensure that unencrypted static authenticators are not embedded in applications or other forms of static storage.
IA-5 (8):
  family: IA
  name: Multiple System Accounts
  description: |
    Implement [Assignment: organization-defined security controls] to manage the risk of compromise due to individuals having accounts on multiple systems.
IA-5 (9):
  family: IA
  name: Federated Credential Management
  description: |
    Use the following external organizations to federate credentials: [Assignment: organization-defined external organizations].
IA-5 (10):
  family: IA
  name: Dynamic Credential Binding
  description: |
    Bind identities and authenticators dynamically using the following rules: [Assignment: organization-defined binding rules].
IA-5 (11):
  family: IA
  name: Hardware Token-based Authentication
  description: ""
IA-5 (12):
  family: IA
  name: Biometric Authentication Performance
  description: |
    For biometric-based authentication, employ mechanisms that satisfy the following biometric quality requirements [Assignment: organization-defined biometric quality requirements].
IA-5 (13):
  family: IA
  name: Expiration of Cached Authenticators
  description: |
    Prohibit the use of cached authenticators after [Assignment: organization-defined time period].
IA-5 (14):
  family: IA
  name: Managing Content of PKI Trust Stores
  description: |
    For PKI-based authentication, employ an organization-wide methodology for managing the content of PKI trust stores installed across all platforms, including networks, operating systems, browsers, and applications.
IA-5 (15):
  family: IA
  name: Gsa-approved Products and Services
  description: |
    Use only General Services Administration-approved products and services for identity, credential, and access management.
IA-5 (16):
  family: IA
  name: In-person or Trusted External Party Authenticator Issuance
  description: |
    Require that the issuance of [Assignment: organization-defined types of and/or specific authenticators] be conducted [Selection: in person, by a trusted external party] before [Assignment: organization-defined registration authority] with authorization by [Assignment: organization-defined personnel or roles].
IA-5 (17):
  family: IA
  name: Presentation Attack Detection for Biometric Authenticators
  description: |
    Employ presentation attack detection mechanisms for biometric-based authentication.
IA-5 (18):
  family: IA
  name: Password Managers
  description: |2
     - (a) Employ [Assignment: organization-defined password managers] to generate and manage passwords; and
     - (b) Protect the passwords using [Assignment: organization-defined controls].
IA-6:
  family: IA
  name: Authentication Feedback
  description: |
    Obscure feedback of authentication information during the authentication process to protect the information from possible exploitation and use by unauthorized individuals.
IA-7:
  family: IA
  name: Cryptographic Module Authentication
  description: |
    Implement mechanisms for authentication to a cryptographic module that meet the requirements of applicable laws, executive orders, directives, policies, regulations, standards, and guidelines for such authentication.
IA-8:
  family: IA
  name: Identification and Authentication (non-organizational Users)
  description: |
    Uniquely identify and authenticate non-organizational users or processes acting on behalf of non-organizational users.
IA-8 (1):
  family: IA
  name: Acceptance of PIV Credentials from Other Agencies
  description: |
    Accept and electronically verify Personal Identity Verification-compliant credentials from other federal agencies.
IA-8 (2):
  family: IA
  name: Acceptance of External Authenticators
  description: |2
     - (a) Accept only external authenticators that are NIST-compliant; and
     - (b) Document and maintain a list of accepted external authenticators.
IA-8 (3):
  family: IA
  name: Use of Ficam-approved Products
  description: ""
IA-8 (4):
  family: IA
  name: Use of Defined Profiles
  description: |
    Conform to the following profiles for identity management [Assignment: organization-defined identity management profiles].
IA-8 (5):
  family: IA
  name: Acceptance of PIV-I Credentials
  description: |
    Accept and verify federated or PKI credentials that meet [Assignment: organization-defined policy].
IA-8 (6):
  family: IA
  name: Disassociability
  description: |
    Implement the following measures to disassociate user attributes or identifier assertion relationships among individuals, credential service providers, and relying parties: [Assignment: organization-defined measures].
IA-9:
  family: IA
  name: Service Identification and Authentication
  description: |
    Uniquely identify and authenticate [Assignment: organization-defined system services and applications] before establishing communications with devices, users, or other services or applications.
IA-9 (1):
  family: IA
  name: Information Exchange
  description: ""
IA-9 (2):
  family: IA
  name: Transmission of Decisions
  description: ""
IA-10:
  family: IA
  name: Adaptive Authentication
  description: |
    Require individuals accessing the system to employ [Assignment: organization-defined supplemental authentication techniques or mechanisms] under specific [Assignment: organization-defined circumstances or situations].
IA-11:
  family: IA
  name: Re-authentication
  description: |
    Require users to re-authenticate when [Assignment: organization-defined circumstances or situations requiring re-authentication].
IA-12:
  family: IA
  name: Identity Proofing
  description: |2
     - a. Identity proof users that require accounts for logical access to systems based on appropriate identity assurance level requirements as specified in applicable standards and guidelines;
     - b. Resolve user identities to a unique individual; and
     - c. Collect, validate, and verify identity evidence.
IA-12 (1):
  family: IA
  name: Supervisor Authorization
  description: |
    Require that the registration process to receive an account for logical access includes supervisor or sponsor authorization.
IA-12 (2):
  family: IA
  name: Identity Evidence
  description: |
    Require evidence of individual identification be presented to the registration authority.
IA-12 (3):
  family: IA
  name: Identity Evidence Validation and Verification
  description: |
    Require that the presented identity evidence be validated and verified through [Assignment: organizational defined methods of validation and verification].
IA-12 (4):
  family: IA
  name: In-person Validation and Verification
  description: |
    Require that the validation and verification of identity evidence be conducted in person before a designated registration authority.
IA-12 (5):
  family: IA
  name: Address Confirmation
  description: |
    Require that a [Selection: registration code, notice of proofing] be delivered through an out-of-band channel to verify the users address (physical or digital) of record.
IA-12 (6):
  family: IA
  name: Accept Externally-proofed Identities
  description: |
    Accept externally-proofed identities at [Assignment: organization-defined identity assurance level].
IR-1:
  family: IR
  name: Policy and Procedures
  description: |2
     - a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]:
       - 1. [Selection (one or more): organization-level, mission/business process-level, system-level] incident response policy that:
         - (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
         - (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
       - 2. Procedures to facilitate the implementation of the incident response policy and the associated incident response controls;
     - b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the incident response policy and procedures; and
     - c. Review and update the current incident response:
       - 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and
       - 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events].
IR-2:
  family: IR
  name: Incident Response Training
  description: |2
     - a. Provide incident response training to system users consistent with assigned roles and responsibilities:
       - 1. Within [Assignment: organization-defined time period] of assuming an incident response role or responsibility or acquiring system access;
       - 2. When required by system changes; and
       - 3. [Assignment: organization-defined frequency] thereafter; and
     - b. Review and update incident response training content [Assignment: organization-defined frequency] and following [Assignment: organization-defined events].
IR-2 (1):
  family: IR
  name: Simulated Events
  description: |
    Incorporate simulated events into incident response training to facilitate the required response by personnel in crisis situations.
IR-2 (2):
  family: IR
  name: Automated Training Environments
  description: |
    Provide an incident response training environment using [Assignment: organization-defined automated mechanisms].
IR-2 (3):
  family: IR
  name: Breach
  description: |
    Provide incident response training on how to identify and respond to a breach, including the organization’s process for reporting a breach.
IR-3:
  family: IR
  name: Incident Response Testing
  description: |
    Test the effectiveness of the incident response capability for the system [Assignment: organization-defined frequency] using the following tests: [Assignment: organization-defined tests].
IR-3 (1):
  family: IR
  name: Automated Testing
  description: |
    Test the incident response capability using [Assignment: organization-defined automated mechanisms].
IR-3 (2):
  family: IR
  name: Coordination with Related Plans
  description: |
    Coordinate incident response testing with organizational elements responsible for related plans.
IR-3 (3):
  family: IR
  name: Continuous Improvement
  description: |
    Use qualitative and quantitative data from testing to:
     - (a) Determine the effectiveness of incident response processes;
     - (b) Continuously improve incident response processes; and
     - (c) Provide incident response measures and metrics that are accurate, consistent, and in a reproducible format.
IR-4:
  family: IR
  name: Incident Handling
  description: |2
     - a. Implement an incident handling capability for incidents that is consistent with the incident response plan and includes preparation, detection and analysis, containment, eradication, and recovery;
     - b. Coordinate incident handling activities with contingency planning activities;
     - c. Incorporate lessons learned from ongoing incident handling activities into incident response procedures, training, and testing, and implement the resulting changes accordingly; and
     - d. Ensure the rigor, intensity, scope, and results of incident handling activities are comparable and predictable across the organization.
IR-4 (1):
  family: IR
  name: Automated Incident Handling Processes
  description: |
    Support the incident handling process using [Assignment: organization-defined automated mechanisms].
IR-4 (2):
  family: IR
  name: Dynamic Reconfiguration
  description: |
    Include the following types of dynamic reconfiguration for [Assignment: organization-defined system components] as part of the incident response capability: [Assignment: organization-defined types of dynamic reconfiguration].
IR-4 (3):
  family: IR
  name: Continuity of Operations
  description: |
    Identify [Assignment: organization-defined classes of incidents] and take the following actions in response to those incidents to ensure continuation of organizational mission and business functions: [Assignment: organization-defined actions to take in response to classes of incidents].
IR-4 (4):
  family: IR
  name: Information Correlation
  description: |
    Correlate incident information and individual incident responses to achieve an organization-wide perspective on incident awareness and response.
IR-4 (5):
  family: IR
  name: Automatic Disabling of System
  description: |
    Implement a configurable capability to automatically disable the system if [Assignment: organization-defined security violations] are detected.
IR-4 (6):
  family: IR
  name: Insider Threats
  description: |
    Implement an incident handling capability for incidents involving insider threats.
IR-4 (7):
  family: IR
  name: Insider Threats — Intra-organization Coordination
  description: |
    Coordinate an incident handling capability for insider threats that includes the following organizational entities [Assignment: organization-defined entities].
IR-4 (8):
  family: IR
  name: Correlation with External Organizations
  description: |
    Coordinate with [Assignment: organization-defined external organizations] to correlate and share [Assignment: organization-defined incident information] to achieve a cross-organization perspective on incident awareness and more effective incident responses.
IR-4 (9):
  family: IR
  name: Dynamic Response Capability
  description: |
    Employ [Assignment: organization-defined dynamic response capabilities] to respond to incidents.
IR-4 (10):
  family: IR
  name: Supply Chain Coordination
  description: |
    Coordinate incident handling activities involving supply chain events with other organizations involved in the supply chain.
IR-4 (11):
  family: IR
  name: Integrated Incident Response Team
  description: |
    Establish and maintain an integrated incident response team that can be deployed to any location identified by the organization in [Assignment: organization-defined time period].
IR-4 (12):
  family: IR
  name: Malicious Code and Forensic Analysis
  description: |
    Analyze malicious code and/or other residual artifacts remaining in the system after the incident.
IR-4 (13):
  family: IR
  name: Behavior Analysis
  description: |
    Analyze anomalous or suspected adversarial behavior in or related to [Assignment: organization-defined environments or resources].
IR-4 (14):
  family: IR
  name: Security Operations Center
  description: |
    Establish and maintain a security operations center.
IR-4 (15):
  family: IR
  name: Public Relations and Reputation Repair
  description: |2
     - (a) Manage public relations associated with an incident; and
     - (b) Employ measures to repair the reputation of the organization.
IR-5:
  family: IR
  name: Incident Monitoring
  description: |
    Track and document incidents.
IR-5 (1):
  family: IR
  name: Automated Tracking, Data Collection, and Analysis
  description: |
    Track incidents and collect and analyze incident information using [Assignment: organization-defined automated mechanisms].
IR-6:
  family: IR
  name: Incident Reporting
  description: |2
     - a. Require personnel to report suspected incidents to the organizational incident response capability within [Assignment: organization-defined time period]; and
     - b. Report incident information to [Assignment: organization-defined authorities].
IR-6 (1):
  family: IR
  name: Automated Reporting
  description: |
    Report incidents using [Assignment: organization-defined automated mechanisms].
IR-6 (2):
  family: IR
  name: Vulnerabilities Related to Incidents
  description: |
    Report system vulnerabilities associated with reported incidents to [Assignment: organization-defined personnel or roles].
IR-6 (3):
  family: IR
  name: Supply Chain Coordination
  description: |
    Provide incident information to the provider of the product or service and other organizations involved in the supply chain or supply chain governance for systems or system components related to the incident.
IR-7:
  family: IR
  name: Incident Response Assistance
  description: |
    Provide an incident response support resource, integral to the organizational incident response capability, that offers advice and assistance to users of the system for the handling and reporting of incidents.
IR-7 (1):
  family: IR
  name: Automation Support for Availability of Information and Support
  description: |
    Increase the availability of incident response information and support using [Assignment: organization-defined automated mechanisms].
IR-7 (2):
  family: IR
  name: Coordination with External Providers
  description: |2
     - (a) Establish a direct, cooperative relationship between its incident response capability and external providers of system protection capability; and
     - (b) Identify organizational incident response team members to the external providers.
IR-8:
  family: IR
  name: Incident Response Plan
  description: |2
     - a. Develop an incident response plan that:
       - 1. Provides the organization with a roadmap for implementing its incident response capability;
       - 2. Describes the structure and organization of the incident response capability;
       - 3. Provides a high-level approach for how the incident response capability fits into the overall organization;
       - 4. Meets the unique requirements of the organization, which relate to mission, size, structure, and functions;
       - 5. Defines reportable incidents;
       - 6. Provides metrics for measuring the incident response capability within the organization;
       - 7. Defines the resources and management support needed to effectively maintain and mature an incident response capability;
       - 8. Addresses the sharing of incident information;
       - 9. Is reviewed and approved by [Assignment: organization-defined personnel or roles]
                         [Assignment: organization-defined frequency]; and
       - 10. Explicitly designates responsibility for incident response to [Assignment: organization-defined entities, personnel, or roles].
     - b. Distribute copies of the incident response plan to [Assignment: organization-defined incident response personnel (identified by name and/or by role) and organizational elements];
     - c. Update the incident response plan to address system and organizational changes or problems encountered during plan implementation, execution, or testing;
     - d. Communicate incident response plan changes to [Assignment: organization-defined incident response personnel (identified by name and/or by role) and organizational elements]; and
     - e. Protect the incident response plan from unauthorized disclosure and modification.
IR-8 (1):
  family: IR
  name: Breaches
  description: |
    Include the following in the Incident Response Plan for breaches involving personally identifiable information:
     - (a) A process to determine if notice to individuals or other organizations, including oversight organizations, is needed;
     - (b) An assessment process to determine the extent of the harm, embarrassment, inconvenience, or unfairness to affected individuals and any mechanisms to mitigate such harms; and
     - (c) Identification of applicable privacy requirements.
IR-9:
  family: IR
  name: Information Spillage Response
  description: |
    Respond to information spills by:
     - a. Assigning [Assignment: organization-defined personnel or roles] with responsibility for responding to information spills;
     - b. Identifying the specific information involved in the system contamination;
     - c. Alerting [Assignment: organization-defined personnel or roles] of the information spill using a method of communication not associated with the spill;
     - d. Isolating the contaminated system or system component;
     - e. Eradicating the information from the contaminated system or component;
     - f. Identifying other systems or system components that may have been subsequently contaminated; and
     - g. Performing the following additional actions: [Assignment: organization-defined actions].
IR-9 (1):
  family: IR
  name: Responsible Personnel
  description: ""
IR-9 (2):
  family: IR
  name: Training
  description: |
    Provide information spillage response training [Assignment: organization-defined frequency].
IR-9 (3):
  family: IR
  name: Post-spill Operations
  description: |
    Implement the following procedures to ensure that organizational personnel impacted by information spills can continue to carry out assigned tasks while contaminated systems are undergoing corrective actions: [Assignment: organization-defined procedures].
IR-9 (4):
  family: IR
  name: Exposure to Unauthorized Personnel
  description: |
    Employ the following controls for personnel exposed to information not within assigned access authorizations: [Assignment: organization-defined controls].
IR-10:
  family: IR
  name: Incident Analysis
  description: ""
MA-1:
  family: MA
  name: Policy and Procedures
  description: |2
     - a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]:
       - 1. [Selection (one or more): organization-level, mission/business process-level, system-level] maintenance policy that:
         - (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
         - (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
       - 2. Procedures to facilitate the implementation of the maintenance policy and the associated maintenance controls;
     - b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the maintenance policy and procedures; and
     - c. Review and update the current maintenance:
       - 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and
       - 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events].
MA-2:
  family: MA
  name: Controlled Maintenance
  description: |2
     - a. Schedule, document, and review records of maintenance, repair, and replacement on system components in accordance with manufacturer or vendor specifications and/or organizational requirements;
     - b. Approve and monitor all maintenance activities, whether performed on site or remotely and whether the system or system components are serviced on site or removed to another location;
     - c. Require that [Assignment: organization-defined personnel or roles] explicitly approve the removal of the system or system components from organizational facilities for off-site maintenance, repair, or replacement;
     - d. Sanitize equipment to remove the following information from associated media prior to removal from organizational facilities for off-site maintenance, repair, or replacement: [Assignment: organization-defined information];
     - e. Check all potentially impacted controls to verify that the controls are still functioning properly following maintenance, repair, or replacement actions; and
     - f. Include the following information in organizational maintenance records: [Assignment: organization-defined information].
MA-2 (1):
  family: MA
  name: Record Content
  description: ""
MA-2 (2):
  family: MA
  name: Automated Maintenance Activities
  description: |2
     - (a) Schedule, conduct, and document maintenance, repair, and replacement actions for the system using [Assignment: organization-defined automated mechanisms]; and
     - (b) Produce up-to date, accurate, and complete records of all maintenance, repair, and replacement actions requested, scheduled, in process, and completed.
MA-3:
  family: MA
  name: Maintenance Tools
  description: |2
     - a. Approve, control, and monitor the use of system maintenance tools; and
     - b. Review previously approved system maintenance tools [Assignment: organization-defined frequency].
MA-3 (1):
  family: MA
  name: Inspect Tools
  description: |
    Inspect the maintenance tools used by maintenance personnel for improper or unauthorized modifications.
MA-3 (2):
  family: MA
  name: Inspect Media
  description: |
    Check media containing diagnostic and test programs for malicious code before the media are used in the system.
MA-3 (3):
  family: MA
  name: Prevent Unauthorized Removal
  description: |
    Prevent the removal of maintenance equipment containing organizational information by:
     - (a) Verifying that there is no organizational information contained on the equipment;
     - (b) Sanitizing or destroying the equipment;
     - (c) Retaining the equipment within the facility; or
     - (d) Obtaining an exemption from [Assignment: organization-defined personnel or roles] explicitly authorizing removal of the equipment from the facility.
MA-3 (4):
  family: MA
  name: Restricted Tool Use
  description: |
    Restrict the use of maintenance tools to authorized personnel only.
MA-3 (5):
  family: MA
  name: Execution with Privilege
  description: |
    Monitor the use of maintenance tools that execute with increased privilege.
MA-3 (6):
  family: MA
  name: Software Updates and Patches
  description: |
    Inspect maintenance tools to ensure the latest software updates and patches are installed.
MA-4:
  family: MA
  name: Nonlocal Maintenance
  description: |2
     - a. Approve and monitor nonlocal maintenance and diagnostic activities;
     - b. Allow the use of nonlocal maintenance and diagnostic tools only as consistent with organizational policy and documented in the security plan for the system;
     - c. Employ strong authentication in the establishment of nonlocal maintenance and diagnostic sessions;
     - d. Maintain records for nonlocal maintenance and diagnostic activities; and
     - e. Terminate session and network connections when nonlocal maintenance is completed.
MA-4 (1):
  family: MA
  name: Logging and Review
  description: |2
     - (a) Log [Assignment: organization-defined audit events] for nonlocal maintenance and diagnostic sessions; and
     - (b) Review the audit records of the maintenance and diagnostic sessions to detect anomalous behavior.
MA-4 (2):
  family: MA
  name: Logically separated communications paths.
  description: |
    Discussion:  Communications paths can be logically separated using encryption.
MA-4 (3):
  family: MA
  name: Comparable Security and Sanitization
  description: |2
     - (a) Require that nonlocal maintenance and diagnostic services be performed from a system that implements a security capability comparable to the capability implemented on the system being serviced; or
     - (b) Remove the component to be serviced from the system prior to nonlocal maintenance or diagnostic services; sanitize the component (for organizational information); and after the service is performed, inspect and sanitize the component (for potentially malicious software) before reconnecting the component to the system.
MA-4 (4):
  family: MA
  name: Authentication and Separation of Maintenance Sessions
  description: |
    Protect nonlocal maintenance sessions by:
     - (a) Employing [Assignment: organization-defined authenticators that are replay resistant]; and
     - (b) Separating the maintenance sessions from other network sessions with the system by either:
       - (1) Physically separated communications paths; or
       - (2) Logically separated communications paths.
MA-4 (5):
  family: MA
  name: Approvals and Notifications
  description: |2
     - (a) Require the approval of each nonlocal maintenance session by [Assignment: organization-defined personnel or roles]; and
     - (b) Notify the following personnel or roles of the date and time of planned nonlocal maintenance: [Assignment: organization-defined personnel or roles].
MA-4 (6):
  family: MA
  name: Cryptographic Protection
  description: |
    Implement the following cryptographic mechanisms to protect the integrity and confidentiality of nonlocal maintenance and diagnostic communications: [Assignment: organization-defined cryptographic mechanisms].
MA-4 (7):
  family: MA
  name: Disconnect Verification
  description: |
    Verify session and network connection termination after the completion of nonlocal maintenance and diagnostic sessions.
MA-5:
  family: MA
  name: Maintenance Personnel
  description: |2
     - a. Establish a process for maintenance personnel authorization and maintain a list of authorized maintenance organizations or personnel;
     - b. Verify that non-escorted personnel performing maintenance on the system possess the required access authorizations; and
     - c. Designate organizational personnel with required access authorizations and technical competence to supervise the maintenance activities of personnel who do not possess the required access authorizations.
MA-5 (1):
  family: MA
  name: Individuals Without Appropriate Access
  description: |2
     - (a) Implement procedures for the use of maintenance personnel that lack appropriate security clearances or are not U.S. citizens, that include the following requirements:
       - (1) Maintenance personnel who do not have needed access authorizations, clearances, or formal access approvals are escorted and supervised during the performance of maintenance and diagnostic activities on the system by approved organizational personnel who are fully cleared, have appropriate access authorizations, and are technically qualified; and
       - (2) Prior to initiating maintenance or diagnostic activities by personnel who do not have needed access authorizations, clearances or formal access approvals, all volatile information storage components within the system are sanitized and all nonvolatile storage media are removed or physically disconnected from the system and secured; and
     - (b) Develop and implement [Assignment: organization-defined alternate controls] in the event a system component cannot be sanitized, removed, or disconnected from the system.
MA-5 (2):
  family: MA
  name: Security Clearances for Classified Systems
  description: |
    Verify that personnel performing maintenance and diagnostic activities on a system processing, storing, or transmitting classified information possess security clearances and formal access approvals for at least the highest classification level and for compartments of information on the system.
MA-5 (3):
  family: MA
  name: Citizenship Requirements for Classified Systems
  description: |
    Verify that personnel performing maintenance and diagnostic activities on a system processing, storing, or transmitting classified information are U.S. citizens.
MA-5 (4):
  family: MA
  name: Foreign Nationals
  description: |
    Ensure that:
     - (a) Foreign nationals with appropriate security clearances are used to conduct maintenance and diagnostic activities on classified systems only when the systems are jointly owned and operated by the United States and foreign allied governments, or owned and operated solely by foreign allied governments; and
     - (b) Approvals, consents, and detailed operational conditions regarding the use of foreign nationals to conduct maintenance and diagnostic activities on classified systems are fully documented within Memoranda of Agreements.
MA-5 (5):
  family: MA
  name: Non-system Maintenance
  description: |
    Ensure that non-escorted personnel performing maintenance activities not directly associated with the system but in the physical proximity of the system, have required access authorizations.
MA-6:
  family: MA
  name: Timely Maintenance
  description: |
    Obtain maintenance support and/or spare parts for [Assignment: organization-defined system components] within [Assignment: organization-defined time period] of failure.
MA-6 (1):
  family: MA
  name: Preventive Maintenance
  description: |
    Perform preventive maintenance on [Assignment: organization-defined system components] at [Assignment: organization-defined time intervals].
MA-6 (2):
  family: MA
  name: Predictive Maintenance
  description: |
    Perform predictive maintenance on [Assignment: organization-defined system components] at [Assignment: organization-defined time intervals].
MA-6 (3):
  family: MA
  name: Automated Support for Predictive Maintenance
  description: |
    Transfer predictive maintenance data to a maintenance management system using [Assignment: organization-defined automated mechanisms].
MA-7:
  family: MA
  name: Field Maintenance
  description: |
    Restrict or prohibit field maintenance on [Assignment: organization-defined systems or system components] to [Assignment: organization-defined trusted maintenance facilities].
MP-1:
  family: MP
  name: Policy and Procedures
  description: |2
     - a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]:
       - 1. [Selection (one or more): organization-level, mission/business process-level, system-level] media protection policy that:
         - (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
         - (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
       - 2. Procedures to facilitate the implementation of the media protection policy and the associated media protection controls;
     - b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the media protection policy and procedures; and
     - c. Review and update the current media protection:
       - 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and
       - 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events].
MP-2:
  family: MP
  name: Media Access
  description: |
    Restrict access to [Assignment: organization-defined types of digital and/or non-digital media] to [Assignment: organization-defined personnel or roles].
MP-2 (1):
  family: MP
  name: Automated Restricted Access
  description: ""
MP-2 (2):
  family: MP
  name: Cryptographic Protection
  description: ""
MP-3:
  family: MP
  name: Media Marking
  description: |2
     - a. Mark system media indicating the distribution limitations, handling caveats, and applicable security markings (if any) of the information; and
     - b. Exempt [Assignment: organization-defined types of system media] from marking if the media remain within [Assignment: organization-defined controlled areas].
MP-4:
  family: MP
  name: Media Storage
  description: |2
     - a. Physically control and securely store [Assignment: organization-defined types of digital and/or non-digital media] within [Assignment: organization-defined controlled areas]; and
     - b. Protect system media types defined in MP-4a until the media are destroyed or sanitized using approved equipment, techniques, and procedures.
MP-4 (1):
  family: MP
  name: Cryptographic Protection
  description: ""
MP-4 (2):
  family: MP
  name: Automated Restricted Access
  description: |
    Restrict access to media storage areas and log access attempts and access granted using [Assignment: organization-defined automated mechanisms].
MP-5:
  family: MP
  name: Media Transport
  description: |2
     - a. Protect and control [Assignment: organization-defined types of system media] during transport outside of controlled areas using [Assignment: organization-defined controls];
     - b. Maintain accountability for system media during transport outside of controlled areas;
     - c. Document activities associated with the transport of system media; and
     - d. Restrict the activities associated with the transport of system media to authorized personnel.
MP-5 (1):
  family: MP
  name: Protection Outside of Controlled Areas
  description: ""
MP-5 (2):
  family: MP
  name: Documentation of Activities
  description: ""
MP-5 (3):
  family: MP
  name: Custodians
  description: |
    Employ an identified custodian during transport of system media outside of controlled areas.
MP-5 (4):
  family: MP
  name: Cryptographic Protection
  description: ""
MP-6:
  family: MP
  name: Media Sanitization
  description: |2
     - a. Sanitize [Assignment: organization-defined system media] prior to disposal, release out of organizational control, or release for reuse using [Assignment: organization-defined sanitization techniques and procedures]; and
     - b. Employ sanitization mechanisms with the strength and integrity commensurate with the security category or classification of the information.
MP-6 (1):
  family: MP
  name: Review, Approve, Track, Document, and Verify
  description: |
    Review, approve, track, document, and verify media sanitization and disposal actions.
MP-6 (2):
  family: MP
  name: Equipment Testing
  description: |
    Test sanitization equipment and procedures [Assignment: organization-defined frequency] to ensure that the intended sanitization is being achieved.
MP-6 (3):
  family: MP
  name: Nondestructive Techniques
  description: |
    Apply nondestructive sanitization techniques to portable storage devices prior to connecting such devices to the system under the following circumstances: [Assignment: organization-defined circumstances requiring sanitization of portable storage devices].
MP-6 (4):
  family: MP
  name: Controlled Unclassified Information
  description: ""
MP-6 (5):
  family: MP
  name: Classified Information
  description: ""
MP-6 (6):
  family: MP
  name: Media Destruction
  description: ""
MP-6 (7):
  family: MP
  name: Dual Authorization
  description: |
    Enforce dual authorization for the sanitization of [Assignment: organization-defined system media].
MP-6 (8):
  family: MP
  name: Remote Purging or Wiping of Information
  description: |
    Provide the capability to purge or wipe information from [Assignment: organization-defined systems or system components]
                      [Selection: remotely, under the following conditions: [Assignment: organization-defined conditions]].
MP-7:
  family: MP
  name: Media Use
  description: |2
     - a. [Selection: Restrict, Prohibit] the use of [Assignment: organization-defined types of system media] on [Assignment: organization-defined systems or system components] using [Assignment: organization-defined controls]; and
     - b. Prohibit the use of portable storage devices in organizational systems when such devices have no identifiable owner.
MP-7 (1):
  family: MP
  name: Prohibit Use Without Owner
  description: ""
MP-7 (2):
  family: MP
  name: Prohibit Use of Sanitization-resistant Media
  description: |
    Prohibit the use of sanitization-resistant media in organizational systems.
MP-8:
  family: MP
  name: Media Downgrading
  description: |2
     - a. Establish [Assignment: organization-defined system media downgrading process] that includes employing downgrading mechanisms with strength and integrity commensurate with the security category or classification of the information;
     - b. Verify that the system media downgrading process is commensurate with the security category and/or classification level of the information to be removed and the access authorizations of the potential recipients of the downgraded information;
     - c. Identify [Assignment: organization-defined system media requiring downgrading]; and
     - d. Downgrade the identified system media using the established process.
MP-8 (1):
  family: MP
  name: Documentation of Process
  description: |
    Document system media downgrading actions.
MP-8 (2):
  family: MP
  name: Equipment Testing
  description: |
    Test downgrading equipment and procedures [Assignment: organization-defined frequency] to ensure that downgrading actions are being achieved.
MP-8 (3):
  family: MP
  name: Controlled Unclassified Information
  description: |
    Downgrade system media containing controlled unclassified information prior to public release.
MP-8 (4):
  family: MP
  name: Classified Information
  description: |
    Downgrade system media containing classified information prior to release to individuals without required access authorizations.
PE-1:
  family: PE
  name: Policy and Procedures
  description: |2
     - a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]:
       - 1. [Selection (one or more): organization-level, mission/business process-level, system-level] physical and environmental protection policy that:
         - (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
         - (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
       - 2. Procedures to facilitate the implementation of the physical and environmental protection policy and the associated physical and environmental protection controls;
     - b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the physical and environmental protection policy and procedures; and
     - c. Review and update the current physical and environmental protection:
       - 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and
       - 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events].
PE-2:
  family: PE
  name: Physical Access Authorizations
  description: |2
     - a. Develop, approve, and maintain a list of individuals with authorized access to the facility where the system resides;
     - b. Issue authorization credentials for facility access;
     - c. Review the access list detailing authorized facility access by individuals [Assignment: organization-defined frequency]; and
     - d. Remove individuals from the facility access list when access is no longer required.
PE-2 (1):
  family: PE
  name: Access by Position or Role
  description: |
    Authorize physical access to the facility where the system resides based on position or role.
PE-2 (2):
  family: PE
  name: Two Forms of Identification
  description: |
    Require two forms of identification from the following forms of identification for visitor access to the facility where the system resides: [Assignment: organization-defined list of acceptable forms of identification].
PE-2 (3):
  family: PE
  name: Restrict Unescorted Access
  description: |
    Restrict unescorted access to the facility where the system resides to personnel with [Selection (one or more): security clearances for all information contained within the system, formal access authorizations for all information contained within the system, need for access to all information contained within the system, [Assignment: organization-defined physical access authorizations]].
PE-3:
  family: PE
  name: Physical Access Control
  description: |2
     - a. Enforce physical access authorizations at [Assignment: organization-defined entry and exit points to the facility where the system resides] by:
       - 1. Verifying individual access authorizations before granting access to the facility; and
       - 2. Controlling ingress and egress to the facility using [Selection (one or more): [Assignment: organization-defined physical access control systems or devices], guards];
     - b. Maintain physical access audit logs for [Assignment: organization-defined entry or exit points];
     - c. Control access to areas within the facility designated as publicly accessible by implementing the following controls: [Assignment: organization-defined physical access controls];
     - d. Escort visitors and control visitor activity [Assignment: organization-defined circumstances requiring visitor escorts and control of visitor activity];
     - e. Secure keys, combinations, and other physical access devices;
     - f. Inventory [Assignment: organization-defined physical access devices] every [Assignment: organization-defined frequency]; and
     - g. Change combinations and keys [Assignment: organization-defined frequency] and/or when keys are lost, combinations are compromised, or when individuals possessing the keys or combinations are transferred or terminated.
PE-3 (1):
  family: PE
  name: System Access
  description: |
    Enforce physical access authorizations to the system in addition to the physical access controls for the facility at [Assignment: organization-defined physical spaces containing one or more components of the system].
PE-3 (2):
  family: PE
  name: Facility and Systems
  description: |
    Perform security checks [Assignment: organization-defined frequency] at the physical perimeter of the facility or system for exfiltration of information or removal of system components.
PE-3 (3):
  family: PE
  name: Continuous Guards
  description: |
    Employ guards to control [Assignment: organization-defined physical access points] to the facility where the system resides 24 hours per day, 7 days per week.
PE-3 (4):
  family: PE
  name: Lockable Casings
  description: |
    Use lockable physical casings to protect [Assignment: organization-defined system components] from unauthorized physical access.
PE-3 (5):
  family: PE
  name: Tamper Protection
  description: |
    Employ [Assignment: organization-defined anti-tamper technologies] to [Selection (one or more): detect, prevent] physical tampering or alteration of [Assignment: organization-defined hardware components] within the system.
PE-3 (6):
  family: PE
  name: Facility Penetration Testing
  description: ""
PE-3 (7):
  family: PE
  name: Physical Barriers
  description: |
    Limit access using physical barriers.
PE-3 (8):
  family: PE
  name: Access Control Vestibules
  description: |
    Employ access control vestibules at [Assignment: organization-defined locations within the facility].
PE-4:
  family: PE
  name: Access Control for Transmission
  description: |
    Control physical access to [Assignment: organization-defined system distribution and transmission lines] within organizational facilities using [Assignment: organization-defined security controls].
PE-5:
  family: PE
  name: Access Control for Output Devices
  description: |
    Control physical access to output from [Assignment: organization-defined output devices] to prevent unauthorized individuals from obtaining the output.
PE-5 (1):
  family: PE
  name: Access to Output by Authorized Individuals
  description: ""
PE-5 (2):
  family: PE
  name: Link to Individual Identity
  description: |
    Link individual identity to receipt of output from output devices.
PE-5 (3):
  family: PE
  name: Marking Output Devices
  description: ""
PE-6:
  family: PE
  name: Monitoring Physical Access
  description: |2
     - a. Monitor physical access to the facility where the system resides to detect and respond to physical security incidents;
     - b. Review physical access logs [Assignment: organization-defined frequency] and upon occurrence of [Assignment: organization-defined events or potential indications of events]; and
     - c. Coordinate results of reviews and investigations with the organizational incident response capability.
PE-6 (1):
  family: PE
  name: Intrusion Alarms and Surveillance Equipment
  description: |
    Monitor physical access to the facility where the system resides using physical intrusion alarms and surveillance equipment.
PE-6 (2):
  family: PE
  name: Automated Intrusion Recognition and Responses
  description: |
    Recognize [Assignment: organization-defined classes or types of intrusions] and initiate [Assignment: organization-defined response actions] using [Assignment: organization-defined automated mechanisms].
PE-6 (3):
  family: PE
  name: Video Surveillance
  description: |2
     - (a) Employ video surveillance of [Assignment: organization-defined operational areas];
     - (b) Review video recordings [Assignment: organization-defined frequency]; and
     - (c) Retain video recordings for [Assignment: organization-defined time period].
PE-6 (4):
  family: PE
  name: Monitoring Physical Access to Systems
  description: |
    Monitor physical access to the system in addition to the physical access monitoring of the facility at [Assignment: organization-defined physical spaces containing one or more components of the system].
PE-7:
  family: PE
  name: Visitor Control
  description: ""
PE-8:
  family: PE
  name: Visitor Access Records
  description: |2
     - a. Maintain visitor access records to the facility where the system resides for [Assignment: organization-defined time period];
     - b. Review visitor access records [Assignment: organization-defined frequency]; and
     - c. Report anomalies in visitor access records to [Assignment: organization-defined personnel].
PE-8 (1):
  family: PE
  name: Automated Records Maintenance and Review
  description: |
    Maintain and review visitor access records using [Assignment: organization-defined automated mechanisms].
PE-8 (2):
  family: PE
  name: Physical Access Records
  description: ""
PE-8 (3):
  family: PE
  name: Limit Personally Identifiable Information Elements
  description: |
    Limit personally identifiable information contained in visitor access records to the following elements identified in the privacy risk assessment: [Assignment: organization-defined elements].
PE-9:
  family: PE
  name: Power Equipment and Cabling
  description: |
    Protect power equipment and power cabling for the system from damage and destruction.
PE-9 (1):
  family: PE
  name: Redundant Cabling
  description: |
    Employ redundant power cabling paths that are physically separated by [Assignment: organization-defined distance].
PE-9 (2):
  family: PE
  name: Automatic Voltage Controls
  description: |
    Employ automatic voltage controls for [Assignment: organization-defined critical system components].
PE-10:
  family: PE
  name: Emergency Shutoff
  description: |2
     - a. Provide the capability of shutting off power to [Assignment: organization-defined system or individual system components] in emergency situations;
     - b. Place emergency shutoff switches or devices in [Assignment: organization-defined location by system or system component] to facilitate access for authorized personnel; and
     - c. Protect emergency power shutoff capability from unauthorized activation.
PE-10 (1):
  family: PE
  name: Accidental and Unauthorized Activation
  description: ""
PE-11:
  family: PE
  name: Emergency Power
  description: |
    Provide an uninterruptible power supply to facilitate [Selection (one or more): an orderly shutdown of the system, transition of the system to long-term alternate power] in the event of a primary power source loss.
PE-11 (1):
  family: PE
  name: Alternate Power Supply — Minimal Operational Capability
  description: |
    Provide an alternate power supply for the system that is activated [Selection: manually, automatically] and that can maintain minimally required operational capability in the event of an extended loss of the primary power source.
PE-11 (2):
  family: PE
  name: Alternate Power Supply — Self-contained
  description: |
    Provide an alternate power supply for the system that is activated [Selection: manually, automatically] and that is:
     - (a) Self-contained;
     - (b) Not reliant on external power generation; and
     - (c) Capable of maintaining [Selection: minimally required operational capability, full operational capability] in the event of an extended loss of the primary power source.
PE-12:
  family: PE
  name: Emergency Lighting
  description: |
    Employ and maintain automatic emergency lighting for the system that activates in the event of a power outage or disruption and that covers emergency exits and evacuation routes within the facility.
PE-12 (1):
  family: PE
  name: Essential Mission and Business Functions
  description: |
    Provide emergency lighting for all areas within the facility supporting essential mission and business functions.
PE-13:
  family: PE
  name: Fire Protection
  description: |
    Employ and maintain fire detection and suppression systems that are supported by an independent energy source.
PE-13 (1):
  family: PE
  name: Detection Systems – Automatic Activation and Notification
  description: |
    Employ fire detection systems that activate automatically and notify [Assignment: organization-defined personnel or roles] and [Assignment: organization-defined emergency responders] in the event of a fire.
PE-13 (2):
  family: PE
  name: Suppression Systems – Automatic Activation and Notification
  description: |2
     - (a) Employ fire suppression systems that activate automatically and notify [Assignment: organization-defined personnel or roles] and [Assignment: organization-defined emergency responders]; and
     - (b) Employ an automatic fire suppression capability when the facility is not staffed on a continuous basis.
PE-13 (3):
  family: PE
  name: Automatic Fire Suppression
  description: ""
PE-13 (4):
  family: PE
  name: Inspections
  description: |
    Ensure that the facility undergoes [Assignment: organization-defined frequency] fire protection inspections by authorized and qualified inspectors and identified deficiencies are resolved within [Assignment: organization-defined time period].
PE-14:
  family: PE
  name: Environmental Controls
  description: |2
     - a. Maintain [Selection (one or more): temperature, humidity, pressure, radiation, [Assignment: organization-defined environmental control]] levels within the facility where the system resides at [Assignment: organization-defined acceptable levels]; and
     - b. Monitor environmental control levels [Assignment: organization-defined frequency].
PE-14 (1):
  family: PE
  name: Automatic Controls
  description: |
    Employ the following automatic environmental controls in the facility to prevent fluctuations potentially harmful to the system: [Assignment: organization-defined automatic environmental controls].
PE-14 (2):
  family: PE
  name: Monitoring with Alarms and Notifications
  description: |
    Employ environmental control monitoring that provides an alarm or notification of changes potentially harmful to personnel or equipment to [Assignment: organization-defined personnel or roles].
PE-15:
  family: PE
  name: Water Damage Protection
  description: |
    Protect the system from damage resulting from water leakage by providing master shutoff or isolation valves that are accessible, working properly, and known to key personnel.
PE-15 (1):
  family: PE
  name: Automation Support
  description: |
    Detect the presence of water near the system and alert [Assignment: organization-defined personnel or roles] using [Assignment: organization-defined automated mechanisms].
PE-16:
  family: PE
  name: Delivery and Removal
  description: |2
     - a. Authorize and control [Assignment: organization-defined types of system components] entering and exiting the facility; and
     - b. Maintain records of the system components.
PE-17:
  family: PE
  name: Alternate Work Site
  description: |2
     - a. Determine and document the [Assignment: organization-defined alternate work sites] allowed for use by employees;
     - b. Employ the following controls at alternate work sites: [Assignment: organization-defined controls];
     - c. Assess the effectiveness of controls at alternate work sites; and
     - d. Provide a means for employees to communicate with information security and privacy personnel in case of incidents.
PE-18:
  family: PE
  name: Location of System Components
  description: |
    Position system components within the facility to minimize potential damage from [Assignment: organization-defined physical and environmental hazards] and to minimize the opportunity for unauthorized access.
PE-18 (1):
  family: PE
  name: Facility Site
  description: ""
PE-19:
  family: PE
  name: Information Leakage
  description: |
    Protect the system from information leakage due to electromagnetic signals emanations.
PE-19 (1):
  family: PE
  name: National Emissions and Tempest Policies and Procedures
  description: |
    Protect system components, associated data communications, and networks in accordance with national Emissions Security policies and procedures based on the security category or classification of the information.
PE-20:
  family: PE
  name: Asset Monitoring and Tracking
  description: |
    Employ [Assignment: organization-defined asset location technologies] to track and monitor the location and movement of [Assignment: organization-defined assets] within [Assignment: organization-defined controlled areas].
PE-21:
  family: PE
  name: Electromagnetic Pulse Protection
  description: |
    Employ [Assignment: organization-defined protective measures] against electromagnetic pulse damage for [Assignment: organization-defined systems and system components].
PE-22:
  family: PE
  name: Component Marking
  description: |
    Mark [Assignment: organization-defined system hardware components] indicating the impact level or classification level of the information permitted to be processed, stored, or transmitted by the hardware component.
PE-23:
  family: PE
  name: Facility Location
  description: |2
     - a. Plan the location or site of the facility where the system resides considering physical and environmental hazards; and
     - b. For existing facilities, consider the physical and environmental hazards in the organizational risk management strategy.
PL-1:
  family: PL
  name: Policy and Procedures
  description: |2
     - a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]:
       - 1. [Selection (one or more): organization-level, mission/business process-level, system-level] planning policy that:
         - (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
         - (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
       - 2. Procedures to facilitate the implementation of the planning policy and the associated planning controls;
     - b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the planning policy and procedures; and
     - c. Review and update the current planning:
       - 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and
       - 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events].
PL-2:
  family: PL
  name: System Security and Privacy Plans
  description: |2
     - a. Develop security and privacy plans for the system that:
       - 1. Are consistent with the organization’s enterprise architecture;
       - 2. Explicitly define the constituent system components;
       - 3. Describe the operational context of the system in terms of mission and business processes;
       - 4. Identify the individuals that fulfill system roles and responsibilities;
       - 5. Identify the information types processed, stored, and transmitted by the system;
       - 6. Provide the security categorization of the system, including supporting rationale;
       - 7. Describe any specific threats to the system that are of concern to the organization;
       - 8. Provide the results of a privacy risk assessment for systems processing personally identifiable information;
       - 9. Describe the operational environment for the system and any dependencies on or connections to other systems or system components;
       - 10. Provide an overview of the security and privacy requirements for the system;
       - 11. Identify any relevant control baselines or overlays, if applicable;
       - 12. Describe the controls in place or planned for meeting the security and privacy requirements, including a rationale for any tailoring decisions;
       - 13. Include risk determinations for security and privacy architecture and design decisions;
       - 14. Include security- and privacy-related activities affecting the system that require planning and coordination with [Assignment: organization-defined individuals or groups]; and
       - 15. Are reviewed and approved by the authorizing official or designated representative prior to plan implementation.
     - b. Distribute copies of the plans and communicate subsequent changes to the plans to [Assignment: organization-defined personnel or roles];
     - c. Review the plans [Assignment: organization-defined frequency];
     - d. Update the plans to address changes to the system and environment of operation or problems identified during plan implementation or control assessments; and
     - e. Protect the plans from unauthorized disclosure and modification.
PL-2 (1):
  family: PL
  name: Concept of Operations
  description: ""
PL-2 (2):
  family: PL
  name: Functional Architecture
  description: ""
PL-2 (3):
  family: PL
  name: Plan and Coordinate with Other Organizational Entities
  description: ""
PL-3:
  family: PL
  name: System Security Plan Update
  description: ""
PL-4:
  family: PL
  name: Rules of Behavior
  description: |2
     - a. Establish and provide to individuals requiring access to the system, the rules that describe their responsibilities and expected behavior for information and system usage, security, and privacy;
     - b. Receive a documented acknowledgment from such individuals, indicating that they have read, understand, and agree to abide by the rules of behavior, before authorizing access to information and the system;
     - c. Review and update the rules of behavior [Assignment: organization-defined frequency]; and
     - d. Require individuals who have acknowledged a previous version of the rules of behavior to read and re-acknowledge [Selection (one or more): [Assignment: organization-defined frequency], when the rules are revised or updated].
PL-4 (1):
  family: PL
  name: Social Media and External Site/application Usage Restrictions
  description: |
    Include in the rules of behavior, restrictions on:
     - (a) Use of social media, social networking sites, and external sites/applications;
     - (b) Posting organizational information on public websites; and
     - (c) Use of organization-provided identifiers (e.g., email addresses) and authentication secrets (e.g., passwords) for creating accounts on external sites/applications.
PL-5:
  family: PL
  name: Privacy Impact Assessment
  description: ""
PL-6:
  family: PL
  name: Security-related Activity Planning
  description: ""
PL-7:
  family: PL
  name: Concept of Operations
  description: |2
     - a. Develop a Concept of Operations (CONOPS) for the system describing how the organization intends to operate the system from the perspective of information security and privacy; and
     - b. Review and update the CONOPS [Assignment: organization-defined frequency].
PL-8:
  family: PL
  name: Security and Privacy Architectures
  description: |2
     - a. Develop security and privacy architectures for the system that:
       - 1. Describe the requirements and approach to be taken for protecting the confidentiality, integrity, and availability of organizational information;
       - 2. Describe the requirements and approach to be taken for processing personally identifiable information to minimize privacy risk to individuals;
       - 3. Describe how the architectures are integrated into and support the enterprise architecture; and
       - 4. Describe any assumptions about, and dependencies on, external systems and services;
     - b. Review and update the architectures [Assignment: organization-defined frequency] to reflect changes in the enterprise architecture; and
     - c. Reflect planned architecture changes in security and privacy plans, Concept of Operations (CONOPS), criticality analysis, organizational procedures, and procurements and acquisitions.
PL-8 (1):
  family: PL
  name: Defense in Depth
  description: |
    Design the security and privacy architectures for the system using a defense-in-depth approach that:
     - (a) Allocates [Assignment: organization-defined controls] to [Assignment: organization-defined locations and architectural layers]; and
     - (b) Ensures that the allocated controls operate in a coordinated and mutually reinforcing manner.
PL-8 (2):
  family: PL
  name: Supplier Diversity
  description: |
    Require that [Assignment: organization-defined controls] allocated to [Assignment: organization-defined locations and architectural layers] are obtained from different suppliers.
PL-9:
  family: PL
  name: Central Management
  description: |
    Centrally manage [Assignment: organization-defined controls and related processes].
PL-10:
  family: PL
  name: Baseline Selection
  description: |
    Select a control baseline for the system.
PL-11:
  family: PL
  name: Baseline Tailoring
  description: |
    Tailor the selected control baseline by applying specified tailoring actions.
PM-1:
  family: PM
  name: Information Security Program Plan
  description: |2
     - a. Develop and disseminate an organization-wide information security program plan that:
       - 1. Provides an overview of the requirements for the security program and a description of the security program management controls and common controls in place or planned for meeting those requirements;
       - 2. Includes the identification and assignment of roles, responsibilities, management commitment, coordination among organizational entities, and compliance;
       - 3. Reflects the coordination among organizational entities responsible for information security; and
       - 4. Is approved by a senior official with responsibility and accountability for the risk being incurred to organizational operations (including mission, functions, image, and reputation), organizational assets, individuals, other organizations, and the Nation;
     - b. Review and update the organization-wide information security program plan [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and
     - c. Protect the information security program plan from unauthorized disclosure and modification.
PM-2:
  family: PM
  name: Information Security Program Leadership Role
  description: |
    Appoint a senior agency information security officer with the mission and resources to coordinate, develop, implement, and maintain an organization-wide information security program.
PM-3:
  family: PM
  name: Information Security and Privacy Resources
  description: |2
     - a. Include the resources needed to implement the information security and privacy programs in capital planning and investment requests and document all exceptions to this requirement;
     - b. Prepare documentation required for addressing information security and privacy programs in capital planning and investment requests in accordance with applicable laws, executive orders, directives, policies, regulations, standards; and
     - c. Make available for expenditure, the planned information security and privacy resources.
PM-4:
  family: PM
  name: Plan of Action and Milestones Process
  description: |2
     - a. Implement a process to ensure that plans of action and milestones for the information security, privacy, and supply chain risk management programs and associated organizational systems:
       - 1. Are developed and maintained;
       - 2. Document the remedial information security, privacy, and supply chain risk management actions to adequately respond to risk to organizational operations and assets, individuals, other organizations, and the Nation; and
       - 3. Are reported in accordance with established reporting requirements.
     - b. Review plans of action and milestones for consistency with the organizational risk management strategy and organization-wide priorities for risk response actions.
PM-5:
  family: PM
  name: System Inventory
  description: |
    Develop and update [Assignment: organization-defined frequency] an inventory of organizational systems.
PM-5 (1):
  family: PM
  name: Inventory of Personally Identifiable Information
  description: |
    Establish, maintain, and update [Assignment: organization-defined frequency] an inventory of all systems, applications, and projects that process personally identifiable information.
PM-6:
  family: PM
  name: Measures of Performance
  description: |
    Develop, monitor, and report on the results of information security and privacy measures of performance.
PM-7:
  family: PM
  name: Enterprise Architecture
  description: |
    Develop and maintain an enterprise architecture with consideration for information security, privacy, and the resulting risk to organizational operations and assets, individuals, other organizations, and the Nation.
PM-7 (1):
  family: PM
  name: Offloading
  description: |
    Offload [Assignment: organization-defined non-essential functions or services] to other systems, system components, or an external provider.
PM-8:
  family: PM
  name: Critical Infrastructure Plan
  description: |
    Address information security and privacy issues in the development, documentation, and updating of a critical infrastructure and key resources protection plan.
PM-9:
  family: PM
  name: Risk Management Strategy
  description: |2
     - a. Develops a comprehensive strategy to manage:
       - 1. Security risk to organizational operations and assets, individuals, other organizations, and the Nation associated with the operation and use of organizational systems; and
       - 2. Privacy risk to individuals resulting from the authorized processing of personally identifiable information;
     - b. Implement the risk management strategy consistently across the organization; and
     - c. Review and update the risk management strategy [Assignment: organization-defined frequency] or as required, to address organizational changes.
PM-10:
  family: PM
  name: Authorization Process
  description: |2
     - a. Manage the security and privacy state of organizational systems and the environments in which those systems operate through authorization processes;
     - b. Designate individuals to fulfill specific roles and responsibilities within the organizational risk management process; and
     - c. Integrate the authorization processes into an organization-wide risk management program.
PM-11:
  family: PM
  name: Mission and Business Process Definition
  description: |2
     - a. Define organizational mission and business processes with consideration for information security and privacy and the resulting risk to organizational operations, organizational assets, individuals, other organizations, and the Nation; and
     - b. Determine information protection and personally identifiable information processing needs arising from the defined mission and business processes; and
     - c. Review and revise the mission and business processes [Assignment: organization-defined frequency].
PM-12:
  family: PM
  name: Insider Threat Program
  description: |
    Implement an insider threat program that includes a cross-discipline insider threat incident handling team.
PM-13:
  family: PM
  name: Security and Privacy Workforce
  description: |
    Establish a security and privacy workforce development and improvement program.
PM-14:
  family: PM
  name: Testing, Training, and Monitoring
  description: |2
     - a. Implement a process for ensuring that organizational plans for conducting security and privacy testing, training, and monitoring activities associated with organizational systems:
       - 1. Are developed and maintained; and
       - 2. Continue to be executed; and
     - b. Review testing, training, and monitoring plans for consistency with the organizational risk management strategy and organization-wide priorities for risk response actions.
PM-15:
  family: PM
  name: Security and Privacy Groups and Associations
  description: |
    Establish and institutionalize contact with selected groups and associations within the security and privacy communities:
     - a. To facilitate ongoing security and privacy education and training for organizational personnel;
     - b. To maintain currency with recommended security and privacy practices, techniques, and technologies; and
     - c. To share current security and privacy information, including threats, vulnerabilities, and incidents.
PM-16:
  family: PM
  name: Threat Awareness Program
  description: |
    Implement a threat awareness program that includes a cross-organization information-sharing capability for threat intelligence.
PM-16 (1):
  family: PM
  name: Automated Means for Sharing Threat Intelligence
  description: |
    Employ automated mechanisms to maximize the effectiveness of sharing threat intelligence information.
PM-17:
  family: PM
  name: Protecting Controlled Unclassified Information on External Systems
  description: |2
     - a. Establish policy and procedures to ensure that requirements for the protection of controlled unclassified information that is processed, stored or transmitted on external systems, are implemented in accordance with applicable laws, executive orders, directives, policies, regulations, and standards; and
     - b. Review and update the policy and procedures [Assignment: organization-defined frequency].
PM-18:
  family: PM
  name: Privacy Program Plan
  description: |2
     - a. Develop and disseminate an organization-wide privacy program plan that provides an overview of the agency’s privacy program, and:
       - 1. Includes a description of the structure of the privacy program and the resources dedicated to the privacy program;
       - 2. Provides an overview of the requirements for the privacy program and a description of the privacy program management controls and common controls in place or planned for meeting those requirements;
       - 3. Includes the role of the senior agency official for privacy and the identification and assignment of roles of other privacy officials and staff and their responsibilities;
       - 4. Describes management commitment, compliance, and the strategic goals and objectives of the privacy program;
       - 5. Reflects coordination among organizational entities responsible for the different aspects of privacy; and
       - 6. Is approved by a senior official with responsibility and accountability for the privacy risk being incurred to organizational operations (including mission, functions, image, and reputation), organizational assets, individuals, other organizations, and the Nation; and
     - b. Update the plan [Assignment: organization-defined frequency] and to address changes in federal privacy laws and policy and organizational changes and problems identified during plan implementation or privacy control assessments.
PM-19:
  family: PM
  name: Privacy Program Leadership Role
  description: |
    Appoint a senior agency official for privacy with the authority, mission, accountability, and resources to coordinate, develop, and implement, applicable privacy requirements and manage privacy risks through the organization-wide privacy program.
PM-20:
  family: PM
  name: Dissemination of Privacy Program Information
  description: |
    Maintain a central resource webpage on the organization’s principal public website that serves as a central source of information about the organization’s privacy program and that:
     - a. Ensures that the public has access to information about organizational privacy activities and can communicate with its senior agency official for privacy;
     - b. Ensures that organizational privacy practices and reports are publicly available; and
     - c. Employs publicly facing email addresses and/or phone lines to enable the public to provide feedback and/or direct questions to privacy offices regarding privacy practices.
PM-20 (1):
  family: PM
  name: Privacy Policies on Websites, Applications, and Digital Services
  description: |
    Develop and post privacy policies on all external-facing websites, mobile applications, and other digital services, that:
     - (a) Are written in plain language and organized in a way that is easy to understand and navigate;
     - (b) Provide information needed by the public to make an informed decision about whether and how to interact with the organization; and
     - (c) Are updated whenever the organization makes a substantive change to the practices it describes and includes a time/date stamp to inform the public of the date of the most recent changes.
PM-21:
  family: PM
  name: Accounting of Disclosures
  description: |2
     - a. Develop and maintain an accurate accounting of disclosures of personally identifiable information, including:
       - 1. Date, nature, and purpose of each disclosure; and
       - 2. Name and address, or other contact information of the individual or organization to which the disclosure was made;
     - b. Retain the accounting of disclosures for the length of the time the personally identifiable information is maintained or five years after the disclosure is made, whichever is longer; and
     - c. Make the accounting of disclosures available to the individual to whom the personally identifiable information relates upon request.
PM-22:
  family: PM
  name: Personally Identifiable Information Quality Management
  description: |
    Develop and document organization-wide policies and procedures for:
     - a. Reviewing for the accuracy, relevance, timeliness, and completeness of personally identifiable information across the information life cycle;
     - b. Correcting or deleting inaccurate or outdated personally identifiable information;
     - c. Disseminating notice of corrected or deleted personally identifiable information to individuals or other appropriate entities; and
     - d. Appeals of adverse decisions on correction or deletion requests.
PM-23:
  family: PM
  name: Data Governance Body
  description: |
    Establish a Data Governance Body consisting of [Assignment: organization-defined roles] with [Assignment: organization-defined responsibilities].
PM-24:
  family: PM
  name: Data Integrity Board
  description: |
    Establish a Data Integrity Board to:
     - a. Review proposals to conduct or participate in a matching program; and
     - b. Conduct an annual review of all matching programs in which the agency has participated.
PM-25:
  family: PM
  name: Minimization of Personally Identifiable Information Used in Testing, Training, and Research
  description: |2
     - a. Develop, document, and implement policies and procedures that address the use of personally identifiable information for internal testing, training, and research;
     - b. Limit or minimize the amount of personally identifiable information used for internal testing, training, and research purposes;
     - c. Authorize the use of personally identifiable information when such information is required for internal testing, training, and research; and
     - d. Review and update policies and procedures [Assignment: organization-defined frequency].
PM-26:
  family: PM
  name: Complaint Management
  description: |
    Implement a process for receiving and responding to complaints, concerns, or questions from individuals about the organizational security and privacy practices that includes:
     - a. Mechanisms that are easy to use and readily accessible by the public;
     - b. All information necessary for successfully filing complaints;
     - c. Tracking mechanisms to ensure all complaints received are reviewed and addressed within [Assignment: organization-defined time period];
     - d. Acknowledgement of receipt of complaints, concerns, or questions from individuals within [Assignment: organization-defined time period]; and
     - e. Response to complaints, concerns, or questions from individuals within [Assignment: organization-defined time period].
PM-27:
  family: PM
  name: Privacy Reporting
  description: |2
     - a. Develop [Assignment: organization-defined privacy reports] and disseminate to:
       - 1. [Assignment: organization-defined oversight bodies] to demonstrate accountability with statutory, regulatory, and policy privacy mandates; and
       - 2. [Assignment: organization-defined officials] and other personnel with responsibility for monitoring privacy program compliance; and
     - b. Review and update privacy reports [Assignment: organization-defined frequency].
PM-28:
  family: PM
  name: Risk Framing
  description: |2
     - a. Identify and document:
       - 1. Assumptions affecting risk assessments, risk responses, and risk monitoring;
       - 2. Constraints affecting risk assessments, risk responses, and risk monitoring;
       - 3. Priorities and trade-offs considered by the organization for managing risk; and
       - 4. Organizational risk tolerance;
     - b. Distribute the results of risk framing activities to [Assignment: organization-defined personnel]; and
     - c. Review and update risk framing considerations [Assignment: organization-defined frequency].
PM-29:
  family: PM
  name: Risk Management Program Leadership Roles
  description: |2
     - a. Appoint a Senior Accountable Official for Risk Management to align organizational information security and privacy management processes with strategic, operational, and budgetary planning processes; and
     - b. Establish a Risk Executive (function) to view and analyze risk from an organization-wide perspective and ensure management of risk is consistent across the organization.
PM-30:
  family: PM
  name: Supply Chain Risk Management Strategy
  description: |2
     - a. Develop an organization-wide strategy for managing supply chain risks associated with the development, acquisition, maintenance, and disposal of systems, system components, and system services;
     - b. Implement the supply chain risk management strategy consistently across the organization; and
     - c. Review and update the supply chain risk management strategy on [Assignment: organization-defined frequency] or as required, to address organizational changes.
PM-30 (1):
  family: PM
  name: Suppliers of Critical or Mission-essential Items
  description: |
    Identify, prioritize, and assess suppliers of critical or mission-essential technologies, products, and services.
PM-31:
  family: PM
  name: Continuous Monitoring Strategy
  description: |
    Develop an organization-wide continuous monitoring strategy and implement continuous monitoring programs that include:
     - a. Establishing the following organization-wide metrics to be monitored: [Assignment: organization-defined metrics];
     - b. Establishing [Assignment: organization-defined frequencies] for monitoring and [Assignment: organization-defined frequencies] for assessment of control effectiveness;
     - c. Ongoing monitoring of organizationally-defined metrics in accordance with the continuous monitoring strategy;
     - d. Correlation and analysis of information generated by control assessments and monitoring;
     - e. Response actions to address results of the analysis of control assessment and monitoring information; and
     - f. Reporting the security and privacy status of organizational systems to [Assignment: organization-defined personnel or roles]
                      [Assignment: organization-defined frequency].
PM-32:
  family: PM
  name: Purposing
  description: |
    Analyze [Assignment: organization-defined systems or systems components] supporting mission essential services or functions to ensure that the information resources are being used consistent with their intended purpose.
PS-1:
  family: PS
  name: Policy and Procedures
  description: |2
     - a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]:
       - 1. [Selection (one or more): organization-level, mission/business process-level, system-level] personnel security policy that:
         - (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
         - (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
       - 2. Procedures to facilitate the implementation of the personnel security policy and the associated personnel security controls;
     - b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the personnel security policy and procedures; and
     - c. Review and update the current personnel security:
       - 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and
       - 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events].
PS-2:
  family: PS
  name: Position Risk Designation
  description: |2
     - a. Assign a risk designation to all organizational positions;
     - b. Establish screening criteria for individuals filling those positions; and
     - c. Review and update position risk designations [Assignment: organization-defined frequency].
PS-3:
  family: PS
  name: Personnel Screening
  description: |2
     - a. Screen individuals prior to authorizing access to the system; and
     - b. Rescreen individuals in accordance with [Assignment: organization-defined conditions requiring rescreening and, where rescreening is so indicated, the frequency of rescreening].
PS-3 (1):
  family: PS
  name: Classified Information
  description: |
    Verify that individuals accessing a system processing, storing, or transmitting classified information are cleared and indoctrinated to the highest classification level of the information to which they have access on the system.
PS-3 (2):
  family: PS
  name: Formal Indoctrination
  description: |
    Verify that individuals accessing a system processing, storing, or transmitting types of classified information that require formal indoctrination, are formally indoctrinated for all the relevant types of information to which they have access on the system.
PS-3 (3):
  family: PS
  name: Information with Special Protective Measures
  description: |
    Verify that individuals accessing a system processing, storing, or transmitting information requiring special protection:
     - (a) Have valid access authorizations that are demonstrated by assigned official government duties; and
     - (b) Satisfy [Assignment: organization-defined additional personnel screening criteria].
PS-3 (4):
  family: PS
  name: Citizenship Requirements
  description: |
    Verify that individuals accessing a system processing, storing, or transmitting [Assignment: organization-defined information types] meet [Assignment: organization-defined citizenship requirements].
PS-4:
  family: PS
  name: Personnel Termination
  description: |
    Upon termination of individual employment:
     - a. Disable system access within [Assignment: organization-defined time period];
     - b. Terminate or revoke any authenticators and credentials associated with the individual;
     - c. Conduct exit interviews that include a discussion of [Assignment: organization-defined information security topics];
     - d. Retrieve all security-related organizational system-related property; and
     - e. Retain access to organizational information and systems formerly controlled by terminated individual.
PS-4 (1):
  family: PS
  name: Post-employment Requirements
  description: |2
     - (a) Notify terminated individuals of applicable, legally binding post-employment requirements for the protection of organizational information; and
     - (b) Require terminated individuals to sign an acknowledgment of post-employment requirements as part of the organizational termination process.
PS-4 (2):
  family: PS
  name: Automated Actions
  description: |
    Use [Assignment: organization-defined automated mechanisms] to [Selection (one or more): notify [Assignment: organization-defined personnel or roles] of individual termination actions, disable access to system resources].
PS-5:
  family: PS
  name: Personnel Transfer
  description: |2
     - a. Review and confirm ongoing operational need for current logical and physical access authorizations to systems and facilities when individuals are reassigned or transferred to other positions within the organization;
     - b. Initiate [Assignment: organization-defined transfer or reassignment actions] within [Assignment: organization-defined time period following the formal transfer action];
     - c. Modify access authorization as needed to correspond with any changes in operational need due to reassignment or transfer; and
     - d. Notify [Assignment: organization-defined personnel or roles] within [Assignment: organization-defined time period].
PS-6:
  family: PS
  name: Access Agreements
  description: |2
     - a. Develop and document access agreements for organizational systems;
     - b. Review and update the access agreements [Assignment: organization-defined frequency]; and
     - c. Verify that individuals requiring access to organizational information and systems:
       - 1. Sign appropriate access agreements prior to being granted access; and
       - 2. Re-sign access agreements to maintain access to organizational systems when access agreements have been updated or [Assignment: organization-defined frequency].
PS-6 (1):
  family: PS
  name: Information Requiring Special Protection
  description: ""
PS-6 (2):
  family: PS
  name: Classified Information Requiring Special Protection
  description: |
    Verify that access to classified information requiring special protection is granted only to individuals who:
     - (a) Have a valid access authorization that is demonstrated by assigned official government duties;
     - (b) Satisfy associated personnel security criteria; and
     - (c) Have read, understood, and signed a nondisclosure agreement.
PS-6 (3):
  family: PS
  name: Post-employment Requirements
  description: |2
     - (a) Notify individuals of applicable, legally binding post-employment requirements for protection of organizational information; and
     - (b) Require individuals to sign an acknowledgment of these requirements, if applicable, as part of granting initial access to covered information.
PS-7:
  family: PS
  name: External Personnel Security
  description: |2
     - a. Establish personnel security requirements, including security roles and responsibilities for external providers;
     - b. Require external providers to comply with personnel security policies and procedures established by the organization;
     - c. Document personnel security requirements;
     - d. Require external providers to notify [Assignment: organization-defined personnel or roles] of any personnel transfers or terminations of external personnel who possess organizational credentials and/or badges, or who have system privileges within [Assignment: organization-defined time period]; and
     - e. Monitor provider compliance with personnel security requirements.
PS-8:
  family: PS
  name: Personnel Sanctions
  description: |2
     - a. Employ a formal sanctions process for individuals failing to comply with established information security and privacy policies and procedures; and
     - b. Notify [Assignment: organization-defined personnel or roles] within [Assignment: organization-defined time period] when a formal employee sanctions process is initiated, identifying the individual sanctioned and the reason for the sanction.
PS-9:
  family: PS
  name: Position Descriptions
  description: |
    Incorporate security and privacy roles and responsibilities into organizational position descriptions.
PT-1:
  family: PT
  name: Policy and Procedures
  description: |2
     - a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]:
       - 1. [Selection (one or more): organization-level, mission/business process-level, system-level] personally identifiable information processing and transparency policy that:
         - (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
         - (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
       - 2. Procedures to facilitate the implementation of the personally identifiable information processing and transparency policy and the associated personally identifiable information processing and transparency controls;
     - b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the personally identifiable information processing and transparency policy and procedures; and
     - c. Review and update the current personally identifiable information processing and transparency:
       - 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and
       - 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events].
PT-2:
  family: PT
  name: Authority to Process Personally Identifiable Information
  description: |2
     - a. Determine and document the [Assignment: organization-defined authority] that permits the [Assignment: organization-defined processing] of personally identifiable information; and
     - b. Restrict the [Assignment: organization-defined processing] of personally identifiable information to only that which is authorized.
PT-2 (1):
  family: PT
  name: Data Tagging
  description: |
    Attach data tags containing [Assignment: organization-defined permissible processing] to [Assignment: organization-defined elements of personally identifiable information].
PT-2 (2):
  family: PT
  name: Automation
  description: |
    Manage enforcement of the authorized processing of personally identifiable information using [Assignment: organization-defined automated mechanisms].
PT-3:
  family: PT
  name: Personally Identifiable Information Processing Purposes
  description: |2
     - a. Identify and document the [Assignment: Assignment organization-defined purpose(s)] for processing personally identifiable information;
     - b. Describe the purpose(s) in the public privacy notices and policies of the organization;
     - c. Restrict the [Assignment: organization-defined processing] of personally identifiable information to only that which is compatible with the identified purpose(s); and
     - d. Monitor changes in processing personally identifiable information and implement [Assignment: organization-defined mechanisms] to ensure that any changes are made in accordance with [Assignment: organization-defined requirements].
PT-3 (1):
  family: PT
  name: Data Tagging
  description: |
    Attach data tags containing the following purposes to [Assignment: organization-defined elements of personally identifiable information]: [Assignment: organization-defined processing purposes].
PT-3 (2):
  family: PT
  name: Automation
  description: |
    Track processing purposes of personally identifiable information using [Assignment: organization-defined automated mechanisms].
PT-4:
  family: PT
  name: Consent
  description: |
    Implement [Assignment: organization-defined tools or mechanisms] for individuals to consent to the processing of their personally identifiable information prior to its collection that facilitate individuals’ informed decision-making.
PT-4 (1):
  family: PT
  name: Tailored Consent
  description: |
    Provide [Assignment: organization-defined mechanisms] to allow individuals to tailor processing permissions to selected elements of personally identifiable information.
PT-4 (2):
  family: PT
  name: Just-in-time Consent
  description: |
    Present [Assignment: organization-defined consent mechanisms] to individuals at [Assignment: organization-defined frequency] and in conjunction with [Assignment: organization-defined personally identifiable information processing].
PT-4 (3):
  family: PT
  name: Revocation
  description: |
    Implement [Assignment: organization-defined tools or mechanisms] for individuals to revoke consent to the processing of their personally identifiable information.
PT-5:
  family: PT
  name: Privacy Notice
  description: |
    Provide notice to individuals about the processing of personally identifiable information that:
     - a. Is available to individuals upon first interacting with an organization, and subsequently at [Assignment: organization-defined frequency];
     - b. Is clear and easy-to-understand, expressing information about personally identifiable information processing in plain language;
     - c. Identifies the authority that authorizes the processing of personally identifiable information;
     - d. Identifies the purposes for which personally identifiable information is to be processed; and
     - e. Includes [Assignment: organization-defined information].
PT-5 (1):
  family: PT
  name: Just-in-time Notice
  description: |
    Present notice of personally identifiable information processing to individuals at a time and location where the individual provides personally identifiable information or in conjunction with a data action, or [Assignment: organization-defined frequency].
PT-5 (2):
  family: PT
  name: Privacy Act Statements
  description: |
    Include Privacy Act statements on forms that collect information that will be maintained in a Privacy Act system of records, or provide Privacy Act statements on separate forms that can be retained by individuals.
PT-6:
  family: PT
  name: System of Records Notice
  description: |
    For systems that process information that will be maintained in a Privacy Act system of records:
     - a. Draft system of records notices in accordance with OMB guidance and submit new and significantly modified system of records notices to the OMB and appropriate congressional committees for advance review;
     - b. Publish system of records notices in the Federal Register; and
     - c. Keep system of records notices accurate, up-to-date, and scoped in accordance with policy.
PT-6 (1):
  family: PT
  name: Routine Uses
  description: |
    Review all routine uses published in the system of records notice at [Assignment: organization-defined frequency] to ensure continued accuracy, and to ensure that routine uses continue to be compatible with the purpose for which the information was collected.
PT-6 (2):
  family: PT
  name: Exemption Rules
  description: |
    Review all Privacy Act exemptions claimed for the system of records at [Assignment: organization-defined frequency] to ensure they remain appropriate and necessary in accordance with law, that they have been promulgated as regulations, and that they are accurately described in the system of records notice.
PT-7:
  family: PT
  name: Specific Categories of Personally Identifiable Information
  description: |
    Apply [Assignment: organization-defined processing conditions] for specific categories of personally identifiable information.
PT-7 (1):
  family: PT
  name: Social Security Numbers
  description: |
    When a system processes Social Security numbers:
     - (a) Eliminate unnecessary collection, maintenance, and use of Social Security numbers, and explore alternatives to their use as a personal identifier;
     - (b) Do not deny any individual any right, benefit, or privilege provided by law because of such individual’s refusal to disclose his or her Social Security number; and
     - (c) Inform any individual who is asked to disclose his or her Social Security number whether that disclosure is mandatory or voluntary, by what statutory or other authority such number is solicited, and what uses will be made of it.
PT-7 (2):
  family: PT
  name: First Amendment Information
  description: |
    Prohibit the processing of information describing how any individual exercises rights guaranteed by the First Amendment unless expressly authorized by statute or by the individual or unless pertinent to and within the scope of an authorized law enforcement activity.
PT-8:
  family: PT
  name: Computer Matching Requirements
  description: |
    When a system or organization processes information for the purpose of conducting a matching program:
     - a. Obtain approval from the Data Integrity Board to conduct the matching program;
     - b. Develop and enter into a computer matching agreement;
     - c. Publish a matching notice in the Federal Register;
     - d. Independently verify the information produced by the matching program before taking adverse action against an individual, if required; and
     - e. Provide individuals with notice and an opportunity to contest the findings before taking adverse action against an individual.
RA-1:
  family: RA
  name: Policy and Procedures
  description: |2
     - a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]:
       - 1. [Selection (one or more): organization-level, mission/business process-level, system-level] risk assessment policy that:
         - (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
         - (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
       - 2. Procedures to facilitate the implementation of the risk assessment policy and the associated risk assessment controls;
     - b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the risk assessment policy and procedures; and
     - c. Review and update the current risk assessment:
       - 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and
       - 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events].
RA-2:
  family: RA
  name: Security Categorization
  description: |2
     - a. Categorize the system and information it processes, stores, and transmits;
     - b. Document the security categorization results, including supporting rationale, in the security plan for the system; and
     - c. Verify that the authorizing official or authorizing official designated representative reviews and approves the security categorization decision.
RA-2 (1):
  family: RA
  name: Impact-level Prioritization
  description: |
    Conduct an impact-level prioritization of organizational systems to obtain additional granularity on system impact levels.
RA-3:
  family: RA
  name: Risk Assessment
  description: |2
     - a. Conduct a risk assessment, including:
       - 1. Identifying threats to and vulnerabilities in the system;
       - 2. Determining the likelihood and magnitude of harm from unauthorized access, use, disclosure, disruption, modification, or destruction of the system, the information it processes, stores, or transmits, and any related information; and
       - 3. Determining the likelihood and impact of adverse effects on individuals arising from the processing of personally identifiable information;
     - b. Integrate risk assessment results and risk management decisions from the organization and mission or business process perspectives with system-level risk assessments;
     - c. Document risk assessment results in [Selection: security and privacy plans, risk assessment report, [Assignment: organization-defined document]];
     - d. Review risk assessment results [Assignment: organization-defined frequency];
     - e. Disseminate risk assessment results to [Assignment: organization-defined personnel or roles]; and
     - f. Update the risk assessment [Assignment: organization-defined frequency] or when there are significant changes to the system, its environment of operation, or other conditions that may impact the security or privacy state of the system.
RA-3 (1):
  family: RA
  name: Supply Chain Risk Assessment
  description: |2
     - (a) Assess supply chain risks associated with [Assignment: organization-defined systems, system components, and system services]; and
     - (b) Update the supply chain risk assessment [Assignment: organization-defined frequency], when there are significant changes to the relevant supply chain, or when changes to the system, environments of operation, or other conditions may necessitate a change in the supply chain.
RA-3 (2):
  family: RA
  name: Use of All-source Intelligence
  description: |
    Use all-source intelligence to assist in the analysis of risk.
RA-3 (3):
  family: RA
  name: Dynamic Threat Awareness
  description: |
    Determine the current cyber threat environment on an ongoing basis using [Assignment: organization-defined means].
RA-3 (4):
  family: RA
  name: Predictive Cyber Analytics
  description: |
    Employ the following advanced automation and analytics capabilities to predict and identify risks to [Assignment: organization-defined systems or system components]: [Assignment: organization-defined advanced automation and analytics capabilities].
RA-4:
  family: RA
  name: Risk Assessment Update
  description: ""
RA-5:
  family: RA
  name: Vulnerability Monitoring and Scanning
  description: |2
     - a. Monitor and scan for vulnerabilities in the system and hosted applications [Assignment: organization-defined frequency and/or randomly in accordance with organization-defined process] and when new vulnerabilities potentially affecting the system are identified and reported;
     - b. Employ vulnerability monitoring tools and techniques that facilitate interoperability among tools and automate parts of the vulnerability management process by using standards for:
       - 1. Enumerating platforms, software flaws, and improper configurations;
       - 2. Formatting checklists and test procedures; and
       - 3. Measuring vulnerability impact;
     - c. Analyze vulnerability scan reports and results from vulnerability monitoring;
     - d. Remediate legitimate vulnerabilities [Assignment: organization-defined response times] in accordance with an organizational assessment of risk;
     - e. Share information obtained from the vulnerability monitoring process and control assessments with [Assignment: organization-defined personnel or roles] to help eliminate similar vulnerabilities in other systems; and
     - f. Employ vulnerability monitoring tools that include the capability to readily update the vulnerabilities to be scanned.
RA-5 (1):
  family: RA
  name: Update Tool Capability
  description: ""
RA-5 (2):
  family: RA
  name: Update Vulnerabilities to Be Scanned
  description: |
    Update the system vulnerabilities to be scanned [Selection (one or more): [Assignment: organization-defined frequency], prior to a new scan, when new vulnerabilities are identified and reported].
RA-5 (3):
  family: RA
  name: Breadth and Depth of Coverage
  description: |
    Define the breadth and depth of vulnerability scanning coverage.
RA-5 (4):
  family: RA
  name: Discoverable Information
  description: |
    Determine information about the system that is discoverable and take [Assignment: organization-defined corrective actions].
RA-5 (5):
  family: RA
  name: Privileged Access
  description: |
    Implement privileged access authorization to [Assignment: organization-defined system components] for [Assignment: organization-defined vulnerability scanning activities].
RA-5 (6):
  family: RA
  name: Automated Trend Analyses
  description: |
    Compare the results of multiple vulnerability scans using [Assignment: organization-defined automated mechanisms].
RA-5 (7):
  family: RA
  name: Automated Detection and Notification of Unauthorized Components
  description: ""
RA-5 (8):
  family: RA
  name: Review Historic Audit Logs
  description: |
    Review historic audit logs to determine if a vulnerability identified in a [Assignment: organization-defined system] has been previously exploited within an [Assignment: organization-defined time period].
RA-5 (9):
  family: RA
  name: Penetration Testing and Analyses
  description: ""
RA-5 (10):
  family: RA
  name: Correlate Scanning Information
  description: |
    Correlate the output from vulnerability scanning tools to determine the presence of multi-vulnerability and multi-hop attack vectors.
RA-5 (11):
  family: RA
  name: Public Disclosure Program
  description: |
    Establish a public reporting channel for receiving reports of vulnerabilities in organizational systems and system components.
RA-6:
  family: RA
  name: Technical Surveillance Countermeasures Survey
  description: |
    Employ a technical surveillance countermeasures survey at [Assignment: organization-defined locations]
                   [Selection (one or more): [Assignment: organization-defined frequency], when the following events or indicators occur, [Assignment: organization-defined events or indicators]].
RA-7:
  family: RA
  name: Risk Response
  description: |
    Respond to findings from security and privacy assessments, monitoring, and audits in accordance with organizational risk tolerance.
RA-8:
  family: RA
  name: Privacy Impact Assessments
  description: |
    Conduct privacy impact assessments for systems, programs, or other activities before:
     - a. Developing or procuring information technology that processes personally identifiable information; and
     - b. Initiating a new collection of personally identifiable information that:
       - 1. Will be processed using information technology; and
       - 2. Includes personally identifiable information permitting the physical or virtual (online) contacting of a specific individual, if identical questions have been posed to, or identical reporting requirements imposed on, ten or more individuals, other than agencies, instrumentalities, or employees of the federal government.
RA-9:
  family: RA
  name: Criticality Analysis
  description: |
    Identify critical system components and functions by performing a criticality analysis for [Assignment: organization-defined systems, system components, or system services] at [Assignment: organization-defined decision points in the system development life cycle].
RA-10:
  family: RA
  name: Threat Hunting
  description: |2
     - a. Establish and maintain a cyber threat hunting capability to:
       - 1. Search for indicators of compromise in organizational systems; and
       - 2. Detect, track, and disrupt threats that evade existing controls; and
     - b. Employ the threat hunting capability [Assignment: organization-defined frequency].
SA-1:
  family: SA
  name: Policy and Procedures
  description: |2
     - a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]:
       - 1. [Selection (one or more): organization-level, mission/business process-level, system-level] system and services acquisition policy that:
         - (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
         - (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
       - 2. Procedures to facilitate the implementation of the system and services acquisition policy and the associated system and services acquisition controls;
     - b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the system and services acquisition policy and procedures; and
     - c. Review and update the current system and services acquisition:
       - 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and
       - 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events].
SA-2:
  family: SA
  name: Allocation of Resources
  description: |2
     - a. Determine the high-level information security and privacy requirements for the system or system service in mission and business process planning;
     - b. Determine, document, and allocate the resources required to protect the system or system service as part of the organizational capital planning and investment control process; and
     - c. Establish a discrete line item for information security and privacy in organizational programming and budgeting documentation.
SA-3:
  family: SA
  name: System Development Life Cycle
  description: |2
     - a. Acquire, develop, and manage the system using [Assignment: organization-defined system development life cycle] that incorporates information security and privacy considerations;
     - b. Define and document information security and privacy roles and responsibilities throughout the system development life cycle;
     - c. Identify individuals having information security and privacy roles and responsibilities; and
     - d. Integrate the organizational information security and privacy risk management process into system development life cycle activities.
SA-3 (1):
  family: SA
  name: Manage Preproduction Environment
  description: |
    Protect system preproduction environments commensurate with risk throughout the system development life cycle for the system, system component, or system service.
SA-3 (2):
  family: SA
  name: Use of Live or Operational Data
  description: |2
     - (a) Approve, document, and control the use of live data in preproduction environments for the system, system component, or system service; and
     - (b) Protect preproduction environments for the system, system component, or system service at the same impact or classification level as any live data in use within the preproduction environments.
SA-3 (3):
  family: SA
  name: Technology Refresh
  description: |
    Plan for and implement a technology refresh schedule for the system throughout the system development life cycle.
SA-4:
  family: SA
  name: Acquisition Process
  description: |
    Include the following requirements, descriptions, and criteria, explicitly or by reference, using [Selection (one or more): standardized contract language, [Assignment: organization-defined contract language]] in the acquisition contract for the system, system component, or system service:
     - a. Security and privacy functional requirements;
     - b. Strength of mechanism requirements;
     - c. Security and privacy assurance requirements;
     - d. Controls needed to satisfy the security and privacy requirements.
     - e. Security and privacy documentation requirements;
     - f. Requirements for protecting security and privacy documentation;
     - g. Description of the system development environment and environment in which the system is intended to operate;
     - h. Allocation of responsibility or identification of parties responsible for information security, privacy, and supply chain risk management; and
     - i. Acceptance criteria.
SA-4 (1):
  family: SA
  name: Functional Properties of Controls
  description: |
    Require the developer of the system, system component, or system service to provide a description of the functional properties of the controls to be implemented.
SA-4 (2):
  family: SA
  name: Design and Implementation Information for Controls
  description: |
    Require the developer of the system, system component, or system service to provide design and implementation information for the controls that includes: [Selection (one or more): security-relevant external system interfaces, high-level design, low-level design, source code or hardware schematics, [Assignment: organization-defined design and implementation information]] at [Assignment: organization-defined level of detail].
SA-4 (3):
  family: SA
  name: Development Methods, Techniques, and Practices
  description: |
    Require the developer of the system, system component, or system service to demonstrate the use of a system development life cycle process that includes:
     - (a) [Assignment: organization-defined systems engineering methods];
     - (b) [Assignment: organization-defined Selection (one or more): systems security; privacy] engineering methods]; and
     - (c) [Assignment: organization-defined software development methods; testing, evaluation, assessment, verification, and validation methods; and quality control processes].
SA-4 (4):
  family: SA
  name: Assignment of Components to Systems
  description: ""
SA-4 (5):
  family: SA
  name: System, Component, and Service Configurations
  description: |
    Require the developer of the system, system component, or system service to:
     - (a) Deliver the system, component, or service with [Assignment: organization-defined security configurations] implemented; and
     - (b) Use the configurations as the default for any subsequent system, component, or service reinstallation or upgrade.
SA-4 (6):
  family: SA
  name: Use of Information Assurance Products
  description: |2
     - (a) Employ only government off-the-shelf or commercial off-the-shelf information assurance and information assurance-enabled information technology products that compose an NSA-approved solution to protect classified information when the networks used to transmit the information are at a lower classification level than the information being transmitted; and
     - (b) Ensure that these products have been evaluated and/or validated by NSA or in accordance with NSA-approved procedures.
SA-4 (7):
  family: SA
  name: Niap-approved Protection Profiles
  description: |2
     - (a) Limit the use of commercially provided information assurance and information assurance-enabled information technology products to those products that have been successfully evaluated against a National Information Assurance partnership (NIAP)-approved Protection Profile for a specific technology type, if such a profile exists; and
     - (b) Require, if no NIAP-approved Protection Profile exists for a specific technology type but a commercially provided information technology product relies on cryptographic functionality to enforce its security policy, that the cryptographic module is FIPS-validated or NSA-approved.
SA-4 (8):
  family: SA
  name: Continuous Monitoring Plan for Controls
  description: |
    Require the developer of the system, system component, or system service to produce a plan for continuous monitoring of control effectiveness that is consistent with the continuous monitoring program of the organization.
SA-4 (9):
  family: SA
  name: Functions, Ports, Protocols, and Services in Use
  description: |
    Require the developer of the system, system component, or system service to identify the functions, ports, protocols, and services intended for organizational use.
SA-4 (10):
  family: SA
  name: Use of Approved PIV Products
  description: |
    Employ only information technology products on the FIPS 201-approved products list for Personal Identity Verification (PIV) capability implemented within organizational systems.
SA-4 (11):
  family: SA
  name: System of Records
  description: |
    Include [Assignment: organization-defined Privacy Act requirements] in the acquisition contract for the operation of a system of records on behalf of an organization to accomplish an organizational mission or function.
SA-4 (12):
  family: SA
  name: Data Ownership
  description: |2
     - (a) Include organizational data ownership requirements in the acquisition contract; and
     - (b) Require all data to be removed from the contractor’s system and returned to the organization within [Assignment: organization-defined time frame].
SA-5:
  family: SA
  name: System Documentation
  description: |2
     - a. Obtain or develop administrator documentation for the system, system component, or system service that describes:
       - 1. Secure configuration, installation, and operation of the system, component, or service;
       - 2. Effective use and maintenance of security and privacy functions and mechanisms; and
       - 3. Known vulnerabilities regarding configuration and use of administrative or privileged functions;
     - b. Obtain or develop user documentation for the system, system component, or system service that describes:
       - 1. User-accessible security and privacy functions and mechanisms and how to effectively use those functions and mechanisms;
       - 2. Methods for user interaction, which enables individuals to use the system, component, or service in a more secure manner and protect individual privacy; and
       - 3. User responsibilities in maintaining the security of the system, component, or service and privacy of individuals;
     - c. Document attempts to obtain system, system component, or system service documentation when such documentation is either unavailable or nonexistent and take [Assignment: organization-defined actions] in response; and
     - d. Distribute documentation to [Assignment: organization-defined personnel or roles].
SA-5 (1):
  family: SA
  name: Functional Properties of Security Controls
  description: ""
SA-5 (2):
  family: SA
  name: Security-relevant External System Interfaces
  description: ""
SA-5 (3):
  family: SA
  name: High-level Design
  description: ""
SA-5 (4):
  family: SA
  name: Low-level Design
  description: ""
SA-5 (5):
  family: SA
  name: Source Code
  description: ""
SA-6:
  family: SA
  name: Software Usage Restrictions
  description: ""
SA-7:
  family: SA
  name: User-installed Software
  description: ""
SA-8:
  family: SA
  name: Security and Privacy Engineering Principles
  description: |
    Apply the following systems security and privacy engineering principles in the specification, design, development, implementation, and modification of the system and system components: [Assignment: organization-defined systems security and privacy engineering principles].
SA-8 (1):
  family: SA
  name: Clear Abstractions
  description: |
    Implement the security design principle of clear abstractions.
SA-8 (2):
  family: SA
  name: Least Common Mechanism
  description: |
    Implement the security design principle of least common mechanism in [Assignment: organization-defined systems or system components].
SA-8 (3):
  family: SA
  name: Modularity and Layering
  description: |
    Implement the security design principles of modularity and layering in [Assignment: organization-defined systems or system components].
SA-8 (4):
  family: SA
  name: Partially Ordered Dependencies
  description: |
    Implement the security design principle of partially ordered dependencies in [Assignment: organization-defined systems or system components].
SA-8 (5):
  family: SA
  name: Efficiently Mediated Access
  description: |
    Implement the security design principle of efficiently mediated access in [Assignment: organization-defined systems or system components].
SA-8 (6):
  family: SA
  name: Minimized Sharing
  description: |
    Implement the security design principle of minimized sharing in [Assignment: organization-defined systems or system components].
SA-8 (7):
  family: SA
  name: Reduced Complexity
  description: |
    Implement the security design principle of reduced complexity in [Assignment: organization-defined systems or system components].
SA-8 (8):
  family: SA
  name: Secure Evolvability
  description: |
    Implement the security design principle of secure evolvability in [Assignment: organization-defined systems or system components].
SA-8 (9):
  family: SA
  name: Trusted Components
  description: |
    Implement the security design principle of trusted components in [Assignment: organization-defined systems or system components].
SA-8 (10):
  family: SA
  name: Hierarchical Trust
  description: |
    Implement the security design principle of hierarchical trust in [Assignment: organization-defined systems or system components].
SA-8 (11):
  family: SA
  name: Inverse Modification Threshold
  description: |
    Implement the security design principle of inverse modification threshold in [Assignment: organization-defined systems or system components].
SA-8 (12):
  family: SA
  name: Hierarchical Protection
  description: |
    Implement the security design principle of hierarchical protection in [Assignment: organization-defined systems or system components].
SA-8 (13):
  family: SA
  name: Minimized Security Elements
  description: |
    Implement the security design principle of minimized security elements in [Assignment: organization-defined systems or system components].
SA-8 (14):
  family: SA
  name: Least Privilege
  description: |
    Implement the security design principle of least privilege in [Assignment: organization-defined systems or system components].
SA-8 (15):
  family: SA
  name: Predicate Permission
  description: |
    Implement the security design principle of predicate permission in [Assignment: organization-defined systems or system components].
SA-8 (16):
  family: SA
  name: Self-reliant Trustworthiness
  description: |
    Implement the security design principle of self-reliant trustworthiness in [Assignment: organization-defined systems or system components].
SA-8 (17):
  family: SA
  name: Secure Distributed Composition
  description: |
    Implement the security design principle of secure distributed composition in [Assignment: organization-defined systems or system components].
SA-8 (18):
  family: SA
  name: Trusted Communications Channels
  description: |
    Implement the security design principle of trusted communications channels in [Assignment: organization-defined systems or system components].
SA-8 (19):
  family: SA
  name: Continuous Protection
  description: |
    Implement the security design principle of continuous protection in [Assignment: organization-defined systems or system components].
SA-8 (20):
  family: SA
  name: Secure Metadata Management
  description: |
    Implement the security design principle of secure metadata management in [Assignment: organization-defined systems or system components].
SA-8 (21):
  family: SA
  name: Self-analysis
  description: |
    Implement the security design principle of self-analysis in [Assignment: organization-defined systems or system components].
SA-8 (22):
  family: SA
  name: Accountability and Traceability
  description: |
    Implement the security design principle of accountability and traceability in [Assignment: organization-defined systems or system components].
SA-8 (23):
  family: SA
  name: Secure Defaults
  description: |
    Implement the security design principle of secure defaults in [Assignment: organization-defined systems or system components].
SA-8 (24):
  family: SA
  name: Secure Failure and Recovery
  description: |
    Implement the security design principle of secure failure and recovery in [Assignment: organization-defined systems or system components].
SA-8 (25):
  family: SA
  name: Economic Security
  description: |
    Implement the security design principle of economic security in [Assignment: organization-defined systems or system components].
SA-8 (26):
  family: SA
  name: Performance Security
  description: |
    Implement the security design principle of performance security in [Assignment: organization-defined systems or system components].
SA-8 (27):
  family: SA
  name: Human Factored Security
  description: |
    Implement the security design principle of human factored security in [Assignment: organization-defined systems or system components].
SA-8 (28):
  family: SA
  name: Acceptable Security
  description: |
    Implement the security design principle of acceptable security in [Assignment: organization-defined systems or system components].
SA-8 (29):
  family: SA
  name: Repeatable and Documented Procedures
  description: |
    Implement the security design principle of repeatable and documented procedures in [Assignment: organization-defined systems or system components].
SA-8 (30):
  family: SA
  name: Procedural Rigor
  description: |
    Implement the security design principle of procedural rigor in [Assignment: organization-defined systems or system components].
SA-8 (31):
  family: SA
  name: Secure System Modification
  description: |
    Implement the security design principle of secure system modification in [Assignment: organization-defined systems or system components].
SA-8 (32):
  family: SA
  name: Sufficient Documentation
  description: |
    Implement the security design principle of sufficient documentation in [Assignment: organization-defined systems or system components].
SA-8 (33):
  family: SA
  name: Minimization
  description: |
    Implement the privacy principle of minimization using [Assignment: organization-defined processes].
SA-9:
  family: SA
  name: External System Services
  description: |2
     - a. Require that providers of external system services comply with organizational security and privacy requirements and employ the following controls: [Assignment: organization-defined controls];
     - b. Define and document organizational oversight and user roles and responsibilities with regard to external system services; and
     - c. Employ the following processes, methods, and techniques to monitor control compliance by external service providers on an ongoing basis: [Assignment: organization-defined processes, methods, and techniques].
SA-9 (1):
  family: SA
  name: Risk Assessments and Organizational Approvals
  description: |2
     - (a) Conduct an organizational assessment of risk prior to the acquisition or outsourcing of information security services; and
     - (b) Verify that the acquisition or outsourcing of dedicated information security services is approved by [Assignment: organization-defined personnel or roles].
SA-9 (2):
  family: SA
  name: Identification of Functions, Ports, Protocols, and Services
  description: |
    Require providers of the following external system services to identify the functions, ports, protocols, and other services required for the use of such services: [Assignment: organization-defined external system services].
SA-9 (3):
  family: SA
  name: Establish and Maintain Trust Relationship with Providers
  description: |
    Establish, document, and maintain trust relationships with external service providers based on the following requirements, properties, factors, or conditions: [Assignment: organization-defined security and privacy requirements, properties, factors, or conditions defining acceptable trust relationships].
SA-9 (4):
  family: SA
  name: Consistent Interests of Consumers and Providers
  description: |
    Take the following actions to verify that the interests of [Assignment: organization-defined external service providers] are consistent with and reflect organizational interests: [Assignment: organization-defined actions].
SA-9 (5):
  family: SA
  name: Processing, Storage, and Service Location
  description: |
    Restrict the location of [Selection (one or more): information processing, information or data, system services] to [Assignment: organization-defined locations] based on [Assignment: organization-defined requirements or conditions].
SA-9 (6):
  family: SA
  name: Organization-controlled Cryptographic Keys
  description: |
    Maintain exclusive control of cryptographic keys for encrypted material stored or transmitted through an external system.
SA-9 (7):
  family: SA
  name: Organization-controlled Integrity Checking
  description: |
    Provide the capability to check the integrity of information while it resides in the external system.
SA-9 (8):
  family: SA
  name: Processing and Storage Location — U.s. Jurisdiction
  description: |
    Restrict the geographic location of information processing and data storage to facilities located within in the legal jurisdictional boundary of the United States.
SA-10:
  family: SA
  name: Developer Configuration Management
  description: |
    Require the developer of the system, system component, or system service to:
     - a. Perform configuration management during system, component, or service [Selection (one or more): design, development, implementation, operation, disposal];
     - b. Document, manage, and control the integrity of changes to [Assignment: organization-defined configuration items under configuration management];
     - c. Implement only organization-approved changes to the system, component, or service;
     - d. Document approved changes to the system, component, or service and the potential security and privacy impacts of such changes; and
     - e. Track security flaws and flaw resolution within the system, component, or service and report findings to [Assignment: organization-defined personnel].
SA-10 (1):
  family: SA
  name: Software and Firmware Integrity Verification
  description: |
    Require the developer of the system, system component, or system service to enable integrity verification of software and firmware components.
SA-10 (2):
  family: SA
  name: Alternative Configuration Management
  description: |
    Provide an alternate configuration management process using organizational personnel in the absence of a dedicated developer configuration management team.
SA-10 (3):
  family: SA
  name: Hardware Integrity Verification
  description: |
    Require the developer of the system, system component, or system service to enable integrity verification of hardware components.
SA-10 (4):
  family: SA
  name: Trusted Generation
  description: |
    Require the developer of the system, system component, or system service to employ tools for comparing newly generated versions of security-relevant hardware descriptions, source code, and object code with previous versions.
SA-10 (5):
  family: SA
  name: Mapping Integrity for Version Control
  description: |
    Require the developer of the system, system component, or system service to maintain the integrity of the mapping between the master build data describing the current version of security-relevant hardware, software, and firmware and the on-site master copy of the data for the current version.
SA-10 (6):
  family: SA
  name: Trusted Distribution
  description: |
    Require the developer of the system, system component, or system service to execute procedures for ensuring that security-relevant hardware, software, and firmware updates distributed to the organization are exactly as specified by the master copies.
SA-10 (7):
  family: SA
  name: Security and Privacy Representatives
  description: |
    Require [Assignment: organization-defined security and privacy representatives] to be included in the [Assignment: organization-defined configuration change management and control process].
SA-11:
  family: SA
  name: Developer Testing and Evaluation
  description: |
    Require the developer of the system, system component, or system service, at all post-design stages of the system development life cycle, to:
     - a. Develop and implement a plan for ongoing security and privacy assessments;
     - b. Perform [Selection (one or more): unit, integration, system, regression] testing/evaluation [Assignment: organization-defined frequency] at [Assignment: organization-defined depth and coverage];
     - c. Produce evidence of the execution of the assessment plan and the results of the testing and evaluation;
     - d. Implement a verifiable flaw remediation process; and
     - e. Correct flaws identified during testing and evaluation.
SA-11 (1):
  family: SA
  name: Static Code Analysis
  description: |
    Require the developer of the system, system component, or system service to employ static code analysis tools to identify common flaws and document the results of the analysis.
SA-11 (2):
  family: SA
  name: Threat Modeling and Vulnerability Analyses
  description: |
    Require the developer of the system, system component, or system service to perform threat modeling and vulnerability analyses during development and the subsequent testing and evaluation of the system, component, or service that:
     - (a) Uses the following contextual information: [Assignment: organization-defined information concerning impact, environment of operations, known or assumed threats, and acceptable risk levels];
     - (b) Employs the following tools and methods: [Assignment: organization-defined tools and methods];
     - (c) Conducts the modeling and analyses at the following level of rigor: [Assignment: organization-defined breadth and depth of modeling and analyses]; and
     - (d) Produces evidence that meets the following acceptance criteria: [Assignment: organization-defined acceptance criteria].
SA-11 (3):
  family: SA
  name: Independent Verification of Assessment Plans and Evidence
  description: |2
     - (a) Require an independent agent satisfying [Assignment: organization-defined independence criteria] to verify the correct implementation of the developer security and privacy assessment plans and the evidence produced during testing and evaluation; and
     - (b) Verify that the independent agent is provided with sufficient information to complete the verification process or granted the authority to obtain such information.
SA-11 (4):
  family: SA
  name: Manual Code Reviews
  description: |
    Require the developer of the system, system component, or system service to perform a manual code review of [Assignment: organization-defined specific code] using the following processes, procedures, and/or techniques: [Assignment: organization-defined processes, procedures, and/or techniques].
SA-11 (5):
  family: SA
  name: Penetration Testing
  description: |
    Require the developer of the system, system component, or system service to perform penetration testing:
     - (a) At the following level of rigor: [Assignment: organization-defined breadth and depth of testing]; and
     - (b) Under the following constraints: [Assignment: organization-defined constraints].
SA-11 (6):
  family: SA
  name: Attack Surface Reviews
  description: |
    Require the developer of the system, system component, or system service to perform attack surface reviews.
SA-11 (7):
  family: SA
  name: Verify Scope of Testing and Evaluation
  description: |
    Require the developer of the system, system component, or system service to verify that the scope of testing and evaluation provides complete coverage of the required controls at the following level of rigor: [Assignment: organization-defined breadth and depth of testing and evaluation].
SA-11 (8):
  family: SA
  name: Dynamic Code Analysis
  description: |
    Require the developer of the system, system component, or system service to employ dynamic code analysis tools to identify common flaws and document the results of the analysis.
SA-11 (9):
  family: SA
  name: Interactive Application Security Testing
  description: |
    Require the developer of the system, system component, or system service to employ interactive application security testing tools to identify flaws and document the results.
SA-12:
  family: SA
  name: Supply Chain Protection
  description: ""
SA-12 (1):
  family: SA
  name: Acquisition Strategies / Tools / Methods
  description: ""
SA-12 (2):
  family: SA
  name: Supplier Reviews
  description: ""
SA-12 (3):
  family: SA
  name: Trusted Shipping and Warehousing
  description: ""
SA-12 (4):
  family: SA
  name: Diversity of Suppliers
  description: ""
SA-12 (5):
  family: SA
  name: Limitation of Harm
  description: ""
SA-12 (6):
  family: SA
  name: Minimizing Procurement Time
  description: ""
SA-12 (7):
  family: SA
  name: Assessments Prior to Selection / Acceptance / Update
  description: ""
SA-12 (8):
  family: SA
  name: Use of All-source Intelligence
  description: ""
SA-12 (9):
  family: SA
  name: Operations Security
  description: ""
SA-12 (10):
  family: SA
  name: Validate as Genuine and Not Altered
  description: ""
SA-12 (11):
  family: SA
  name: Penetration Testing / Analysis of Elements, Processes, and Actors
  description: ""
SA-12 (12):
  family: SA
  name: Inter-organizational Agreements
  description: ""
SA-12 (13):
  family: SA
  name: Critical Information System Components
  description: ""
SA-12 (14):
  family: SA
  name: Identity and Traceability
  description: ""
SA-12 (15):
  family: SA
  name: Processes to Address Weaknesses or Deficiencies
  description: ""
SA-13:
  family: SA
  name: Trustworthiness
  description: ""
SA-14:
  family: SA
  name: Criticality Analysis
  description: ""
SA-14 (1):
  family: SA
  name: Critical Components with No Viable Alternative Sourcing
  description: ""
SA-15:
  family: SA
  name: Development Process, Standards, and Tools
  description: |2
     - a. Require the developer of the system, system component, or system service to follow a documented development process that:
       - 1. Explicitly addresses security and privacy requirements;
       - 2. Identifies the standards and tools used in the development process;
       - 3. Documents the specific tool options and tool configurations used in the development process; and
       - 4. Documents, manages, and ensures the integrity of changes to the process and/or tools used in development; and
     - b. Review the development process, standards, tools, tool options, and tool configurations [Assignment: organization-defined frequency] to determine if the process, standards, tools, tool options and tool configurations selected and employed can satisfy the following security and privacy requirements: [Assignment: organization-defined security and privacy requirements].
SA-15 (1):
  family: SA
  name: Quality Metrics
  description: |
    Require the developer of the system, system component, or system service to:
     - (a) Define quality metrics at the beginning of the development process; and
     - (b) Provide evidence of meeting the quality metrics [Selection (one or more): [Assignment: organization-defined frequency], [Assignment: organization-defined program review milestones], upon delivery].
SA-15 (2):
  family: SA
  name: Security and Privacy Tracking Tools
  description: |
    Require the developer of the system, system component, or system service to select and employ security and privacy tracking tools for use during the development process.
SA-15 (3):
  family: SA
  name: Criticality Analysis
  description: |
    Require the developer of the system, system component, or system service to perform a criticality analysis:
     - (a) At the following decision points in the system development life cycle: [Assignment: organization-defined decision points in the system development life cycle]; and
     - (b) At the following level of rigor: [Assignment: organization-defined breadth and depth of criticality analysis].
SA-15 (4):
  family: SA
  name: Threat Modeling and Vulnerability Analysis
  description: ""
SA-15 (5):
  family: SA
  name: Attack Surface Reduction
  description: |
    Require the developer of the system, system component, or system service to reduce attack surfaces to [Assignment: organization-defined thresholds].
SA-15 (6):
  family: SA
  name: Continuous Improvement
  description: |
    Require the developer of the system, system component, or system service to implement an explicit process to continuously improve the development process.
SA-15 (7):
  family: SA
  name: Automated Vulnerability Analysis
  description: |
    Require the developer of the system, system component, or system service [Assignment: organization-defined frequency] to:
     - (a) Perform an automated vulnerability analysis using [Assignment: organization-defined tools];
     - (b) Determine the exploitation potential for discovered vulnerabilities;
     - (c) Determine potential risk mitigations for delivered vulnerabilities; and
     - (d) Deliver the outputs of the tools and results of the analysis to [Assignment: organization-defined personnel or roles].
SA-15 (8):
  family: SA
  name: Reuse of Threat and Vulnerability Information
  description: |
    Require the developer of the system, system component, or system service to use threat modeling and vulnerability analyses from similar systems, components, or services to inform the current development process.
SA-15 (9):
  family: SA
  name: Use of Live Data
  description: ""
SA-15 (10):
  family: SA
  name: Incident Response Plan
  description: |
    Require the developer of the system, system component, or system service to provide, implement, and test an incident response plan.
SA-15 (11):
  family: SA
  name: Archive System or Component
  description: |
    Require the developer of the system or system component to archive the system or component to be released or delivered together with the corresponding evidence supporting the final security and privacy review.
SA-15 (12):
  family: SA
  name: Minimize Personally Identifiable Information
  description: |
    Require the developer of the system or system component to minimize the use of personally identifiable information in development and test environments.
SA-16:
  family: SA
  name: Developer-provided Training
  description: |
    Require the developer of the system, system component, or system service to provide the following training on the correct use and operation of the implemented security and privacy functions, controls, and/or mechanisms: [Assignment: organization-defined training].
SA-17:
  family: SA
  name: Developer Security and Privacy Architecture and Design
  description: |
    Require the developer of the system, system component, or system service to produce a design specification and security and privacy architecture that:
     - a. Is consistent with the organization’s security and privacy architecture that is an integral part the organization’s enterprise architecture;
     - b. Accurately and completely describes the required security and privacy functionality, and the allocation of controls among physical and logical components; and
     - c. Expresses how individual security and privacy functions, mechanisms, and services work together to provide required security and privacy capabilities and a unified approach to protection.
SA-17 (1):
  family: SA
  name: Formal Policy Model
  description: |
    Require the developer of the system, system component, or system service to:
     - (a) Produce, as an integral part of the development process, a formal policy model describing the [Assignment: organization-defined elements of organizational security and privacy policy] to be enforced; and
     - (b) Prove that the formal policy model is internally consistent and sufficient to enforce the defined elements of the organizational security and privacy policy when implemented.
SA-17 (2):
  family: SA
  name: Security-relevant Components
  description: |
    Require the developer of the system, system component, or system service to:
     - (a) Define security-relevant hardware, software, and firmware; and
     - (b) Provide a rationale that the definition for security-relevant hardware, software, and firmware is complete.
SA-17 (3):
  family: SA
  name: Formal Correspondence
  description: |
    Require the developer of the system, system component, or system service to:
     - (a) Produce, as an integral part of the development process, a formal top-level specification that specifies the interfaces to security-relevant hardware, software, and firmware in terms of exceptions, error messages, and effects;
     - (b) Show via proof to the extent feasible with additional informal demonstration as necessary, that the formal top-level specification is consistent with the formal policy model;
     - (c) Show via informal demonstration, that the formal top-level specification completely covers the interfaces to security-relevant hardware, software, and firmware;
     - (d) Show that the formal top-level specification is an accurate description of the implemented security-relevant hardware, software, and firmware; and
     - (e) Describe the security-relevant hardware, software, and firmware mechanisms not addressed in the formal top-level specification but strictly internal to the security-relevant hardware, software, and firmware.
SA-17 (4):
  family: SA
  name: Informal Correspondence
  description: |
    Require the developer of the system, system component, or system service to:
     - (a) Produce, as an integral part of the development process, an informal descriptive top-level specification that specifies the interfaces to security-relevant hardware, software, and firmware in terms of exceptions, error messages, and effects;
     - (b) Show via [Selection: informal demonstration, convincing argument with formal methods as feasible] that the descriptive top-level specification is consistent with the formal policy model;
     - (c) Show via informal demonstration, that the descriptive top-level specification completely covers the interfaces to security-relevant hardware, software, and firmware;
     - (d) Show that the descriptive top-level specification is an accurate description of the interfaces to security-relevant hardware, software, and firmware; and
     - (e) Describe the security-relevant hardware, software, and firmware mechanisms not addressed in the descriptive top-level specification but strictly internal to the security-relevant hardware, software, and firmware.
SA-17 (5):
  family: SA
  name: Conceptually Simple Design
  description: |
    Require the developer of the system, system component, or system service to:
     - (a) Design and structure the security-relevant hardware, software, and firmware to use a complete, conceptually simple protection mechanism with precisely defined semantics; and
     - (b) Internally structure the security-relevant hardware, software, and firmware with specific regard for this mechanism.
SA-17 (6):
  family: SA
  name: Structure for Testing
  description: |
    Require the developer of the system, system component, or system service to structure security-relevant hardware, software, and firmware to facilitate testing.
SA-17 (7):
  family: SA
  name: Structure for Least Privilege
  description: |
    Require the developer of the system, system component, or system service to structure security-relevant hardware, software, and firmware to facilitate controlling access with least privilege.
SA-17 (8):
  family: SA
  name: Orchestration
  description: |
    Design [Assignment: organization-defined critical systems or system components] with coordinated behavior to implement the following capabilities: [Assignment: organization-defined capabilities, by system or component].
SA-17 (9):
  family: SA
  name: Design Diversity
  description: |
    Use different designs for [Assignment: organization-defined critical systems or system components] to satisfy a common set of requirements or to provide equivalent functionality.
SA-18:
  family: SA
  name: Tamper Resistance and Detection
  description: ""
SA-18 (1):
  family: SA
  name: Multiple Phases of System Development Life Cycle
  description: ""
SA-18 (2):
  family: SA
  name: Inspection of Systems or Components
  description: ""
SA-19:
  family: SA
  name: Component Authenticity
  description: ""
SA-19 (1):
  family: SA
  name: Anti-counterfeit Training
  description: ""
SA-19 (2):
  family: SA
  name: Configuration Control for Component Service and Repair
  description: ""
SA-19 (3):
  family: SA
  name: Component Disposal
  description: ""
SA-19 (4):
  family: SA
  name: Anti-counterfeit Scanning
  description: ""
SA-20:
  family: SA
  name: Customized Development of Critical Components
  description: |
    Reimplement or custom develop the following critical system components: [Assignment: organization-defined critical system components].
SA-21:
  family: SA
  name: Developer Screening
  description: |
    Require that the developer of [Assignment: organization-defined system, system component, or system service]:
     - a. Has appropriate access authorizations as determined by assigned [Assignment: organization-defined official government duties]; and
     - b. Satisfies the following additional personnel screening criteria: [Assignment: organization-defined additional personnel screening criteria].
SA-21 (1):
  family: SA
  name: Validation of Screening
  description: ""
SA-22:
  family: SA
  name: Unsupported System Components
  description: |2
     - a. Replace system components when support for the components is no longer available from the developer, vendor, or manufacturer; or
     - b. Provide the following options for alternative sources for continued support for unsupported components [Selection (one or more): in-house support, [Assignment: organization-defined support from external providers]].
SA-22 (1):
  family: SA
  name: Alternative Sources for Continued Support
  description: ""
SA-23:
  family: SA
  name: Specialization
  description: |
    Employ [Selection (one or more): design modification, augmentation, reconfiguration] on [Assignment: organization-defined systems or system components] supporting mission essential services or functions to increase the trustworthiness in those systems or components.
SC-1:
  family: SC
  name: Policy and Procedures
  description: |2
     - a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]:
       - 1. [Selection (one or more): organization-level, mission/business process-level, system-level] system and communications protection policy that:
         - (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
         - (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
       - 2. Procedures to facilitate the implementation of the system and communications protection policy and the associated system and communications protection controls;
     - b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the system and communications protection policy and procedures; and
     - c. Review and update the current system and communications protection:
       - 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and
       - 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events].
SC-2:
  family: SC
  name: Separation of System and User Functionality
  description: |
    Separate user functionality, including user interface services, from system management functionality.
SC-2 (1):
  family: SC
  name: Interfaces for Non-privileged Users
  description: |
    Prevent the presentation of system management functionality at interfaces to non-privileged users.
SC-2 (2):
  family: SC
  name: Disassociability
  description: |
    Store state information from applications and software separately.
SC-3:
  family: SC
  name: Security Function Isolation
  description: |
    Isolate security functions from nonsecurity functions.
SC-3 (1):
  family: SC
  name: Hardware Separation
  description: |
    Employ hardware separation mechanisms to implement security function isolation.
SC-3 (2):
  family: SC
  name: Access and Flow Control Functions
  description: |
    Isolate security functions enforcing access and information flow control from nonsecurity functions and from other security functions.
SC-3 (3):
  family: SC
  name: Minimize Nonsecurity Functionality
  description: |
    Minimize the number of nonsecurity functions included within the isolation boundary containing security functions.
SC-3 (4):
  family: SC
  name: Module Coupling and Cohesiveness
  description: |
    Implement security functions as largely independent modules that maximize internal cohesiveness within modules and minimize coupling between modules.
SC-3 (5):
  family: SC
  name: Layered Structures
  description: |
    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 layers.
SC-4:
  family: SC
  name: Information in Shared System Resources
  description: |
    Prevent unauthorized and unintended information transfer via shared system resources.
SC-4 (1):
  family: SC
  name: Security Levels
  description: ""
SC-4 (2):
  family: SC
  name: Multilevel or Periods Processing
  description: |
    Prevent unauthorized information transfer via shared resources in accordance with [Assignment: organization-defined procedures] when system processing explicitly switches between different information classification levels or security categories.
SC-5:
  family: SC
  name: Denial-of-service Protection
  description: |2
     - a. [Selection: Protect against, Limit] the effects of the following types of denial-of-service events: [Assignment: organization-defined types of denial-of-service events]; and
     - b. Employ the following controls to achieve the denial-of-service objective: [Assignment: organization-defined controls by type of denial-of-service event].
SC-5 (1):
  family: SC
  name: Restrict Ability to Attack Other Systems
  description: |
    Restrict the ability of individuals to launch the following denial-of-service attacks against other systems: [Assignment: organization-defined denial-of-service attacks].
SC-5 (2):
  family: SC
  name: Capacity, Bandwidth, and Redundancy
  description: |
    Manage capacity, bandwidth, or other redundancy to limit the effects of information flooding denial-of-service attacks.
SC-5 (3):
  family: SC
  name: Detection and Monitoring
  description: |2
     - (a) Employ the following monitoring tools to detect indicators of denial-of-service attacks against, or launched from, the system: [Assignment: organization-defined monitoring tools]; and
     - (b) Monitor the following system resources to determine if sufficient resources exist to prevent effective denial-of-service attacks: [Assignment: organization-defined system resources].
SC-6:
  family: SC
  name: Resource Availability
  description: |
    Protect the availability of resources by allocating [Assignment: organization-defined resources] by [Selection (one or more): priority, quota, [Assignment: organization-defined controls]].
SC-7:
  family: SC
  name: Boundary Protection
  description: |2
     - 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 system components that are [Selection: physically, logically] separated from internal organizational networks; and
     - c. Connect to external networks or systems only through managed interfaces consisting of boundary protection devices arranged in accordance with an organizational security and privacy architecture.
SC-7 (1):
  family: SC
  name: Physically Separated Subnetworks
  description: ""
SC-7 (2):
  family: SC
  name: Public Access
  description: ""
SC-7 (3):
  family: SC
  name: Access Points
  description: |
    Limit the number of external network connections to the system.
SC-7 (4):
  family: SC
  name: External Telecommunications Services
  description: |2
     - (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 the information being transmitted across each interface;
     - (d) Document each exception to the traffic flow policy with a supporting mission or business need and duration of that need;
     - (e) Review exceptions to the traffic flow policy [Assignment: organization-defined frequency] and remove exceptions that are no longer supported by an explicit mission or business need;
     - (f) Prevent unauthorized exchange of control plane traffic with external networks;
     - (g) Publish information to enable remote networks to detect unauthorized control plane traffic from internal networks; and
     - (h) Filter unauthorized control plane traffic from external networks.
SC-7 (5):
  family: SC
  name: Deny by Default — Allow by Exception
  description: |
    Deny network communications traffic by default and allow network communications traffic by exception [Selection (one or more): at managed interfaces, for [Assignment: organization-defined systems]].
SC-7 (6):
  family: SC
  name: Response to Recognized Failures
  description: ""
SC-7 (7):
  family: SC
  name: Split Tunneling for Remote Devices
  description: |
    Prevent split tunneling for remote devices connecting to organizational systems unless the split tunnel is securely provisioned using [Assignment: organization-defined safeguards].
SC-7 (8):
  family: SC
  name: Route Traffic to Authenticated Proxy Servers
  description: |
    Route [Assignment: organization-defined internal communications traffic] to [Assignment: organization-defined external networks] through authenticated proxy servers at managed interfaces.
SC-7 (9):
  family: SC
  name: Restrict Threatening Outgoing Communications Traffic
  description: |2
     - (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.
SC-7 (10):
  family: SC
  name: Prevent Exfiltration
  description: |2
     - (a) Prevent the exfiltration of information; and
     - (b) Conduct exfiltration tests [Assignment: organization-defined frequency].
SC-7 (11):
  family: SC
  name: Restrict Incoming Communications Traffic
  description: |
    Only allow incoming communications from [Assignment: organization-defined authorized sources] to be routed to [Assignment: organization-defined authorized destinations].
SC-7 (12):
  family: SC
  name: Host-based Protection
  description: |
    Implement [Assignment: organization-defined host-based boundary protection mechanisms] at [Assignment: organization-defined system components].
SC-7 (13):
  family: SC
  name: Isolation of Security Tools, Mechanisms, and Support Components
  description: |
    Isolate [Assignment: organization-defined information security tools, mechanisms, and support components] from other internal system components by implementing physically separate subnetworks with managed interfaces to other components of the system.
SC-7 (14):
  family: SC
  name: Protect Against Unauthorized Physical Connections
  description: |
    Protect against unauthorized physical connections at [Assignment: organization-defined managed interfaces].
SC-7 (15):
  family: SC
  name: Networked Privileged Accesses
  description: |
    Route networked, privileged accesses through a dedicated, managed interface for purposes of access control and auditing.
SC-7 (16):
  family: SC
  name: Prevent Discovery of System Components
  description: |
    Prevent the discovery of specific system components that represent a managed interface.
SC-7 (17):
  family: SC
  name: Automated Enforcement of Protocol Formats
  description: |
    Enforce adherence to protocol formats.
SC-7 (18):
  family: SC
  name: Fail Secure
  description: |
    Prevent systems from entering unsecure states in the event of an operational failure of a boundary protection device.
SC-7 (19):
  family: SC
  name: Block Communication from Non-organizationally Configured Hosts
  description: |
    Block inbound and outbound communications traffic between [Assignment: organization-defined communication clients] that are independently configured by end users and external service providers.
SC-7 (20):
  family: SC
  name: Dynamic Isolation and Segregation
  description: |
    Provide the capability to dynamically isolate [Assignment: organization-defined system components] from other system components.
SC-7 (21):
  family: SC
  name: Isolation of System Components
  description: |
    Employ boundary protection mechanisms to isolate [Assignment: organization-defined system components] supporting [Assignment: organization-defined missions and/or business functions].
SC-7 (22):
  family: SC
  name: Separate Subnets for Connecting to Different Security Domains
  description: |
    Implement separate network addresses to connect to systems in different security domains.
SC-7 (23):
  family: SC
  name: Disable Sender Feedback on Protocol Validation Failure
  description: |
    Disable feedback to senders on protocol format validation failure.
SC-7 (24):
  family: SC
  name: Personally Identifiable Information
  description: |
    For systems that process personally identifiable information:
     - (a) Apply the following processing rules to data elements of personally identifiable information: [Assignment: organization-defined processing rules];
     - (b) Monitor for permitted processing at the external interfaces to the system and at key internal boundaries within the system;
     - (c) Document each processing exception; and
     - (d) Review and remove exceptions that are no longer supported.
SC-7 (25):
  family: SC
  name: Unclassified National Security System Connections
  description: |
    Prohibit the direct connection of [Assignment: organization-defined unclassified national security system] to an external network without the use of [Assignment: organization-defined boundary protection device].
SC-7 (26):
  family: SC
  name: Classified National Security System Connections
  description: |
    Prohibit the direct connection of a classified national security system to an external network without the use of [Assignment: organization-defined boundary protection device].
SC-7 (27):
  family: SC
  name: Unclassified Non-national Security System Connections
  description: |
    Prohibit the direct connection of [Assignment: organization-defined unclassified non-national security system] to an external network without the use of [Assignment: organization-defined boundary protection device].
SC-7 (28):
  family: SC
  name: Connections to Public Networks
  description: |
    Prohibit the direct connection of [Assignment: organization-defined system] to a public network.
SC-7 (29):
  family: SC
  name: Separate Subnets to Isolate Functions
  description: |
    Implement [Selection: physically, logically] separate subnetworks to isolate the following critical system components and functions: [Assignment: organization-defined critical system components and functions].
SC-8:
  family: SC
  name: Transmission Confidentiality and Integrity
  description: |
    Protect the [Selection (one or more): confidentiality, integrity] of transmitted information.
SC-8 (1):
  family: SC
  name: Cryptographic Protection
  description: |
    Implement cryptographic mechanisms to [Selection (one or more): prevent unauthorized disclosure of information, detect changes to information] during transmission.
SC-8 (2):
  family: SC
  name: Pre- and Post-transmission Handling
  description: |
    Maintain the [Selection (one or more): confidentiality, integrity] of information during preparation for transmission and during reception.
SC-8 (3):
  family: SC
  name: Cryptographic Protection for Message Externals
  description: |
    Implement cryptographic mechanisms to protect message externals unless otherwise protected by [Assignment: organization-defined alternative physical controls].
SC-8 (4):
  family: SC
  name: Conceal or Randomize Communications
  description: |
    Implement cryptographic mechanisms to conceal or randomize communication patterns unless otherwise protected by [Assignment: organization-defined alternative physical controls].
SC-8 (5):
  family: SC
  name: Protected Distribution System
  description: |
    Implement [Assignment: organization-defined protected distribution system] to [Selection (one or more): prevent unauthorized disclosure of information, detect changes to information] during transmission.
SC-9:
  family: SC
  name: Transmission Confidentiality
  description: ""
SC-10:
  family: SC
  name: Network Disconnect
  description: |
    Terminate the network connection associated with a communications session at the end of the session or after [Assignment: organization-defined time period] of inactivity.
SC-11:
  family: SC
  name: Trusted Path
  description: |2
     - 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].
SC-11 (1):
  family: SC
  name: Irrefutable Communications Path
  description: |2
     - (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.
SC-12:
  family: SC
  name: Cryptographic Key Establishment and Management
  description: |
    Establish and manage cryptographic keys when cryptography is employed within the system in accordance with the following key management requirements: [Assignment: organization-defined requirements for key generation, distribution, storage, access, and destruction].
SC-12 (1):
  family: SC
  name: Availability
  description: |
    Maintain availability of information in the event of the loss of cryptographic keys by users.
SC-12 (2):
  family: SC
  name: Symmetric Keys
  description: |
    Produce, control, and distribute symmetric cryptographic keys using [Selection: NIST FIPS-validated, NSA-approved] key management technology and processes.
SC-12 (3):
  family: SC
  name: Asymmetric Keys
  description: |
    Produce, control, and distribute asymmetric cryptographic keys using [Selection: NSA-approved key management technology and processes, prepositioned keying material, DoD-approved or DoD-issued Medium Assurance PKI certificates, DoD-approved or DoD-issued Medium Hardware Assurance PKI certificates and hardware security tokens that protect the user’s private key, certificates issued in accordance with organization-defined requirements].
SC-12 (4):
  family: SC
  name: PKI Certificates
  description: ""
SC-12 (5):
  family: SC
  name: PKI Certificates / Hardware Tokens
  description: ""
SC-12 (6):
  family: SC
  name: Physical Control of Keys
  description: |
    Maintain physical control of cryptographic keys when stored information is encrypted by external service providers.
SC-13:
  family: SC
  name: Cryptographic Protection
  description: |2
     - a. Determine the [Assignment: organization-defined cryptographic uses]; and
     - b. Implement the following types of cryptography required for each specified cryptographic use: [Assignment: organization-defined types of cryptography for each specified cryptographic use].
SC-13 (1):
  family: SC
  name: Fips-validated Cryptography
  description: ""
SC-13 (2):
  family: SC
  name: Nsa-approved Cryptography
  description: ""
SC-13 (3):
  family: SC
  name: Individuals Without Formal Access Approvals
  description: ""
SC-13 (4):
  family: SC
  name: Digital Signatures
  description: ""
SC-14:
  family: SC
  name: Public Access Protections
  description: ""
SC-15:
  family: SC
  name: Collaborative Computing Devices and Applications
  description: |2
     - a. Prohibit remote activation of collaborative computing devices and applications with the following exceptions: [Assignment: organization-defined exceptions where remote activation is to be allowed]; and
     - b. Provide an explicit indication of use to users physically present at the devices.
SC-15 (1):
  family: SC
  name: Physical or Logical Disconnect
  description: |
    Provide [Selection (one or more): physical, logical] disconnect of collaborative computing devices in a manner that supports ease of use.
SC-15 (2):
  family: SC
  name: Blocking Inbound and Outbound Communications Traffic
  description: ""
SC-15 (3):
  family: SC
  name: Disabling and Removal in Secure Work Areas
  description: |
    Disable or remove collaborative computing devices and applications from [Assignment: organization-defined systems or system components] in [Assignment: organization-defined secure work areas].
SC-15 (4):
  family: SC
  name: Explicitly Indicate Current Participants
  description: |
    Provide an explicit indication of current participants in [Assignment: organization-defined online meetings and teleconferences].
SC-16:
  family: SC
  name: Transmission of Security and Privacy Attributes
  description: |
    Associate [Assignment: organization-defined security and privacy attributes] with information exchanged between systems and between system components.
SC-16 (1):
  family: SC
  name: Integrity Verification
  description: |
    Verify the integrity of transmitted security and privacy attributes.
SC-16 (2):
  family: SC
  name: Anti-spoofing Mechanisms
  description: |
    Implement anti-spoofing mechanisms to prevent adversaries from falsifying the security attributes indicating the successful application of the security process.
SC-16 (3):
  family: SC
  name: Cryptographic Binding
  description: |
    Implement [Assignment: organization-defined mechanisms or techniques] to bind security and privacy attributes to transmitted information.
SC-17:
  family: SC
  name: Public Key Infrastructure Certificates
  description: |2
     - a. Issue public key certificates under an [Assignment: organization-defined certificate policy] or obtain public key certificates from an approved service provider; and
     - b. Include only approved trust anchors in trust stores or certificate stores managed by the organization.
SC-18:
  family: SC
  name: Mobile Code
  description: |2
     - 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.
SC-18 (1):
  family: SC
  name: Identify Unacceptable Code and Take Corrective Actions
  description: |
    Identify [Assignment: organization-defined unacceptable mobile code] and take [Assignment: organization-defined corrective actions].
SC-18 (2):
  family: SC
  name: Acquisition, Development, and Use
  description: |
    Verify that the acquisition, development, and use of mobile code to be deployed in the system meets [Assignment: organization-defined mobile code requirements].
SC-18 (3):
  family: SC
  name: Prevent Downloading and Execution
  description: |
    Prevent the download and execution of [Assignment: organization-defined unacceptable mobile code].
SC-18 (4):
  family: SC
  name: Prevent Automatic Execution
  description: |
    Prevent the automatic execution of mobile code in [Assignment: organization-defined software applications] and enforce [Assignment: organization-defined actions] prior to executing the code.
SC-18 (5):
  family: SC
  name: Allow Execution Only in Confined Environments
  description: |
    Allow execution of permitted mobile code only in confined virtual machine environments.
SC-19:
  family: SC
  name: Voice Over Internet Protocol
  description: |
    <em>Technology-specific; addressed as any other technology or protocol.</em>
SC-20:
  family: SC
  name: Secure Name/address Resolution Service (authoritative Source)
  description: |2
     - 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 resolution queries; and
     - b. Provide the means to indicate the security status of child zones and (if the child supports secure resolution services) to enable verification of a chain of trust among parent and child domains, when operating as part of a distributed, hierarchical namespace.
SC-20 (1):
  family: SC
  name: Child Subspaces
  description: ""
SC-20 (2):
  family: SC
  name: Data Origin and Integrity
  description: |
    Provide data origin and integrity protection artifacts for internal name/address resolution queries.
SC-21:
  family: SC
  name: Secure Name/address Resolution Service (recursive or Caching Resolver)
  description: |
    Request and perform data origin authentication and data integrity verification on the name/address resolution responses the system receives from authoritative sources.
SC-21 (1):
  family: SC
  name: Data Origin and Integrity
  description: ""
SC-22:
  family: SC
  name: Architecture and Provisioning for Name/address Resolution Service
  description: |
    Ensure the systems that collectively provide name/address resolution service for an organization are fault-tolerant and implement internal and external role separation.
SC-23:
  family: SC
  name: Session Authenticity
  description: |
    Protect the authenticity of communications sessions.
SC-23 (1):
  family: SC
  name: Invalidate Session Identifiers at Logout
  description: |
    Invalidate session identifiers upon user logout or other session termination.
SC-23 (2):
  family: SC
  name: User-initiated Logouts and Message Displays
  description: ""
SC-23 (3):
  family: SC
  name: Unique System-generated Session Identifiers
  description: |
    Generate a unique session identifier for each session with [Assignment: organization-defined randomness requirements] and recognize only session identifiers that are system-generated.
SC-23 (4):
  family: SC
  name: Unique Session Identifiers with Randomization
  description: ""
SC-23 (5):
  family: SC
  name: Allowed Certificate Authorities
  description: |
    Only allow the use of [Assignment: organization-defined certificate authorities] for verification of the establishment of protected sessions.
SC-24:
  family: SC
  name: Fail in Known State
  description: |
    Fail to a [Assignment: organization-defined known system state] for the following failures on the indicated components while preserving [Assignment: organization-defined system state information] in failure: [Assignment: list of organization-defined types of system failures on organization-defined system components].
SC-25:
  family: SC
  name: Thin Nodes
  description: |
    Employ minimal functionality and information storage on the following system components: [Assignment: organization-defined system components].
SC-26:
  family: SC
  name: Decoys
  description: |
    Include components within organizational systems specifically designed to be the target of malicious attacks for detecting, deflecting, and analyzing such attacks.
SC-26 (1):
  family: SC
  name: Detection of Malicious Code
  description: ""
SC-27:
  family: SC
  name: Platform-independent Applications
  description: |
    Include within organizational systems the following platform independent applications: [Assignment: organization-defined platform-independent applications].
SC-28:
  family: SC
  name: Protection of Information at Rest
  description: |
    Protect the [Selection (one or more): confidentiality, integrity] of the following information at rest: [Assignment: organization-defined information at rest].
SC-28 (1):
  family: SC
  name: Cryptographic Protection
  description: |
    Implement cryptographic mechanisms to prevent unauthorized disclosure and modification of the following information at rest on [Assignment: organization-defined system components or media]: [Assignment: organization-defined information].
SC-28 (2):
  family: SC
  name: Offline Storage
  description: |
    Remove the following information from online storage and store offline in a secure location: [Assignment: organization-defined information].
SC-28 (3):
  family: SC
  name: Cryptographic Keys
  description: |
    Provide protected storage for cryptographic keys [Selection: [Assignment: organization-defined safeguards], hardware-protected key store].
SC-29:
  family: SC
  name: Heterogeneity
  description: |
    Employ a diverse set of information technologies for the following system components in the implementation of the system: [Assignment: organization-defined system components].
SC-29 (1):
  family: SC
  name: Virtualization Techniques
  description: |
    Employ virtualization techniques to support the deployment of a diversity of operating systems and applications that are changed [Assignment: organization-defined frequency].
SC-30:
  family: SC
  name: Concealment and Misdirection
  description: |
    Employ the following concealment and misdirection techniques for [Assignment: organization-defined systems] at [Assignment: organization-defined time periods] to confuse and mislead adversaries: [Assignment: organization-defined concealment and misdirection techniques].
SC-30 (1):
  family: SC
  name: Virtualization Techniques
  description: ""
SC-30 (2):
  family: SC
  name: Randomness
  description: |
    Employ [Assignment: organization-defined techniques] to introduce randomness into organizational operations and assets.
SC-30 (3):
  family: SC
  name: Change Processing and Storage Locations
  description: |
    Change the location of [Assignment: organization-defined processing and/or storage]
                      [Selection: [Assignment: organization-defined time frequency], at random time intervals]].
SC-30 (4):
  family: SC
  name: Misleading Information
  description: |
    Employ realistic, but misleading information in [Assignment: organization-defined system components] about its security state or posture.
SC-30 (5):
  family: SC
  name: Concealment of System Components
  description: |
    Employ the following techniques to hide or conceal [Assignment: organization-defined system components]: [Assignment: organization-defined techniques].
SC-31:
  family: SC
  name: Covert Channel Analysis
  description: |2
     - a. Perform a covert channel analysis to identify those aspects of communications within the system that are potential avenues for covert [Selection (one or more): storage, timing] channels; and
     - b. Estimate the maximum bandwidth of those channels.
SC-31 (1):
  family: SC
  name: Test Covert Channels for Exploitability
  description: |
    Test a subset of the identified covert channels to determine the channels that are exploitable.
SC-31 (2):
  family: SC
  name: Maximum Bandwidth
  description: |
    Reduce the maximum bandwidth for identified covert [Selection (one or more): storage, timing] channels to [Assignment: organization-defined values].
SC-31 (3):
  family: SC
  name: Measure Bandwidth in Operational Environments
  description: |
    Measure the bandwidth of [Assignment: organization-defined subset of identified covert channels] in the operational environment of the system.
SC-32:
  family: SC
  name: System Partitioning
  description: |
    Partition the system into [Assignment: organization-defined system components] residing in separate [Selection: physical, logical] domains or environments based on [Assignment: organization-defined circumstances for physical or logical separation of components].
SC-32 (1):
  family: SC
  name: Separate Physical Domains for Privileged Functions
  description: |
    Partition privileged functions into separate physical domains.
SC-33:
  family: SC
  name: Transmission Preparation Integrity
  description: ""
SC-34:
  family: SC
  name: Non-modifiable Executable Programs
  description: |
    For [Assignment: organization-defined system components], load and execute:
     - a. The operating environment from hardware-enforced, read-only media; and
     - b. The following applications from hardware-enforced, read-only media: [Assignment: organization-defined applications].
SC-34 (1):
  family: SC
  name: No Writable Storage
  description: |
    Employ [Assignment: organization-defined system components] with no writeable storage that is persistent across component restart or power on/off.
SC-34 (2):
  family: SC
  name: Integrity Protection on Read-only Media
  description: |
    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.
SC-34 (3):
  family: SC
  name: Hardware-based Protection
  description: ""
SC-35:
  family: SC
  name: External Malicious Code Identification
  description: |
    Include system components that proactively seek to identify network-based malicious code or malicious websites.
SC-36:
  family: SC
  name: Distributed Processing and Storage
  description: |
    Distribute the following processing and storage components across multiple [Selection: physical locations, logical domains]: [Assignment: organization-defined processing and storage components].
SC-36 (1):
  family: SC
  name: Polling Techniques
  description: |2
     - (a) Employ polling techniques to identify potential faults, errors, or compromises to the following processing and storage components: [Assignment: organization-defined distributed processing and storage components]; and
     - (b) Take the following actions in response to identified faults, errors, or compromises: [Assignment: organization-defined actions].
SC-36 (2):
  family: SC
  name: Synchronization
  description: |
    Synchronize the following duplicate systems or system components: [Assignment: organization-defined duplicate systems or system components].
SC-37:
  family: SC
  name: Out-of-band Channels
  description: |
    Employ the following out-of-band channels for the physical delivery or electronic transmission of [Assignment: organization-defined information, system components, or devices] to [Assignment: organization-defined individuals or systems]: [Assignment: organization-defined out-of-band channels].
SC-37 (1):
  family: SC
  name: Ensure Delivery and Transmission
  description: |
    Employ [Assignment: organization-defined controls] to ensure that only [Assignment: organization-defined individuals or systems] receive the following information, system components, or devices: [Assignment: organization-defined information, system components, or devices].
SC-38:
  family: SC
  name: Operations Security
  description: |
    Employ the following operations security controls to protect key organizational information throughout the system development life cycle: [Assignment: organization-defined operations security controls].
SC-39:
  family: SC
  name: Process Isolation
  description: |
    Maintain a separate execution domain for each executing system process.
SC-39 (1):
  family: SC
  name: Hardware Separation
  description: |
    Implement hardware separation mechanisms to facilitate process isolation.
SC-39 (2):
  family: SC
  name: Separate Execution Domain Per Thread
  description: |
    Maintain a separate execution domain for each thread in [Assignment: organization-defined multi-threaded processing].
SC-40:
  family: SC
  name: Wireless Link Protection
  description: |
    Protect external and internal [Assignment: organization-defined wireless links] from the following signal parameter attacks: [Assignment: organization-defined types of signal parameter attacks or references to sources for such attacks].
SC-40 (1):
  family: SC
  name: Electromagnetic Interference
  description: |
    Implement cryptographic mechanisms that achieve [Assignment: organization-defined level of protection] against the effects of intentional electromagnetic interference.
SC-40 (2):
  family: SC
  name: Reduce Detection Potential
  description: |
    Implement cryptographic mechanisms to reduce the detection potential of wireless links to [Assignment: organization-defined level of reduction].
SC-40 (3):
  family: SC
  name: Imitative or Manipulative Communications Deception
  description: |
    Implement cryptographic mechanisms to identify and reject wireless transmissions that are deliberate attempts to achieve imitative or manipulative communications deception based on signal parameters.
SC-40 (4):
  family: SC
  name: Signal Parameter Identification
  description: |
    Implement cryptographic mechanisms to prevent the identification of [Assignment: organization-defined wireless transmitters] by using the transmitter signal parameters.
SC-41:
  family: SC
  name: Port and I/O Device Access
  description: |
    [Selection: Physically, Logically] disable or remove [Assignment: organization-defined connection ports or input/output devices] on the following systems or system components: [Assignment: organization-defined systems or system components].
SC-42:
  family: SC
  name: Sensor Capability and Data
  description: |2
     - a. Prohibit [Selection (one or more): the use of devices possessing [Assignment: organization-defined environmental sensing capabilities] in [Assignment: organization-defined facilities, areas, or systems], the remote activation of environmental sensing capabilities on organizational systems or system components with the following exceptions, [Assignment: organization-defined exceptions where remote activation of sensors is allowed]]; and
     - b. Provide an explicit indication of sensor use to [Assignment: organization-defined class of users].
SC-42 (1):
  family: SC
  name: Reporting to Authorized Individuals or Roles
  description: |
    Verify that the system is configured so that data or information collected by the [Assignment: organization-defined sensors] is only reported to authorized individuals or roles.
SC-42 (2):
  family: SC
  name: Authorized Use
  description: |
    Employ the following measures so that data or information collected by [Assignment: organization-defined sensors] is only used for authorized purposes: [Assignment: organization-defined measures].
SC-42 (3):
  family: SC
  name: Prohibit Use of Devices
  description: ""
SC-42 (4):
  family: SC
  name: Notice of Collection
  description: |
    Employ the following measures to facilitate an individual’s awareness that personally identifiable information is being collected by [Assignment: organization-defined sensors]: [Assignment: organization-defined measures].
SC-42 (5):
  family: SC
  name: Collection Minimization
  description: |
    Employ [Assignment: organization-defined sensors] that are configured to minimize the collection of information about individuals that is not needed.
SC-43:
  family: SC
  name: Usage Restrictions
  description: |2
     - a. Establish usage restrictions and implementation guidelines for the following system components: [Assignment: organization-defined system components]; and
     - b. Authorize, monitor, and control the use of such components within the system.
SC-44:
  family: SC
  name: Detonation Chambers
  description: |
    Employ a detonation chamber capability within [Assignment: organization-defined system, system component, or location].
SC-45:
  family: SC
  name: System Time Synchronization
  description: |
    Synchronize system clocks within and between systems and system components.
SC-45 (1):
  family: SC
  name: Synchronization with Authoritative Time Source
  description: |2
     - (a) Compare the internal system clocks [Assignment: organization-defined frequency] with [Assignment: organization-defined authoritative time source]; and
     - (b) Synchronize the internal system clocks to the authoritative time source when the time difference is greater than [Assignment: organization-defined time period].
SC-45 (2):
  family: SC
  name: Secondary Authoritative Time Source
  description: |2
     - (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 secondary authoritative time source if the primary authoritative time source is unavailable.
SC-46:
  family: SC
  name: Cross Domain Policy Enforcement
  description: |
    Implement a policy enforcement mechanism [Selection: physically, logically] between the physical and/or network interfaces for the connecting security domains.
SC-47:
  family: SC
  name: Alternate Communications Paths
  description: |
    Establish [Assignment: organization-defined alternate communications paths] for system operations organizational command and control.
SC-48:
  family: SC
  name: Sensor Relocation
  description: |
    Relocate [Assignment: organization-defined sensors and monitoring capabilities] to [Assignment: organization-defined locations] under the following conditions or circumstances: [Assignment: organization-defined conditions or circumstances].
SC-48 (1):
  family: SC
  name: Dynamic Relocation of Sensors or Monitoring Capabilities
  description: |
    Dynamically relocate [Assignment: organization-defined sensors and monitoring capabilities] to [Assignment: organization-defined locations] under the following conditions or circumstances: [Assignment: organization-defined conditions or circumstances].
SC-49:
  family: SC
  name: Hardware-enforced Separation and Policy Enforcement
  description: |
    Implement hardware-enforced separation and policy enforcement mechanisms between [Assignment: organization-defined security domains].
SC-50:
  family: SC
  name: Software-enforced Separation and Policy Enforcement
  description: |
    Implement software-enforced separation and policy enforcement mechanisms between [Assignment: organization-defined security domains].
SC-51:
  family: SC
  name: Hardware-based Protection
  description: |2
     - a. Employ hardware-based, write-protect for [Assignment: organization-defined system firmware components]; and
     - b. Implement specific procedures for [Assignment: organization-defined authorized individuals] to manually disable hardware write-protect for firmware modifications and re-enable the write-protect prior to returning to operational mode.
SI-1:
  family: SI
  name: Policy and Procedures
  description: |2
     - a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]:
       - 1. [Selection (one or more): organization-level, mission/business process-level, system-level] system and information integrity policy that:
         - (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
         - (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
       - 2. Procedures to facilitate the implementation of the system and information integrity policy and the associated system and information integrity controls;
     - b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the system and information integrity policy and procedures; and
     - c. Review and update the current system and information integrity:
       - 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and
       - 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events].
SI-2:
  family: SI
  name: Flaw Remediation
  description: |2
     - a. Identify, report, and correct system flaws;
     - b. Test software and firmware updates related to flaw remediation for effectiveness and potential side effects before installation;
     - c. Install security-relevant software and firmware updates within [Assignment: organization-defined time period] of the release of the updates; and
     - d. Incorporate flaw remediation into the organizational configuration management process.
SI-2 (1):
  family: SI
  name: Central Management
  description: ""
SI-2 (2):
  family: SI
  name: Automated Flaw Remediation Status
  description: |
    Determine if system components have applicable security-relevant software and firmware updates installed using [Assignment: organization-defined automated mechanisms]
                      [Assignment: organization-defined frequency].
SI-2 (3):
  family: SI
  name: Time to Remediate Flaws and Benchmarks for Corrective Actions
  description: |2
     - (a) Measure the time between flaw identification and flaw remediation; and
     - (b) Establish the following benchmarks for taking corrective actions: [Assignment: organization-defined benchmarks].
SI-2 (4):
  family: SI
  name: Automated Patch Management Tools
  description: |
    Employ automated patch management tools to facilitate flaw remediation to the following system components: [Assignment: organization-defined system components].
SI-2 (5):
  family: SI
  name: Automatic Software and Firmware Updates
  description: |
    Install [Assignment: organization-defined security-relevant software and firmware updates] automatically to [Assignment: organization-defined system components].
SI-2 (6):
  family: SI
  name: Removal of Previous Versions of Software and Firmware
  description: |
    Remove previous versions of [Assignment: organization-defined software and firmware components] after updated versions have been installed.
SI-3:
  family: SI
  name: Malicious Code Protection
  description: |2
     - a. Implement [Selection (one or more): signature based, non-signature based] malicious code protection mechanisms at system entry and exit points to detect and eradicate malicious code;
     - b. Automatically update malicious code protection mechanisms as new releases are available in accordance with organizational configuration management policy and procedures;
     - c. Configure malicious code protection mechanisms to:
       - 1. Perform periodic scans of the system [Assignment: organization-defined frequency] and real-time scans of files from external sources at [Selection (one or more): endpoint, network entry and exit points] as the files are downloaded, opened, or executed in accordance with organizational policy; and
       - 2. [Selection (one or more): block malicious code, quarantine malicious code, take [Assignment: organization-defined action]]; and send alert to [Assignment: organization-defined personnel or roles] in response to malicious code detection; and
     - d. Address the receipt of false positives during malicious code detection and eradication and the resulting potential impact on the availability of the system.
SI-3 (1):
  family: SI
  name: Central Management
  description: ""
SI-3 (2):
  family: SI
  name: Automatic Updates
  description: ""
SI-3 (3):
  family: SI
  name: Non-privileged Users
  description: ""
SI-3 (4):
  family: SI
  name: Updates Only by Privileged Users
  description: |
    Update malicious code protection mechanisms only when directed by a privileged user.
SI-3 (5):
  family: SI
  name: Portable Storage Devices
  description: ""
SI-3 (6):
  family: SI
  name: Testing and Verification
  description: |2
     - (a) Test malicious code protection mechanisms [Assignment: organization-defined frequency] by introducing known benign code into the system; and
     - (b) Verify that the detection of the code and the associated incident reporting occur.
SI-3 (7):
  family: SI
  name: Nonsignature-based Detection
  description: ""
SI-3 (8):
  family: SI
  name: Detect Unauthorized Commands
  description: |2
     - (a) Detect the following unauthorized operating system commands through the kernel application programming interface on [Assignment: organization-defined system hardware components]: [Assignment: organization-defined unauthorized operating system commands]; and
     - (b) [Selection (one or more): issue a warning, audit the command execution, prevent the execution of the command].
SI-3 (9):
  family: SI
  name: Authenticate Remote Commands
  description: ""
SI-3 (10):
  family: SI
  name: Malicious Code Analysis
  description: |2
     - (a) Employ the following tools and techniques to analyze the characteristics and behavior of malicious code: [Assignment: organization-defined tools and techniques]; and
     - (b) Incorporate the results from malicious code analysis into organizational incident response and flaw remediation processes.
SI-4:
  family: SI
  name: System Monitoring
  description: |2
     - a. Monitor the system to detect:
       - 1. Attacks and indicators of potential attacks in accordance with the following monitoring objectives: [Assignment: organization-defined monitoring objectives]; and
       - 2. Unauthorized local, network, and remote connections;
     - b. Identify unauthorized use of the system through the following techniques and methods: [Assignment: organization-defined techniques and methods];
     - c. Invoke internal monitoring capabilities or deploy monitoring devices:
       - 1. Strategically within the system to collect organization-determined essential information; and
       - 2. At ad hoc locations within the system to track specific types of transactions of interest to the organization;
     - d. Analyze detected events and anomalies;
     - e. Adjust the level of system monitoring activity when there is a change in risk to organizational operations and assets, individuals, other organizations, or the Nation;
     - f. Obtain legal opinion regarding system monitoring activities; and
     - g. Provide [Assignment: organization-defined system monitoring information] to [Assignment: organization-defined personnel or roles]
                      [Selection (one or more): as needed, [Assignment: organization-defined frequency]].
SI-4 (1):
  family: SI
  name: System-wide Intrusion Detection System
  description: |
    Connect and configure individual intrusion detection tools into a system-wide intrusion detection system.
SI-4 (2):
  family: SI
  name: Automated Tools and Mechanisms for Real-time Analysis
  description: |
    Employ automated tools and mechanisms to support near real-time analysis of events.
SI-4 (3):
  family: SI
  name: Automated Tool and Mechanism Integration
  description: |
    Employ automated tools and mechanisms to integrate intrusion detection tools and mechanisms into access control and flow control mechanisms.
SI-4 (4):
  family: SI
  name: Inbound and Outbound Communications Traffic
  description: |2
     - (a) Determine criteria for unusual or unauthorized activities or conditions for inbound and outbound communications traffic;
     - (b) Monitor inbound and outbound communications traffic [Assignment: organization-defined frequency] for [Assignment: organization-defined unusual or unauthorized activities or conditions].
SI-4 (5):
  family: SI
  name: System-generated Alerts
  description: |
    Alert [Assignment: organization-defined personnel or roles] when the following system-generated indications of compromise or potential compromise occur: [Assignment: organization-defined compromise indicators].
SI-4 (6):
  family: SI
  name: Restrict Non-privileged Users
  description: ""
SI-4 (7):
  family: SI
  name: Automated Response to Suspicious Events
  description: |2
     - (a) Notify [Assignment: organization-defined incident response personnel (identified by name and/or by role)] of detected suspicious events; and
     - (b) Take the following actions upon detection: [Assignment: organization-defined least-disruptive actions to terminate suspicious events].
SI-4 (8):
  family: SI
  name: Protection of Monitoring Information
  description: ""
SI-4 (9):
  family: SI
  name: Testing of Monitoring Tools and Mechanisms
  description: |
    Test intrusion-monitoring tools and mechanisms [Assignment: organization-defined frequency].
SI-4 (10):
  family: SI
  name: Visibility of Encrypted Communications
  description: |
    Make provisions so that [Assignment: organization-defined encrypted communications traffic] is visible to [Assignment: organization-defined system monitoring tools and mechanisms].
SI-4 (11):
  family: SI
  name: Analyze Communications Traffic Anomalies
  description: |
    Analyze outbound communications traffic at the external interfaces to the system and selected [Assignment: organization-defined interior points within the system] to discover anomalies.
SI-4 (12):
  family: SI
  name: Automated Organization-generated Alerts
  description: |
    Alert [Assignment: organization-defined personnel or roles] using [Assignment: organization-defined automated mechanisms] when the following indications of inappropriate or unusual activities with security or privacy implications occur: [Assignment: organization-defined activities that trigger alerts].
SI-4 (13):
  family: SI
  name: Analyze Traffic and Event Patterns
  description: |2
     - (a) Analyze communications traffic and event patterns for the system;
     - (b) Develop profiles representing common traffic and event patterns; and
     - (c) Use the traffic and event profiles in tuning system-monitoring devices.
SI-4 (14):
  family: SI
  name: Wireless Intrusion Detection
  description: |
    Employ a wireless intrusion detection system to identify rogue wireless devices and to detect attack attempts and potential compromises or breaches to the system.
SI-4 (15):
  family: SI
  name: Wireless to Wireline Communications
  description: |
    Employ an intrusion detection system to monitor wireless communications traffic as the traffic passes from wireless to wireline networks.
SI-4 (16):
  family: SI
  name: Correlate Monitoring Information
  description: |
    Correlate information from monitoring tools and mechanisms employed throughout the system.
SI-4 (17):
  family: SI
  name: Integrated Situational Awareness
  description: |
    Correlate information from monitoring physical, cyber, and supply chain activities to achieve integrated, organization-wide situational awareness.
SI-4 (18):
  family: SI
  name: Analyze Traffic and Covert Exfiltration
  description: |
    Analyze outbound communications traffic at external interfaces to the system and at the following interior points to detect covert exfiltration of information: [Assignment: organization-defined interior points within the system].
SI-4 (19):
  family: SI
  name: Risk for Individuals
  description: |
    Implement [Assignment: organization-defined additional monitoring] of individuals who have been identified by [Assignment: organization-defined sources] as posing an increased level of risk.
SI-4 (20):
  family: SI
  name: Privileged Users
  description: |
    Implement the following additional monitoring of privileged users: [Assignment: organization-defined additional monitoring].
SI-4 (21):
  family: SI
  name: Probationary Periods
  description: |
    Implement the following additional monitoring of individuals during [Assignment: organization-defined probationary period]: [Assignment: organization-defined additional monitoring].
SI-4 (22):
  family: SI
  name: Unauthorized Network Services
  description: |2
     - (a) Detect network services that have not been authorized or approved by [Assignment: organization-defined authorization or approval processes]; and
     - (b) [Selection (one or more): Audit, Alert [Assignment: organization-defined personnel or roles]] when detected.
SI-4 (23):
  family: SI
  name: Host-based Devices
  description: |
    Implement the following host-based monitoring mechanisms at [Assignment: organization-defined system components]: [Assignment: organization-defined host-based monitoring mechanisms].
SI-4 (24):
  family: SI
  name: Indicators of Compromise
  description: |
    Discover, collect, and distribute to [Assignment: organization-defined personnel or roles], indicators of compromise provided by [Assignment: organization-defined sources].
SI-4 (25):
  family: SI
  name: Optimize Network Traffic Analysis
  description: |
    Provide visibility into network traffic at external and key internal system interfaces to optimize the effectiveness of monitoring devices.
SI-5:
  family: SI
  name: Security Alerts, Advisories, and Directives
  description: |2
     - a. Receive system security alerts, advisories, and directives from [Assignment: organization-defined external organizations] on an ongoing basis;
     - b. Generate internal security alerts, advisories, and directives as deemed necessary;
     - c. Disseminate security alerts, advisories, and directives to: [Selection (one or more): [Assignment: organization-defined personnel or roles], [Assignment: organization-defined elements within the organization], [Assignment: organization-defined external organizations]]; and
     - d. Implement security directives in accordance with established time frames, or notify the issuing organization of the degree of noncompliance.
SI-5 (1):
  family: SI
  name: Automated Alerts and Advisories
  description: |
    Broadcast security alert and advisory information throughout the organization using [Assignment: organization-defined automated mechanisms].
SI-6:
  family: SI
  name: Security and Privacy Function Verification
  description: |2
     - a. Verify the correct operation of [Assignment: organization-defined security and privacy functions];
     - b. Perform the verification of the functions specified in SI-6a [Selection (one or more): [Assignment: organization-defined system transitional states], upon command by user with appropriate privilege, [Assignment: organization-defined frequency]];
     - c. Alert [Assignment: organization-defined personnel or roles] to failed security and privacy verification tests; and
     - d. [Selection (one or more): Shut the system down, Restart the system, [Assignment: organization-defined alternative action(s)]] when anomalies are discovered.
SI-6 (1):
  family: SI
  name: Notification of Failed Security Tests
  description: ""
SI-6 (2):
  family: SI
  name: Automation Support for Distributed Testing
  description: |
    Implement automated mechanisms to support the management of distributed security and privacy function testing.
SI-6 (3):
  family: SI
  name: Report Verification Results
  description: |
    Report the results of security and privacy function verification to [Assignment: organization-defined personnel or roles].
SI-7:
  family: SI
  name: Software, Firmware, and Information Integrity
  description: |2
     - a. Employ integrity verification tools to detect unauthorized changes to the following software, firmware, and information: [Assignment: organization-defined software, firmware, and information]; and
     - b. Take the following actions when unauthorized changes to the software, firmware, and information are detected: [Assignment: organization-defined actions].
SI-7 (1):
  family: SI
  name: Integrity Checks
  description: |
    Perform an integrity check of [Assignment: organization-defined software, firmware, and information]
                      [Selection (one or more): at startup, at [Assignment: organization-defined transitional states or security-relevant events], [Assignment: organization-defined frequency]].
SI-7 (2):
  family: SI
  name: Automated Notifications of Integrity Violations
  description: |
    Employ automated tools that provide notification to [Assignment: organization-defined personnel or roles] upon discovering discrepancies during integrity verification.
SI-7 (3):
  family: SI
  name: Centrally Managed Integrity Tools
  description: |
    Employ centrally managed integrity verification tools.
SI-7 (4):
  family: SI
  name: Tamper-evident Packaging
  description: ""
SI-7 (5):
  family: SI
  name: Automated Response to Integrity Violations
  description: |
    Automatically [Selection (one or more): shut the system down, restart the system, implement [Assignment: organization-defined controls]] when integrity violations are discovered.
SI-7 (6):
  family: SI
  name: Cryptographic Protection
  description: |
    Implement cryptographic mechanisms to detect unauthorized changes to software, firmware, and information.
SI-7 (7):
  family: SI
  name: Integration of Detection and Response
  description: |
    Incorporate the detection of the following unauthorized changes into the organizational incident response capability: [Assignment: organization-defined security-relevant changes to the system].
SI-7 (8):
  family: SI
  name: Auditing Capability for Significant Events
  description: |
    Upon detection of a potential integrity violation, provide the capability to audit the event and initiate the following actions: [Selection (one or more): generate an audit record, alert current user, alert [Assignment: organization-defined personnel or roles], [Assignment: organization-defined other actions]].
SI-7 (9):
  family: SI
  name: Verify Boot Process
  description: |
    Verify the integrity of the boot process of the following system components: [Assignment: organization-defined system components].
SI-7 (10):
  family: SI
  name: Protection of Boot Firmware
  description: |
    Implement the following mechanisms to protect the integrity of boot firmware in [Assignment: organization-defined system components]: [Assignment: organization-defined mechanisms].
SI-7 (11):
  family: SI
  name: Confined Environments with Limited Privileges
  description: ""
SI-7 (12):
  family: SI
  name: Integrity Verification
  description: |
    Require that the integrity of the following user-installed software be verified prior to execution: [Assignment: organization-defined user-installed software].
SI-7 (13):
  family: SI
  name: Code Execution in Protected Environments
  description: ""
SI-7 (14):
  family: SI
  name: Binary or Machine Executable Code
  description: ""
SI-7 (15):
  family: SI
  name: Code Authentication
  description: |
    Implement cryptographic mechanisms to authenticate the following software or firmware components prior to installation: [Assignment: organization-defined software or firmware components].
SI-7 (16):
  family: SI
  name: Time Limit on Process Execution Without Supervision
  description: |
    Prohibit processes from executing without supervision for more than [Assignment: organization-defined time period].
SI-7 (17):
  family: SI
  name: Runtime Application Self-protection
  description: |
    Implement [Assignment: organization-defined controls] for application self-protection at runtime.
SI-8:
  family: SI
  name: Spam Protection
  description: |2
     - a. Employ spam protection mechanisms at system entry and exit points to detect and act on unsolicited messages; and
     - b. Update spam protection mechanisms when new releases are available in accordance with organizational configuration management policy and procedures.
SI-8 (1):
  family: SI
  name: Central Management
  description: ""
SI-8 (2):
  family: SI
  name: Automatic Updates
  description: |
    Automatically update spam protection mechanisms [Assignment: organization-defined frequency].
SI-8 (3):
  family: SI
  name: Continuous Learning Capability
  description: |
    Implement spam protection mechanisms with a learning capability to more effectively identify legitimate communications traffic.
SI-9:
  family: SI
  name: Information Input Restrictions
  description: ""
SI-10:
  family: SI
  name: Information Input Validation
  description: |
    Check the validity of the following information inputs: [Assignment: organization-defined information inputs to the system].
SI-10 (1):
  family: SI
  name: Manual Override Capability
  description: |2
     - (a) Provide a manual override capability for input validation of the following information inputs: [Assignment: organization-defined inputs defined in the base control (SI-10)];
     - (b) Restrict the use of the manual override capability to only [Assignment: organization-defined authorized individuals]; and
     - (c) Audit the use of the manual override capability.
SI-10 (2):
  family: SI
  name: Review and Resolve Errors
  description: |
    Review and resolve input validation errors within [Assignment: organization-defined time period].
SI-10 (3):
  family: SI
  name: Predictable Behavior
  description: |
    Verify that the system behaves in a predictable and documented manner when invalid inputs are received.
SI-10 (4):
  family: SI
  name: Timing Interactions
  description: |
    Account for timing interactions among system components in determining appropriate responses for invalid inputs.
SI-10 (5):
  family: SI
  name: Restrict Inputs to Trusted Sources and Approved Formats
  description: |
    Restrict the use of information inputs to [Assignment: organization-defined trusted sources] and/or [Assignment: organization-defined formats].
SI-10 (6):
  family: SI
  name: Injection Prevention
  description: |
    Prevent untrusted data injections.
SI-11:
  family: SI
  name: Error Handling
  description: |2
     - a. Generate error messages that provide information necessary for corrective actions without revealing information that could be exploited; and
     - b. Reveal error messages only to [Assignment: organization-defined personnel or roles].
SI-12:
  family: SI
  name: Information Management and Retention
  description: |
    Manage and retain information within the system and information output from the system in accordance with applicable laws, executive orders, directives, regulations, policies, standards, guidelines and operational requirements.
SI-12 (1):
  family: SI
  name: Limit Personally Identifiable Information Elements
  description: |
    Limit personally identifiable information being processed in the information life cycle to the following elements of PII: [Assignment: organization-defined elements of personally identifiable information].
SI-12 (2):
  family: SI
  name: Minimize Personally Identifiable Information in Testing, Training, and Research
  description: |
    Use the following techniques to minimize the use of personally identifiable information for research, testing, or training: [Assignment: organization-defined techniques].
SI-12 (3):
  family: SI
  name: Information Disposal
  description: |
    Use the following techniques to dispose of, destroy, or erase information following the retention period: [Assignment: organization-defined techniques].
SI-13:
  family: SI
  name: Predictable Failure Prevention
  description: |2
     - a. Determine mean time to failure (MTTF) for the following system components in specific environments of operation: [Assignment: organization-defined system components]; and
     - b. Provide substitute system components and a means to exchange active and standby components in accordance with the following criteria: [Assignment: organization-defined MTTF substitution criteria].
SI-13 (1):
  family: SI
  name: Transferring Component Responsibilities
  description: |
    Take system components out of service by transferring component responsibilities to substitute components no later than [Assignment: organization-defined fraction or percentage] of mean time to failure.
SI-13 (2):
  family: SI
  name: Time Limit on Process Execution Without Supervision
  description: ""
SI-13 (3):
  family: SI
  name: Manual Transfer Between Components
  description: |
    Manually initiate transfers between active and standby system components when the use of the active component reaches [Assignment: organization-defined percentage] of the mean time to failure.
SI-13 (4):
  family: SI
  name: Standby Component Installation and Notification
  description: |
    If system component failures are detected:
     - (a) Ensure that the standby components are successfully and transparently installed within [Assignment: organization-defined time period]; and
     - (b) [Selection (one or more): Activate [Assignment: organization-defined alarm], Automatically shut down the system, [Assignment: organization-defined action]].
SI-13 (5):
  family: SI
  name: Failover Capability
  description: |
    Provide [Selection: real-time, near real-time]
                      [Assignment: organization-defined failover capability] for the system.
SI-14:
  family: SI
  name: Non-persistence
  description: |
    Implement non-persistent [Assignment: organization-defined system components and services] that are initiated in a known state and terminated [Selection (one or more): upon end of session of use, periodically at [Assignment: organization-defined frequency]].
SI-14 (1):
  family: SI
  name: Refresh from Trusted Sources
  description: |
    Obtain software and data employed during system component and service refreshes from the following trusted sources: [Assignment: organization-defined trusted sources].
SI-14 (2):
  family: SI
  name: Non-persistent Information
  description: |2
     - (a) [Selection: Refresh [Assignment: organization-defined information]
                         [Assignment: organization-defined frequency], Generate [Assignment: organization-defined information] on demand]; and
     - (b) Delete information when no longer needed.
SI-14 (3):
  family: SI
  name: Non-persistent Connectivity
  description: |
    Establish connections to the system on demand and terminate connections after [Selection: completion of a request, a period of non-use].
SI-15:
  family: SI
  name: Information Output Filtering
  description: |
    Validate information output from the following software programs and/or applications to ensure that the information is consistent with the expected content: [Assignment: organization-defined software programs and/or applications].
SI-16:
  family: SI
  name: Memory Protection
  description: |
    Implement the following controls to protect the system memory from unauthorized code execution: [Assignment: organization-defined controls].
SI-17:
  family: SI
  name: Fail-safe Procedures
  description: |
    Implement the indicated fail-safe procedures when the indicated failures occur: [Assignment: organization-defined list of failure conditions and associated fail-safe procedures].
SI-18:
  family: SI
  name: Personally Identifiable Information Quality Operations
  description: |2
     - a. Check the accuracy, relevance, timeliness, and completeness of personally identifiable information across the information life cycle [Assignment: organization-defined frequency]; and
     - b. Correct or delete inaccurate or outdated personally identifiable information.
SI-18 (1):
  family: SI
  name: Automation Support
  description: |
    Correct or delete personally identifiable information that is inaccurate or outdated, incorrectly determined regarding impact, or incorrectly de-identified using [Assignment: organization-defined automated mechanisms].
SI-18 (2):
  family: SI
  name: Data Tags
  description: |
    Employ data tags to automate the correction or deletion of personally identifiable information across the information life cycle within organizational systems.
SI-18 (3):
  family: SI
  name: Collection
  description: |
    Collect personally identifiable information directly from the individual.
SI-18 (4):
  family: SI
  name: Individual Requests
  description: |
    Correct or delete personally identifiable information upon request by individuals or their designated representatives.
SI-18 (5):
  family: SI
  name: Notice of Correction or Deletion
  description: |
    Notify [Assignment: organization-defined recipients of personally identifiable information] and individuals that the personally identifiable information has been corrected or deleted.
SI-19:
  family: SI
  name: De-identification
  description: |2
     - a. Remove the following elements of personally identifiable information from datasets: [Assignment: organization-defined elements of personally identifiable information]; and
     - b. Evaluate [Assignment: organization-defined frequency] for effectiveness of de-identification.
SI-19 (1):
  family: SI
  name: Collection
  description: |
    De-identify the dataset upon collection by not collecting personally identifiable information.
SI-19 (2):
  family: SI
  name: Archiving
  description: |
    Prohibit archiving of personally identifiable information elements if those elements in a dataset will not be needed after the dataset is archived.
SI-19 (3):
  family: SI
  name: Release
  description: |
    Remove personally identifiable information elements from a dataset prior to its release if those elements in the dataset do not need to be part of the data release.
SI-19 (4):
  family: SI
  name: Removal, Masking, Encryption, Hashing, or Replacement of Direct Identifiers
  description: |
    Remove, mask, encrypt, hash, or replace direct identifiers in a dataset.
SI-19 (5):
  family: SI
  name: Statistical Disclosure Control
  description: |
    Manipulate numerical data, contingency tables, and statistical findings so that no individual or organization is identifiable in the results of the analysis.
SI-19 (6):
  family: SI
  name: Differential Privacy
  description: |
    Prevent disclosure of personally identifiable information by adding non-deterministic noise to the results of mathematical operations before the results are reported.
SI-19 (7):
  family: SI
  name: Validated Algorithms and Software
  description: |
    Perform de-identification using validated algorithms and software that is validated to implement the algorithms.
SI-19 (8):
  family: SI
  name: Motivated Intruder
  description: |
    Perform a motivated intruder test on the de-identified dataset to determine if the identified data remains or if the de-identified data can be re-identified.
SI-20:
  family: SI
  name: Tainting
  description: |
    Embed data or capabilities in the following systems or system components to determine if organizational data has been exfiltrated or improperly removed from the organization: [Assignment: organization-defined systems or system components].
SI-21:
  family: SI
  name: Information Refresh
  description: |
    Refresh [Assignment: organization-defined information] at [Assignment: organization-defined frequencies] or generate the information on demand and delete the information when no longer needed.
SI-22:
  family: SI
  name: Information Diversity
  description: |2
     - a. Identify the following alternative sources of information for [Assignment: organization-defined essential functions and services]: [Assignment: organization-defined alternative information sources]; and
     - b. Use an alternative information source for the execution of essential functions or services on [Assignment: organization-defined systems or system components] when the primary source of information is corrupted or unavailable.
SI-23:
  family: SI
  name: Information Fragmentation
  description: |
    Based on [Assignment: organization-defined circumstances]:
     - a. Fragment the following information: [Assignment: organization-defined information]; and
     - b. Distribute the fragmented information across the following systems or system components: [Assignment: Assignment organization-defined systems or system components].
SR-1:
  family: SR
  name: Policy and Procedures
  description: |2
     - a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]:
       - 1. [Selection (one or more): organization-level, mission/business process-level, system-level] supply chain risk management policy that:
         - (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
         - (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
       - 2. Procedures to facilitate the implementation of the supply chain risk management policy and the associated supply chain risk management controls;
     - b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the supply chain risk management policy and procedures; and
     - c. Review and update the current supply chain risk management:
       - 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and
       - 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events].
SR-2:
  family: SR
  name: Supply Chain Risk Management Plan
  description: |2
     - a. Develop a plan for managing supply chain risks associated with the research and development, design, manufacturing, acquisition, delivery, integration, operations and maintenance, and disposal of the following systems, system components or system services: [Assignment: organization-defined systems, system components, or system services];
     - b. Review and update the supply chain risk management plan [Assignment: organization-defined frequency] or as required, to address threat, organizational or environmental changes; and
     - c. Protect the supply chain risk management plan from unauthorized disclosure and modification.
SR-2 (1):
  family: SR
  name: Establish Scrm Team
  description: |
    Establish a supply chain risk management team consisting of [Assignment: organization-defined personnel, roles, and responsibilities] to lead and support the following SCRM activities: [Assignment: organization-defined supply chain risk management activities].
SR-3:
  family: SR
  name: Supply Chain Controls and Processes
  description: |2
     - a. Establish a process or processes to identify and address weaknesses or deficiencies in the supply chain elements and processes of [Assignment: organization-defined system or system component] in coordination with [Assignment: organization-defined supply chain personnel];
     - b. Employ the following controls to protect against supply chain risks to the system, system component, or system service and to limit the harm or consequences from supply chain-related events: [Assignment: organization-defined supply chain controls]; and
     - c. Document the selected and implemented supply chain processes and controls in [Selection: security and privacy plans, supply chain risk management plan, [Assignment: organization-defined document]].
SR-3 (1):
  family: SR
  name: Diverse Supply Base
  description: |
    Employ a diverse set of sources for the following system components and services:  [Assignment: organization-defined system components and services].
SR-3 (2):
  family: SR
  name: Limitation of Harm
  description: |
    Employ the following controls to limit harm from potential adversaries identifying and targeting the organizational supply chain: [Assignment: organization-defined controls].
SR-3 (3):
  family: SR
  name: Sub-tier Flow Down
  description: |
    Ensure that the controls included in the contracts of prime contractors are also included in the contracts of subcontractors.
SR-4:
  family: SR
  name: Provenance
  description: |
    Document, monitor, and maintain valid provenance of the following systems, system components, and associated data: [Assignment: organization-defined systems, system components, and associated data].
SR-4 (1):
  family: SR
  name: Identity
  description: |
    Establish and maintain unique identification of the following supply chain elements, processes, and personnel associated with the identified system and critical system components: [Assignment: organization-defined supply chain elements, processes, and personnel associated with organization-defined systems and critical system components].
SR-4 (2):
  family: SR
  name: Track and Trace
  description: |
    Establish and maintain unique identification of the following systems and critical system components for tracking through the supply chain: [Assignment: organization-defined systems and critical system components].
SR-4 (3):
  family: SR
  name: Validate as Genuine and Not Altered
  description: |
    Employ the following controls to validate that the system or system component received is genuine and has not been altered: [Assignment: organization-defined controls].
SR-4 (4):
  family: SR
  name: Supply Chain Integrity — Pedigree
  description: |
    Employ [Assignment: organization-defined controls] and conduct [Assignment: organization-defined analysis] to ensure the integrity of the system and system components by validating the internal composition and provenance of critical or mission-essential technologies, products, and services.
SR-5:
  family: SR
  name: Acquisition Strategies, Tools, and Methods
  description: |
    Employ the following acquisition strategies, contract tools, and procurement methods to protect against, identify, and mitigate supply chain risks: [Assignment: organization-defined acquisition strategies, contract tools, and procurement methods].
SR-5 (1):
  family: SR
  name: Adequate Supply
  description: |
    Employ the following controls to ensure an adequate supply of [Assignment: organization-defined critical system components]: [Assignment: organization-defined controls].
SR-5 (2):
  family: SR
  name: Assessments Prior to Selection, Acceptance, Modification, or Update
  description: |
    Assess the system, system component, or system service prior to selection, acceptance, modification, or update.
SR-6:
  family: SR
  name: Supplier Assessments and Reviews
  description: |
    Assess and review the supply chain-related risks associated with suppliers or contractors and the system, system component, or system service they provide [Assignment: organization-defined frequency].
SR-6 (1):
  family: SR
  name: Testing and Analysis
  description: |
    Employ [Selection (one or more): organizational analysis, independent third-party analysis, organizational testing, independent third-party testing] of the following supply chain elements, processes, and actors associated with the system, system component, or system service: [Assignment: organization-defined supply chain elements, processes, and actors].
SR-7:
  family: SR
  name: Supply Chain Operations Security
  description: |
    Employ the following Operations Security (OPSEC) controls to protect supply chain-related information for the system, system component, or system service: [Assignment: organization-defined Operations Security (OPSEC) controls].
SR-8:
  family: SR
  name: Notification Agreements
  description: |
    Establish agreements and procedures with entities involved in the supply chain for the system, system component, or system service for the [Selection (one or more): notification of supply chain compromises, results of assessments or audits, [Assignment: organization-defined information]].
SR-9:
  family: SR
  name: Tamper Resistance and Detection
  description: |
    Implement a tamper protection program for the system, system component, or system service.
SR-9 (1):
  family: SR
  name: Multiple Stages of System Development Life Cycle
  description: |
    Employ anti-tamper technologies, tools, and techniques throughout the system development life cycle.
SR-10:
  family: SR
  name: Inspection of Systems or Components
  description: |
    Inspect the following systems or system components [Selection (one or more): at random, at [Assignment: organization-defined frequency], upon [Assignment: organization-defined indications of need for inspection]] to detect tampering: [Assignment: organization-defined systems or system components].
SR-11:
  family: SR
  name: Component Authenticity
  description: |2
     - a. Develop and implement anti-counterfeit policy and procedures that include the means to detect and prevent counterfeit components from entering the system; and
     - b. Report counterfeit system components to [Selection (one or more): source of counterfeit component, [Assignment: organization-defined external reporting organizations], [Assignment: organization-defined personnel or roles]].
SR-11 (1):
  family: SR
  name: Anti-counterfeit Training
  description: |
    Train [Assignment: organization-defined personnel or roles] to detect counterfeit system components (including hardware, software, and firmware).
SR-11 (2):
  family: SR
  name: Configuration Control for Component Service and Repair
  description: |
    Maintain configuration control over the following system components awaiting service or repair and serviced or repaired components awaiting return to service: [Assignment: organization-defined system components].
SR-11 (3):
  family: SR
  name: Anti-counterfeit Scanning
  description: |
    Scan for counterfeit system components [Assignment: organization-defined frequency].
SR-12:
  family: SR
  name: Component Disposal
  description: |
    Dispose of [Assignment: organization-defined data, documentation, tools, or system components] using the following techniques and methods: [Assignment: organization-defined techniques and methods].