diff --git "a/sec_attestation/NIST800-53Rev5.json" "b/sec_attestation/NIST800-53Rev5.json" new file mode 100644--- /dev/null +++ "b/sec_attestation/NIST800-53Rev5.json" @@ -0,0 +1 @@ +{"catalog":{"description":"NIST 800-53 Revision 5 Security & Privacy Controls for Information Systems and Organizations. Originally published in September of 2020 (See DOI https://doi.org/10.6028/NIST.SP.800-53r5). This catalog is derived from the machine-readable version last modified April 14, 2023 at https://github.com/usnistgov/oscal-content/tree/main/src/nist.gov/SP800-53/rev5/xml","datePublished":"2020-09-01T04:00:00","uuid":"ade1c997-bd88-4a59-b586-06421f0ad6d2","regulationDateModified":"","abstract":"This publication provides a catalog of security and privacy controls for information systems and organizations to protect organizational operations and assets, individuals, other organizations, and the Nation from a diverse set of threats and risks, including hostile attacks, human errors, natural disasters, structural failures, foreign intelligence entities, and privacy risks. The controls are flexible and customizable and implemented as part of an organization-wide process to manage risk. The controls address diverse requirements derived from mission and business needs, laws, executive orders, directives, regulations, policies, standards, and guidelines. Finally, the consolidated control catalog addresses security and privacy from a functionality perspective (i.e., the strength of functions and mechanisms provided by the controls) and from an assurance perspective (i.e., the measure of confidence in the security or privacy capability provided by the controls). Addressing functionality and assurance helps to ensure that information technology products and the systems that rely on those products are sufficiently trustworthy.","url":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","defaultName":"NIST800-53Rev5","title":"Electronic Version of NIST SP 800-53 Rev 5 Controls and SP 800-53A Rev 5 Assessment Procedures","lastRevisionDate":"2024-06-26T04:00:00","regulationDatePublished":"2020-09-01T04:00:00","keywords":" assurance; availability; computer security; confidentiality; control; cybersecurity; FISMA; information security; information system; integrity; personally identifiable information; Privacy Act; privacy controls; privacy functions; privacy requirements; Risk Management Framework; security controls; security functions; security requirements; system; system security ","requireUniqueControlId":true,"securityControls":[{"objectives":[{"objectiveType":"","otherId":"ac-1_obj.a-1","name":"AC-01a.[01]","description":"An access control policy is developed and documented;","uuid":"a3e9b818-d693-4a39-a500-9dfec462157f"},{"objectiveType":"","otherId":"ac-1_obj.a-2","name":"AC-01a.[02]","description":"The access control policy is disseminated to {{ insert: param, ac-01_odp.01 }};","uuid":"58a3211e-623b-473a-af34-8a97759370a2"},{"objectiveType":"","otherId":"ac-1_obj.a-3","name":"AC-01a.[03]","description":"Access control procedures to facilitate the implementation of the access control policy and associated controls are developed and documented;","uuid":"d9eeb9e2-241e-4057-aafc-b82af33b535c"},{"objectiveType":"","otherId":"ac-1_obj.a-4","name":"AC-01a.[04]","description":"The access control procedures are disseminated to {{ insert: param, ac-01_odp.02 }};","uuid":"46227259-ead4-443d-a522-172f2fcc3240"},{"objectiveType":"","otherId":"ac-1_obj.a.1.a-1","name":"AC-01a.01(a)[01]","description":"The {{ insert: param, ac-01_odp.03 }} access control policy addresses purpose;","uuid":"b3c67c75-28c5-4d96-9be1-09d4cd449cf5"},{"objectiveType":"","otherId":"ac-1_obj.a.1.a-2","name":"AC-01a.01(a)[02]","description":"The {{ insert: param, ac-01_odp.03 }} access control policy addresses scope;","uuid":"cf3cddce-8c94-46c5-9e83-b921032462de"},{"objectiveType":"","otherId":"ac-1_obj.a.1.a-3","name":"AC-01a.01(a)[03]","description":"The {{ insert: param, ac-01_odp.03 }} access control policy addresses roles;","uuid":"8489b811-3b5e-426a-ad13-2d4ed9aee7fd"},{"objectiveType":"","otherId":"ac-1_obj.a.1.a-4","name":"AC-01a.01(a)[04]","description":"The {{ insert: param, ac-01_odp.03 }} access control policy addresses responsibilities;","uuid":"4fdca2e0-f63a-4504-8bf0-575d638d3d3c"},{"objectiveType":"","otherId":"ac-1_obj.a.1.a-5","name":"AC-01a.01(a)[05]","description":"The {{ insert: param, ac-01_odp.03 }} access control policy addresses management commitment;","uuid":"8e925f0a-1f4c-4242-8e4e-a622d862215a"},{"objectiveType":"","otherId":"ac-1_obj.a.1.a-6","name":"AC-01a.01(a)[06]","description":"The {{ insert: param, ac-01_odp.03 }} access control policy addresses coordination among organizational entities;","uuid":"2c2bd7d8-ac1a-44b5-935b-54f1ddb4a69e"},{"objectiveType":"","otherId":"ac-1_obj.a.1.a-7","name":"AC-01a.01(a)[07]","description":"The {{ insert: param, ac-01_odp.03 }} access control policy addresses compliance;","uuid":"b0307a85-f1ae-4006-a88c-2819dd4f3981"},{"objectiveType":"","otherId":"ac-1_obj.a.1.b","name":"AC-01a.01(b)","description":"The {{ insert: param, ac-01_odp.03 }} access control policy is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines;","uuid":"09751f0e-68c3-4d05-8b50-c13ddc93fc3c"},{"objectiveType":"","otherId":"ac-1_obj.b","name":"AC-01b.","description":"The {{ insert: param, ac-01_odp.04 }} is designated to manage the development, documentation, and dissemination of the access control policy and procedures;","uuid":"85de562c-5fb8-4d27-8886-6f39fb4f5102"},{"objectiveType":"","otherId":"ac-1_obj.c.1-1","name":"AC-01c.01[01]","description":"The current access control policy is reviewed and updated {{ insert: param, ac-01_odp.05 }};","uuid":"102cfc6f-dd07-49b0-ae97-df2f0ca502f0"},{"objectiveType":"","otherId":"ac-1_obj.c.1-2","name":"AC-01c.01[02]","description":"The current access control policy is reviewed and updated following {{ insert: param, ac-01_odp.06 }};","uuid":"8b59a140-ab82-43e1-b51b-ea06da742801"},{"objectiveType":"","otherId":"ac-1_obj.c.2-1","name":"AC-01c.02[01]","description":"The current access control procedures are reviewed and updated {{ insert: param, ac-01_odp.07 }};","uuid":"5b907dfe-fa06-4ce9-a610-68558e3262cd"},{"objectiveType":"","otherId":"ac-1_obj.c.2-2","name":"AC-01c.02[02]","description":"The current access control procedures are reviewed and updated following {{ insert: param, ac-01_odp.08 }}.","uuid":"2806f1f8-c437-4687-a130-c73b2b915ab8"}],"description":"
Access control policy and procedures address the controls in the AC family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of access control policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies reflecting the complex nature of organizations. Procedures can be established for security and privacy programs, for mission or business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to access control policy and procedures include assessment or audit findings, security incidents or breaches, or changes in laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure.
","uuid":"81c97dc9-f42f-451f-9319-f1ad1c8149af","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"a98b7c79-94f4-46ef-b0f8-ef956aefd6bd","text":"organization-defined personnel or roles","parameterId":"ac-1_prm_1","default":" [Assignment: organization-defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"a8890cd2-6ea8-43f8-a067-51d997f82bdd","text":"personnel or roles","parameterId":"ac-01_odp.01","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"00f8afb2-2e73-46b0-9306-5c9490e169e0","text":"personnel or roles","parameterId":"ac-01_odp.02","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"0a129b60-0f1b-4e1f-9ff6-07a5e8f0dc61","text":"[Selection (one or more): organization-level; mission/business process-level; system-level]","parameterId":"ac-01_odp.03","default":"[Selection (one or more): organization-level; mission/business process-level; system-level]"},{"constraints":"","displayName":"","guidance":"","uuid":"aa4df469-53c3-4cff-ba4f-74d6eb3cb387","text":"official","parameterId":"ac-01_odp.04","default":" [Assignment: organization defined official] "},{"constraints":"","displayName":"","guidance":"","uuid":"d0735cf9-fd46-4724-a49f-433bbe3a8836","text":"frequency","parameterId":"ac-01_odp.05","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"c3ac73f4-fea4-468f-b930-3641afd0ed5d","text":"events","parameterId":"ac-01_odp.06","default":" [Assignment: organization defined events] "},{"constraints":"","displayName":"","guidance":"","uuid":"7fca32c2-62e4-43f2-a08d-a632e4de561f","text":"frequency","parameterId":"ac-01_odp.07","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"d3011662-d205-40e6-ad10-ca9af819afb6","text":"events","parameterId":"ac-01_odp.08","default":" [Assignment: organization defined events] "}],"subControls":"","tests":[{"testId":"AC-01a.[01]","uuid":"b01a85dc-35ab-4271-bd54-cbd733df1d64","test":"Determine if an access control policy is developed and documented;Examples of system account types include individual, shared, group, system, guest, anonymous, emergency, developer, temporary, and service. Identification of authorized system users and the specification of access privileges reflect the requirements in other controls in the security plan. Users requiring administrative privileges on system accounts receive additional scrutiny by organizational personnel responsible for approving such accounts and privileged access, including system owner, mission or business owner, senior agency information security officer, or senior agency official for privacy. Types of accounts that organizations may wish to prohibit due to increased risk include shared, group, emergency, anonymous, temporary, and guest accounts.
Where access involves personally identifiable information, security programs collaborate with the senior agency official for privacy to establish the specific conditions for group and role membership; specify authorized users, group and role membership, and access authorizations for each account; and create, adjust, or remove system accounts in accordance with organizational policies. Policies can include such information as account expiration dates or other factors that trigger the disabling of accounts. Organizations may choose to define access privileges or other attributes by account, type of account, or a combination of the two. Examples of other attributes required for authorizing access include restrictions on time of day, day of week, and point of origin. In defining other system account attributes, organizations consider system-related requirements and mission/business requirements. Failure to consider these factors could affect system availability.
Temporary and emergency accounts are intended for short-term use. Organizations establish temporary accounts as part of normal account activation procedures when there is a need for short-term accounts without the demand for immediacy in account activation. Organizations establish emergency accounts in response to crisis situations and with the need for rapid account activation. Therefore, emergency account activation may bypass normal account authorization processes. Emergency and temporary accounts are not to be confused with infrequently used accounts, including local logon accounts used for special tasks or when network resources are unavailable (may also be known as accounts of last resort). Such accounts remain available and are not subject to automatic disabling or removal dates. Conditions for disabling or deactivating accounts include when shared/group, emergency, or temporary accounts are no longer required and when individuals are transferred or terminated. Changing shared/group authenticators when members leave the group is intended to ensure that former group members do not retain access to the shared or group account. Some types of system accounts may require specialized training.
","uuid":"9dcdd7ff-e2ff-4a29-bd74-e061730275a1","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"2c1d07aa-69e9-4506-8971-7314ce9908a0","text":"prerequisites and criteria","parameterId":"ac-02_odp.01","default":" [Assignment: organization defined prerequisites and criteria] "},{"constraints":"","displayName":"","guidance":"","uuid":"6a32fb42-72a4-42c4-af5f-0e1e25b783ce","text":"attributes (as required)","parameterId":"ac-02_odp.02","default":" [Assignment: organization defined attributes (as required)] "},{"constraints":"","displayName":"","guidance":"","uuid":"0acf54c2-df8a-468e-9248-95fc37c7b959","text":"personnel or roles","parameterId":"ac-02_odp.03","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"2149bd43-5129-4b69-b612-9005e4d63bfa","text":"policy, procedures, prerequisites, and criteria","parameterId":"ac-02_odp.04","default":" [Assignment: organization defined policy, procedures, prerequisites, and criteria] "},{"constraints":"","displayName":"","guidance":"","uuid":"932df96d-a31d-401a-b1fd-5fc90d1a2147","text":"personnel or roles","parameterId":"ac-02_odp.05","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"04e58efe-defe-4524-92a3-6536ba4c0b42","text":"time period","parameterId":"ac-02_odp.06","default":" [Assignment: organization defined time period] "},{"constraints":"","displayName":"","guidance":"","uuid":"30de3560-efdc-4992-ae38-8174349be6b0","text":"time period","parameterId":"ac-02_odp.07","default":" [Assignment: organization defined time period] "},{"constraints":"","displayName":"","guidance":"","uuid":"a3be5a8f-9de3-40f7-8171-9d31fca4dc7e","text":"time period","parameterId":"ac-02_odp.08","default":" [Assignment: organization defined time period] "},{"constraints":"","displayName":"","guidance":"","uuid":"bddfb2dd-7f4d-4270-878d-5ff85a8f99a8","text":"attributes (as required)","parameterId":"ac-02_odp.09","default":" [Assignment: organization defined attributes (as required)] "},{"constraints":"","displayName":"","guidance":"","uuid":"b17f9cd7-77bb-4762-aa36-129b6a5d2f6c","text":"frequency","parameterId":"ac-02_odp.10","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"AC-02a.[01]","uuid":"a0ec0c18-c71b-40cf-bb01-07da523b39d6","test":"Determine if account types allowed for use within the system are defined and documented;Automated system account management includes using automated mechanisms to create, enable, modify, disable, and remove accounts; notify account managers when an account is created, enabled, modified, disabled, or removed, or when users are terminated or transferred; monitor system account usage; and report atypical system account usage. Automated mechanisms can include internal system functions and email, telephonic, and text messaging notifications.
","uuid":"baa79689-7897-4c2f-b6ea-bbb90c3159f6","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"358abe5e-3e9d-4e83-86fe-8beec3095786","text":"automated mechanisms","parameterId":"ac-02.01_odp","default":" [Assignment: organization defined automated mechanisms] "}],"subControls":"","tests":[{"testId":"AC-02(01)","uuid":"fe8ccd89-0a42-482d-a2f8-5983b0c56b43","test":"Determine if the management of system accounts is supported using [SELECTED PARAMETER VALUE(S): automated mechanisms ].Management of temporary and emergency accounts includes the removal or disabling of such accounts automatically after a predefined time period rather than at the convenience of the system administrator. Automatic removal or disabling of accounts provides a more consistent implementation.
","uuid":"db8c3877-0a1c-40c5-9de6-ed1b5ce26257","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"705cc7a7-9597-4022-af3c-8b3fbb8fd55c","text":"[Selection: remove; disable]","parameterId":"ac-02.02_odp.01","default":"[Selection: remove; disable]"},{"constraints":"","displayName":"","guidance":"","uuid":"c3488763-ea4e-4479-828f-3a38b6403993","text":"time period","parameterId":"ac-02.02_odp.02","default":" [Assignment: organization defined time period] "}],"subControls":"","tests":[{"testId":"AC-02(02)","uuid":"1fd0ddec-e9a4-4e27-b9ab-d03b11c1f3bf","test":"Determine if temporary and emergency accounts are automatically [SELECTED PARAMETER VALUE(S): [Selection: remove; disable] ] after [SELECTED PARAMETER VALUE(S): time period ].Disabling expired, inactive, or otherwise anomalous accounts supports the concepts of least privilege and least functionality which reduce the attack surface of the system.
","uuid":"ada5f5c6-24db-4319-b249-b2a4b6e695ae","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"11cc4216-e652-4ca2-a849-b30ef7e305ba","text":"time period","parameterId":"ac-02.03_odp.01","default":" [Assignment: organization defined time period] "},{"constraints":"","displayName":"","guidance":"","uuid":"f031c4cb-71b9-4154-825c-7908ee0ce717","text":"time period","parameterId":"ac-02.03_odp.02","default":" [Assignment: organization defined time period] "}],"subControls":"","tests":[{"testId":"AC-02(03)(a)","uuid":"bd4061d1-4a60-46c4-ba3c-5e0262496ad0","test":"Determine if accounts are disabled within [SELECTED PARAMETER VALUE(S): time period ] when the accounts have expired;Account management audit records are defined in accordance with AU-2 and reviewed, analyzed, and reported in accordance with AU-6.
","uuid":"5677488d-beda-4035-9260-735693c84d20","family":"Access Control","parameters":[],"subControls":"","tests":[{"testId":"AC-02(04)[01]","uuid":"57b86e4e-531c-4996-bca6-5a86a6b86b8f","test":"Determine if account creation is automatically audited;Inactivity logout is behavior- or policy-based and requires users to take physical action to log out when they are expecting inactivity longer than the defined period. Automatic enforcement of inactivity logout is addressed by AC-11.
","uuid":"8fc06797-2f00-4df5-bcf3-5d2b71f855be","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"25d883d1-2faa-4284-ad0b-40b6ae2ca43b","text":"time period of expected inactivity or description of when to log out","parameterId":"ac-02.05_odp","default":" [Assignment: organization defined time period of expected inactivity or description of when to log out] "}],"subControls":"","tests":[{"testId":"AC-02(05)","uuid":"16be11bb-ae1a-423a-9d00-4ece3d04ef8d","test":"Determine if users are required to log out when [SELECTED PARAMETER VALUE(S): time period of expected inactivity or description of when to log out ].In contrast to access control approaches that employ static accounts and predefined user privileges, dynamic access control approaches rely on runtime access control decisions facilitated by dynamic privilege management, such as attribute-based access control. While user identities remain relatively constant over time, user privileges typically change more frequently based on ongoing mission or business requirements and the operational needs of organizations. An example of dynamic privilege management is the immediate revocation of privileges from users as opposed to requiring that users terminate and restart their sessions to reflect changes in privileges. Dynamic privilege management can also include mechanisms that change user privileges based on dynamic rules as opposed to editing specific user profiles. Examples include automatic adjustments of user privileges if they are operating out of their normal work times, if their job function or assignment changes, or if systems are under duress or in emergency situations. Dynamic privilege management includes the effects of privilege changes, for example, when there are changes to encryption keys used for communications.
","uuid":"4a8ae8b5-de56-450e-9c3c-1b9fee1efd11","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"1b48165e-8617-4868-b1c3-ed02f3aa05af","text":"dynamic privilege management capabilities","parameterId":"ac-02.06_odp","default":" [Assignment: organization defined dynamic privilege management capabilities] "}],"subControls":"","tests":[{"testId":"AC-02(06)","uuid":"a7a4e9dc-91f8-4c66-be18-462436e40ada","test":"Determine if [SELECTED PARAMETER VALUE(S): dynamic privilege management capabilities ] are implemented.Privileged roles are organization-defined roles assigned to individuals that allow those individuals to perform certain security-relevant functions that ordinary users are not authorized to perform. Privileged roles include key management, account management, database administration, system and network administration, and web administration. A role-based access scheme organizes permitted system access and privileges into roles. In contrast, an attribute-based access scheme specifies allowed system access and privileges based on attributes.
","uuid":"cd5e7892-2472-4544-9b27-004ef7837d51","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"e484c091-23be-4c48-986d-fc632abce034","text":"[Selection: a role-based access scheme; an attribute-based access scheme]","parameterId":"ac-02.07_odp","default":"[Selection: a role-based access scheme; an attribute-based access scheme]"}],"subControls":"","tests":[{"testId":"AC-02(07)(a)","uuid":"dd520c3f-35df-413b-a809-ebbb974a38c0","test":"Determine if privileged user accounts are established and administered in accordance with [SELECTED PARAMETER VALUE(S): [Selection: a role-based access scheme; an attribute-based access scheme] ];Approaches for dynamically creating, activating, managing, and deactivating system accounts rely on automatically provisioning the accounts at runtime for entities that were previously unknown. Organizations plan for the dynamic management, creation, activation, and deactivation of system accounts by establishing trust relationships, business rules, and mechanisms with appropriate authorities to validate related authorizations and privileges.
","uuid":"390708a0-3d22-4420-ace3-bd81b8002d67","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"f2784e91-ed06-4c1a-9751-114866c6f98a","text":"system accounts","parameterId":"ac-02.08_odp","default":" [Assignment: organization defined system accounts] "}],"subControls":"","tests":[{"testId":"AC-02(08)[01]","uuid":"dc6ebdd0-2388-4255-a672-4b5e7fdfe6b6","test":"Determine if [SELECTED PARAMETER VALUE(S): system accounts ] are created dynamically;Before permitting the use of shared or group accounts, organizations consider the increased risk due to the lack of accountability with such accounts.
","uuid":"8e721ef9-30b4-49a8-a8a7-43be7f751e72","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"070321c4-032a-459e-b0c8-c050cb91bc79","text":"conditions","parameterId":"ac-02.09_odp","default":" [Assignment: organization defined conditions] "}],"subControls":"","tests":[{"testId":"AC-02(09)","uuid":"313361ef-0c0d-4884-a9fd-6d97b939e541","test":"Determine if the use of shared and group accounts is only permitted if [SELECTED PARAMETER VALUE(S): conditions ] are met.Specifying and enforcing usage conditions helps to enforce the principle of least privilege, increase user accountability, and enable effective account monitoring. Account monitoring includes alerts generated if the account is used in violation of organizational parameters. Organizations can describe specific conditions or circumstances under which system accounts can be used, such as by restricting usage to certain days of the week, time of day, or specific durations of time.
","uuid":"6f6b1325-2517-4dd3-97ee-7b0a6f2dffb3","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"7f17953f-ad8d-48fd-96d5-061b6b42e09c","text":"circumstances and/or usage conditions","parameterId":"ac-02.11_odp.01","default":" [Assignment: organization defined circumstances and/or usage conditions] "},{"constraints":"","displayName":"","guidance":"","uuid":"dc1c5d4d-2765-4603-a4aa-206bcb8b25f2","text":"system accounts","parameterId":"ac-02.11_odp.02","default":" [Assignment: organization defined system accounts] "}],"subControls":"","tests":[{"testId":"AC-02(11)","uuid":"7357e3d2-5449-42be-906f-5a1c6385b31a","test":"Determine if [SELECTED PARAMETER VALUE(S): circumstances and/or usage conditions ] for [SELECTED PARAMETER VALUE(S): system accounts ] are enforced.Atypical usage includes accessing systems at certain times of the day or from locations that are not consistent with the normal usage patterns of individuals. Monitoring for atypical usage may reveal rogue behavior by individuals or an attack in progress. Account monitoring may inadvertently create privacy risks since data collected to identify atypical usage may reveal previously unknown information about the behavior of individuals. Organizations assess and document privacy risks from monitoring accounts for atypical usage in their privacy impact assessment and make determinations that are in alignment with their privacy program plan.
","uuid":"8a5fb1f4-14fc-4843-af2d-b86c557e9ffc","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"747481d0-9ff6-4035-8a44-df7b026d3a3b","text":"atypical usage","parameterId":"ac-02.12_odp.01","default":" [Assignment: organization defined atypical usage] "},{"constraints":"","displayName":"","guidance":"","uuid":"590fb9eb-8578-4166-8b8a-4f62542c3533","text":"personnel or roles","parameterId":"ac-02.12_odp.02","default":" [Assignment: organization defined personnel or roles] "}],"subControls":"","tests":[{"testId":"AC-02(12)(a)","uuid":"fe4aca5f-fcd4-4915-b1a3-1bafecefa4be","test":"Determine if system accounts are monitored for [SELECTED PARAMETER VALUE(S): atypical usage ];Users who pose a significant security and/or privacy risk include individuals for whom reliable evidence indicates either the intention to use authorized access to systems to cause harm or through whom adversaries will cause harm. Such harm includes adverse impacts to organizational operations, organizational assets, individuals, other organizations, or the Nation. Close coordination among system administrators, legal staff, human resource managers, and authorizing officials is essential when disabling system accounts for high-risk individuals.
","uuid":"78a69a55-89d4-4d7c-b192-487d9bee7c74","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"94d5ba08-4fbd-4f4e-b051-0ea2b01c44a3","text":"time period","parameterId":"ac-02.13_odp.01","default":" [Assignment: organization defined time period] "},{"constraints":"","displayName":"","guidance":"","uuid":"8272be26-ed44-41b6-b55c-4b6df0caa00f","text":"significant risks","parameterId":"ac-02.13_odp.02","default":" [Assignment: organization defined significant risks] "}],"subControls":"","tests":[{"testId":"AC-02(13)","uuid":"0bd50afd-5cac-476c-b601-f9a9d93e4b4b","test":"Determine if accounts of individuals are disabled within [SELECTED PARAMETER VALUE(S): time period ] of discovery of [SELECTED PARAMETER VALUE(S): significant risks ].Access control policies control access between active entities or subjects (i.e., users or processes acting on behalf of users) and passive entities or objects (i.e., devices, files, records, domains) in organizational systems. In addition to enforcing authorized access at the system level and recognizing that systems can host many applications and services in support of mission and business functions, access enforcement mechanisms can also be employed at the application and service level to provide increased information security and privacy. In contrast to logical access controls that are implemented within the system, physical access controls are addressed by the controls in the Physical and Environmental Protection ( PE ) family.
","uuid":"ac197491-d451-47a1-b0a1-c20da127d7c5","family":"Access Control","parameters":[],"subControls":"","tests":[{"testId":"AC-03","uuid":"51b74e16-188c-4371-890c-333f6e9f9e53","test":"Determine if approved authorizations for logical access to information and system resources are enforced in accordance with applicable access control policies.Dual authorization, also known as two-person control, reduces risk related to insider threats. Dual authorization mechanisms require the approval of two authorized individuals to execute. To reduce the risk of collusion, organizations consider rotating dual authorization duties. Organizations consider the risk associated with implementing dual authorization mechanisms when immediate responses are necessary to ensure public and environmental safety.
","uuid":"2f8d669d-a7df-4215-8e97-406b2f47e46a","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"e1796006-67ac-4e05-8301-463b39551e34","text":"privileged commands and/or other actions","parameterId":"ac-03.02_odp","default":" [Assignment: organization defined privileged commands and/or other actions] "}],"subControls":"","tests":[{"testId":"AC-03(02)","uuid":"1cec8d45-6f71-4033-85ae-43bcea5f4bae","test":"Determine if dual authorization is enforced for [SELECTED PARAMETER VALUE(S): privileged commands and/or other actions ].Mandatory access control is a type of nondiscretionary access control. Mandatory access control policies constrain what actions subjects can take with information obtained from objects for which they have already been granted access. This prevents the subjects from passing the information to unauthorized subjects and objects. Mandatory access control policies constrain actions that subjects can take with respect to the propagation of access control privileges; that is, a subject with a privilege cannot pass that privilege to other subjects. The policy is uniformly enforced over all subjects and objects to which the system has control. Otherwise, the access control policy can be circumvented. This enforcement is provided by an implementation that meets the reference monitor concept as described in AC-25 . The policy is bounded by the system (i.e., once the information is passed outside of the control of the system, additional means may be required to ensure that the constraints on the information remain in effect).
The trusted subjects described above are granted privileges consistent with the concept of least privilege (see AC-6 ). Trusted subjects are only given the minimum privileges necessary for satisfying organizational mission/business needs relative to the above policy. The control is most applicable when there is a mandate that establishes a policy regarding access to controlled unclassified information or classified information and some users of the system are not authorized access to all such information resident in the system. Mandatory access control can operate in conjunction with discretionary access control as described in AC-3(4) . A subject constrained in its operation by mandatory access control policies can still operate under the less rigorous constraints of AC-3(4), but mandatory access control policies take precedence over the less rigorous constraints of AC-3(4). For example, while a mandatory access control policy imposes a constraint that prevents a subject from passing information to another subject operating at a different impact or classification level, AC-3(4) permits the subject to pass the information to any other subject with the same impact or classification level as the subject. Examples of mandatory access control policies include the Bell-LaPadula policy to protect confidentiality of information and the Biba policy to protect the integrity of information.
","uuid":"9e682702-6590-494b-8f3b-413dd7d49598","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"bb4fec60-7c72-49bc-8080-f1dd047a6380","text":"organization-defined mandatory access control policy","parameterId":"ac-3.3_prm_1","default":" [Assignment: organization-defined mandatory access control policy] "},{"constraints":"","displayName":"","guidance":"","uuid":"0c04aa1b-543f-4dc3-96d5-4a5c1d57b03c","text":"mandatory access control policy","parameterId":"ac-03.03_odp.01","default":" [Assignment: organization defined mandatory access control policy] "},{"constraints":"","displayName":"","guidance":"","uuid":"bcc000ab-474a-477b-88de-ba82fd40386a","text":"mandatory access control policy","parameterId":"ac-03.03_odp.02","default":" [Assignment: organization defined mandatory access control policy] "},{"constraints":"","displayName":"","guidance":"","uuid":"2db2f6b8-51f7-4548-ba18-e43fa1e66a1a","text":"subjects","parameterId":"ac-03.03_odp.03","default":" [Assignment: organization defined subjects] "},{"constraints":"","displayName":"","guidance":"","uuid":"59e7cc1d-1a65-498d-a54c-5b265cfe7eaf","text":"privileges","parameterId":"ac-03.03_odp.04","default":" [Assignment: organization defined privileges] "}],"subControls":"","tests":[{"testId":"AC-03(03)[01]","uuid":"2624d10b-e927-4e22-b4a5-da81a004f37b","test":"Determine if [SELECTED PARAMETER VALUE(S): mandatory access control policy ] is enforced over the set of covered subjects specified in the policy;When discretionary access control policies are implemented, subjects are not constrained with regard to what actions they can take with information for which they have already been granted access. Thus, subjects that have been granted access to information are not prevented from passing the information to other subjects or objects (i.e., subjects have the discretion to pass). Discretionary access control can operate in conjunction with mandatory access control as described in AC-3(3) and AC-3(15) . A subject that is constrained in its operation by mandatory access control policies can still operate under the less rigorous constraints of discretionary access control. Therefore, while AC-3(3) imposes constraints that prevent a subject from passing information to another subject operating at a different impact or classification level, AC-3(4) permits the subject to pass the information to any subject at the same impact or classification level. The policy is bounded by the system. Once the information is passed outside of system control, additional means may be required to ensure that the constraints remain in effect. While traditional definitions of discretionary access control require identity-based access control, that limitation is not required for this particular use of discretionary access control.
","uuid":"46ed6114-b54f-4da1-a002-f7cd386f7eb1","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"1b2523bc-fa67-4999-ba50-38b08681f4e3","text":"organization-defined discretionary access control policy","parameterId":"ac-3.4_prm_1","default":" [Assignment: organization-defined discretionary access control policy] "},{"constraints":"","displayName":"","guidance":"","uuid":"9f9cb139-8aa9-427b-a612-8febb279a57f","text":"discretionary access control policy","parameterId":"ac-03.04_odp.01","default":" [Assignment: organization defined discretionary access control policy] "},{"constraints":"","displayName":"","guidance":"","uuid":"b5b93aac-ed20-4f64-bc3c-2146b3c86b0c","text":"discretionary access control policy","parameterId":"ac-03.04_odp.02","default":" [Assignment: organization defined discretionary access control policy] "}],"subControls":"","tests":[{"testId":"AC-03(04)[01]","uuid":"b2a18134-ffdb-4b90-9e0c-5297c322df32","test":"Determine if [SELECTED PARAMETER VALUE(S): discretionary access control policy ] is enforced over the set of covered subjects specified in the policy;Security-relevant information is information within systems that can potentially impact the operation of security functions or the provision of security services in a manner that could result in failure to enforce system security and privacy policies or maintain the separation of code and data. Security-relevant information includes access control lists, filtering rules for routers or firewalls, configuration parameters for security services, and cryptographic key management information. Secure, non-operable system states include the times in which systems are not performing mission or business-related processing, such as when the system is offline for maintenance, boot-up, troubleshooting, or shut down.
","uuid":"d4881f7b-ab39-4ff5-9422-7e63d0d62b4a","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"f4420b7d-185d-4cb2-9e59-0aebcae7763f","text":"security-relevant information","parameterId":"ac-03.05_odp","default":" [Assignment: organization defined security-relevant information] "}],"subControls":"","tests":[{"testId":"AC-03(05)","uuid":"51f34c4d-a4dd-4674-ac70-460d9f3f42d1","test":"Determine if access to [SELECTED PARAMETER VALUE(S): security-relevant information ] is prevented except during secure, non-operable system states.Role-based access control (RBAC) is an access control policy that enforces access to objects and system functions based on the defined role (i.e., job function) of the subject. Organizations can create specific roles based on job functions and the authorizations (i.e., privileges) to perform needed operations on the systems associated with the organization-defined roles. When users are assigned to specific roles, they inherit the authorizations or privileges defined for those roles. RBAC simplifies privilege administration for organizations because privileges are not assigned directly to every user (which can be a large number of individuals) but are instead acquired through role assignments. RBAC can also increase privacy and security risk if individuals assigned to a role are given access to information beyond what they need to support organizational missions or business functions. RBAC can be implemented as a mandatory or discretionary form of access control. For organizations implementing RBAC with mandatory access controls, the requirements in AC-3(3) define the scope of the subjects and objects covered by the policy.
","uuid":"4edf7e3f-078b-46b7-97da-dccc07866600","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"a0717f98-80a8-4065-8a7a-eb1238d02c81","text":"organization-defined roles and users authorized to assume such roles","parameterId":"ac-3.7_prm_1","default":" [Assignment: organization-defined roles and users authorized to assume such roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"5ba20599-a397-4668-9cc8-ec4547813db6","text":"roles","parameterId":"ac-03.07_odp.01","default":" [Assignment: organization defined roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"1e8492af-c679-4526-8136-3f6fd453c9e1","text":"users authorized to assume such roles","parameterId":"ac-03.07_odp.02","default":" [Assignment: organization defined users authorized to assume such roles] "}],"subControls":"","tests":[{"testId":"AC-03(07)[01]","uuid":"bd3134af-7b76-4f4f-b158-a1e9531cd95b","test":"Determine if a role-based access control policy is enforced over defined subjects;Revocation of access rules may differ based on the types of access revoked. For example, if a subject (i.e., user or process acting on behalf of a user) is removed from a group, access may not be revoked until the next time the object is opened or the next time the subject attempts to access the object. Revocation based on changes to security labels may take effect immediately. Organizations provide alternative approaches on how to make revocations immediate if systems cannot provide such capability and immediate revocation is necessary.
","uuid":"962839fd-7475-406f-8df0-678c409f7c0b","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"0e755317-dc30-4b06-94fa-2ee150895845","text":"rules","parameterId":"ac-03.08_odp","default":" [Assignment: organization defined rules] "}],"subControls":"","tests":[{"testId":"AC-03(08)[01]","uuid":"17ab7f93-a06b-41d0-8c04-3116892b4d69","test":"Determine if revocation of access authorizations is enforced, resulting from changes to the security attributes of subjects based on [SELECTED PARAMETER VALUE(S): rules ];Organizations can only directly protect information when it resides within the system. Additional controls may be needed to ensure that organizational information is adequately protected once it is transmitted outside of the system. In situations where the system is unable to determine the adequacy of the protections provided by external entities, as a mitigation measure, organizations procedurally determine whether the external systems are providing adequate controls. The means used to determine the adequacy of controls provided by external systems include conducting periodic assessments (inspections/tests), establishing agreements between the organization and its counterpart organizations, or some other process. The means used by external entities to protect the information received need not be the same as those used by the organization, but the means employed are sufficient to provide consistent adjudication of the security and privacy policy to protect the information and individuals’ privacy.
Controlled release of information requires systems to implement technical or procedural means to validate the information prior to releasing it to external systems. For example, if the system passes information to a system controlled by another organization, technical means are employed to validate that the security and privacy attributes associated with the exported information are appropriate for the receiving system. Alternatively, if the system passes information to a printer in organization-controlled space, procedural means can be employed to ensure that only authorized individuals gain access to the printer.
","uuid":"66d5778f-d0c1-48a3-96b3-0ce4e2268a23","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"75c69d52-9e01-4434-9146-f028194148ee","text":"system or system component","parameterId":"ac-03.09_odp.01","default":" [Assignment: organization defined system or system component] "},{"constraints":"","displayName":"","guidance":"","uuid":"aa10a2ae-1129-4c52-a0e6-f7ee8c440ad7","text":"controls","parameterId":"ac-03.09_odp.02","default":" [Assignment: organization defined controls] "},{"constraints":"","displayName":"","guidance":"","uuid":"130a4e91-c79c-4818-8820-54a02e8cb0b3","text":"controls","parameterId":"ac-03.09_odp.03","default":" [Assignment: organization defined controls] "}],"subControls":"","tests":[{"testId":"AC-03(09)(a)","uuid":"1d3fda2a-1c1c-4ff1-ad86-8dec8f1b5a81","test":"Determine if information is released outside of the system only if the receiving [SELECTED PARAMETER VALUE(S): system or system component ] provides [SELECTED PARAMETER VALUE(S): controls ];In certain situations, such as when there is a threat to human life or an event that threatens the organization’s ability to carry out critical missions or business functions, an override capability for access control mechanisms may be needed. Override conditions are defined by organizations and used only in those limited circumstances. Audit events are defined in AU-2 . Audit records are generated in AU-12.
","uuid":"700b5739-c4a1-445c-8378-6a2dbbf4ae1d","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"cba41744-5f21-442f-b565-e960cd5b8961","text":"conditions","parameterId":"ac-03.10_odp.01","default":" [Assignment: organization defined conditions] "},{"constraints":"","displayName":"","guidance":"","uuid":"7dcf4886-aaa4-4bff-a06d-706713afe3d0","text":"roles","parameterId":"ac-03.10_odp.02","default":" [Assignment: organization defined roles] "}],"subControls":"","tests":[{"testId":"AC-03(10)","uuid":"29806f0d-c074-4a64-bcb2-e5fbf42506c1","test":"Determine if an audited override of automated access control mechanisms is employed under [SELECTED PARAMETER VALUE(S): conditions ] by [SELECTED PARAMETER VALUE(S): roles ].Restricting access to specific information is intended to provide flexibility regarding access control of specific information types within a system. For example, role-based access could be employed to allow access to only a specific type of personally identifiable information within a database rather than allowing access to the database in its entirety. Other examples include restricting access to cryptographic keys, authentication information, and selected system information.
","uuid":"a662b06f-e7bc-4c8e-b07f-3caed01e89bf","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"48f90fc0-fb7c-47f7-b8ab-899ce52fa490","text":"information types","parameterId":"ac-03.11_odp","default":" [Assignment: organization defined information types] "}],"subControls":"","tests":[{"testId":"AC-03(11)","uuid":"db68c0fe-ffe0-41c7-a933-d5241592bfe5","test":"Determine if access to data repositories containing [SELECTED PARAMETER VALUE(S): information types ] is restricted.Asserting and enforcing application access is intended to address applications that need to access existing system applications and functions, including user contacts, global positioning systems, cameras, keyboards, microphones, networks, phones, or other files.
","uuid":"6087544f-2895-4cdb-b6cb-473191dbd59a","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"df5c374e-eb57-4ad1-8a5c-2eb91e8a9061","text":"system applications and functions","parameterId":"ac-03.12_odp","default":" [Assignment: organization defined system applications and functions] "}],"subControls":"","tests":[{"testId":"AC-03(12)(a)","uuid":"d5906227-1f29-4bea-8dda-e103b741b05c","test":"Determine if as part of the installation process, applications are required to assert the access needed to the following system applications and functions: [SELECTED PARAMETER VALUE(S): system applications and functions ];Attribute-based access control is an access control policy that restricts system access to authorized users based on specified organizational attributes (e.g., job function, identity), action attributes (e.g., read, write, delete), environmental attributes (e.g., time of day, location), and resource attributes (e.g., classification of a document). Organizations can create rules based on attributes and the authorizations (i.e., privileges) to perform needed operations on the systems associated with organization-defined attributes and rules. When users are assigned to attributes defined in attribute-based access control policies or rules, they can be provisioned to a system with the appropriate privileges or dynamically granted access to a protected resource. Attribute-based access control can be implemented as either a mandatory or discretionary form of access control. When implemented with mandatory access controls, the requirements in AC-3(3) define the scope of the subjects and objects covered by the policy.
","uuid":"dc3a2121-e99d-4231-8e57-a8e8c68314dc","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"82b25a70-92ed-459d-a387-2eb928711c50","text":"attributes","parameterId":"ac-03.13_odp","default":" [Assignment: organization defined attributes] "}],"subControls":"","tests":[{"testId":"AC-03(13)[01]","uuid":"dbb0df8c-6b97-42de-8964-940aaeca836e","test":"Determine if the attribute-based access control policy is enforced over defined subjects;Individual access affords individuals the ability to review personally identifiable information about them held within organizational records, regardless of format. Access helps individuals to develop an understanding about how their personally identifiable information is being processed. It can also help individuals ensure that their data is accurate. Access mechanisms can include request forms and application interfaces. For federal agencies, PRIVACT processes can be located in systems of record notices and on agency websites. Access to certain types of records may not be appropriate (e.g., for federal agencies, law enforcement records within a system of records may be exempt from disclosure under the PRIVACT ) or may require certain levels of authentication assurance. Organizational personnel consult with the senior agency official for privacy and legal counsel to determine appropriate mechanisms and access rights or limitations.
","uuid":"2acee40a-24fd-42eb-ad4c-59d01cc41f4d","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"19dfb3cc-4212-4a8e-a935-d9b5d7675693","text":"mechanisms","parameterId":"ac-03.14_odp.01","default":" [Assignment: organization defined mechanisms] "},{"constraints":"","displayName":"","guidance":"","uuid":"768919db-4888-4f4f-9ba4-a9fda21f764c","text":"elements","parameterId":"ac-03.14_odp.02","default":" [Assignment: organization defined elements] "}],"subControls":"","tests":[{"testId":"AC-03(14)","uuid":"4a1553d2-5bb5-4487-8c0a-c7d015eb411e","test":"Determine if [SELECTED PARAMETER VALUE(S): mechanisms ] are provided to enable individuals to have access to [SELECTED PARAMETER VALUE(S): elements ] of their personally identifiable information.Simultaneously implementing a mandatory access control policy and a discretionary access control policy can provide additional protection against the unauthorized execution of code by users or processes acting on behalf of users. This helps prevent a single compromised user or process from compromising the entire system.
","uuid":"a4ac6f79-72ac-47f8-b55f-af3743359bc7","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"69b5bc81-15d9-408f-8a94-68177fa1d5cc","text":"organization-defined mandatory access control policy","parameterId":"ac-3.15_prm_1","default":" [Assignment: organization-defined mandatory access control policy] "},{"constraints":"","displayName":"","guidance":"","uuid":"b13e7873-6366-447f-b76a-417fed682bb9","text":"organization-defined discretionary access control policy","parameterId":"ac-3.15_prm_2","default":" [Assignment: organization-defined discretionary access control policy] "},{"constraints":"","displayName":"","guidance":"","uuid":"c8affaea-2ef8-4ce5-adda-aafe40b7e5ca","text":"mandatory access control policy","parameterId":"ac-03.15_odp.01","default":" [Assignment: organization defined mandatory access control policy] "},{"constraints":"","displayName":"","guidance":"","uuid":"3a3576a5-1dd3-40bb-8180-7337f66f0231","text":"mandatory access control policy","parameterId":"ac-03.15_odp.02","default":" [Assignment: organization defined mandatory access control policy] "},{"constraints":"","displayName":"","guidance":"","uuid":"c838d904-3c05-4f29-a088-724da86e70d8","text":"discretionary access control policy","parameterId":"ac-03.15_odp.03","default":" [Assignment: organization defined discretionary access control policy] "},{"constraints":"","displayName":"","guidance":"","uuid":"cf039a89-d979-462c-a6d8-d28b01b7e989","text":"discretionary access control policy","parameterId":"ac-03.15_odp.04","default":" [Assignment: organization defined discretionary access control policy] "}],"subControls":"","tests":[{"testId":"AC-03(15)(a)[01]","uuid":"7c372e64-b931-48fd-b554-f36134b80bd0","test":"Determine if [SELECTED PARAMETER VALUE(S): mandatory access control policy ] is enforced over the set of covered subjects specified in the policy;Information flow control regulates where information can travel within a system and between systems (in contrast to who is allowed to access the information) and without regard to subsequent accesses to that information. Flow control restrictions include blocking external traffic that claims to be from within the organization, keeping export-controlled information from being transmitted in the clear to the Internet, restricting web requests that are not from the internal web proxy server, and limiting information transfers between organizations based on data structures and content. Transferring information between organizations may require an agreement specifying how the information flow is enforced (see CA-3 ). Transferring information between systems in different security or privacy domains with different security or privacy policies introduces the risk that such transfers violate one or more domain security or privacy policies. In such situations, information owners/stewards provide guidance at designated policy enforcement points between connected systems. Organizations consider mandating specific architectural solutions to enforce specific security and privacy policies. Enforcement includes prohibiting information transfers between connected systems (i.e., allowing access only), verifying write permissions before accepting information from another security or privacy domain or connected system, employing hardware mechanisms to enforce one-way information flows, and implementing trustworthy regrading mechanisms to reassign security or privacy attributes and labels.
Organizations commonly employ information flow control policies and enforcement mechanisms to control the flow of information between designated sources and destinations within systems and between connected systems. Flow control is based on the characteristics of the information and/or the information path. Enforcement occurs, for example, in boundary protection devices that employ rule sets or establish configuration settings that restrict system services, provide a packet-filtering capability based on header information, or provide a message-filtering capability based on message content. Organizations also consider the trustworthiness of filtering and/or inspection mechanisms (i.e., hardware, firmware, and software components) that are critical to information flow enforcement. Control enhancements 3 through 32 primarily address cross-domain solution needs that focus on more advanced filtering techniques, in-depth analysis, and stronger flow enforcement mechanisms implemented in cross-domain products, such as high-assurance guards. Such capabilities are generally not available in commercial off-the-shelf products. Information flow enforcement also applies to control plane traffic (e.g., routing and DNS).
","uuid":"dfa7034a-9709-494a-a603-9f0841f70ba6","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"3df50c65-1bf3-4ef8-b61c-361d26d8b218","text":"information flow control policies","parameterId":"ac-04_odp","default":" [Assignment: organization defined information flow control policies] "}],"subControls":"","tests":[{"testId":"AC-04","uuid":"c1f6665b-fcb8-4e02-bc53-ff8ee207d99b","test":"Determine if approved authorizations are enforced for controlling the flow of information within the system and between connected systems based on [SELECTED PARAMETER VALUE(S): information flow control policies ].Information flow enforcement mechanisms compare security and privacy attributes associated with information (i.e., data content and structure) and source and destination objects and respond appropriately when the enforcement mechanisms encounter information flows not explicitly allowed by information flow policies. For example, an information object labeled Secret would be allowed to flow to a destination object labeled Secret, but an information object labeled Top Secret would not be allowed to flow to a destination object labeled Secret. A dataset of personally identifiable information may be tagged with restrictions against combining with other types of datasets and, thus, would not be allowed to flow to the restricted dataset. Security and privacy attributes can also include source and destination addresses employed in traffic filter firewalls. Flow enforcement using explicit security or privacy attributes can be used, for example, to control the release of certain types of information.
","uuid":"a81274ce-3778-473f-ae0e-c1d10d34de23","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"786373fb-a564-4826-a8f5-d7c2001d408e","text":"organization-defined security and privacy attributes","parameterId":"ac-4.1_prm_1","default":" [Assignment: organization-defined security and privacy attributes] "},{"constraints":"","displayName":"","guidance":"","uuid":"23e221f5-bf2a-417e-b92d-cb3ae66f6975","text":"organization-defined information, source, and destination objects","parameterId":"ac-4.1_prm_2","default":" [Assignment: organization-defined information, source, and destination objects] "},{"constraints":"","displayName":"","guidance":"","uuid":"bf897be7-7940-4b32-b10d-f91ac3e3c580","text":"security attributes","parameterId":"ac-04.01_odp.01","default":" [Assignment: organization defined security attributes] "},{"constraints":"","displayName":"","guidance":"","uuid":"3140d5df-09a0-4dbf-94a4-d6be0926fe74","text":"privacy attributes","parameterId":"ac-04.01_odp.02","default":" [Assignment: organization defined privacy attributes] "},{"constraints":"","displayName":"","guidance":"","uuid":"a478f79c-970c-4aa0-8788-1cae1c70e38b","text":"information objects","parameterId":"ac-04.01_odp.03","default":" [Assignment: organization defined information objects] "},{"constraints":"","displayName":"","guidance":"","uuid":"c6d2a3b4-ba1c-4d42-9ebb-593fd4cb4c1d","text":"information objects","parameterId":"ac-04.01_odp.04","default":" [Assignment: organization defined information objects] "},{"constraints":"","displayName":"","guidance":"","uuid":"cf566441-1526-442a-8d81-5f1f8744f079","text":"source objects","parameterId":"ac-04.01_odp.05","default":" [Assignment: organization defined source objects] "},{"constraints":"","displayName":"","guidance":"","uuid":"bca02bdf-42ca-4426-8b79-637c69e19333","text":"source objects","parameterId":"ac-04.01_odp.06","default":" [Assignment: organization defined source objects] "},{"constraints":"","displayName":"","guidance":"","uuid":"46ee4b3e-7b28-44a5-b57f-134b6f834f78","text":"destination objects","parameterId":"ac-04.01_odp.07","default":" [Assignment: organization defined destination objects] "},{"constraints":"","displayName":"","guidance":"","uuid":"62975704-01de-40eb-9812-33233009db72","text":"destination objects","parameterId":"ac-04.01_odp.08","default":" [Assignment: organization defined destination objects] "},{"constraints":"","displayName":"","guidance":"","uuid":"11cfbeef-7f23-493f-9b54-3a8e56ce6293","text":"information flow control policies","parameterId":"ac-04.01_odp.09","default":" [Assignment: organization defined information flow control policies] "}],"subControls":"","tests":[{"testId":"AC-04(01)[01]","uuid":"5b7f816d-5a29-458d-b091-027dc52eea62","test":"Determine if [SELECTED PARAMETER VALUE(S): security attributes ] associated with [SELECTED PARAMETER VALUE(S): information objects ], [SELECTED PARAMETER VALUE(S): source objects ] , and [SELECTED PARAMETER VALUE(S): destination objects ] are used to enforce [SELECTED PARAMETER VALUE(S): information flow control policies ] as a basis for flow control decisions;Protected processing domains within systems are processing spaces that have controlled interactions with other processing spaces, enabling control of information flows between these spaces and to/from information objects. A protected processing domain can be provided, for example, by implementing domain and type enforcement. In domain and type enforcement, system processes are assigned to domains, information is identified by types, and information flows are controlled based on allowed information accesses (i.e., determined by domain and type), allowed signaling among domains, and allowed process transitions to other domains.
","uuid":"f10ffa4d-566a-44ac-90d4-2368e08e5978","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"c22760dd-fb56-401f-8458-3e973002f66b","text":"information flow control policies","parameterId":"ac-04.02_odp","default":" [Assignment: organization defined information flow control policies] "}],"subControls":"","tests":[{"testId":"AC-04(02)","uuid":"39527508-9d62-4a4c-9779-a1493f6524a8","test":"Determine if protected processing domains are used to enforce [SELECTED PARAMETER VALUE(S): information flow control policies ] as a basis for flow control decisions.Organizational policies regarding dynamic information flow control include allowing or disallowing information flows based on changing conditions or mission or operational considerations. Changing conditions include changes in risk tolerance due to changes in the immediacy of mission or business needs, changes in the threat environment, and detection of potentially harmful or adverse events.
","uuid":"3313287d-054d-4cd9-bd8c-3a68dca0781c","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"e473e57c-1a65-46db-be2c-4c3aa1830b08","text":"information flow control policies","parameterId":"ac-04.03_odp","default":" [Assignment: organization defined information flow control policies] "}],"subControls":"","tests":[{"testId":"AC-04(03)","uuid":"e3b53029-73c8-4a40-8d24-9e1ee84f84da","test":"Determine if [SELECTED PARAMETER VALUE(S): information flow control policies ] are enforced.Flow control mechanisms include content checking, security policy filters, and data type identifiers. The term encryption is extended to cover encoded data not recognized by filtering mechanisms.
","uuid":"d5706bcf-fba8-4b7c-877c-48b0cac98e99","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"4b1b528d-144b-4aaa-ae14-0b688111087a","text":"information flow control mechanisms","parameterId":"ac-04.04_odp.01","default":" [Assignment: organization defined information flow control mechanisms] "},{"constraints":"","displayName":"","guidance":"","uuid":"60722be7-2764-4edc-a0ea-4c86c2104dd2","text":"[Selection (one or more): decrypting the information; blocking the flow of the encrypted information; terminating communications sessions attempting to pass encrypted information; [(NESTED PARAMETER) Assignment for ac-04.04_odp.03: organization-defined procedure or method]]","parameterId":"ac-04.04_odp.02","default":"[Selection (one or more): decrypting the information; blocking the flow of the encrypted information; terminating communications sessions attempting to pass encrypted information; [(NESTED PARAMETER) Assignment for ac-04.04_odp.03: organization-defined procedure or method]]"},{"constraints":"","displayName":"","guidance":"","uuid":"db4abc6a-f31e-4ea5-96a7-c3bcf133aed1","text":"organization-defined procedure or method","parameterId":"ac-04.04_odp.03","default":" [Assignment: organization defined organization-defined procedure or method] "}],"subControls":"","tests":[{"testId":"AC-04(04)","uuid":"586a0659-6438-4c00-8e0b-6a783b5745e6","test":"Determine if encrypted information is prevented from bypassing [SELECTED PARAMETER VALUE(S): information flow control mechanisms ] by [SELECTED PARAMETER VALUE(S): [Selection (one or more): decrypting the information; blocking the flow of the encrypted information; terminating communications sessions attempting to pass encrypted information; [(NESTED PARAMETER) Assignment for ac-04.04_odp.03: organization-defined procedure or method]] ].Embedding data types within other data types may result in reduced flow control effectiveness. Data type embedding includes inserting files as objects within other files and using compressed or archived data types that may include multiple embedded data types. Limitations on data type embedding consider the levels of embedding and prohibit levels of data type embedding that are beyond the capability of the inspection tools.
","uuid":"d8c10a8f-a6d3-421f-a28c-bc04ded3277f","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"01fd48b2-0167-4253-8bf6-b2bf7be19f45","text":"limitations","parameterId":"ac-04.05_odp","default":" [Assignment: organization defined limitations] "}],"subControls":"","tests":[{"testId":"AC-04(05)","uuid":"1565a17b-d8fe-4c3e-b502-92c572fed721","test":"Determine if [SELECTED PARAMETER VALUE(S): limitations ] are enforced on embedding data types within other data types.Metadata is information that describes the characteristics of data. Metadata can include structural metadata describing data structures or descriptive metadata describing data content. Enforcement of allowed information flows based on metadata enables simpler and more effective flow control. Organizations consider the trustworthiness of metadata regarding data accuracy (i.e., knowledge that the metadata values are correct with respect to the data), data integrity (i.e., protecting against unauthorized changes to metadata tags), and the binding of metadata to the data payload (i.e., employing sufficiently strong binding techniques with appropriate assurance).
","uuid":"f9a1d62e-ff8e-40d0-bd59-3d14eb79feb9","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"240b2be7-fb7e-45fc-9e6e-5a3e5a80c05a","text":"metadata","parameterId":"ac-04.06_odp","default":" [Assignment: organization defined metadata] "}],"subControls":"","tests":[{"testId":"AC-04(06)","uuid":"7ccab462-b295-47a4-9570-dc35cabbf63f","test":"Determine if information flow control enforcement is based on [SELECTED PARAMETER VALUE(S): metadata ].One-way flow mechanisms may also be referred to as a unidirectional network, unidirectional security gateway, or data diode. One-way flow mechanisms can be used to prevent data from being exported from a higher impact or classified domain or system while permitting data from a lower impact or unclassified domain or system to be imported.
","uuid":"ec7b30c1-9b25-4f95-b0d2-11e71250b3f3","family":"Access Control","parameters":[],"subControls":"","tests":[{"testId":"AC-04(07)","uuid":"1aa5161f-9331-4b05-8afe-b98147bcc9c2","test":"Determine if one-way information flows are enforced through hardware-based flow control mechanisms.Organization-defined security or privacy policy filters can address data structures and content. For example, security or privacy policy filters for data structures can check for maximum file lengths, maximum field sizes, and data/file types (for structured and unstructured data). Security or privacy policy filters for data content can check for specific words, enumerated values or data value ranges, and hidden content. Structured data permits the interpretation of data content by applications. Unstructured data refers to digital information without a data structure or with a data structure that does not facilitate the development of rule sets to address the impact or classification level of the information conveyed by the data or the flow enforcement decisions. Unstructured data consists of bitmap objects that are inherently non-language-based (i.e., image, video, or audio files) and textual objects that are based on written or printed languages. Organizations can implement more than one security or privacy policy filter to meet information flow control objectives.
","uuid":"93b334bf-43aa-4b4b-98a3-9adbc19c9932","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"18ac5602-0cd6-437d-965f-0fb59ac8fbbf","text":"organization-defined security or privacy policy filters","parameterId":"ac-4.8_prm_1","default":" [Assignment: organization-defined security or privacy policy filters] "},{"constraints":"","displayName":"","guidance":"","uuid":"ca905196-4c57-4f4b-87f8-7c80801ccc5f","text":"organization-defined information flows","parameterId":"ac-4.8_prm_2","default":" [Assignment: organization-defined information flows] "},{"constraints":"","displayName":"","guidance":"","uuid":"50b3596d-109b-45d6-b735-9c1dc0ca7e64","text":"organization-defined security or privacy policy","parameterId":"ac-4.8_prm_4","default":" [Assignment: organization-defined security or privacy policy] "},{"constraints":"","displayName":"","guidance":"","uuid":"70afe590-4dc2-4764-b7b3-45d1f2b4aa36","text":"security policy filter","parameterId":"ac-04.08_odp.01","default":" [Assignment: organization defined security policy filter] "},{"constraints":"","displayName":"","guidance":"","uuid":"9c00be3f-a850-4b81-93df-ebe566e9f5f2","text":"privacy policy filter","parameterId":"ac-04.08_odp.02","default":" [Assignment: organization defined privacy policy filter] "},{"constraints":"","displayName":"","guidance":"","uuid":"193eb3c7-3d13-4678-9cf8-da87b1bf0f7f","text":"information flows","parameterId":"ac-04.08_odp.03","default":" [Assignment: organization defined information flows] "},{"constraints":"","displayName":"","guidance":"","uuid":"dc5f68ac-5f16-41a7-b50b-f1b283375171","text":"information flows","parameterId":"ac-04.08_odp.04","default":" [Assignment: organization defined information flows] "},{"constraints":"","displayName":"","guidance":"","uuid":"2b7c01e7-8001-4bca-a843-84fc446d5e5f","text":"[Selection (one or more): block; strip; modify; quarantine]","parameterId":"ac-04.08_odp.05","default":"[Selection (one or more): block; strip; modify; quarantine]"},{"constraints":"","displayName":"","guidance":"","uuid":"1bd842e0-2207-4063-950b-a06d8a3ff21a","text":"security policy","parameterId":"ac-04.08_odp.06","default":" [Assignment: organization defined security policy] "},{"constraints":"","displayName":"","guidance":"","uuid":"45f742ab-5ab7-4ef9-8b4b-0a8ed11a0861","text":"privacy policy","parameterId":"ac-04.08_odp.07","default":" [Assignment: organization defined privacy policy] "}],"subControls":"","tests":[{"testId":"AC-04(08)(a)[01]","uuid":"d6dc81fd-837f-425c-904b-c030debe852a","test":"Determine if information flow control is enforced using [SELECTED PARAMETER VALUE(S): security policy filter ] as a basis for flow control decisions for [SELECTED PARAMETER VALUE(S): information flows ];Organizations define security or privacy policy filters for all situations where automated flow control decisions are possible. When a fully automated flow control decision is not possible, then a human review may be employed in lieu of or as a complement to automated security or privacy policy filtering. Human reviews may also be employed as deemed necessary by organizations.
","uuid":"833d4918-e1e1-4f3b-baba-6384a6c32df1","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"87714d39-e782-4228-944f-fd6e64f26947","text":"information flows","parameterId":"ac-04.09_odp.01","default":" [Assignment: organization defined information flows] "},{"constraints":"","displayName":"","guidance":"","uuid":"fcbbc61b-5c23-40b4-8134-106455ca44e8","text":"conditions","parameterId":"ac-04.09_odp.02","default":" [Assignment: organization defined conditions] "}],"subControls":"","tests":[{"testId":"AC-04(09)","uuid":"dd67b35b-99ec-4661-869c-450d1d5e3f8a","test":"Determine if human reviews are used for [SELECTED PARAMETER VALUE(S): information flows ] under [SELECTED PARAMETER VALUE(S): conditions ].For example, as allowed by the system authorization, administrators can enable security or privacy policy filters to accommodate approved data types. Administrators also have the capability to select the filters that are executed on a specific data flow based on the type of data that is being transferred, the source and destination security domains, and other security or privacy relevant features, as needed.
","uuid":"2fa3127a-ebdd-4879-816e-00a49ae413d6","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"e9ab222b-b673-4a1e-8d4b-03e999e8a851","text":"organization-defined security or privacy policy filters","parameterId":"ac-4.10_prm_1","default":" [Assignment: organization-defined security or privacy policy filters] "},{"constraints":"","displayName":"","guidance":"","uuid":"5b6264eb-fa8b-40e2-96d0-d7fd346a9dd5","text":"organization-defined conditions","parameterId":"ac-4.10_prm_2","default":" [Assignment: organization-defined conditions] "},{"constraints":"","displayName":"","guidance":"","uuid":"d7d7dad0-b41c-44f8-9ecb-b8bd1329ab24","text":"security filters","parameterId":"ac-04.10_odp.01","default":" [Assignment: organization defined security filters] "},{"constraints":"","displayName":"","guidance":"","uuid":"181e7f4c-2cf4-4295-9367-aba9049fa4cd","text":"privacy filters","parameterId":"ac-04.10_odp.02","default":" [Assignment: organization defined privacy filters] "},{"constraints":"","displayName":"","guidance":"","uuid":"b060095d-b3b3-4bae-9f3d-c53182ce1c1b","text":"conditions","parameterId":"ac-04.10_odp.03","default":" [Assignment: organization defined conditions] "},{"constraints":"","displayName":"","guidance":"","uuid":"320db9a3-e6ef-421e-827f-45dfff7aa3fd","text":"conditions","parameterId":"ac-04.10_odp.04","default":" [Assignment: organization defined conditions] "}],"subControls":"","tests":[{"testId":"AC-04(10)[01]","uuid":"b1a7119b-575d-4932-b37f-fb227cf59ca4","test":"Determine if capability is provided for privileged administrators to enable and disable [SELECTED PARAMETER VALUE(S): security filters ] under [SELECTED PARAMETER VALUE(S): conditions ];Documentation contains detailed information for configuring security or privacy policy filters. For example, administrators can configure security or privacy policy filters to include the list of inappropriate words that security or privacy policy mechanisms check in accordance with the definitions provided by organizations.
","uuid":"99a78ce1-28b5-44e4-b1f5-024dc0ba7594","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"bf3609e5-28b6-45cd-9d4b-c5486c3fbf91","text":"organization-defined security or privacy policy filters","parameterId":"ac-4.11_prm_1","default":" [Assignment: organization-defined security or privacy policy filters] "},{"constraints":"","displayName":"","guidance":"","uuid":"9b9a2fbf-befd-4b73-852c-c472eb9b7089","text":"security policy filters","parameterId":"ac-04.11_odp.01","default":" [Assignment: organization defined security policy filters] "},{"constraints":"","displayName":"","guidance":"","uuid":"3d20ab2f-ac9b-418a-94c5-0ba593b38d78","text":"privacy policy filters","parameterId":"ac-04.11_odp.02","default":" [Assignment: organization defined privacy policy filters] "}],"subControls":"","tests":[{"testId":"AC-04(11)[01]","uuid":"483a9e3b-a986-4ded-bb75-343764fd3787","test":"Determine if capability is provided for privileged administrators to configure [SELECTED PARAMETER VALUE(S): security policy filters ] to support different security or privacy policies;Data type identifiers include filenames, file types, file signatures or tokens, and multiple internal file signatures or tokens. Systems only allow transfer of data that is compliant with data type format specifications. Identification and validation of data types is based on defined specifications associated with each allowed data format. The filename and number alone are not used for data type identification. Content is validated syntactically and semantically against its specification to ensure that it is the proper data type.
","uuid":"32cf0bae-8a2c-4f04-9e3b-e5d370c45f72","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"14d85582-6713-4a50-b989-fbd319d9de25","text":"data type identifiers","parameterId":"ac-04.12_odp","default":" [Assignment: organization defined data type identifiers] "}],"subControls":"","tests":[{"testId":"AC-04(12)","uuid":"51990a9c-5008-431d-8da7-fd8ce1a2ba44","test":"Determine if when transferring information between different security domains, [SELECTED PARAMETER VALUE(S): data type identifiers ] are used to validate data essential for information flow decisions.Decomposing information into policy-relevant subcomponents prior to information transfer facilitates policy decisions on source, destination, certificates, classification, attachments, and other security- or privacy-related component differentiators. Policy enforcement mechanisms apply filtering, inspection, and/or sanitization rules to the policy-relevant subcomponents of information to facilitate flow enforcement prior to transferring such information to different security domains.
","uuid":"4af7efda-428d-4cba-a695-b36848e96410","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"411a711f-775c-4ab9-9c62-518d37db462c","text":"policy-relevant subcomponents","parameterId":"ac-04.13_odp","default":" [Assignment: organization defined policy-relevant subcomponents] "}],"subControls":"","tests":[{"testId":"AC-04(13)","uuid":"a496c73e-5bad-4504-b97f-fe03895e7f68","test":"Determine if when transferring information between different security domains, information is decomposed into [SELECTED PARAMETER VALUE(S): policy-relevant subcomponents ] for submission to policy enforcement mechanisms.Data structure and content restrictions reduce the range of potential malicious or unsanctioned content in cross-domain transactions. Security or privacy policy filters that restrict data structures include restricting file sizes and field lengths. Data content policy filters include encoding formats for character sets, restricting character data fields to only contain alpha-numeric characters, prohibiting special characters, and validating schema structures.
","uuid":"9bcaca43-c358-4dcd-92e5-692cd3a8c31f","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"1084b6fb-9981-4a1a-8305-50b6f320d251","text":"organization-defined security or privacy policy filters","parameterId":"ac-4.14_prm_1","default":" [Assignment: organization-defined security or privacy policy filters] "},{"constraints":"","displayName":"","guidance":"","uuid":"581e605d-6934-4933-882b-14191f029ce4","text":"security policy filters","parameterId":"ac-04.14_odp.01","default":" [Assignment: organization defined security policy filters] "},{"constraints":"","displayName":"","guidance":"","uuid":"f21c39cd-4265-41de-8c4b-3589e6f597a3","text":"privacy policy filters","parameterId":"ac-04.14_odp.02","default":" [Assignment: organization defined privacy policy filters] "}],"subControls":"","tests":[{"testId":"AC-04(14)[01]","uuid":"b958e2da-1973-4f2f-b54f-8855702bfa92","test":"Determine if when transferring information between different security domains, implemented [SELECTED PARAMETER VALUE(S): security policy filters ] require fully enumerated formats that restrict data structure and content;Unsanctioned information includes malicious code, information that is inappropriate for release from the source network, or executable code that could disrupt or harm the services or systems on the destination network.
","uuid":"2ffd6b60-9c50-43db-9e57-624b7d93d0c8","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"b03f1026-097f-4f7b-a7f0-736dcb7d28b0","text":"organization-defined security or privacy policy","parameterId":"ac-4.15_prm_2","default":" [Assignment: organization-defined security or privacy policy] "},{"constraints":"","displayName":"","guidance":"","uuid":"56021dd3-280b-485d-99ab-12ac9a948e7b","text":"unsanctioned information","parameterId":"ac-04.15_odp.01","default":" [Assignment: organization defined unsanctioned information] "},{"constraints":"","displayName":"","guidance":"","uuid":"65fef5dc-25f4-45c3-8bba-c5acae317219","text":"security policy","parameterId":"ac-04.15_odp.02","default":" [Assignment: organization defined security policy] "},{"constraints":"","displayName":"","guidance":"","uuid":"7412bf76-dc01-44bb-9354-ad276ed31493","text":"privacy policy","parameterId":"ac-04.15_odp.03","default":" [Assignment: organization defined privacy policy] "}],"subControls":"","tests":[{"testId":"AC-04(15)[01]","uuid":"4c609124-fb5c-4a93-8564-4c67042d5358","test":"Determine if when transferring information between different security domains, information is examined for the presence of [SELECTED PARAMETER VALUE(S): unsanctioned information ];Attribution is a critical component of a security and privacy concept of operations. The ability to identify source and destination points for information flowing within systems allows the forensic reconstruction of events and encourages policy compliance by attributing policy violations to specific organizations or individuals. Successful domain authentication requires that system labels distinguish among systems, organizations, and individuals involved in preparing, sending, receiving, or disseminating information. Attribution also allows organizations to better maintain the lineage of personally identifiable information processing as it flows through systems and can facilitate consent tracking, as well as correction, deletion, or access requests from individuals.
","uuid":"f76cd4c3-d326-4d0f-8c65-a5c73a6b6646","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"e1c7799e-4e18-4410-a512-a7ddbb195282","text":"[Selection (one or more): organization, system, application, service, individual]","parameterId":"ac-04.17_odp","default":"[Selection (one or more): organization, system, application, service, individual]"}],"subControls":"","tests":[{"testId":"AC-04(17)","uuid":"e338fdfd-0418-4b21-88de-cf72b69bf0e2","test":"Determine if source and destination points are uniquely identified and authenticated by [SELECTED PARAMETER VALUE(S): [Selection (one or more): organization, system, application, service, individual] ] for information transfer.All information (including metadata and the data to which the metadata applies) is subject to filtering and inspection. Some organizations distinguish between metadata and data payloads (i.e., only the data to which the metadata is bound). Other organizations do not make such distinctions and consider metadata and the data to which the metadata applies to be part of the payload.
","uuid":"705c57fe-4a1b-4af3-a626-dc39f2b58d7e","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"b569d1a1-0f1a-41a3-b487-e9165a263ace","text":"organization-defined security or privacy policy filters","parameterId":"ac-4.19_prm_1","default":" [Assignment: organization-defined security or privacy policy filters] "},{"constraints":"","displayName":"","guidance":"","uuid":"3a4479ea-1a03-45b3-be74-dbcab72b1810","text":"security policy filters","parameterId":"ac-04.19_odp.01","default":" [Assignment: organization defined security policy filters] "},{"constraints":"","displayName":"","guidance":"","uuid":"45ed2905-d76a-4e6d-91a2-24881a2ddbf9","text":"privacy policy filters","parameterId":"ac-04.19_odp.02","default":" [Assignment: organization defined privacy policy filters] "}],"subControls":"","tests":[{"testId":"AC-04(19)[01]","uuid":"d98b0789-32ea-48a1-abd5-3c69fdbda192","test":"Determine if when transferring information between different security domains, [SELECTED PARAMETER VALUE(S): security policy filters ] are implemented on metadata;Organizations define approved solutions and configurations in cross-domain policies and guidance in accordance with the types of information flows across classification boundaries. The National Security Agency (NSA) National Cross Domain Strategy and Management Office provides a listing of approved cross-domain solutions. Contact ncdsmo@nsa.gov for more information.
","uuid":"6bc9ade1-1d8f-4a71-9497-9735cd48259e","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"093a702f-6995-4d95-8f7e-bf07ca156c99","text":"solutions in approved configurations","parameterId":"ac-04.20_odp.01","default":" [Assignment: organization defined solutions in approved configurations] "},{"constraints":"","displayName":"","guidance":"","uuid":"b62f6aab-2003-4dfd-8403-6a59e3d0c05e","text":"information","parameterId":"ac-04.20_odp.02","default":" [Assignment: organization defined information] "}],"subControls":"","tests":[{"testId":"AC-04(20)","uuid":"3a729388-efb3-4e10-970e-909310818863","test":"Determine if [SELECTED PARAMETER VALUE(S): solutions in approved configurations ] are employed to control the flow of [SELECTED PARAMETER VALUE(S): information ] across security domains.Enforcing the separation of information flows associated with defined types of data can enhance protection by ensuring that information is not commingled while in transit and by enabling flow control by transmission paths that are not otherwise achievable. Types of separable information include inbound and outbound communications traffic, service requests and responses, and information of differing security impact or classification levels.
","uuid":"7e73fb32-1ec8-4460-a223-20131ac53841","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"61fe1463-da06-4c89-9957-690a04140095","text":"organization-defined mechanisms and/or techniques","parameterId":"ac-4.21_prm_1","default":" [Assignment: organization-defined mechanisms and/or techniques] "},{"constraints":"","displayName":"","guidance":"","uuid":"c328c575-411e-41ee-8750-95a8e4e39057","text":"mechanisms and/or techniques","parameterId":"ac-04.21_odp.01","default":" [Assignment: organization defined mechanisms and/or techniques] "},{"constraints":"","displayName":"","guidance":"","uuid":"bf15a8a2-9c7b-4ee5-907b-7cfde441e9e2","text":"mechanisms and/or techniques","parameterId":"ac-04.21_odp.02","default":" [Assignment: organization defined mechanisms and/or techniques] "},{"constraints":"","displayName":"","guidance":"","uuid":"32d3fcf6-bf71-4fb2-9025-c9d6309c9c09","text":"required separations","parameterId":"ac-04.21_odp.03","default":" [Assignment: organization defined required separations] "}],"subControls":"","tests":[{"testId":"AC-04(21)[01]","uuid":"5beee1bd-d2ee-49b2-8cf2-dc3d24be41d9","test":"Determine if information flows are separated logically using [SELECTED PARAMETER VALUE(S): mechanisms and/or techniques ] to accomplish [SELECTED PARAMETER VALUE(S): required separations ];The system provides a capability for users to access each connected security domain without providing any mechanisms to allow users to transfer data or information between the different security domains. An example of an access-only solution is a terminal that provides a user access to information with different security classifications while assuredly keeping the information separate.
","uuid":"4a81901e-b757-4592-935b-36ccd143e34f","family":"Access Control","parameters":[],"subControls":"","tests":[{"testId":"AC-04(22)","uuid":"47a66b30-414b-43af-91f2-06f888354399","test":"Determine if access is provided from a single device to computing platforms, applications, or data that reside in multiple different security domains while preventing information flow between the different security domains.Modifying non-releasable information can help prevent a data spill or attack when information is transferred across security domains. Modification actions include masking, permutation, alteration, removal, or redaction.
","uuid":"9f6e0aa6-57ca-42ed-8e14-536799f0aff4","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"658bb0f0-fb3c-4e83-9012-08e64e1f7bdc","text":"modification action","parameterId":"ac-04.23_odp","default":" [Assignment: organization defined modification action] "}],"subControls":"","tests":[{"testId":"AC-04(23)","uuid":"9928f3ed-c5d5-4194-bf55-043db8f3e834","test":"Determine if when transferring information between security domains, non-releasable information is modified by implementing [SELECTED PARAMETER VALUE(S): modification action ].Converting data into normalized forms is one of most of effective mechanisms to stop malicious attacks and large classes of data exfiltration.
","uuid":"4a8fc5a1-d170-4d22-b40c-be5d23e375be","family":"Access Control","parameters":[],"subControls":"","tests":[{"testId":"AC-04(24)[01]","uuid":"3b0bbc4a-adcb-4619-bb79-c4ef0a712b0d","test":"Determine if when transferring information between different security domains, incoming data is parsed into an internal, normalized format;Data sanitization is the process of irreversibly removing or destroying data stored on a memory device (e.g., hard drives, flash memory/solid state drives, mobile devices, CDs, and DVDs) or in hard copy form.
","uuid":"690ce071-0216-4399-aead-755923b4af29","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"171e9cbe-c33c-495a-8dbc-d3efa017d7f1","text":"[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]","parameterId":"ac-04.25_odp.01","default":"[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]"},{"constraints":"","displayName":"","guidance":"","uuid":"75498667-7baa-43a5-ad70-9386bb0d3a4e","text":"policy","parameterId":"ac-04.25_odp.02","default":" [Assignment: organization defined policy] "}],"subControls":"","tests":[{"testId":"AC-04(25)","uuid":"c7efd31e-0659-4db1-860c-fe071e28732b","test":"Determine if when transferring information between different security domains, data is sanitized to minimize [SELECTED PARAMETER VALUE(S): [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 [SELECTED PARAMETER VALUE(S): policy ].Content filtering is the process of inspecting information as it traverses a cross-domain solution and determines if the information meets a predefined policy. Content filtering actions and the results of filtering actions are recorded for individual messages to ensure that the correct filter actions were applied. Content filter reports are used to assist in troubleshooting actions by, for example, determining why message content was modified and/or why it failed the filtering process. Audit events are defined in AU-2 . Audit records are generated in AU-12.
","uuid":"5a58f094-f4cd-4bb1-9b71-ac2abd0df9d6","family":"Access Control","parameters":[],"subControls":"","tests":[{"testId":"AC-04(26)[01]","uuid":"b5955d46-a7fd-42f0-97fb-e2731d11c236","test":"Determine if when transferring information between different security domains, content-filtering actions are recorded and audited;Content filtering is the process of inspecting information as it traverses a cross-domain solution and determines if the information meets a predefined policy. Redundant and independent content filtering eliminates a single point of failure filtering system. Independence is defined as the implementation of a content filter that uses a different code base and supporting libraries (e.g., two JPEG filters using different vendors’ JPEG libraries) and multiple, independent system processes.
","uuid":"d8df5ee6-60ee-4073-b799-46320e6e18a7","family":"Access Control","parameters":[],"subControls":"","tests":[{"testId":"AC-04(27)","uuid":"1f3f2dde-172b-4210-a4d9-5de2e47bf85f","test":"Determine if when transferring information between security domains, implemented content filtering solutions provide redundant and independent filtering mechanisms for each data type.Content filtering is the process of inspecting information as it traverses a cross-domain solution and determines if the information meets a predefined policy. The use of linear content filter pipelines ensures that filter processes are non-bypassable and always invoked. In general, the use of parallel filtering architectures for content filtering of a single data type introduces bypass and non-invocation issues.
","uuid":"1e770367-f6ef-45b5-b903-3d0ae43fa855","family":"Access Control","parameters":[],"subControls":"","tests":[{"testId":"AC-04(28)","uuid":"3f867338-c7fc-4627-9a51-94e452ed25c5","test":"Determine if when transferring information between security domains, a linear content filter pipeline is implemented that is enforced with discretionary and mandatory access controls.Content filtering is the process of inspecting information as it traverses a cross-domain solution and determines if the information meets a predefined security policy. An orchestration engine coordinates the sequencing of activities (manual and automated) in a content filtering process. Errors are defined as either anomalous actions or unexpected termination of the content filter process. This is not the same as a filter failing content due to non-compliance with policy. Content filter reports are a commonly used mechanism to ensure that expected filtering actions are completed successfully.
","uuid":"8bb16a64-a31b-47e1-ac93-f7b0e6747391","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"15e46222-a3b0-4ab8-b7cf-3bb0c4ef84f9","text":"policy","parameterId":"ac-04.29_odp","default":" [Assignment: organization defined policy] "}],"subControls":"","tests":[{"testId":"AC-04(29)(a)","uuid":"9552e8b6-7bc7-4124-ac18-4df85e5636bd","test":"Determine if when transferring information between security domains, content filter orchestration engines are employed to ensure that content-filtering mechanisms successfully complete execution without errors;The use of multiple processes to implement content filtering mechanisms reduces the likelihood of a single point of failure.
","uuid":"b02022fc-64c3-40a4-9c45-df8be2e65df2","family":"Access Control","parameters":[],"subControls":"","tests":[{"testId":"AC-04(30)","uuid":"25424056-5720-4004-88dd-cfaaf166045f","test":"Determine if when transferring information between security domains, content-filtering mechanisms using multiple processes are implemented.Content that failed filtering checks can corrupt the system if transferred to the receiving domain.
","uuid":"a75b71eb-2e4d-4219-be98-5010c720abbb","family":"Access Control","parameters":[],"subControls":"","tests":[{"testId":"AC-04(31)","uuid":"124d5d56-f8bf-4c95-b50e-414f2ec6acdc","test":"Determine if when transferring information between different security domains, the transfer of failed content to the receiving domain is prevented.The processes transferring information between filter pipelines have minimum complexity and functionality to provide assurance that the processes operate correctly.
","uuid":"65f9837b-6849-4076-96c4-f9aca2fa44a3","family":"Access Control","parameters":[],"subControls":"","tests":[{"testId":"AC-04(32)(a)","uuid":"74b7e208-ac2e-4633-9e76-5a2b14a7689b","test":"Determine if when transferring information between different security domains, the process that transfers information between filter pipelines does not filter message content;Separation of duties addresses the potential for abuse of authorized privileges and helps to reduce the risk of malevolent activity without collusion. Separation of duties includes dividing mission or business functions and support functions among different individuals or roles, conducting system support functions with different individuals, and ensuring that security personnel who administer access control functions do not also administer audit functions. Because separation of duty violations can span systems and application domains, organizations consider the entirety of systems and system components when developing policy on separation of duties. Separation of duties is enforced through the account management activities in AC-2 , access control mechanisms in AC-3 , and identity management activities in IA-2, IA-4 , and IA-12.
","uuid":"dc3ad31c-ad2e-4cc2-b590-29679bc3aa5a","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"1415d46d-eb8c-4c31-8bcc-5e41778ef55b","text":"duties of individuals","parameterId":"ac-05_odp","default":" [Assignment: organization defined duties of individuals] "}],"subControls":"","tests":[{"testId":"AC-05a.","uuid":"a24eaae2-7406-4f00-b7c4-5d3836b80caf","test":"Determine if [SELECTED PARAMETER VALUE(S): duties of individuals ] are identified and documented;Organizations employ least privilege for specific duties and systems. The principle of least privilege is also applied to system processes, ensuring that the processes have access to systems and operate at privilege levels no higher than necessary to accomplish organizational missions or business functions. Organizations consider the creation of additional processes, roles, and accounts as necessary to achieve least privilege. Organizations apply least privilege to the development, implementation, and operation of organizational systems.
","uuid":"c5f6ae41-7ccc-40fd-9069-be5f5aec4c5a","family":"Access Control","parameters":[],"subControls":"","tests":[{"testId":"AC-06","uuid":"8c295b45-07bb-4101-84a6-5fdc96bafefd","test":"Determine if the principle of least privilege is employed, allowing only authorized accesses for users (or processes acting on behalf of users) that are necessary to accomplish assigned organizational tasks.Security functions include establishing system accounts, configuring access authorizations (i.e., permissions, privileges), configuring settings for events to be audited, and establishing intrusion detection parameters. Security-relevant information includes filtering rules for routers or firewalls, configuration parameters for security services, cryptographic key management information, and access control lists. Authorized personnel include security administrators, system administrators, system security officers, system programmers, and other privileged users.
","uuid":"50dc81a5-e755-40fe-ae55-d5c085b6afe2","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"211a094a-22af-4d46-b3bc-e4b928c95e8f","text":"organization-defined security functions (deployed in hardware, software, and firmware)","parameterId":"ac-6.1_prm_2","default":" [Assignment: organization-defined security functions (deployed in hardware, software, and firmware)] "},{"constraints":"","displayName":"","guidance":"","uuid":"ff9c3d5f-3a01-4817-b2df-3c7e258c5151","text":"individuals and roles","parameterId":"ac-06.01_odp.01","default":" [Assignment: organization defined individuals and roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"e97ad30a-b5bd-41d7-9a5b-1bd09761a3de","text":"security functions (deployed in hardware)","parameterId":"ac-06.01_odp.02","default":" [Assignment: organization defined security functions (deployed in hardware)] "},{"constraints":"","displayName":"","guidance":"","uuid":"d802b6f7-2bfe-46ec-b01e-e703b72350f0","text":"security functions (deployed in software)","parameterId":"ac-06.01_odp.03","default":" [Assignment: organization defined security functions (deployed in software)] "},{"constraints":"","displayName":"","guidance":"","uuid":"04d850d4-63b5-4124-972b-88ed10579a3f","text":"security functions (deployed in firmware)","parameterId":"ac-06.01_odp.04","default":" [Assignment: organization defined security functions (deployed in firmware)] "},{"constraints":"","displayName":"","guidance":"","uuid":"ec12ed76-5c1a-4603-b3e4-4e1d7b95f1cf","text":"security-relevant information","parameterId":"ac-06.01_odp.05","default":" [Assignment: organization defined security-relevant information] "}],"subControls":"","tests":[{"testId":"AC-06(01)(a)[01]","uuid":"69fb11df-cb1a-4f7f-8cfd-b12e93c3b6b1","test":"Determine if access is authorized for [SELECTED PARAMETER VALUE(S): individuals and roles ] to [SELECTED PARAMETER VALUE(S): security functions (deployed in hardware) ];Requiring the use of non-privileged accounts when accessing nonsecurity functions limits exposure when operating from within privileged accounts or roles. The inclusion of roles addresses situations where organizations implement access control policies, such as role-based access control, and where a change of role provides the same degree of assurance in the change of access authorizations for the user and the processes acting on behalf of the user as would be provided by a change between a privileged and non-privileged account.
","uuid":"6e676df7-6640-463f-9fc9-3bcb858b8f61","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"b12d7e7f-4ac5-4c2b-ac98-2ea80b91094a","text":"security functions or security-relevant information","parameterId":"ac-06.02_odp","default":" [Assignment: organization defined security functions or security-relevant information] "}],"subControls":"","tests":[{"testId":"AC-06(02)","uuid":"e86305e9-b71d-44f8-b8b5-9acd9fb06d7e","test":"Determine if users of system accounts (or roles) with access to [SELECTED PARAMETER VALUE(S): security functions or security-relevant information ] are required to use non-privileged accounts or roles when accessing non-security functions.Network access is any access across a network connection in lieu of local access (i.e., user being physically present at the device).
","uuid":"790d20cc-24a1-4e89-a356-abdc91ac56ac","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"9c32bbd5-0376-4fb1-8d0d-ec136a46014c","text":"privileged commands","parameterId":"ac-06.03_odp.01","default":" [Assignment: organization defined privileged commands] "},{"constraints":"","displayName":"","guidance":"","uuid":"73f5abde-b207-4753-82ce-cf9af249c336","text":"compelling operational needs","parameterId":"ac-06.03_odp.02","default":" [Assignment: organization defined compelling operational needs] "}],"subControls":"","tests":[{"testId":"AC-06(03)[01]","uuid":"17f611ae-05fb-4b82-9903-ba01fb66ab07","test":"Determine if network access to [SELECTED PARAMETER VALUE(S): privileged commands ] is authorized only for [SELECTED PARAMETER VALUE(S): compelling operational needs ];Providing separate processing domains for finer-grained allocation of user privileges includes using virtualization techniques to permit additional user privileges within a virtual machine while restricting privileges to other virtual machines or to the underlying physical machine, implementing separate physical domains, and employing hardware or software domain separation mechanisms.
","uuid":"3d8d5f6f-7505-40fc-9027-301339081a0d","family":"Access Control","parameters":[],"subControls":"","tests":[{"testId":"AC-06(04)","uuid":"a0496608-f86f-4e62-82d0-0e6a295d90fb","test":"Determine if separate processing domains are provided to enable finer-grain allocation of user privileges.Privileged accounts, including super user accounts, are typically described as system administrator for various types of commercial off-the-shelf operating systems. Restricting privileged accounts to specific personnel or roles prevents day-to-day users from accessing privileged information or privileged functions. Organizations may differentiate in the application of restricting privileged accounts between allowed privileges for local accounts and for domain accounts provided that they retain the ability to control system configurations for key parameters and as otherwise necessary to sufficiently mitigate risk.
","uuid":"f5bf2962-c130-4fb8-b7d9-c6799ca03615","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"903ecc18-b88e-403e-b796-390a78113bb6","text":"personnel or roles","parameterId":"ac-06.05_odp","default":" [Assignment: organization defined personnel or roles] "}],"subControls":"","tests":[{"testId":"AC-06(05)","uuid":"530c644f-667d-4a52-b54d-c391fffc7af1","test":"Determine if privileged accounts on the system are restricted to [SELECTED PARAMETER VALUE(S): personnel or roles ].An organizational user is an employee or an individual considered by the organization to have the equivalent status of an employee. Organizational users include contractors, guest researchers, or individuals detailed from other organizations. A non-organizational user is a user who is not an organizational user. Policies and procedures for granting equivalent status of employees to individuals include a need-to-know, citizenship, and the relationship to the organization.
","uuid":"36c4db8a-8183-4311-9b23-d57265cdf004","family":"Access Control","parameters":[],"subControls":"","tests":[{"testId":"AC-06(06)","uuid":"d1fefc9a-0b9f-4052-b8ae-d99b83db0251","test":"Determine if privileged access to the system by non-organizational users is prohibited.The need for certain assigned user privileges may change over time to reflect changes in organizational mission and business functions, environments of operation, technologies, or threats. A periodic review of assigned user privileges is necessary to determine if the rationale for assigning such privileges remains valid. If the need cannot be revalidated, organizations take appropriate corrective actions.
","uuid":"c435bc7b-524c-4767-a9c6-eeca880b682e","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"010c0d15-8b27-4c5e-a77c-5fff77e951e2","text":"frequency","parameterId":"ac-06.07_odp.01","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"9492c96a-fa7e-4f08-bdd5-99e33cfac58a","text":"roles and classes","parameterId":"ac-06.07_odp.02","default":" [Assignment: organization defined roles and classes] "}],"subControls":"","tests":[{"testId":"AC-06(07)(a)","uuid":"8623c031-f741-4436-8408-ee13da7aa2f5","test":"Determine if privileges assigned to [SELECTED PARAMETER VALUE(S): roles and classes ] are reviewed [SELECTED PARAMETER VALUE(S): frequency ] to validate the need for such privileges;In certain situations, software applications or programs need to execute with elevated privileges to perform required functions. However, depending on the software functionality and configuration, if the privileges required for execution are at a higher level than the privileges assigned to organizational users invoking such applications or programs, those users may indirectly be provided with greater privileges than assigned.
","uuid":"53b8de5a-2ea5-42d9-afec-89ef2ab285b0","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"bb038fa7-2448-45f4-881f-f64b933fae3c","text":"software","parameterId":"ac-06.08_odp","default":" [Assignment: organization defined software] "}],"subControls":"","tests":[{"testId":"AC-06(08)","uuid":"2078b807-9c07-414e-9cc0-d558cb69630c","test":"Determine if [SELECTED PARAMETER VALUE(S): software ] is prevented from executing at higher privilege levels than users executing the software.The misuse of privileged functions, either intentionally or unintentionally by authorized users or by unauthorized external entities that have compromised system accounts, is a serious and ongoing concern and can have significant adverse impacts on organizations. Logging and analyzing the use of privileged functions is one way to detect such misuse and, in doing so, help mitigate the risk from insider threats and the advanced persistent threat.
","uuid":"119364f6-9c84-4460-b6da-23766f44a572","family":"Access Control","parameters":[],"subControls":"","tests":[{"testId":"AC-06(09)","uuid":"4eb57024-52c0-4ef6-a9a3-24004fa6cc03","test":"Determine if the execution of privileged functions is logged.Privileged functions include disabling, circumventing, or altering implemented security or privacy controls, establishing system accounts, performing system integrity checks, and administering cryptographic key management activities. Non-privileged users are individuals who do not possess appropriate authorizations. Privileged functions that require protection from non-privileged users include circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms. Preventing non-privileged users from executing privileged functions is enforced by AC-3.
","uuid":"80cfbe90-5206-4434-9b81-11883c6f26e0","family":"Access Control","parameters":[],"subControls":"","tests":[{"testId":"AC-06(10)","uuid":"1281c823-bbff-4ee9-9bd2-712aebde9c9e","test":"Determine if non-privileged users are prevented from executing privileged functions.The need to limit unsuccessful logon attempts and take subsequent action when the maximum number of attempts is exceeded applies regardless of whether the logon occurs via a local or network connection. Due to the potential for denial of service, automatic lockouts initiated by systems are usually temporary and automatically release after a predetermined, organization-defined time period. If a delay algorithm is selected, organizations may employ different algorithms for different components of the system based on the capabilities of those components. Responses to unsuccessful logon attempts may be implemented at the operating system and the application levels. Organization-defined actions that may be taken when the number of allowed consecutive invalid logon attempts is exceeded include prompting the user to answer a secret question in addition to the username and password, invoking a lockdown mode with limited user capabilities (instead of full lockout), allowing users to only logon from specified Internet Protocol (IP) addresses, requiring a CAPTCHA to prevent automated attacks, or applying user profiles such as location, time of day, IP address, device, or Media Access Control (MAC) address. If automatic system lockout or execution of a delay algorithm is not implemented in support of the availability objective, organizations consider a combination of other actions to help prevent brute force attacks. In addition to the above, organizations can prompt users to respond to a secret question before the number of allowed unsuccessful logon attempts is exceeded. Automatically unlocking an account after a specified period of time is generally not permitted. However, exceptions may be required based on operational mission or need.
","uuid":"3f452c18-b5ee-483d-aa43-72ed548139a3","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"71ee44bf-714d-4602-b4cc-4ec8d5164e4d","text":"number","parameterId":"ac-07_odp.01","default":" [Assignment: organization defined number] "},{"constraints":"","displayName":"","guidance":"","uuid":"fce4d551-d643-42ab-8a14-f20861aec80c","text":"time period","parameterId":"ac-07_odp.02","default":" [Assignment: organization defined time period] "},{"constraints":"","displayName":"","guidance":"","uuid":"2a19fe9e-0455-49b5-ac3c-869082bffb60","text":"[Selection (one or more): lock the account or node for [(NESTED PARAMETER) Assignment for ac-07_odp.04: time period]; lock the account or node until released by an administrator; delay next logon prompt per [(NESTED PARAMETER) Assignment for ac-07_odp.05: delay algorithm]; notify system administrator; take other [(NESTED PARAMETER) Assignment for ac-07_odp.06: action]]","parameterId":"ac-07_odp.03","default":"[Selection (one or more): lock the account or node for [(NESTED PARAMETER) Assignment for ac-07_odp.04: time period]; lock the account or node until released by an administrator; delay next logon prompt per [(NESTED PARAMETER) Assignment for ac-07_odp.05: delay algorithm]; notify system administrator; take other [(NESTED PARAMETER) Assignment for ac-07_odp.06: action]]"},{"constraints":"","displayName":"","guidance":"","uuid":"17cd1e18-ad19-4ef8-acc0-abd51f888d98","text":"time period","parameterId":"ac-07_odp.04","default":" [Assignment: organization defined time period] "},{"constraints":"","displayName":"","guidance":"","uuid":"704ccd1a-1119-4658-9338-24a312e22ebb","text":"delay algorithm","parameterId":"ac-07_odp.05","default":" [Assignment: organization defined delay algorithm] "},{"constraints":"","displayName":"","guidance":"","uuid":"cfeb21db-32ae-47c5-b04f-200734aceba2","text":"action","parameterId":"ac-07_odp.06","default":" [Assignment: organization defined action] "}],"subControls":"","tests":[{"testId":"AC-07a.","uuid":"1be153b8-26c2-4314-9d57-3402081a5394","test":"Determine if a limit of [SELECTED PARAMETER VALUE(S): number ] consecutive invalid logon attempts by a user during [SELECTED PARAMETER VALUE(S): time period ] is enforced;A mobile device is a computing device that has a small form factor such that it can be carried by a single individual; is designed to operate without a physical connection; possesses local, non-removable or removable data storage; and includes a self-contained power source. Purging or wiping the device applies only to mobile devices for which the organization-defined number of unsuccessful logons occurs. The logon is to the mobile device, not to any one account on the device. Successful logons to accounts on mobile devices reset the unsuccessful logon count to zero. Purging or wiping may be unnecessary if the information on the device is protected with sufficiently strong encryption mechanisms.
","uuid":"b86a7576-530a-4509-b0df-07202d3d5a10","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"2cff6401-736f-4a3c-a4c4-bad22f2266a6","text":"mobile devices","parameterId":"ac-07.02_odp.01","default":" [Assignment: organization defined mobile devices] "},{"constraints":"","displayName":"","guidance":"","uuid":"c6361c84-c48b-4577-ba90-36e332823a1a","text":"purging or wiping requirements or techniques","parameterId":"ac-07.02_odp.02","default":" [Assignment: organization defined purging or wiping requirements or techniques] "},{"constraints":"","displayName":"","guidance":"","uuid":"012f34b2-e7e2-4c42-a0b1-6c4da1e007cf","text":"number","parameterId":"ac-07.02_odp.03","default":" [Assignment: organization defined number] "}],"subControls":"","tests":[{"testId":"AC-07(02)","uuid":"66b70597-252e-42d7-bb8d-d120bb5a0e9a","test":"Determine if information is purged or wiped from [SELECTED PARAMETER VALUE(S): mobile devices ] based on [SELECTED PARAMETER VALUE(S): purging or wiping requirements or techniques ] after [SELECTED PARAMETER VALUE(S): number ] consecutive, unsuccessful device logon attempts.Biometrics are probabilistic in nature. The ability to successfully authenticate can be impacted by many factors, including matching performance and presentation attack detection mechanisms. Organizations select the appropriate number of attempts for users based on organizationally-defined factors.
","uuid":"a92fa342-c466-4d70-9364-e07217c65803","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"14dde7db-dab1-4852-b6de-631e74bbc5de","text":"number","parameterId":"ac-07.03_odp","default":" [Assignment: organization defined number] "}],"subControls":"","tests":[{"testId":"AC-07(03)","uuid":"d7b55153-ad76-407a-a9b9-d8825a70ea21","test":"Determine if unsuccessful biometric logon attempts are limited to [SELECTED PARAMETER VALUE(S): number ].The use of alternate authentication factors supports the objective of availability and allows a user who has inadvertently been locked out to use additional authentication factors to bypass the lockout.
","uuid":"a581a01d-4279-4886-8627-8c54d8c28f7c","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"66a01cd7-41ea-4c3f-a535-b6e44160aed0","text":"authentication factors","parameterId":"ac-07.04_odp.01","default":" [Assignment: organization defined authentication factors] "},{"constraints":"","displayName":"","guidance":"","uuid":"981b6835-0148-46f1-96f8-154ba212b93d","text":"number","parameterId":"ac-07.04_odp.02","default":" [Assignment: organization defined number] "},{"constraints":"","displayName":"","guidance":"","uuid":"e67f2bdf-2d1f-4ab4-ae6a-f82e3d561ae2","text":"time period","parameterId":"ac-07.04_odp.03","default":" [Assignment: organization defined time period] "}],"subControls":"","tests":[{"testId":"AC-07(04)(a)","uuid":"7af487d1-7728-41c3-bf0b-711b053cd6b5","test":"Determine if [SELECTED PARAMETER VALUE(S): authentication factors ] that are different from the primary authentication factors are allowed to be used after the number of organization-defined consecutive invalid logon attempts have been exceeded;System use notifications can be implemented using messages or warning banners displayed before individuals log in to systems. System use notifications are used only for access via logon interfaces with human users. Notifications are not required when human interfaces do not exist. Based on an assessment of risk, organizations consider whether or not a secondary system use notification is needed to access applications or other system resources after the initial network logon. Organizations consider system use notification messages or banners displayed in multiple languages based on organizational needs and the demographics of system users. Organizations consult with the privacy office for input regarding privacy messaging and the Office of the General Counsel or organizational equivalent for legal review and approval of warning banner content.
","uuid":"d40c4b44-df70-4f74-8cbc-a2d33f009d01","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"70a00a6f-1a7c-493c-9916-e60b8ea9fa15","text":"system use notification","parameterId":"ac-08_odp.01","default":" [Assignment: organization defined system use notification] "},{"constraints":"","displayName":"","guidance":"","uuid":"51b719a7-8ee0-426d-9042-848c5fb7b741","text":"conditions","parameterId":"ac-08_odp.02","default":" [Assignment: organization defined conditions] "}],"subControls":"","tests":[{"testId":"AC-08a.","uuid":"717d09fa-5851-4878-9fed-c5824c5651eb","test":"Determine if [SELECTED PARAMETER VALUE(S): system use notification ] is displayed 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;Previous logon notification is applicable to system access via human user interfaces and access to systems that occurs in other types of architectures. Information about the last successful logon allows the user to recognize if the date and time provided is not consistent with the user’s last access.
","uuid":"fdc23d47-dfda-48d5-a421-b7a7f9bf2685","family":"Access Control","parameters":[],"subControls":"","tests":[{"testId":"AC-09","uuid":"41e4ef95-d989-44f8-a446-d17cce2a0cac","test":"Determine if the user is notified, upon successful logon to the system, of the date and time of the last logon.Information about the number of unsuccessful logon attempts since the last successful logon allows the user to recognize if the number of unsuccessful logon attempts is consistent with the user’s actual logon attempts.
","uuid":"0671391b-e61e-4ee8-bfe6-3395fdbea6d0","family":"Access Control","parameters":[],"subControls":"","tests":[{"testId":"AC-09(01)","uuid":"3447bdc7-cca7-4ac6-ac1b-cd9b55092bcb","test":"Determine if the user is notified, upon successful logon, of the number of unsuccessful logon attempts since the last successful logon.Information about the number of successful and unsuccessful logon attempts within a specified time period allows the user to recognize if the number and type of logon attempts are consistent with the user’s actual logon attempts.
","uuid":"3679ad1d-9c11-446f-b184-d6ce94e78d58","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"38765b00-949e-4173-9a81-fb447e7f1006","text":"[Selection: successful logons; unsuccessful logon attempts; both]","parameterId":"ac-09.02_odp.01","default":"[Selection: successful logons; unsuccessful logon attempts; both]"},{"constraints":"","displayName":"","guidance":"","uuid":"7d6bdae8-5ffe-4f94-ad5b-a675ccce7f51","text":"time period","parameterId":"ac-09.02_odp.02","default":" [Assignment: organization defined time period] "}],"subControls":"","tests":[{"testId":"AC-09(02)","uuid":"317fc6bc-ed53-4a56-8660-2b5e8d7e1b76","test":"Determine if the user is notified, upon successful logon, of the number of [SELECTED PARAMETER VALUE(S): [Selection: successful logons; unsuccessful logon attempts; both] ] during [SELECTED PARAMETER VALUE(S): time period ].Information about changes to security-related account characteristics within a specified time period allows users to recognize if changes were made without their knowledge.
","uuid":"e5e8c977-6d02-49f4-b6ef-a65fbbd301be","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"8d1bdd5f-2d53-44c2-9aaa-5f4ce41d4c5f","text":"security-related characteristics or parameters","parameterId":"ac-09.03_odp.01","default":" [Assignment: organization defined security-related characteristics or parameters] "},{"constraints":"","displayName":"","guidance":"","uuid":"91f57236-236b-4410-923a-cc9faaa89f84","text":"time period","parameterId":"ac-09.03_odp.02","default":" [Assignment: organization defined time period] "}],"subControls":"","tests":[{"testId":"AC-09(03)","uuid":"be380e12-01a7-49b4-9d57-1845576792d0","test":"Determine if the user is notified, upon successful logon, of changes to [SELECTED PARAMETER VALUE(S): security-related characteristics or parameters ] during [SELECTED PARAMETER VALUE(S): time period ].Organizations can specify additional information to be provided to users upon logon, including the location of the last logon. User location is defined as information that can be determined by systems, such as Internet Protocol (IP) addresses from which network logons occurred, notifications of local logons, or device identifiers.
","uuid":"231938a8-2c71-4456-83d7-4861333f9fa8","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"0f6ec4f1-1a7c-4b1c-8b53-090e207c3c89","text":"additional information","parameterId":"ac-09.04_odp","default":" [Assignment: organization defined additional information] "}],"subControls":"","tests":[{"testId":"AC-09(04)","uuid":"fdfbe0c6-dd98-47cf-937b-c8a4593fdca1","test":"Determine if the user is notified, upon successful logon, of [SELECTED PARAMETER VALUE(S): additional information ].Organizations may define the maximum number of concurrent sessions for system accounts globally, by account type, by account, or any combination thereof. For example, organizations may limit the number of concurrent sessions for system administrators or other individuals working in particularly sensitive domains or mission-critical applications. Concurrent session control addresses concurrent sessions for system accounts. It does not, however, address concurrent sessions by single users via multiple system accounts.
","uuid":"3bcec61b-591f-4a17-b966-0bd06d399519","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"05de05c0-a863-498f-a0cb-1c4d24981aa2","text":"account and/or account types","parameterId":"ac-10_odp.01","default":" [Assignment: organization defined account and/or account types] "},{"constraints":"","displayName":"","guidance":"","uuid":"4ff5da6d-1661-40fd-b115-c72696cad6bd","text":"number","parameterId":"ac-10_odp.02","default":" [Assignment: organization defined number] "}],"subControls":"","tests":[{"testId":"AC-10","uuid":"35b5f91c-cb8d-4c6b-8761-01e5e58b8285","test":"Determine if the number of concurrent sessions for each [SELECTED PARAMETER VALUE(S): account and/or account types ] is limited to [SELECTED PARAMETER VALUE(S): number ].Device locks are temporary actions taken to prevent logical access to organizational systems when users stop work and move away from the immediate vicinity of those systems but do not want to log out because of the temporary nature of their absences. Device locks can be implemented at the operating system level or at the application level. A proximity lock may be used to initiate the device lock (e.g., via a Bluetooth-enabled device or dongle). User-initiated device locking is behavior or policy-based and, as such, requires users to take physical action to initiate the device lock. Device locks are not an acceptable substitute for logging out of systems, such as when organizations require users to log out at the end of workdays.
","uuid":"728de5e1-7b73-4d33-ae11-7c7a4f167277","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"bdcdae40-d723-488f-a396-a707d7848948","text":"[Selection (one or more): initiating a device lock after [(NESTED PARAMETER) Assignment for ac-11_odp.02: time period] of inactivity; requiring the user to initiate a device lock before leaving the system unattended]","parameterId":"ac-11_odp.01","default":"[Selection (one or more): initiating a device lock after [(NESTED PARAMETER) Assignment for ac-11_odp.02: time period] of inactivity; requiring the user to initiate a device lock before leaving the system unattended]"},{"constraints":"","displayName":"","guidance":"","uuid":"1592c687-967f-4bcb-914e-6047273e6020","text":"time period","parameterId":"ac-11_odp.02","default":" [Assignment: organization defined time period] "}],"subControls":"","tests":[{"testId":"AC-11a.","uuid":"c3a8ccb3-d1cc-4feb-a38b-baab4dc1b7b8","test":"Determine if further access to the system is prevented by [SELECTED PARAMETER VALUE(S): [Selection (one or more): initiating a device lock after [(NESTED PARAMETER) Assignment for ac-11_odp.02: time period] of inactivity; requiring the user to initiate a device lock before leaving the system unattended] ];The pattern-hiding display can include static or dynamic images, such as patterns used with screen savers, photographic images, solid colors, clock, battery life indicator, or a blank screen with the caveat that controlled unclassified information is not displayed.
","uuid":"42bf1937-a95c-412d-8e05-5ab3b092edf4","family":"Access Control","parameters":[],"subControls":"","tests":[{"testId":"AC-11(01)","uuid":"6e9702bc-3abc-42c6-9297-971f10a38110","test":"Determine if information previously visible on the display is concealed, via device lock, with a publicly viewable image.Session termination addresses the termination of user-initiated logical sessions (in contrast to SC-10 , which addresses the termination of network connections associated with communications sessions (i.e., network disconnect)). A logical session (for local, network, and remote access) is initiated whenever a user (or process acting on behalf of a user) accesses an organizational system. Such user sessions can be terminated without terminating network sessions. Session termination ends all processes associated with a user’s logical session except for those processes that are specifically created by the user (i.e., session owner) to continue after the session is terminated. Conditions or trigger events that require automatic termination of the session include organization-defined periods of user inactivity, targeted responses to certain types of incidents, or time-of-day restrictions on system use.
","uuid":"72610597-d37b-4f3c-9c7c-5d8fffd2a770","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"a8fe3b05-3c01-4792-bf81-7e727d1d0ecd","text":"conditions or trigger events","parameterId":"ac-12_odp","default":" [Assignment: organization defined conditions or trigger events] "}],"subControls":"","tests":[{"testId":"AC-12","uuid":"1a49b3bd-48bd-40a2-86d9-007020f88c2b","test":"Determine if a user session is automatically terminated after [SELECTED PARAMETER VALUE(S): conditions or trigger events ].Information resources to which users gain access via authentication include local workstations, databases, and password-protected websites or web-based services.
","uuid":"8c79fd96-fb00-4ddf-aca4-52b3eebda2b2","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"2cde5165-0a36-4d1b-9dd1-f333491e3f3c","text":"information resources","parameterId":"ac-12.01_odp","default":" [Assignment: organization defined information resources] "}],"subControls":"","tests":[{"testId":"AC-12(01)","uuid":"6f7e6e0a-8dbb-4a89-ad39-40d7074198ae","test":"Determine if a logout capability is provided for user-initiated communications sessions whenever authentication is used to gain access to [SELECTED PARAMETER VALUE(S): information resources ].Logout messages for web access can be displayed after authenticated sessions have been terminated. However, for certain types of sessions, including file transfer protocol (FTP) sessions, systems typically send logout messages as final messages prior to terminating sessions.
","uuid":"ed15f0d1-8816-4dc0-a1dd-34e6ca2a36fa","family":"Access Control","parameters":[],"subControls":"","tests":[{"testId":"AC-12(02)","uuid":"072cd152-b191-4a30-be1b-28602366f42c","test":"Determine if an explicit logout message is displayed to users indicating the termination of authenticated communication sessions.To increase usability, notify users of pending session termination and prompt users to continue the session. The pending session termination time period is based on the parameters defined in the AC-12 base control.
","uuid":"7d01f0d5-5ab2-4f85-aaff-b4746243e1a1","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"ac29393d-40d2-4ba0-adfe-1f0690d81931","text":"time","parameterId":"ac-12.03_odp","default":" [Assignment: organization defined time] "}],"subControls":"","tests":[{"testId":"AC-12(03)","uuid":"23b46c6d-6a29-4a42-a614-22717a8b1eb0","test":"Determine if an explicit message to users is displayed indicating that the session will end in [SELECTED PARAMETER VALUE(S): time ].Specific user actions may be permitted without identification or authentication if organizations determine that identification and authentication are not required for the specified user actions. Organizations may allow a limited number of user actions without identification or authentication, including when individuals access public websites or other publicly accessible federal systems, when individuals use mobile phones to receive calls, or when facsimiles are received. Organizations identify actions that normally require identification or authentication but may, under certain circumstances, allow identification or authentication mechanisms to be bypassed. Such bypasses may occur, for example, via a software-readable physical switch that commands bypass of the logon functionality and is protected from accidental or unmonitored use. Permitting actions without identification or authentication does not apply to situations where identification and authentication have already occurred and are not repeated but rather to situations where identification and authentication have not yet occurred. Organizations may decide that there are no user actions that can be performed on organizational systems without identification and authentication, and therefore, the value for the assignment operation can be none.
\n
Information is represented internally within systems using abstractions known as data structures. Internal data structures can represent different types of entities, both active and passive. Active entities, also known as subjects, are typically associated with individuals, devices, or processes acting on behalf of individuals. Passive entities, also known as objects, are typically associated with data structures, such as records, buffers, tables, files, inter-process pipes, and communications ports. Security attributes, a form of metadata, are abstractions that represent the basic properties or characteristics of active and passive entities with respect to safeguarding information. Privacy attributes, which may be used independently or in conjunction with security attributes, represent the basic properties or characteristics of active or passive entities with respect to the management of personally identifiable information. Attributes can be either explicitly or implicitly associated with the information contained in organizational systems or system components.
Attributes may be associated with active entities (i.e., subjects) that have the potential to send or receive information, cause information to flow among objects, or change the system state. These attributes may also be associated with passive entities (i.e., objects) that contain or receive information. The association of attributes to subjects and objects by a system is referred to as binding and is inclusive of setting the attribute value and the attribute type. Attributes, when bound to data or information, permit the enforcement of security and privacy policies for access control and information flow control, including data retention limits, permitted uses of personally identifiable information, and identification of personal information within data objects. Such enforcement occurs through organizational processes or system functions or mechanisms. The binding techniques implemented by systems affect the strength of attribute binding to information. Binding strength and the assurance associated with binding techniques play important parts in the trust that organizations have in the information flow enforcement process. The binding techniques affect the number and degree of additional reviews required by organizations. The content or assigned values of attributes can directly affect the ability of individuals to access organizational information.
Organizations can define the types of attributes needed for systems to support missions or business functions. There are many values that can be assigned to a security attribute. By specifying the permitted attribute ranges and values, organizations ensure that attribute values are meaningful and relevant. Labeling refers to the association of attributes with the subjects and objects represented by the internal data structures within systems. This facilitates system-based enforcement of information security and privacy policies. Labels include classification of information in accordance with legal and compliance requirements (e.g., top secret, secret, confidential, controlled unclassified), information impact level; high value asset information, access authorizations, nationality; data life cycle protection (i.e., encryption and data expiration), personally identifiable information processing permissions, including individual consent to personally identifiable information processing, and contractor affiliation. A related term to labeling is marking. Marking refers to the association of attributes with objects in a human-readable form and displayed on system media. Marking enables manual, procedural, or process-based enforcement of information security and privacy policies. Security and privacy labels may have the same value as media markings (e.g., top secret, secret, confidential). See MP-3 (Media Marking).
","uuid":"08cfddee-2e49-4a2a-bb03-7f5bb7d67b9e","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"aa8dca64-4de3-45ff-ad10-b3936decd116","text":"organization-defined types of security and privacy attributes","parameterId":"ac-16_prm_1","default":" [Assignment: organization-defined types of security and privacy attributes] "},{"constraints":"","displayName":"","guidance":"","uuid":"5a0265ca-dc62-4ede-942a-53cebbd10453","text":"organization-defined security and privacy attribute values","parameterId":"ac-16_prm_2","default":" [Assignment: organization-defined security and privacy attribute values] "},{"constraints":"","displayName":"","guidance":"","uuid":"cb48fb11-32c9-492f-8b97-0dc0d488541c","text":"organization-defined systems","parameterId":"ac-16_prm_3","default":" [Assignment: organization-defined systems] "},{"constraints":"","displayName":"","guidance":"","uuid":"953cfe10-8eef-4953-929c-0920db54c34e","text":"organization-defined security and privacy attributes","parameterId":"ac-16_prm_4","default":" [Assignment: organization-defined security and privacy attributes] "},{"constraints":"","displayName":"","guidance":"","uuid":"a7d2872b-70cf-4c39-9bdc-ce7458020e5f","text":"organization-defined security and privacy attributes","parameterId":"ac-16_prm_6","default":" [Assignment: organization-defined security and privacy attributes] "},{"constraints":"","displayName":"","guidance":"","uuid":"06b32819-18f2-4419-9944-7e1c4f054440","text":"organization-defined frequency","parameterId":"ac-16_prm_7","default":" [Assignment: organization-defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"8a2de31d-a05a-420f-ba6d-b7fc6203b035","text":"types of security attributes","parameterId":"ac-16_odp.01","default":" [Assignment: organization defined types of security attributes] "},{"constraints":"","displayName":"","guidance":"","uuid":"27d83c05-439e-4113-a80d-d2b0e8c2382a","text":"types of privacy attributes","parameterId":"ac-16_odp.02","default":" [Assignment: organization defined types of privacy attributes] "},{"constraints":"","displayName":"","guidance":"","uuid":"5ea24611-d460-4ef4-883a-caa54827bca1","text":"security attribute values","parameterId":"ac-16_odp.03","default":" [Assignment: organization defined security attribute values] "},{"constraints":"","displayName":"","guidance":"","uuid":"be0f2089-8aee-4b1e-96c8-cd45038199a2","text":"privacy attribute values","parameterId":"ac-16_odp.04","default":" [Assignment: organization defined privacy attribute values] "},{"constraints":"","displayName":"","guidance":"","uuid":"92e0c605-c5d1-48cd-a888-dc42a0b3f01c","text":"systems","parameterId":"ac-16_odp.05","default":" [Assignment: organization defined systems] "},{"constraints":"","displayName":"","guidance":"","uuid":"c03012ee-df00-46be-94ec-4252d485fe3f","text":"systems","parameterId":"ac-16_odp.06","default":" [Assignment: organization defined systems] "},{"constraints":"","displayName":"","guidance":"","uuid":"350fd049-4c73-4abb-b497-48927c629fe5","text":"security attributes","parameterId":"ac-16_odp.07","default":" [Assignment: organization defined security attributes] "},{"constraints":"","displayName":"","guidance":"","uuid":"deff0472-314a-49df-afbd-d98b1b1fef81","text":"privacy attributes","parameterId":"ac-16_odp.08","default":" [Assignment: organization defined privacy attributes] "},{"constraints":"","displayName":"","guidance":"","uuid":"cc0a5f17-acd5-4ff4-b5fc-1d8eec7d8622","text":"attribute values or ranges","parameterId":"ac-16_odp.09","default":" [Assignment: organization defined attribute values or ranges] "},{"constraints":"","displayName":"","guidance":"","uuid":"4413ef4c-6393-4fa1-b135-f4d765c9ec77","text":"frequency","parameterId":"ac-16_odp.10","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"639347af-e475-4fa2-bfcc-9f6f38ec4000","text":"frequency","parameterId":"ac-16_odp.11","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"AC-16a.[01]","uuid":"7bc5a2ea-ab77-4ff3-b9f8-7c061f5a7f19","test":"Determine if the means to associate [SELECTED PARAMETER VALUE(S): types of security attributes ] with [SELECTED PARAMETER VALUE(S): security attribute values ] for information in storage, in process, and/or in transmission are provided;Dynamic association of attributes is appropriate whenever the security or privacy characteristics of information change over time. Attributes may change due to information aggregation issues (i.e., characteristics of individual data elements are different from the combined elements), changes in individual access authorizations (i.e., privileges), changes in the security category of information, or changes in security or privacy policies. Attributes may also change situationally.
","uuid":"3c547db3-7f9b-46e5-9ceb-f40fdb54273f","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"39538b2f-15aa-4040-ab83-91bccf397a5a","text":"organization-defined subjects and objects","parameterId":"ac-16.1_prm_1","default":" [Assignment: organization-defined subjects and objects] "},{"constraints":"","displayName":"","guidance":"","uuid":"68bd4f82-91e7-4666-8946-ad44620d9f96","text":"organization-defined security and privacy policies","parameterId":"ac-16.1_prm_2","default":" [Assignment: organization-defined security and privacy policies] "},{"constraints":"","displayName":"","guidance":"","uuid":"0c9ac127-31b9-4653-be8b-2d9941e524ed","text":"subjects","parameterId":"ac-16.01_odp.01","default":" [Assignment: organization defined subjects] "},{"constraints":"","displayName":"","guidance":"","uuid":"fa08053a-428e-401b-9dad-1b21f8f8cee6","text":"objects","parameterId":"ac-16.01_odp.02","default":" [Assignment: organization defined objects] "},{"constraints":"","displayName":"","guidance":"","uuid":"a1109b5a-e4d0-41ce-a810-322db4c4777d","text":"subjects","parameterId":"ac-16.01_odp.03","default":" [Assignment: organization defined subjects] "},{"constraints":"","displayName":"","guidance":"","uuid":"70f8aaa1-3820-4972-a3aa-e16df33ec7b3","text":"objects","parameterId":"ac-16.01_odp.04","default":" [Assignment: organization defined objects] "},{"constraints":"","displayName":"","guidance":"","uuid":"9b57758d-d2e4-4ce2-87c6-b5c5a0a13d7d","text":"security policies","parameterId":"ac-16.01_odp.05","default":" [Assignment: organization defined security policies] "},{"constraints":"","displayName":"","guidance":"","uuid":"52e4a94b-6f46-440b-bb55-965d0b072898","text":"privacy policies","parameterId":"ac-16.01_odp.06","default":" [Assignment: organization defined privacy policies] "}],"subControls":"","tests":[{"testId":"AC-16(01)[01]","uuid":"d84190bc-793f-4bfe-b7ca-a5b6d7224c7e","test":"Determine if security attributes are dynamically associated with [SELECTED PARAMETER VALUE(S): subjects ] in accordance with the following security policies as information is created and combined: [SELECTED PARAMETER VALUE(S): security policies ];The content or assigned values of attributes can directly affect the ability of individuals to access organizational information. Therefore, it is important for systems to be able to limit the ability to create or modify attributes to authorized individuals.
","uuid":"519b1741-b5d8-41a6-8b7e-71929d62b17e","family":"Access Control","parameters":[],"subControls":"","tests":[{"testId":"AC-16(02)[01]","uuid":"06b0e1eb-9aac-431c-92d2-3668d7113106","test":"Determine if authorized individuals (or processes acting on behalf of individuals) are provided with the capability to define or change the value of associated security attributes;Maintaining the association and integrity of security and privacy attributes to subjects and objects with sufficient assurance helps to ensure that the attribute associations can be used as the basis of automated policy actions. The integrity of specific items, such as security configuration files, may be maintained through the use of an integrity monitoring mechanism that detects anomalies and changes that deviate from known good
baselines. Automated policy actions include retention date expirations, access control decisions, information flow control decisions, and information disclosure decisions.
Systems, in general, provide the capability for privileged users to assign security and privacy attributes to system-defined subjects (e.g., users) and objects (e.g., directories, files, and ports). Some systems provide additional capability for general users to assign security and privacy attributes to additional objects (e.g., files, emails). The association of attributes by authorized individuals is described in the design documentation. The support provided by systems can include prompting users to select security and privacy attributes to be associated with information objects, employing automated mechanisms to categorize information with attributes based on defined policies, or ensuring that the combination of the security or privacy attributes selected is valid. Organizations consider the creation, deletion, or modification of attributes when defining auditable events.
","uuid":"62f51f35-4c16-461e-94b9-96a4373a622e","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"b0368848-cb6e-46f8-b57c-9b5a52be7f2c","text":"organization-defined security and privacy attributes","parameterId":"ac-16.4_prm_1","default":" [Assignment: organization-defined security and privacy attributes] "},{"constraints":"","displayName":"","guidance":"","uuid":"6215a85a-4dac-4201-b2f2-222c77029ba1","text":"organization-defined subjects and objects","parameterId":"ac-16.4_prm_2","default":" [Assignment: organization-defined subjects and objects] "},{"constraints":"","displayName":"","guidance":"","uuid":"6f04e98f-5039-422f-8351-f956028a84ab","text":"security attributes","parameterId":"ac-16.04_odp.01","default":" [Assignment: organization defined security attributes] "},{"constraints":"","displayName":"","guidance":"","uuid":"ad345961-1990-42d2-b648-ba5362549ced","text":"security attributes","parameterId":"ac-16.04_odp.02","default":" [Assignment: organization defined security attributes] "},{"constraints":"","displayName":"","guidance":"","uuid":"d4bbd972-421d-4668-bc06-f3f1be724bd7","text":"privacy attributes","parameterId":"ac-16.04_odp.03","default":" [Assignment: organization defined privacy attributes] "},{"constraints":"","displayName":"","guidance":"","uuid":"4dee05f3-dd5f-46d5-85b5-5832851bd07d","text":"privacy attributes","parameterId":"ac-16.04_odp.04","default":" [Assignment: organization defined privacy attributes] "},{"constraints":"","displayName":"","guidance":"","uuid":"10c9ee35-8b0a-415b-bd4c-f9abd750e235","text":"subjects","parameterId":"ac-16.04_odp.05","default":" [Assignment: organization defined subjects] "},{"constraints":"","displayName":"","guidance":"","uuid":"2e27b668-3a34-4488-9415-e1290a8c3189","text":"objects","parameterId":"ac-16.04_odp.06","default":" [Assignment: organization defined objects] "},{"constraints":"","displayName":"","guidance":"","uuid":"dccb31a4-2929-487a-a37b-e1d15bc50556","text":"subjects","parameterId":"ac-16.04_odp.07","default":" [Assignment: organization defined subjects] "},{"constraints":"","displayName":"","guidance":"","uuid":"4d1be412-2e0d-4294-85fb-69bc6fc66670","text":"objects","parameterId":"ac-16.04_odp.08","default":" [Assignment: organization defined objects] "}],"subControls":"","tests":[{"testId":"AC-16(04)[01]","uuid":"c56e8747-c99a-4e07-a342-a96f91c4dbb2","test":"Determine if authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [SELECTED PARAMETER VALUE(S): security attributes ] with [SELECTED PARAMETER VALUE(S): subjects ];System outputs include printed pages, screens, or equivalent items. System output devices include printers, notebook computers, video displays, smart phones, and tablets. To mitigate the risk of unauthorized exposure of information (e.g., shoulder surfing), the outputs display full attribute values when unmasked by the subscriber.
","uuid":"0d25c5c5-1284-4b3c-9f7a-140c281591d6","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"7a53f59d-f1f8-45bc-be38-c973ed500ed4","text":"instructions","parameterId":"ac-16.05_odp.01","default":" [Assignment: organization defined instructions] "},{"constraints":"","displayName":"","guidance":"","uuid":"d0438c59-8a75-4156-a1da-f39771e609ad","text":"naming conventions","parameterId":"ac-16.05_odp.02","default":" [Assignment: organization defined naming conventions] "}],"subControls":"","tests":[{"testId":"AC-16(05)[01]","uuid":"63b6effa-9b34-42a0-997e-4bd30cfd4f82","test":"Determine if security attributes are displayed in human-readable form on each object that the system transmits to output devices to identify [SELECTED PARAMETER VALUE(S): instructions ] using [SELECTED PARAMETER VALUE(S): naming conventions ];Maintaining attribute association requires individual users (as opposed to the system) to maintain associations of defined security and privacy attributes with subjects and objects.
","uuid":"5e5985c3-1a50-4068-850b-feea3cd0d891","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"b3c44638-b555-4190-96ba-98a586f9e143","text":"organization-defined security and privacy attributes","parameterId":"ac-16.6_prm_1","default":" [Assignment: organization-defined security and privacy attributes] "},{"constraints":"","displayName":"","guidance":"","uuid":"3e60345f-5586-4447-bcb1-aa688ed50b1a","text":"organization-defined subjects and objects","parameterId":"ac-16.6_prm_2","default":" [Assignment: organization-defined subjects and objects] "},{"constraints":"","displayName":"","guidance":"","uuid":"f286f0bf-3f0f-41e5-8cd4-bd552021c3bb","text":"organization-defined security and privacy policies","parameterId":"ac-16.6_prm_3","default":" [Assignment: organization-defined security and privacy policies] "},{"constraints":"","displayName":"","guidance":"","uuid":"32d69ed0-6f2a-4795-b4c1-b6cd58e1a935","text":"security attributes","parameterId":"ac-16.06_odp.01","default":" [Assignment: organization defined security attributes] "},{"constraints":"","displayName":"","guidance":"","uuid":"0533a15e-a832-4718-90dd-3b8e6379457a","text":"security attributes","parameterId":"ac-16.06_odp.02","default":" [Assignment: organization defined security attributes] "},{"constraints":"","displayName":"","guidance":"","uuid":"2255b358-b15c-4c8c-af66-8c140c880b12","text":"privacy attributes","parameterId":"ac-16.06_odp.03","default":" [Assignment: organization defined privacy attributes] "},{"constraints":"","displayName":"","guidance":"","uuid":"d1828d17-0b95-42eb-b399-9ae0f03f1721","text":"privacy attributes","parameterId":"ac-16.06_odp.04","default":" [Assignment: organization defined privacy attributes] "},{"constraints":"","displayName":"","guidance":"","uuid":"5e7857e7-347b-4604-aff5-ee427e3e2c54","text":"subjects","parameterId":"ac-16.06_odp.05","default":" [Assignment: organization defined subjects] "},{"constraints":"","displayName":"","guidance":"","uuid":"a45272e6-e4ed-4704-b6eb-12c6b16562ad","text":"objects","parameterId":"ac-16.06_odp.06","default":" [Assignment: organization defined objects] "},{"constraints":"","displayName":"","guidance":"","uuid":"adcf536b-4f24-4296-98fc-d9600e9af3ef","text":"subjects","parameterId":"ac-16.06_odp.07","default":" [Assignment: organization defined subjects] "},{"constraints":"","displayName":"","guidance":"","uuid":"643edbb0-73da-4cde-9921-c744066fa432","text":"objects","parameterId":"ac-16.06_odp.08","default":" [Assignment: organization defined objects] "},{"constraints":"","displayName":"","guidance":"","uuid":"7ca90d68-fb85-4394-969a-ee2174a7277a","text":"security policies","parameterId":"ac-16.06_odp.09","default":" [Assignment: organization defined security policies] "},{"constraints":"","displayName":"","guidance":"","uuid":"0a3b0bf1-d989-4269-825d-c8702fe96da8","text":"privacy policies","parameterId":"ac-16.06_odp.10","default":" [Assignment: organization defined privacy policies] "}],"subControls":"","tests":[{"testId":"AC-16(06)[01]","uuid":"9df5516a-5122-4445-8e40-72f460e24efc","test":"Determine if personnel are required to associate and maintain the association of [SELECTED PARAMETER VALUE(S): security attributes ] with [SELECTED PARAMETER VALUE(S): subjects ] in accordance with [SELECTED PARAMETER VALUE(S): security policies ];To enforce security and privacy policies across multiple system components in distributed systems, organizations provide a consistent interpretation of security and privacy attributes employed in access enforcement and flow enforcement decisions. Organizations can establish agreements and processes to help ensure that distributed system components implement attributes with consistent interpretations in automated access enforcement and flow enforcement actions.
","uuid":"9ba91b3b-72c9-4b4d-9fc6-b791ce983307","family":"Access Control","parameters":[],"subControls":"","tests":[{"testId":"AC-16(07)[01]","uuid":"46df4fd6-4843-4a49-ba68-8f77f26404aa","test":"Determine if a consistent interpretation of security attributes transmitted between distributed system components is provided;The association of security and privacy attributes to information within systems is important for conducting automated access enforcement and flow enforcement actions. The association of such attributes to information (i.e., binding) can be accomplished with technologies and techniques that provide different levels of assurance. For example, systems can cryptographically bind attributes to information using digital signatures that support cryptographic keys protected by hardware devices (sometimes known as hardware roots of trust).
","uuid":"9d77e1a6-490b-433f-987c-8c761bca5b65","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"059faaaa-31ba-4030-b33f-a02943dd8754","text":"organization-defined techniques and technologies","parameterId":"ac-16.8_prm_1","default":" [Assignment: organization-defined techniques and technologies] "},{"constraints":"","displayName":"","guidance":"","uuid":"70a35926-046c-43fb-908a-538b85ad49de","text":"techniques and technologies","parameterId":"ac-16.08_odp.01","default":" [Assignment: organization defined techniques and technologies] "},{"constraints":"","displayName":"","guidance":"","uuid":"d6923111-30db-42a4-9eff-1d2703c975be","text":"techniques and technologies","parameterId":"ac-16.08_odp.02","default":" [Assignment: organization defined techniques and technologies] "}],"subControls":"","tests":[{"testId":"AC-16(08)[01]","uuid":"a99bece0-c426-4c79-a3e7-e6056d69a59c","test":"Determine if [SELECTED PARAMETER VALUE(S): techniques and technologies ] are implemented in associating security attributes to information;A regrading mechanism is a trusted process authorized to re-classify and re-label data in accordance with a defined policy exception. Validated regrading mechanisms are used by organizations to provide the requisite levels of assurance for attribute reassignment activities. The validation is facilitated by ensuring that regrading mechanisms are single purpose and of limited function. Since security and privacy attribute changes can directly affect policy enforcement actions, implementing trustworthy regrading mechanisms is necessary to help ensure that such mechanisms perform in a consistent and correct mode of operation.
","uuid":"f0fcb76a-34d8-4f01-abb3-1bffb9aec7e5","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"ee0d6e25-1a4b-43b2-91da-6e5670ba7dcb","text":"organization-defined techniques or procedures","parameterId":"ac-16.9_prm_1","default":" [Assignment: organization-defined techniques or procedures] "},{"constraints":"","displayName":"","guidance":"","uuid":"9820a0aa-cd37-4f76-9cf1-d0f0ab9f6d33","text":"techniques or procedures","parameterId":"ac-16.09_odp.01","default":" [Assignment: organization defined techniques or procedures] "},{"constraints":"","displayName":"","guidance":"","uuid":"932afaba-0f08-40e0-9c72-7a091bfeda74","text":"techniques or procedures","parameterId":"ac-16.09_odp.02","default":" [Assignment: organization defined techniques or procedures] "}],"subControls":"","tests":[{"testId":"AC-16(09)[01]","uuid":"8d0708ec-8e1e-4f95-8a46-afe16997be9f","test":"Determine if security attributes associated with information are changed only via regrading mechanisms validated using [SELECTED PARAMETER VALUE(S): techniques or procedures ];The content or assigned values of security and privacy attributes can directly affect the ability of individuals to access organizational information. Thus, it is important for systems to be able to limit the ability to create or modify the type and value of attributes available for association with subjects and objects to authorized individuals only.
","uuid":"a87b8cb7-04fc-4822-985f-48825cc7c9ef","family":"Access Control","parameters":[],"subControls":"","tests":[{"testId":"AC-16(10)[01]","uuid":"adcd4ac7-3532-4dc3-9585-957caaf3a65b","test":"Determine if authorized individuals are provided with the capability to define or change the type and value of security attributes available for association with subjects and objects;Remote access is access to organizational systems (or processes acting on behalf of users) that communicate through external networks such as the Internet. Types of remote access include dial-up, broadband, and wireless. Organizations use encrypted virtual private networks (VPNs) to enhance confidentiality and integrity for remote connections. The use of encrypted VPNs provides sufficient assurance to the organization that it can effectively treat such connections as internal networks if the cryptographic mechanisms used are implemented in accordance with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Still, VPN connections traverse external networks, and the encrypted VPN does not enhance the availability of remote connections. VPNs with encrypted tunnels can also affect the ability to adequately monitor network communications traffic for malicious code. Remote access controls apply to systems other than public web servers or systems designed for public access. Authorization of each remote access type addresses authorization prior to allowing remote access without specifying the specific formats for such authorization. While organizations may use information exchange and system connection security agreements to manage remote access connections to other systems, such agreements are addressed as part of CA-3 . Enforcing access restrictions for remote access is addressed via AC-3.
","uuid":"740a1d12-878a-49fe-a3d1-9565186842e4","family":"Access Control","parameters":[],"subControls":"","tests":[{"testId":"AC-17a.[01]","uuid":"831a8527-a8ea-48b5-8f9f-d656b42efcf8","test":"Determine if usage restrictions are established and documented for each type of remote access allowed;Monitoring and control of remote access methods allows organizations to detect attacks and help ensure compliance with remote access policies by auditing the connection activities of remote users on a variety of system components, including servers, notebook computers, workstations, smart phones, and tablets. Audit logging for remote access is enforced by AU-2 . Audit events are defined in AU-2a.
","uuid":"073de708-2a36-4e7f-8aca-e92d1c173076","family":"Access Control","parameters":[],"subControls":"","tests":[{"testId":"AC-17(01)[01]","uuid":"4d54bb19-a9f2-408f-b24f-5dc69d38aa3a","test":"Determine if automated mechanisms are employed to monitor remote access methods;Virtual private networks can be used to protect the confidentiality and integrity of remote access sessions. Transport Layer Security (TLS) is an example of a cryptographic protocol that provides end-to-end communications security over networks and is used for Internet communications and online transactions.
","uuid":"a27ca81c-4c44-46b6-aa8f-3207f53af792","family":"Access Control","parameters":[],"subControls":"","tests":[{"testId":"AC-17(02)","uuid":"b079081a-a0b9-4e2c-bf2c-131e90746653","test":"Determine if cryptographic mechanisms are implemented to protect the confidentiality and integrity of remote access sessions.Organizations consider the Trusted Internet Connections (TIC) initiative DHS TIC requirements for external network connections since limiting the number of access control points for remote access reduces attack surfaces.
","uuid":"df6cc611-3bd6-471a-a518-711fdc275dd7","family":"Access Control","parameters":[],"subControls":"","tests":[{"testId":"AC-17(03)","uuid":"e82909b0-0067-477d-819f-31d7e558919b","test":"Determine if remote accesses are routed through authorized and managed network access control points.Remote access to systems represents a significant potential vulnerability that can be exploited by adversaries. As such, restricting the execution of privileged commands and access to security-relevant information via remote access reduces the exposure of the organization and the susceptibility to threats by adversaries to the remote access capability.
","uuid":"dd1849b3-cdd6-4283-adcb-83e09cc9ada6","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"17026de6-9402-43a6-bf6c-5c6fde3f04c0","text":"organization-defined needs","parameterId":"ac-17.4_prm_1","default":" [Assignment: organization-defined needs] "},{"constraints":"","displayName":"","guidance":"","uuid":"4d0bf424-0271-4880-84f6-66dcb9102f91","text":"needs requiring remote access","parameterId":"ac-17.04_odp.01","default":" [Assignment: organization defined needs requiring remote access] "},{"constraints":"","displayName":"","guidance":"","uuid":"398708ae-e585-43f1-8581-41982e4900b9","text":"needs requiring remote access","parameterId":"ac-17.04_odp.02","default":" [Assignment: organization defined needs requiring remote access] "}],"subControls":"","tests":[{"testId":"AC-17(04)(a)[01]","uuid":"4e7c674c-4563-46db-ac57-d595efac1695","test":"Determine if the execution of privileged commands via remote access is authorized only in a format that provides assessable evidence;Remote access to organizational information by non-organizational entities can increase the risk of unauthorized use and disclosure about remote access mechanisms. The organization considers including remote access requirements in the information exchange agreements with other organizations, as applicable. Remote access requirements can also be included in rules of behavior (see PL-4 ) and access agreements (see PS-6).
","uuid":"a7c1d5c7-604e-4872-b1d9-942a82a4214f","family":"Access Control","parameters":[],"subControls":"","tests":[{"testId":"AC-17(06)","uuid":"bb826912-7dd8-4098-a916-95e2363beea3","test":"Determine if information about remote access mechanisms is protected from unauthorized use and disclosure.The speed of system disconnect or disablement varies based on the criticality of missions or business functions and the need to eliminate immediate or future remote access to systems.
","uuid":"30442fdd-ee23-45e3-b576-d0b980193d9b","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"8fc96642-36a1-4f12-95cd-ad05612e4d5d","text":"time period","parameterId":"ac-17.09_odp","default":" [Assignment: organization defined time period] "}],"subControls":"","tests":[{"testId":"AC-17(09)","uuid":"2a7b0a8f-f9b1-4ca2-883e-39d1835c92c7","test":"Determine if the capability to disconnect or disable remote access to the system within [SELECTED PARAMETER VALUE(S): time period ] is provided.Authenticating remote commands protects against unauthorized commands and the replay of authorized commands. The ability to authenticate remote commands is important for remote systems for which loss, malfunction, misdirection, or exploitation would have immediate or serious consequences, such as injury, death, property damage, loss of high value assets, failure of mission or business functions, or compromise of classified or controlled unclassified information. Authentication mechanisms for remote commands ensure that systems accept and execute commands in the order intended, execute only authorized commands, and reject unauthorized commands. Cryptographic mechanisms can be used, for example, to authenticate remote commands.
","uuid":"e65896f7-0951-4d2d-8660-830cbee3bc10","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"91307758-0c6b-4702-a8cc-9d19abe1e25b","text":"mechanisms","parameterId":"ac-17.10_odp.01","default":" [Assignment: organization defined mechanisms] "},{"constraints":"","displayName":"","guidance":"","uuid":"382baf65-80f0-4d60-ae6f-e84c4ca4e516","text":"remote commands","parameterId":"ac-17.10_odp.02","default":" [Assignment: organization defined remote commands] "}],"subControls":"","tests":[{"testId":"AC-17(10)","uuid":"f5f36458-1bf1-4711-b89d-abd8da245547","test":"Determine if [SELECTED PARAMETER VALUE(S): mechanisms ] are implemented to authenticate [SELECTED PARAMETER VALUE(S): remote commands ].Wireless technologies include microwave, packet radio (ultra-high frequency or very high frequency), 802.11x, and Bluetooth. Wireless networks use authentication protocols that provide authenticator protection and mutual authentication.
","uuid":"2604b122-4804-4d81-8d17-84039eb8a8c5","family":"Access Control","parameters":[],"subControls":"","tests":[{"testId":"AC-18a.[01]","uuid":"235a4bd0-4779-4ae1-ae11-c03957c72ac6","test":"Determine if configuration requirements are established for each type of wireless access;Wireless networking capabilities represent a significant potential vulnerability that can be exploited by adversaries. To protect systems with wireless access points, strong authentication of users and devices along with strong encryption can reduce susceptibility to threats by adversaries involving wireless technologies.
","uuid":"8372a2bd-e547-4f0c-9649-ea31bb713c7d","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"e086496b-82fa-4d4f-9335-17ce168d4a65","text":"[Selection (one or more): users; devices]","parameterId":"ac-18.01_odp","default":"[Selection (one or more): users; devices]"}],"subControls":"","tests":[{"testId":"AC-18(01)[01]","uuid":"e2e6d3f2-8cfc-4817-aed3-f0a475c25ab8","test":"Determine if wireless access to the system is protected using authentication of [SELECTED PARAMETER VALUE(S): [Selection (one or more): users; devices] ];Wireless networking capabilities that are embedded within system components represent a significant potential vulnerability that can be exploited by adversaries. Disabling wireless capabilities when not needed for essential organizational missions or functions can reduce susceptibility to threats by adversaries involving wireless technologies.
","uuid":"b5ce76ba-86b3-4f16-b546-a0fdec77038d","family":"Access Control","parameters":[],"subControls":"","tests":[{"testId":"AC-18(03)","uuid":"cb295c3f-10a2-40d3-95ee-6c6a8b4b3726","test":"Determine if when not intended for use, wireless networking capabilities embedded within system components are disabled prior to issuance and deployment.Organizational authorizations to allow selected users to configure wireless networking capabilities are enforced, in part, by the access enforcement mechanisms employed within organizational systems.
","uuid":"02a043ca-c40f-442e-b2ab-874481502f9e","family":"Access Control","parameters":[],"subControls":"","tests":[{"testId":"AC-18(04)[01]","uuid":"65aca6d2-2923-4f97-b5b0-f93743ceadca","test":"Determine if users allowed to independently configure wireless networking capabilities are identified;Actions that may be taken to limit unauthorized use of wireless communications outside of organization-controlled boundaries include reducing the power of wireless transmissions so that the transmissions are less likely to emit a signal that can be captured outside of the physical perimeters of the organization, employing measures such as emissions security to control wireless emanations, and using directional or beamforming antennas that reduce the likelihood that unintended receivers will be able to intercept signals. Prior to taking such mitigating actions, organizations can conduct periodic wireless surveys to understand the radio frequency profile of organizational systems as well as other systems that may be operating in the area.
","uuid":"568b3c21-524d-4db3-90fc-d2e4469e85e7","family":"Access Control","parameters":[],"subControls":"","tests":[{"testId":"AC-18(05)[01]","uuid":"3a567f9c-ca3a-4ca0-9d95-6f8a9ef3863b","test":"Determine if radio antennas are selected to reduce the probability that signals from wireless access points can be received outside of organization-controlled boundaries;A mobile device is a computing device that has a small form factor such that it can easily be carried by a single individual; is designed to operate without a physical connection; possesses local, non-removable or removable data storage; and includes a self-contained power source. Mobile device functionality may also include voice communication capabilities, on-board sensors that allow the device to capture information, and/or built-in features for synchronizing local data with remote locations. Examples include smart phones and tablets. Mobile devices are typically associated with a single individual. The processing, storage, and transmission capability of the mobile device may be comparable to or merely a subset of notebook/desktop systems, depending on the nature and intended purpose of the device. Protection and control of mobile devices is behavior or policy-based and requires users to take physical action to protect and control such devices when outside of controlled areas. Controlled areas are spaces for which organizations provide physical or procedural controls to meet the requirements established for protecting information and systems.
Due to the large variety of mobile devices with different characteristics and capabilities, organizational restrictions may vary for the different classes or types of such devices. Usage restrictions and specific implementation guidance for mobile devices include configuration management, device identification and authentication, implementation of mandatory protective software, scanning devices for malicious code, updating virus protection software, scanning for critical software updates and patches, conducting primary operating system (and possibly other resident software) integrity checks, and disabling unnecessary hardware.
Usage restrictions and authorization to connect may vary among organizational systems. For example, the organization may authorize the connection of mobile devices to its network and impose a set of usage restrictions, while a system owner may withhold authorization for mobile device connection to specific applications or impose additional usage restrictions before allowing mobile device connections to a system. Adequate security for mobile devices goes beyond the requirements specified in AC-19 . Many safeguards for mobile devices are reflected in other controls. AC-20 addresses mobile devices that are not organization-controlled.
","uuid":"4e6007c9-550d-4154-813d-2e0ae06bb705","family":"Access Control","parameters":[],"subControls":"","tests":[{"testId":"AC-19a.[01]","uuid":"8c20ad07-3dfe-45c6-972f-16b2029ce4ae","test":"Determine if configuration requirements are established for organization-controlled mobile devices, including when such devices are outside of the controlled area;None.
","uuid":"ad5c7a7e-f9a1-4033-8889-c9fcc39572ff","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"9bf0a242-2a3d-4f37-a4e1-4a072cc1a52c","text":"security officials","parameterId":"ac-19.04_odp.01","default":" [Assignment: organization defined security officials] "},{"constraints":"","displayName":"","guidance":"","uuid":"5f5d4caf-efc3-4d7a-bc95-42d13702ef40","text":"security policies","parameterId":"ac-19.04_odp.02","default":" [Assignment: organization defined security policies] "}],"subControls":"","tests":[{"testId":"AC-19(04)(a)","uuid":"8ed154f6-9421-43ea-bc68-1498c0fb5b3f","test":"Determine if the use of unclassified mobile devices in facilities containing systems processing, storing, or transmitting classified information is prohibited unless specifically permitted by the authorizing official;Container-based encryption provides a more fine-grained approach to data and information encryption on mobile devices, including encrypting selected data structures such as files, records, or fields.
","uuid":"44d267f4-594f-4012-98e3-01771c56d52d","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"7fb33a1a-733e-4401-a665-c8dc81b4d164","text":"[Selection: full-device encryption; container-based encryption]","parameterId":"ac-19.05_odp.01","default":"[Selection: full-device encryption; container-based encryption]"},{"constraints":"","displayName":"","guidance":"","uuid":"d03a9b9c-b20a-41ee-8c88-789aa883d892","text":"mobile devices","parameterId":"ac-19.05_odp.02","default":" [Assignment: organization defined mobile devices] "}],"subControls":"","tests":[{"testId":"AC-19(05)","uuid":"f3a78289-c70c-43e4-b116-f28d35725df5","test":"Determine if [SELECTED PARAMETER VALUE(S): [Selection: full-device encryption; container-based encryption] ] is employed to protect the confidentiality and integrity of information on [SELECTED PARAMETER VALUE(S): mobile devices ].External systems are systems that are used by but not part of organizational systems, and for which the organization has no direct control over the implementation of required controls or the assessment of control effectiveness. External systems include personally owned systems, components, or devices; privately owned computing and communications devices in commercial or public facilities; systems owned or controlled by nonfederal organizations; systems managed by contractors; and federal information systems that are not owned by, operated by, or under the direct supervision or authority of the organization. External systems also include systems owned or operated by other components within the same organization and systems within the organization with different authorization boundaries. Organizations have the option to prohibit the use of any type of external system or prohibit the use of specified types of external systems, (e.g., prohibit the use of any external system that is not organizationally owned or prohibit the use of personally-owned systems).
For some external systems (i.e., systems operated by other organizations), the trust relationships that have been established between those organizations and the originating organization may be such that no explicit terms and conditions are required. Systems within these organizations may not be considered external. These situations occur when, for example, there are pre-existing information exchange agreements (either implicit or explicit) established between organizations or components or when such agreements are specified by applicable laws, executive orders, directives, regulations, policies, or standards. Authorized individuals include organizational personnel, contractors, or other individuals with authorized access to organizational systems and over which organizations have the authority to impose specific rules of behavior regarding system access. Restrictions that organizations impose on authorized individuals need not be uniform, as the restrictions may vary depending on trust relationships between organizations. Therefore, organizations may choose to impose different security restrictions on contractors than on state, local, or tribal governments.
External systems used to access public interfaces to organizational systems are outside the scope of AC-20 . Organizations establish specific terms and conditions for the use of external systems in accordance with organizational security policies and procedures. At a minimum, terms and conditions address the specific types of applications that can be accessed on organizational systems from external systems and the highest security category of information that can be processed, stored, or transmitted on external systems. If the terms and conditions with the owners of the external systems cannot be established, organizations may impose restrictions on organizational personnel using those external systems.
","uuid":"31774732-7665-4473-84e8-80783568967f","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"e7bf547c-1f25-40eb-b8da-52e1c5d88d96","text":"[Selection (one or more): establish [(NESTED PARAMETER) Assignment for ac-20_odp.02: terms and conditions]; identify [(NESTED PARAMETER) Assignment for ac-20_odp.03: controls asserted]]","parameterId":"ac-20_odp.01","default":"[Selection (one or more): establish [(NESTED PARAMETER) Assignment for ac-20_odp.02: terms and conditions]; identify [(NESTED PARAMETER) Assignment for ac-20_odp.03: controls asserted]]"},{"constraints":"","displayName":"","guidance":"","uuid":"40219bab-b949-4db9-9d9c-83efc037f8ab","text":"terms and conditions","parameterId":"ac-20_odp.02","default":" [Assignment: organization defined terms and conditions] "},{"constraints":"","displayName":"","guidance":"","uuid":"dbf327d4-cc90-4770-86af-1a43cde99667","text":"controls asserted","parameterId":"ac-20_odp.03","default":" [Assignment: organization defined controls asserted] "},{"constraints":"","displayName":"","guidance":"","uuid":"009d5696-29ca-4937-a93e-4a9b5464a1f9","text":"prohibited types of external systems","parameterId":"ac-20_odp.04","default":" [Assignment: organization defined prohibited types of external systems] "}],"subControls":"","tests":[{"testId":"AC-20a.1","uuid":"f8ce5790-341a-4248-867d-de651c707776","test":"Determine if [SELECTED PARAMETER VALUE(S): [Selection (one or more): establish [(NESTED PARAMETER) Assignment for ac-20_odp.02: terms and conditions]; identify [(NESTED PARAMETER) Assignment for ac-20_odp.03: controls asserted]] ] is/are consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems, allowing authorized individuals to access the system from external systems (if applicable);Limiting authorized use recognizes circumstances where individuals using external systems may need to access organizational systems. Organizations need assurance that the external systems contain the necessary controls so as not to compromise, damage, or otherwise harm organizational systems. Verification that the required controls have been implemented can be achieved by external, independent assessments, attestations, or other means, depending on the confidence level required by organizations.
","uuid":"c9d94995-b73a-4e7e-9ee9-6e6eade266e8","family":"Access Control","parameters":[],"subControls":"","tests":[{"testId":"AC-20(01)(a)","uuid":"e84232f2-e729-4456-87bd-95bab244720e","test":"Determine if authorized individuals are permitted to use an external system to access the system or to process, store, or transmit organization-controlled information only after 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 (if applicable);Limits on the use of organization-controlled portable storage devices in external systems include restrictions on how the devices may be used and under what conditions the devices may be used.
","uuid":"779166fb-b84c-494d-aa0f-c81af5b343ad","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"caf38c43-5781-4b3b-bd05-d3677e73b72e","text":"restrictions","parameterId":"ac-20.02_odp","default":" [Assignment: organization defined restrictions] "}],"subControls":"","tests":[{"testId":"AC-20(02)","uuid":"690611d2-91e5-44b0-9351-9bb923a97c26","test":"Determine if the use of organization-controlled portable storage devices by authorized individuals is restricted on external systems using [SELECTED PARAMETER VALUE(S): restrictions ].Non-organizationally owned systems or system components include systems or system components owned by other organizations as well as personally owned devices. There are potential risks to using non-organizationally owned systems or components. In some cases, the risk is sufficiently high as to prohibit such use (see AC-20 b. ). In other cases, the use of such systems or system components may be allowed but restricted in some way. Restrictions include requiring the implementation of approved controls prior to authorizing the connection of non-organizationally owned systems and components; limiting access to types of information, services, or applications; using virtualization techniques to limit processing and storage activities to servers or system components provisioned by the organization; and agreeing to the terms and conditions for usage. Organizations consult with the Office of the General Counsel regarding legal issues associated with using personally owned devices, including requirements for conducting forensic analyses during investigations after an incident.
","uuid":"79c03f73-9661-4563-82cf-7d0713e3d16a","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"34d4dce8-b228-42c6-84ae-715cbb74792a","text":"restrictions","parameterId":"ac-20.03_odp","default":" [Assignment: organization defined restrictions] "}],"subControls":"","tests":[{"testId":"AC-20(03)","uuid":"a55895ac-6c37-4561-9412-dd6efbaf8caa","test":"Determine if the use of non-organizationally owned systems or system components to process, store, or transmit organizational information is restricted using [SELECTED PARAMETER VALUE(S): restrictions ].Network-accessible storage devices in external systems include online storage devices in public, hybrid, or community cloud-based systems.
","uuid":"eb78b634-ebff-416f-87d0-c9833ac3839e","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"d6e463f8-3814-455b-8bcf-4ca8e6796345","text":"network-accessible storage devices","parameterId":"ac-20.04_odp","default":" [Assignment: organization defined network-accessible storage devices] "}],"subControls":"","tests":[{"testId":"AC-20(04)","uuid":"701daecd-249e-4a6f-beaa-7dda495a56e2","test":"Determine if the use of [SELECTED PARAMETER VALUE(S): network-accessible storage devices ] is prohibited in external systems.Limits on the use of organization-controlled portable storage devices in external systems include a complete prohibition of the use of such devices. Prohibiting such use is enforced using technical methods and/or nontechnical (i.e., process-based) methods.
","uuid":"3c96f47c-e462-4863-92ee-e76bdca3d3b4","family":"Access Control","parameters":[],"subControls":"","tests":[{"testId":"AC-20(05)","uuid":"cf3a9df3-1382-40f5-99c8-06e00de99d26","test":"Determine if the use of organization-controlled portable storage devices by authorized individuals is prohibited on external systems.Information sharing applies to information that may be restricted in some manner based on some formal or administrative determination. Examples of such information include, contract-sensitive information, classified information related to special access programs or compartments, privileged information, proprietary information, and personally identifiable information. Security and privacy risk assessments as well as applicable laws, regulations, and policies can provide useful inputs to these determinations. Depending on the circumstances, sharing partners may be defined at the individual, group, or organizational level. Information may be defined by content, type, security category, or special access program or compartment. Access restrictions may include non-disclosure agreements (NDA). Information flow techniques and security attributes may be used to provide automated assistance to users making sharing and collaboration decisions.
","uuid":"424ba5b6-ab2a-4569-85ce-42f76d6817f5","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"91528978-c249-44d5-b540-808cd6e8a07d","text":"information-sharing circumstances","parameterId":"ac-21_odp.01","default":" [Assignment: organization defined information-sharing circumstances] "},{"constraints":"","displayName":"","guidance":"","uuid":"cf04b920-e7b2-457c-9086-2d776357a405","text":"automated mechanisms","parameterId":"ac-21_odp.02","default":" [Assignment: organization defined automated mechanisms] "}],"subControls":"","tests":[{"testId":"AC-21a.","uuid":"35d8ef69-dab3-46b0-a881-cae7a47b798d","test":"Determine if authorized users are enabled to determine whether access authorizations assigned to a sharing partner match the information’s access and use restrictions for [SELECTED PARAMETER VALUE(S): information-sharing circumstances ];Automated mechanisms are used to enforce information sharing decisions.
","uuid":"b9fc5275-6734-44b2-a5f6-c06a06c59152","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"494bd446-98d8-4bca-8c19-8b1ecdef81c3","text":"automated mechanisms","parameterId":"ac-21.01_odp","default":" [Assignment: organization defined automated mechanisms] "}],"subControls":"","tests":[{"testId":"AC-21(01)","uuid":"2a16e43b-0399-4d1a-a149-3e96e453babb","test":"Determine if [SELECTED PARAMETER VALUE(S): automated mechanisms ] are employed to enforce information-sharing decisions by authorized users based on access authorizations of sharing partners and access restrictions on information to be shared.Information search and retrieval services identify information system resources relevant to an information need.
","uuid":"3b0b48d5-4d8a-4f04-a962-856e3328e5af","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"78e7a7fb-27cd-42c4-925e-2ffe22f60f39","text":"information-sharing restrictions","parameterId":"ac-21.02_odp","default":" [Assignment: organization defined information-sharing restrictions] "}],"subControls":"","tests":[{"testId":"AC-21(02)","uuid":"24a57192-0116-4537-adad-2f5eddaddc61","test":"Determine if information search and retrieval services that enforce [SELECTED PARAMETER VALUE(S): information-sharing restrictions ] are implemented.In accordance with applicable laws, executive orders, directives, policies, regulations, standards, and guidelines, the public is not authorized to have access to nonpublic information, including information protected under the PRIVACT and proprietary information. Publicly accessible content addresses systems that are controlled by the organization and accessible to the public, typically without identification or authentication. Posting information on non-organizational systems (e.g., non-organizational public websites, forums, and social media) is covered by organizational policy. While organizations may have individuals who are responsible for developing and implementing policies about the information that can be made publicly accessible, publicly accessible content addresses the management of the individuals who make such information publicly accessible.
","uuid":"b8ad9964-5d87-4278-8248-7aebaf4455ff","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"6e5ad341-1589-4b09-a9ef-094dbbcff3a2","text":"frequency","parameterId":"ac-22_odp","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"AC-22a.","uuid":"416668d5-a989-4be2-bb75-6d9e9a0a842a","test":"Determine if designated individuals are authorized to make information publicly accessible;Data mining is an analytical process that attempts to find correlations or patterns in large data sets for the purpose of data or knowledge discovery. Data storage objects include database records and database fields. Sensitive information can be extracted from data mining operations. When information is personally identifiable information, it may lead to unanticipated revelations about individuals and give rise to privacy risks. Prior to performing data mining activities, organizations determine whether such activities are authorized. Organizations may be subject to applicable laws, executive orders, directives, regulations, or policies that address data mining requirements. Organizational personnel consult with the senior agency official for privacy and legal counsel regarding such requirements.
Data mining prevention and detection techniques include limiting the number and frequency of database queries to increase the work factor needed to determine the contents of databases, limiting types of responses provided to database queries, applying differential privacy techniques or homomorphic encryption, and notifying personnel when atypical database queries or accesses occur. Data mining protection focuses on protecting information from data mining while such information resides in organizational data stores. In contrast, AU-13 focuses on monitoring for organizational information that may have been mined or otherwise obtained from data stores and is available as open-source information residing on external sites, such as social networking or social media websites.
EO 13587 requires the establishment of an insider threat program for deterring, detecting, and mitigating insider threats, including the safeguarding of sensitive information from exploitation, compromise, or other unauthorized disclosure. Data mining protection requires organizations to identify appropriate techniques to prevent and detect unnecessary or unauthorized data mining. Data mining can be used by an insider to collect organizational information for the purpose of exfiltration.
","uuid":"1ee218ed-c51c-4e81-a7b2-5ada1cd86c0e","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"1c6d50e8-067e-42a0-9d13-739ee8367e72","text":"techniques","parameterId":"ac-23_odp.01","default":" [Assignment: organization defined techniques] "},{"constraints":"","displayName":"","guidance":"","uuid":"4b053e10-b4ac-4c03-bad9-72db227e426e","text":"data storage objects","parameterId":"ac-23_odp.02","default":" [Assignment: organization defined data storage objects] "}],"subControls":"","tests":[{"testId":"AC-23","uuid":"866134d5-f14f-4824-9f18-01de82d4a497","test":"Determine if [SELECTED PARAMETER VALUE(S): techniques ] are employed for [SELECTED PARAMETER VALUE(S): data storage objects ] to detect and protect against unauthorized data mining.Access control decisions (also known as authorization decisions) occur when authorization information is applied to specific accesses. In contrast, access enforcement occurs when systems enforce access control decisions. While it is common to have access control decisions and access enforcement implemented by the same entity, it is not required, and it is not always an optimal implementation choice. For some architectures and distributed systems, different entities may make access control decisions and enforce access.
","uuid":"bc18ad87-ddc4-400e-8ba4-f0dfa38c54d2","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"0fd11b72-359e-4413-815e-da25bbcca42b","text":"[Selection (one or more): establish procedures; implement mechanisms]","parameterId":"ac-24_odp.01","default":"[Selection (one or more): establish procedures; implement mechanisms]"},{"constraints":"","displayName":"","guidance":"","uuid":"089f7923-1b6b-48f0-ac77-df5ca267483a","text":"access control decisions","parameterId":"ac-24_odp.02","default":" [Assignment: organization defined access control decisions] "}],"subControls":"","tests":[{"testId":"AC-24","uuid":"6677ddb6-3e0c-4871-9090-50d7aa20fbb8","test":"Determine if [SELECTED PARAMETER VALUE(S): [Selection (one or more): establish procedures; implement mechanisms] ] are taken to ensure that [SELECTED PARAMETER VALUE(S): access control decisions ] are applied to each access request prior to access enforcement.Authorization processes and access control decisions may occur in separate parts of systems or in separate systems. In such instances, authorization information is transmitted securely (e.g., using cryptographic mechanisms) so that timely access control decisions can be enforced at the appropriate locations. To support the access control decisions, it may be necessary to transmit as part of the access authorization information supporting security and privacy attributes. This is because in distributed systems, there are various access control decisions that need to be made, and different entities make these decisions in a serial fashion, each requiring those attributes to make the decisions. Protecting access authorization information ensures that such information cannot be altered, spoofed, or compromised during transmission.
","uuid":"a7039783-7096-4065-810a-0aaf40be91e3","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"d431b358-ef28-4ddc-9db2-b6078260d54e","text":"access authorization information","parameterId":"ac-24.01_odp.01","default":" [Assignment: organization defined access authorization information] "},{"constraints":"","displayName":"","guidance":"","uuid":"d25e34af-dbe9-463c-ae5b-027d28f45ce3","text":"controls","parameterId":"ac-24.01_odp.02","default":" [Assignment: organization defined controls] "},{"constraints":"","displayName":"","guidance":"","uuid":"e07724d4-7004-454e-8848-0b07a1d4298d","text":"systems","parameterId":"ac-24.01_odp.03","default":" [Assignment: organization defined systems] "}],"subControls":"","tests":[{"testId":"AC-24(01)","uuid":"30fb0b72-adb3-4f2b-b985-5aec55d5813f","test":"Determine if [SELECTED PARAMETER VALUE(S): access authorization information ] is transmitted using [SELECTED PARAMETER VALUE(S): controls ] to [SELECTED PARAMETER VALUE(S): systems ] that enforce access control decisions.In certain situations, it is important that access control decisions can be made without information regarding the identity of the users issuing the requests. These are generally instances where preserving individual privacy is of paramount importance. In other situations, user identification information is simply not needed for access control decisions, and especially in the case of distributed systems, transmitting such information with the needed degree of assurance may be very expensive or difficult to accomplish. MAC, RBAC, ABAC, and label-based control policies, for example, might not include user identity as an attribute.
","uuid":"757401a5-2896-4ee1-965a-2b1404cfa640","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"fbf339eb-b998-4b47-942c-ca1193b530ff","text":"organization-defined security or privacy attributes","parameterId":"ac-24.2_prm_1","default":" [Assignment: organization-defined security or privacy attributes] "},{"constraints":"","displayName":"","guidance":"","uuid":"a5e5425a-1608-45d2-b255-6722953c90cf","text":"security attributes","parameterId":"ac-24.02_odp.01","default":" [Assignment: organization defined security attributes] "},{"constraints":"","displayName":"","guidance":"","uuid":"1a1ffc4b-fcf4-4d02-9c0f-12ac29c7a543","text":"privacy attributes","parameterId":"ac-24.02_odp.02","default":" [Assignment: organization defined privacy attributes] "}],"subControls":"","tests":[{"testId":"AC-24(02)[01]","uuid":"65f5f336-e6ae-4b36-a62f-b8065bcd8991","test":"Determine if access control decisions are enforced based on [SELECTED PARAMETER VALUE(S): security attributes ] that do not include the identity of the user or process acting on behalf of the user (if selected);A reference monitor is a set of design requirements on a reference validation mechanism that, as a key component of an operating system, enforces an access control policy over all subjects and objects. A reference validation mechanism is always invoked, tamper-proof, and small enough to be subject to analysis and tests, the completeness of which can be assured (i.e., verifiable). Information is represented internally within systems using abstractions known as data structures. Internal data structures can represent different types of entities, both active and passive. Active entities, also known as subjects, are associated with individuals, devices, or processes acting on behalf of individuals. Passive entities, also known as objects, are associated with data structures, such as records, buffers, communications ports, tables, files, and inter-process pipes. Reference monitors enforce access control policies that restrict access to objects based on the identity of subjects or groups to which the subjects belong. The system enforces the access control policy based on the rule set established by the policy. The tamper-proof property of the reference monitor prevents determined adversaries from compromising the functioning of the reference validation mechanism. The always invoked property prevents adversaries from bypassing the mechanism and violating the security policy. The smallness property helps to ensure completeness in the analysis and testing of the mechanism to detect any weaknesses or deficiencies (i.e., latent flaws) that would prevent the enforcement of the security policy.
","uuid":"029b5e55-aa1f-487f-a0a4-1931db977f8d","family":"Access Control","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"5e28c9bd-1ddb-4f30-b91d-8655d1c41c81","text":"access control policies","parameterId":"ac-25_odp","default":" [Assignment: organization defined access control policies] "}],"subControls":"","tests":[{"testId":"AC-25","uuid":"2944519e-16e9-4933-a34b-deb50bc17321","test":"Determine if a reference monitor is implemented for [SELECTED PARAMETER VALUE(S): access control policies ] that is tamper-proof, always invoked, and small enough to be subject to analysis and testing, the completeness of which can be assured.Awareness and training policy and procedures address the controls in the AT family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of awareness and training policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission or business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to awareness and training policy and procedures include assessment or audit findings, security incidents or breaches, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure.
","uuid":"7f7f1c7f-db12-40e0-ae37-9592c00334d3","family":"Awareness and Training","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"d54e5978-e88d-4006-af04-e52a36ea432c","text":"organization-defined personnel or roles","parameterId":"at-1_prm_1","default":" [Assignment: organization-defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"a70011c2-1cc3-43fd-b761-ab34bbdcc21e","text":"personnel or roles","parameterId":"at-01_odp.01","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"aa6128c4-0679-4098-a6bf-039805ba9960","text":"personnel or roles","parameterId":"at-01_odp.02","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"1b1d1671-1185-4a77-8b04-e755aa532d96","text":"[Selection (one or more): organization-level; mission/business process-level; system-level]","parameterId":"at-01_odp.03","default":"[Selection (one or more): organization-level; mission/business process-level; system-level]"},{"constraints":"","displayName":"","guidance":"","uuid":"4a87bc2d-8c6f-45c7-b732-f91f48faec7e","text":"official","parameterId":"at-01_odp.04","default":" [Assignment: organization defined official] "},{"constraints":"","displayName":"","guidance":"","uuid":"9725006a-17d6-4fcf-bfa4-cc9b2923e042","text":"frequency","parameterId":"at-01_odp.05","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"364b5d8c-cc3d-40a3-8331-735f961c0502","text":"events","parameterId":"at-01_odp.06","default":" [Assignment: organization defined events] "},{"constraints":"","displayName":"","guidance":"","uuid":"0f02f1c4-3afd-4363-92b3-7c3b031fa145","text":"frequency","parameterId":"at-01_odp.07","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"bc81df69-5f58-48c7-a83f-4af9107732c4","text":"events","parameterId":"at-01_odp.08","default":" [Assignment: organization defined events] "}],"subControls":"","tests":[{"testId":"AT-01a.[01]","uuid":"e28aca67-8e46-4b27-a196-f8023665f97d","test":"Determine if an awareness and training policy is developed and documented;Organizations provide basic and advanced levels of literacy training to system users, including measures to test the knowledge level of users. Organizations determine the content of literacy training and awareness based on specific organizational requirements, the systems to which personnel have authorized access, and work environments (e.g., telework). The content includes an understanding of the need for security and privacy as well as actions by users to maintain security and personal privacy and to respond to suspected incidents. The content addresses the need for operations security and the handling of personally identifiable information.
Awareness techniques include displaying posters, offering supplies inscribed with security and privacy reminders, displaying logon screen messages, generating email advisories or notices from organizational officials, and conducting awareness events. Literacy training after the initial training described in AT-2a.1 is conducted at a minimum frequency consistent with applicable laws, directives, regulations, and policies. Subsequent literacy training may be satisfied by one or more short ad hoc sessions and include topical information on recent attack schemes, changes to organizational security and privacy policies, revised security and privacy expectations, or a subset of topics from the initial training. Updating literacy training and awareness content on a regular basis helps to ensure that the content remains relevant. Events that may precipitate an update to literacy training and awareness content include, but are not limited to, assessment or audit findings, security incidents or breaches, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines.
","uuid":"4057bb7a-2bea-4230-8ab2-a93fca449165","family":"Awareness and Training","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"fc9ecd31-fc54-4351-aac6-b1237f8656ec","text":"organization-defined frequency","parameterId":"at-2_prm_1","default":" [Assignment: organization-defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"973d7a92-6f5b-4018-9f23-e796ca7715dc","text":"organization-defined events","parameterId":"at-2_prm_2","default":" [Assignment: organization-defined events] "},{"constraints":"","displayName":"","guidance":"","uuid":"0b9c7b29-c48f-4ca1-8954-cf4e1fd8d7e3","text":"frequency","parameterId":"at-02_odp.01","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"aafc341f-5e30-4873-a89c-f5f1827aa814","text":"frequency","parameterId":"at-02_odp.02","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"76c2a0b7-f322-4f22-a560-3c378dcd3016","text":"events","parameterId":"at-02_odp.03","default":" [Assignment: organization defined events] "},{"constraints":"","displayName":"","guidance":"","uuid":"8f54de22-b6cb-4ca4-b307-ecf619bed1eb","text":"events","parameterId":"at-02_odp.04","default":" [Assignment: organization defined events] "},{"constraints":"","displayName":"","guidance":"","uuid":"39adb57b-0d58-4887-982b-8d8e0ef926e3","text":"awareness techniques","parameterId":"at-02_odp.05","default":" [Assignment: organization defined awareness techniques] "},{"constraints":"","displayName":"","guidance":"","uuid":"60c1b124-03eb-438f-a67e-6d02460d5a4f","text":"frequency","parameterId":"at-02_odp.06","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"0def8d19-6b43-49d3-8256-2ee5054c8618","text":"events","parameterId":"at-02_odp.07","default":" [Assignment: organization defined events] "}],"subControls":"","tests":[{"testId":"AT-02a.01[01]","uuid":"eceb2ea1-49c5-4506-a12d-8904df61001f","test":"Determine if security literacy training is provided to system users (including managers, senior executives, and contractors) as part of initial training for new users;Practical exercises include no-notice social engineering attempts to collect information, gain unauthorized access, or simulate the adverse impact of opening malicious email attachments or invoking, via spear phishing attacks, malicious web links.
","uuid":"b715b694-c0ca-4696-9cbc-d13d889e613a","family":"Awareness and Training","parameters":[],"subControls":"","tests":[{"testId":"AT-02(01)","uuid":"f021aa3e-51e9-4e11-8524-b61995135f21","test":"Determine if practical exercises in literacy training that simulate events and incidents are provided.Potential indicators and possible precursors of insider threat can include behaviors such as inordinate, long-term job dissatisfaction; attempts to gain access to information not required for job performance; unexplained access to financial resources; bullying or harassment of fellow employees; workplace violence; and other serious violations of policies, procedures, directives, regulations, rules, or practices. Literacy training includes how to communicate the concerns of employees and management regarding potential indicators of insider threat through channels established by the organization and in accordance with established policies and procedures. Organizations may consider tailoring insider threat awareness topics to the role. For example, training for managers may be focused on changes in the behavior of team members, while training for employees may be focused on more general observations.
","uuid":"f7850388-4200-4556-8f3b-44373c0a1410","family":"Awareness and Training","parameters":[],"subControls":"","tests":[{"testId":"AT-02(02)[01]","uuid":"b553ff15-cc2c-47e0-91fb-6a674f716dd7","test":"Determine if literacy training on recognizing potential indicators of insider threat is provided;Social engineering is an attempt to trick an individual into revealing information or taking an action that can be used to breach, compromise, or otherwise adversely impact a system. Social engineering includes phishing, pretexting, impersonation, baiting, quid pro quo, thread-jacking, social media exploitation, and tailgating. Social mining is an attempt to gather information about the organization that may be used to support future attacks. Literacy training includes information on how to communicate the concerns of employees and management regarding potential and actual instances of social engineering and data mining through organizational channels based on established policies and procedures.
","uuid":"01aeb8c0-6e6f-4573-a9f6-90b8124a31c1","family":"Awareness and Training","parameters":[],"subControls":"","tests":[{"testId":"AT-02(03)[01]","uuid":"3967949a-2ea3-4e9d-8a0d-8cf6757743bf","test":"Determine if literacy training on recognizing potential and actual instances of social engineering is provided;A well-trained workforce provides another organizational control that can be employed as part of a defense-in-depth strategy to protect against malicious code coming into organizations via email or the web applications. Personnel are trained to look for indications of potentially suspicious email (e.g., receiving an unexpected email, receiving an email containing strange or poor grammar, or receiving an email from an unfamiliar sender that appears to be from a known sponsor or contractor). Personnel are also trained on how to respond to suspicious email or web communications. For this process to work effectively, personnel are trained and made aware of what constitutes suspicious communications. Training personnel on how to recognize anomalous behaviors in systems can provide organizations with early warning for the presence of malicious code. Recognition of anomalous behavior by organizational personnel can supplement malicious code detection and protection tools and systems employed by organizations.
","uuid":"a310665b-4699-4b5b-9381-dc5909a9d92b","family":"Awareness and Training","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"b095bdf1-0077-4e23-87f7-98770356b2da","text":"indicators of malicious code","parameterId":"at-02.04_odp","default":" [Assignment: organization defined indicators of malicious code] "}],"subControls":"","tests":[{"testId":"AT-02(04)","uuid":"9ff99a00-3877-4292-bdf4-ca84b157f6e2","test":"Determine if literacy training on recognizing suspicious communications and anomalous behavior in organizational systems using [SELECTED PARAMETER VALUE(S): indicators of malicious code ] is provided.An effective way to detect advanced persistent threats (APT) and to preclude successful attacks is to provide specific literacy training for individuals. Threat literacy training includes educating individuals on the various ways that APTs can infiltrate the organization (e.g., through websites, emails, advertisement pop-ups, articles, and social engineering). Effective training includes techniques for recognizing suspicious emails, use of removable systems in non-secure settings, and the potential targeting of individuals at home.
","uuid":"f819d335-31c7-41f1-b9c8-1b41b2b45450","family":"Awareness and Training","parameters":[],"subControls":"","tests":[{"testId":"AT-02(05)","uuid":"74e16951-620d-4232-9651-7255fe093229","test":"Determine if literacy training on the advanced persistent threat is provided.Since threats continue to change over time, threat literacy training by the organization is dynamic. Moreover, threat literacy training is not performed in isolation from the system operations that support organizational mission and business functions.
","uuid":"6d88c12e-f521-4eac-9f1a-b7adaee1f979","family":"Awareness and Training","parameters":[],"subControls":"","tests":[{"testId":"AT-02(06)(a)","uuid":"4f85310e-d978-43a3-a7e9-971c2275a2ad","test":"Determine if literacy training on the cyber threat environment is provided;Organizations determine the content of training based on the assigned roles and responsibilities of individuals as well as the security and privacy requirements of organizations and the systems to which personnel have authorized access, including technical training specifically tailored for assigned duties. Roles that may require role-based training include senior leaders or management officials (e.g., head of agency/chief executive officer, chief information officer, senior accountable official for risk management, senior agency information security officer, senior agency official for privacy), system owners; authorizing officials; system security officers; privacy officers; acquisition and procurement officials; enterprise architects; systems engineers; software developers; systems security engineers; privacy engineers; system, network, and database administrators; auditors; personnel conducting configuration management activities; personnel performing verification and validation activities; personnel with access to system-level software; control assessors; personnel with contingency planning and incident response duties; personnel with privacy management responsibilities; and personnel with access to personally identifiable information.
Comprehensive role-based training addresses management, operational, and technical roles and responsibilities covering physical, personnel, and technical controls. Role-based training also includes policies, procedures, tools, methods, and artifacts for the security and privacy roles defined. Organizations provide the training necessary for individuals to fulfill their responsibilities related to operations and supply chain risk management within the context of organizational security and privacy programs. Role-based training also applies to contractors who provide services to federal agencies. Types of training include web-based and computer-based training, classroom-style training, and hands-on training (including micro-training). Updating role-based training on a regular basis helps to ensure that the content remains relevant and effective. Events that may precipitate an update to role-based training content include, but are not limited to, assessment or audit findings, security incidents or breaches, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines.
","uuid":"2c4e7b11-1ff7-4aa3-825b-19eb6bbd794d","family":"Awareness and Training","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"81300e8d-285e-4cf3-a59d-589e746bbcf5","text":"organization-defined roles and responsibilities","parameterId":"at-3_prm_1","default":" [Assignment: organization-defined roles and responsibilities] "},{"constraints":"","displayName":"","guidance":"","uuid":"d6105e36-2b8a-44ae-b5e1-ec849e9c673e","text":"roles and responsibilities","parameterId":"at-03_odp.01","default":" [Assignment: organization defined roles and responsibilities] "},{"constraints":"","displayName":"","guidance":"","uuid":"12870aa7-7ea3-4fab-aac8-42c035fa8cc6","text":"roles and responsibilities","parameterId":"at-03_odp.02","default":" [Assignment: organization defined roles and responsibilities] "},{"constraints":"","displayName":"","guidance":"","uuid":"48697d1c-9716-4666-820a-c3a0949aedf5","text":"frequency","parameterId":"at-03_odp.03","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"feb73d32-3cb8-4b5f-a7ca-ecba2da14728","text":"frequency","parameterId":"at-03_odp.04","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"b2ea6942-4432-4cec-b56a-dff2beba5d64","text":"events","parameterId":"at-03_odp.05","default":" [Assignment: organization defined events] "}],"subControls":"","tests":[{"testId":"AT-03a.01[01]","uuid":"594c4357-d6d5-434d-b3e6-96cdb36083b0","test":"Determine if role-based security training is provided to [SELECTED PARAMETER VALUE(S): roles and responsibilities ] before authorizing access to the system, information, or performing assigned duties;Environmental controls include fire suppression and detection devices or systems, sprinkler systems, handheld fire extinguishers, fixed fire hoses, smoke detectors, temperature or humidity, heating, ventilation, air conditioning, and power within the facility.
","uuid":"542b2d9e-aadd-4c6c-b07a-4feed04a214b","family":"Awareness and Training","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"544546a9-6b80-4e89-bc09-3427c616ec1c","text":"personnel or roles","parameterId":"at-03.01_odp.01","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"0040b2dc-e9f8-4301-80ce-1e438cd5fcfb","text":"frequency","parameterId":"at-03.01_odp.02","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"AT-03(01)","uuid":"69ac8552-7320-4377-bf9e-84ae56fbfcc0","test":"Determine if [SELECTED PARAMETER VALUE(S): personnel or roles ] are provided with initial and refresher training [SELECTED PARAMETER VALUE(S): frequency ] in the employment and operation of environmental controls.Physical security controls include physical access control devices, physical intrusion and detection alarms, operating procedures for facility security guards, and monitoring or surveillance equipment.
","uuid":"72ee44c7-f64a-4594-b1c1-fd2bcd751d40","family":"Awareness and Training","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"5cda0d03-8e6f-4176-9ac6-96e181923c25","text":"personnel or roles","parameterId":"at-03.02_odp.01","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"6ff4023f-9308-40b1-8b57-acf8a9ee073e","text":"frequency","parameterId":"at-03.02_odp.02","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"AT-03(02)","uuid":"e03eb02b-7649-4e23-a189-545ee25768c3","test":"Determine if [SELECTED PARAMETER VALUE(S): personnel or roles ] is/are provided with initial and refresher training [SELECTED PARAMETER VALUE(S): frequency ] in the employment and operation of physical security controls.Practical exercises for security include training for software developers that addresses simulated attacks that exploit common software vulnerabilities or spear or whale phishing attacks targeted at senior leaders or executives. Practical exercises for privacy include modules with quizzes on identifying and processing personally identifiable information in various scenarios or scenarios on conducting privacy impact assessments.
","uuid":"cdd61128-5544-42ed-95b7-de7c51e2c287","family":"Awareness and Training","parameters":[],"subControls":"","tests":[{"testId":"AT-03(03)[01]","uuid":"d2a2ecfa-afca-427d-97fc-27c45264d179","test":"Determine if practical exercises in security training that reinforce training objectives are provided;Personally identifiable information processing and transparency controls include the organization’s authority to process personally identifiable information and personally identifiable information processing purposes. Role-based training for federal agencies addresses the types of information that may constitute personally identifiable information and the risks, considerations, and obligations associated with its processing. Such training also considers the authority to process personally identifiable information documented in privacy policies and notices, system of records notices, computer matching agreements and notices, privacy impact assessments, PRIVACT statements, contracts, information sharing agreements, memoranda of understanding, and/or other documentation.
","uuid":"4dceeec5-6202-4d8c-8db1-de601483d742","family":"Awareness and Training","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"6f310e81-9c95-4851-9c82-8088106be774","text":"personnel or roles","parameterId":"at-03.05_odp.01","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"64757565-fae6-4e2b-b159-ad2efee3e798","text":"frequency","parameterId":"at-03.05_odp.02","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"AT-03(05)","uuid":"17bea13e-d82b-487e-add5-52be94e30c7b","test":"Determine if [SELECTED PARAMETER VALUE(S): personnel or roles ] are provided with initial and refresher training [SELECTED PARAMETER VALUE(S): frequency ] in the employment and operation of personally identifiable information processing and transparency controls.Documentation for specialized training may be maintained by individual supervisors at the discretion of the organization. The National Archives and Records Administration provides guidance on records retention for federal agencies.
","uuid":"c68ce9cc-8b4f-4f20-8223-7f1aedf6b7cb","family":"Awareness and Training","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"a2256464-cfc2-4a4f-9d52-0b51fad650c1","text":"time period","parameterId":"at-04_odp","default":" [Assignment: organization defined time period] "}],"subControls":"","tests":[{"testId":"AT-04a.[01]","uuid":"9f7b635b-2172-4223-a614-524e149ed39c","test":"Determine if information security and privacy training activities, including security and privacy awareness training and specific role-based security and privacy training, are documented;Training feedback includes awareness training results and role-based training results. Training results, especially failures of personnel in critical roles, can be indicative of a potentially serious problem. Therefore, it is important that senior managers are made aware of such situations so that they can take appropriate response actions. Training feedback supports the evaluation and update of organizational training described in AT-2b and AT-3b.
","uuid":"0c62855a-077e-4df4-ab98-b76bce31afb0","family":"Awareness and Training","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"c084d6e8-063f-44fb-b762-12ea99258797","text":"frequency","parameterId":"at-06_odp.01","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"11bb7ce0-7190-4eb3-966a-253e55c71f01","text":"personnel","parameterId":"at-06_odp.02","default":" [Assignment: organization defined personnel] "}],"subControls":"","tests":[{"testId":"AT-06","uuid":"a3bbcc79-fbcd-455d-9ee9-98f45a155f25","test":"Determine if feedback on organizational training results is provided [SELECTED PARAMETER VALUE(S): frequency ] to [SELECTED PARAMETER VALUE(S): personnel ].Audit and accountability policy and procedures address the controls in the AU family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of audit and accountability policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission or business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to audit and accountability policy and procedures include assessment or audit findings, security incidents or breaches, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure.
","uuid":"42296b66-fabf-4d50-84fb-587b20e88a68","family":"Audit and Accountability","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"cc659b66-5d37-4958-885c-24c25afffcd6","text":"organization-defined personnel or roles","parameterId":"au-1_prm_1","default":" [Assignment: organization-defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"dad38130-86a7-4c01-a430-ed31eef7e1ae","text":"personnel or roles","parameterId":"au-01_odp.01","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"3c121353-9ff8-4fce-b33a-35087a5ec70e","text":"personnel or roles","parameterId":"au-01_odp.02","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"8cebcd39-fdaf-40c5-9a59-5eb5ca52ab9d","text":"[Selection (one or more): organization-level; mission/business process-level; system-level]","parameterId":"au-01_odp.03","default":"[Selection (one or more): organization-level; mission/business process-level; system-level]"},{"constraints":"","displayName":"","guidance":"","uuid":"d58c7f8d-d0ab-4933-80fa-b63305d6f016","text":"official","parameterId":"au-01_odp.04","default":" [Assignment: organization defined official] "},{"constraints":"","displayName":"","guidance":"","uuid":"82d70e25-9ed4-4461-9e24-bb24d9b6d6c6","text":"frequency","parameterId":"au-01_odp.05","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"2bd4b3a9-067c-4f82-8a81-a60b309ab528","text":"events","parameterId":"au-01_odp.06","default":" [Assignment: organization defined events] "},{"constraints":"","displayName":"","guidance":"","uuid":"5d977288-7e34-47e1-aa91-1c59274821fc","text":"frequency","parameterId":"au-01_odp.07","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"749d8555-f76d-4b09-ab5e-36743231afdf","text":"events","parameterId":"au-01_odp.08","default":" [Assignment: organization defined events] "}],"subControls":"","tests":[{"testId":"AU-01a.[01]","uuid":"3524d644-f927-400e-b247-6b1699949fb5","test":"Determine if an audit and accountability policy is developed and documented;An event is an observable occurrence in a system. The types of events that require logging are those events that are significant and relevant to the security of systems and the privacy of individuals. Event logging also supports specific monitoring and auditing needs. Event types include password changes, failed logons or failed accesses related to systems, security or privacy attribute changes, administrative privilege usage, PIV credential usage, data action changes, query parameters, or external credential usage. In determining the set of event types that require logging, organizations consider the monitoring and auditing appropriate for each of the controls to be implemented. For completeness, event logging includes all protocols that are operational and supported by the system.
To balance monitoring and auditing requirements with other system needs, event logging requires identifying the subset of event types that are logged at a given point in time. For example, organizations may determine that systems need the capability to log every file access successful and unsuccessful, but not activate that capability except for specific circumstances due to the potential burden on system performance. The types of events that organizations desire to be logged may change. Reviewing and updating the set of logged events is necessary to help ensure that the events remain relevant and continue to support the needs of the organization. Organizations consider how the types of logging events can reveal information about individuals that may give rise to privacy risk and how best to mitigate such risks. For example, there is the potential to reveal personally identifiable information in the audit trail, especially if the logging event is based on patterns or time of usage.
Event logging requirements, including the need to log specific event types, may be referenced in other controls and control enhancements. These include AC-2(4), AC-3(10), AC-6(9), AC-17(1), CM-3f, CM-5(1), IA-3(3)(b), MA-4(1), MP-4(2), PE-3, PM-21, PT-7, RA-8, SC-7(9), SC-7(15), SI-3(8), SI-4(22), SI-7(8) , and SI-10(1) . Organizations include event types that are required by applicable laws, executive orders, directives, policies, regulations, standards, and guidelines. Audit records can be generated at various levels, including at the packet level as information traverses the network. Selecting the appropriate level of event logging is an important part of a monitoring and auditing capability and can identify the root causes of problems. When defining event types, organizations consider the logging necessary to cover related event types, such as the steps in distributed, transaction-based processes and the actions that occur in service-oriented architectures.
","uuid":"f80535b8-f5f1-42c8-ada4-ffc2eea479d6","family":"Audit and Accountability","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"5cab91e5-6f26-4d9c-a5b9-a9d6ca456dfa","text":"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","parameterId":"au-2_prm_2","default":" [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] "},{"constraints":"","displayName":"","guidance":"","uuid":"c33fde4a-123f-43af-8ffe-8d929e5ab591","text":"event types","parameterId":"au-02_odp.01","default":" [Assignment: organization defined event types] "},{"constraints":"","displayName":"","guidance":"","uuid":"e039e7e5-18ed-4cc5-8bd2-50495defdeba","text":"event types (subset of AU-02_ODP[01])","parameterId":"au-02_odp.02","default":" [Assignment: organization defined event types (subset of AU-02_ODP[01])] "},{"constraints":"","displayName":"","guidance":"","uuid":"6db2bd44-1f25-474a-8c76-07aa287a9fa8","text":"frequency or situation","parameterId":"au-02_odp.03","default":" [Assignment: organization defined frequency or situation] "},{"constraints":"","displayName":"","guidance":"","uuid":"97342f41-8790-4603-b49a-6ff9b46ef5df","text":"frequency","parameterId":"au-02_odp.04","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"AU-02a.","uuid":"d554d0d1-88ef-40f0-923f-67c3b2f2b8e7","test":"Determine if [SELECTED PARAMETER VALUE(S): event types ] that the system is capable of logging are identified in support of the audit logging function;Audit record content that may be necessary to support the auditing function includes event descriptions (item a), time stamps (item b), source and destination addresses (item c), user or process identifiers (items d and f), success or fail indications (item e), and filenames involved (items a, c, e, and f) . Event outcomes include indicators of event success or failure and event-specific results, such as the system security and privacy posture after the event occurred. Organizations consider how audit records can reveal information about individuals that may give rise to privacy risks and how best to mitigate such risks. For example, there is the potential to reveal personally identifiable information in the audit trail, especially if the trail records inputs or is based on patterns or time of usage.
","uuid":"31f0384e-0f66-4a2e-bd36-1f397160c1d5","family":"Audit and Accountability","parameters":[],"subControls":"","tests":[{"testId":"AU-03a.","uuid":"c8c60b1f-b9bd-49f2-a296-120e84621b3a","test":"Determine if audit records contain information that establishes what type of event occurred;The ability to add information generated in audit records is dependent on system functionality to configure the audit record content. Organizations may consider additional information in audit records including, but not limited to, access control or flow control rules invoked and individual identities of group account users. Organizations may also consider limiting additional audit record information to only information that is explicitly needed for audit requirements. This facilitates the use of audit trails and audit logs by not including information in audit records that could potentially be misleading, make it more difficult to locate information of interest, or increase the risk to individuals' privacy.
","uuid":"cd32202f-eefa-4077-a270-4aee659a6b05","family":"Audit and Accountability","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"a1b46fb4-3097-4f4d-961d-437f37d56ef1","text":"additional information","parameterId":"au-03.01_odp","default":" [Assignment: organization defined additional information] "}],"subControls":"","tests":[{"testId":"AU-03(01)","uuid":"a9418657-6004-44ee-b0f5-e3371ebcc685","test":"Determine if generated audit records contain the following [SELECTED PARAMETER VALUE(S): additional information ].Limiting personally identifiable information in audit records when such information is not needed for operational purposes helps reduce the level of privacy risk created by a system.
","uuid":"dd7e6c63-0700-409d-9fc8-e5c0447ca860","family":"Audit and Accountability","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"1a4423da-7461-44e2-908e-63506c005bbe","text":"elements","parameterId":"au-03.03_odp","default":" [Assignment: organization defined elements] "}],"subControls":"","tests":[{"testId":"AU-03(03)","uuid":"2b9ed076-d82d-4dea-be36-1b6a76065dfa","test":"Determine if personally identifiable information contained in audit records is limited to [SELECTED PARAMETER VALUE(S): elements ] identified in the privacy risk assessment.Organizations consider the types of audit logging to be performed and the audit log processing requirements when allocating audit log storage capacity. Allocating sufficient audit log storage capacity reduces the likelihood of such capacity being exceeded and resulting in the potential loss or reduction of audit logging capability.
","uuid":"21247519-ad90-4bc1-a4e9-3c28ca02dc69","family":"Audit and Accountability","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"65a5d0b3-34de-4cb1-8a59-022581d1b67e","text":"audit log retention requirements","parameterId":"au-04_odp","default":" [Assignment: organization defined audit log retention requirements] "}],"subControls":"","tests":[{"testId":"AU-04","uuid":"c0095026-7d60-42ac-8d63-19dbffc5a284","test":"Determine if audit log storage capacity is allocated to accommodate [SELECTED PARAMETER VALUE(S): audit log retention requirements ].Audit log transfer, also known as off-loading, is a common process in systems with limited audit log storage capacity and thus supports availability of the audit logs. The initial audit log storage is only used in a transitory fashion until the system can communicate with the secondary or alternate system allocated to audit log storage, at which point the audit logs are transferred. Transferring audit logs to alternate storage is similar to AU-9(2) in that audit logs are transferred to a different entity. However, the purpose of selecting AU-9(2) is to protect the confidentiality and integrity of audit records. Organizations can select either control enhancement to obtain the benefit of increased audit log storage capacity and preserving the confidentiality, integrity, and availability of audit records and logs.
","uuid":"d4a35e68-58db-4488-944b-8186c0b2df51","family":"Audit and Accountability","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"2f1f6bf7-d7fc-42d2-b260-d32862146ed2","text":"frequency","parameterId":"au-04.01_odp","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"AU-04(01)","uuid":"30716e5f-609d-446e-b06f-a705e1fa7422","test":"Determine if audit logs are transferred [SELECTED PARAMETER VALUE(S): frequency ] to a different system, system component, or media other than the system or system component conducting the logging.Audit logging process failures include software and hardware errors, failures in audit log capturing mechanisms, and reaching or exceeding audit log storage capacity. Organization-defined actions include overwriting oldest audit records, shutting down the system, and stopping the generation of audit records. Organizations may choose to define additional actions for audit logging process failures based on the type of failure, the location of the failure, the severity of the failure, or a combination of such factors. When the audit logging process failure is related to storage, the response is carried out for the audit log storage repository (i.e., the distinct system component where the audit logs are stored), the system on which the audit logs reside, the total audit log storage capacity of the organization (i.e., all audit log storage repositories combined), or all three. Organizations may decide to take no additional actions after alerting designated roles or personnel.
","uuid":"2dac3f70-cedb-43ec-bbad-220789e4f395","family":"Audit and Accountability","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"dfa0c759-e60e-4a43-95fa-4be621751d59","text":"personnel or roles","parameterId":"au-05_odp.01","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"9f2b64de-9dd0-4e28-9f7a-895750edb0ce","text":"time period","parameterId":"au-05_odp.02","default":" [Assignment: organization defined time period] "},{"constraints":"","displayName":"","guidance":"","uuid":"02dee322-9c62-4270-b297-d38d943aec39","text":"additional actions","parameterId":"au-05_odp.03","default":" [Assignment: organization defined additional actions] "}],"subControls":"","tests":[{"testId":"AU-05a.","uuid":"7f9ceb31-8e4f-4f77-81e6-674e0a8446b3","test":"Determine if [SELECTED PARAMETER VALUE(S): personnel or roles ] are alerted in the event of an audit logging process failure within [SELECTED PARAMETER VALUE(S): time period ];Organizations may have multiple audit log storage repositories distributed across multiple system components with each repository having different storage volume capacities.
","uuid":"f3cd4e23-95ed-4151-906d-cc63d83e6d66","family":"Audit and Accountability","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"1581e0db-636b-466f-852e-15db8edea7a0","text":"personnel, roles, and/or locations","parameterId":"au-05.01_odp.01","default":" [Assignment: organization defined personnel, roles, and/or locations] "},{"constraints":"","displayName":"","guidance":"","uuid":"c0ad2704-b954-421e-ae65-3a2d53223231","text":"time period","parameterId":"au-05.01_odp.02","default":" [Assignment: organization defined time period] "},{"constraints":"","displayName":"","guidance":"","uuid":"f9955ed8-f95b-4137-b5c4-7cdf0bd826e6","text":"percentage","parameterId":"au-05.01_odp.03","default":" [Assignment: organization defined percentage] "}],"subControls":"","tests":[{"testId":"AU-05(01)","uuid":"295a3c2f-2775-4e0f-bb4e-c3ee099301d3","test":"Determine if a warning is provided to [SELECTED PARAMETER VALUE(S): personnel, roles, and/or locations ] within [SELECTED PARAMETER VALUE(S): time period ] when allocated audit log storage volume reaches [SELECTED PARAMETER VALUE(S): percentage ] of repository maximum audit log storage capacity.Alerts provide organizations with urgent messages. Real-time alerts provide these messages at information technology speed (i.e., the time from event detection to alert occurs in seconds or less).
","uuid":"641a5164-f865-45ac-8735-f5863ce37a7e","family":"Audit and Accountability","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"ae85707e-4620-4e64-8822-855c74206c31","text":"real-time period","parameterId":"au-05.02_odp.01","default":" [Assignment: organization defined real-time period] "},{"constraints":"","displayName":"","guidance":"","uuid":"53e927b6-1441-4a45-8678-d5d6d1891068","text":"personnel, roles, and/or locations","parameterId":"au-05.02_odp.02","default":" [Assignment: organization defined personnel, roles, and/or locations] "},{"constraints":"","displayName":"","guidance":"","uuid":"eaa897b9-53ea-4bfc-b6f8-0de3ef1ec52f","text":"audit logging failure events requiring real-time alerts","parameterId":"au-05.02_odp.03","default":" [Assignment: organization defined audit logging failure events requiring real-time alerts] "}],"subControls":"","tests":[{"testId":"AU-05(02)","uuid":"3436f0ee-60b6-453e-9a39-4802bd54245a","test":"Determine if an alert is provided within [SELECTED PARAMETER VALUE(S): real-time period ] to [SELECTED PARAMETER VALUE(S): personnel, roles, and/or locations ] when [SELECTED PARAMETER VALUE(S): audit logging failure events requiring real-time alerts ] occur.Organizations have the capability to reject or delay the processing of network communications traffic if audit logging information about such traffic is determined to exceed the storage capacity of the system audit logging function. The rejection or delay response is triggered by the established organizational traffic volume thresholds that can be adjusted based on changes to audit log storage capacity.
","uuid":"157b1e13-9d56-45b4-a967-2b3f59bdd896","family":"Audit and Accountability","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"bf821a7b-812b-4b1e-8bec-dc0b8e0fc4dc","text":"[Selection (one or more): reject; delay]","parameterId":"au-05.03_odp","default":"[Selection (one or more): reject; delay]"}],"subControls":"","tests":[{"testId":"AU-05(03)[01]","uuid":"d3b0c9bf-dda7-4e2e-84cf-5b01ac47891e","test":"Determine if configurable network communications traffic volume thresholds reflecting limits on audit log storage capacity are enforced;Organizations determine the types of audit logging failures that can trigger automatic system shutdowns or degraded operations. Because of the importance of ensuring mission and business continuity, organizations may determine that the nature of the audit logging failure is not so severe that it warrants a complete shutdown of the system supporting the core organizational mission and business functions. In those instances, partial system shutdowns or operating in a degraded mode with reduced capability may be viable alternatives.
","uuid":"7b3ca207-93ae-414a-a75d-01ec1a746356","family":"Audit and Accountability","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"0765d117-e650-43e3-962c-0f97ff6daea7","text":"[Selection (one or more): full system shutdown; partial system shutdown; degraded operational mode with limited mission or business functionality available]","parameterId":"au-05.04_odp.01","default":"[Selection (one or more): full system shutdown; partial system shutdown; degraded operational mode with limited mission or business functionality available]"},{"constraints":"","displayName":"","guidance":"","uuid":"1e10249e-f751-4201-97ce-a5894a8641ee","text":"audit logging failures","parameterId":"au-05.04_odp.02","default":" [Assignment: organization defined audit logging failures] "}],"subControls":"","tests":[{"testId":"AU-05(04)","uuid":"64f2b5e4-f5fe-4432-959a-4a2b24aafc4a","test":"Determine if [SELECTED PARAMETER VALUE(S): [Selection (one or more): full system shutdown; partial system shutdown; degraded operational mode with limited mission or business functionality available] ] is/are invoked in the event of [SELECTED PARAMETER VALUE(S): audit logging failures ] , unless an alternate audit logging capability exists.Since an alternate audit logging capability may be a short-term protection solution employed until the failure in the primary audit logging capability is corrected, organizations may determine that the alternate audit logging capability need only provide a subset of the primary audit logging functionality that is impacted by the failure.
","uuid":"fd010df4-14d7-4581-a8b4-076413560f1b","family":"Audit and Accountability","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"8644cdf2-b730-4ef1-b164-a89b35898b99","text":"alternate audit logging functionality","parameterId":"au-05.05_odp","default":" [Assignment: organization defined alternate audit logging functionality] "}],"subControls":"","tests":[{"testId":"AU-05(05)","uuid":"491d51c5-c642-4bc3-96c7-9db0ad4f2748","test":"Determine if an alternate audit logging capability is provided in the event of a failure in primary audit logging capability that implements [SELECTED PARAMETER VALUE(S): alternate audit logging functionality ].Audit record review, analysis, and reporting covers information security- and privacy-related logging performed by organizations, including logging that results from the monitoring of account usage, remote access, wireless connectivity, mobile device connection, configuration settings, system component inventory, use of maintenance tools and non-local maintenance, physical access, temperature and humidity, equipment delivery and removal, communications at system interfaces, and use of mobile code or Voice over Internet Protocol (VoIP). Findings can be reported to organizational entities that include the incident response team, help desk, and security or privacy offices. If organizations are prohibited from reviewing and analyzing audit records or unable to conduct such activities, the review or analysis may be carried out by other organizations granted such authority. The frequency, scope, and/or depth of the audit record review, analysis, and reporting may be adjusted to meet organizational needs based on new information received.
","uuid":"4abb599e-92f8-4d32-925e-3261ad1b012b","family":"Audit and Accountability","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"ea7b661a-7918-4131-9095-8220578d9e74","text":"frequency","parameterId":"au-06_odp.01","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"6287206e-3fc5-4247-b815-456f8484dcfe","text":"inappropriate or unusual activity","parameterId":"au-06_odp.02","default":" [Assignment: organization defined inappropriate or unusual activity] "},{"constraints":"","displayName":"","guidance":"","uuid":"3be35fd4-db2c-4dda-872e-a44b7604ff04","text":"personnel or roles","parameterId":"au-06_odp.03","default":" [Assignment: organization defined personnel or roles] "}],"subControls":"","tests":[{"testId":"AU-06a.","uuid":"b3814441-46d9-4bcc-b0f5-0a1433698ea7","test":"Determine if system audit records are reviewed and analyzed [SELECTED PARAMETER VALUE(S): frequency ] for indications of [SELECTED PARAMETER VALUE(S): inappropriate or unusual activity ] and the potential impact of the inappropriate or unusual activity;Organizational processes that benefit from integrated audit record review, analysis, and reporting include incident response, continuous monitoring, contingency planning, investigation and response to suspicious activities, and Inspector General audits.
","uuid":"6531d538-e8b9-4c21-a03e-737f0b9a077a","family":"Audit and Accountability","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"d83400a0-cdb7-483c-8cb3-2033b0f74e64","text":"automated mechanisms","parameterId":"au-06.01_odp","default":" [Assignment: organization defined automated mechanisms] "}],"subControls":"","tests":[{"testId":"AU-06(01)","uuid":"e8bd59e5-bac6-4bff-8f5f-3f9d9cc2a277","test":"Determine if audit record review, analysis, and reporting processes are integrated using [SELECTED PARAMETER VALUE(S): automated mechanisms ].Organization-wide situational awareness includes awareness across all three levels of risk management (i.e., organizational level, mission/business process level, and information system level) and supports cross-organization awareness.
","uuid":"b7fcd63b-5601-4aa3-8347-c9bd28870918","family":"Audit and Accountability","parameters":[],"subControls":"","tests":[{"testId":"AU-06(03)","uuid":"3346ed1f-1a2d-497f-a8bb-861889dc6a79","test":"Determine if audit records across different repositories are analyzed and correlated to gain organization-wide situational awareness.Automated mechanisms for centralized reviews and analyses include Security Information and Event Management products.
","uuid":"d86f58c5-2944-464d-8141-b078f2f36513","family":"Audit and Accountability","parameters":[],"subControls":"","tests":[{"testId":"AU-06(04)[01]","uuid":"aba990bb-523c-4529-a6d2-561ee93478e6","test":"Determine if the capability to centrally review and analyze audit records from multiple components within the system is provided;Integrated analysis of audit records does not require vulnerability scanning, the generation of performance data, or system monitoring. Rather, integrated analysis requires that the analysis of information generated by scanning, monitoring, or other data collection activities is integrated with the analysis of audit record information. Security Information and Event Management tools can facilitate audit record aggregation or consolidation from multiple system components as well as audit record correlation and analysis. The use of standardized audit record analysis scripts developed by organizations (with localized script adjustments, as necessary) provides more cost-effective approaches for analyzing audit record information collected. The correlation of audit record information with vulnerability scanning information is important in determining the veracity of vulnerability scans of the system and in correlating attack detection events with scanning results. Correlation with performance data can uncover denial-of-service attacks or other types of attacks that result in the unauthorized use of resources. Correlation with system monitoring information can assist in uncovering attacks and in better relating audit information to operational situations.
","uuid":"4fc460dc-c26b-4e07-ac03-2b1176ca1d3d","family":"Audit and Accountability","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"29246b9a-f43c-48b7-a952-7b77ccaf4556","text":"[Selection (one or more): vulnerability scanning information; performance data; system monitoring information; [(NESTED PARAMETER) Assignment for au-06.05_odp.02: data/information collected from other sources]]","parameterId":"au-06.05_odp.01","default":"[Selection (one or more): vulnerability scanning information; performance data; system monitoring information; [(NESTED PARAMETER) Assignment for au-06.05_odp.02: data/information collected from other sources]]"},{"constraints":"","displayName":"","guidance":"","uuid":"1454531d-4dce-45ef-b639-4a2cbd4bcfa5","text":"data/information collected from other sources","parameterId":"au-06.05_odp.02","default":" [Assignment: organization defined data/information collected from other sources] "}],"subControls":"","tests":[{"testId":"AU-06(05)","uuid":"adfba35e-53ca-44d2-967a-2b587a8e0453","test":"Determine if analysis of audit records is integrated with analysis of [SELECTED PARAMETER VALUE(S): [Selection (one or more): vulnerability scanning information; performance data; system monitoring information; [(NESTED PARAMETER) Assignment for au-06.05_odp.02: data/information collected from other sources]] ] to further enhance the ability to identify inappropriate or unusual activity.The correlation of physical audit record information and the audit records from systems may assist organizations in identifying suspicious behavior or supporting evidence of such behavior. For example, the correlation of an individual’s identity for logical access to certain systems with the additional physical security information that the individual was present at the facility when the logical access occurred may be useful in investigations.
","uuid":"600ac191-3f95-424b-87b4-ef6a302e7b3b","family":"Audit and Accountability","parameters":[],"subControls":"","tests":[{"testId":"AU-06(06)","uuid":"a0cf1c30-c3db-4bb6-bcbb-c7c3324c24d1","test":"Determine if information from audit records is correlated with information obtained from monitoring physical access to further enhance the ability to identify suspicious, inappropriate, unusual, or malevolent activity.Organizations specify permitted actions for system processes, roles, and users associated with the review, analysis, and reporting of audit records through system account management activities. Specifying permitted actions on audit record information is a way to enforce the principle of least privilege. Permitted actions are enforced by the system and include read, write, execute, append, and delete.
","uuid":"4c62c2a6-0ab4-4fd5-a6b0-78bd6d4b0ee2","family":"Audit and Accountability","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"6e0ed287-3c09-454b-83d4-2a6b9220dda4","text":"[Selection (one or more): system process; role; user]","parameterId":"au-06.07_odp","default":"[Selection (one or more): system process; role; user]"}],"subControls":"","tests":[{"testId":"AU-06(07)","uuid":"53f3a47d-3702-4c44-a049-6213833dd70e","test":"Determine if the permitted actions for each [SELECTED PARAMETER VALUE(S): [Selection (one or more): system process; role; user] ] associated with the review, analysis, and reporting of audit record information are specified.Full text analysis of privileged commands requires a distinct environment for the analysis of audit record information related to privileged users without compromising such information on the system where the users have elevated privileges, including the capability to execute privileged commands. Full text analysis refers to analysis that considers the full text of privileged commands (i.e., commands and parameters) as opposed to analysis that considers only the name of the command. Full text analysis includes the use of pattern matching and heuristics.
","uuid":"1d8559e2-deb3-4a15-92f4-af7a36652127","family":"Audit and Accountability","parameters":[],"subControls":"","tests":[{"testId":"AU-06(08)","uuid":"4ceeb749-88f6-40d8-be19-b0d0d1d026be","test":"Determine if 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 is performed.Nontechnical sources include records that document organizational policy violations related to harassment incidents and the improper use of information assets. Such information can lead to a directed analytical effort to detect potential malicious insider activity. Organizations limit access to information that is available from nontechnical sources due to its sensitive nature. Limited access minimizes the potential for inadvertent release of privacy-related information to individuals who do not have a need to know. The correlation of information from nontechnical sources with audit record information generally occurs only when individuals are suspected of being involved in an incident. Organizations obtain legal advice prior to initiating such actions.
","uuid":"29fb4836-2ec2-4140-b844-fd942f1fdb48","family":"Audit and Accountability","parameters":[],"subControls":"","tests":[{"testId":"AU-06(09)","uuid":"50e44024-46bd-4fbf-b1b8-3c288173bada","test":"Determine if information from non-technical sources is correlated with audit record information to enhance organization-wide situational awareness.Audit record reduction is a process that manipulates collected audit log information and organizes it into a summary format that is more meaningful to analysts. Audit record reduction and report generation capabilities do not always emanate from the same system or from the same organizational entities that conduct audit logging activities. The audit record reduction capability includes modern data mining techniques with advanced data filters to identify anomalous behavior in audit records. The report generation capability provided by the system can generate customizable reports. Time ordering of audit records can be an issue if the granularity of the timestamp in the record is insufficient.
","uuid":"27d91301-9592-4ca3-9c0d-c578198015b2","family":"Audit and Accountability","parameters":[],"subControls":"","tests":[{"testId":"AU-07a.[01]","uuid":"e68bdc51-5a7f-4563-8801-db7d6afd102a","test":"Determine if an audit record reduction and report generation capability is provided that supports on-demand audit record review, analysis, and reporting requirements and after-the-fact investigations of incidents;Events of interest can be identified by the content of audit records, including system resources involved, information objects accessed, identities of individuals, event types, event locations, event dates and times, Internet Protocol addresses involved, or event success or failure. Organizations may define event criteria to any degree of granularity required, such as locations selectable by a general networking location or by specific system component.
","uuid":"200ea616-9769-4c6a-a745-b161b654e7fe","family":"Audit and Accountability","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"0d4bd0f6-bc8f-4614-bb48-1bc6d489d478","text":"fields within audit records","parameterId":"au-07.01_odp","default":" [Assignment: organization defined fields within audit records] "}],"subControls":"","tests":[{"testId":"AU-07(01)[01]","uuid":"c2a51af7-0dce-4752-96bc-767b389f8332","test":"Determine if the capability to process, sort, and search audit records for events of interest based on [SELECTED PARAMETER VALUE(S): fields within audit records ] are provided;Time stamps generated by the system include date and time. Time is commonly expressed in Coordinated Universal Time (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC. Granularity of time measurements refers to the degree of synchronization between system clocks and reference clocks (e.g., clocks synchronizing within hundreds of milliseconds or tens of milliseconds). Organizations may define different time granularities for different system components. Time service can be critical to other security capabilities such as access control and identification and authentication, depending on the nature of the mechanisms used to support those capabilities.
","uuid":"74cd56f8-0b68-4998-b517-1fd4de8b135e","family":"Audit and Accountability","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"d466f74a-b5dd-48b9-94d8-810ec022042c","text":"granularity of time measurement","parameterId":"au-08_odp","default":" [Assignment: organization defined granularity of time measurement] "}],"subControls":"","tests":[{"testId":"AU-08a.","uuid":"2a425eb3-a799-4b5a-9cce-058727c8359c","test":"Determine if internal system clocks are used to generate timestamps for audit records;Audit information includes all information needed to successfully audit system activity, such as audit records, audit log settings, audit reports, and personally identifiable information. Audit logging tools are those programs and devices used to conduct system audit and logging activities. Protection of audit information focuses on technical protection and limits the ability to access and execute audit logging tools to authorized individuals. Physical protection of audit information is addressed by both media protection controls and physical and environmental protection controls.
","uuid":"20ad23e3-310d-49b4-bddc-789a266a44c6","family":"Audit and Accountability","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"f4880a25-b018-462f-ac4c-da6accc1ac53","text":"personnel or roles","parameterId":"au-09_odp","default":" [Assignment: organization defined personnel or roles] "}],"subControls":"","tests":[{"testId":"AU-09a.","uuid":"07a6cff2-7410-4519-a31a-c22c5fa06e4d","test":"Determine if audit information and audit logging tools are protected from unauthorized access, modification, and deletion;Writing audit trails to hardware-enforced, write-once media applies to the initial generation of audit trails (i.e., the collection of audit records that represents the information to be used for detection, analysis, and reporting purposes) and to the backup of those audit trails. Writing audit trails to hardware-enforced, write-once media does not apply to the initial generation of audit records prior to being written to an audit trail. Write-once, read-many (WORM) media includes Compact Disc-Recordable (CD-R), Blu-Ray Disc Recordable (BD-R), and Digital Versatile Disc-Recordable (DVD-R). In contrast, the use of switchable write-protection media, such as tape cartridges, Universal Serial Bus (USB) drives, Compact Disc Re-Writeable (CD-RW), and Digital Versatile Disc-Read Write (DVD-RW) results in write-protected but not write-once media.
","uuid":"256bd145-3a3c-4cfd-aec9-e99aedb6a4fc","family":"Audit and Accountability","parameters":[],"subControls":"","tests":[{"testId":"AU-09(01)","uuid":"4e58f9b5-b955-4c6a-9824-f340a846f02f","test":"Determine if audit trails are written to hardware-enforced, write-once media.Storing audit records in a repository separate from the audited system or system component helps to ensure that a compromise of the system being audited does not also result in a compromise of the audit records. Storing audit records on separate physical systems or components also preserves the confidentiality and integrity of audit records and facilitates the management of audit records as an organization-wide activity. Storing audit records on separate systems or components applies to initial generation as well as backup or long-term storage of audit records.
","uuid":"4ba72761-0721-4bc6-9fc3-6f513d12ebf6","family":"Audit and Accountability","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"9f72af67-742f-45d7-b6cf-c308c007c381","text":"frequency","parameterId":"au-09.02_odp","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"AU-09(02)","uuid":"e88177ac-d12c-4cc2-b273-9c5488512b86","test":"Determine if audit records are stored [SELECTED PARAMETER VALUE(S): frequency ] in a repository that is part of a physically different system or system component than the system or component being audited.Cryptographic mechanisms used for protecting the integrity of audit information include signed hash functions using asymmetric cryptography. This enables the distribution of the public key to verify the hash information while maintaining the confidentiality of the secret key used to generate the hash.
","uuid":"7b210e5e-c94c-4b18-800b-f675e15379ea","family":"Audit and Accountability","parameters":[],"subControls":"","tests":[{"testId":"AU-09(03)","uuid":"e5276d05-064a-4723-82a7-8f46afb6d6a9","test":"Determine if cryptographic mechanisms to protect the integrity of audit information and audit tools are implemented.Individuals or roles with privileged access to a system and who are also the subject of an audit by that system may affect the reliability of the audit information by inhibiting audit activities or modifying audit records. Requiring privileged access to be further defined between audit-related privileges and other privileges limits the number of users or roles with audit-related privileges.
","uuid":"cfb7a182-1a57-4e39-a8ae-8589aa283cd2","family":"Audit and Accountability","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"d7173102-b01a-4680-b033-cb3b52ba88ed","text":"subset of privileged users or roles","parameterId":"au-09.04_odp","default":" [Assignment: organization defined subset of privileged users or roles] "}],"subControls":"","tests":[{"testId":"AU-09(04)","uuid":"1489c6c2-8622-4a39-8fed-f5403e390a1b","test":"Determine if access to management of audit logging functionality is authorized only to [SELECTED PARAMETER VALUE(S): subset of privileged users or roles ].Organizations may choose different selection options for different types of audit information. Dual authorization mechanisms (also known as two-person control) require the approval of two authorized individuals to execute audit functions. To reduce the risk of collusion, organizations consider rotating dual authorization duties to other individuals. Organizations do not require dual authorization mechanisms when immediate responses are necessary to ensure public and environmental safety.
","uuid":"a2833d5e-71d6-4f40-bdce-4307ef72bfc0","family":"Audit and Accountability","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"a85f7c51-f7bd-4268-85fd-75075e97ad50","text":"[Selection (one or more): movement; deletion]","parameterId":"au-09.05_odp.01","default":"[Selection (one or more): movement; deletion]"},{"constraints":"","displayName":"","guidance":"","uuid":"c285a61d-786b-487e-b39e-6096bcc9d800","text":"audit information","parameterId":"au-09.05_odp.02","default":" [Assignment: organization defined audit information] "}],"subControls":"","tests":[{"testId":"AU-09(05)","uuid":"7f94c046-0c88-40e6-b402-6b54c75f484f","test":"Determine if dual authorization is enforced for the [SELECTED PARAMETER VALUE(S): [Selection (one or more): movement; deletion] ] of [SELECTED PARAMETER VALUE(S): audit information ].Restricting privileged user or role authorizations to read-only helps to limit the potential damage to organizations that could be initiated by such users or roles, such as deleting audit records to cover up malicious activity.
","uuid":"2859d1ff-8ffc-4eef-af55-3c71a93b23b3","family":"Audit and Accountability","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"c2a7db10-314e-46bf-94b8-595a34214e0a","text":"subset of privileged users or roles","parameterId":"au-09.06_odp","default":" [Assignment: organization defined subset of privileged users or roles] "}],"subControls":"","tests":[{"testId":"AU-09(06)","uuid":"c9d3daf9-3a89-4ccc-b30f-0315aeb61d7f","test":"Determine if read-only access to audit information is authorized to [SELECTED PARAMETER VALUE(S): subset of privileged users or roles ].Storing auditing information on a system component running a different operating system reduces the risk of a vulnerability specific to the system, resulting in a compromise of the audit records.
","uuid":"3a9cd86d-c2d4-4b08-a253-2b82a2758107","family":"Audit and Accountability","parameters":[],"subControls":"","tests":[{"testId":"AU-09(07)","uuid":"44a8d918-8c9e-45cf-a5fb-2f1d43b05890","test":"Determine if audit information is stored on a component running a different operating system than the system or component being audited.Types of individual actions covered by non-repudiation include creating information, sending and receiving messages, and approving information. Non-repudiation protects against claims by authors of not having authored certain documents, senders of not having transmitted messages, receivers of not having received messages, and signatories of not having signed documents. Non-repudiation services can be used to determine if information originated from an individual or if an individual took specific actions (e.g., sending an email, signing a contract, approving a procurement request, or receiving specific information). Organizations obtain non-repudiation services by employing various techniques or mechanisms, including digital signatures and digital message receipts.
","uuid":"98b6522e-3b4e-42e4-a25f-505b9f78e80f","family":"Audit and Accountability","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"b7cd5084-2988-4d66-868b-cb7f761986d8","text":"actions","parameterId":"au-10_odp","default":" [Assignment: organization defined actions] "}],"subControls":"","tests":[{"testId":"AU-10","uuid":"cbdbcf6b-ae9f-4b05-851b-fb8795d076e1","test":"Determine if irrefutable evidence is provided that an individual (or process acting on behalf of an individual) has performed [SELECTED PARAMETER VALUE(S): actions ].Binding identities to the information supports audit requirements that provide organizational personnel with the means to identify who produced specific information in the event of an information transfer. Organizations determine and approve the strength of attribute binding between the information producer and the information based on the security category of the information and other relevant risk factors.
","uuid":"6b40294d-43ed-44b5-b3a0-bfe06fb32a63","family":"Audit and Accountability","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"29cbd9f0-0001-4c4f-84e7-f50e3ca10524","text":"strength of binding","parameterId":"au-10.01_odp","default":" [Assignment: organization defined strength of binding] "}],"subControls":"","tests":[{"testId":"AU-10(01)(a)","uuid":"a1359f18-3257-4373-887b-80712a8cb4d6","test":"Determine if the identity of the information producer is bound with the information to [SELECTED PARAMETER VALUE(S): strength of binding ];Validating the binding of the information producer identity to the information prevents the modification of information between production and review. The validation of bindings can be achieved by, for example, using cryptographic checksums. Organizations determine if validations are in response to user requests or generated automatically.
","uuid":"f1a6491f-7e45-4703-b657-626b9db96c4c","family":"Audit and Accountability","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"49b292d0-6dfa-4639-8f01-eaf324201f24","text":"frequency","parameterId":"au-10.02_odp.01","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"bb3f9a21-21f1-4058-be9b-7b6f1e6dae12","text":"actions","parameterId":"au-10.02_odp.02","default":" [Assignment: organization defined actions] "}],"subControls":"","tests":[{"testId":"AU-10(02)(a)","uuid":"f5b5f76d-36a5-4797-a515-e338350ad662","test":"Determine if the binding of the information producer identity to the information is validated at [SELECTED PARAMETER VALUE(S): frequency ];Chain of custody is a process that tracks the movement of evidence through its collection, safeguarding, and analysis life cycle by documenting each individual who handled the evidence, the date and time the evidence was collected or transferred, and the purpose for the transfer. If the reviewer is a human or if the review function is automated but separate from the release or transfer function, the system associates the identity of the reviewer of the information to be released with the information and the information label. In the case of human reviews, maintaining the credentials of reviewers or releasers provides the organization with the means to identify who reviewed and released the information. In the case of automated reviews, it ensures that only approved review functions are used.
","uuid":"a04ea8f3-c9a6-4c5f-afda-2b0f5cd92f4a","family":"Audit and Accountability","parameters":[],"subControls":"","tests":[{"testId":"AU-10(03)","uuid":"3a5d0ff3-ab1f-4e5d-b098-1ddb485e5a08","test":"Determine if reviewer or releaser credentials are maintained within the established chain of custody for information reviewed or released.Validating the binding of the information reviewer identity to the information at transfer or release points prevents the unauthorized modification of information between review and the transfer or release. The validation of bindings can be achieved by using cryptographic checksums. Organizations determine if validations are in response to user requests or generated automatically.
","uuid":"1388ad3e-d5b9-41f3-b3b2-ec1af9e9e3c8","family":"Audit and Accountability","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"f10fceea-4181-4f11-9de1-93cc108d53c5","text":"security domains","parameterId":"au-10.04_odp.01","default":" [Assignment: organization defined security domains] "},{"constraints":"","displayName":"","guidance":"","uuid":"dcdd7a24-feb0-4ed6-a7a4-575b7879ae3c","text":"actions","parameterId":"au-10.04_odp.02","default":" [Assignment: organization defined actions] "}],"subControls":"","tests":[{"testId":"AU-10(04)(a)","uuid":"ad9f8af9-f440-4925-806e-b02ebc8dfa8a","test":"Determine if the binding of the information reviewer identity to the information at the transfer or release points prior to release or transfer between [SELECTED PARAMETER VALUE(S): security domains ] is validated;Organizations retain audit records until it is determined that the records are no longer needed for administrative, legal, audit, or other operational purposes. This includes the retention and availability of audit records relative to Freedom of Information Act (FOIA) requests, subpoenas, and law enforcement actions. Organizations develop standard categories of audit records relative to such types of actions and standard response processes for each type of action. The National Archives and Records Administration (NARA) General Records Schedules provide federal policy on records retention.
","uuid":"ee024f9a-1d56-45c8-9549-9133dd0df155","family":"Audit and Accountability","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"1656c78f-986b-435e-a858-69b8539f48fd","text":"time period","parameterId":"au-11_odp","default":" [Assignment: organization defined time period] "}],"subControls":"","tests":[{"testId":"AU-11","uuid":"41cb08de-b427-4a34-b846-2724b64b72d8","test":"Determine if audit records are retained for [SELECTED PARAMETER VALUE(S): time period ] to provide support for after-the-fact investigations of incidents and to meet regulatory and organizational information retention requirements.Organizations need to access and read audit records requiring long-term storage (on the order of years). Measures employed to help facilitate the retrieval of audit records include converting records to newer formats, retaining equipment capable of reading the records, and retaining the necessary documentation to help personnel understand how to interpret the records.
","uuid":"df59e91d-0043-40e3-ad83-1dcfb0ee2b0e","family":"Audit and Accountability","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"6ba3c7b1-7033-441b-abc8-b51445290f5a","text":"measures","parameterId":"au-11.01_odp","default":" [Assignment: organization defined measures] "}],"subControls":"","tests":[{"testId":"AU-11(01)","uuid":"c657f870-2b3e-4cc3-8d0d-2132b6e1975a","test":"Determine if [SELECTED PARAMETER VALUE(S): measures ] are employed to ensure that long-term audit records generated by the system can be retrieved.Audit records can be generated from many different system components. The event types specified in AU-2d are the event types for which audit logs are to be generated and are a subset of all event types for which the system can generate audit records.
","uuid":"507c9968-390e-4d89-8f8e-1eb3e8d2fd10","family":"Audit and Accountability","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"352d75d1-d4c7-496a-9376-719430a10d88","text":"system components","parameterId":"au-12_odp.01","default":" [Assignment: organization defined system components] "},{"constraints":"","displayName":"","guidance":"","uuid":"792fc2f8-351f-48c0-ba45-0528f44efe38","text":"personnel or roles","parameterId":"au-12_odp.02","default":" [Assignment: organization defined personnel or roles] "}],"subControls":"","tests":[{"testId":"AU-12a.","uuid":"bda9de2b-c86c-4cde-9228-abf75514b209","test":"Determine if audit record generation capability for the event types the system is capable of auditing (defined in au-02_odp[01]) is provided by [SELECTED PARAMETER VALUE(S): system components ];Audit trails are time-correlated if the time stamps in the individual audit records can be reliably related to the time stamps in other audit records to achieve a time ordering of the records within organizational tolerances.
","uuid":"64ee54c3-b651-4305-985a-bc75fe3caae4","family":"Audit and Accountability","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"d1368f0a-2dda-4583-8576-e1ea892c8db3","text":"system components","parameterId":"au-12.01_odp.01","default":" [Assignment: organization defined system components] "},{"constraints":"","displayName":"","guidance":"","uuid":"4109d85f-18a3-46c9-8e91-fecce33c2ccd","text":"level of tolerance","parameterId":"au-12.01_odp.02","default":" [Assignment: organization defined level of tolerance] "}],"subControls":"","tests":[{"testId":"AU-12(01)","uuid":"4d34d3c9-af0f-4b67-9483-0630a9169afd","test":"Determine if audit records from [SELECTED PARAMETER VALUE(S): system components ] are compiled into a system-wide (logical or physical) audit trail that is time-correlated to within [SELECTED PARAMETER VALUE(S): level of tolerance ].Audit records that follow common standards promote interoperability and information exchange between devices and systems. Promoting interoperability and information exchange facilitates the production of event information that can be readily analyzed and correlated. If logging mechanisms do not conform to standardized formats, systems may convert individual audit records into standardized formats when compiling system-wide audit trails.
","uuid":"30871533-cbb7-4795-ae53-2af251511e04","family":"Audit and Accountability","parameters":[],"subControls":"","tests":[{"testId":"AU-12(02)","uuid":"2e315b4c-24c1-4a33-aaf9-c0c2ed5653bc","test":"Determine if a system-wide (logical or physical) audit trail composed of audit records is produced in a standardized format.Permitting authorized individuals to make changes to system logging enables organizations to extend or limit logging as necessary to meet organizational requirements. Logging that is limited to conserve system resources may be extended (either temporarily or permanently) to address certain threat situations. In addition, logging may be limited to a specific set of event types to facilitate audit reduction, analysis, and reporting. Organizations can establish time thresholds in which logging actions are changed (e.g., near real-time, within minutes, or within hours).
","uuid":"20a28573-6d3e-4ec0-b33c-a2d3c90e51fe","family":"Audit and Accountability","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"76018792-a481-4003-9cb2-01b6f5b76594","text":"individuals or roles","parameterId":"au-12.03_odp.01","default":" [Assignment: organization defined individuals or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"85dcd598-651c-4812-9f9e-f9e8c5bc5749","text":"system components","parameterId":"au-12.03_odp.02","default":" [Assignment: organization defined system components] "},{"constraints":"","displayName":"","guidance":"","uuid":"d0d9d8ee-947d-4e83-ac37-24f06e52d5cf","text":"selectable event criteria","parameterId":"au-12.03_odp.03","default":" [Assignment: organization defined selectable event criteria] "},{"constraints":"","displayName":"","guidance":"","uuid":"41c8a952-7e0f-4240-af7d-6ab28778453b","text":"time thresholds","parameterId":"au-12.03_odp.04","default":" [Assignment: organization defined time thresholds] "}],"subControls":"","tests":[{"testId":"AU-12(03)[01]","uuid":"008f5557-685c-4d81-ad27-b5eaa0bbdbb4","test":"Determine if the capability for [SELECTED PARAMETER VALUE(S): individuals or roles ] to change the logging to be performed on [SELECTED PARAMETER VALUE(S): system components ] based on [SELECTED PARAMETER VALUE(S): selectable event criteria ] within [SELECTED PARAMETER VALUE(S): time thresholds ] is provided;Query parameters are explicit criteria that an individual or automated system submits to a system to retrieve data. Auditing of query parameters for datasets that contain personally identifiable information augments the capability of an organization to track and understand the access, usage, or sharing of personally identifiable information by authorized personnel.
","uuid":"3a7928bd-fc71-4a3b-b9e0-78ec5fa72294","family":"Audit and Accountability","parameters":[],"subControls":"","tests":[{"testId":"AU-12(04)[01]","uuid":"74e4211c-495b-4fbb-aa91-14f119726370","test":"Determine if the capability to audit the parameters of user query events for data sets containing personally identifiable information is provided;Unauthorized disclosure of information is a form of data leakage. Open-source information includes social networking sites and code-sharing platforms and repositories. Examples of organizational information include personally identifiable information retained by the organization or proprietary information generated by the organization.
","uuid":"3c477a80-8a96-42db-a94d-1a8619153279","family":"Audit and Accountability","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"5bfdba02-e68e-408c-b3ff-cee04b65f297","text":"open-source information and/or information sites","parameterId":"au-13_odp.01","default":" [Assignment: organization defined open-source information and/or information sites] "},{"constraints":"","displayName":"","guidance":"","uuid":"fa3702bb-1bd4-4858-8724-1fe1b0d647d0","text":"frequency","parameterId":"au-13_odp.02","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"0431d183-7ac0-4c5a-94b3-216e2a391213","text":"personnel or roles","parameterId":"au-13_odp.03","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"7a2bedad-380d-4345-9196-90ac5919eda1","text":"additional actions","parameterId":"au-13_odp.04","default":" [Assignment: organization defined additional actions] "}],"subControls":"","tests":[{"testId":"AU-13a.","uuid":"8540beaf-9681-4718-8895-e22f2c5b3467","test":"Determine if [SELECTED PARAMETER VALUE(S): open-source information and/or information sites ] is/are monitored [SELECTED PARAMETER VALUE(S): frequency ] for evidence of unauthorized disclosure of organizational information;Automated mechanisms include commercial services that provide notifications and alerts to organizations and automated scripts to monitor new posts on websites.
","uuid":"74fea25b-3295-47d9-8096-77cd9bd49671","family":"Audit and Accountability","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"64ddd574-ffa6-4101-9e45-0b89ff261705","text":"automated mechanisms","parameterId":"au-13.01_odp","default":" [Assignment: organization defined automated mechanisms] "}],"subControls":"","tests":[{"testId":"AU-13(01)","uuid":"b583a596-93f8-48b5-8549-aee5f30b642d","test":"Determine if open-source information and information sites are monitored using [SELECTED PARAMETER VALUE(S): automated mechanisms ].Reviewing the current list of open-source information sites being monitored on a regular basis helps to ensure that the selected sites remain relevant. The review also provides the opportunity to add new open-source information sites with the potential to provide evidence of unauthorized disclosure of organizational information. The list of sites monitored can be guided and informed by threat intelligence of other credible sources of information.
","uuid":"a86145b4-abe6-4815-bc0b-9bb3aa30548d","family":"Audit and Accountability","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"5d025a79-6358-4efa-8876-65047c8ccd05","text":"frequency","parameterId":"au-13.02_odp","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"AU-13(02)","uuid":"b32df999-7ac3-4eef-9aeb-d808d349fa01","test":"Determine if the list of open-source information sites being monitored is reviewed [SELECTED PARAMETER VALUE(S): frequency ].The unauthorized use or replication of organizational information by external entities can cause adverse impacts on organizational operations and assets, including damage to reputation. Such activity can include the replication of an organizational website by an adversary or hostile threat actor who attempts to impersonate the web-hosting organization. Discovery tools, techniques, and processes used to determine if external entities are replicating organizational information in an unauthorized manner include scanning external websites, monitoring social media, and training staff to recognize the unauthorized use of organizational information.
","uuid":"2dbf35b9-71de-41cb-9c73-e85e36afaf19","family":"Audit and Accountability","parameters":[],"subControls":"","tests":[{"testId":"AU-13(03)","uuid":"544a9a9a-a313-4542-b832-86ab456fd60e","test":"Determine if discovery techniques, processes, and tools are employed to determine if external entities are replicating organizational information in an unauthorized manner.Session audits can include monitoring keystrokes, tracking websites visited, and recording information and/or file transfers. Session audit capability is implemented in addition to event logging and may involve implementation of specialized session capture technology. Organizations consider how session auditing can reveal information about individuals that may give rise to privacy risk as well as how to mitigate those risks. Because session auditing can impact system and network performance, organizations activate the capability under well-defined situations (e.g., the organization is suspicious of a specific individual). Organizations consult with legal counsel, civil liberties officials, and privacy officials to ensure that any legal, privacy, civil rights, or civil liberties issues, including the use of personally identifiable information, are appropriately addressed.
","uuid":"7fe5dd7c-a24f-49c8-987f-157a33972fa4","family":"Audit and Accountability","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"b72d9b7a-7fc3-4cad-beef-f62617499828","text":"users or roles","parameterId":"au-14_odp.01","default":" [Assignment: organization defined users or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"08aad27f-9d64-4be7-a477-0d9f72c36c47","text":"[Selection (one or more): record; view; hear; log]","parameterId":"au-14_odp.02","default":"[Selection (one or more): record; view; hear; log]"},{"constraints":"","displayName":"","guidance":"","uuid":"c8bed25c-040c-43d3-bc7f-99807ca43d29","text":"circumstances","parameterId":"au-14_odp.03","default":" [Assignment: organization defined circumstances] "}],"subControls":"","tests":[{"testId":"AU-14a.[01]","uuid":"8b830f82-137e-471d-90cf-cc5e6db2648c","test":"Determine if [SELECTED PARAMETER VALUE(S): users or roles ] are provided with the capability to [SELECTED PARAMETER VALUE(S): [Selection (one or more): record; view; hear; log] ] the content of a user session under [SELECTED PARAMETER VALUE(S): circumstances ];The automatic initiation of session audits at startup helps to ensure that the information being captured on selected individuals is complete and not subject to compromise through tampering by malicious threat actors.
","uuid":"a77efe89-9888-46a0-8685-f6dd0bc15e70","family":"Audit and Accountability","parameters":[],"subControls":"","tests":[{"testId":"AU-14(01)","uuid":"5e9f92dd-ded9-4292-ac07-ff33ae89e2c9","test":"Determine if session audits are initiated automatically at system start-up.None.
","uuid":"56fdb583-c167-4fb2-a749-b172445ed535","family":"Audit and Accountability","parameters":[],"subControls":"","tests":[{"testId":"AU-14(03)[01]","uuid":"ce26d662-828f-4c79-9935-f1c99bb909a4","test":"Determine if the capability for authorized users to remotely view and hear content related to an established user session in real time is provided;When organizations use systems or services of external organizations, the audit logging capability necessitates a coordinated, cross-organization approach. For example, maintaining the identity of individuals who request specific services across organizational boundaries may often be difficult, and doing so may prove to have significant performance and privacy ramifications. Therefore, it is often the case that cross-organizational audit logging simply captures the identity of individuals who issue requests at the initial system, and subsequent systems record that the requests originated from authorized individuals. Organizations consider including processes for coordinating audit information requirements and protection of audit information in information exchange agreements.
","uuid":"5d717051-d65a-4574-b124-5c844e9d4373","family":"Audit and Accountability","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"744f0b7f-7310-4789-834c-8acd8aadd599","text":"methods","parameterId":"au-16_odp.01","default":" [Assignment: organization defined methods] "},{"constraints":"","displayName":"","guidance":"","uuid":"8a217bfd-6a49-46bb-8a64-4e0205315d0f","text":"audit information","parameterId":"au-16_odp.02","default":" [Assignment: organization defined audit information] "}],"subControls":"","tests":[{"testId":"AU-16","uuid":"d15b5906-94f2-425e-a9f1-186ce5cd3e0f","test":"Determine if [SELECTED PARAMETER VALUE(S): methods ] for coordinating [SELECTED PARAMETER VALUE(S): audit information ] among external organizations when audit information is transmitted across organizational boundaries are employed.Identity preservation is applied when there is a need to be able to trace actions that are performed across organizational boundaries to a specific individual.
","uuid":"1bd07809-add7-47dd-a758-b6b0f8992e4b","family":"Audit and Accountability","parameters":[],"subControls":"","tests":[{"testId":"AU-16(01)","uuid":"9901e1e6-2dbb-4ef7-846e-30121ba5623f","test":"Determine if the identity of individuals in cross-organizational audit trails is preserved.Due to the distributed nature of the audit information, cross-organization sharing of audit information may be essential for effective analysis of the auditing being performed. For example, the audit records of one organization may not provide sufficient information to determine the appropriate or inappropriate use of organizational information resources by individuals in other organizations. In some instances, only individuals’ home organizations have the appropriate knowledge to make such determinations, thus requiring the sharing of audit information among organizations.
","uuid":"4ea7a98f-dd16-4488-9052-5f2d4af1893d","family":"Audit and Accountability","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"c90bc088-7370-4d30-b5db-eb2d707245f3","text":"organizations","parameterId":"au-16.02_odp.01","default":" [Assignment: organization defined organizations] "},{"constraints":"","displayName":"","guidance":"","uuid":"cf766254-6c21-4be2-9e24-bb1834de2442","text":"cross-organizational sharing agreements","parameterId":"au-16.02_odp.02","default":" [Assignment: organization defined cross-organizational sharing agreements] "}],"subControls":"","tests":[{"testId":"AU-16(02)","uuid":"74c31ad4-f08f-4902-b951-0fe987fff881","test":"Determine if cross-organizational audit information is provided to [SELECTED PARAMETER VALUE(S): organizations ] based on [SELECTED PARAMETER VALUE(S): cross-organizational sharing agreements ].Preserving identities in audit trails could have privacy ramifications, such as enabling the tracking and profiling of individuals, but may not be operationally necessary. These risks could be further amplified when transmitting information across organizational boundaries. Implementing privacy-enhancing cryptographic techniques can disassociate individuals from audit information and reduce privacy risk while maintaining accountability.
","uuid":"7a96420a-4c98-476e-bc77-bc9ba5ec4831","family":"Audit and Accountability","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"c1b0c77f-71cd-4221-8cc1-198f8ccaea7b","text":"measures","parameterId":"au-16.03_odp","default":" [Assignment: organization defined measures] "}],"subControls":"","tests":[{"testId":"AU-16(03)","uuid":"5a817025-31a5-4904-bb09-783d060015c0","test":"Determine if [SELECTED PARAMETER VALUE(S): measures ] are implemented to disassociate individuals from audit information transmitted across organizational boundaries.Assessment, authorization, and monitoring policy and procedures address the controls in the CA family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of assessment, authorization, and monitoring policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission or business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to assessment, authorization, and monitoring policy and procedures include assessment or audit findings, security incidents or breaches, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure.
","uuid":"62b6c80d-4a6d-4286-b418-36d865f3e4cf","family":"Assessment, Authorization, and Monitoring","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"b0ce3d70-da17-469a-a597-da5c47a97b90","text":"organization-defined personnel or roles","parameterId":"ca-1_prm_1","default":" [Assignment: organization-defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"dd9bd18a-3624-4a5b-95fa-8bf589f58750","text":"personnel or roles","parameterId":"ca-01_odp.01","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"06ca63a2-3167-4d8a-8c9b-78e29e935124","text":"personnel or roles","parameterId":"ca-01_odp.02","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"71d97a01-7ace-460a-b321-84e1aa05e7ba","text":"[Selection (one or more): organization-level; mission/business process-level; system-level]","parameterId":"ca-01_odp.03","default":"[Selection (one or more): organization-level; mission/business process-level; system-level]"},{"constraints":"","displayName":"","guidance":"","uuid":"2a719135-f1f8-4d12-86bb-ab2354862e49","text":"official","parameterId":"ca-01_odp.04","default":" [Assignment: organization defined official] "},{"constraints":"","displayName":"","guidance":"","uuid":"a19b3070-4bed-446e-a31f-62c17d2e2f8b","text":"frequency","parameterId":"ca-01_odp.05","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"da09262b-8832-4bb0-857a-9a7bcba0dc8c","text":"events","parameterId":"ca-01_odp.06","default":" [Assignment: organization defined events] "},{"constraints":"","displayName":"","guidance":"","uuid":"ae4a9bfb-5b1d-468a-9830-836e948ceeb0","text":"frequency","parameterId":"ca-01_odp.07","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"a839dde8-99e9-4331-bb62-dbedb80193ce","text":"events","parameterId":"ca-01_odp.08","default":" [Assignment: organization defined events] "}],"subControls":"","tests":[{"testId":"CA-01a.[01]","uuid":"9274013c-90d1-4ba1-b0c5-7992fda7bea4","test":"Determine if an assessment, authorization, and monitoring policy is developed and documented;Organizations ensure that control assessors possess the required skills and technical expertise to develop effective assessment plans and to conduct assessments of system-specific, hybrid, common, and program management controls, as appropriate. The required skills include general knowledge of risk management concepts and approaches as well as comprehensive knowledge of and experience with the hardware, software, and firmware system components implemented.
Organizations assess controls in systems and the environments in which those systems operate as part of initial and ongoing authorizations, continuous monitoring, FISMA annual assessments, system design and development, systems security engineering, privacy engineering, and the system development life cycle. Assessments help to ensure that organizations meet information security and privacy requirements, identify weaknesses and deficiencies in the system design and development process, provide essential information needed to make risk-based decisions as part of authorization processes, and comply with vulnerability mitigation procedures. Organizations conduct assessments on the implemented controls as documented in security and privacy plans. Assessments can also be conducted throughout the system development life cycle as part of systems engineering and systems security engineering processes. The design for controls can be assessed as RFPs are developed, responses assessed, and design reviews conducted. If a design to implement controls and subsequent implementation in accordance with the design are assessed during development, the final control testing can be a simple confirmation utilizing previously completed control assessment and aggregating the outcomes.
Organizations may develop a single, consolidated security and privacy assessment plan for the system or maintain separate plans. A consolidated assessment plan clearly delineates the roles and responsibilities for control assessment. If multiple organizations participate in assessing a system, a coordinated approach can reduce redundancies and associated costs.
Organizations can use other types of assessment activities, such as vulnerability scanning and system monitoring, to maintain the security and privacy posture of systems during the system life cycle. Assessment reports document assessment results in sufficient detail, as deemed necessary by organizations, to determine the accuracy and completeness of the reports and whether the controls are implemented correctly, operating as intended, and producing the desired outcome with respect to meeting requirements. Assessment results are provided to the individuals or roles appropriate for the types of assessments being conducted. For example, assessments conducted in support of authorization decisions are provided to authorizing officials, senior agency officials for privacy, senior agency information security officers, and authorizing official designated representatives.
To satisfy annual assessment requirements, organizations can use assessment results from the following sources: initial or ongoing system authorizations, continuous monitoring, systems engineering processes, or system development life cycle activities. Organizations ensure that assessment results are current, relevant to the determination of control effectiveness, and obtained with the appropriate level of assessor independence. Existing control assessment results can be reused to the extent that the results are still valid and can also be supplemented with additional assessments as needed. After the initial authorizations, organizations assess controls during continuous monitoring. Organizations also establish the frequency for ongoing assessments in accordance with organizational continuous monitoring strategies. External audits, including audits by external entities such as regulatory agencies, are outside of the scope of CA-2.
","uuid":"3efe28f8-337f-4483-b7c2-c38afb912762","family":"Assessment, Authorization, and Monitoring","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"506af71e-3928-4fd2-b88e-fd596e27332e","text":"assessment frequency","parameterId":"ca-02_odp.01","default":" [Assignment: organization defined assessment frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"3bd8ed2b-659e-4142-8979-470381107ca4","text":"individuals or roles","parameterId":"ca-02_odp.02","default":" [Assignment: organization defined individuals or roles] "}],"subControls":"","tests":[{"testId":"CA-02a.","uuid":"68c8de88-dad5-4d06-ab71-0a15d51d81aa","test":"Determine if an appropriate assessor or assessment team is selected for the type of assessment to be conducted;Independent assessors or assessment teams are individuals or groups who conduct impartial assessments of systems. Impartiality means that assessors are free from any perceived or actual conflicts of interest regarding the development, operation, sustainment, or management of the systems under assessment or the determination of control effectiveness. To achieve impartiality, assessors do not create a mutual or conflicting interest with the organizations where the assessments are being conducted, assess their own work, act as management or employees of the organizations they are serving, or place themselves in positions of advocacy for the organizations acquiring their services.
Independent assessments can be obtained from elements within organizations or be contracted to public or private sector entities outside of organizations. Authorizing officials determine the required level of independence based on the security categories of systems and/or the risk to organizational operations, organizational assets, or individuals. Authorizing officials also determine if the level of assessor independence provides sufficient assurance that the results are sound and can be used to make credible, risk-based decisions. Assessor independence determination includes whether contracted assessment services have sufficient independence, such as when system owners are not directly involved in contracting processes or cannot influence the impartiality of the assessors conducting the assessments. During the system design and development phase, having independent assessors is analogous to having independent SMEs involved in design reviews.
When organizations that own the systems are small or the structures of the organizations require that assessments be conducted by individuals that are in the developmental, operational, or management chain of the system owners, independence in assessment processes can be achieved by ensuring that assessment results are carefully reviewed and analyzed by independent teams of experts to validate the completeness, accuracy, integrity, and reliability of the results. Assessments performed for purposes other than to support authorization decisions are more likely to be useable for such decisions when performed by assessors with sufficient independence, thereby reducing the need to repeat assessments.
","uuid":"8b486d04-e583-48f9-b746-c5e90ed66254","family":"Assessment, Authorization, and Monitoring","parameters":[],"subControls":"","tests":[{"testId":"CA-02(01)","uuid":"ff5c5552-4733-451d-8afe-e18ff862d47c","test":"Determine if independent assessors or assessment teams are employed to conduct control assessments.Organizations can conduct specialized assessments, including verification and validation, system monitoring, insider threat assessments, malicious user testing, and other forms of testing. These assessments can improve readiness by exercising organizational capabilities and indicating current levels of performance as a means of focusing actions to improve security and privacy. Organizations conduct specialized assessments in accordance with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Authorizing officials approve the assessment methods in coordination with the organizational risk executive function. Organizations can include vulnerabilities uncovered during assessments into vulnerability remediation processes. Specialized assessments can also be conducted early in the system development life cycle (e.g., during initial design, development, and unit testing).
","uuid":"d9bdd4c4-ab0a-4ea3-b90a-6ef917c00e7e","family":"Assessment, Authorization, and Monitoring","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"e8093173-d6b6-4301-914e-4ba412fdc3bc","text":"specialized assessment frequency","parameterId":"ca-02.02_odp.01","default":" [Assignment: organization defined specialized assessment frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"13e4dc80-1be4-4f8b-a899-d3e1c037ed39","text":"[Selection: announced; unannounced]","parameterId":"ca-02.02_odp.02","default":"[Selection: announced; unannounced]"},{"constraints":"","displayName":"","guidance":"","uuid":"472c9661-bffb-4b85-91bb-b2e7f950dd0d","text":"[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; [(NESTED PARAMETER) Assignment for ca-02.02_odp.04: other forms of assessment]]","parameterId":"ca-02.02_odp.03","default":"[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; [(NESTED PARAMETER) Assignment for ca-02.02_odp.04: other forms of assessment]]"},{"constraints":"","displayName":"","guidance":"","uuid":"392b1245-bfa7-46c3-a69f-ae1fe64f59f7","text":"other forms of assessment","parameterId":"ca-02.02_odp.04","default":" [Assignment: organization defined other forms of assessment] "}],"subControls":"","tests":[{"testId":"CA-02(02)","uuid":"c1673376-d80c-4f31-a549-0a35d94a47b3","test":"Determine if [SELECTED PARAMETER VALUE(S): specialized assessment frequency ], [SELECTED PARAMETER VALUE(S): [Selection: announced; unannounced] ], [SELECTED PARAMETER VALUE(S): [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; [(NESTED PARAMETER) Assignment for ca-02.02_odp.04: other forms of assessment]] ] are included as part of control assessments.Organizations may rely on control assessments of organizational systems by other (external) organizations. Using such assessments and reusing existing assessment evidence can decrease the time and resources required for assessments by limiting the independent assessment activities that organizations need to perform. The factors that organizations consider in determining whether to accept assessment results from external organizations can vary. Such factors include the organization’s past experience with the organization that conducted the assessment, the reputation of the assessment organization, the level of detail of supporting assessment evidence provided, and mandates imposed by applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Accredited testing laboratories that support the Common Criteria Program ISO 15408-1 , the NIST Cryptographic Module Validation Program (CMVP), or the NIST Cryptographic Algorithm Validation Program (CAVP) can provide independent assessment results that organizations can leverage.
","uuid":"2129430d-d034-4c7f-9611-546adfe60f18","family":"Assessment, Authorization, and Monitoring","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"39f66397-ee16-4a58-b7cf-ae7a828c6757","text":"external organizations","parameterId":"ca-02.03_odp.01","default":" [Assignment: organization defined external organizations] "},{"constraints":"","displayName":"","guidance":"","uuid":"439cf48b-9e24-434e-bf4a-b200ac4d262e","text":"system","parameterId":"ca-02.03_odp.02","default":" [Assignment: organization defined system] "},{"constraints":"","displayName":"","guidance":"","uuid":"1a7cb731-5dab-4d39-b6c1-b0c6dc6f24e8","text":"requirements","parameterId":"ca-02.03_odp.03","default":" [Assignment: organization defined requirements] "}],"subControls":"","tests":[{"testId":"CA-02(03)","uuid":"315245a7-5514-40ec-82eb-60d53ad28695","test":"Determine if the results of control assessments performed by [SELECTED PARAMETER VALUE(S): external organizations ] on [SELECTED PARAMETER VALUE(S): system ] are leveraged when the assessment meets [SELECTED PARAMETER VALUE(S): requirements ].System information exchange requirements apply to information exchanges between two or more systems. System information exchanges include connections via leased lines or virtual private networks, connections to internet service providers, database sharing or exchanges of database transaction information, connections and exchanges with cloud services, exchanges via web-based services, or exchanges of files via file transfer protocols, network protocols (e.g., IPv4, IPv6), email, or other organization-to-organization communications. Organizations consider the risk related to new or increased threats that may be introduced when systems exchange information with other systems that may have different security and privacy requirements and controls. This includes systems within the same organization and systems that are external to the organization. A joint authorization of the systems exchanging information, as described in CA-6(1) or CA-6(2) , may help to communicate and reduce risk.
Authorizing officials determine the risk associated with system information exchange and the controls needed for appropriate risk mitigation. The types of agreements selected are based on factors such as the impact level of the information being exchanged, the relationship between the organizations exchanging information (e.g., government to government, government to business, business to business, government or business to service provider, government or business to individual), or the level of access to the organizational system by users of the other system. If systems that exchange information have the same authorizing official, organizations need not develop agreements. Instead, the interface characteristics between the systems (e.g., how the information is being exchanged. how the information is protected) are described in the respective security and privacy plans. If the systems that exchange information have different authorizing officials within the same organization, the organizations can develop agreements or provide the same information that would be provided in the appropriate agreement type from CA-3a in the respective security and privacy plans for the systems. Organizations may incorporate agreement information into formal contracts, especially for information exchanges established between federal agencies and nonfederal organizations (including service providers, contractors, system developers, and system integrators). Risk considerations include systems that share the same networks.
","uuid":"6edf8204-9a19-43bf-b432-d97bbd8d755d","family":"Assessment, Authorization, and Monitoring","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"ba64f51a-b965-450e-beac-6fa6aec8ee54","text":"[Selection (one or more): interconnection security agreements; information exchange security agreements; memoranda of understanding or agreement; service level agreements; user agreements; non-disclosure agreements; [(NESTED PARAMETER) Assignment for ca-03_odp.02: type of agreement]]","parameterId":"ca-03_odp.01","default":"[Selection (one or more): interconnection security agreements; information exchange security agreements; memoranda of understanding or agreement; service level agreements; user agreements; non-disclosure agreements; [(NESTED PARAMETER) Assignment for ca-03_odp.02: type of agreement]]"},{"constraints":"","displayName":"","guidance":"","uuid":"cb6fd884-fb77-4388-b1e0-d1ab8d61d35a","text":"type of agreement","parameterId":"ca-03_odp.02","default":" [Assignment: organization defined type of agreement] "},{"constraints":"","displayName":"","guidance":"","uuid":"70425328-9300-445a-8fdd-9e99292cc30d","text":"frequency","parameterId":"ca-03_odp.03","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"CA-03a.","uuid":"2c7ade03-ef94-4aaf-adae-06553fb6136c","test":"Determine if the exchange of information between the system and other systems is approved and managed using [SELECTED PARAMETER VALUE(S): [Selection (one or more): interconnection security agreements; information exchange security agreements; memoranda of understanding or agreement; service level agreements; user agreements; non-disclosure agreements; [(NESTED PARAMETER) Assignment for ca-03_odp.02: type of agreement]] ];To prevent unauthorized individuals and systems from making information transfers to protected systems, the protected system verifies—via independent means— whether the individual or system attempting to transfer information is authorized to do so. Verification of the authorization to transfer information also applies to control plane traffic (e.g., routing and DNS) and services (e.g., authenticated SMTP relays).
","uuid":"626914ee-df9e-44b8-9b92-ff6a9bd28625","family":"Assessment, Authorization, and Monitoring","parameters":[],"subControls":"","tests":[{"testId":"CA-03(06)","uuid":"e8d05d71-1833-4c86-b7c1-6fce4fdd5967","test":"Determine if individuals or systems transferring data between interconnecting systems have the requisite authorizations (i.e., write permissions or privileges) prior to accepting such data.Transitive or downstream
information exchanges are information exchanges between the system or systems with which the organizational system exchanges information and other systems. For mission-essential systems, services, and applications, including high value assets, it is necessary to identify such information exchanges. The transparency of the controls or protection measures in place in such downstream systems connected directly or indirectly to organizational systems is essential to understanding the security and privacy risks resulting from those information exchanges. Organizational systems can inherit risk from downstream systems through transitive connections and information exchanges, which can make the organizational systems more susceptible to threats, hazards, and adverse impacts.
Plans of action and milestones are useful for any type of organization to track planned remedial actions. Plans of action and milestones are required in authorization packages and subject to federal reporting requirements established by OMB.
","uuid":"97450633-6180-4a4d-9028-eecd0f535eb8","family":"Assessment, Authorization, and Monitoring","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"f1439d72-91b3-417e-9cd8-094045250ade","text":"frequency","parameterId":"ca-05_odp","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"CA-05a.","uuid":"aa6fc841-ab33-466b-861b-05a5952b44d6","test":"Determine if a plan of action and milestones for the system is developed 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;Using automated tools helps maintain the accuracy, currency, and availability of the plan of action and milestones and facilitates the coordination and sharing of security and privacy information throughout the organization. Such coordination and information sharing help to identify systemic weaknesses or deficiencies in organizational systems and ensure that appropriate resources are directed at the most critical system vulnerabilities in a timely manner.
","uuid":"2c9b7ac4-53f4-489b-9a2f-c2725caeb405","family":"Assessment, Authorization, and Monitoring","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"43fcc861-65ae-47d7-b63a-d95b741af7b0","text":"automated mechanisms","parameterId":"ca-05.01_odp","default":" [Assignment: organization defined automated mechanisms] "}],"subControls":"","tests":[{"testId":"CA-05(01)","uuid":"fdaa2538-8b81-4aa3-9d17-bd1a393fc812","test":"Determine if [SELECTED PARAMETER VALUE(S): automated mechanisms ] are used to ensure the accuracy, currency, and availability of the plan of action and milestones for the system.Authorizations are official management decisions by senior officials to authorize operation of systems, authorize the use of common controls for inheritance by organizational systems, and explicitly accept the risk to organizational operations and assets, individuals, other organizations, and the Nation based on the implementation of agreed-upon controls. Authorizing officials provide budgetary oversight for organizational systems and common controls or assume responsibility for the mission and business functions supported by those systems or common controls. The authorization process is a federal responsibility, and therefore, authorizing officials must be federal employees. Authorizing officials are both responsible and accountable for security and privacy risks associated with the operation and use of organizational systems. Nonfederal organizations may have similar processes to authorize systems and senior officials that assume the authorization role and associated responsibilities.
Authorizing officials issue ongoing authorizations of systems based on evidence produced from implemented continuous monitoring programs. Robust continuous monitoring programs reduce the need for separate reauthorization processes. Through the employment of comprehensive continuous monitoring processes, the information contained in authorization packages (i.e., security and privacy plans, assessment reports, and plans of action and milestones) is updated on an ongoing basis. This provides authorizing officials, common control providers, and system owners with an up-to-date status of the security and privacy posture of their systems, controls, and operating environments. To reduce the cost of reauthorization, authorizing officials can leverage the results of continuous monitoring processes to the maximum extent possible as the basis for rendering reauthorization decisions.
","uuid":"998fde29-a2fa-4c27-876f-a3c1989ca600","family":"Assessment, Authorization, and Monitoring","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"43902be2-055a-475c-839d-fe7939fda07f","text":"frequency","parameterId":"ca-06_odp","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"CA-06a.","uuid":"0cf5b5f3-7691-421f-b59d-6b49aa47a2b9","test":"Determine if a senior official is assigned as the authorizing official for the system;Assigning multiple authorizing officials from the same organization to serve as co-authorizing officials for the system increases the level of independence in the risk-based decision-making process. It also implements the concepts of separation of duties and dual authorization as applied to the system authorization process. The intra-organization joint authorization process is most relevant for connected systems, shared systems, and systems with multiple information owners.
","uuid":"434b3944-fcd2-44fc-98d8-1767fe5a1c16","family":"Assessment, Authorization, and Monitoring","parameters":[],"subControls":"","tests":[{"testId":"CA-06(01)[01]","uuid":"80ea5ea9-fb2a-44bc-b4cb-0a17a2763e12","test":"Determine if a joint authorization process is employed for the system;Assigning multiple authorizing officials, at least one of whom comes from an external organization, to serve as co-authorizing officials for the system increases the level of independence in the risk-based decision-making process. It implements the concepts of separation of duties and dual authorization as applied to the system authorization process. Employing authorizing officials from external organizations to supplement the authorizing official from the organization that owns or hosts the system may be necessary when the external organizations have a vested interest or equities in the outcome of the authorization decision. The inter-organization joint authorization process is relevant and appropriate for connected systems, shared systems or services, and systems with multiple information owners. The authorizing officials from the external organizations are key stakeholders of the system undergoing authorization.
","uuid":"6356518f-2610-48e4-8621-365110e247e5","family":"Assessment, Authorization, and Monitoring","parameters":[],"subControls":"","tests":[{"testId":"CA-06(02)[01]","uuid":"e6be6ce2-3fa4-4ec2-90c2-740b32e05f3a","test":"Determine if a joint authorization process is employed for the system;Continuous monitoring at the system level facilitates ongoing awareness of the system security and privacy posture to support organizational risk management decisions. The terms continuous
and ongoing
imply that organizations assess and monitor their controls and risks at a frequency sufficient to support risk-based decisions. Different types of controls may require different monitoring frequencies. The results of continuous monitoring generate risk response actions by organizations. When monitoring the effectiveness of multiple controls that have been grouped into capabilities, a root-cause analysis may be needed to determine the specific control that has failed. Continuous monitoring programs allow organizations to maintain the authorizations of systems and common controls in highly dynamic environments of operation with changing mission and business needs, threats, vulnerabilities, and technologies. Having access to security and privacy information on a continuing basis through reports and dashboards gives organizational officials the ability to make effective and timely risk management decisions, including ongoing authorization decisions.
Automation supports more frequent updates to hardware, software, and firmware inventories, authorization packages, and other system information. Effectiveness is further enhanced when continuous monitoring outputs are formatted to provide information that is specific, measurable, actionable, relevant, and timely. Continuous monitoring activities are scaled in accordance with the security categories of systems. Monitoring requirements, including the need for specific monitoring, may be referenced in other controls and control enhancements, such as AC-2g, AC-2(7), AC-2(12)(a), AC-2(7)(b), AC-2(7)(c), AC-17(1), AT-4a, AU-13, AU-13(1), AU-13(2), CM-3f, CM-6d, CM-11c, IR-5, MA-2b, MA-3a, MA-4a, PE-3d, PE-6, PE-14b, PE-16, PE-20, PM-6, PM-23, PM-31, PS-7e, SA-9c, SR-4, SC-5(3)(b), SC-7a, SC-7(24)(b), SC-18b, SC-43b , and SI-4.
","uuid":"34dd10ce-80f2-46a5-be32-0c91d28241a8","family":"Assessment, Authorization, and Monitoring","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"ef2a810f-872e-41ff-bdc0-4a9a65101f87","text":"organization-defined personnel or roles","parameterId":"ca-7_prm_4","default":" [Assignment: organization-defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"c1a4cda9-d5ad-45c4-9b94-b1ad0b7fe91c","text":"organization-defined frequency","parameterId":"ca-7_prm_5","default":" [Assignment: organization-defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"d0f10140-63a6-4e2a-8977-0af0b6e19379","text":"system-level metrics","parameterId":"ca-07_odp.01","default":" [Assignment: organization defined system-level metrics] "},{"constraints":"","displayName":"","guidance":"","uuid":"70f8da20-2b78-49c5-a0cf-0dd2397c57da","text":"frequencies","parameterId":"ca-07_odp.02","default":" [Assignment: organization defined frequencies] "},{"constraints":"","displayName":"","guidance":"","uuid":"930e1fb8-4e27-4c21-ae61-d78a164c58b5","text":"frequencies","parameterId":"ca-07_odp.03","default":" [Assignment: organization defined frequencies] "},{"constraints":"","displayName":"","guidance":"","uuid":"5ba225b1-2400-4539-8401-42b207972f48","text":"personnel or roles","parameterId":"ca-07_odp.04","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"e08c770d-18ab-4e31-9e6e-cfa664bed68c","text":"frequency","parameterId":"ca-07_odp.05","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"faca3e90-7ffb-498f-8000-6161a2a66bbd","text":"personnel or roles","parameterId":"ca-07_odp.06","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"22011514-9cfd-4d09-b660-67531998beec","text":"frequency","parameterId":"ca-07_odp.07","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"CA-07[01]","uuid":"730ef601-a41b-4e37-9d37-2e701b9db0d9","test":"Determine if a system-level continuous monitoring strategy is developed;Organizations maximize the value of control assessments by requiring that assessments be conducted by assessors with appropriate levels of independence. The level of required independence is based on organizational continuous monitoring strategies. Assessor independence provides a degree of impartiality to the monitoring process. To achieve such impartiality, assessors do not create a mutual or conflicting interest with the organizations where the assessments are being conducted, assess their own work, act as management or employees of the organizations they are serving, or place themselves in advocacy positions for the organizations acquiring their services.
","uuid":"4fedbd43-e7c3-4dbc-9828-b8c0f7b3aee9","family":"Assessment, Authorization, and Monitoring","parameters":[],"subControls":"","tests":[{"testId":"CA-07(01)","uuid":"5ba016d9-07ab-476e-a687-969acd0e154b","test":"Determine if independent assessors or assessment teams are employed to monitor the controls in the system on an ongoing basis.Trend analyses include examining recent threat information that addresses the types of threat events that have occurred in the organization or the Federal Government, success rates of certain types of attacks, emerging vulnerabilities in technologies, evolving social engineering techniques, the effectiveness of configuration settings, results from multiple control assessments, and findings from Inspectors General or auditors.
","uuid":"8f68cf1a-ad37-43bb-b132-e4f4dc32c97a","family":"Assessment, Authorization, and Monitoring","parameters":[],"subControls":"","tests":[{"testId":"CA-07(03)[01]","uuid":"a29f01ca-7c46-40fc-8bc0-4568c4aa7d36","test":"Determine if trend analysis is employed to determine if control implementations used in the continuous monitoring process need to be modified based on empirical data;Risk monitoring is informed by the established organizational risk tolerance. Effectiveness monitoring determines the ongoing effectiveness of the implemented risk response measures. Compliance monitoring verifies that required risk response measures are implemented. It also verifies that security and privacy requirements are satisfied. Change monitoring identifies changes to organizational systems and environments of operation that may affect security and privacy risk.
","uuid":"4089687c-d3e6-448f-a9d2-12b2308dcd28","family":"Assessment, Authorization, and Monitoring","parameters":[],"subControls":"","tests":[{"testId":"CA-07(04)(a)","uuid":"5ad11d64-e093-4870-959f-0d565409c4b8","test":"Determine if effectiveness monitoring is included in risk monitoring;Security and privacy controls are often added incrementally to a system. As a result, policies for selecting and implementing controls may be inconsistent, and the controls could fail to work together in a consistent or coordinated manner. At a minimum, the lack of consistency and coordination could mean that there are unacceptable security and privacy gaps in the system. At worst, it could mean that some of the controls implemented in one location or by one component are actually impeding the functionality of other controls (e.g., encrypting internal network traffic can impede monitoring). In other situations, failing to consistently monitor all implemented network protocols (e.g., a dual stack of IPv4 and IPv6) may create unintended vulnerabilities in the system that could be exploited by adversaries. It is important to validate—through testing, monitoring, and analysis—that the implemented controls are operating in a consistent, coordinated, non-interfering manner.
","uuid":"bd95c70d-932f-45e6-aeb1-bc04b5dec4ef","family":"Assessment, Authorization, and Monitoring","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"2d06ebd6-812f-41fc-a5bd-498915e13b87","text":"organization-defined actions","parameterId":"ca-7.5_prm_1","default":" [Assignment: organization-defined actions] "},{"constraints":"","displayName":"","guidance":"","uuid":"b23c0235-8756-4993-8558-0455cd0db52a","text":"actions","parameterId":"ca-07.05_odp.01","default":" [Assignment: organization defined actions] "},{"constraints":"","displayName":"","guidance":"","uuid":"50bcd7e3-a686-408c-ae97-667c48dc5593","text":"actions","parameterId":"ca-07.05_odp.02","default":" [Assignment: organization defined actions] "}],"subControls":"","tests":[{"testId":"CA-07(05)[01]","uuid":"9b714845-3e14-4503-961f-c69908bebe2e","test":"Determine if [SELECTED PARAMETER VALUE(S): actions ] are employed to validate that policies are established;Using automated tools for monitoring helps to maintain the accuracy, currency, and availability of monitoring information which in turns helps to increase the level of ongoing awareness of the system security and privacy posture in support of organizational risk management decisions.
","uuid":"4fe91a81-993d-4788-82e9-c9cf24258d81","family":"Assessment, Authorization, and Monitoring","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"b1a25ef4-7eaf-458e-b05f-da8557997d70","text":"automated mechanisms","parameterId":"ca-07.06_odp","default":" [Assignment: organization defined automated mechanisms] "}],"subControls":"","tests":[{"testId":"CA-07(06)","uuid":"2172a22a-5fe3-4926-8324-14f75ed9ad9c","test":"Determine if [SELECTED PARAMETER VALUE(S): automated mechanisms ] are used to ensure the accuracy, currency, and availability of monitoring results for the system.Penetration testing is a specialized type of assessment conducted on systems or individual system components to identify vulnerabilities that could be exploited by adversaries. Penetration testing goes beyond automated vulnerability scanning and is conducted by agents and teams with demonstrable skills and experience that include technical expertise in network, operating system, and/or application level security. Penetration testing can be used to validate vulnerabilities or determine the degree of penetration resistance of systems to adversaries within specified constraints. Such constraints include time, resources, and skills. Penetration testing attempts to duplicate the actions of adversaries and provides a more in-depth analysis of security- and privacy-related weaknesses or deficiencies. Penetration testing is especially important when organizations are transitioning from older technologies to newer technologies (e.g., transitioning from IPv4 to IPv6 network protocols).
Organizations can use the results of vulnerability analyses to support penetration testing activities. Penetration testing can be conducted internally or externally on the hardware, software, or firmware components of a system and can exercise both physical and technical controls. A standard method for penetration testing includes a pretest analysis based on full knowledge of the system, pretest identification of potential vulnerabilities based on the pretest analysis, and testing designed to determine the exploitability of vulnerabilities. All parties agree to the rules of engagement before commencing penetration testing scenarios. Organizations correlate the rules of engagement for the penetration tests with the tools, techniques, and procedures that are anticipated to be employed by adversaries. Penetration testing may result in the exposure of information that is protected by laws or regulations, to individuals conducting the testing. Rules of engagement, contracts, or other appropriate mechanisms can be used to communicate expectations for how to protect this information. Risk assessments guide the decisions on the level of independence required for the personnel conducting penetration testing.
","uuid":"32d5ee33-0c06-4096-9cca-ded027f8a105","family":"Assessment, Authorization, and Monitoring","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"adb5eae8-d8f2-4e71-8491-605cdb22d5b5","text":"frequency","parameterId":"ca-08_odp.01","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"1029a18b-fb65-43fb-bf7e-c8aa3d2d82ba","text":"system(s) or system components","parameterId":"ca-08_odp.02","default":" [Assignment: organization defined system(s) or system components] "}],"subControls":"","tests":[{"testId":"CA-08","uuid":"0584de9c-836f-43d4-a80c-d88c75c5a3f1","test":"Determine if penetration testing is conducted [SELECTED PARAMETER VALUE(S): frequency ] on [SELECTED PARAMETER VALUE(S): system(s) or system components ].Independent penetration testing agents or teams are individuals or groups who conduct impartial penetration testing of organizational systems. Impartiality implies that penetration testing agents or teams are free from perceived or actual conflicts of interest with respect to the development, operation, or management of the systems that are the targets of the penetration testing. CA-2(1) provides additional information on independent assessments that can be applied to penetration testing.
","uuid":"2cce22ac-0da1-4329-8013-a92d0dc7fb8a","family":"Assessment, Authorization, and Monitoring","parameters":[],"subControls":"","tests":[{"testId":"CA-08(01)","uuid":"03278265-b0ef-40a2-b9e5-4d32abbfc690","test":"Determine if an independent penetration testing agent or team is employed to perform penetration testing on the system or system components.Red team exercises extend the objectives of penetration testing by examining the security and privacy posture of organizations and the capability to implement effective cyber defenses. Red team exercises simulate attempts by adversaries to compromise mission and business functions and provide a comprehensive assessment of the security and privacy posture of systems and organizations. Such attempts may include technology-based attacks and social engineering-based attacks. Technology-based attacks include interactions with hardware, software, or firmware components and/or mission and business processes. Social engineering-based attacks include interactions via email, telephone, shoulder surfing, or personal conversations. Red team exercises are most effective when conducted by penetration testing agents and teams with knowledge of and experience with current adversarial tactics, techniques, procedures, and tools. While penetration testing may be primarily laboratory-based testing, organizations can use red team exercises to provide more comprehensive assessments that reflect real-world conditions. The results from red team exercises can be used by organizations to improve security and privacy awareness and training and to assess control effectiveness.
","uuid":"6b0285be-7338-4467-ab78-b1454fe6caa6","family":"Assessment, Authorization, and Monitoring","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"d49b6e44-57f5-41ed-a2c5-b3333eb1642b","text":"red team exercises","parameterId":"ca-08.02_odp","default":" [Assignment: organization defined red team exercises] "}],"subControls":"","tests":[{"testId":"CA-08(02)","uuid":"4ec52481-61db-43b4-bf7f-9295f072d5a6","test":"Determine if [SELECTED PARAMETER VALUE(S): red team exercises ] are employed to simulate attempts by adversaries to compromise organizational systems in accordance with applicable rules of engagement.Penetration testing of physical access points can provide information on critical vulnerabilities in the operating environments of organizational systems. Such information can be used to correct weaknesses or deficiencies in physical controls that are necessary to protect organizational systems.
","uuid":"5524e767-87a5-48ea-b241-eaee2ddb61a0","family":"Assessment, Authorization, and Monitoring","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"c4a96f32-a9a3-4433-81a8-bc437506f530","text":"frequency","parameterId":"ca-08.03_odp.01","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"4749a2bf-108a-46e2-a7d1-a7188579de03","text":"[Selection (one or more): announced; unannounced]","parameterId":"ca-08.03_odp.02","default":"[Selection (one or more): announced; unannounced]"}],"subControls":"","tests":[{"testId":"CA-08(03)","uuid":"6f6090fa-064c-443c-85ab-fa7047d2f74c","test":"Determine if the penetration testing process includes [SELECTED PARAMETER VALUE(S): frequency ], [SELECTED PARAMETER VALUE(S): [Selection (one or more): announced; unannounced] ] attempts to bypass or circumvent controls associated with physical access points to facility.Internal system connections are connections between organizational systems and separate constituent system components (i.e., connections between components that are part of the same system) including components used for system development. Intra-system connections include connections with mobile devices, notebook and desktop computers, tablets, printers, copiers, facsimile machines, scanners, sensors, and servers. Instead of authorizing each internal system connection individually, organizations can authorize internal connections for a class of system components with common characteristics and/or configurations, including printers, scanners, and copiers with a specified processing, transmission, and storage capability or smart phones and tablets with a specific baseline configuration. The continued need for an internal system connection is reviewed from the perspective of whether it provides support for organizational missions or business functions.
","uuid":"351791c8-5016-4e95-ba3e-c198e35bc2b5","family":"Assessment, Authorization, and Monitoring","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"092d49ed-22cd-4d99-aeaf-2c743306d829","text":"system components","parameterId":"ca-09_odp.01","default":" [Assignment: organization defined system components] "},{"constraints":"","displayName":"","guidance":"","uuid":"a7d7b8a1-7352-4779-b923-09994bbf9cd2","text":"conditions","parameterId":"ca-09_odp.02","default":" [Assignment: organization defined conditions] "},{"constraints":"","displayName":"","guidance":"","uuid":"23a806f1-b2d7-410e-9242-2c3a5ec3dc74","text":"frequency","parameterId":"ca-09_odp.03","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"CA-09a.","uuid":"5d60d9a6-0977-490e-a416-02ec23f375ab","test":"Determine if internal connections of [SELECTED PARAMETER VALUE(S): system components ] to the system are authorized;Compliance checks include verification of the relevant baseline configuration.
","uuid":"b4636d41-cf57-42ef-9f25-58e9b2e0cea5","family":"Assessment, Authorization, and Monitoring","parameters":[],"subControls":"","tests":[{"testId":"CA-09(01)[01]","uuid":"f0727050-2eab-44c4-ab40-d06bf57c8bbe","test":"Determine if security compliance checks are performed on constituent system components prior to the establishment of the internal connection;Configuration management policy and procedures address the controls in the CM family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of configuration management policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission/business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to configuration management policy and procedures include, but are not limited to, assessment or audit findings, security incidents or breaches, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure.
","uuid":"5b8111c1-28cc-4d26-9c5f-db3fd367aa37","family":"Configuration Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"ec141f88-5e5a-41ba-8e34-a2e043ae3902","text":"organization-defined personnel or roles","parameterId":"cm-1_prm_1","default":" [Assignment: organization-defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"3361944d-1ab9-4d8a-9e2d-39d059335e0f","text":"personnel or roles","parameterId":"cm-01_odp.01","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"3b50ac14-c035-4c99-ac7b-e783807e84da","text":"personnel or roles","parameterId":"cm-01_odp.02","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"0bff6c61-a51f-4f71-98e7-0986d951d350","text":"[Selection (one or more): organization-level; mission/business process-level; system-level]","parameterId":"cm-01_odp.03","default":"[Selection (one or more): organization-level; mission/business process-level; system-level]"},{"constraints":"","displayName":"","guidance":"","uuid":"8cddf3a4-53d2-4c82-b8e5-c61f383c5a9d","text":"official","parameterId":"cm-01_odp.04","default":" [Assignment: organization defined official] "},{"constraints":"","displayName":"","guidance":"","uuid":"6f7dde27-67ae-4f76-bf80-dabe423f6580","text":"frequency","parameterId":"cm-01_odp.05","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"db288e64-769e-4552-bcef-2b2990910a89","text":"events","parameterId":"cm-01_odp.06","default":" [Assignment: organization defined events] "},{"constraints":"","displayName":"","guidance":"","uuid":"75c6a0b6-d823-4b16-bcda-b3ea7a5698a0","text":"frequency","parameterId":"cm-01_odp.07","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"9616b4bd-4070-4876-89f6-1f89e3fe6373","text":"events","parameterId":"cm-01_odp.08","default":" [Assignment: organization defined events] "}],"subControls":"","tests":[{"testId":"CM-01a.[01]","uuid":"c3c35b36-0516-4794-a427-4320814f4e82","test":"Determine if a configuration management policy is developed and documented;Baseline configurations for systems and system components include connectivity, operational, and communications aspects of systems. Baseline configurations are documented, formally reviewed, and agreed-upon specifications for systems or configuration items within those systems. Baseline configurations serve as a basis for future builds, releases, or changes to systems and include security and privacy control implementations, operational procedures, information about system components, network topology, and logical placement of components in the system architecture. Maintaining baseline configurations requires creating new baselines as organizational systems change over time. Baseline configurations of systems reflect the current enterprise architecture.
","uuid":"04bb97ca-34c9-477f-be29-764534a97557","family":"Configuration Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"ee5a90a5-260c-400e-bdbf-06a3083b436f","text":"frequency","parameterId":"cm-02_odp.01","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"f1f91dca-23ef-49cf-bb55-ec804c46fc32","text":"circumstances","parameterId":"cm-02_odp.02","default":" [Assignment: organization defined circumstances] "}],"subControls":"","tests":[{"testId":"CM-02a.[01]","uuid":"0944d0e9-3e14-4fd4-8ff4-971c84e484cc","test":"Determine if a current baseline configuration of the system is developed and documented;Automated mechanisms that help organizations maintain consistent baseline configurations for systems include configuration management tools, hardware, software, firmware inventory tools, and network management tools. Automated tools can be used at the organization level, mission and business process level, or system level on workstations, servers, notebook computers, network components, or mobile devices. Tools can be used to track version numbers on operating systems, applications, types of software installed, and current patch levels. Automation support for accuracy and currency can be satisfied by the implementation of CM-8(2) for organizations that combine system component inventory and baseline configuration activities.
","uuid":"86707605-c4fa-400a-8537-fc849bb188d6","family":"Configuration Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"02d30438-0b85-4162-9712-539c80c9f08f","text":"automated mechanisms","parameterId":"cm-02.02_odp","default":" [Assignment: organization defined automated mechanisms] "}],"subControls":"","tests":[{"testId":"CM-02(02)[01]","uuid":"5bab36ac-bf8e-4d08-b511-6e64b3dd51fa","test":"Determine if the currency of the baseline configuration of the system is maintained using [SELECTED PARAMETER VALUE(S): automated mechanisms ];Retaining previous versions of baseline configurations to support rollback include hardware, software, firmware, configuration files, configuration records, and associated documentation.
","uuid":"ae052a3e-e3f8-4ab5-927f-6251b771f1a4","family":"Configuration Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"96727d20-16ee-4208-9d99-991cd2474917","text":"number","parameterId":"cm-02.03_odp","default":" [Assignment: organization defined number] "}],"subControls":"","tests":[{"testId":"CM-02(03)","uuid":"de6624ba-b38c-4625-8e9a-e9d5f5b99c0d","test":"Determine if [SELECTED PARAMETER VALUE(S): number ] of previous baseline configuration version(s) of the system is/are retained to support rollback.Establishing separate baseline configurations for development, testing, and operational environments protects systems from unplanned or unexpected events related to development and testing activities. Separate baseline configurations allow organizations to apply the configuration management that is most appropriate for each type of configuration. For example, the management of operational configurations typically emphasizes the need for stability, while the management of development or test configurations requires greater flexibility. Configurations in the test environment mirror configurations in the operational environment to the extent practicable so that the results of the testing are representative of the proposed changes to the operational systems. Separate baseline configurations do not necessarily require separate physical environments.
","uuid":"2bda8fac-0294-4d19-9ed3-b9484b714119","family":"Configuration Management","parameters":[],"subControls":"","tests":[{"testId":"CM-02(06)[01]","uuid":"1f138c38-d9b6-4391-a5b9-6b57a6ca19de","test":"Determine if a baseline configuration for system development environments that is managed separately from the operational baseline configuration is maintained;When it is known that systems or system components will be in high-risk areas external to the organization, additional controls may be implemented to counter the increased threat in such areas. For example, organizations can take actions for notebook computers used by individuals departing on and returning from travel. Actions include determining the locations that are of concern, defining the required configurations for the components, ensuring that components are configured as intended before travel is initiated, and applying controls to the components after travel is completed. Specially configured notebook computers include computers with sanitized hard drives, limited applications, and more stringent configuration settings. Controls applied to mobile devices upon return from travel include examining the mobile device for signs of physical tampering and purging and reimaging disk drives. Protecting information that resides on mobile devices is addressed in the MP (Media Protection) family.
","uuid":"2746aadf-72a5-490f-8e37-1a5d5b6146d9","family":"Configuration Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"1934e914-12fc-4332-8b36-4f70b37f5603","text":"systems or system components","parameterId":"cm-02.07_odp.01","default":" [Assignment: organization defined systems or system components] "},{"constraints":"","displayName":"","guidance":"","uuid":"0215d317-2da6-43ce-8862-df5ab2436199","text":"configurations","parameterId":"cm-02.07_odp.02","default":" [Assignment: organization defined configurations] "},{"constraints":"","displayName":"","guidance":"","uuid":"03e304d4-b90d-4c44-9daa-9b1266930ae9","text":"controls","parameterId":"cm-02.07_odp.03","default":" [Assignment: organization defined controls] "}],"subControls":"","tests":[{"testId":"CM-02(07)(a)","uuid":"8e188897-7dba-466a-8e99-84fdae96bebd","test":"Determine if [SELECTED PARAMETER VALUE(S): systems or system components ] with [SELECTED PARAMETER VALUE(S): configurations ] are issued to individuals traveling to locations that the organization deems to be of significant risk;Configuration change control for organizational systems involves the systematic proposal, justification, implementation, testing, review, and disposition of system changes, including system upgrades and modifications. Configuration change control includes changes to baseline configurations, configuration items of systems, operational procedures, configuration settings for system components, remediate vulnerabilities, and unscheduled or unauthorized changes. Processes for managing configuration changes to systems include Configuration Control Boards or Change Advisory Boards that review and approve proposed changes. For changes that impact privacy risk, the senior agency official for privacy updates privacy impact assessments and system of records notices. For new systems or major upgrades, organizations consider including representatives from the development organizations on the Configuration Control Boards or Change Advisory Boards. Auditing of changes includes activities before and after changes are made to systems and the auditing activities required to implement such changes. See also SA-10.
","uuid":"9bf92b78-330c-4fa3-b8c1-d0c118afc03a","family":"Configuration Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"426520b8-855c-4463-9ee1-059dfbcbf616","text":"time period","parameterId":"cm-03_odp.01","default":" [Assignment: organization defined time period] "},{"constraints":"","displayName":"","guidance":"","uuid":"3c147c59-99c7-4be6-9daf-d73b6142eb23","text":"configuration change control element","parameterId":"cm-03_odp.02","default":" [Assignment: organization defined configuration change control element] "},{"constraints":"","displayName":"","guidance":"","uuid":"dde2e3f5-ec93-4950-a7b1-a29c3a8eb184","text":"[Selection (one or more): [(NESTED PARAMETER) Assignment for cm-03_odp.04: frequency]; when [(NESTED PARAMETER) Assignment for cm-03_odp.05: configuration change conditions]]","parameterId":"cm-03_odp.03","default":"[Selection (one or more): [(NESTED PARAMETER) Assignment for cm-03_odp.04: frequency]; when [(NESTED PARAMETER) Assignment for cm-03_odp.05: configuration change conditions]]"},{"constraints":"","displayName":"","guidance":"","uuid":"0491a9e3-79c4-497e-8940-233b98719d64","text":"frequency","parameterId":"cm-03_odp.04","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"9a621328-67d0-413f-8166-7bca88482a3c","text":"configuration change conditions","parameterId":"cm-03_odp.05","default":" [Assignment: organization defined configuration change conditions] "}],"subControls":"","tests":[{"testId":"CM-03a.","uuid":"1e83b264-2d62-476c-a208-41739f02f734","test":"Determine if the types of changes to the system that are configuration-controlled are determined and documented;None.
","uuid":"ec33e2b6-3753-4f45-ba6c-c87fa7862900","family":"Configuration Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"efad7a52-8b24-441f-bf30-582291ab4bf0","text":"automated mechanisms","parameterId":"cm-03.01_odp.01","default":" [Assignment: organization defined automated mechanisms] "},{"constraints":"","displayName":"","guidance":"","uuid":"f4d9d19a-b27a-47e1-a353-2e49870a9d1d","text":"approval authorities","parameterId":"cm-03.01_odp.02","default":" [Assignment: organization defined approval authorities] "},{"constraints":"","displayName":"","guidance":"","uuid":"53b1d8e0-d950-48c6-ac85-54f14f88235f","text":"time period","parameterId":"cm-03.01_odp.03","default":" [Assignment: organization defined time period] "},{"constraints":"","displayName":"","guidance":"","uuid":"cc3c37db-2966-4770-9621-8d544cb739b8","text":"personnel","parameterId":"cm-03.01_odp.04","default":" [Assignment: organization defined personnel] "}],"subControls":"","tests":[{"testId":"CM-03(01)(a)","uuid":"9aadc52f-f966-49e0-8ef0-9a30061af6c8","test":"Determine if [SELECTED PARAMETER VALUE(S): automated mechanisms ] are used to document proposed changes to the system;Changes to systems include modifications to hardware, software, or firmware components and configuration settings defined in CM-6 . Organizations ensure that testing does not interfere with system operations that support organizational mission and business functions. Individuals or groups conducting tests understand security and privacy policies and procedures, system security and privacy policies and procedures, and the health, safety, and environmental risks associated with specific facilities or processes. Operational systems may need to be taken offline, or replicated to the extent feasible, before testing can be conducted. If systems must be taken offline for testing, the tests are scheduled to occur during planned system outages whenever possible. If the testing cannot be conducted on operational systems, organizations employ compensating controls.
","uuid":"1ec0765f-7062-4409-b047-e3bbf4e36fb0","family":"Configuration Management","parameters":[],"subControls":"","tests":[{"testId":"CM-03(02)[01]","uuid":"caee144e-7023-4b64-9322-c635e84d8748","test":"Determine if changes to the system are tested before finalizing the implementation of the changes;Automated tools can improve the accuracy, consistency, and availability of configuration baseline information. Automation can also provide data aggregation and data correlation capabilities, alerting mechanisms, and dashboards to support risk-based decision-making within the organization.
","uuid":"a5a0b5b4-ad9c-41b6-8007-0abb09959b09","family":"Configuration Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"6efd1eb6-654a-4578-83a3-9ea45eb1cac4","text":"automated mechanisms","parameterId":"cm-03.03_odp","default":" [Assignment: organization defined automated mechanisms] "}],"subControls":"","tests":[{"testId":"CM-03(03)[01]","uuid":"8ca27da0-ec52-4f93-9070-3bf3f164150e","test":"Determine if changes to the current system baseline are implemented using [SELECTED PARAMETER VALUE(S): automated mechanisms ];Information security and privacy representatives include system security officers, senior agency information security officers, senior agency officials for privacy, or system privacy officers. Representation by personnel with information security and privacy expertise is important because changes to system configurations can have unintended side effects, some of which may be security- or privacy-relevant. Detecting such changes early in the process can help avoid unintended, negative consequences that could ultimately affect the security and privacy posture of systems. The configuration change control element referred to in the second organization-defined parameter reflects the change control elements defined by organizations in CM-3g.
","uuid":"9610e8ba-af7c-48bd-90ce-fc2a5e716afd","family":"Configuration Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"a6fc1153-d06c-4c50-85b6-98209f32c8ee","text":"organization-defined security and privacy representatives","parameterId":"cm-3.4_prm_1","default":" [Assignment: organization-defined security and privacy representatives] "},{"constraints":"","displayName":"","guidance":"","uuid":"521145c5-198c-42b2-ac7d-83948576d5ce","text":"security representatives","parameterId":"cm-03.04_odp.01","default":" [Assignment: organization defined security representatives] "},{"constraints":"","displayName":"","guidance":"","uuid":"ddb1b1fd-d109-4970-80f1-6d9fda205f8e","text":"privacy representatives","parameterId":"cm-03.04_odp.02","default":" [Assignment: organization defined privacy representatives] "},{"constraints":"","displayName":"","guidance":"","uuid":"5d68988a-1907-4637-afc1-67c9e4b2031c","text":"configuration change control element","parameterId":"cm-03.04_odp.03","default":" [Assignment: organization defined configuration change control element] "}],"subControls":"","tests":[{"testId":"CM-03(04)[01]","uuid":"36d41345-c0a0-47d9-aea5-bb565b43914f","test":"Determine if [SELECTED PARAMETER VALUE(S): security representatives ] are required to be members of the [SELECTED PARAMETER VALUE(S): configuration change control element ];Automated security responses include halting selected system functions, halting system processing, and issuing alerts or notifications to organizational personnel when there is an unauthorized modification of a configuration item.
","uuid":"8a9aec79-87a6-4ff5-b360-c120d246d143","family":"Configuration Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"ff20cd0e-b37c-4e68-bc42-0156ed3df193","text":"security responses","parameterId":"cm-03.05_odp","default":" [Assignment: organization defined security responses] "}],"subControls":"","tests":[{"testId":"CM-03(05)","uuid":"dffe53ee-597c-4df9-8028-fe44a06cc40b","test":"Determine if [SELECTED PARAMETER VALUE(S): security responses ] are automatically implemented if baseline configurations are changed in an unauthorized manner.The controls referenced in the control enhancement refer to security and privacy controls from the control catalog. Regardless of the cryptographic mechanisms employed, processes and procedures are in place to manage those mechanisms. For example, if system components use certificates for identification and authentication, a process is implemented to address the expiration of those certificates.
","uuid":"51ff79c8-94b5-47b6-b40e-195cbd0fc790","family":"Configuration Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"ef2d36dc-6865-403d-9a14-b825f3026c76","text":"controls","parameterId":"cm-03.06_odp","default":" [Assignment: organization defined controls] "}],"subControls":"","tests":[{"testId":"CM-03(06)","uuid":"6535aa3d-405c-4e3b-a7e4-e3b5ccc6786c","test":"Determine if cryptographic mechanisms used to provide [SELECTED PARAMETER VALUE(S): controls ] are under configuration management.Indications that warrant a review of changes to the system and the specific circumstances justifying such reviews may be obtained from activities carried out by organizations during the configuration change process or continuous monitoring process.
","uuid":"362b167e-a4c4-4158-8026-934705b340a1","family":"Configuration Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"2ef63a5b-dff7-491e-9c88-235a0738a3a2","text":"frequency","parameterId":"cm-03.07_odp.01","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"7baf32fe-001d-4625-aad4-8bed47225a02","text":"circumstances","parameterId":"cm-03.07_odp.02","default":" [Assignment: organization defined circumstances] "}],"subControls":"","tests":[{"testId":"CM-03(07)","uuid":"7e2e809d-03cc-46e3-98f1-9b09b7b711ca","test":"Determine if changes to the system are reviewed [SELECTED PARAMETER VALUE(S): frequency ] or when [SELECTED PARAMETER VALUE(S): circumstances ] to determine whether unauthorized changes have occurred.System configuration changes can adversely affect critical system security and privacy functionality. Change restrictions can be enforced through automated mechanisms.
","uuid":"4e4b6d29-2285-4f25-abc9-c6735c50f419","family":"Configuration Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"e7e2c1fb-83e3-432e-bf66-c610fe08ef46","text":"circumstances","parameterId":"cm-03.08_odp","default":" [Assignment: organization defined circumstances] "}],"subControls":"","tests":[{"testId":"CM-03(08)","uuid":"21ab50cb-fb5c-41ad-bb03-6c3dfa5126a3","test":"Determine if changes to the configuration of the system are prevented or restricted under [SELECTED PARAMETER VALUE(S): circumstances ].Organizational personnel with security or privacy responsibilities conduct impact analyses. Individuals conducting impact analyses possess the necessary skills and technical expertise to analyze the changes to systems as well as the security or privacy ramifications. Impact analyses include reviewing security and privacy plans, policies, and procedures to understand control requirements; reviewing system design documentation and operational procedures to understand control implementation and how specific system changes might affect the controls; reviewing the impact of changes on organizational supply chain partners with stakeholders; and determining how potential changes to a system create new risks to the privacy of individuals and the ability of implemented controls to mitigate those risks. Impact analyses also include risk assessments to understand the impact of the changes and determine if additional controls are required.
","uuid":"5704362c-1772-4de2-a2ec-2838dd4d7dcf","family":"Configuration Management","parameters":[],"subControls":"","tests":[{"testId":"CM-04[01]","uuid":"5cf6555d-30ba-425b-8607-1f94aea17cc1","test":"Determine if changes to the system are analyzed to determine potential security impacts prior to change implementation;A separate test environment requires an environment that is physically or logically separate and distinct from the operational environment. The separation is sufficient to ensure that activities in the test environment do not impact activities in the operational environment and that information in the operational environment is not inadvertently transmitted to the test environment. Separate environments can be achieved by physical or logical means. If physically separate test environments are not implemented, organizations determine the strength of mechanism required when implementing logical separation.
","uuid":"0cd3c468-866a-49f9-9f64-d67e3825562d","family":"Configuration Management","parameters":[],"subControls":"","tests":[{"testId":"CM-04(01)[01]","uuid":"fb187284-ca56-45df-a72c-d5031d6f0de8","test":"Determine if changes to the system are analyzed in a separate test environment before implementation in an operational environment;Implementation in this context refers to installing changed code in the operational system that may have an impact on security or privacy controls.
","uuid":"dad847f4-d619-4d1c-ba9e-3c7b6b63934d","family":"Configuration Management","parameters":[],"subControls":"","tests":[{"testId":"CM-04(02)[01]","uuid":"c3688aaa-6ead-448c-87e2-8ec5f9e5c60a","test":"Determine if the impacted controls are implemented correctly with regard to meeting the security requirements for the system after system changes;Changes to the hardware, software, or firmware components of systems or the operational procedures related to the system can potentially have significant effects on the security of the systems or individuals’ privacy. Therefore, organizations permit only qualified and authorized individuals to access systems for purposes of initiating changes. Access restrictions include physical and logical access controls (see AC-3 and PE-3 ), software libraries, workflow automation, media libraries, abstract layers (i.e., changes implemented into external interfaces rather than directly into systems), and change windows (i.e., changes occur only during specified times).
","uuid":"16999e98-d7a5-4a76-ad0f-93a47618882f","family":"Configuration Management","parameters":[],"subControls":"","tests":[{"testId":"CM-05[01]","uuid":"1a5389a4-f204-4d38-b02d-f84e119b0f4f","test":"Determine if physical access restrictions associated with changes to the system are defined and documented;Organizations log system accesses associated with applying configuration changes to ensure that configuration change control is implemented and to support after-the-fact actions should organizations discover any unauthorized changes.
","uuid":"b1f8b89d-b0ed-41e3-b135-25e188bf188c","family":"Configuration Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"0ca517f2-da12-448b-8cdd-13f07edcd0c0","text":"automated mechanisms","parameterId":"cm-05.01_odp","default":" [Assignment: organization defined automated mechanisms] "}],"subControls":"","tests":[{"testId":"CM-05(01)(a)","uuid":"6c1868d1-7b6b-4efc-8a22-bb1b9e1ef6fb","test":"Determine if access restrictions for change are enforced using [SELECTED PARAMETER VALUE(S): automated mechanisms ];Organizations employ dual authorization to help ensure that any changes to selected system components and information cannot occur unless two qualified individuals approve and implement such changes. The two individuals possess the skills and expertise to determine if the proposed changes are correct implementations of approved changes. The individuals are also accountable for the changes. Dual authorization may also be known as two-person control. To reduce the risk of collusion, organizations consider rotating dual authorization duties to other individuals. System-level information includes operational procedures.
","uuid":"29cef688-5ae3-47be-abc0-b78cce615033","family":"Configuration Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"32d0d473-43d5-4bd2-a5b3-c075795f4a34","text":"organization-defined system components and system-level information","parameterId":"cm-5.4_prm_1","default":" [Assignment: organization-defined system components and system-level information] "},{"constraints":"","displayName":"","guidance":"","uuid":"cf908926-7544-4cbc-941e-236c4e4438da","text":"system components","parameterId":"cm-05.04_odp.01","default":" [Assignment: organization defined system components] "},{"constraints":"","displayName":"","guidance":"","uuid":"2632c2c3-4c09-4caa-b981-61f545c9439f","text":"system-level information","parameterId":"cm-05.04_odp.02","default":" [Assignment: organization defined system-level information] "}],"subControls":"","tests":[{"testId":"CM-05(04)[01]","uuid":"9213c332-3d4f-40eb-a3cd-9dd5fce75e73","test":"Determine if dual authorization for implementing changes to [SELECTED PARAMETER VALUE(S): system components ] is enforced;In many organizations, systems support multiple mission and business functions. Limiting privileges to change system components with respect to operational systems is necessary because changes to a system component may have far-reaching effects on mission and business processes supported by the system. The relationships between systems and mission/business processes are, in some cases, unknown to developers. System-related information includes operational procedures.
","uuid":"b4427ef0-bdb3-4f5d-b8bf-07c7574dd661","family":"Configuration Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"675efd71-52ec-4402-b541-e17b1c16a787","text":"organization-defined frequency","parameterId":"cm-5.5_prm_1","default":" [Assignment: organization-defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"571eb88c-2988-490d-9515-151fa956d347","text":"frequency","parameterId":"cm-05.05_odp.01","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"92a8f790-2bc6-4e36-99f8-8551e6b4c89a","text":"frequency","parameterId":"cm-05.05_odp.02","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"CM-05(05)(a)[01]","uuid":"c4277c5f-9525-42c9-913b-0619781a123e","test":"Determine if privileges to change system components within a production or operational environment are limited;Software libraries include privileged programs.
","uuid":"227ec7f9-3313-4a97-94d6-ab09caa0d5a8","family":"Configuration Management","parameters":[],"subControls":"","tests":[{"testId":"CM-05(06)","uuid":"27948ec8-81fa-43bd-996f-f715ca7ea9bf","test":"Determine if privileges to change software resident within software libraries are limited.Configuration settings are the parameters that can be changed in the hardware, software, or firmware components of the system that affect the security and privacy posture or functionality of the system. Information technology products for which configuration settings can be defined include mainframe computers, servers, workstations, operating systems, mobile devices, input/output devices, protocols, and applications. Parameters that impact the security posture of systems include registry settings; account, file, or directory permission settings; and settings for functions, protocols, ports, services, and remote connections. Privacy parameters are parameters impacting the privacy posture of systems, including the parameters required to satisfy other privacy controls. Privacy parameters include settings for access controls, data processing preferences, and processing and retention permissions. Organizations establish organization-wide configuration settings and subsequently derive specific configuration settings for systems. The established settings become part of the configuration baseline for the system.
Common secure configurations (also known as security configuration checklists, lockdown and hardening guides, and security reference guides) provide recognized, standardized, and established benchmarks that stipulate secure configuration settings for information technology products and platforms as well as instructions for configuring those products or platforms to meet operational requirements. Common secure configurations can be developed by a variety of organizations, including information technology product developers, manufacturers, vendors, federal agencies, consortia, academia, industry, and other organizations in the public and private sectors.
Implementation of a common secure configuration may be mandated at the organization level, mission and business process level, system level, or at a higher level, including by a regulatory agency. Common secure configurations include the United States Government Configuration Baseline USGCB and security technical implementation guides (STIGs), which affect the implementation of CM-6 and other controls such as AC-19 and CM-7 . The Security Content Automation Protocol (SCAP) and the defined standards within the protocol provide an effective method to uniquely identify, track, and control configuration settings.
","uuid":"76418ae2-3cf1-46d9-95bc-0be43ac14d90","family":"Configuration Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"b6cb6a3e-f319-4642-af7d-94b871149fc4","text":"common secure configurations","parameterId":"cm-06_odp.01","default":" [Assignment: organization defined common secure configurations] "},{"constraints":"","displayName":"","guidance":"","uuid":"5f1c8820-3533-401d-98d7-f3fccba4006f","text":"system components","parameterId":"cm-06_odp.02","default":" [Assignment: organization defined system components] "},{"constraints":"","displayName":"","guidance":"","uuid":"79f629d3-5075-4adc-a081-cffc3e85d8e2","text":"operational requirements","parameterId":"cm-06_odp.03","default":" [Assignment: organization defined operational requirements] "}],"subControls":"","tests":[{"testId":"CM-06a.","uuid":"d1b37155-f1a5-4e28-a736-addc4b4e6271","test":"Determine if configuration settings that reflect the most restrictive mode consistent with operational requirements are established and documented for components employed within the system using [SELECTED PARAMETER VALUE(S): common secure configurations ];Automated tools (e.g., hardening tools, baseline configuration tools) can improve the accuracy, consistency, and availability of configuration settings information. Automation can also provide data aggregation and data correlation capabilities, alerting mechanisms, and dashboards to support risk-based decision-making within the organization.
","uuid":"42ccdf63-20ef-4b2b-aec1-e0ed93230e37","family":"Configuration Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"e16f2599-8149-4b38-8afb-82111e902876","text":"organization-defined automated mechanisms","parameterId":"cm-6.1_prm_2","default":" [Assignment: organization-defined automated mechanisms] "},{"constraints":"","displayName":"","guidance":"","uuid":"be3c7d41-81dc-4a39-a758-3017b281dc9e","text":"system components","parameterId":"cm-06.01_odp.01","default":" [Assignment: organization defined system components] "},{"constraints":"","displayName":"","guidance":"","uuid":"b964ef1d-d43a-45aa-b33b-6a22d06775c5","text":"automated mechanisms","parameterId":"cm-06.01_odp.02","default":" [Assignment: organization defined automated mechanisms] "},{"constraints":"","displayName":"","guidance":"","uuid":"650bd801-c7e4-4225-97d2-024abec7343a","text":"automated mechanisms","parameterId":"cm-06.01_odp.03","default":" [Assignment: organization defined automated mechanisms] "},{"constraints":"","displayName":"","guidance":"","uuid":"538ec90a-0f43-4fd7-b1cf-0bc223d1529b","text":"automated mechanisms","parameterId":"cm-06.01_odp.04","default":" [Assignment: organization defined automated mechanisms] "}],"subControls":"","tests":[{"testId":"CM-06(01)[01]","uuid":"406d2639-9b5f-43c1-b4c5-19b38889a9ef","test":"Determine if configuration settings for [SELECTED PARAMETER VALUE(S): system components ] are managed using [SELECTED PARAMETER VALUE(S): automated mechanisms ];Responses to unauthorized changes to configuration settings include alerting designated organizational personnel, restoring established configuration settings, or—in extreme cases—halting affected system processing.
","uuid":"f45816a6-e06f-4dd0-b176-1e9b3658557c","family":"Configuration Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"468e722b-db3b-44d8-a1ac-c90ee90d2b4c","text":"actions","parameterId":"cm-06.02_odp.01","default":" [Assignment: organization defined actions] "},{"constraints":"","displayName":"","guidance":"","uuid":"4f33f05c-7d04-4d0a-91e6-4a3a10bc930e","text":"configuration settings","parameterId":"cm-06.02_odp.02","default":" [Assignment: organization defined configuration settings] "}],"subControls":"","tests":[{"testId":"CM-06(02)","uuid":"5bf0cbc7-bc6a-497a-9a93-5f291ff08701","test":"Determine if [SELECTED PARAMETER VALUE(S): actions ] are taken in response to unauthorized changes to [SELECTED PARAMETER VALUE(S): configuration settings ].Systems provide a wide variety of functions and services. Some of the functions and services routinely provided by default may not be necessary to support essential organizational missions, functions, or operations. Additionally, it is sometimes convenient to provide multiple services from a single system component, but doing so increases risk over limiting the services provided by that single component. Where feasible, organizations limit component functionality to a single function per component. Organizations consider removing unused or unnecessary software and disabling unused or unnecessary physical and logical ports and protocols to prevent unauthorized connection of components, transfer of information, and tunneling. Organizations employ network scanning tools, intrusion detection and prevention systems, and end-point protection technologies, such as firewalls and host-based intrusion detection systems, to identify and prevent the use of prohibited functions, protocols, ports, and services. Least functionality can also be achieved as part of the fundamental design and development of the system (see SA-8, SC-2 , and SC-3).
","uuid":"4f054503-f9ee-4d2b-a520-dce5bbc534ab","family":"Configuration Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"d3744a6e-d020-4e9f-b0c4-e56da5df4c1c","text":"organization-defined prohibited or restricted functions, system ports, protocols, software, and/or services","parameterId":"cm-7_prm_2","default":" [Assignment: organization-defined prohibited or restricted functions, system ports, protocols, software, and/or services] "},{"constraints":"","displayName":"","guidance":"","uuid":"2eea9562-09b1-4062-a921-373d9ff06b00","text":"mission-essential capabilities","parameterId":"cm-07_odp.01","default":" [Assignment: organization defined mission-essential capabilities] "},{"constraints":"","displayName":"","guidance":"","uuid":"72ece70c-25f5-45a0-8f37-bd5b7e0316a1","text":"functions","parameterId":"cm-07_odp.02","default":" [Assignment: organization defined functions] "},{"constraints":"","displayName":"","guidance":"","uuid":"10fa5c8d-d72f-4da0-a6aa-99a6b9190a05","text":"ports","parameterId":"cm-07_odp.03","default":" [Assignment: organization defined ports] "},{"constraints":"","displayName":"","guidance":"","uuid":"2fbeb453-96ff-4c13-920f-9abcc1eac493","text":"protocols","parameterId":"cm-07_odp.04","default":" [Assignment: organization defined protocols] "},{"constraints":"","displayName":"","guidance":"","uuid":"d49b6e6f-c37e-4977-825d-d9dd303218b9","text":"software","parameterId":"cm-07_odp.05","default":" [Assignment: organization defined software] "},{"constraints":"","displayName":"","guidance":"","uuid":"8dd36d06-2f16-4902-a3b1-67b5974538be","text":"services","parameterId":"cm-07_odp.06","default":" [Assignment: organization defined services] "}],"subControls":"","tests":[{"testId":"CM-07a.","uuid":"58cd8d47-3250-4c3d-8840-5569311e71fa","test":"Determine if the system is configured to provide only [SELECTED PARAMETER VALUE(S): mission-essential capabilities ];Organizations review functions, ports, protocols, and services provided by systems or system components to determine the functions and services that are candidates for elimination. Such reviews are especially important during transition periods from older technologies to newer technologies (e.g., transition from IPv4 to IPv6). These technology transitions may require implementing the older and newer technologies simultaneously during the transition period and returning to minimum essential functions, ports, protocols, and services at the earliest opportunity. Organizations can either decide the relative security of the function, port, protocol, and/or service or base the security decision on the assessment of other entities. Unsecure protocols include Bluetooth, FTP, and peer-to-peer networking.
","uuid":"9de098ab-1b4e-4693-a766-4e8c48eaa75b","family":"Configuration Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"b0db105e-3866-479d-96dd-9c6e0ff3a7a0","text":"organization-defined functions, ports, protocols, software, and services within the system deemed to be unnecessary and/or nonsecure","parameterId":"cm-7.1_prm_2","default":" [Assignment: organization-defined functions, ports, protocols, software, and services within the system deemed to be unnecessary and/or nonsecure] "},{"constraints":"","displayName":"","guidance":"","uuid":"1f60b3ee-1be0-4578-b4ed-edca771ee57e","text":"frequency","parameterId":"cm-07.01_odp.01","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"6433ce9a-54c5-4602-b0b3-e1a25a4ce745","text":"functions","parameterId":"cm-07.01_odp.02","default":" [Assignment: organization defined functions] "},{"constraints":"","displayName":"","guidance":"","uuid":"d7c6853d-5d16-4f6e-b7dc-84ea857f23ee","text":"ports","parameterId":"cm-07.01_odp.03","default":" [Assignment: organization defined ports] "},{"constraints":"","displayName":"","guidance":"","uuid":"49fcee3b-5375-44c1-913f-6bf3a6bc3056","text":"protocols","parameterId":"cm-07.01_odp.04","default":" [Assignment: organization defined protocols] "},{"constraints":"","displayName":"","guidance":"","uuid":"a8c20231-796f-4630-af42-b3a4fed38030","text":"software","parameterId":"cm-07.01_odp.05","default":" [Assignment: organization defined software] "},{"constraints":"","displayName":"","guidance":"","uuid":"e72e4f13-5d0a-4372-922b-283cff1d34ca","text":"services","parameterId":"cm-07.01_odp.06","default":" [Assignment: organization defined services] "}],"subControls":"","tests":[{"testId":"CM-07(01)(a)","uuid":"59fc81b6-dbbc-45b9-af4f-65608f54835d","test":"Determine if the system is reviewed [SELECTED PARAMETER VALUE(S): frequency ] to identify unnecessary and/or non-secure functions, ports, protocols, software, and services:Prevention of program execution addresses organizational policies, rules of behavior, and/or access agreements that restrict software usage and the terms and conditions imposed by the developer or manufacturer, including software licensing and copyrights. Restrictions include prohibiting auto-execute features, restricting roles allowed to approve program execution, permitting or prohibiting specific software programs, or restricting the number of program instances executed at the same time.
","uuid":"369fafc7-0e29-494e-a06a-b0e258abc283","family":"Configuration Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"a5aa5686-df25-4c17-82d9-e3572fb1c530","text":"[Selection (one or more): [(NESTED PARAMETER) Assignment for cm-07.02_odp.02: policies, rules of behavior, and/or access agreements regarding software program usage and restrictions]; rules authorizing the terms and conditions of software program usage]","parameterId":"cm-07.02_odp.01","default":"[Selection (one or more): [(NESTED PARAMETER) Assignment for cm-07.02_odp.02: policies, rules of behavior, and/or access agreements regarding software program usage and restrictions]; rules authorizing the terms and conditions of software program usage]"},{"constraints":"","displayName":"","guidance":"","uuid":"a33ba5aa-1361-4888-99e2-04fac95069c6","text":"policies, rules of behavior, and/or access agreements regarding software program usage and restrictions","parameterId":"cm-07.02_odp.02","default":" [Assignment: organization defined policies, rules of behavior, and/or access agreements regarding software program usage and restrictions] "}],"subControls":"","tests":[{"testId":"CM-07(02)","uuid":"5134ccd7-a84b-40c7-b925-2b85cc7fa31a","test":"Determine if program execution is prevented in accordance with [SELECTED PARAMETER VALUE(S): [Selection (one or more): [(NESTED PARAMETER) Assignment for cm-07.02_odp.02: policies, rules of behavior, and/or access agreements regarding software program usage and restrictions]; rules authorizing the terms and conditions of software program usage] ].Organizations use the registration process to manage, track, and provide oversight for systems and implemented functions, ports, protocols, and services.
","uuid":"0774de65-dbb2-42b9-adfb-bc6cb316bfd5","family":"Configuration Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"9619c43c-f4c5-4ba6-bdc5-9d99396a3bf4","text":"registration requirements","parameterId":"cm-07.03_odp","default":" [Assignment: organization defined registration requirements] "}],"subControls":"","tests":[{"testId":"CM-07(03)","uuid":"60e9ab5f-f79b-435d-a9b6-18db5a958f44","test":"Determine if [SELECTED PARAMETER VALUE(S): registration requirements ] are complied with.Unauthorized software programs can be limited to specific versions or from a specific source. The concept of prohibiting the execution of unauthorized software may also be applied to user actions, system ports and protocols, IP addresses/ranges, websites, and MAC addresses.
","uuid":"7369dc2d-ce01-4d8d-aec1-35f8890712e6","family":"Configuration Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"f1f715da-8e3d-42e8-a7c0-c619ff56e5b8","text":"software programs","parameterId":"cm-07.04_odp.01","default":" [Assignment: organization defined software programs] "},{"constraints":"","displayName":"","guidance":"","uuid":"f43ea94b-0ae0-4fd1-80cd-4afaecefe94f","text":"frequency","parameterId":"cm-07.04_odp.02","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"CM-07(04)(a)","uuid":"4438ce41-b101-4978-b2b0-4d7bb139dfa9","test":"Determine if [SELECTED PARAMETER VALUE(S): software programs ] are identified;Authorized software programs can be limited to specific versions or from a specific source. To facilitate a comprehensive authorized software process and increase the strength of protection for attacks that bypass application level authorized software, software programs may be decomposed into and monitored at different levels of detail. These levels include applications, application programming interfaces, application modules, scripts, system processes, system services, kernel functions, registries, drivers, and dynamic link libraries. The concept of permitting the execution of authorized software may also be applied to user actions, system ports and protocols, IP addresses/ranges, websites, and MAC addresses. Organizations consider verifying the integrity of authorized software programs using digital signatures, cryptographic checksums, or hash functions. Verification of authorized software can occur either prior to execution or at system startup. The identification of authorized URLs for websites is addressed in CA-3(5) and SC-7.
","uuid":"d15a5dec-79c1-4583-9dfe-33e258cff86d","family":"Configuration Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"f218ccf4-e64e-455c-a46e-239c2bf27cc5","text":"software programs","parameterId":"cm-07.05_odp.01","default":" [Assignment: organization defined software programs] "},{"constraints":"","displayName":"","guidance":"","uuid":"77431448-5a82-426d-aba8-d6da832621a9","text":"frequency","parameterId":"cm-07.05_odp.02","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"CM-07(05)(a)","uuid":"1f65e7ad-95df-4541-9ff7-74f0f8297472","test":"Determine if [SELECTED PARAMETER VALUE(S): software programs ] are identified;Organizations identify software that may be of concern regarding its origin or potential for containing malicious code. For this type of software, user installations occur in confined environments of operation to limit or contain damage from malicious code that may be executed.
","uuid":"34e3fb8e-cad8-49fb-af97-2a0d49834227","family":"Configuration Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"b6714d9a-28ef-42dc-88c6-0247905ef44b","text":"user-installed software","parameterId":"cm-07.06_odp","default":" [Assignment: organization defined user-installed software] "}],"subControls":"","tests":[{"testId":"CM-07(06)","uuid":"ea36534c-6c85-43be-a7d7-c57d58b71919","test":"Determine if [SELECTED PARAMETER VALUE(S): user-installed software ] is required to be executed in a confined physical or virtual machine environment with limited privileges.Code execution in protected environments applies to all sources of binary or machine-executable code, including commercial software and firmware and open-source software.
","uuid":"7f35cad4-757f-4b31-ae18-b65b1c6b832b","family":"Configuration Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"c39e6980-2613-411e-8eb2-f297cace77f5","text":"personnel or roles","parameterId":"cm-07.07_odp","default":" [Assignment: organization defined personnel or roles] "}],"subControls":"","tests":[{"testId":"CM-07(07)(a)","uuid":"367b9823-de97-4efc-8ca5-25b9656f654f","test":"Determine if the execution of binary or machine-executable code obtained from sources with limited or no warranty is only allowed with the explicit approval of [SELECTED PARAMETER VALUE(S): personnel or roles ];Binary or machine executable code applies to all sources of binary or machine-executable code, including commercial software and firmware and open-source software. Organizations assess software products without accompanying source code or from sources with limited or no warranty for potential security impacts. The assessments address the fact that software products without the provision of source code may be difficult to review, repair, or extend. In addition, there may be no owners to make such repairs on behalf of organizations. If open-source software is used, the assessments address the fact that there is no warranty, the open-source software could contain back doors or malware, and there may be no support available.
","uuid":"1fe7f480-4185-480b-a2ae-730f98edd53d","family":"Configuration Management","parameters":[],"subControls":"","tests":[{"testId":"CM-07(08)(a)","uuid":"9d573348-21aa-419a-9700-40e9a722eff1","test":"Determine if the use of binary or machine-executable code is prohibited when it originates from sources with limited or no warranty or without the provision of source code;Hardware components provide the foundation for organizational systems and the platform for the execution of authorized software programs. Managing the inventory of hardware components and controlling which hardware components are permitted to be installed or connected to organizational systems is essential in order to provide adequate security.
","uuid":"a2e7a46a-92b7-4525-b0ef-488bb2904cdf","family":"Configuration Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"492c9608-5aa6-4459-a243-5f2d9c26daf3","text":"hardware components","parameterId":"cm-07.09_odp.01","default":" [Assignment: organization defined hardware components] "},{"constraints":"","displayName":"","guidance":"","uuid":"3f488b19-761b-4109-803c-277eaad0e965","text":"frequency","parameterId":"cm-07.09_odp.02","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"CM-07(09)(a)","uuid":"2fb81962-5238-4589-9689-161e4bdb5980","test":"Determine if [SELECTED PARAMETER VALUE(S): hardware components ] are identified;System components are discrete, identifiable information technology assets that include hardware, software, and firmware. Organizations may choose to implement centralized system component inventories that include components from all organizational systems. In such situations, organizations ensure that the inventories include system-specific information required for component accountability. The information necessary for effective accountability of system components includes the system name, software owners, software version numbers, hardware inventory specifications, software license information, and for networked components, the machine names and network addresses across all implemented protocols (e.g., IPv4, IPv6). Inventory specifications include date of receipt, cost, model, serial number, manufacturer, supplier information, component type, and physical location.
Preventing duplicate accounting of system components addresses the lack of accountability that occurs when component ownership and system association is not known, especially in large or complex connected systems. Effective prevention of duplicate accounting of system components necessitates use of a unique identifier for each component. For software inventory, centrally managed software that is accessed via other systems is addressed as a component of the system on which it is installed and managed. Software installed on multiple organizational systems and managed at the system level is addressed for each individual system and may appear more than once in a centralized component inventory, necessitating a system association for each software instance in the centralized inventory to avoid duplicate accounting of components. Scanning systems implementing multiple network protocols (e.g., IPv4 and IPv6) can result in duplicate components being identified in different address spaces. The implementation of CM-8(7) can help to eliminate duplicate accounting of components.
","uuid":"708e2d1b-df92-4388-b729-4c4b4555bf5a","family":"Configuration Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"b06afb86-f664-416b-90f7-74fdf9ebe864","text":"information","parameterId":"cm-08_odp.01","default":" [Assignment: organization defined information] "},{"constraints":"","displayName":"","guidance":"","uuid":"da504f9c-6108-4667-8af6-478cae93f220","text":"frequency","parameterId":"cm-08_odp.02","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"CM-08a.01","uuid":"0332b0cc-ab9d-4125-bf8a-bfe7b9a39aff","test":"Determine if an inventory of system components that accurately reflects the system is developed and documented;Organizations can improve the accuracy, completeness, and consistency of system component inventories if the inventories are updated as part of component installations or removals or during general system updates. If inventories are not updated at these key times, there is a greater likelihood that the information will not be appropriately captured and documented. System updates include hardware, software, and firmware components.
","uuid":"97539ca0-a43e-455e-bfd1-c1a1f419b82e","family":"Configuration Management","parameters":[],"subControls":"","tests":[{"testId":"CM-08(01)[01]","uuid":"8b85c4f3-05df-463c-b1d2-49dce1b74d54","test":"Determine if the inventory of system components is updated as part of component installations;Organizations maintain system inventories to the extent feasible. For example, virtual machines can be difficult to monitor because such machines are not visible to the network when not in use. In such cases, organizations maintain as up-to-date, complete, and accurate an inventory as is deemed reasonable. Automated maintenance can be achieved by the implementation of CM-2(2) for organizations that combine system component inventory and baseline configuration activities.
","uuid":"bd2b44d2-fb73-43af-accb-a82ee99d0771","family":"Configuration Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"f98099a0-2b90-4eeb-ac14-953fa3248ea7","text":"organization-defined automated mechanisms","parameterId":"cm-8.2_prm_1","default":" [Assignment: organization-defined automated mechanisms] "},{"constraints":"","displayName":"","guidance":"","uuid":"f0919a42-8a2d-4d4e-82d7-3ddbed227e42","text":"automated mechanisms","parameterId":"cm-08.02_odp.01","default":" [Assignment: organization defined automated mechanisms] "},{"constraints":"","displayName":"","guidance":"","uuid":"405dd5f6-ffb7-4d84-833e-cbf92f447c7e","text":"automated mechanisms","parameterId":"cm-08.02_odp.02","default":" [Assignment: organization defined automated mechanisms] "},{"constraints":"","displayName":"","guidance":"","uuid":"5df26581-bbaf-49d9-9f76-730cce656392","text":"automated mechanisms","parameterId":"cm-08.02_odp.03","default":" [Assignment: organization defined automated mechanisms] "},{"constraints":"","displayName":"","guidance":"","uuid":"4e5b8a3e-d02d-45db-895c-e166ec11a55c","text":"automated mechanisms","parameterId":"cm-08.02_odp.04","default":" [Assignment: organization defined automated mechanisms] "}],"subControls":"","tests":[{"testId":"CM-08(02)[01]","uuid":"878a454c-0969-41f7-aee6-eccfaa08fcc4","test":"Determine if [SELECTED PARAMETER VALUE(S): automated mechanisms ] are used to maintain the currency of the system component inventory;Automated unauthorized component detection is applied in addition to the monitoring for unauthorized remote connections and mobile devices. Monitoring for unauthorized system components may be accomplished on an ongoing basis or by the periodic scanning of systems for that purpose. Automated mechanisms may also be used to prevent the connection of unauthorized components (see CM-7(9) ). Automated mechanisms can be implemented in systems or in separate system components. When acquiring and implementing automated mechanisms, organizations consider whether such mechanisms depend on the ability of the system component to support an agent or supplicant in order to be detected since some types of components do not have or cannot support agents (e.g., IoT devices, sensors). Isolation can be achieved , for example, by placing unauthorized system components in separate domains or subnets or quarantining such components. This type of component isolation is commonly referred to as sandboxing.
\n
Identifying individuals who are responsible and accountable for administering system components ensures that the assigned components are properly administered and that organizations can contact those individuals if some action is required (e.g., when the component is determined to be the source of a breach, needs to be recalled or replaced, or needs to be relocated).
","uuid":"6bf9f714-af26-4548-acce-1371e45c2c80","family":"Configuration Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"25725a3c-f44f-490a-9b93-1858333faada","text":"[Selection (one or more): name; position; role]","parameterId":"cm-08.04_odp","default":"[Selection (one or more): name; position; role]"}],"subControls":"","tests":[{"testId":"CM-08(04)","uuid":"aca79d6c-6df6-428c-808a-48a15b0808d4","test":"Determine if individuals responsible and accountable for administering system components are identified by [SELECTED PARAMETER VALUE(S): [Selection (one or more): name; position; role] ] in the system component inventory.Assessed configurations and approved deviations focus on configuration settings established by organizations for system components, the specific components that have been assessed to determine compliance with the required configuration settings, and any approved deviations from established configuration settings.
","uuid":"12f889ae-a573-4f1e-bd8b-2180b9f7b1f6","family":"Configuration Management","parameters":[],"subControls":"","tests":[{"testId":"CM-08(06)[01]","uuid":"8ecfa600-a410-4db3-a50d-be72d89e7303","test":"Determine if assessed component configurations are included in the system component inventory;Organizations may implement centralized system component inventories that include components from all organizational systems. Centralized repositories of component inventories provide opportunities for efficiencies in accounting for organizational hardware, software, and firmware assets. Such repositories may also help organizations rapidly identify the location and responsible individuals of components that have been compromised, breached, or are otherwise in need of mitigation actions. Organizations ensure that the resulting centralized inventories include system-specific information required for proper component accountability.
","uuid":"53d2a48c-3f57-44e3-a34e-f24bafc28294","family":"Configuration Management","parameters":[],"subControls":"","tests":[{"testId":"CM-08(07)","uuid":"0c2d81f3-292b-4d83-bf5e-1b0fddccf04c","test":"Determine if a centralized repository for the system component inventory is provided.The use of automated mechanisms to track the location of system components can increase the accuracy of component inventories. Such capability may help organizations rapidly identify the location and responsible individuals of system components that have been compromised, breached, or are otherwise in need of mitigation actions. The use of tracking mechanisms can be coordinated with senior agency officials for privacy if there are implications that affect individual privacy.
","uuid":"1e9f6a59-caba-47d6-a4bb-900914f686b9","family":"Configuration Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"b392bdaa-edb5-4715-9df6-796a26f3ece9","text":"automated mechanisms","parameterId":"cm-08.08_odp","default":" [Assignment: organization defined automated mechanisms] "}],"subControls":"","tests":[{"testId":"CM-08(08)","uuid":"0f117d98-dd3a-46c0-a3d2-77164be7678f","test":"Determine if [SELECTED PARAMETER VALUE(S): automated mechanisms ] are used to support the tracking of system components by geographic location.System components that are not assigned to a system may be unmanaged, lack the required protection, and become an organizational vulnerability.
","uuid":"51212d07-e505-4a17-aa6a-649438b07224","family":"Configuration Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"248e3d26-ffdb-4fe2-94ac-39ec847d8cfd","text":"personnel or roles","parameterId":"cm-08.09_odp","default":" [Assignment: organization defined personnel or roles] "}],"subControls":"","tests":[{"testId":"CM-08(09)(a)","uuid":"582a9ffa-9434-4865-b18e-fd16f6378a41","test":"Determine if system components are assigned to a system;Configuration management activities occur throughout the system development life cycle. As such, there are developmental configuration management activities (e.g., the control of code and software libraries) and operational configuration management activities (e.g., control of installed components and how the components are configured). Configuration management plans satisfy the requirements in configuration management policies while being tailored to individual systems. Configuration management plans define processes and procedures for how configuration management is used to support system development life cycle activities.
Configuration management plans are generated during the development and acquisition stage of the system development life cycle. The plans describe how to advance changes through change management processes; update configuration settings and baselines; maintain component inventories; control development, test, and operational environments; and develop, release, and update key documents.
Organizations can employ templates to help ensure the consistent and timely development and implementation of configuration management plans. Templates can represent a configuration management plan for the organization with subsets of the plan implemented on a system by system basis. Configuration management approval processes include the designation of key stakeholders responsible for reviewing and approving proposed changes to systems, and personnel who conduct security and privacy impact analyses prior to the implementation of changes to the systems. Configuration items are the system components, such as the hardware, software, firmware, and documentation to be configuration-managed. As systems continue through the system development life cycle, new configuration items may be identified, and some existing configuration items may no longer need to be under configuration control.
","uuid":"326776de-3653-41b0-a84b-ab955f116c4d","family":"Configuration Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"6b0b9209-a9e2-4531-873b-d84a784440be","text":"personnel or roles","parameterId":"cm-09_odp","default":" [Assignment: organization defined personnel or roles] "}],"subControls":"","tests":[{"testId":"CM-09[01]","uuid":"4cafe115-4667-409d-b4bf-a4ab9d7a8cea","test":"Determine if a configuration management plan for the system is developed and documented;In the absence of dedicated configuration management teams assigned within organizations, system developers may be tasked with developing configuration management processes using personnel who are not directly involved in system development or system integration. This separation of duties ensures that organizations establish and maintain a sufficient degree of independence between the system development and integration processes and configuration management processes to facilitate quality control and more effective oversight.
","uuid":"2ef01b73-b0a9-4ac0-9580-e03982c79616","family":"Configuration Management","parameters":[],"subControls":"","tests":[{"testId":"CM-09(01)","uuid":"bfcfca15-1c70-4503-90f0-ae94f807b721","test":"Determine if the responsibility for developing the configuration management process is assigned to organizational personnel who are not directly involved in system development.Software license tracking can be accomplished by manual or automated methods, depending on organizational needs. Examples of contract agreements include software license agreements and non-disclosure agreements.
","uuid":"40c2e457-26dd-4e9e-923b-25cbfea9fcbc","family":"Configuration Management","parameters":[],"subControls":"","tests":[{"testId":"CM-10a.","uuid":"8a594c44-a731-4c92-837e-1e152b0a68a7","test":"Determine if software and associated documentation are used in accordance with contract agreements and copyright laws;Open-source software refers to software that is available in source code form. Certain software rights normally reserved for copyright holders are routinely provided under software license agreements that permit individuals to study, change, and improve the software. From a security perspective, the major advantage of open-source software is that it provides organizations with the ability to examine the source code. In some cases, there is an online community associated with the software that inspects, tests, updates, and reports on issues found in software on an ongoing basis. However, remediating vulnerabilities in open-source software may be problematic. There may also be licensing issues associated with open-source software, including the constraints on derivative use of such software. Open-source software that is available only in binary form may increase the level of risk in using such software.
","uuid":"9270a1d2-b496-4207-8863-ed6938207c27","family":"Configuration Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"d5eec0cc-9431-4a2c-8c6d-fa99afa7e1f8","text":"restrictions","parameterId":"cm-10.01_odp","default":" [Assignment: organization defined restrictions] "}],"subControls":"","tests":[{"testId":"CM-10(01)","uuid":"f99657f0-8991-41ef-af8f-92cd08d49d8f","test":"Determine if [SELECTED PARAMETER VALUE(S): restrictions ] are established for the use of open-source software.If provided the necessary privileges, users can install software in organizational systems. To maintain control over the software installed, organizations identify permitted and prohibited actions regarding software installation. Permitted software installations include updates and security patches to existing software and downloading new applications from organization-approved app stores.
Prohibited software installations include software with unknown or suspect pedigrees or software that organizations consider potentially malicious. Policies selected for governing user-installed software are organization-developed or provided by some external entity. Policy enforcement methods can include procedural methods and automated methods.
Privileged status can be obtained, for example, by serving in the role of system administrator.
","uuid":"f8f9c121-82be-4f24-9311-a4716204663a","family":"Configuration Management","parameters":[],"subControls":"","tests":[{"testId":"CM-11(02)","uuid":"930d40b8-550c-43de-b7d2-e0fb37f684b5","test":"Determine if user installation of software is allowed only with explicit privileged status.Organizations enforce and monitor compliance with software installation policies using automated mechanisms to more quickly detect and respond to unauthorized software installation which can be an indicator of an internal or external hostile attack.
","uuid":"d8c9b717-e1f7-4f40-9130-044e598d7d6b","family":"Configuration Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"bf85b040-b825-4e44-8846-07aff1c39435","text":"organization-defined automated mechanisms","parameterId":"cm-11.3_prm_1","default":" [Assignment: organization-defined automated mechanisms] "},{"constraints":"","displayName":"","guidance":"","uuid":"90e78b7c-eb43-4da0-83d4-d68bc509e5bd","text":"automated mechanisms","parameterId":"cm-11.03_odp.01","default":" [Assignment: organization defined automated mechanisms] "},{"constraints":"","displayName":"","guidance":"","uuid":"c93e922c-654b-449f-9556-0c318cc108bd","text":"automated mechanisms","parameterId":"cm-11.03_odp.02","default":" [Assignment: organization defined automated mechanisms] "}],"subControls":"","tests":[{"testId":"CM-11(03)[01]","uuid":"521d242a-0cc8-4f53-b2ea-912b5c82ba6f","test":"Determine if compliance with software installation policies is enforced using [SELECTED PARAMETER VALUE(S): automated mechanisms ];Information location addresses the need to understand where information is being processed and stored. Information location includes identifying where specific information types and information reside in system components and how information is being processed so that information flow can be understood and adequate protection and policy management provided for such information and system components. The security category of the information is also a factor in determining the controls necessary to protect the information and the system component where the information resides (see FIPS 199 ). The location of the information and system components is also a factor in the architecture and design of the system (see SA-4, SA-8, SA-17).
","uuid":"2461facf-5a72-4bc7-9b90-4d177e60b391","family":"Configuration Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"3335dc9b-e5a4-4e10-8580-583a7e3d3698","text":"information","parameterId":"cm-12_odp","default":" [Assignment: organization defined information] "}],"subControls":"","tests":[{"testId":"CM-12a.[01]","uuid":"a2730e84-d395-4ac0-bffa-8e77c3b4f8b1","test":"Determine if the location of [SELECTED PARAMETER VALUE(S): information ] is identified and documented;The use of automated tools helps to increase the effectiveness and efficiency of the information location capability implemented within the system. Automation also helps organizations manage the data produced during information location activities and share such information across the organization. The output of automated information location tools can be used to guide and inform system architecture and design decisions.
","uuid":"f66f6e12-debd-469f-9ed3-d7e23da79eee","family":"Configuration Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"653ffb95-0463-4fa8-8b7d-2550adb4a3dc","text":"information by information type","parameterId":"cm-12.01_odp.01","default":" [Assignment: organization defined information by information type] "},{"constraints":"","displayName":"","guidance":"","uuid":"f1811395-6016-4210-9ef5-2533ffe78f34","text":"system components","parameterId":"cm-12.01_odp.02","default":" [Assignment: organization defined system components] "}],"subControls":"","tests":[{"testId":"CM-12(01)","uuid":"75d578e3-5e07-49ed-92a4-94967f98652a","test":"Determine if automated tools are used to identify [SELECTED PARAMETER VALUE(S): information by information type ] on [SELECTED PARAMETER VALUE(S): system components ] to ensure that controls are in place to protect organizational information and individual privacy.Data actions are system operations that process personally identifiable information. The processing of such information encompasses the full information life cycle, which includes collection, generation, transformation, use, disclosure, retention, and disposal. A map of system data actions includes discrete data actions, elements of personally identifiable information being processed in the data actions, system components involved in the data actions, and the owners or operators of the system components. Understanding what personally identifiable information is being processed (e.g., the sensitivity of the personally identifiable information), how personally identifiable information is being processed (e.g., if the data action is visible to the individual or is processed in another part of the system), and by whom (e.g., individuals may have different privacy perceptions based on the entity that is processing the personally identifiable information) provides a number of contextual factors that are important to assessing the degree of privacy risk created by the system. Data maps can be illustrated in different ways, and the level of detail may vary based on the mission and business needs of the organization. The data map may be an overlay of any system design artifact that the organization is using. The development of this map may necessitate coordination between the privacy and security programs regarding the covered data actions and the components that are identified as part of the system.
","uuid":"4fccd0c1-1c48-4e4a-a77f-7a49a7046821","family":"Configuration Management","parameters":[],"subControls":"","tests":[{"testId":"CM-13","uuid":"83327a9a-2ad0-4aab-b059-afec0939b711","test":"Determine if a map of system data actions is developed and documented.Software and firmware components prevented from installation unless signed with recognized and approved certificates include software and firmware version updates, patches, service packs, device drivers, and basic input/output system updates. Organizations can identify applicable software and firmware components by type, by specific items, or a combination of both. Digital signatures and organizational verification of such signatures is a method of code authentication.
","uuid":"81f1ac6e-2c28-4632-8649-01a8e3445805","family":"Configuration Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"579a952d-890c-425f-afcd-8c7d925daaab","text":"organization-defined software and firmware components","parameterId":"cm-14_prm_1","default":" [Assignment: organization-defined software and firmware components] "},{"constraints":"","displayName":"","guidance":"","uuid":"1a052ac8-f8e4-413f-acd1-dfb92588df13","text":"software components","parameterId":"cm-14_odp.01","default":" [Assignment: organization defined software components] "},{"constraints":"","displayName":"","guidance":"","uuid":"71ffae85-062b-41b2-ab63-b38a02afeb8e","text":"firmware components","parameterId":"cm-14_odp.02","default":" [Assignment: organization defined firmware components] "}],"subControls":"","tests":[{"testId":"CM-14[01]","uuid":"78a61455-adb1-4975-b77e-f6f701fd3311","test":"Determine if the installation of [SELECTED PARAMETER VALUE(S): software components ] is prevented unless it is verified that the software has been digitally signed using a certificate recognized and approved by the organization;Contingency planning policy and procedures address the controls in the CP family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of contingency planning policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission or business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to contingency planning policy and procedures include assessment or audit findings, security incidents or breaches, or changes in laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure.
","uuid":"14831c4f-2d1e-4092-ae22-a0331cd71219","family":"Contingency Planning","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"d431b90f-c908-4b74-bcee-f30d02688181","text":"organization-defined personnel or roles","parameterId":"cp-1_prm_1","default":" [Assignment: organization-defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"12f5aabf-6634-4b97-9b37-f1f402396b75","text":"personnel or roles","parameterId":"cp-01_odp.01","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"f9641897-27cb-4e43-a7ce-b268683ab1f9","text":"personnel or roles","parameterId":"cp-01_odp.02","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"2e81ee8c-49e0-45d4-8828-3849cdf02797","text":"[Selection (one or more): organization-level; mission/business process-level; system-level]","parameterId":"cp-01_odp.03","default":"[Selection (one or more): organization-level; mission/business process-level; system-level]"},{"constraints":"","displayName":"","guidance":"","uuid":"86b070a7-0c1c-4cc1-ac68-e0a8f76fcd39","text":"official","parameterId":"cp-01_odp.04","default":" [Assignment: organization defined official] "},{"constraints":"","displayName":"","guidance":"","uuid":"bf84d315-b5d5-4fe5-ac8c-29ed96b25108","text":"frequency","parameterId":"cp-01_odp.05","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"354ddb32-87a4-40b5-b56f-e43d0bde584b","text":"events","parameterId":"cp-01_odp.06","default":" [Assignment: organization defined events] "},{"constraints":"","displayName":"","guidance":"","uuid":"36a8c728-4e36-4914-86a4-fbe2af204b85","text":"frequency","parameterId":"cp-01_odp.07","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"4cbbb213-e427-4fb2-a8f6-bd033b18f105","text":"events","parameterId":"cp-01_odp.08","default":" [Assignment: organization defined events] "}],"subControls":"","tests":[{"testId":"CP-01a.[01]","uuid":"f804da54-7431-4321-b7a9-7e3812b690b0","test":"Determine if a contingency planning policy is developed and documented;Contingency planning for systems is part of an overall program for achieving continuity of operations for organizational mission and business functions. Contingency planning addresses system restoration and implementation of alternative mission or business processes when systems are compromised or breached. Contingency planning is considered throughout the system development life cycle and is a fundamental part of the system design. Systems can be designed for redundancy, to provide backup capabilities, and for resilience. Contingency plans reflect the degree of restoration required for organizational systems since not all systems need to fully recover to achieve the level of continuity of operations desired. System recovery objectives reflect applicable laws, executive orders, directives, regulations, policies, standards, guidelines, organizational risk tolerance, and system impact level.
Actions addressed in contingency plans include orderly system degradation, system shutdown, fallback to a manual mode, alternate information flows, and operating in modes reserved for when systems are under attack. By coordinating contingency planning with incident handling activities, organizations ensure that the necessary planning activities are in place and activated in the event of an incident. Organizations consider whether continuity of operations during an incident conflicts with the capability to automatically disable the system, as specified in IR-4(5) . Incident response planning is part of contingency planning for organizations and is addressed in the IR (Incident Response) family.
","uuid":"03482310-a8cc-4053-a241-70a7c1d37c24","family":"Contingency Planning","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"73c1beb4-c1f0-4cc6-8ab7-cefc884d7acb","text":"organization-defined personnel or roles","parameterId":"cp-2_prm_1","default":" [Assignment: organization-defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"5ac596ca-1837-4530-8909-79e8199991f1","text":"organization-defined key contingency personnel (identified by name and/or by role) and organizational elements","parameterId":"cp-2_prm_2","default":" [Assignment: organization-defined key contingency personnel (identified by name and/or by role) and organizational elements] "},{"constraints":"","displayName":"","guidance":"","uuid":"eb91b730-3375-491d-b194-ab56ff97a9d5","text":"organization-defined key contingency personnel (identified by name and/or by role) and organizational elements","parameterId":"cp-2_prm_4","default":" [Assignment: organization-defined key contingency personnel (identified by name and/or by role) and organizational elements] "},{"constraints":"","displayName":"","guidance":"","uuid":"d0716270-6131-4406-a134-df4d3fad3f34","text":"personnel or roles","parameterId":"cp-02_odp.01","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"ddb0f7a4-fab3-4dc1-a32c-3ca2f4748c8b","text":"personnel or roles","parameterId":"cp-02_odp.02","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"bf195c3a-3b77-471e-9caf-936fb088414b","text":"key contingency personnel","parameterId":"cp-02_odp.03","default":" [Assignment: organization defined key contingency personnel] "},{"constraints":"","displayName":"","guidance":"","uuid":"f7e1fe23-afbe-4975-bc29-4a859aa2dbb9","text":"organizational elements","parameterId":"cp-02_odp.04","default":" [Assignment: organization defined organizational elements] "},{"constraints":"","displayName":"","guidance":"","uuid":"3ec334a3-ee11-42cb-a1aa-68956db312b5","text":"frequency","parameterId":"cp-02_odp.05","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"6b084360-80b9-41dc-b07d-596e25a6e25e","text":"key contingency personnel","parameterId":"cp-02_odp.06","default":" [Assignment: organization defined key contingency personnel] "},{"constraints":"","displayName":"","guidance":"","uuid":"03a32be5-43c0-467a-a75b-1b2ac00126db","text":"organizational elements","parameterId":"cp-02_odp.07","default":" [Assignment: organization defined organizational elements] "}],"subControls":"","tests":[{"testId":"CP-02a.01","uuid":"d02f4815-825f-4476-b43f-a12d9a019d48","test":"Determine if a contingency plan for the system is developed that identifies essential mission and business functions and associated contingency requirements;Plans that are related to contingency plans include Business Continuity Plans, Disaster Recovery Plans, Critical Infrastructure Plans, Continuity of Operations Plans, Crisis Communications Plans, Insider Threat Implementation Plans, Data Breach Response Plans, Cyber Incident Response Plans, Breach Response Plans, and Occupant Emergency Plans.
","uuid":"011ca744-7fd0-4749-8c02-1f9c53761302","family":"Contingency Planning","parameters":[],"subControls":"","tests":[{"testId":"CP-02(01)","uuid":"ac06ed2d-3547-456f-a8c5-e96f12f95e36","test":"Determine if contingency plan development is coordinated with organizational elements responsible for related plans.Capacity planning is needed because different threats can result in a reduction of the available processing, telecommunications, and support services intended to support essential mission and business functions. Organizations anticipate degraded operations during contingency operations and factor the degradation into capacity planning. For capacity planning, environmental support refers to any environmental factor for which the organization determines that it needs to provide support in a contingency situation, even if in a degraded state. Such determinations are based on an organizational assessment of risk, system categorization (impact level), and organizational risk tolerance.
","uuid":"0c5f5253-1024-4fea-b56d-f13c824a3e9f","family":"Contingency Planning","parameters":[],"subControls":"","tests":[{"testId":"CP-02(02)[01]","uuid":"c37dce26-fd37-4a60-ad2d-1de0ac1e5149","test":"Determine if capacity planning is conducted so that the necessary capacity exists during contingency operations for information processing;Organizations may choose to conduct contingency planning activities to resume mission and business functions as part of business continuity planning or as part of business impact analyses. Organizations prioritize the resumption of mission and business functions. The time period for resuming mission and business functions may be dependent on the severity and extent of the disruptions to the system and its supporting infrastructure.
","uuid":"fd36ccfe-cb59-4b3d-9227-c7b9d694d99b","family":"Contingency Planning","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"c684b5bf-7077-44cf-96fa-d066dbac75eb","text":"[Selection: all; essential]","parameterId":"cp-02.03_odp.01","default":"[Selection: all; essential]"},{"constraints":"","displayName":"","guidance":"","uuid":"664ea426-f0d3-4d95-90b8-492ebf237278","text":"time period","parameterId":"cp-02.03_odp.02","default":" [Assignment: organization defined time period] "}],"subControls":"","tests":[{"testId":"CP-02(03)","uuid":"65fda164-6ece-4f99-8c25-4aa371125d37","test":"Determine if the resumption of [SELECTED PARAMETER VALUE(S): [Selection: all; essential] ] mission and business functions are planned for within [SELECTED PARAMETER VALUE(S): time period ] of contingency plan activation.Organizations may choose to conduct the contingency planning activities to continue mission and business functions as part of business continuity planning or business impact analyses. Primary processing and/or storage sites defined by organizations as part of contingency planning may change depending on the circumstances associated with the contingency.
","uuid":"08cd6c18-c284-4ec5-a66a-0d33f149d77b","family":"Contingency Planning","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"02d4e7f4-a44d-4b9c-9637-0b1853781af2","text":"[Selection: all; essential]","parameterId":"cp-02.05_odp","default":"[Selection: all; essential]"}],"subControls":"","tests":[{"testId":"CP-02(05)[01]","uuid":"326a3137-8e45-40cd-aaf5-0df06b969c0e","test":"Determine if the continuance of [SELECTED PARAMETER VALUE(S): [Selection: all; essential] ] mission and business functions with minimal or no loss of operational continuity is planned for;Organizations may choose to conduct contingency planning activities for alternate processing and storage sites as part of business continuity planning or business impact analyses. Primary processing and/or storage sites defined by organizations as part of contingency planning may change depending on the circumstances associated with the contingency.
","uuid":"07bd8d89-ed6c-4186-8637-60f69c2c22d5","family":"Contingency Planning","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"5fcc2fa9-79a4-4aed-80cd-09e76dfb0743","text":"[Selection: all; essential]","parameterId":"cp-02.06_odp","default":"[Selection: all; essential]"}],"subControls":"","tests":[{"testId":"CP-02(06)[01]","uuid":"cff9c0fa-8ca9-4233-a8dc-dd8f38157175","test":"Determine if the transfer of [SELECTED PARAMETER VALUE(S): [Selection: all; essential] ] mission and business functions to alternate processing and/or storage sites with minimal or no loss of operational continuity is planned for;When the capability of an organization to carry out its mission and business functions is dependent on external service providers, developing a comprehensive and timely contingency plan may become more challenging. When mission and business functions are dependent on external service providers, organizations coordinate contingency planning activities with the external entities to ensure that the individual plans reflect the overall contingency needs of the organization.
","uuid":"18150a42-560e-4545-80ce-536a25b9feda","family":"Contingency Planning","parameters":[],"subControls":"","tests":[{"testId":"CP-02(07)","uuid":"848da701-0183-4a17-b151-d37075353b75","test":"Determine if the contingency plan is coordinated with the contingency plans of external service providers to ensure that contingency requirements can be satisfied.Organizations may choose to identify critical assets as part of criticality analysis, business continuity planning, or business impact analyses. Organizations identify critical system assets so that additional controls can be employed (beyond the controls routinely implemented) to help ensure that organizational mission and business functions can continue to be conducted during contingency operations. The identification of critical information assets also facilitates the prioritization of organizational resources. Critical system assets include technical and operational aspects. Technical aspects include system components, information technology services, information technology products, and mechanisms. Operational aspects include procedures (i.e., manually executed operations) and personnel (i.e., individuals operating technical controls and/or executing manual procedures). Organizational program protection plans can assist in identifying critical assets. If critical assets are resident within or supported by external service providers, organizations consider implementing CP-2(7) as a control enhancement.
","uuid":"4b99303a-890f-46dd-8620-20999963d973","family":"Contingency Planning","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"2b13ae8f-b7b8-44cf-b8e0-c41be90a79ae","text":"[Selection: all; essential]","parameterId":"cp-02.08_odp","default":"[Selection: all; essential]"}],"subControls":"","tests":[{"testId":"CP-02(08)","uuid":"9e9b09d6-0426-4430-afbc-df5e0f93b599","test":"Determine if critical system assets supporting [SELECTED PARAMETER VALUE(S): [Selection: all; essential] ] mission and business functions are identified.Contingency training provided by organizations is linked to the assigned roles and responsibilities of organizational personnel to ensure that the appropriate content and level of detail is included in such training. For example, some individuals may only need to know when and where to report for duty during contingency operations and if normal duties are affected; system administrators may require additional training on how to establish systems at alternate processing and storage sites; and organizational officials may receive more specific training on how to conduct mission-essential functions in designated off-site locations and how to establish communications with other governmental entities for purposes of coordination on contingency-related activities. Training for contingency roles or responsibilities reflects the specific continuity requirements in the contingency plan. Events that may precipitate an update to contingency training content include, but are not limited to, contingency plan testing or an actual contingency (lessons learned), assessment or audit findings, security incidents or breaches, or changes in laws, executive orders, directives, regulations, policies, standards, and guidelines. At the discretion of the organization, participation in a contingency plan test or exercise, including lessons learned sessions subsequent to the test or exercise, may satisfy contingency plan training requirements.
","uuid":"8f10e947-9b9e-43b2-b2cc-3e39e4a720c4","family":"Contingency Planning","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"aab1ca20-fe72-4376-bee0-d010c01e6340","text":"time period","parameterId":"cp-03_odp.01","default":" [Assignment: organization defined time period] "},{"constraints":"","displayName":"","guidance":"","uuid":"8c006192-ff10-430d-8b84-379b769c2ebb","text":"frequency","parameterId":"cp-03_odp.02","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"0e102944-40ad-47b8-a806-a029c9f6078e","text":"frequency","parameterId":"cp-03_odp.03","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"aacf96d8-f565-40dc-80f0-d73c4694c836","text":"events","parameterId":"cp-03_odp.04","default":" [Assignment: organization defined events] "}],"subControls":"","tests":[{"testId":"CP-03a.01","uuid":"8873db4c-8bee-4846-b530-f5788a64be1b","test":"Determine if contingency training is provided to system users consistent with assigned roles and responsibilities within [SELECTED PARAMETER VALUE(S): time period ] of assuming a contingency role or responsibility;The use of simulated events creates an environment for personnel to experience actual threat events, including cyber-attacks that disable websites, ransomware attacks that encrypt organizational data on servers, hurricanes that damage or destroy organizational facilities, or hardware or software failures.
","uuid":"d9621be8-603f-4386-839c-98814e920b27","family":"Contingency Planning","parameters":[],"subControls":"","tests":[{"testId":"CP-03(01)","uuid":"2dfe9f69-423f-4f10-87df-6d3438cdfd7c","test":"Determine if simulated events are incorporated into contingency training to facilitate effective response by personnel in crisis situations.Operational mechanisms refer to processes that have been established to accomplish an organizational goal or a system that supports a particular organizational mission or business objective. Actual mission and business processes, systems, and/or facilities may be used to generate simulated events and enhance the realism of simulated events during contingency training.
","uuid":"edb54731-21c0-4452-8c2f-1b87adefbbbd","family":"Contingency Planning","parameters":[],"subControls":"","tests":[{"testId":"CP-03(02)","uuid":"1995eb38-51bf-49ff-ab41-48cff80637cf","test":"Determine if mechanisms used in operations are employed to provide a more thorough and realistic contingency training environment.Methods for testing contingency plans to determine the effectiveness of the plans and identify potential weaknesses include checklists, walk-through and tabletop exercises, simulations (parallel or full interrupt), and comprehensive exercises. Organizations conduct testing based on the requirements in contingency plans and include a determination of the effects on organizational operations, assets, and individuals due to contingency operations. Organizations have flexibility and discretion in the breadth, depth, and timelines of corrective actions.
","uuid":"b5a61f9d-44b7-48c6-a730-8ad0a494de62","family":"Contingency Planning","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"3906d9e8-47fd-42b2-a7c9-d22d28ad6548","text":"organization-defined tests","parameterId":"cp-4_prm_2","default":" [Assignment: organization-defined tests] "},{"constraints":"","displayName":"","guidance":"","uuid":"a5c3ada4-3096-4e68-88b3-89ce1035eb64","text":"frequency","parameterId":"cp-04_odp.01","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"f2169a22-2727-4685-8692-4552ff77988e","text":"tests","parameterId":"cp-04_odp.02","default":" [Assignment: organization defined tests] "},{"constraints":"","displayName":"","guidance":"","uuid":"93a6c396-86bf-4f31-9295-bb109d7bc7db","text":"tests","parameterId":"cp-04_odp.03","default":" [Assignment: organization defined tests] "}],"subControls":"","tests":[{"testId":"CP-04a.[01]","uuid":"b35af927-2193-4027-b8f8-c4016d208206","test":"Determine if the contingency plan for the system is tested [SELECTED PARAMETER VALUE(S): frequency ];Plans related to contingency planning for organizational systems include Business Continuity Plans, Disaster Recovery Plans, Continuity of Operations Plans, Crisis Communications Plans, Critical Infrastructure Plans, Cyber Incident Response Plans, and Occupant Emergency Plans. Coordination of contingency plan testing does not require organizations to create organizational elements to handle related plans or to align such elements with specific plans. However, it does require that if such organizational elements are responsible for related plans, organizations coordinate with those elements.
","uuid":"8b24c128-b7a2-41fd-96f0-ecf3891c881e","family":"Contingency Planning","parameters":[],"subControls":"","tests":[{"testId":"CP-04(01)","uuid":"cbaf6c7a-b69b-49bd-8d3b-37eab5910bdb","test":"Determine if contingency plan testing is coordinated with organizational elements responsible for related plans.Conditions at the alternate processing site may be significantly different than the conditions at the primary site. Having the opportunity to visit the alternate site and experience the actual capabilities available at the site can provide valuable information on potential vulnerabilities that could affect essential organizational mission and business functions. The on-site visit can also provide an opportunity to refine the contingency plan to address the vulnerabilities discovered during testing.
","uuid":"3642b0c7-ad47-4e27-a67e-e8f003b3c85d","family":"Contingency Planning","parameters":[],"subControls":"","tests":[{"testId":"CP-04(02)(a)","uuid":"76825318-d229-4f7e-9405-850d63bf140e","test":"Determine if the contingency plan is tested at the alternate processing site to familiarize contingency personnel with the facility and available resources;Automated mechanisms facilitate thorough and effective testing of contingency plans by providing more complete coverage of contingency issues, selecting more realistic test scenarios and environments, and effectively stressing the system and supported mission and business functions.
","uuid":"3f8444ff-cb88-4bb3-bf3e-a81dbcfbf27b","family":"Contingency Planning","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"1e0698f3-17a3-4fb7-86bd-1b3f9590e87e","text":"automated mechanisms","parameterId":"cp-04.03_odp","default":" [Assignment: organization defined automated mechanisms] "}],"subControls":"","tests":[{"testId":"CP-04(03)","uuid":"7b19f285-7a3e-4912-a108-167185d1e50a","test":"Determine if the contingency plan is tested using [SELECTED PARAMETER VALUE(S): automated mechanisms ].Recovery is executing contingency plan activities to restore organizational mission and business functions. Reconstitution takes place following recovery and includes activities for returning systems to fully operational states. Organizations establish a known state for systems that includes system state information for hardware, software programs, and data. Preserving system state information facilitates system restart and return to the operational mode of organizations with less disruption of mission and business processes.
","uuid":"6123eced-1514-43b6-9cea-ff6baae769c5","family":"Contingency Planning","parameters":[],"subControls":"","tests":[{"testId":"CP-04(04)[01]","uuid":"86b3969d-fe5d-4abe-9cdc-8dc28a57ca5b","test":"Determine if a full recovery of the system to a known state is included as part of contingency plan testing;Often, the best method of assessing system resilience is to disrupt the system in some manner. The mechanisms used by the organization could disrupt system functions or system services in many ways, including terminating or disabling critical system components, changing the configuration of system components, degrading critical functionality (e.g., restricting network bandwidth), or altering privileges. Automated, on-going, and simulated cyber-attacks and service disruptions can reveal unexpected functional dependencies and help the organization determine its ability to ensure resilience in the face of an actual cyber-attack.
","uuid":"f4f5f1b0-e4b7-4375-9dc1-550b4908c592","family":"Contingency Planning","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"df2628cb-4d16-4d97-835f-11f8a622bf42","text":"mechanisms","parameterId":"cp-04.05_odp.01","default":" [Assignment: organization defined mechanisms] "},{"constraints":"","displayName":"","guidance":"","uuid":"105eea3c-5b2a-499b-90e8-d62d59dbd61e","text":"system or system component","parameterId":"cp-04.05_odp.02","default":" [Assignment: organization defined system or system component] "}],"subControls":"","tests":[{"testId":"CP-04(05)","uuid":"45bde58c-2258-4814-a1a6-d28fd1d574ac","test":"Determine if [SELECTED PARAMETER VALUE(S): mechanisms ] are employed to disrupt and adversely affect the [SELECTED PARAMETER VALUE(S): system or system component ].Alternate storage sites are geographically distinct from primary storage sites and maintain duplicate copies of information and data if the primary storage site is not available. Similarly, alternate processing sites provide processing capability if the primary processing site is not available. Geographically distributed architectures that support contingency requirements may be considered alternate storage sites. Items covered by alternate storage site agreements include environmental conditions at the alternate sites, access rules for systems and facilities, physical and environmental protection requirements, and coordination of delivery and retrieval of backup media. Alternate storage sites reflect the requirements in contingency plans so that organizations can maintain essential mission and business functions despite compromise, failure, or disruption in organizational systems.
","uuid":"68b06cc7-d9a7-472a-bebf-f0b49368dc0c","family":"Contingency Planning","parameters":[],"subControls":"","tests":[{"testId":"CP-06a.[01]","uuid":"5183b2ee-668f-421d-af2a-1dc269f733ef","test":"Determine if an alternate storage site is established;Threats that affect alternate storage sites are defined in organizational risk assessments and include natural disasters, structural failures, hostile attacks, and errors of omission or commission. Organizations determine what is considered a sufficient degree of separation between primary and alternate storage sites based on the types of threats that are of concern. For threats such as hostile attacks, the degree of separation between sites is less relevant.
","uuid":"57563258-cc85-45ce-84cc-3a8ee7ee87a5","family":"Contingency Planning","parameters":[],"subControls":"","tests":[{"testId":"CP-06(01)","uuid":"37b63660-f159-421c-a293-5e47bb93fdb2","test":"Determine if an alternate storage site that is sufficiently separated from the primary storage site is identified to reduce susceptibility to the same threats.Organizations establish recovery time and recovery point objectives as part of contingency planning. Configuration of the alternate storage site includes physical facilities and the systems supporting recovery operations that ensure accessibility and correct execution.
","uuid":"d935e159-cd01-48f3-98a3-c617a20e4d9d","family":"Contingency Planning","parameters":[],"subControls":"","tests":[{"testId":"CP-06(02)[01]","uuid":"382be77a-c7d1-4209-9240-0aeeb81d03ba","test":"Determine if the alternate storage site is configured to facilitate recovery operations in accordance with recovery time objectives;Area-wide disruptions refer to those types of disruptions that are broad in geographic scope with such determinations made by organizations based on organizational assessments of risk. Explicit mitigation actions include duplicating backup information at other alternate storage sites if access problems occur at originally designated alternate sites or planning for physical access to retrieve backup information if electronic accessibility to the alternate site is disrupted.
","uuid":"597f3431-0797-4dce-a96b-afd5c7995283","family":"Contingency Planning","parameters":[],"subControls":"","tests":[{"testId":"CP-06(03)[01]","uuid":"65c86e05-6470-41b9-862d-958f99418fb7","test":"Determine if potential accessibility problems to the alternate storage site in the event of an area-wide disruption or disaster are identified;Alternate processing sites are geographically distinct from primary processing sites and provide processing capability if the primary processing site is not available. The alternate processing capability may be addressed using a physical processing site or other alternatives, such as failover to a cloud-based service provider or other internally or externally provided processing service. Geographically distributed architectures that support contingency requirements may also be considered alternate processing sites. Controls that are covered by alternate processing site agreements include the environmental conditions at alternate sites, access rules, physical and environmental protection requirements, and the coordination for the transfer and assignment of personnel. Requirements are allocated to alternate processing sites that reflect the requirements in contingency plans to maintain essential mission and business functions despite disruption, compromise, or failure in organizational systems.
","uuid":"571edd41-5102-4141-b001-40f571aa35d1","family":"Contingency Planning","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"7909fbed-a3df-4831-9631-2b631c2bbc20","text":"system operations","parameterId":"cp-07_odp.01","default":" [Assignment: organization defined system operations] "},{"constraints":"","displayName":"","guidance":"","uuid":"e9f146b3-0da4-4b84-a71d-c415d8a9a5af","text":"time period","parameterId":"cp-07_odp.02","default":" [Assignment: organization defined time period] "}],"subControls":"","tests":[{"testId":"CP-07a.","uuid":"ad0554c2-bcb1-4c82-aa4d-817e3c76b73b","test":"Determine if an alternate processing site, including necessary agreements to permit the transfer and resumption of [SELECTED PARAMETER VALUE(S): system operations ] for essential mission and business functions, is established within [SELECTED PARAMETER VALUE(S): time period ] when the primary processing capabilities are unavailable;Threats that affect alternate processing sites are defined in organizational assessments of risk and include natural disasters, structural failures, hostile attacks, and errors of omission or commission. Organizations determine what is considered a sufficient degree of separation between primary and alternate processing sites based on the types of threats that are of concern. For threats such as hostile attacks, the degree of separation between sites is less relevant.
","uuid":"85757b09-4200-46de-9202-fbffbc9c3c74","family":"Contingency Planning","parameters":[],"subControls":"","tests":[{"testId":"CP-07(01)","uuid":"6773b9a6-23e0-4fea-9c86-ec1e72c860d6","test":"Determine if an alternate processing site that is sufficiently separated from the primary processing site to reduce susceptibility to the same threats is identified.Area-wide disruptions refer to those types of disruptions that are broad in geographic scope with such determinations made by organizations based on organizational assessments of risk.
","uuid":"f818364d-4be3-4a55-a526-72d70673106e","family":"Contingency Planning","parameters":[],"subControls":"","tests":[{"testId":"CP-07(02)[01]","uuid":"08895c63-865e-47d7-abe1-071343c71c97","test":"Determine if potential accessibility problems to alternate processing sites in the event of an area-wide disruption or disaster are identified;Priority of service agreements refer to negotiated agreements with service providers that ensure that organizations receive priority treatment consistent with their availability requirements and the availability of information resources for logical alternate processing and/or at the physical alternate processing site. Organizations establish recovery time objectives as part of contingency planning.
","uuid":"b78b43c2-7f63-4b54-96c1-8b6dbb580724","family":"Contingency Planning","parameters":[],"subControls":"","tests":[{"testId":"CP-07(03)","uuid":"471e8623-0ff8-413a-ba5d-ce3f1204b865","test":"Determine if alternate processing site agreements that contain priority-of-service provisions in accordance with availability requirements (including recovery time objectives) are developed.Site preparation includes establishing configuration settings for systems at the alternate processing site consistent with the requirements for such settings at the primary site and ensuring that essential supplies and logistical considerations are in place.
","uuid":"d45096db-d2b6-45a6-8f44-9e01c930b2cb","family":"Contingency Planning","parameters":[],"subControls":"","tests":[{"testId":"CP-07(04)","uuid":"500e924b-9e64-4c94-878d-acebeecfbc51","test":"Determine if the alternate processing site is prepared so that the site can serve as the operational site supporting essential mission and business functions.There may be situations that preclude an organization from returning to the primary processing site such as if a natural disaster (e.g., flood or a hurricane) damaged or destroyed a facility and it was determined that rebuilding in the same location was not prudent.
","uuid":"cbda236d-a59c-4e1d-8be6-f4333f425608","family":"Contingency Planning","parameters":[],"subControls":"","tests":[{"testId":"CP-07(06)[01]","uuid":"fdd20972-c4b2-42f6-9525-75c8682e5506","test":"Determine if circumstances that preclude returning to the primary processing site are planned for;Telecommunications services (for data and voice) for primary and alternate processing and storage sites are in scope for CP-8 . Alternate telecommunications services reflect the continuity requirements in contingency plans to maintain essential mission and business functions despite the loss of primary telecommunications services. Organizations may specify different time periods for primary or alternate sites. Alternate telecommunications services include additional organizational or commercial ground-based circuits or lines, network-based approaches to telecommunications, or the use of satellites. Organizations consider factors such as availability, quality of service, and access when entering into alternate telecommunications agreements.
","uuid":"0cf6081e-da21-4d58-93d3-b6107dddd06b","family":"Contingency Planning","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"495d96ea-7b15-4b04-9576-cd71ef0a88a8","text":"system operations","parameterId":"cp-08_odp.01","default":" [Assignment: organization defined system operations] "},{"constraints":"","displayName":"","guidance":"","uuid":"642b7995-920c-4351-9ce9-ee67f42e0e52","text":"time period","parameterId":"cp-08_odp.02","default":" [Assignment: organization defined time period] "}],"subControls":"","tests":[{"testId":"CP-08","uuid":"61481589-0d25-440b-ba52-b9bc9f5840af","test":"Determine if alternate telecommunications services, including necessary agreements to permit the resumption of [SELECTED PARAMETER VALUE(S): system operations ] , are established for essential mission and business functions within [SELECTED PARAMETER VALUE(S): time period ] when the primary telecommunications capabilities are unavailable at either the primary or alternate processing or storage sites.Organizations consider the potential mission or business impact in situations where telecommunications service providers are servicing other organizations with similar priority of service provisions. Telecommunications Service Priority (TSP) is a Federal Communications Commission (FCC) program that directs telecommunications service providers (e.g., wireline and wireless phone companies) to give preferential treatment to users enrolled in the program when they need to add new lines or have their lines restored following a disruption of service, regardless of the cause. The FCC sets the rules and policies for the TSP program, and the Department of Homeland Security manages the TSP program. The TSP program is always in effect and not contingent on a major disaster or attack taking place. Federal sponsorship is required to enroll in the TSP program.
","uuid":"e90526c9-3a1e-4f0a-874f-6696b21164ee","family":"Contingency Planning","parameters":[],"subControls":"","tests":[{"testId":"CP-08(01)(a)[01]","uuid":"b16b20d6-9ec7-449e-9bd4-cdec81a27cec","test":"Determine if primary telecommunications service agreements that contain priority-of-service provisions in accordance with availability requirements (including recovery time objectives) are developed;In certain circumstances, telecommunications service providers or services may share the same physical lines, which increases the vulnerability of a single failure point. It is important to have provider transparency for the actual physical transmission capability for telecommunication services.
","uuid":"2d693f38-a182-489e-a8bf-6436e6cc6547","family":"Contingency Planning","parameters":[],"subControls":"","tests":[{"testId":"CP-08(02)","uuid":"ecfb4c04-2899-440a-a151-2435da891952","test":"Determine if alternate telecommunications services to reduce the likelihood of sharing a single point of failure with primary telecommunications services are obtained.Threats that affect telecommunications services are defined in organizational assessments of risk and include natural disasters, structural failures, cyber or physical attacks, and errors of omission or commission. Organizations can reduce common susceptibilities by minimizing shared infrastructure among telecommunications service providers and achieving sufficient geographic separation between services. Organizations may consider using a single service provider in situations where the service provider can provide alternate telecommunications services that meet the separation needs addressed in the risk assessment.
","uuid":"c352a4c6-6265-4c3a-9c88-0c19118cfcb3","family":"Contingency Planning","parameters":[],"subControls":"","tests":[{"testId":"CP-08(03)","uuid":"8051101b-651e-405c-be4c-8bc9887fc01f","test":"Determine if alternate telecommunications services from providers that are separated from primary service providers are obtained to reduce susceptibility to the same threats.Reviews of provider contingency plans consider the proprietary nature of such plans. In some situations, a summary of provider contingency plans may be sufficient evidence for organizations to satisfy the review requirement. Telecommunications service providers may also participate in ongoing disaster recovery exercises in coordination with the Department of Homeland Security and state and local governments. Organizations may use these types of activities to satisfy evidentiary requirements related to service provider contingency plan reviews, testing, and training.
","uuid":"77494e22-82ca-46b7-9c1e-f46f3e6e4b90","family":"Contingency Planning","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"d95f091e-ad73-48e9-9704-e1a4c2d4453d","text":"organization-defined frequency","parameterId":"cp-8.4_prm_1","default":" [Assignment: organization-defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"e5820300-7ad8-4885-8867-687ba98a935a","text":"frequency","parameterId":"cp-08.04_odp.01","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"c34d5a63-174f-4aa7-9cbb-81bb8eb415a5","text":"frequency","parameterId":"cp-08.04_odp.02","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"CP-08(04)(a)[01]","uuid":"14f8820f-a2c3-43c6-8049-20ce95af619b","test":"Determine if primary telecommunications service providers are required to have contingency plans;Alternate telecommunications services testing is arranged through contractual agreements with service providers. The testing may occur in parallel with normal operations to ensure that there is no degradation in organizational missions or functions.
","uuid":"12e9c992-f36d-4962-93fe-d594dcf72d0f","family":"Contingency Planning","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"e6f6b717-e3db-4717-8c92-32592e5274c4","text":"frequency","parameterId":"cp-08.05_odp","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"CP-08(05)","uuid":"c99ed971-63e7-4d75-911f-3577e2dfc2b3","test":"Determine if alternate telecommunications services are tested [SELECTED PARAMETER VALUE(S): frequency ].System-level information includes system state information, operating system software, middleware, application software, and licenses. User-level information includes information other than system-level information. Mechanisms employed to protect the integrity of system backups include digital signatures and cryptographic hashes. Protection of system backup information while in transit is addressed by MP-5 and SC-8 . System backups reflect the requirements in contingency plans as well as other organizational requirements for backing up information. Organizations may be subject to laws, executive orders, directives, regulations, or policies with requirements regarding specific categories of information (e.g., personal health information). Organizational personnel consult with the senior agency official for privacy and legal counsel regarding such requirements.
","uuid":"e3c05e26-3237-4af9-a86b-35a7cee2589d","family":"Contingency Planning","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"5515d9f7-b5ae-4e3e-bead-0cb5699b186b","text":"system components","parameterId":"cp-09_odp.01","default":" [Assignment: organization defined system components] "},{"constraints":"","displayName":"","guidance":"","uuid":"145ffc27-c9dd-42c9-9c70-74ae97584c83","text":"frequency","parameterId":"cp-09_odp.02","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"b25dc169-6839-4b76-9278-ea46467b2a83","text":"frequency","parameterId":"cp-09_odp.03","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"00c0a94a-41ac-4cf1-97ea-5dc8bedd9d17","text":"frequency","parameterId":"cp-09_odp.04","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"CP-09a.","uuid":"33449a20-f76b-4ab8-a8a5-36551db9d193","test":"Determine if backups of user-level information contained in [SELECTED PARAMETER VALUE(S): system components ] are conducted [SELECTED PARAMETER VALUE(S): frequency ];Organizations need assurance that backup information can be reliably retrieved. Reliability pertains to the systems and system components where the backup information is stored, the operations used to retrieve the information, and the integrity of the information being retrieved. Independent and specialized tests can be used for each of the aspects of reliability. For example, decrypting and transporting (or transmitting) a random sample of backup files from the alternate storage or backup site and comparing the information to the same information at the primary processing site can provide such assurance.
","uuid":"ad948a88-06bb-448c-98c6-aeeebc778ffc","family":"Contingency Planning","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"24d47801-4a6e-41a0-bcfa-22103252b4cf","text":"organization-defined frequency","parameterId":"cp-9.1_prm_1","default":" [Assignment: organization-defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"b33fb1aa-33f6-4aad-9d64-7926c01bbd3c","text":"frequency","parameterId":"cp-09.01_odp.01","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"78932a06-c887-41d0-817f-7465ae7ec74f","text":"frequency","parameterId":"cp-09.01_odp.02","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"CP-09(01)[01]","uuid":"c055c6d7-8a8a-43cd-ade1-b6b46151a0da","test":"Determine if backup information is tested [SELECTED PARAMETER VALUE(S): frequency ] to verify media reliability;Organizations need assurance that system functions can be restored correctly and can support established organizational missions. To ensure that the selected system functions are thoroughly exercised during contingency plan testing, a sample of backup information is retrieved to determine whether the functions are operating as intended. Organizations can determine the sample size for the functions and backup information based on the level of assurance needed.
","uuid":"364bdf18-d977-4202-91ac-b866e24b58c1","family":"Contingency Planning","parameters":[],"subControls":"","tests":[{"testId":"CP-09(02)","uuid":"03864723-4821-4fcc-ad3a-f67a8c1b34d7","test":"Determine if a sample of backup information in the restoration of selected system functions is used as part of contingency plan testing.Separate storage for critical information applies to all critical information regardless of the type of backup storage media. Critical system software includes operating systems, middleware, cryptographic key management systems, and intrusion detection systems. Security-related information includes inventories of system hardware, software, and firmware components. Alternate storage sites, including geographically distributed architectures, serve as separate storage facilities for organizations. Organizations may provide separate storage by implementing automated backup processes at alternative storage sites (e.g., data centers). The General Services Administration (GSA) establishes standards and specifications for security and fire rated containers.
","uuid":"c1dfcede-0c79-4930-9568-73906959c314","family":"Contingency Planning","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"721bd2f1-7655-446e-a9b0-67b0cb6e1a4b","text":"critical system software and other security-related information","parameterId":"cp-09.03_odp","default":" [Assignment: organization defined critical system software and other security-related information] "}],"subControls":"","tests":[{"testId":"CP-09(03)","uuid":"1c9aaa94-ba44-4172-8e73-e065223423f6","test":"Determine if backup copies of [SELECTED PARAMETER VALUE(S): critical system software and other security-related information ] are stored in a separate facility or in a fire rated container that is not collocated with the operational system.System backup information can be transferred to alternate storage sites either electronically or by the physical shipment of storage media.
","uuid":"3432c42a-7cfa-4ced-89c3-086d89340b00","family":"Contingency Planning","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"6344e9f3-ea32-4418-b176-ba94d097758e","text":"organization-defined time period and transfer rate consistent with the recovery time and recovery point objectives","parameterId":"cp-9.5_prm_1","default":" [Assignment: organization-defined time period and transfer rate consistent with the recovery time and recovery point objectives] "},{"constraints":"","displayName":"","guidance":"","uuid":"0677ea64-41cb-40d2-8b77-ac71eac4df63","text":"time period","parameterId":"cp-09.05_odp.01","default":" [Assignment: organization defined time period] "},{"constraints":"","displayName":"","guidance":"","uuid":"477f0fd6-c120-498c-b1bb-89d61cd45afc","text":"transfer rate","parameterId":"cp-09.05_odp.02","default":" [Assignment: organization defined transfer rate] "}],"subControls":"","tests":[{"testId":"CP-09(05)[01]","uuid":"46f3a575-56ed-48a4-9bdc-97fd376edcc8","test":"Determine if system backup information is transferred to the alternate storage site for [SELECTED PARAMETER VALUE(S): time period ];The effect of system backup can be achieved by maintaining a redundant secondary system that mirrors the primary system, including the replication of information. If this type of redundancy is in place and there is sufficient geographic separation between the two systems, the secondary system can also serve as the alternate processing site.
","uuid":"0a2417f9-3033-4d7d-8442-dafd38e607e6","family":"Contingency Planning","parameters":[],"subControls":"","tests":[{"testId":"CP-09(06)[01]","uuid":"f69c12db-174d-42b8-87d3-e9ca2f3a3d96","test":"Determine if system backup is conducted by maintaining a redundant secondary system that is not collocated with the primary system;Dual authorization ensures that deletion or destruction of backup information cannot occur unless two qualified individuals carry out the task. Individuals deleting or destroying backup information possess the skills or expertise to determine if the proposed deletion or destruction of information reflects organizational policies and procedures. Dual authorization may also be known as two-person control. To reduce the risk of collusion, organizations consider rotating dual authorization duties to other individuals.
","uuid":"7b94b949-3053-41cc-8e0d-6657781e9b88","family":"Contingency Planning","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"9467414b-bac4-4fa3-8d6f-32f7dee6a510","text":"backup information","parameterId":"cp-09.07_odp","default":" [Assignment: organization defined backup information] "}],"subControls":"","tests":[{"testId":"CP-09(07)","uuid":"7626cbc1-1e96-4f36-9f31-3e842133ab73","test":"Determine if dual authorization for the deletion or destruction of [SELECTED PARAMETER VALUE(S): backup information ] is enforced.The selection of cryptographic mechanisms is based on the need to protect the confidentiality and integrity of backup information. The strength of mechanisms selected is commensurate with the security category or classification of the information. Cryptographic protection applies to system backup information in storage at both primary and alternate locations. Organizations that implement cryptographic mechanisms to protect information at rest also consider cryptographic key management solutions.
","uuid":"2dc19ce4-a493-4333-9509-61d3c05ab83d","family":"Contingency Planning","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"581937f3-b9a7-4aec-bb70-0da40212450f","text":"backup information","parameterId":"cp-09.08_odp","default":" [Assignment: organization defined backup information] "}],"subControls":"","tests":[{"testId":"CP-09(08)","uuid":"6fb6c817-9b04-4fbf-8237-d7e3fb530c6f","test":"Determine if cryptographic mechanisms are implemented to prevent unauthorized disclosure and modification of [SELECTED PARAMETER VALUE(S): backup information ].Recovery is executing contingency plan activities to restore organizational mission and business functions. Reconstitution takes place following recovery and includes activities for returning systems to fully operational states. Recovery and reconstitution operations reflect mission and business priorities; recovery point, recovery time, and reconstitution objectives; and organizational metrics consistent with contingency plan requirements. Reconstitution includes the deactivation of interim system capabilities that may have been needed during recovery operations. Reconstitution also includes assessments of fully restored system capabilities, reestablishment of continuous monitoring activities, system reauthorization (if required), and activities to prepare the system and organization for future disruptions, breaches, compromises, or failures. Recovery and reconstitution capabilities can include automated mechanisms and manual procedures. Organizations establish recovery time and recovery point objectives as part of contingency planning.
","uuid":"0e203621-efba-447c-9220-01f71e380b63","family":"Contingency Planning","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"b7515ffc-f184-47b4-a010-f2ac55f95a7b","text":"organization-defined time period consistent with recovery time and recovery point objectives","parameterId":"cp-10_prm_1","default":" [Assignment: organization-defined time period consistent with recovery time and recovery point objectives] "},{"constraints":"","displayName":"","guidance":"","uuid":"aa142c8c-45bc-45c8-8df3-79a24b7ff41e","text":"time period","parameterId":"cp-10_odp.01","default":" [Assignment: organization defined time period] "},{"constraints":"","displayName":"","guidance":"","uuid":"886960b7-eb4b-4478-abe4-692d48d4fd80","text":"time period","parameterId":"cp-10_odp.02","default":" [Assignment: organization defined time period] "}],"subControls":"","tests":[{"testId":"CP-10[01]","uuid":"ed89941d-c326-457a-9dba-ed8f814f260c","test":"Determine if the recovery of the system to a known state is provided within [SELECTED PARAMETER VALUE(S): time period ] after a disruption, compromise, or failure;Transaction-based systems include database management systems and transaction processing systems. Mechanisms supporting transaction recovery include transaction rollback and transaction journaling.
","uuid":"ff89b99d-d035-4cb6-91c2-c8cce488edaf","family":"Contingency Planning","parameters":[],"subControls":"","tests":[{"testId":"CP-10(02)","uuid":"dfbbf885-dea7-4ce6-9dea-568b0f1a5c6b","test":"Determine if transaction recovery is implemented for systems that are transaction-based.Restoration of system components includes reimaging, which restores the components to known, operational states.
","uuid":"456d4f2b-1ae7-418a-b7f3-7fe73fd38910","family":"Contingency Planning","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"63e28fca-b3c4-45e6-a962-f022201a9ee5","text":"restoration time periods","parameterId":"cp-10.04_odp","default":" [Assignment: organization defined restoration time periods] "}],"subControls":"","tests":[{"testId":"CP-10(04)","uuid":"6bc07340-036a-4542-ae51-c85177c5ff9e","test":"Determine if the capability to restore system components within [SELECTED PARAMETER VALUE(S): restoration time periods ] from configuration-controlled and integrity-protected information representing a known, operational state for the components is provided.Protection of system recovery and reconstitution components (i.e., hardware, firmware, and software) includes physical and technical controls. Backup and restoration components used for recovery and reconstitution include router tables, compilers, and other system software.
","uuid":"4d077572-4187-40e1-973d-6ab1baf31487","family":"Contingency Planning","parameters":[],"subControls":"","tests":[{"testId":"CP-10(06)","uuid":"af75ecda-4713-4bd6-b950-71ff0ad39bdd","test":"Determine if system components used for recovery and reconstitution are protected.Contingency plans and the contingency training or testing associated with those plans incorporate an alternate communications protocol capability as part of establishing resilience in organizational systems. Switching communications protocols may affect software applications and operational aspects of systems. Organizations assess the potential side effects of introducing alternate communications protocols prior to implementation.
","uuid":"9a646d09-482b-4992-b0c4-712a1bb1566d","family":"Contingency Planning","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"d44c11c5-55e9-4be8-a678-a9a74a5bad94","text":"alternative communications protocols","parameterId":"cp-11_odp","default":" [Assignment: organization defined alternative communications protocols] "}],"subControls":"","tests":[{"testId":"CP-11","uuid":"959f0d71-edd8-45f5-881a-a4e128032eb4","test":"Determine if the capability to employ [SELECTED PARAMETER VALUE(S): alternative communications protocols ] are provided in support of maintaining continuity of operations.For systems that support critical mission and business functions—including military operations, civilian space operations, nuclear power plant operations, and air traffic control operations (especially real-time operational environments)—organizations can identify certain conditions under which those systems revert to a predefined safe mode of operation. The safe mode of operation, which can be activated either automatically or manually, restricts the operations that systems can execute when those conditions are encountered. Restriction includes allowing only selected functions to execute that can be carried out under limited power or with reduced communications bandwidth.
","uuid":"3a04d244-6cad-46c2-bdab-2e1cca8c5a36","family":"Contingency Planning","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"77753dad-1279-49dc-bdf1-27491fd2eb5a","text":"restrictions","parameterId":"cp-12_odp.01","default":" [Assignment: organization defined restrictions] "},{"constraints":"","displayName":"","guidance":"","uuid":"17c77424-bac5-4419-addc-dee8a87bc990","text":"conditions","parameterId":"cp-12_odp.02","default":" [Assignment: organization defined conditions] "}],"subControls":"","tests":[{"testId":"CP-12","uuid":"b943e626-ca21-4f38-a5b1-e77a5adfa5a4","test":"Determine if a safe mode of operation is entered with [SELECTED PARAMETER VALUE(S): restrictions ] when [SELECTED PARAMETER VALUE(S): conditions ] are detected.Use of alternative security mechanisms supports system resiliency, contingency planning, and continuity of operations. To ensure mission and business continuity, organizations can implement alternative or supplemental security mechanisms. The mechanisms may be less effective than the primary mechanisms. However, having the capability to readily employ alternative or supplemental mechanisms enhances mission and business continuity that might otherwise be adversely impacted if operations had to be curtailed until the primary means of implementing the functions was restored. Given the cost and level of effort required to provide such alternative capabilities, the alternative or supplemental mechanisms are only applied to critical security capabilities provided by systems, system components, or system services. For example, an organization may issue one-time pads to senior executives, officials, and system administrators if multi-factor tokens—the standard means for achieving secure authentication— are compromised.
","uuid":"91fedf39-dc69-4623-bc81-96178a186902","family":"Contingency Planning","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"bddffed5-afe4-4b8b-b0bf-defef22e1cc0","text":"alternative or supplemental security mechanisms","parameterId":"cp-13_odp.01","default":" [Assignment: organization defined alternative or supplemental security mechanisms] "},{"constraints":"","displayName":"","guidance":"","uuid":"3dd58b0e-9a37-43f9-b594-007015ccd848","text":"security functions","parameterId":"cp-13_odp.02","default":" [Assignment: organization defined security functions] "}],"subControls":"","tests":[{"testId":"CP-13","uuid":"127170c0-307b-4345-92e2-26e59b4d02cc","test":"Determine if [SELECTED PARAMETER VALUE(S): alternative or supplemental security mechanisms ] are employed for satisfying [SELECTED PARAMETER VALUE(S): security functions ] when the primary means of implementing the security function is unavailable or compromised.Identification and authentication policy and procedures address the controls in the IA family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of identification and authentication policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission or business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to identification and authentication policy and procedures include assessment or audit findings, security incidents or breaches, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure.
","uuid":"6206d1fe-7f59-408d-a7a5-369c93c55701","family":"Identification and Authentication","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"ccca78cc-835b-4620-bb89-738670e80ae5","text":"organization-defined personnel or roles","parameterId":"ia-1_prm_1","default":" [Assignment: organization-defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"e8f3e7d7-47a6-414d-9c4c-f24f30212398","text":"personnel or roles","parameterId":"ia-01_odp.01","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"cf9b52ea-39b0-486f-93fa-667228a2eeba","text":"personnel or roles","parameterId":"ia-01_odp.02","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"14ac8064-7bf7-4c64-a935-0b4497185ff0","text":"[Selection (one or more): organization-level; mission/business process-level; system-level]","parameterId":"ia-01_odp.03","default":"[Selection (one or more): organization-level; mission/business process-level; system-level]"},{"constraints":"","displayName":"","guidance":"","uuid":"e1f8eb33-e012-439b-82ad-e7fc5766a554","text":"official","parameterId":"ia-01_odp.04","default":" [Assignment: organization defined official] "},{"constraints":"","displayName":"","guidance":"","uuid":"db4b084d-7041-489c-81cd-a802f4a0eefc","text":"frequency","parameterId":"ia-01_odp.05","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"f5d8c271-55c0-4b59-ba1a-c6388edd6cf9","text":"events","parameterId":"ia-01_odp.06","default":" [Assignment: organization defined events] "},{"constraints":"","displayName":"","guidance":"","uuid":"4ed096bd-c20b-47b0-a6c7-d0e6b4595137","text":"frequency","parameterId":"ia-01_odp.07","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"8f9d3861-2d6d-44e7-830a-4c4ea7dbad62","text":"events","parameterId":"ia-01_odp.08","default":" [Assignment: organization defined events] "}],"subControls":"","tests":[{"testId":"IA-01a.[01]","uuid":"46bfa0c1-256d-4a1a-884a-adf3a8095779","test":"Determine if an identification and authentication policy is developed and documented;Organizations can satisfy the identification and authentication requirements by complying with the requirements in HSPD 12 . Organizational users include employees or individuals who organizations consider to have an equivalent status to employees (e.g., contractors and guest researchers). Unique identification and authentication of users applies to all accesses other than those that are explicitly identified in AC-14 and that occur through the authorized use of group authenticators without individual authentication. Since processes execute on behalf of groups and roles, organizations may require unique identification of individuals in group accounts or for detailed accountability of individual activity.
Organizations employ passwords, physical authenticators, or biometrics to authenticate user identities or, in the case of multi-factor authentication, some combination thereof. Access to organizational systems is defined as either local access or network access. Local access is any access to organizational systems by users or processes acting on behalf of users, where access is obtained through direct connections without the use of networks. Network access is access to organizational systems by users (or processes acting on behalf of users) where access is obtained through network connections (i.e., nonlocal accesses). Remote access is a type of network access that involves communication through external networks. Internal networks include local area networks and wide area networks.
The use of encrypted virtual private networks for network connections between organization-controlled endpoints and non-organization-controlled endpoints may be treated as internal networks with respect to protecting the confidentiality and integrity of information traversing the network. Identification and authentication requirements for non-organizational users are described in IA-8.
","uuid":"9f1bf6d4-96fc-41f0-ab17-b654e3a9433f","family":"Identification and Authentication","parameters":[],"subControls":"","tests":[{"testId":"IA-02[01]","uuid":"e90e9e80-851c-4252-9d7f-9b8e8c5b01fc","test":"Determine if organizational users are uniquely identified and authenticated;Multi-factor authentication requires the use of two or more different factors to achieve authentication. The authentication factors are defined as follows: something you know (e.g., a personal identification number [PIN]), something you have (e.g., a physical authenticator such as a cryptographic private key), or something you are (e.g., a biometric). Multi-factor authentication solutions that feature physical authenticators include hardware authenticators that provide time-based or challenge-response outputs and smart cards such as the U.S. Government Personal Identity Verification (PIV) card or the Department of Defense (DoD) Common Access Card (CAC). In addition to authenticating users at the system level (i.e., at logon), organizations may employ authentication mechanisms at the application level, at their discretion, to provide increased security. Regardless of the type of access (i.e., local, network, remote), privileged accounts are authenticated using multi-factor options appropriate for the level of risk. Organizations can add additional security measures, such as additional or more rigorous authentication mechanisms, for specific types of access.
","uuid":"d8698082-5396-4cec-8c63-405b49d13027","family":"Identification and Authentication","parameters":[],"subControls":"","tests":[{"testId":"IA-02(01)","uuid":"0a66dca4-e278-46ec-8878-c40f71dbc217","test":"Determine if multi-factor authentication is implemented for access to privileged accounts.Multi-factor authentication requires the use of two or more different factors to achieve authentication. The authentication factors are defined as follows: something you know (e.g., a personal identification number [PIN]), something you have (e.g., a physical authenticator such as a cryptographic private key), or something you are (e.g., a biometric). Multi-factor authentication solutions that feature physical authenticators include hardware authenticators that provide time-based or challenge-response outputs and smart cards such as the U.S. Government Personal Identity Verification card or the DoD Common Access Card. In addition to authenticating users at the system level, organizations may also employ authentication mechanisms at the application level, at their discretion, to provide increased information security. Regardless of the type of access (i.e., local, network, remote), non-privileged accounts are authenticated using multi-factor options appropriate for the level of risk. Organizations can provide additional security measures, such as additional or more rigorous authentication mechanisms, for specific types of access.
","uuid":"35dd7494-16d7-4dc0-a0ac-2ab827305a1d","family":"Identification and Authentication","parameters":[],"subControls":"","tests":[{"testId":"IA-02(02)","uuid":"85efebf4-c615-472b-a523-8e6a59d870d8","test":"Determine if multi-factor authentication for access to non-privileged accounts is implemented.Individual authentication prior to shared group authentication mitigates the risk of using group accounts or authenticators.
","uuid":"dd7fa49d-3dda-4168-8f87-d75b41fe0f52","family":"Identification and Authentication","parameters":[],"subControls":"","tests":[{"testId":"IA-02(05)","uuid":"b4456ebd-7dac-4a2f-b63b-a1990ba5abd2","test":"Determine if users are required to be individually authenticated before granting access to the shared accounts or resources when shared accounts or authenticators are employed.The purpose of requiring a device that is separate from the system to which the user is attempting to gain access for one of the factors during multi-factor authentication is to reduce the likelihood of compromising authenticators or credentials stored on the system. Adversaries may be able to compromise such authenticators or credentials and subsequently impersonate authorized users. Implementing one of the factors on a separate device (e.g., a hardware token), provides a greater strength of mechanism and an increased level of assurance in the authentication process.
","uuid":"4f07f97a-07db-40fb-94e3-a8ec79443e68","family":"Identification and Authentication","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"0dc765bb-dd68-414e-a637-669dede0b759","text":"[Selection (one or more): local; network; remote]","parameterId":"ia-02.06_odp.01","default":"[Selection (one or more): local; network; remote]"},{"constraints":"","displayName":"","guidance":"","uuid":"002195b2-367a-44a2-b355-183377f2c3a4","text":"[Selection (one or more): privileged accounts; non-privileged accounts]","parameterId":"ia-02.06_odp.02","default":"[Selection (one or more): privileged accounts; non-privileged accounts]"},{"constraints":"","displayName":"","guidance":"","uuid":"e2f625f1-8354-4935-a35d-e0e4d8f7b226","text":"strength of mechanism requirements","parameterId":"ia-02.06_odp.03","default":" [Assignment: organization defined strength of mechanism requirements] "}],"subControls":"","tests":[{"testId":"IA-02(06)(a)","uuid":"a8ae5f47-fb1b-4d9e-ac51-037be650655f","test":"Determine if multi-factor authentication is implemented for [SELECTED PARAMETER VALUE(S): [Selection (one or more): local; network; remote] ] access to [SELECTED PARAMETER VALUE(S): [Selection (one or more): privileged accounts; non-privileged accounts] ] such that one of the factors is provided by a device separate from the system gaining access;Authentication processes resist replay attacks if it is impractical to achieve successful authentications by replaying previous authentication messages. Replay-resistant techniques include protocols that use nonces or challenges such as time synchronous or cryptographic authenticators.
","uuid":"e059a8f1-9b70-40a8-8a7a-fa26eb982945","family":"Identification and Authentication","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"59f00c58-dff0-46c7-90cd-6e5d7cd98bfb","text":"[Selection (one or more): privileged accounts; non-privileged accounts]","parameterId":"ia-02.08_odp","default":"[Selection (one or more): privileged accounts; non-privileged accounts]"}],"subControls":"","tests":[{"testId":"IA-02(08)","uuid":"b85e89e1-b89f-4bfb-a49e-49554a1b4c82","test":"Determine if replay-resistant authentication mechanisms for access to [SELECTED PARAMETER VALUE(S): [Selection (one or more): privileged accounts; non-privileged accounts] ] are implemented.Single sign-on enables users to log in once and gain access to multiple system resources. Organizations consider the operational efficiencies provided by single sign-on capabilities with the risk introduced by allowing access to multiple systems via a single authentication event. Single sign-on can present opportunities to improve system security, for example by providing the ability to add multi-factor authentication for applications and systems (existing and new) that may not be able to natively support multi-factor authentication.
","uuid":"00855d3b-7914-4dc6-8630-790ef0551e26","family":"Identification and Authentication","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"f73d7a22-01a5-4a15-a984-159bafdc8c0a","text":"system accounts and services","parameterId":"ia-02.10_odp","default":" [Assignment: organization defined system accounts and services] "}],"subControls":"","tests":[{"testId":"IA-02(10)","uuid":"3ab0ec06-a8e0-423b-9dfd-ae0716606b25","test":"Determine if a single sign-on capability is provided for [SELECTED PARAMETER VALUE(S): system accounts and services ].Acceptance of Personal Identity Verification (PIV)-compliant credentials applies to organizations implementing logical access control and physical access control systems. PIV-compliant credentials are those credentials issued by federal agencies that conform to FIPS Publication 201 and supporting guidance documents. The adequacy and reliability of PIV card issuers are authorized using SP 800-79-2 . Acceptance of PIV-compliant credentials includes derived PIV credentials, the use of which is addressed in SP 800-166 . The DOD Common Access Card (CAC) is an example of a PIV credential.
","uuid":"0c548ef3-2a5a-4b44-ae7c-95c45ec7de8b","family":"Identification and Authentication","parameters":[],"subControls":"","tests":[{"testId":"IA-02(12)","uuid":"5979b84e-9607-4943-86af-e3fcee0b7f67","test":"Determine if personal identity verification-compliant credentials are accepted and electronically verified.Out-of-band authentication refers to the use of two separate communication paths to identify and authenticate users or devices to an information system. The first path (i.e., the in-band path) is used to identify and authenticate users or devices and is generally the path through which information flows. The second path (i.e., the out-of-band path) is used to independently verify the authentication and/or requested action. For example, a user authenticates via a notebook computer to a remote server to which the user desires access and requests some action of the server via that communication path. Subsequently, the server contacts the user via the user’s cell phone to verify that the requested action originated from the user. The user may confirm the intended action to an individual on the telephone or provide an authentication code via the telephone. Out-of-band authentication can be used to mitigate actual or suspected man-in the-middle
attacks. The conditions or criteria for activation include suspicious activities, new threat indicators, elevated threat levels, or the impact or classification level of information in requested transactions.
Devices that require unique device-to-device identification and authentication are defined by type, device, or a combination of type and device. Organization-defined device types include devices that are not owned by the organization. Systems use shared known information (e.g., Media Access Control [MAC], Transmission Control Protocol/Internet Protocol [TCP/IP] addresses) for device identification or organizational authentication solutions (e.g., Institute of Electrical and Electronics Engineers (IEEE) 802.1x and Extensible Authentication Protocol [EAP], RADIUS server with EAP-Transport Layer Security [TLS] authentication, Kerberos) to identify and authenticate devices on local and wide area networks. Organizations determine the required strength of authentication mechanisms based on the security categories of systems and mission or business requirements. Because of the challenges of implementing device authentication on a large scale, organizations can restrict the application of the control to a limited number/type of devices based on mission or business needs.
","uuid":"0884bbd7-fed6-48a5-9517-dd80fff49996","family":"Identification and Authentication","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"92be5891-9472-4319-8870-d15d16bbbe6a","text":"devices and/or types of devices","parameterId":"ia-03_odp.01","default":" [Assignment: organization defined devices and/or types of devices] "},{"constraints":"","displayName":"","guidance":"","uuid":"bfbbfe27-c6f4-46f7-a790-47adcf7e4998","text":"[Selection (one or more): local; remote; network]","parameterId":"ia-03_odp.02","default":"[Selection (one or more): local; remote; network]"}],"subControls":"","tests":[{"testId":"IA-03","uuid":"f05333b2-0343-456d-a8fe-87eec327af51","test":"Determine if [SELECTED PARAMETER VALUE(S): devices and/or types of devices ] are uniquely identified and authenticated before establishing a [SELECTED PARAMETER VALUE(S): [Selection (one or more): local; remote; network] ] connection.A local connection is a connection with a device that communicates without the use of a network. A network connection is a connection with a device that communicates through a network. A remote connection is a connection with a device that communicates through an external network. Bidirectional authentication provides stronger protection to validate the identity of other devices for connections that are of greater risk.
","uuid":"655653fe-19ca-4f1d-a4bc-a22bd0b19fe7","family":"Identification and Authentication","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"28a55c2f-d030-4064-812a-9563e3508563","text":"devices and/or types of devices","parameterId":"ia-03.01_odp.01","default":" [Assignment: organization defined devices and/or types of devices] "},{"constraints":"","displayName":"","guidance":"","uuid":"e7d4cd5a-1524-45c6-a7bd-1633cfb05472","text":"[Selection (one or more): local; remote; network]","parameterId":"ia-03.01_odp.02","default":"[Selection (one or more): local; remote; network]"}],"subControls":"","tests":[{"testId":"IA-03(01)","uuid":"b2eebf3f-4887-4067-a5e3-aceaae63b4f3","test":"Determine if [SELECTED PARAMETER VALUE(S): devices and/or types of devices ] are authenticated before establishing [SELECTED PARAMETER VALUE(S): [Selection (one or more): local; remote; network] ] connection using bidirectional authentication that is cryptographically based.The Dynamic Host Configuration Protocol (DHCP) is an example of a means by which clients can dynamically receive network address assignments.
","uuid":"041caaaf-fd03-42dc-acd4-bbccc753fa9d","family":"Identification and Authentication","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"cddfebb3-4ff7-453b-acaa-dd7af8913a94","text":"organization-defined lease information and lease duration","parameterId":"ia-3.3_prm_1","default":" [Assignment: organization-defined lease information and lease duration] "},{"constraints":"","displayName":"","guidance":"","uuid":"1f2d7b08-dde3-456e-ab98-51a5feaef342","text":"lease information","parameterId":"ia-03.03_odp.01","default":" [Assignment: organization defined lease information] "},{"constraints":"","displayName":"","guidance":"","uuid":"819870cb-967f-416e-a8dc-98060467400e","text":"lease duration","parameterId":"ia-03.03_odp.02","default":" [Assignment: organization defined lease duration] "}],"subControls":"","tests":[{"testId":"IA-03(03)(a)[01]","uuid":"d7bcb807-d9a5-4938-afec-1e8f1e16ffc6","test":"Determine if dynamic address allocation lease information assigned to devices where addresses are allocated dynamically are standardized in accordance with [SELECTED PARAMETER VALUE(S): lease information ];Device attestation refers to the identification and authentication of a device based on its configuration and known operating state. Device attestation can be determined via a cryptographic hash of the device. If device attestation is the means of identification and authentication, then it is important that patches and updates to the device are handled via a configuration management process such that the patches and updates are done securely and do not disrupt identification and authentication to other devices.
","uuid":"b5d87dca-b41c-445e-8c68-a3f9e8df3f1f","family":"Identification and Authentication","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"897bec89-d423-4ff6-97aa-8de25392f125","text":"configuration management process","parameterId":"ia-03.04_odp","default":" [Assignment: organization defined configuration management process] "}],"subControls":"","tests":[{"testId":"IA-03(04)","uuid":"5a245521-7563-429a-ac09-c9348cd7d43f","test":"Determine if device identification and authentication are handled based on attestation by [SELECTED PARAMETER VALUE(S): configuration management process ].Common device identifiers include Media Access Control (MAC) addresses, Internet Protocol (IP) addresses, or device-unique token identifiers. The management of individual identifiers is not applicable to shared system accounts. Typically, individual identifiers are the usernames of the system accounts assigned to those individuals. In such instances, the account management activities of AC-2 use account names provided by IA-4 . Identifier management also addresses individual identifiers not necessarily associated with system accounts. Preventing the reuse of identifiers implies preventing the assignment of previously used individual, group, role, service, or device identifiers to different individuals, groups, roles, services, or devices.
","uuid":"6d5273a3-3a3d-44c7-ae8c-5c0b8a10afb8","family":"Identification and Authentication","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"9744a7de-37d8-4f08-afc5-e3bbae3b53e0","text":"personnel or roles","parameterId":"ia-04_odp.01","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"092740a7-fe25-4648-84db-e3edef8904ff","text":"time period","parameterId":"ia-04_odp.02","default":" [Assignment: organization defined time period] "}],"subControls":"","tests":[{"testId":"IA-04a.","uuid":"37c0de7c-8297-428e-90a6-3f92b99fd74e","test":"Determine if system identifiers are managed by receiving authorization from [SELECTED PARAMETER VALUE(S): personnel or roles ] to assign to an individual, group, role, or device identifier;Prohibiting account identifiers as public identifiers applies to any publicly disclosed account identifier used for communication such as, electronic mail and instant messaging. Prohibiting the use of systems account identifiers that are the same as some public identifier, such as the individual identifier section of an electronic mail address, makes it more difficult for adversaries to guess user identifiers. Prohibiting account identifiers as public identifiers without the implementation of other supporting controls only complicates guessing of identifiers. Additional protections are required for authenticators and credentials to protect the account.
","uuid":"e1ff3170-4ab0-47fb-bc27-4690282b79a2","family":"Identification and Authentication","parameters":[],"subControls":"","tests":[{"testId":"IA-04(01)","uuid":"61202f01-427c-49a6-84b8-d7f11273752f","test":"Determine if the use of system account identifiers that are the same as public identifiers is prohibited for individual accounts.Characteristics that identify the status of individuals include contractors, foreign nationals, and non-organizational users. Identifying the status of individuals by these characteristics provides additional information about the people with whom organizational personnel are communicating. For example, it might be useful for a government employee to know that one of the individuals on an email message is a contractor.
","uuid":"db09a18c-9d35-46ac-a5cd-c12a067c780d","family":"Identification and Authentication","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"714e620e-6c81-42e8-b673-318de88024f1","text":"characteristics","parameterId":"ia-04.04_odp","default":" [Assignment: organization defined characteristics] "}],"subControls":"","tests":[{"testId":"IA-04(04)","uuid":"d1efe3b6-cea3-420e-9bea-cb4e6b6c9351","test":"Determine if individual identifiers are managed by uniquely identifying each individual as [SELECTED PARAMETER VALUE(S): characteristics ].In contrast to conventional approaches to identification that presume static accounts for preregistered users, many distributed systems establish identifiers at runtime for entities that were previously unknown. When identifiers are established at runtime for previously unknown entities, organizations can anticipate and provision for the dynamic establishment of identifiers. Pre-established trust relationships and mechanisms with appropriate authorities to validate credentials and related identifiers are essential.
","uuid":"05d69b2e-b06e-4251-98d6-ad7c989b14ca","family":"Identification and Authentication","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"464082a3-d0d5-4b40-a4dd-6ff963c3c163","text":"dynamic identifier policy","parameterId":"ia-04.05_odp","default":" [Assignment: organization defined dynamic identifier policy] "}],"subControls":"","tests":[{"testId":"IA-04(05)","uuid":"d94ad180-1266-492c-9b7e-112ef0a4a841","test":"Determine if individual identifiers are dynamically managed in accordance with [SELECTED PARAMETER VALUE(S): dynamic identifier policy ].Cross-organization identifier management provides the capability to identify individuals, groups, roles, or devices when conducting cross-organization activities involving the processing, storage, or transmission of information.
","uuid":"e2c2ef12-2b20-486b-9d68-3da93741bfdf","family":"Identification and Authentication","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"c896c06b-ea7a-42f0-b6cf-3463d85386d0","text":"external organizations","parameterId":"ia-04.06_odp","default":" [Assignment: organization defined external organizations] "}],"subControls":"","tests":[{"testId":"IA-04(06)","uuid":"dca98f47-8b6a-4d6f-8742-830cda0cb460","test":"Determine if cross-organization management of identifiers is coordinated with [SELECTED PARAMETER VALUE(S): external organizations ].A pairwise pseudonymous identifier is an opaque unguessable subscriber identifier generated by an identity provider for use at a specific individual relying party. Generating distinct pairwise pseudonymous identifiers with no identifying information about a subscriber discourages subscriber activity tracking and profiling beyond the operational requirements established by an organization. The pairwise pseudonymous identifiers are unique to each relying party except in situations where relying parties can show a demonstrable relationship justifying an operational need for correlation, or all parties consent to being correlated in such a manner.
","uuid":"94c07305-8179-4d8f-841d-515b7fe8fdd9","family":"Identification and Authentication","parameters":[],"subControls":"","tests":[{"testId":"IA-04(08)","uuid":"54c8c97b-047e-4524-80fe-57d29a4fbd49","test":"Determine if pairwise pseudonymous identifiers are generated.For each of the entities covered in IA-2, IA-3, IA-8 , and IA-9 , it is important to maintain the attributes for each authenticated entity on an ongoing basis in a central (protected) store.
","uuid":"b524ed28-5121-4bc5-831c-bb7468ad7a21","family":"Identification and Authentication","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"ff6a171c-7888-4a5d-a15b-3dbe550fd3db","text":"protected central storage","parameterId":"ia-04.09_odp","default":" [Assignment: organization defined protected central storage] "}],"subControls":"","tests":[{"testId":"IA-04(09)","uuid":"835957e2-eb34-4cad-bed5-d16825932ef8","test":"Determine if the attributes for each uniquely identified individual, device, or service are maintained in [SELECTED PARAMETER VALUE(S): protected central storage ].Authenticators include passwords, cryptographic devices, biometrics, certificates, one-time password devices, and ID badges. Device authenticators include certificates and passwords. Initial authenticator content is the actual content of the authenticator (e.g., the initial password). In contrast, the requirements for authenticator content contain specific criteria or characteristics (e.g., minimum password length). Developers may deliver system components with factory default authentication credentials (i.e., passwords) to allow for initial installation and configuration. Default authentication credentials are often well known, easily discoverable, and present a significant risk. The requirement to protect individual authenticators may be implemented via control PL-4 or PS-6 for authenticators in the possession of individuals and by controls AC-3, AC-6 , and SC-28 for authenticators stored in organizational systems, including passwords stored in hashed or encrypted formats or files containing encrypted or hashed passwords accessible with administrator privileges.
Systems support authenticator management by organization-defined settings and restrictions for various authenticator characteristics (e.g., minimum password length, validation time window for time synchronous one-time tokens, and number of allowed rejections during the verification stage of biometric authentication). Actions can be taken to safeguard individual authenticators, including maintaining possession of authenticators, not sharing authenticators with others, and immediately reporting lost, stolen, or compromised authenticators. Authenticator management includes issuing and revoking authenticators for temporary access when no longer needed.
","uuid":"202ea754-5fc6-4318-85fe-8ffeb8856ccc","family":"Identification and Authentication","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"28825e30-17cd-43d0-bb55-f702ef5afb88","text":"time period by authenticator type","parameterId":"ia-05_odp.01","default":" [Assignment: organization defined time period by authenticator type] "},{"constraints":"","displayName":"","guidance":"","uuid":"9ab4fcac-c420-4e7b-8246-455cf4d5898e","text":"events","parameterId":"ia-05_odp.02","default":" [Assignment: organization defined events] "}],"subControls":"","tests":[{"testId":"IA-05a.","uuid":"942db52d-011a-4505-841c-bdbcc97e2833","test":"Determine if system authenticators are managed through the verification of the identity of the individual, group, role, service, or device receiving the authenticator as part of the initial authenticator distribution;Password-based authentication applies to passwords regardless of whether they are used in single-factor or multi-factor authentication. Long passwords or passphrases are preferable over shorter passwords. Enforced composition rules provide marginal security benefits while decreasing usability. However, organizations may choose to establish certain rules for password generation (e.g., minimum character length for long passwords) under certain circumstances and can enforce this requirement in IA-5(1)(h). Account recovery can occur, for example, in situations when a password is forgotten. Cryptographically protected passwords include salted one-way cryptographic hashes of passwords. The list of commonly used, compromised, or expected passwords includes passwords obtained from previous breach corpuses, dictionary words, and repetitive or sequential characters. The list includes context-specific words, such as the name of the service, username, and derivatives thereof.
","uuid":"0ad00d4a-bc36-42ac-ba58-a6baa5deaf87","family":"Identification and Authentication","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"424f92d6-022a-44c1-bb12-5fc3c4a42e85","text":"frequency","parameterId":"ia-05.01_odp.01","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"8a4796eb-11ef-4687-8388-0e3a8480ce3a","text":"composition and complexity rules","parameterId":"ia-05.01_odp.02","default":" [Assignment: organization defined composition and complexity rules] "}],"subControls":"","tests":[{"testId":"IA-05(01)(a)","uuid":"8ecc1675-2632-4f42-a523-c0bd6ed1d87a","test":"Determine if for password-based authentication, a list of commonly used, expected, or compromised passwords is maintained and updated [SELECTED PARAMETER VALUE(S): frequency ] and when organizational passwords are suspected to have been compromised directly or indirectly;Public key cryptography is a valid authentication mechanism for individuals, machines, and devices. For PKI solutions, status information for certification paths includes certificate revocation lists or certificate status protocol responses. For PIV cards, certificate validation involves the construction and verification of a certification path to the Common Policy Root trust anchor, which includes certificate policy processing. Implementing a local cache of revocation data to support path discovery and validation also supports system availability in situations where organizations are unable to access revocation information via the network.
","uuid":"25dd8191-c3e0-4bee-9cf8-e0f47fe01c5d","family":"Identification and Authentication","parameters":[],"subControls":"","tests":[{"testId":"IA-05(02)(a)(01)","uuid":"531f8630-3114-4d2f-9a02-6d94b5e5552b","test":"Determine if authorized access to the corresponding private key is enforced for public key-based authentication;Changing authenticators prior to the delivery and installation of system components extends the requirement for organizations to change default authenticators upon system installation by requiring developers and/or installers to provide unique authenticators or change default authenticators for system components prior to delivery and/or installation. However, it typically does not apply to developers of commercial off-the-shelf information technology products. Requirements for unique authenticators can be included in acquisition documents prepared by organizations when procuring systems or system components.
","uuid":"1fab9385-576b-4d54-a672-d294efc8433f","family":"Identification and Authentication","parameters":[],"subControls":"","tests":[{"testId":"IA-05(05)","uuid":"5bfa47e8-2535-4c19-b2c3-1da7f62661e1","test":"Determine if developers and installers of system components are required to provide unique authenticators or change default authenticators prior to delivery and installation.For systems that contain multiple security categories of information without reliable physical or logical separation between categories, authenticators used to grant access to the systems are protected commensurate with the highest security category of information on the systems. Security categories of information are determined as part of the security categorization process.
","uuid":"38c272f7-edba-4e21-83a8-fd413a059816","family":"Identification and Authentication","parameters":[],"subControls":"","tests":[{"testId":"IA-05(06)","uuid":"ebea86ad-ff87-4629-a778-c66cd33f160a","test":"Determine if authenticators are protected commensurate with the security category of the information to which use of the authenticator permits access.In addition to applications, other forms of static storage include access scripts and function keys. Organizations exercise caution when determining whether embedded or stored authenticators are in encrypted or unencrypted form. If authenticators are used in the manner stored, then those representations are considered unencrypted authenticators.
","uuid":"95f2899a-ae37-46ca-b069-1e28c19936ec","family":"Identification and Authentication","parameters":[],"subControls":"","tests":[{"testId":"IA-05(07)","uuid":"6b73649d-0382-4ada-a229-026f7e3b1911","test":"Determine if unencrypted static authenticators are not embedded in applications or other forms of static storage.When individuals have accounts on multiple systems and use the same authenticators such as passwords, there is the risk that a compromise of one account may lead to the compromise of other accounts. Alternative approaches include having different authenticators (passwords) on all systems, employing a single sign-on or federation mechanism, or using some form of one-time passwords on all systems. Organizations can also use rules of behavior (see PL-4 ) and access agreements (see PS-6 ) to mitigate the risk of multiple system accounts.
","uuid":"7afb67c2-f9e0-42f9-9eea-7980515390bf","family":"Identification and Authentication","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"31213abc-80f3-4a05-8aa6-614e235d624e","text":"security controls","parameterId":"ia-05.08_odp","default":" [Assignment: organization defined security controls] "}],"subControls":"","tests":[{"testId":"IA-05(08)","uuid":"7b8d3e8a-0cc8-40ed-810c-b3240341ef95","test":"Determine if [SELECTED PARAMETER VALUE(S): security controls ] are implemented to manage the risk of compromise due to individuals having accounts on multiple systems.Federation provides organizations with the capability to authenticate individuals and devices when conducting cross-organization activities involving the processing, storage, or transmission of information. Using a specific list of approved external organizations for authentication helps to ensure that those organizations are vetted and trusted.
","uuid":"bc1bf8ff-1c17-4d4f-bc2b-bfe1be0094e7","family":"Identification and Authentication","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"a4f39f02-c98f-43a9-8b96-8ac36f08385b","text":"external organizations","parameterId":"ia-05.09_odp","default":" [Assignment: organization defined external organizations] "}],"subControls":"","tests":[{"testId":"IA-05(09)","uuid":"69c7020a-f2cb-4cb8-9677-98ddcd4767e4","test":"Determine if [SELECTED PARAMETER VALUE(S): external organizations ] are used to federate credentials.Authentication requires some form of binding between an identity and the authenticator that is used to confirm the identity. In conventional approaches, binding is established by pre-provisioning both the identity and the authenticator to the system. For example, the binding between a username (i.e., identity) and a password (i.e., authenticator) is accomplished by provisioning the identity and authenticator as a pair in the system. New authentication techniques allow the binding between the identity and the authenticator to be implemented external to a system. For example, with smartcard credentials, the identity and authenticator are bound together on the smartcard. Using these credentials, systems can authenticate identities that have not been pre-provisioned, dynamically provisioning the identity after authentication. In these situations, organizations can anticipate the dynamic provisioning of identities. Pre-established trust relationships and mechanisms with appropriate authorities to validate identities and related credentials are essential.
","uuid":"86a31b73-dae9-4bf8-9f01-b25f161f41cc","family":"Identification and Authentication","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"9cfbd862-7a2d-4f30-a746-d0f20e18cead","text":"binding rules","parameterId":"ia-05.10_odp","default":" [Assignment: organization defined binding rules] "}],"subControls":"","tests":[{"testId":"IA-05(10)","uuid":"1957ddf2-f96f-4b3d-86e6-3d2f9810ee6f","test":"Determine if identities and authenticators are dynamically bound using [SELECTED PARAMETER VALUE(S): binding rules ].Unlike password-based authentication, which provides exact matches of user-input passwords to stored passwords, biometric authentication does not provide exact matches. Depending on the type of biometric and the type of collection mechanism, there is likely to be some divergence from the presented biometric and the stored biometric that serves as the basis for comparison. Matching performance is the rate at which a biometric algorithm correctly results in a match for a genuine user and rejects other users. Biometric performance requirements include the match rate, which reflects the accuracy of the biometric matching algorithm used by a system.
","uuid":"dba63925-f82f-4559-903f-bdd18af0ea11","family":"Identification and Authentication","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"74761ffe-bec7-42b1-af16-c33bd64802a6","text":"biometric quality requirements","parameterId":"ia-05.12_odp","default":" [Assignment: organization defined biometric quality requirements] "}],"subControls":"","tests":[{"testId":"IA-05(12)","uuid":"4c7dd2e7-38e1-48a2-a402-9ecedd2bf560","test":"Determine if mechanisms that satisfy [SELECTED PARAMETER VALUE(S): biometric quality requirements ] are employed for biometric-based authentication.Cached authenticators are used to authenticate to the local machine when the network is not available. If cached authentication information is out of date, the validity of the authentication information may be questionable.
","uuid":"bc7bfc4a-79bb-4a31-a316-e25e5f664c72","family":"Identification and Authentication","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"e956e83c-7669-4846-ad7c-2bd4e57f7497","text":"time period","parameterId":"ia-05.13_odp","default":" [Assignment: organization defined time period] "}],"subControls":"","tests":[{"testId":"IA-05(13)","uuid":"2dcbcfe7-1acb-419b-b6ef-7a98b6a2f346","test":"Determine if the use of cached authenticators is prohibited after [SELECTED PARAMETER VALUE(S): time period ].An organization-wide methodology for managing the content of PKI trust stores helps improve the accuracy and currency of PKI-based authentication credentials across the organization.
","uuid":"d04cf9c1-6f91-4589-a55c-9fb9b2e3a254","family":"Identification and Authentication","parameters":[],"subControls":"","tests":[{"testId":"IA-05(14)","uuid":"a5063444-66f1-4153-827a-9c77bd247c55","test":"Determine if an organization-wide methodology for managing the content of pki trust stores is employed across all platforms, including networks, operating systems, browsers, and applications for pki-based authentication.General Services Administration (GSA)-approved products and services are products and services that have been approved through the GSA conformance program, where applicable, and posted to the GSA Approved Products List. GSA provides guidance for teams to design and build functional and secure systems that comply with Federal Identity, Credential, and Access Management (FICAM) policies, technologies, and implementation patterns.
","uuid":"838f24e4-5fe9-420e-95ea-4bc2cc863b6b","family":"Identification and Authentication","parameters":[],"subControls":"","tests":[{"testId":"IA-05(15)","uuid":"a8059f73-e9cf-456e-8459-b9b963dce9d8","test":"Determine if only general services administration-approved products and services are used for identity, credential, and access management.Issuing authenticators in person or by a trusted external party enhances and reinforces the trustworthiness of the identity proofing process.
","uuid":"4013a3af-61e8-4edd-b1a1-377cd9570863","family":"Identification and Authentication","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"1eaf55c4-04cd-4d36-af6b-92b16cc27fc3","text":"types of and/or specific authenticators","parameterId":"ia-05.16_odp.01","default":" [Assignment: organization defined types of and/or specific authenticators] "},{"constraints":"","displayName":"","guidance":"","uuid":"8339b5e8-e9df-453a-b62b-9388451a707b","text":"[Selection: in person; by a trusted external party]","parameterId":"ia-05.16_odp.02","default":"[Selection: in person; by a trusted external party]"},{"constraints":"","displayName":"","guidance":"","uuid":"f820fbc3-5415-4163-a067-d734d2c06791","text":"registration authority","parameterId":"ia-05.16_odp.03","default":" [Assignment: organization defined registration authority] "},{"constraints":"","displayName":"","guidance":"","uuid":"06942824-b8e9-4f88-9583-eebc31a49de6","text":"personnel or roles","parameterId":"ia-05.16_odp.04","default":" [Assignment: organization defined personnel or roles] "}],"subControls":"","tests":[{"testId":"IA-05(16)","uuid":"6613428c-ad18-491c-8517-ec14994cc606","test":"Determine if the issuance of [SELECTED PARAMETER VALUE(S): types of and/or specific authenticators ] is required to be conducted [SELECTED PARAMETER VALUE(S): [Selection: in person; by a trusted external party] ] before [SELECTED PARAMETER VALUE(S): registration authority ] with authorization by [SELECTED PARAMETER VALUE(S): personnel or roles ].Biometric characteristics do not constitute secrets. Such characteristics can be obtained by online web accesses, taking a picture of someone with a camera phone to obtain facial images with or without their knowledge, lifting from objects that someone has touched (e.g., a latent fingerprint), or capturing a high-resolution image (e.g., an iris pattern). Presentation attack detection technologies including liveness detection, can mitigate the risk of these types of attacks by making it difficult to produce artifacts intended to defeat the biometric sensor.
","uuid":"a7c605c7-31a8-4b5c-aac9-2ab3d121cd27","family":"Identification and Authentication","parameters":[],"subControls":"","tests":[{"testId":"IA-05(17)","uuid":"619c4c9c-92cd-4449-af55-489ecf791f14","test":"Determine if presentation attack detection mechanisms are employed for biometric-based authentication.For systems where static passwords are employed, it is often a challenge to ensure that the passwords are suitably complex and that the same passwords are not employed on multiple systems. A password manager is a solution to this problem as it automatically generates and stores strong and different passwords for various accounts. A potential risk of using password managers is that adversaries can target the collection of passwords generated by the password manager. Therefore, the collection of passwords requires protection including encrypting the passwords (see IA-5(1)(d) ) and storing the collection offline in a token.
","uuid":"69fa4723-b6ac-4a1a-8a3d-636617fd2bc7","family":"Identification and Authentication","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"1010dcc1-59ec-4997-9114-4741e1d0d32f","text":"password managers","parameterId":"ia-05.18_odp.01","default":" [Assignment: organization defined password managers] "},{"constraints":"","displayName":"","guidance":"","uuid":"8cd62eb5-0048-4988-8fb9-0c4edf3feb4d","text":"controls","parameterId":"ia-05.18_odp.02","default":" [Assignment: organization defined controls] "}],"subControls":"","tests":[{"testId":"IA-05(18)(a)","uuid":"e0d60307-ea7b-4488-bd26-8b956257b2af","test":"Determine if [SELECTED PARAMETER VALUE(S): password managers ] are employed to generate and manage passwords;Authentication feedback from systems does not provide information that would allow unauthorized individuals to compromise authentication mechanisms. For some types of systems, such as desktops or notebooks with relatively large monitors, the threat (referred to as shoulder surfing) may be significant. For other types of systems, such as mobile devices with small displays, the threat may be less significant and is balanced against the increased likelihood of typographic input errors due to small keyboards. Thus, the means for obscuring authentication feedback is selected accordingly. Obscuring authentication feedback includes displaying asterisks when users type passwords into input devices or displaying feedback for a very limited time before obscuring it.
","uuid":"017f47f6-ee3b-4d8b-b9bf-4d006a46f27a","family":"Identification and Authentication","parameters":[],"subControls":"","tests":[{"testId":"IA-06","uuid":"b4d8db95-53d5-4786-9409-ac537c452f10","test":"Determine if the feedback of authentication information is obscured during the authentication process to protect the information from possible exploitation and use by unauthorized individuals.Authentication mechanisms may be required within a cryptographic module to authenticate an operator accessing the module and to verify that the operator is authorized to assume the requested role and perform services within that role.
","uuid":"927ca906-5050-4c42-904c-266b0a62bddb","family":"Identification and Authentication","parameters":[],"subControls":"","tests":[{"testId":"IA-07","uuid":"0bb4c15a-9242-4ae4-8d45-506a69a2c83d","test":"Determine if mechanisms for authentication to a cryptographic module are implemented that meet the requirements of applicable laws, executive orders, directives, policies, regulations, standards, and guidelines for such authentication.Non-organizational users include system users other than organizational users explicitly covered by IA-2 . Non-organizational users are uniquely identified and authenticated for accesses other than those explicitly identified and documented in AC-14 . Identification and authentication of non-organizational users accessing federal systems may be required to protect federal, proprietary, or privacy-related information (with exceptions noted for national security systems). Organizations consider many factors—including security, privacy, scalability, and practicality—when balancing the need to ensure ease of use for access to federal information and systems with the need to protect and adequately mitigate risk.
","uuid":"799b6347-8dc7-49a2-9867-08226736c7c9","family":"Identification and Authentication","parameters":[],"subControls":"","tests":[{"testId":"IA-08","uuid":"0f1ba3b0-0f7c-49a1-93b3-1ec237a42602","test":"Determine if non-organizational users or processes acting on behalf of non-organizational users are uniquely identified and authenticated.Acceptance of Personal Identity Verification (PIV) credentials from other federal agencies applies to both logical and physical access control systems. PIV credentials are those credentials issued by federal agencies that conform to FIPS Publication 201 and supporting guidelines. The adequacy and reliability of PIV card issuers are addressed and authorized using SP 800-79-2.
","uuid":"897ec432-f85c-448a-9b44-a657f36eda26","family":"Identification and Authentication","parameters":[],"subControls":"","tests":[{"testId":"IA-08(01)[01]","uuid":"90de4db6-47cf-45e4-bb12-b0e5f9b2c8a8","test":"Determine if personal identity verification-compliant credentials from other federal agencies are accepted;Acceptance of only NIST-compliant external authenticators applies to organizational systems that are accessible to the public (e.g., public-facing websites). External authenticators are issued by nonfederal government entities and are compliant with SP 800-63B . Approved external authenticators meet or exceed the minimum Federal Government-wide technical, security, privacy, and organizational maturity requirements. Meeting or exceeding Federal requirements allows Federal Government relying parties to trust external authenticators in connection with an authentication transaction at a specified authenticator assurance level.
","uuid":"c382e676-d091-44b7-8e66-7c76cbc92b86","family":"Identification and Authentication","parameters":[],"subControls":"","tests":[{"testId":"IA-08(02)(a)","uuid":"7dc542ae-fbcb-44f7-bd28-453dca4dd2bc","test":"Determine if only external authenticators that are nist-compliant are accepted;Organizations define profiles for identity management based on open identity management standards. To ensure that open identity management standards are viable, robust, reliable, sustainable, and interoperable as documented, the Federal Government assesses and scopes the standards and technology implementations against applicable laws, executive orders, directives, policies, regulations, standards, and guidelines.
","uuid":"ab3c5512-4871-4a72-bb14-f7ea6356982e","family":"Identification and Authentication","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"e2668fce-5dd8-4ec3-a019-e252f965d7a9","text":"identity management profiles","parameterId":"ia-08.04_odp","default":" [Assignment: organization defined identity management profiles] "}],"subControls":"","tests":[{"testId":"IA-08(04)","uuid":"c127a6d0-3b36-4c98-89c9-111586d8d0fb","test":"Determine if there is conformance with [SELECTED PARAMETER VALUE(S): identity management profiles ] for identity management.Acceptance of PIV-I credentials can be implemented by PIV, PIV-I, and other commercial or external identity providers. The acceptance and verification of PIV-I-compliant credentials apply to both logical and physical access control systems. The acceptance and verification of PIV-I credentials address nonfederal issuers of identity cards that desire to interoperate with United States Government PIV systems and that can be trusted by Federal Government-relying parties. The X.509 certificate policy for the Federal Bridge Certification Authority (FBCA) addresses PIV-I requirements. The PIV-I card is commensurate with the PIV credentials as defined in cited references. PIV-I credentials are the credentials issued by a PIV-I provider whose PIV-I certificate policy maps to the Federal Bridge PIV-I Certificate Policy. A PIV-I provider is cross-certified with the FBCA (directly or through another PKI bridge) with policies that have been mapped and approved as meeting the requirements of the PIV-I policies defined in the FBCA certificate policy.
","uuid":"c97891af-dfac-4d9c-a10d-667678eb4073","family":"Identification and Authentication","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"1ae57fdb-a637-491c-be25-b09816b78edb","text":"policy","parameterId":"ia-08.05_odp","default":" [Assignment: organization defined policy] "}],"subControls":"","tests":[{"testId":"IA-08(05)[01]","uuid":"61463639-4ffa-46ba-94d7-a56f4d2d52d3","test":"Determine if federated or pki credentials that meet [SELECTED PARAMETER VALUE(S): policy ] are accepted;Federated identity solutions can create increased privacy risks due to the tracking and profiling of individuals. Using identifier mapping tables or cryptographic techniques to blind credential service providers and relying parties from each other or to make identity attributes less visible to transmitting parties can reduce these privacy risks.
","uuid":"a18c9895-8f9c-494f-9873-f8c97071aa32","family":"Identification and Authentication","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"45a96b9f-5270-4756-a2e1-04122e1e5efa","text":"measures","parameterId":"ia-08.06_odp","default":" [Assignment: organization defined measures] "}],"subControls":"","tests":[{"testId":"IA-08(06)","uuid":"941c4975-c705-478d-a27e-e006b1b4b5ee","test":"Determine if [SELECTED PARAMETER VALUE(S): measures ] to disassociate user attributes or identifier assertion relationships among individuals, credential service providers, and relying parties are implemented.Services that may require identification and authentication include web applications using digital certificates or services or applications that query a database. Identification and authentication methods for system services and applications include information or code signing, provenance graphs, and electronic signatures that indicate the sources of services. Decisions regarding the validity of identification and authentication claims can be made by services separate from the services acting on those decisions. This can occur in distributed system architectures. In such situations, the identification and authentication decisions (instead of actual identifiers and authentication data) are provided to the services that need to act on those decisions.
","uuid":"f88acf75-4ef9-43d8-9626-d3439c48701e","family":"Identification and Authentication","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"665e1afc-5efa-4899-8662-1313e9075bf2","text":"system services and applications","parameterId":"ia-09_odp","default":" [Assignment: organization defined system services and applications] "}],"subControls":"","tests":[{"testId":"IA-09","uuid":"79968537-b3c4-46f1-8805-f0c8c2943b5f","test":"Determine if [SELECTED PARAMETER VALUE(S): system services and applications ] are uniquely identified and authenticated before establishing communications with devices, users, or other services or applications.Adversaries may compromise individual authentication mechanisms employed by organizations and subsequently attempt to impersonate legitimate users. To address this threat, organizations may employ specific techniques or mechanisms and establish protocols to assess suspicious behavior. Suspicious behavior may include accessing information that individuals do not typically access as part of their duties, roles, or responsibilities; accessing greater quantities of information than individuals would routinely access; or attempting to access information from suspicious network addresses. When pre-established conditions or triggers occur, organizations can require individuals to provide additional authentication information. Another potential use for adaptive authentication is to increase the strength of mechanism based on the number or types of records being accessed. Adaptive authentication does not replace and is not used to avoid the use of multi-factor authentication mechanisms but can augment implementations of multi-factor authentication.
","uuid":"8d386c1d-66eb-48a3-b356-e41341f5f0dc","family":"Identification and Authentication","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"a26a5ade-c62e-41a6-800a-fab1d1ec1a85","text":"supplemental authentication techniques or mechanisms","parameterId":"ia-10_odp.01","default":" [Assignment: organization defined supplemental authentication techniques or mechanisms] "},{"constraints":"","displayName":"","guidance":"","uuid":"e02ef6c7-2b6f-4aee-94a4-6a4a547bd445","text":"circumstances or situations","parameterId":"ia-10_odp.02","default":" [Assignment: organization defined circumstances or situations] "}],"subControls":"","tests":[{"testId":"IA-10","uuid":"7b69eb6f-b87a-4da7-af54-4543f5dfc442","test":"Determine if individuals accessing the system are required to employ [SELECTED PARAMETER VALUE(S): supplemental authentication techniques or mechanisms ] under specific [SELECTED PARAMETER VALUE(S): circumstances or situations ].In addition to the re-authentication requirements associated with device locks, organizations may require re-authentication of individuals in certain situations, including when roles, authenticators or credentials change, when security categories of systems change, when the execution of privileged functions occurs, after a fixed time period, or periodically.
","uuid":"aee4787c-7475-4cb2-aa7a-1982ab9aacf0","family":"Identification and Authentication","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"fb9fbe81-16ee-416b-9b0a-30fab99fe1f8","text":"circumstances or situations","parameterId":"ia-11_odp","default":" [Assignment: organization defined circumstances or situations] "}],"subControls":"","tests":[{"testId":"IA-11","uuid":"623dfb73-217f-4df5-88b3-5b8f3ea050d5","test":"Determine if users are required to re-authenticate when [SELECTED PARAMETER VALUE(S): circumstances or situations ].Identity proofing is the process of collecting, validating, and verifying a user’s identity information for the purposes of establishing credentials for accessing a system. Identity proofing is intended to mitigate threats to the registration of users and the establishment of their accounts. Standards and guidelines specifying identity assurance levels for identity proofing include SP 800-63-3 and SP 800-63A . Organizations may be subject to laws, executive orders, directives, regulations, or policies that address the collection of identity evidence. Organizational personnel consult with the senior agency official for privacy and legal counsel regarding such requirements.
","uuid":"16b6816c-a6b4-45cd-83c7-44d81e267521","family":"Identification and Authentication","parameters":[],"subControls":"","tests":[{"testId":"IA-12a.","uuid":"ecf12688-2e0e-4724-9161-93099a3fdce5","test":"Determine if users who require accounts for logical access to systems based on appropriate identity assurance level requirements as specified in applicable standards and guidelines are identity proofed;Including supervisor or sponsor authorization as part of the registration process provides an additional level of scrutiny to ensure that the user’s management chain is aware of the account, the account is essential to carry out organizational missions and functions, and the user’s privileges are appropriate for the anticipated responsibilities and authorities within the organization.
","uuid":"b17da285-8d54-4bf1-9ad4-5c649b67be7f","family":"Identification and Authentication","parameters":[],"subControls":"","tests":[{"testId":"IA-12(01)","uuid":"653fd292-d35d-4c1c-ae6c-f081f04ede88","test":"Determine if the registration process to receive an account for logical access includes supervisor or sponsor authorization.Identity evidence, such as documentary evidence or a combination of documents and biometrics, reduces the likelihood of individuals using fraudulent identification to establish an identity or at least increases the work factor of potential adversaries. The forms of acceptable evidence are consistent with the risks to the systems, roles, and privileges associated with the user’s account.
","uuid":"d47392cf-4c46-4146-92f8-7325aa696666","family":"Identification and Authentication","parameters":[],"subControls":"","tests":[{"testId":"IA-12(02)","uuid":"8d63ec15-8089-4055-a60d-6474f8ae4ba7","test":"Determine if evidence of individual identification is presented to the registration authority.Validation and verification of identity evidence increases the assurance that accounts and identifiers are being established for the correct user and authenticators are being bound to that user. Validation refers to the process of confirming that the evidence is genuine and authentic, and the data contained in the evidence is correct, current, and related to an individual. Verification confirms and establishes a linkage between the claimed identity and the actual existence of the user presenting the evidence. Acceptable methods for validating and verifying identity evidence are consistent with the risks to the systems, roles, and privileges associated with the users account.
","uuid":"b7b61dd6-5d81-41b0-a393-12583074b0d6","family":"Identification and Authentication","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"9f265a0b-6feb-4da9-a910-e58381e4bbf0","text":"methods of validation and verification","parameterId":"ia-12.03_odp","default":" [Assignment: organization defined methods of validation and verification] "}],"subControls":"","tests":[{"testId":"IA-12(03)","uuid":"23e3a87d-03d6-46d0-84e0-b8f6af93bf1b","test":"Determine if the presented identity evidence is validated and verified through [SELECTED PARAMETER VALUE(S): methods of validation and verification ].In-person proofing reduces the likelihood of fraudulent credentials being issued because it requires the physical presence of individuals, the presentation of physical identity documents, and actual face-to-face interactions with designated registration authorities.
","uuid":"9c035c82-6776-467c-8922-fda30165e6bc","family":"Identification and Authentication","parameters":[],"subControls":"","tests":[{"testId":"IA-12(04)","uuid":"f7d54526-9aa4-4b36-bdaa-ac389ee27340","test":"Determine if the validation and verification of identity evidence is conducted in person before a designated registration authority.To make it more difficult for adversaries to pose as legitimate users during the identity proofing process, organizations can use out-of-band methods to ensure that the individual associated with an address of record is the same individual that participated in the registration. Confirmation can take the form of a temporary enrollment code or a notice of proofing. The delivery address for these artifacts is obtained from records and not self-asserted by the user. The address can include a physical or digital address. A home address is an example of a physical address. Email addresses and telephone numbers are examples of digital addresses.
","uuid":"66396291-a11d-4c9f-9999-414f83de9102","family":"Identification and Authentication","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"5a2839e9-1166-48ae-8805-93db3e89c0bd","text":"[Selection: registration code; notice of proofing]","parameterId":"ia-12.05_odp","default":"[Selection: registration code; notice of proofing]"}],"subControls":"","tests":[{"testId":"IA-12(05)","uuid":"5e4134ec-eef9-49a9-b133-4f367fe7e2a5","test":"Determine if a [SELECTED PARAMETER VALUE(S): [Selection: registration code; notice of proofing] ] is delivered through an out-of-band channel to verify the user’s address (physical or digital) of record.To limit unnecessary re-proofing of identities, particularly of non-PIV users, organizations accept proofing conducted at a commensurate level of assurance by other agencies or organizations. Proofing is consistent with organizational security policy and the identity assurance level appropriate for the system, application, or information accessed. Accepting externally-proofed identities is a fundamental component of managing federated identities across agencies and organizations.
","uuid":"368bad2d-766e-4bc0-871f-7e189c18a7a5","family":"Identification and Authentication","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"d05dc194-210d-4999-ad3e-f9037320e767","text":"identity assurance level","parameterId":"ia-12.06_odp","default":" [Assignment: organization defined identity assurance level] "}],"subControls":"","tests":[{"testId":"IA-12(06)","uuid":"0d58327f-0d23-4161-8e11-73fb091fe956","test":"Determine if externally proofed identities are accepted [SELECTED PARAMETER VALUE(S): identity assurance level ].Incident response policy and procedures address the controls in the IR family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of incident response policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission or business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to incident response policy and procedures include assessment or audit findings, security incidents or breaches, or changes in laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure.
","uuid":"57c21e5d-9a15-4259-bf35-24ccabafcb37","family":"Incident Response","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"408c1d24-8c8a-459a-b420-eb4198c81c19","text":"organization-defined personnel or roles","parameterId":"ir-1_prm_1","default":" [Assignment: organization-defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"1010745b-63a0-4ef9-913d-8aeef6c0d678","text":"personnel or roles","parameterId":"ir-01_odp.01","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"fed6ccd2-f489-45ee-a42c-9c05def0be5b","text":"personnel or roles","parameterId":"ir-01_odp.02","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"6e6c4b20-c7fe-48b4-8d65-f51ba9466e2f","text":"[Selection (one or more): organization-level; mission/business process-level; system-level]","parameterId":"ir-01_odp.03","default":"[Selection (one or more): organization-level; mission/business process-level; system-level]"},{"constraints":"","displayName":"","guidance":"","uuid":"c1147e9b-1584-46aa-90d8-384962e72407","text":"official","parameterId":"ir-01_odp.04","default":" [Assignment: organization defined official] "},{"constraints":"","displayName":"","guidance":"","uuid":"a357e900-8eb3-4bbd-87d8-6af1583d9499","text":"frequency","parameterId":"ir-01_odp.05","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"33e1c477-94c0-4d48-8522-bf6a38960c20","text":"events","parameterId":"ir-01_odp.06","default":" [Assignment: organization defined events] "},{"constraints":"","displayName":"","guidance":"","uuid":"873c83ef-3643-49d8-b837-2c69200fd1cf","text":"frequency","parameterId":"ir-01_odp.07","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"cf5d33b7-0e75-4e7d-95ad-e800b0846c53","text":"events","parameterId":"ir-01_odp.08","default":" [Assignment: organization defined events] "}],"subControls":"","tests":[{"testId":"IR-01a.[01]","uuid":"4d7790b7-71bb-44fb-b2b5-84df7d7b6e2a","test":"Determine if an incident response policy is developed and documented;Incident response training is associated with the assigned roles and responsibilities of organizational personnel to ensure that the appropriate content and level of detail are included in such training. For example, users may only need to know who to call or how to recognize an incident; system administrators may require additional training on how to handle incidents; and incident responders may receive more specific training on forensics, data collection techniques, reporting, system recovery, and system restoration. Incident response training includes user training in identifying and reporting suspicious activities from external and internal sources. Incident response training for users may be provided as part of AT-2 or AT-3 . Events that may precipitate an update to incident response training content include, but are not limited to, incident response plan testing or response to an actual incident (lessons learned), assessment or audit findings, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines.
","uuid":"50039198-53e0-47a8-9802-634b0e688ea1","family":"Incident Response","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"2174a568-c4c4-4bca-9889-040e62f9b246","text":"time period","parameterId":"ir-02_odp.01","default":" [Assignment: organization defined time period] "},{"constraints":"","displayName":"","guidance":"","uuid":"5478d2ff-57f7-465b-98b1-f3e5b4b96994","text":"frequency","parameterId":"ir-02_odp.02","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"2ec9726c-7e6a-40ea-a3a9-d6f75298b735","text":"frequency","parameterId":"ir-02_odp.03","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"4e67aefc-5515-4bf0-a60c-649980df6525","text":"events","parameterId":"ir-02_odp.04","default":" [Assignment: organization defined events] "}],"subControls":"","tests":[{"testId":"IR-02a.01","uuid":"75f65afc-6ef6-4cbd-a501-9147deb2496e","test":"Determine if incident response training is provided to system users consistent with assigned roles and responsibilities within [SELECTED PARAMETER VALUE(S): time period ] of assuming an incident response role or responsibility or acquiring system access;Organizations establish requirements for responding to incidents in incident response plans. Incorporating simulated events into incident response training helps to ensure that personnel understand their individual responsibilities and what specific actions to take in crisis situations.
","uuid":"28345a3c-20ab-4f5d-83e5-65899d9e2ed1","family":"Incident Response","parameters":[],"subControls":"","tests":[{"testId":"IR-02(01)","uuid":"3ba59121-aecf-4d98-ad00-8d29d5abb707","test":"Determine if simulated events are incorporated into incident response training to facilitate the required response by personnel in crisis situations.Automated mechanisms can provide a more thorough and realistic incident response training environment. This can be accomplished, for example, by providing more complete coverage of incident response issues, selecting more realistic training scenarios and environments, and stressing the response capability.
","uuid":"729ee8c3-cc14-40f8-a8a4-2e899963e532","family":"Incident Response","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"7beff617-f917-4554-8e9a-8f296a64ed1c","text":"automated mechanisms","parameterId":"ir-02.02_odp","default":" [Assignment: organization defined automated mechanisms] "}],"subControls":"","tests":[{"testId":"IR-02(02)","uuid":"1c7c0ae8-32c9-4e4b-abe2-0fa8c81469aa","test":"Determine if an incident response training environment is provided using [SELECTED PARAMETER VALUE(S): automated mechanisms ].For federal agencies, an incident that involves personally identifiable information is considered a breach. A breach results in the loss of control, compromise, unauthorized disclosure, unauthorized acquisition, or a similar occurrence where a person other than an authorized user accesses or potentially accesses personally identifiable information or an authorized user accesses or potentially accesses such information for other than authorized purposes. The incident response training emphasizes the obligation of individuals to report both confirmed and suspected breaches involving information in any medium or form, including paper, oral, and electronic. Incident response training includes tabletop exercises that simulate a breach. See IR-2(1).
","uuid":"70d3b13d-06f0-4c2b-911b-ca2a12fa7310","family":"Incident Response","parameters":[],"subControls":"","tests":[{"testId":"IR-02(03)[01]","uuid":"183201f3-233d-49d4-b000-44a0883ffdde","test":"Determine if incident response training on how to identify and respond to a breach is provided;Organizations test incident response capabilities to determine their effectiveness and identify potential weaknesses or deficiencies. Incident response testing includes the use of checklists, walk-through or tabletop exercises, and simulations (parallel or full interrupt). Incident response testing can include a determination of the effects on organizational operations and assets and individuals due to incident response. The use of qualitative and quantitative data aids in determining the effectiveness of incident response processes.
","uuid":"440b0e14-5125-41c2-908c-2cbf963203a8","family":"Incident Response","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"30bd7f0f-9919-4788-9577-372713b96019","text":"frequency","parameterId":"ir-03_odp.01","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"c4653255-ae51-40a8-9ad0-419646c13981","text":"tests","parameterId":"ir-03_odp.02","default":" [Assignment: organization defined tests] "}],"subControls":"","tests":[{"testId":"IR-03","uuid":"d2641e5d-d216-4de9-a1ef-d6136f05cfcf","test":"Determine if the effectiveness of the incident response capability for the system is tested [SELECTED PARAMETER VALUE(S): frequency ] using [SELECTED PARAMETER VALUE(S): tests ].Organizations use automated mechanisms to more thoroughly and effectively test incident response capabilities. This can be accomplished by providing more complete coverage of incident response issues, selecting realistic test scenarios and environments, and stressing the response capability.
","uuid":"35d15a28-8c1d-4950-80b0-70da6f51a5c3","family":"Incident Response","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"fb0cc555-0b73-4e33-b42c-d374fea873ee","text":"automated mechanisms","parameterId":"ir-03.01_odp","default":" [Assignment: organization defined automated mechanisms] "}],"subControls":"","tests":[{"testId":"IR-03(01)","uuid":"89b7f288-8e49-4c06-be93-49fa21c2ba89","test":"Determine if the incident response capability is tested using [SELECTED PARAMETER VALUE(S): automated mechanisms ].Organizational plans related to incident response testing include business continuity plans, disaster recovery plans, continuity of operations plans, contingency plans, crisis communications plans, critical infrastructure plans, and occupant emergency plans.
","uuid":"6ca72642-3680-42ca-b57e-743d01ee023f","family":"Incident Response","parameters":[],"subControls":"","tests":[{"testId":"IR-03(02)","uuid":"f1df57ca-8178-42a8-b984-11b99d306db1","test":"Determine if incident response testing is coordinated with organizational elements responsible for related plans.To help incident response activities function as intended, organizations may use metrics and evaluation criteria to assess incident response programs as part of an effort to continually improve response performance. These efforts facilitate improvement in incident response efficacy and lessen the impact of incidents.
","uuid":"c6d9403e-a99a-4e1f-b5c9-cbd250f98c43","family":"Incident Response","parameters":[],"subControls":"","tests":[{"testId":"IR-03(03)(a)[01]","uuid":"f85d70c5-fbc7-4317-8a52-cf883abcd7ca","test":"Determine if qualitative data from testing are used to determine the effectiveness of incident response processes;Organizations recognize that incident response capabilities are dependent on the capabilities of organizational systems and the mission and business processes being supported by those systems. Organizations consider incident response as part of the definition, design, and development of mission and business processes and systems. Incident-related information can be obtained from a variety of sources, including audit monitoring, physical access monitoring, and network monitoring; user or administrator reports; and reported supply chain events. An effective incident handling capability includes coordination among many organizational entities (e.g., mission or business owners, system owners, authorizing officials, human resources offices, physical security offices, personnel security offices, legal departments, risk executive [function], operations personnel, procurement offices). Suspected security incidents include the receipt of suspicious email communications that can contain malicious code. Suspected supply chain incidents include the insertion of counterfeit hardware or malicious code into organizational systems or system components. For federal agencies, an incident that involves personally identifiable information is considered a breach. A breach results in unauthorized disclosure, the loss of control, unauthorized acquisition, compromise, or a similar occurrence where a person other than an authorized user accesses or potentially accesses personally identifiable information or an authorized user accesses or potentially accesses such information for other than authorized purposes.
","uuid":"455a24f4-5b82-4087-8042-79fabb5707e7","family":"Incident Response","parameters":[],"subControls":"","tests":[{"testId":"IR-04a.[01]","uuid":"6711ba0d-7a5d-4435-b0ef-a1fef701b144","test":"Determine if an incident handling capability for incidents is implemented that is consistent with the incident response plan;Automated mechanisms that support incident handling processes include online incident management systems and tools that support the collection of live response data, full network packet capture, and forensic analysis.
","uuid":"53672f9b-a8c4-4747-9733-63f370ca7721","family":"Incident Response","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"39ab1f79-a140-4ef6-9522-34952576707f","text":"automated mechanisms","parameterId":"ir-04.01_odp","default":" [Assignment: organization defined automated mechanisms] "}],"subControls":"","tests":[{"testId":"IR-04(01)","uuid":"ba9331ac-52e4-41f2-8571-c49d2d299d7b","test":"Determine if the incident handling process is supported using [SELECTED PARAMETER VALUE(S): automated mechanisms ].Dynamic reconfiguration includes changes to router rules, access control lists, intrusion detection or prevention system parameters, and filter rules for guards or firewalls. Organizations may perform dynamic reconfiguration of systems to stop attacks, misdirect attackers, and isolate components of systems, thus limiting the extent of the damage from breaches or compromises. Organizations include specific time frames for achieving the reconfiguration of systems in the definition of the reconfiguration capability, considering the potential need for rapid response to effectively address cyber threats.
","uuid":"6b2553a0-7db2-4139-9cdb-59ed5f03bfef","family":"Incident Response","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"414953fc-7b71-4b27-95ea-e8071a59357d","text":"types of dynamic reconfiguration","parameterId":"ir-04.02_odp.01","default":" [Assignment: organization defined types of dynamic reconfiguration] "},{"constraints":"","displayName":"","guidance":"","uuid":"2c6d6424-8018-4549-97bb-a8f98fecc92f","text":"system components","parameterId":"ir-04.02_odp.02","default":" [Assignment: organization defined system components] "}],"subControls":"","tests":[{"testId":"IR-04(02)","uuid":"684f58c3-3bb5-4bc2-88a4-ab6bf4401ffc","test":"Determine if [SELECTED PARAMETER VALUE(S): types of dynamic reconfiguration ] for [SELECTED PARAMETER VALUE(S): system components ] are included as part of the incident response capability.Classes of incidents include malfunctions due to design or implementation errors and omissions, targeted malicious attacks, and untargeted malicious attacks. Incident response actions include orderly system degradation, system shutdown, fall back to manual mode or activation of alternative technology whereby the system operates differently, employing deceptive measures, alternate information flows, or operating in a mode that is reserved for when systems are under attack. Organizations consider whether continuity of operations requirements during an incident conflict with the capability to automatically disable the system as specified as part of IR-4(5).
","uuid":"34b01801-71b6-447e-be07-2c00abc50230","family":"Incident Response","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"d8098485-e576-4124-83fe-5fcd30e11682","text":"classes of incidents","parameterId":"ir-04.03_odp.01","default":" [Assignment: organization defined classes of incidents] "},{"constraints":"","displayName":"","guidance":"","uuid":"a515fe74-c163-422b-823f-6d31e8860969","text":"actions","parameterId":"ir-04.03_odp.02","default":" [Assignment: organization defined actions] "}],"subControls":"","tests":[{"testId":"IR-04(03)[01]","uuid":"28ca9a66-94cb-4dc3-8e6e-c5ddaea8125c","test":"Determine if [SELECTED PARAMETER VALUE(S): classes of incidents ] are identified;Sometimes, a threat event, such as a hostile cyber-attack, can only be observed by bringing together information from different sources, including various reports and reporting procedures established by organizations.
","uuid":"01dd27a1-33b9-411f-af74-4f4037dd4c39","family":"Incident Response","parameters":[],"subControls":"","tests":[{"testId":"IR-04(04)","uuid":"0ce627e9-3725-4078-adca-807952fb93dc","test":"Determine if incident information and individual incident responses are correlated to achieve an organization-wide perspective on incident awareness and response.Organizations consider whether the capability to automatically disable the system conflicts with continuity of operations requirements specified as part of CP-2 or IR-4(3) . Security violations include cyber-attacks that have compromised the integrity of the system or exfiltrated organizational information and serious errors in software programs that could adversely impact organizational missions or functions or jeopardize the safety of individuals.
","uuid":"24f671f7-5b7a-4e66-bbb3-ad833c756a62","family":"Incident Response","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"05ca1323-f4ca-46d3-8685-31fba2badf8f","text":"security violations","parameterId":"ir-04.05_odp","default":" [Assignment: organization defined security violations] "}],"subControls":"","tests":[{"testId":"IR-04(05)","uuid":"2f73f887-6782-49dd-aa20-171aef610f8f","test":"Determine if a configurable capability is implemented to automatically disable the system if [SELECTED PARAMETER VALUE(S): security violations ] are detected.Explicit focus on handling incidents involving insider threats provides additional emphasis on this type of threat and the need for specific incident handling capabilities to provide appropriate and timely responses.
","uuid":"4907aa8c-c6fb-419d-8fc1-9bcdb3869445","family":"Incident Response","parameters":[],"subControls":"","tests":[{"testId":"IR-04(06)","uuid":"1f49a119-06ed-49e0-a6bb-7dabb5343058","test":"Determine if an incident handling capability is implemented for incidents involving insider threats.Incident handling for insider threat incidents (e.g., preparation, detection and analysis, containment, eradication, and recovery) requires coordination among many organizational entities, including mission or business owners, system owners, human resources offices, procurement offices, personnel offices, physical security offices, senior agency information security officer, operations personnel, risk executive (function), senior agency official for privacy, and legal counsel. In addition, organizations may require external support from federal, state, and local law enforcement agencies.
","uuid":"86ec792c-322e-46aa-b45c-9319ece44422","family":"Incident Response","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"54c5ba34-5907-4c15-bfc8-f634fa63d415","text":"entities","parameterId":"ir-04.07_odp","default":" [Assignment: organization defined entities] "}],"subControls":"","tests":[{"testId":"IR-04(07)[01]","uuid":"5288459a-2140-4b52-999f-9b5ca6d5a8a0","test":"Determine if an incident handling capability is coordinated for insider threats;The coordination of incident information with external organizations—including mission or business partners, military or coalition partners, customers, and developers—can provide significant benefits. Cross-organizational coordination can serve as an important risk management capability. This capability allows organizations to leverage information from a variety of sources to effectively respond to incidents and breaches that could potentially affect the organization’s operations, assets, and individuals.
","uuid":"580d81a6-5a30-4dc5-9c59-b3a67e93afe3","family":"Incident Response","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"54a71a7e-3d07-470e-9e11-00e5192a5950","text":"external organizations","parameterId":"ir-04.08_odp.01","default":" [Assignment: organization defined external organizations] "},{"constraints":"","displayName":"","guidance":"","uuid":"c52066d7-5874-4af6-99c1-3a8874d41bda","text":"incident information","parameterId":"ir-04.08_odp.02","default":" [Assignment: organization defined incident information] "}],"subControls":"","tests":[{"testId":"IR-04(08)","uuid":"f8c230ee-a359-430a-96af-1687bae6efef","test":"Determine if there is coordination with [SELECTED PARAMETER VALUE(S): external organizations ] to correlate and share [SELECTED PARAMETER VALUE(S): incident information ] to achieve a cross-organization perspective on incident awareness and more effective incident responses.The dynamic response capability addresses the timely deployment of new or replacement organizational capabilities in response to incidents. This includes capabilities implemented at the mission and business process level and at the system level.
","uuid":"eca98801-88f4-4548-9658-3492003fa560","family":"Incident Response","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"e2b3a1bb-6d02-4637-ad15-c82eb97e6d7c","text":"dynamic response capabilities","parameterId":"ir-04.09_odp","default":" [Assignment: organization defined dynamic response capabilities] "}],"subControls":"","tests":[{"testId":"IR-04(09)","uuid":"c4707336-6df1-41b7-87a3-80d238746c5c","test":"Determine if [SELECTED PARAMETER VALUE(S): dynamic response capabilities ] are employed to respond to incidents.Organizations involved in supply chain activities include product developers, system integrators, manufacturers, packagers, assemblers, distributors, vendors, and resellers. Supply chain incidents can occur anywhere through or to the supply chain and include compromises or breaches that involve primary or sub-tier providers, information technology products, system components, development processes or personnel, and distribution processes or warehousing facilities. Organizations consider including processes for protecting and sharing incident information in information exchange agreements and their obligations for reporting incidents to government oversight bodies (e.g., Federal Acquisition Security Council).
","uuid":"b86baf66-42d3-4d5e-b236-99d5dbee2910","family":"Incident Response","parameters":[],"subControls":"","tests":[{"testId":"IR-04(10)","uuid":"ba8d9aa1-65f8-4fc0-8ef0-3bf0b6e368f9","test":"Determine if incident handling activities involving supply chain events are coordinated with other organizations involved in the supply chain.An integrated incident response team is a team of experts that assesses, documents, and responds to incidents so that organizational systems and networks can recover quickly and implement the necessary controls to avoid future incidents. Incident response team personnel include forensic and malicious code analysts, tool developers, systems security and privacy engineers, and real-time operations personnel. The incident handling capability includes performing rapid forensic preservation of evidence and analysis of and response to intrusions. For some organizations, the incident response team can be a cross-organizational entity.
An integrated incident response team facilitates information sharing and allows organizational personnel (e.g., developers, implementers, and operators) to leverage team knowledge of the threat and implement defensive measures that enable organizations to deter intrusions more effectively. Moreover, integrated teams promote the rapid detection of intrusions, the development of appropriate mitigations, and the deployment of effective defensive measures. For example, when an intrusion is detected, the integrated team can rapidly develop an appropriate response for operators to implement, correlate the new incident with information on past intrusions, and augment ongoing cyber intelligence development. Integrated incident response teams are better able to identify adversary tactics, techniques, and procedures that are linked to the operations tempo or specific mission and business functions and to define responsive actions in a way that does not disrupt those mission and business functions. Incident response teams can be distributed within organizations to make the capability resilient.
","uuid":"4e1bc7a3-a504-4668-8b3f-95cef54b9a48","family":"Incident Response","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"659468f4-255a-4338-83f1-90555da2c4d4","text":"time period","parameterId":"ir-04.11_odp","default":" [Assignment: organization defined time period] "}],"subControls":"","tests":[{"testId":"IR-04(11)[01]","uuid":"b967804c-4939-421e-b080-2668b651995b","test":"Determine if an integrated incident response team is established and maintained;When conducted carefully in an isolated environment, analysis of malicious code and other residual artifacts of a security incident or breach can give the organization insight into adversary tactics, techniques, and procedures. It can also indicate the identity or some defining characteristics of the adversary. In addition, malicious code analysis can help the organization develop responses to future incidents.
","uuid":"ca05bece-443b-4de5-bfa1-5afd2193aa7c","family":"Incident Response","parameters":[],"subControls":"","tests":[{"testId":"IR-04(12)[01]","uuid":"853cfc0d-4464-4740-a7b7-79143692a431","test":"Determine if malicious code remaining in the system is analyzed after the incident;If the organization maintains a deception environment, an analysis of behaviors in that environment, including resources targeted by the adversary and timing of the incident or event, can provide insight into adversarial tactics, techniques, and procedures. External to a deception environment, the analysis of anomalous adversarial behavior (e.g., changes in system performance or usage patterns) or suspected behavior (e.g., changes in searches for the location of specific resources) can give the organization such insight.
","uuid":"f26e4928-2808-439b-b5bc-45c0d69ba638","family":"Incident Response","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"6b7529fa-33c3-4aa3-84d4-32b1fe3ede4a","text":"environments or resources","parameterId":"ir-04.13_odp","default":" [Assignment: organization defined environments or resources] "}],"subControls":"","tests":[{"testId":"IR-04(13)","uuid":"9d82dd37-efd1-4063-b034-adea00c5d604","test":"Determine if anomalous or suspected adversarial behavior in or related to [SELECTED PARAMETER VALUE(S): environments or resources ] are analyzed.A security operations center (SOC) is the focal point for security operations and computer network defense for an organization. The purpose of the SOC is to defend and monitor an organization’s systems and networks (i.e., cyber infrastructure) on an ongoing basis. The SOC is also responsible for detecting, analyzing, and responding to cybersecurity incidents in a timely manner. The organization staffs the SOC with skilled technical and operational personnel (e.g., security analysts, incident response personnel, systems security engineers) and implements a combination of technical, management, and operational controls (including monitoring, scanning, and forensics tools) to monitor, fuse, correlate, analyze, and respond to threat and security-relevant event data from multiple sources. These sources include perimeter defenses, network devices (e.g., routers, switches), and endpoint agent data feeds. The SOC provides a holistic situational awareness capability to help organizations determine the security posture of the system and organization. A SOC capability can be obtained in a variety of ways. Larger organizations may implement a dedicated SOC while smaller organizations may employ third-party organizations to provide such a capability.
","uuid":"71046ba3-bb4c-4e7a-a785-c11c737c4559","family":"Incident Response","parameters":[],"subControls":"","tests":[{"testId":"IR-04(14)[01]","uuid":"ee5fbda7-fc92-492a-bfa7-655f2fc12c4f","test":"Determine if a security operations center is established;It is important for an organization to have a strategy in place for addressing incidents that have been brought to the attention of the general public, have cast the organization in a negative light, or have affected the organization’s constituents (e.g., partners, customers). Such publicity can be extremely harmful to the organization and affect its ability to carry out its mission and business functions. Taking proactive steps to repair the organization’s reputation is an essential aspect of reestablishing the trust and confidence of its constituents.
","uuid":"b7a2015a-2ae4-4675-a6fa-5caa0d44675c","family":"Incident Response","parameters":[],"subControls":"","tests":[{"testId":"IR-04(15)(a)","uuid":"d170b8e1-903f-4374-a1a0-bfc16203edbe","test":"Determine if public relations associated with an incident are managed;Documenting incidents includes maintaining records about each incident, the status of the incident, and other pertinent information necessary for forensics as well as evaluating incident details, trends, and handling. Incident information can be obtained from a variety of sources, including network monitoring, incident reports, incident response teams, user complaints, supply chain partners, audit monitoring, physical access monitoring, and user and administrator reports. IR-4 provides information on the types of incidents that are appropriate for monitoring.
","uuid":"92e5ada6-530d-451a-9658-10e767dd473e","family":"Incident Response","parameters":[],"subControls":"","tests":[{"testId":"IR-05[01]","uuid":"414a9088-54ee-4baa-9409-0d6720d86c0a","test":"Determine if incidents are tracked;Automated mechanisms for tracking incidents and collecting and analyzing incident information include Computer Incident Response Centers or other electronic databases of incidents and network monitoring devices.
","uuid":"5b00894f-4fc4-4bf1-8fe5-f5cab1899640","family":"Incident Response","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"f8a20ab3-4c44-429c-b728-3ce95cdd87ea","text":"organization-defined automated mechanisms","parameterId":"ir-5.1_prm_1","default":" [Assignment: organization-defined automated mechanisms] "},{"constraints":"","displayName":"","guidance":"","uuid":"e48e69aa-2bb3-4c74-945e-92d2744ee9f8","text":"automated mechanisms","parameterId":"ir-05.01_odp.01","default":" [Assignment: organization defined automated mechanisms] "},{"constraints":"","displayName":"","guidance":"","uuid":"4ce40209-72f8-4bca-b797-adf71dc4da0c","text":"automated mechanisms","parameterId":"ir-05.01_odp.02","default":" [Assignment: organization defined automated mechanisms] "},{"constraints":"","displayName":"","guidance":"","uuid":"fc41312b-8b17-4c98-9462-41ff7d505e31","text":"automated mechanisms","parameterId":"ir-05.01_odp.03","default":" [Assignment: organization defined automated mechanisms] "}],"subControls":"","tests":[{"testId":"IR-05(01)[01]","uuid":"17fbab2f-3d8a-4bd4-ba3e-cc93fb1c6ebf","test":"Determine if incidents are tracked using [SELECTED PARAMETER VALUE(S): automated mechanisms ];The types of incidents reported, the content and timeliness of the reports, and the designated reporting authorities reflect applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Incident information can inform risk assessments, control effectiveness assessments, security requirements for acquisitions, and selection criteria for technology products.
","uuid":"3ea3e8fe-ef9c-4892-a388-44545968c3b1","family":"Incident Response","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"967232ce-3bc9-4048-ba9f-f1f74e09a076","text":"time period","parameterId":"ir-06_odp.01","default":" [Assignment: organization defined time period] "},{"constraints":"","displayName":"","guidance":"","uuid":"f6ec727c-2b09-49b9-82ab-c72fa753e070","text":"authorities","parameterId":"ir-06_odp.02","default":" [Assignment: organization defined authorities] "}],"subControls":"","tests":[{"testId":"IR-06a.","uuid":"bb5794b6-61d6-4870-92ab-ff9f6584aac7","test":"Determine if personnel is/are required to report suspected incidents to the organizational incident response capability within [SELECTED PARAMETER VALUE(S): time period ];The recipients of incident reports are specified in IR-6b . Automated reporting mechanisms include email, posting on websites (with automatic updates), and automated incident response tools and programs.
","uuid":"eb059530-b7fc-461d-8fe2-1464b22117ab","family":"Incident Response","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"2a5fd0b6-1193-479a-b9e6-862e8b721f56","text":"automated mechanisms","parameterId":"ir-06.01_odp","default":" [Assignment: organization defined automated mechanisms] "}],"subControls":"","tests":[{"testId":"IR-06(01)","uuid":"0117e2ad-ba5b-448f-b38f-a35019f30880","test":"Determine if incidents are reported using [SELECTED PARAMETER VALUE(S): automated mechanisms ].Reported incidents that uncover system vulnerabilities are analyzed by organizational personnel including system owners, mission and business owners, senior agency information security officers, senior agency officials for privacy, authorizing officials, and the risk executive (function). The analysis can serve to prioritize and initiate mitigation actions to address the discovered system vulnerability.
","uuid":"1f386613-acc3-4042-a13b-5644fabfd2f3","family":"Incident Response","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"b838f135-2302-467f-93a5-b69e80d8f660","text":"personnel or roles","parameterId":"ir-06.02_odp","default":" [Assignment: organization defined personnel or roles] "}],"subControls":"","tests":[{"testId":"IR-06(02)","uuid":"40aec9ac-b014-4d7d-a24c-98c9c8983dc7","test":"Determine if system vulnerabilities associated with reported incidents are reported to [SELECTED PARAMETER VALUE(S): personnel or roles ].Organizations involved in supply chain activities include product developers, system integrators, manufacturers, packagers, assemblers, distributors, vendors, and resellers. Entities that provide supply chain governance include the Federal Acquisition Security Council (FASC). Supply chain incidents include compromises or breaches that involve information technology products, system components, development processes or personnel, distribution processes, or warehousing facilities. Organizations determine the appropriate information to share and consider the value gained from informing external organizations about supply chain incidents, including the ability to improve processes or to identify the root cause of an incident.
","uuid":"cdecafa7-c727-4e3b-80dd-542ca29c5ed1","family":"Incident Response","parameters":[],"subControls":"","tests":[{"testId":"IR-06(03)","uuid":"ad16ec6f-db58-4839-b47a-4acf4844ac37","test":"Determine if incident information is provided 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.Incident response support resources provided by organizations include help desks, assistance groups, automated ticketing systems to open and track incident response tickets, and access to forensics services or consumer redress services, when required.
","uuid":"3e913b48-0aec-4822-91ed-4eb2d2d4421f","family":"Incident Response","parameters":[],"subControls":"","tests":[{"testId":"IR-07[01]","uuid":"e9981ffd-3ee6-42bb-a975-e35a42f6d3d1","test":"Determine if an incident response support resource, integral to the organizational incident response capability, is provided;Automated mechanisms can provide a push or pull capability for users to obtain incident response assistance. For example, individuals may have access to a website to query the assistance capability, or the assistance capability can proactively send incident response information to users (general distribution or targeted) as part of increasing understanding of current response capabilities and support.
","uuid":"8c21a4fb-cc49-4ffd-b90b-5fae183bb1c0","family":"Incident Response","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"edcb0220-1fda-4195-85f2-fc980b684461","text":"automated mechanisms","parameterId":"ir-07.01_odp","default":" [Assignment: organization defined automated mechanisms] "}],"subControls":"","tests":[{"testId":"IR-07(01)","uuid":"e364745a-ccf1-4da4-96d6-6b56d3a79e23","test":"Determine if the availability of incident response information and support is increased using [SELECTED PARAMETER VALUE(S): automated mechanisms ].External providers of a system protection capability include the Computer Network Defense program within the U.S. Department of Defense. External providers help to protect, monitor, analyze, detect, and respond to unauthorized activity within organizational information systems and networks. It may be beneficial to have agreements in place with external providers to clarify the roles and responsibilities of each party before an incident occurs.
","uuid":"6ad8aa28-3b5e-49d9-998f-8bf184e55066","family":"Incident Response","parameters":[],"subControls":"","tests":[{"testId":"IR-07(02)(a)","uuid":"a05df9f5-ad9a-4d6b-b506-747e11bf5d3b","test":"Determine if a direct, cooperative relationship is established between its incident response capability and external providers of the system protection capability;It is important that organizations develop and implement a coordinated approach to incident response. Organizational mission and business functions determine the structure of incident response capabilities. As part of the incident response capabilities, organizations consider the coordination and sharing of information with external organizations, including external service providers and other organizations involved in the supply chain. For incidents involving personally identifiable information (i.e., breaches), include a process to determine whether notice to oversight organizations or affected individuals is appropriate and provide that notice accordingly.
","uuid":"57a71fd2-38a8-4dc4-b87a-b22e3cea780f","family":"Incident Response","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"5334d267-c622-4bb5-9663-6905e34fd2f2","text":"organization-defined incident response personnel (identified by name and/or by role) and organizational elements","parameterId":"ir-8_prm_5","default":" [Assignment: organization-defined incident response personnel (identified by name and/or by role) and organizational elements] "},{"constraints":"","displayName":"","guidance":"","uuid":"c3e25f51-7d7f-41bc-8d71-2bae4c05aef4","text":"personnel or roles","parameterId":"ir-08_odp.01","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"d4033d83-6910-4f28-b335-f4e404e3600a","text":"frequency","parameterId":"ir-08_odp.02","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"fcd299ec-6510-4664-83e2-49edf21c1054","text":"entities, personnel, or roles","parameterId":"ir-08_odp.03","default":" [Assignment: organization defined entities, personnel, or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"a5ae2d38-94ce-4e1e-90bd-75b26d2bac37","text":"incident response personnel","parameterId":"ir-08_odp.04","default":" [Assignment: organization defined incident response personnel] "},{"constraints":"","displayName":"","guidance":"","uuid":"9cacd100-db9e-42ce-8ca3-a54976792412","text":"organizational elements","parameterId":"ir-08_odp.05","default":" [Assignment: organization defined organizational elements] "},{"constraints":"","displayName":"","guidance":"","uuid":"a0fb6b63-5f98-4032-ace6-881e5b6627c4","text":"incident response personnel","parameterId":"ir-08_odp.06","default":" [Assignment: organization defined incident response personnel] "},{"constraints":"","displayName":"","guidance":"","uuid":"fe532bfa-69f5-4d69-8da3-d24397634de6","text":"organizational elements","parameterId":"ir-08_odp.07","default":" [Assignment: organization defined organizational elements] "}],"subControls":"","tests":[{"testId":"IR-08a.01","uuid":"a61f2b00-cf05-4cf1-9f32-a9ee40b890f1","test":"Determine if an incident response plan is developed that provides the organization with a roadmap for implementing its incident response capability;Organizations may be required by law, regulation, or policy to follow specific procedures relating to breaches, including notice to individuals, affected organizations, and oversight bodies; standards of harm; and mitigation or other specific requirements.
","uuid":"9672df7d-cb91-4a8d-a0ca-9d5bf81da38f","family":"Incident Response","parameters":[],"subControls":"","tests":[{"testId":"IR-08(01)(a)","uuid":"77262158-b02d-43f9-a895-35547fbb352f","test":"Determine if the incident response plan for breaches involving personally identifiable information includes a process to determine if notice to individuals or other organizations, including oversight organizations, is needed;Information spillage refers to instances where information is placed on systems that are not authorized to process such information. Information spills occur when information that is thought to be a certain classification or impact level is transmitted to a system and subsequently is determined to be of a higher classification or impact level. At that point, corrective action is required. The nature of the response is based on the classification or impact level of the spilled information, the security capabilities of the system, the specific nature of the contaminated storage media, and the access authorizations of individuals with authorized access to the contaminated system. The methods used to communicate information about the spill after the fact do not involve methods directly associated with the actual spill to minimize the risk of further spreading the contamination before such contamination is isolated and eradicated.
","uuid":"ec64c07a-cec4-44f8-a14e-ac6e98b8848f","family":"Incident Response","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"e9557c1d-c141-4cec-92a9-d9251137d2f6","text":"personnel or roles","parameterId":"ir-09_odp.01","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"6c634976-e6e1-4caa-a7c9-0b1a5ef8d381","text":"personnel or roles","parameterId":"ir-09_odp.02","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"67a5d62c-e0ce-4daf-9d82-81180f0eb753","text":"actions","parameterId":"ir-09_odp.03","default":" [Assignment: organization defined actions] "}],"subControls":"","tests":[{"testId":"IR-09a.","uuid":"4374d7f5-95d6-49ab-bc1e-d18959f7df68","test":"Determine if [SELECTED PARAMETER VALUE(S): personnel or roles ] is/are assigned the responsibility to respond to information spills;Organizations establish requirements for responding to information spillage incidents in incident response plans. Incident response training on a regular basis helps to ensure that organizational personnel understand their individual responsibilities and what specific actions to take when spillage incidents occur.
","uuid":"6f635214-5459-466f-84b3-aa8c295b858b","family":"Incident Response","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"9e53a083-8612-4981-9cd0-9f5fa11e01a1","text":"frequency","parameterId":"ir-09.02_odp","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"IR-09(02)","uuid":"6186f087-db07-4f03-8037-86c94c572d09","test":"Determine if information spillage response training is provided [SELECTED PARAMETER VALUE(S): frequency ].Corrective actions for systems contaminated due to information spillages may be time-consuming. Personnel may not have access to the contaminated systems while corrective actions are being taken, which may potentially affect their ability to conduct organizational business.
","uuid":"3c131ccb-5427-4e35-873e-25a9b8f680b2","family":"Incident Response","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"5f783c1f-bf81-457c-a49b-db62b94b9d5a","text":"procedures","parameterId":"ir-09.03_odp","default":" [Assignment: organization defined procedures] "}],"subControls":"","tests":[{"testId":"IR-09(03)","uuid":"5f8c28e7-167f-458a-a62c-e1aab2ed016a","test":"Determine if [SELECTED PARAMETER VALUE(S): procedures ] are implemented to ensure that organizational personnel impacted by information spills can continue to carry out assigned tasks while contaminated systems are undergoing corrective actions.Controls include ensuring that personnel who are exposed to spilled information are made aware of the laws, executive orders, directives, regulations, policies, standards, and guidelines regarding the information and the restrictions imposed based on exposure to such information.
","uuid":"37198394-343c-4dfb-aea3-bfbfe6b2aa54","family":"Incident Response","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"9bbc9365-3aca-400a-86b9-1657e5ff4a84","text":"controls","parameterId":"ir-09.04_odp","default":" [Assignment: organization defined controls] "}],"subControls":"","tests":[{"testId":"IR-09(04)","uuid":"dd42405a-e02d-487c-88b4-a8021da3dd42","test":"Determine if [SELECTED PARAMETER VALUE(S): controls ] are employed for personnel exposed to information not within assigned access authorizations.Maintenance policy and procedures address the controls in the MA family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of maintenance policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission or business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to maintenance policy and procedures assessment or audit findings, security incidents or breaches, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure.
","uuid":"99605155-db9c-4388-b816-43e3f810c65e","family":"Maintenance","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"d37435e4-91f0-4b5f-9b29-1ec4805eac62","text":"organization-defined personnel or roles","parameterId":"ma-1_prm_1","default":" [Assignment: organization-defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"7bdde8e7-a359-43e9-a9a1-08124f17b993","text":"personnel or roles","parameterId":"ma-01_odp.01","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"2f0aec50-1a61-471f-8d23-fecca7528eed","text":"personnel or roles","parameterId":"ma-01_odp.02","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"6d0caa42-c977-4ce6-94ac-7f68639adefd","text":"[Selection (one or more): organization-level; mission/business process-level; system-level]","parameterId":"ma-01_odp.03","default":"[Selection (one or more): organization-level; mission/business process-level; system-level]"},{"constraints":"","displayName":"","guidance":"","uuid":"c07884c3-5785-4066-b04a-d9b6535d7226","text":"official","parameterId":"ma-01_odp.04","default":" [Assignment: organization defined official] "},{"constraints":"","displayName":"","guidance":"","uuid":"87c645e4-bcea-4d93-bd0c-9a77b6a28602","text":"frequency","parameterId":"ma-01_odp.05","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"a5b8fcaf-9122-4d72-8107-1cabbc3913ab","text":"events","parameterId":"ma-01_odp.06","default":" [Assignment: organization defined events] "},{"constraints":"","displayName":"","guidance":"","uuid":"18c93902-0dc8-40fb-9f19-556d90927a3f","text":"frequency","parameterId":"ma-01_odp.07","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"97949452-6e7d-48d5-8d3c-00a551130a4b","text":"events","parameterId":"ma-01_odp.08","default":" [Assignment: organization defined events] "}],"subControls":"","tests":[{"testId":"MA-01a.[01]","uuid":"e43b223f-f0b1-4a2b-8923-2f6d76a04eb8","test":"Determine if a maintenance policy is developed and documented;Controlling system maintenance addresses the information security aspects of the system maintenance program and applies to all types of maintenance to system components conducted by local or nonlocal entities. Maintenance includes peripherals such as scanners, copiers, and printers. Information necessary for creating effective maintenance records includes the date and time of maintenance, a description of the maintenance performed, names of the individuals or group performing the maintenance, name of the escort, and system components or equipment that are removed or replaced. Organizations consider supply chain-related risks associated with replacement components for systems.
","uuid":"2879e9ef-dd5d-4e21-97cc-67312a04900d","family":"Maintenance","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"95ed1a8b-a6a8-4eda-a405-602e76a09195","text":"personnel or roles","parameterId":"ma-02_odp.01","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"e75746b7-ae63-44ea-83ca-aade25e5934d","text":"information","parameterId":"ma-02_odp.02","default":" [Assignment: organization defined information] "},{"constraints":"","displayName":"","guidance":"","uuid":"2c4ee830-d100-4214-b8ab-51f39db0468f","text":"information","parameterId":"ma-02_odp.03","default":" [Assignment: organization defined information] "}],"subControls":"","tests":[{"testId":"MA-02a.[01]","uuid":"1677f5ce-37fd-4e2b-838e-b64d21a5451d","test":"Determine if maintenance, repair, and replacement of system components are scheduled in accordance with manufacturer or vendor specifications and/or organizational requirements;The use of automated mechanisms to manage and control system maintenance programs and activities helps to ensure the generation of timely, accurate, complete, and consistent maintenance records.
","uuid":"19973e9f-63c4-433a-ad12-55d77f2d8264","family":"Maintenance","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"2224d312-250a-4cc9-9377-ffd15015b760","text":"organization-defined automated mechanisms","parameterId":"ma-2.2_prm_1","default":" [Assignment: organization-defined automated mechanisms] "},{"constraints":"","displayName":"","guidance":"","uuid":"cb23855c-c398-4900-987e-37385e5c66dd","text":"automated mechanisms","parameterId":"ma-02.02_odp.01","default":" [Assignment: organization defined automated mechanisms] "},{"constraints":"","displayName":"","guidance":"","uuid":"c9c46ab0-b9b8-40db-96d3-c813726ccb39","text":"automated mechanisms","parameterId":"ma-02.02_odp.02","default":" [Assignment: organization defined automated mechanisms] "},{"constraints":"","displayName":"","guidance":"","uuid":"2d34e676-005f-4e8e-899c-e6fad69c5607","text":"automated mechanisms","parameterId":"ma-02.02_odp.03","default":" [Assignment: organization defined automated mechanisms] "}],"subControls":"","tests":[{"testId":"MA-02(02)(a)[01]","uuid":"d2127fbc-2003-4477-97fe-042ae15e0d42","test":"Determine if [SELECTED PARAMETER VALUE(S): automated mechanisms ] are used to schedule maintenance, repair, and replacement actions for the system;Approving, controlling, monitoring, and reviewing maintenance tools address security-related issues associated with maintenance tools that are not within system authorization boundaries and are used specifically for diagnostic and repair actions on organizational systems. Organizations have flexibility in determining roles for the approval of maintenance tools and how that approval is documented. A periodic review of maintenance tools facilitates the withdrawal of approval for outdated, unsupported, irrelevant, or no-longer-used tools. Maintenance tools can include hardware, software, and firmware items and may be pre-installed, brought in with maintenance personnel on media, cloud-based, or downloaded from a website. Such tools can be vehicles for transporting malicious code, either intentionally or unintentionally, into a facility and subsequently into systems. Maintenance tools can include hardware and software diagnostic test equipment and packet sniffers. The hardware and software components that support maintenance and are a part of the system (including the software implementing utilities such as ping,
\nls,
\nipconfig,
or the hardware and software implementing the monitoring port of an Ethernet switch) are not addressed by maintenance tools.
Maintenance tools can be directly brought into a facility by maintenance personnel or downloaded from a vendor’s website. If, upon inspection of the maintenance tools, organizations determine that the tools have been modified in an improper manner or the tools contain malicious code, the incident is handled consistent with organizational policies and procedures for incident handling.
","uuid":"e9187b0e-f260-4f3b-b35b-cd77f24e0bb0","family":"Maintenance","parameters":[],"subControls":"","tests":[{"testId":"MA-03(01)","uuid":"12a21383-db0b-4ab0-8b69-a811a12f8bd1","test":"Determine if maintenance tools used by maintenance personnel are inspected for improper or unauthorized modifications.If, upon inspection of media containing maintenance, diagnostic, and test programs, organizations determine that the media contains malicious code, the incident is handled consistent with organizational incident handling policies and procedures.
","uuid":"1e70100d-3a85-4a30-954f-98a528338584","family":"Maintenance","parameters":[],"subControls":"","tests":[{"testId":"MA-03(02)","uuid":"9679c45b-06e6-47e6-ac80-16ccefed0948","test":"Determine if media containing diagnostic and test programs are checked for malicious code before the media are used in the system.Organizational information includes all information owned by organizations and any information provided to organizations for which the organizations serve as information stewards.
","uuid":"6d58f7c5-970f-45f3-ac5b-6fde848e5ca0","family":"Maintenance","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"94640ad5-9364-4927-8bfa-8fedb91979c1","text":"personnel or roles","parameterId":"ma-03.03_odp","default":" [Assignment: organization defined personnel or roles] "}],"subControls":"","tests":[{"testId":"MA-03(03)(a)","uuid":"b03f03ab-c7af-4203-be9a-7bbaa1cefd37","test":"Determine if the removal of maintenance equipment containing organizational information is prevented by verifying that there is no organizational information contained on the equipment; orRestricting the use of maintenance tools to only authorized personnel applies to systems that are used to carry out maintenance functions.
","uuid":"f83e5440-ae3e-443d-9b59-4b99a5caf287","family":"Maintenance","parameters":[],"subControls":"","tests":[{"testId":"MA-03(04)","uuid":"5197a6d5-11d6-4564-880b-9fbe80a00e39","test":"Determine if the use of maintenance tools is restricted to authorized personnel only.Maintenance tools that execute with increased system privilege can result in unauthorized access to organizational information and assets that would otherwise be inaccessible.
","uuid":"97ead2a8-c838-4a86-a950-86317f94334f","family":"Maintenance","parameters":[],"subControls":"","tests":[{"testId":"MA-03(05)","uuid":"927a20cd-b2d0-4efb-98a6-ea33e0cb9b49","test":"Determine if the use of maintenance tools that execute with increased privilege is monitored.Maintenance tools using outdated and/or unpatched software can provide a threat vector for adversaries and result in a significant vulnerability for organizations.
","uuid":"d79177e0-9123-4aeb-b4e4-bdd81a4eebdc","family":"Maintenance","parameters":[],"subControls":"","tests":[{"testId":"MA-03(06)","uuid":"f332b4c5-6f4d-464e-80e3-2b9b14ab63db","test":"Determine if maintenance tools are inspected to ensure that the latest software updates and patches are installed.Nonlocal maintenance and diagnostic activities are conducted by individuals who communicate through either an external or internal network. Local maintenance and diagnostic activities are carried out by individuals who are physically present at the system location and not communicating across a network connection. Authentication techniques used to establish nonlocal maintenance and diagnostic sessions reflect the network access requirements in IA-2 . Strong authentication requires authenticators that are resistant to replay attacks and employ multi-factor authentication. Strong authenticators include PKI where certificates are stored on a token protected by a password, passphrase, or biometric. Enforcing requirements in MA-4 is accomplished, in part, by other controls. SP 800-63B provides additional guidance on strong authentication and authenticators.
","uuid":"c36f0adb-b65a-4ae1-b211-7ba4f13ecd7c","family":"Maintenance","parameters":[],"subControls":"","tests":[{"testId":"MA-04a.[01]","uuid":"5887bc01-0680-40ef-80aa-df9091e7acb4","test":"Determine if nonlocal maintenance and diagnostic activities are approved;Audit logging for nonlocal maintenance is enforced by AU-2 . Audit events are defined in AU-2a.
","uuid":"848b384f-f57f-4472-9656-3a0d11c221ca","family":"Maintenance","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"16b1083b-364a-4163-a679-0187736bf4c7","text":"organization-defined audit events","parameterId":"ma-4.1_prm_1","default":" [Assignment: organization-defined audit events] "},{"constraints":"","displayName":"","guidance":"","uuid":"883f5a35-7349-494b-9738-5e875f1565a9","text":"audit events","parameterId":"ma-04.01_odp.01","default":" [Assignment: organization defined audit events] "},{"constraints":"","displayName":"","guidance":"","uuid":"6ca2c304-87a3-44a8-9957-a9256ec8eb95","text":"audit events","parameterId":"ma-04.01_odp.02","default":" [Assignment: organization defined audit events] "}],"subControls":"","tests":[{"testId":"MA-04(01)(a)[01]","uuid":"8ef37729-4896-43c5-9f28-136fd17b20a7","test":"Determine if [SELECTED PARAMETER VALUE(S): audit events ] are logged for nonlocal maintenance sessions;Comparable security capability on systems, diagnostic tools, and equipment providing maintenance services implies that the implemented controls on those systems, tools, and equipment are at least as comprehensive as the controls on the system being serviced.
","uuid":"1c919624-028d-444d-8e26-b711b19161da","family":"Maintenance","parameters":[],"subControls":"","tests":[{"testId":"MA-04(03)(a)[01]","uuid":"aa6c2e0d-426a-4de4-aa76-2f71e5eed153","test":"Determine if nonlocal maintenance services are required to be performed from a system that implements a security capability comparable to the capability implemented on the system being serviced;Communications paths can be logically separated using encryption.
","uuid":"8b90a046-0458-49ab-817a-d2bef6df51f2","family":"Maintenance","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"4b696a3a-eedc-4088-8993-37b4444de5b9","text":"authenticators that are replay resistant","parameterId":"ma-04.04_odp","default":" [Assignment: organization defined authenticators that are replay resistant] "}],"subControls":"","tests":[{"testId":"MA-04(04)(a)","uuid":"7be6b791-a150-4a93-ab88-a2c82b1e5ec2","test":"Determine if nonlocal maintenance sessions are protected by employing [SELECTED PARAMETER VALUE(S): authenticators that are replay resistant ];Notification may be performed by maintenance personnel. Approval of nonlocal maintenance is accomplished by personnel with sufficient information security and system knowledge to determine the appropriateness of the proposed maintenance.
","uuid":"989ebb80-c166-4bff-92a1-b47544995b5c","family":"Maintenance","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"99f53ae7-6784-4307-bae2-dc96e9a01672","text":"personnel or roles","parameterId":"ma-04.05_odp.01","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"bed73172-9e77-4b13-b0fd-5646b08d2b54","text":"personnel and roles","parameterId":"ma-04.05_odp.02","default":" [Assignment: organization defined personnel and roles] "}],"subControls":"","tests":[{"testId":"MA-04(05)(a)","uuid":"2962e842-b9c7-49e7-add1-2c97a0584a30","test":"Determine if the approval of each nonlocal maintenance session is required by [SELECTED PARAMETER VALUE(S): personnel or roles ];Failure to protect nonlocal maintenance and diagnostic communications can result in unauthorized individuals gaining access to organizational information. Unauthorized access during remote maintenance sessions can result in a variety of hostile actions, including malicious code insertion, unauthorized changes to system parameters, and exfiltration of organizational information. Such actions can result in the loss or degradation of mission or business capabilities.
","uuid":"341f3001-653b-4541-bf86-950fb42bab47","family":"Maintenance","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"4419fcc2-d8f6-473b-952c-f989f518c627","text":"cryptographic mechanisms","parameterId":"ma-04.06_odp","default":" [Assignment: organization defined cryptographic mechanisms] "}],"subControls":"","tests":[{"testId":"MA-04(06)[01]","uuid":"6d170bb1-992a-442f-b980-8834bae195f2","test":"Determine if [SELECTED PARAMETER VALUE(S): cryptographic mechanisms ] are implemented to protect the integrity of nonlocal maintenance and diagnostic communications;Verifying the termination of a connection once maintenance is completed ensures that connections established during nonlocal maintenance and diagnostic sessions have been terminated and are no longer available for use.
","uuid":"f6bf0ffc-fdbf-4652-8303-d7edd96f7c7c","family":"Maintenance","parameters":[],"subControls":"","tests":[{"testId":"MA-04(07)[01]","uuid":"9ed675e1-4c86-4659-8785-559bdba02ff0","test":"Determine if session connection termination is verified after the completion of nonlocal maintenance and diagnostic sessions;Maintenance personnel refers to individuals who perform hardware or software maintenance on organizational systems, while PE-2 addresses physical access for individuals whose maintenance duties place them within the physical protection perimeter of the systems. Technical competence of supervising individuals relates to the maintenance performed on the systems, while having required access authorizations refers to maintenance on and near the systems. Individuals not previously identified as authorized maintenance personnel—such as information technology manufacturers, vendors, systems integrators, and consultants—may require privileged access to organizational systems, such as when they are required to conduct maintenance activities with little or no notice. Based on organizational assessments of risk, organizations may issue temporary credentials to these individuals. Temporary credentials may be for one-time use or for very limited time periods.
","uuid":"d1ad35f6-5015-477c-b60b-576c2bf810a0","family":"Maintenance","parameters":[],"subControls":"","tests":[{"testId":"MA-05a.[01]","uuid":"3fbac5ee-d495-4f75-92f8-274f9373142c","test":"Determine if a process for maintenance personnel authorization is established;Procedures for individuals who lack appropriate security clearances or who are not U.S. citizens are intended to deny visual and electronic access to classified or controlled unclassified information contained on organizational systems. Procedures for the use of maintenance personnel can be documented in security plans for the systems.
","uuid":"b15ec3e7-968a-4492-a389-d756dc7cfb06","family":"Maintenance","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"725d73c4-e450-448d-ae63-83a79adcb2f6","text":"alternate controls","parameterId":"ma-05.01_odp","default":" [Assignment: organization defined alternate controls] "}],"subControls":"","tests":[{"testId":"MA-05(01)(a)(01)","uuid":"892cce9c-19fc-45e5-894d-cd04f6c7796c","test":"Determine if procedures for the use of maintenance personnel who lack appropriate security clearances or are not u.s. citizens are implemented and include approved organizational personnel who are fully cleared, have appropriate access authorizations, and are technically qualified escorting and supervising maintenance personnel without the needed access authorization during the performance of maintenance and diagnostic activities;Personnel who conduct maintenance on organizational systems may be exposed to classified information during the course of their maintenance activities. To mitigate the inherent risk of such exposure, organizations use maintenance personnel that are cleared (i.e., possess security clearances) to the classification level of the information stored on the system.
","uuid":"f87710a1-69df-4db3-983f-6224fae83c9f","family":"Maintenance","parameters":[],"subControls":"","tests":[{"testId":"MA-05(02)[01]","uuid":"2a123a4a-5df7-4b7b-9819-0c65ab77202b","test":"Determine if personnel performing maintenance and diagnostic activities on a system processing, storing, or transmitting classified information possess security clearances for at least the highest classification level and for compartments of information on the system;Personnel who conduct maintenance on organizational systems may be exposed to classified information during the course of their maintenance activities. If access to classified information on organizational systems is restricted to U.S. citizens, the same restriction is applied to personnel performing maintenance on those systems.
","uuid":"cdb163d9-0b9f-44be-9db8-5765f1d27506","family":"Maintenance","parameters":[],"subControls":"","tests":[{"testId":"MA-05(03)","uuid":"a57b94b0-0d2f-469b-a9e2-074ed0015d2e","test":"Determine if personnel performing maintenance and diagnostic activities on a system processing, storing, or transmitting classified information are u.s. citizens.Personnel who conduct maintenance and diagnostic activities on organizational systems may be exposed to classified information. If non-U.S. citizens are permitted to perform maintenance and diagnostics activities on classified systems, then additional vetting is required to ensure agreements and restrictions are not being violated.
","uuid":"f3643cb3-4cb9-41bc-a142-998451d96296","family":"Maintenance","parameters":[],"subControls":"","tests":[{"testId":"MA-05(04)(a)","uuid":"6bdb1b06-3496-481b-b1b0-34176b255b44","test":"Determine if 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;Personnel who perform maintenance activities in other capacities not directly related to the system include physical plant personnel and custodial personnel.
","uuid":"f4221a18-6493-4101-afa6-229ad8d6c854","family":"Maintenance","parameters":[],"subControls":"","tests":[{"testId":"MA-05(05)","uuid":"69e8c384-3453-40ac-83d3-5dee3ccba6b7","test":"Determine if non-escorted personnel performing maintenance activities not directly associated with the system but in the physical proximity of the system have required access authorizations.Organizations specify the system components that result in increased risk to organizational operations and assets, individuals, other organizations, or the Nation when the functionality provided by those components is not operational. Organizational actions to obtain maintenance support include having appropriate contracts in place.
","uuid":"b3d02dc3-0a83-4563-ad5e-e3e6f3aba70e","family":"Maintenance","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"46dfa84c-9cc0-4627-a6c8-a9cdc929cbd8","text":"system components","parameterId":"ma-06_odp.01","default":" [Assignment: organization defined system components] "},{"constraints":"","displayName":"","guidance":"","uuid":"307f74ef-787d-4a9d-9cbb-ec43a6fbf6ba","text":"time period","parameterId":"ma-06_odp.02","default":" [Assignment: organization defined time period] "}],"subControls":"","tests":[{"testId":"MA-06","uuid":"a1206711-2777-415a-a8e6-44868308b1b4","test":"Determine if maintenance support and/or spare parts are obtained for [SELECTED PARAMETER VALUE(S): system components ] within [SELECTED PARAMETER VALUE(S): time period ] of failure.Preventive maintenance includes proactive care and the servicing of system components to maintain organizational equipment and facilities in satisfactory operating condition. Such maintenance provides for the systematic inspection, tests, measurements, adjustments, parts replacement, detection, and correction of incipient failures either before they occur or before they develop into major defects. The primary goal of preventive maintenance is to avoid or mitigate the consequences of equipment failures. Preventive maintenance is designed to preserve and restore equipment reliability by replacing worn components before they fail. Methods of determining what preventive (or other) failure management policies to apply include original equipment manufacturer recommendations; statistical failure records; expert opinion; maintenance that has already been conducted on similar equipment; requirements of codes, laws, or regulations within a jurisdiction; or measured values and performance indications.
","uuid":"a0fed42d-9b67-403d-a4c7-e77f62238b99","family":"Maintenance","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"f99617a5-92a3-4df4-8ca2-581b237c65b9","text":"system components","parameterId":"ma-06.01_odp.01","default":" [Assignment: organization defined system components] "},{"constraints":"","displayName":"","guidance":"","uuid":"898d75c3-1005-4a35-a8ca-78a444859502","text":"time intervals","parameterId":"ma-06.01_odp.02","default":" [Assignment: organization defined time intervals] "}],"subControls":"","tests":[{"testId":"MA-06(01)","uuid":"da59458b-9c3d-4211-aa25-f6cb7a12b817","test":"Determine if preventive maintenance is performed on [SELECTED PARAMETER VALUE(S): system components ] at [SELECTED PARAMETER VALUE(S): time intervals ].Predictive maintenance evaluates the condition of equipment by performing periodic or continuous (online) equipment condition monitoring. The goal of predictive maintenance is to perform maintenance at a scheduled time when the maintenance activity is most cost-effective and before the equipment loses performance within a threshold. The predictive component of predictive maintenance stems from the objective of predicting the future trend of the equipment's condition. The predictive maintenance approach employs principles of statistical process control to determine at what point in the future maintenance activities will be appropriate. Most predictive maintenance inspections are performed while equipment is in service, thus minimizing disruption of normal system operations. Predictive maintenance can result in substantial cost savings and higher system reliability.
","uuid":"f5ef09d1-f66c-43eb-97b5-46d5b408bbc5","family":"Maintenance","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"9e66c77a-5e85-4a1c-afe5-4d7ee1e513ad","text":"system components","parameterId":"ma-06.02_odp.01","default":" [Assignment: organization defined system components] "},{"constraints":"","displayName":"","guidance":"","uuid":"4866fe86-d993-4968-882e-f45dc2ce312d","text":"time intervals","parameterId":"ma-06.02_odp.02","default":" [Assignment: organization defined time intervals] "}],"subControls":"","tests":[{"testId":"MA-06(02)","uuid":"22972916-0dcb-4204-8d8f-5fbd229c34fa","test":"Determine if predictive maintenance is performed on [SELECTED PARAMETER VALUE(S): system components ] at [SELECTED PARAMETER VALUE(S): time intervals ].A computerized maintenance management system maintains a database of information about the maintenance operations of organizations and automates the processing of equipment condition data to trigger maintenance planning, execution, and reporting.
","uuid":"8e0381be-89a5-4073-b910-52d84fa1ff51","family":"Maintenance","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"65ec8701-a7e8-44e5-8bef-3f915e4c1bfe","text":"automated mechanisms","parameterId":"ma-06.03_odp","default":" [Assignment: organization defined automated mechanisms] "}],"subControls":"","tests":[{"testId":"MA-06(03)","uuid":"378de171-8a6d-407b-8bd3-c3e4b31f0548","test":"Determine if predictive maintenance data is transferred to a maintenance management system using [SELECTED PARAMETER VALUE(S): automated mechanisms ].Field maintenance is the type of maintenance conducted on a system or system component after the system or component has been deployed to a specific site (i.e., operational environment). In certain instances, field maintenance (i.e., local maintenance at the site) may not be executed with the same degree of rigor or with the same quality control checks as depot maintenance. For critical systems designated as such by the organization, it may be necessary to restrict or prohibit field maintenance at the local site and require that such maintenance be conducted in trusted facilities with additional controls.
","uuid":"9bf4b7c5-1382-4ab9-bf49-4bf2ab0e27d1","family":"Maintenance","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"4ba0a537-1251-43ee-8cee-e61fd6307993","text":"systems or system components","parameterId":"ma-07_odp.01","default":" [Assignment: organization defined systems or system components] "},{"constraints":"","displayName":"","guidance":"","uuid":"e7d476a4-0733-4e24-a691-e066a3bbd225","text":"trusted maintenance facilities","parameterId":"ma-07_odp.02","default":" [Assignment: organization defined trusted maintenance facilities] "}],"subControls":"","tests":[{"testId":"MA-07","uuid":"0e09942d-6bba-4096-b218-fc2e8e0e9872","test":"Determine if field maintenance on [SELECTED PARAMETER VALUE(S): systems or system components ] are restricted or prohibited to [SELECTED PARAMETER VALUE(S): trusted maintenance facilities ].Media protection policy and procedures address the controls in the MP family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of media protection policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission or business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to media protection policy and procedures include assessment or audit findings, security incidents or breaches, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure.
","uuid":"5d15abb3-0cdb-40d1-8305-e541daf3d150","family":"Media Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"a04e6510-8393-4731-9c86-1610656714c3","text":"organization-defined personnel or roles","parameterId":"mp-1_prm_1","default":" [Assignment: organization-defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"78b2e4a6-a3dc-4f96-8bc5-ab73a2ebfc98","text":"personnel or roles","parameterId":"mp-01_odp.01","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"567f4ace-4489-442d-b5fe-a12d7886ca08","text":"personnel or roles","parameterId":"mp-01_odp.02","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"819dc7e4-b869-4c54-9fd1-c5495a90716f","text":"[Selection (one or more): organization-level; mission/business process-level; system-level]","parameterId":"mp-01_odp.03","default":"[Selection (one or more): organization-level; mission/business process-level; system-level]"},{"constraints":"","displayName":"","guidance":"","uuid":"247fe4f5-8e1e-4dd5-a315-13174f3a3127","text":"official","parameterId":"mp-01_odp.04","default":" [Assignment: organization defined official] "},{"constraints":"","displayName":"","guidance":"","uuid":"28644884-9dff-46ca-8dfa-3c31a24b041d","text":"frequency","parameterId":"mp-01_odp.05","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"b16920ed-809f-4136-8dba-3ceb66283335","text":"events","parameterId":"mp-01_odp.06","default":" [Assignment: organization defined events] "},{"constraints":"","displayName":"","guidance":"","uuid":"64be5dcd-ae50-4903-a460-17f71e62c0dd","text":"frequency","parameterId":"mp-01_odp.07","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"8450456d-49d3-473b-8eda-cc8a84f4c258","text":"events","parameterId":"mp-01_odp.08","default":" [Assignment: organization defined events] "}],"subControls":"","tests":[{"testId":"MP-01a.[01]","uuid":"c7fad390-ac69-4576-bd9e-3a8c6dbc57f0","test":"Determine if a media protection policy is developed and documented;System media includes digital and non-digital media. Digital media includes flash drives, diskettes, magnetic tapes, external or removable hard disk drives (e.g., solid state, magnetic), compact discs, and digital versatile discs. Non-digital media includes paper and microfilm. Denying access to patient medical records in a community hospital unless the individuals seeking access to such records are authorized healthcare providers is an example of restricting access to non-digital media. Limiting access to the design specifications stored on compact discs in the media library to individuals on the system development team is an example of restricting access to digital media.
","uuid":"700a53f4-a0d5-4901-ab28-9e8f72acae38","family":"Media Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"f12607c0-e817-4748-a5d8-9171da31f02d","text":"organization-defined types of digital and/or non-digital media","parameterId":"mp-2_prm_1","default":" [Assignment: organization-defined types of digital and/or non-digital media] "},{"constraints":"","displayName":"","guidance":"","uuid":"db3d36c2-42ae-4770-b641-996a0b736e5c","text":"organization-defined personnel or roles","parameterId":"mp-2_prm_2","default":" [Assignment: organization-defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"0fa1f182-ed23-4db2-841d-40acca5dffe5","text":"types of digital media","parameterId":"mp-02_odp.01","default":" [Assignment: organization defined types of digital media] "},{"constraints":"","displayName":"","guidance":"","uuid":"e10fe0d1-5040-4557-b321-8247679cd3c2","text":"personnel or roles","parameterId":"mp-02_odp.02","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"667f7146-7d31-4554-a860-aeefbe8d3972","text":"types of non-digital media","parameterId":"mp-02_odp.03","default":" [Assignment: organization defined types of non-digital media] "},{"constraints":"","displayName":"","guidance":"","uuid":"0c564405-cad3-4c35-af1e-c0d80335d6f7","text":"personnel or roles","parameterId":"mp-02_odp.04","default":" [Assignment: organization defined personnel or roles] "}],"subControls":"","tests":[{"testId":"MP-02[01]","uuid":"8cb5bf5a-daf0-4655-bfbc-aa4bbdefd638","test":"Determine if access to [SELECTED PARAMETER VALUE(S): types of digital media ] is restricted to [SELECTED PARAMETER VALUE(S): personnel or roles ];Security marking refers to the application or use of human-readable security attributes. Digital media includes diskettes, magnetic tapes, external or removable hard disk drives (e.g., solid state, magnetic), flash drives, compact discs, and digital versatile discs. Non-digital media includes paper and microfilm. Controlled unclassified information is defined by the National Archives and Records Administration along with the appropriate safeguarding and dissemination requirements for such information and is codified in 32 CFR 2002 . Security markings are generally not required for media that contains information determined by organizations to be in the public domain or to be publicly releasable. Some organizations may require markings for public information indicating that the information is publicly releasable. System media marking reflects applicable laws, executive orders, directives, policies, regulations, standards, and guidelines.
","uuid":"afd8e230-b517-4901-98e1-75477f54b3cc","family":"Media Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"f5b25508-4cfd-4025-84f3-80b8403de90c","text":"types of media exempted from marking","parameterId":"mp-03_odp.01","default":" [Assignment: organization defined types of media exempted from marking] "},{"constraints":"","displayName":"","guidance":"","uuid":"6d63fe6c-2c41-4b47-9962-24aee53ab44f","text":"controlled areas","parameterId":"mp-03_odp.02","default":" [Assignment: organization defined controlled areas] "}],"subControls":"","tests":[{"testId":"MP-03a.","uuid":"4027add6-d477-4873-bdf6-15bc6b2bd863","test":"Determine if system media is marked to indicate distribution limitations, handling caveats, and applicable security markings (if any) of the information;System media includes digital and non-digital media. Digital media includes flash drives, diskettes, magnetic tapes, external or removable hard disk drives (e.g., solid state, magnetic), compact discs, and digital versatile discs. Non-digital media includes paper and microfilm. Physically controlling stored media includes conducting inventories, ensuring procedures are in place to allow individuals to check out and return media to the library, and maintaining accountability for stored media. Secure storage includes a locked drawer, desk, or cabinet or a controlled media library. The type of media storage is commensurate with the security category or classification of the information on the media. Controlled areas are spaces that provide physical and procedural controls to meet the requirements established for protecting information and systems. Fewer controls may be needed for media that contains information determined to be in the public domain, publicly releasable, or have limited adverse impacts on organizations, operations, or individuals if accessed by other than authorized personnel. In these situations, physical access controls provide adequate protection.
","uuid":"b0c0f1c1-9aa1-4950-8b7f-04954fdf92a8","family":"Media Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"7150c102-4ba2-4873-ac88-83f925714dce","text":"organization-defined types of digital and/or non-digital media","parameterId":"mp-4_prm_1","default":" [Assignment: organization-defined types of digital and/or non-digital media] "},{"constraints":"","displayName":"","guidance":"","uuid":"c8753d92-2b27-4119-852e-91ce2298a6e6","text":"organization-defined controlled areas","parameterId":"mp-4_prm_2","default":" [Assignment: organization-defined controlled areas] "},{"constraints":"","displayName":"","guidance":"","uuid":"1a0ac946-7753-446a-9014-01c58dc03fe9","text":"types of digital media","parameterId":"mp-04_odp.01","default":" [Assignment: organization defined types of digital media] "},{"constraints":"","displayName":"","guidance":"","uuid":"e36dc87b-0abc-454d-b50b-08981b2a47c7","text":"types of non-digital media","parameterId":"mp-04_odp.02","default":" [Assignment: organization defined types of non-digital media] "},{"constraints":"","displayName":"","guidance":"","uuid":"095e8ec8-ce0d-4675-b072-1056100b0051","text":"types of digital media","parameterId":"mp-04_odp.03","default":" [Assignment: organization defined types of digital media] "},{"constraints":"","displayName":"","guidance":"","uuid":"85582a79-6e53-418e-be81-3e1287b381e6","text":"types of non-digital media","parameterId":"mp-04_odp.04","default":" [Assignment: organization defined types of non-digital media] "},{"constraints":"","displayName":"","guidance":"","uuid":"3e225431-234a-4626-a9c6-85397142d58d","text":"controlled areas","parameterId":"mp-04_odp.05","default":" [Assignment: organization defined controlled areas] "},{"constraints":"","displayName":"","guidance":"","uuid":"fa5b8539-db25-41c2-bdde-a9c1841a1e83","text":"controlled areas","parameterId":"mp-04_odp.06","default":" [Assignment: organization defined controlled areas] "}],"subControls":"","tests":[{"testId":"MP-04a.[01]","uuid":"1130dd02-1ece-4fce-a21c-7178bf11596f","test":"Determine if [SELECTED PARAMETER VALUE(S): types of digital media ] are physically controlled;Automated mechanisms include keypads, biometric readers, or card readers on the external entries to media storage areas.
","uuid":"31d144b3-16df-4c83-8a83-4cae11decda0","family":"Media Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"f81ab67a-9ec7-46ee-bae7-69c7fa9d8be0","text":"organization-defined automated mechanisms","parameterId":"mp-4.2_prm_1","default":" [Assignment: organization-defined automated mechanisms] "},{"constraints":"","displayName":"","guidance":"","uuid":"324775d7-964c-4c22-97bf-d3bbcdec2ff1","text":"automated mechanisms","parameterId":"mp-04.02_odp.01","default":" [Assignment: organization defined automated mechanisms] "},{"constraints":"","displayName":"","guidance":"","uuid":"fc263c55-953d-4ca5-abd5-311d832855d4","text":"automated mechanisms","parameterId":"mp-04.02_odp.02","default":" [Assignment: organization defined automated mechanisms] "},{"constraints":"","displayName":"","guidance":"","uuid":"4fed5103-4847-4653-8254-ef20db53a0e7","text":"automated mechanisms","parameterId":"mp-04.02_odp.03","default":" [Assignment: organization defined automated mechanisms] "}],"subControls":"","tests":[{"testId":"MP-04(02)[01]","uuid":"222a276a-ddf1-46f7-b9ec-547be7c3087c","test":"Determine if access to media storage areas is restricted using [SELECTED PARAMETER VALUE(S): automated mechanisms ];System media includes digital and non-digital media. Digital media includes flash drives, diskettes, magnetic tapes, external or removable hard disk drives (e.g., solid state and magnetic), compact discs, and digital versatile discs. Non-digital media includes microfilm and paper. Controlled areas are spaces for which organizations provide physical or procedural controls to meet requirements established for protecting information and systems. Controls to protect media during transport include cryptography and locked containers. Cryptographic mechanisms can provide confidentiality and integrity protections depending on the mechanisms implemented. Activities associated with media transport include releasing media for transport, ensuring that media enters the appropriate transport processes, and the actual transport. Authorized transport and courier personnel may include individuals external to the organization. Maintaining accountability of media during transport includes restricting transport activities to authorized personnel and tracking and/or obtaining records of transport activities as the media moves through the transportation system to prevent and detect loss, destruction, or tampering. Organizations establish documentation requirements for activities associated with the transport of system media in accordance with organizational assessments of risk. Organizations maintain the flexibility to define record-keeping methods for the different types of media transport as part of a system of transport-related records.
","uuid":"3bee0a9c-b408-45e3-8b4a-b29462125a8c","family":"Media Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"7fa2b5d3-f7c3-4ee1-bed9-63497ef933d2","text":"organization-defined controls","parameterId":"mp-5_prm_2","default":" [Assignment: organization-defined controls] "},{"constraints":"","displayName":"","guidance":"","uuid":"91d7e880-3d33-4578-b27d-14d9f74c47eb","text":"types of system media","parameterId":"mp-05_odp.01","default":" [Assignment: organization defined types of system media] "},{"constraints":"","displayName":"","guidance":"","uuid":"b9d627ec-b614-4b92-b049-ceedd21ee53c","text":"controls","parameterId":"mp-05_odp.02","default":" [Assignment: organization defined controls] "},{"constraints":"","displayName":"","guidance":"","uuid":"62638515-be31-435d-9a91-74ccdec90104","text":"controls","parameterId":"mp-05_odp.03","default":" [Assignment: organization defined controls] "}],"subControls":"","tests":[{"testId":"MP-05a.[01]","uuid":"8c6e3052-d475-4455-80fa-5f8c2ca63fb4","test":"Determine if [SELECTED PARAMETER VALUE(S): types of system media ] are protected during transport outside of controlled areas using [SELECTED PARAMETER VALUE(S): controls ];Identified custodians provide organizations with specific points of contact during the media transport process and facilitate individual accountability. Custodial responsibilities can be transferred from one individual to another if an unambiguous custodian is identified.
","uuid":"3637edba-9412-4094-86f8-23ed27cfb7bf","family":"Media Protection","parameters":[],"subControls":"","tests":[{"testId":"MP-05(03)[01]","uuid":"9a6e4488-9176-475e-aa99-2b0dafc13be0","test":"Determine if a custodian to transport system media outside of controlled areas is identified;Media sanitization applies to all digital and non-digital system media subject to disposal or reuse, whether or not the media is considered removable. Examples include digital media in scanners, copiers, printers, notebook computers, workstations, network components, mobile devices, and non-digital media (e.g., paper and microfilm). The sanitization process removes information from system media such that the information cannot be retrieved or reconstructed. Sanitization techniques—including clearing, purging, cryptographic erase, de-identification of personally identifiable information, and destruction—prevent the disclosure of information to unauthorized individuals when such media is reused or released for disposal. Organizations determine the appropriate sanitization methods, recognizing that destruction is sometimes necessary when other methods cannot be applied to media requiring sanitization. Organizations use discretion on the employment of approved sanitization techniques and procedures for media that contains information deemed to be in the public domain or publicly releasable or information deemed to have no adverse impact on organizations or individuals if released for reuse or disposal. Sanitization of non-digital media includes destruction, removing a classified appendix from an otherwise unclassified document, or redacting selected sections or words from a document by obscuring the redacted sections or words in a manner equivalent in effectiveness to removing them from the document. NSA standards and policies control the sanitization process for media that contains classified information. NARA policies control the sanitization process for controlled unclassified information.
","uuid":"91d5f263-3b40-4fb8-9851-2b6578dfe9e2","family":"Media Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"4d855978-1270-49bd-b86a-676933cbb979","text":"organization-defined system media","parameterId":"mp-6_prm_1","default":" [Assignment: organization-defined system media] "},{"constraints":"","displayName":"","guidance":"","uuid":"c6c80161-0568-483f-b9e0-aadefe8cd55e","text":"organization-defined sanitization techniques and procedures","parameterId":"mp-6_prm_2","default":" [Assignment: organization-defined sanitization techniques and procedures] "},{"constraints":"","displayName":"","guidance":"","uuid":"80960cfb-6a08-4e5f-8d62-e053d4215392","text":"system media","parameterId":"mp-06_odp.01","default":" [Assignment: organization defined system media] "},{"constraints":"","displayName":"","guidance":"","uuid":"d88290a3-9955-451f-bfa5-8ae93da77cf5","text":"system media","parameterId":"mp-06_odp.02","default":" [Assignment: organization defined system media] "},{"constraints":"","displayName":"","guidance":"","uuid":"a23a658f-51b9-4b05-b516-aa33fbc7b82a","text":"system media","parameterId":"mp-06_odp.03","default":" [Assignment: organization defined system media] "},{"constraints":"","displayName":"","guidance":"","uuid":"8b17e5c8-ffcc-48b9-88f3-9bd367486266","text":"sanitization techniques and procedures","parameterId":"mp-06_odp.04","default":" [Assignment: organization defined sanitization techniques and procedures] "},{"constraints":"","displayName":"","guidance":"","uuid":"8978ab76-bad2-4a33-9903-e599fe0957cf","text":"sanitization techniques and procedures","parameterId":"mp-06_odp.05","default":" [Assignment: organization defined sanitization techniques and procedures] "},{"constraints":"","displayName":"","guidance":"","uuid":"e0731a29-2fee-42a5-9c6a-8d476bbf76d4","text":"sanitization techniques and procedures","parameterId":"mp-06_odp.06","default":" [Assignment: organization defined sanitization techniques and procedures] "}],"subControls":"","tests":[{"testId":"MP-06a.[01]","uuid":"8e7cb610-f605-42ca-86ce-d21043ffec8f","test":"Determine if [SELECTED PARAMETER VALUE(S): system media ] is sanitized using [SELECTED PARAMETER VALUE(S): sanitization techniques and procedures ] prior to disposal;Organizations review and approve media to be sanitized to ensure compliance with records retention policies. Tracking and documenting actions include listing personnel who reviewed and approved sanitization and disposal actions, types of media sanitized, files stored on the media, sanitization methods used, date and time of the sanitization actions, personnel who performed the sanitization, verification actions taken and personnel who performed the verification, and the disposal actions taken. Organizations verify that the sanitization of the media was effective prior to disposal.
","uuid":"6966d8af-9dcd-42e7-a821-7403093b6fcd","family":"Media Protection","parameters":[],"subControls":"","tests":[{"testId":"MP-06(01)[01]","uuid":"e5cb9a9e-6d08-4356-bf23-5bcbfd79aa7e","test":"Determine if media sanitization and disposal actions are reviewed;Testing of sanitization equipment and procedures may be conducted by qualified and authorized external entities, including federal agencies or external service providers.
","uuid":"7896d035-fa67-47be-a59a-2aebcfa35fd0","family":"Media Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"fc600695-734a-41d6-a131-7a9172645e16","text":"organization-defined frequency","parameterId":"mp-6.2_prm_1","default":" [Assignment: organization-defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"e2bce022-2be0-4ac2-b319-97f852e99f5b","text":"frequency","parameterId":"mp-06.02_odp.01","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"b9c069cb-21ca-485f-a430-c4f4b99b9a43","text":"frequency","parameterId":"mp-06.02_odp.02","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"MP-06(02)[01]","uuid":"0a5f7505-5f66-4e40-9484-dc582d36021c","test":"Determine if sanitization equipment is tested [SELECTED PARAMETER VALUE(S): frequency ] to ensure that the intended sanitization is being achieved;Portable storage devices include external or removable hard disk drives (e.g., solid state, magnetic), optical discs, magnetic or optical tapes, flash memory devices, flash memory cards, and other external or removable disks. Portable storage devices can be obtained from untrustworthy sources and contain malicious code that can be inserted into or transferred to organizational systems through USB ports or other entry portals. While scanning storage devices is recommended, sanitization provides additional assurance that such devices are free of malicious code. Organizations consider nondestructive sanitization of portable storage devices when the devices are purchased from manufacturers or vendors prior to initial use or when organizations cannot maintain a positive chain of custody for the devices.
","uuid":"4903c01e-d074-4a16-b9d6-839e1d4a9611","family":"Media Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"5b8f47ad-75b5-4fd8-a91a-66ec219a59d0","text":"circumstances","parameterId":"mp-06.03_odp","default":" [Assignment: organization defined circumstances] "}],"subControls":"","tests":[{"testId":"MP-06(03)","uuid":"d58be70e-e79e-4969-b6dd-c789f234990b","test":"Determine if non-destructive sanitization techniques are applied to portable storage devices prior to connecting such devices to the system under [SELECTED PARAMETER VALUE(S): circumstances ].Organizations employ dual authorization to help ensure that system media sanitization cannot occur unless two technically qualified individuals conduct the designated task. Individuals who sanitize system media possess sufficient skills and expertise to determine if the proposed sanitization reflects applicable federal and organizational standards, policies, and procedures. Dual authorization also helps to ensure that sanitization occurs as intended, protecting against errors and false claims of having performed the sanitization actions. Dual authorization may also be known as two-person control. To reduce the risk of collusion, organizations consider rotating dual authorization duties to other individuals.
","uuid":"09ccadc7-1e1e-4fc0-ace5-531803237d2c","family":"Media Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"b7a75cb9-27cf-4450-bed6-da6a596f3e40","text":"system media","parameterId":"mp-06.07_odp","default":" [Assignment: organization defined system media] "}],"subControls":"","tests":[{"testId":"MP-06(07)","uuid":"6464e6ac-e3ad-42ff-ba07-d03566aa30be","test":"Determine if dual authorization for sanitization of [SELECTED PARAMETER VALUE(S): system media ] is enforced.Remote purging or wiping of information protects information on organizational systems and system components if systems or components are obtained by unauthorized individuals. Remote purge or wipe commands require strong authentication to help mitigate the risk of unauthorized individuals purging or wiping the system, component, or device. The purge or wipe function can be implemented in a variety of ways, including by overwriting data or information multiple times or by destroying the key necessary to decrypt encrypted data.
","uuid":"88438a76-00db-40f6-86fe-f89395f62d4e","family":"Media Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"8a143016-1cff-48d3-9c8e-b518733feb94","text":"systems or system components","parameterId":"mp-06.08_odp.01","default":" [Assignment: organization defined systems or system components] "},{"constraints":"","displayName":"","guidance":"","uuid":"89e3bc27-2e5a-480d-9e36-d29fb1d0abcf","text":"[Selection: remotely; under [(NESTED PARAMETER) Assignment for mp-06.08_odp.03: conditions]]","parameterId":"mp-06.08_odp.02","default":"[Selection: remotely; under [(NESTED PARAMETER) Assignment for mp-06.08_odp.03: conditions]]"},{"constraints":"","displayName":"","guidance":"","uuid":"ddbdc75b-0c56-449c-85ab-810927835ead","text":"conditions","parameterId":"mp-06.08_odp.03","default":" [Assignment: organization defined conditions] "}],"subControls":"","tests":[{"testId":"MP-06(08)","uuid":"8ffc2b9e-15a3-4c42-8ebd-edd0606b35cb","test":"Determine if the capability to purge or wipe information from [SELECTED PARAMETER VALUE(S): systems or system components ], [SELECTED PARAMETER VALUE(S): [Selection: remotely; under [(NESTED PARAMETER) Assignment for mp-06.08_odp.03: conditions]] ] is provided.System media includes both digital and non-digital media. Digital media includes diskettes, magnetic tapes, flash drives, compact discs, digital versatile discs, and removable hard disk drives. Non-digital media includes paper and microfilm. Media use protections also apply to mobile devices with information storage capabilities. In contrast to MP-2 , which restricts user access to media, MP-7 restricts the use of certain types of media on systems, for example, restricting or prohibiting the use of flash drives or external hard disk drives. Organizations use technical and nontechnical controls to restrict the use of system media. Organizations may restrict the use of portable storage devices, for example, by using physical cages on workstations to prohibit access to certain external ports or disabling or removing the ability to insert, read, or write to such devices. Organizations may also limit the use of portable storage devices to only approved devices, including devices provided by the organization, devices provided by other approved organizations, and devices that are not personally owned. Finally, organizations may restrict the use of portable storage devices based on the type of device, such as by prohibiting the use of writeable, portable storage devices and implementing this restriction by disabling or removing the capability to write to such devices. Requiring identifiable owners for storage devices reduces the risk of using such devices by allowing organizations to assign responsibility for addressing known vulnerabilities in the devices.
","uuid":"a623345f-c4ef-47b0-a833-f874e4017f91","family":"Media Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"a5443fd6-20a4-4b14-bcea-af8da14cac86","text":"types of system media","parameterId":"mp-07_odp.01","default":" [Assignment: organization defined types of system media] "},{"constraints":"","displayName":"","guidance":"","uuid":"f9416940-ee6d-435f-b59b-346182bb5c59","text":"[Selection: restrict; prohibit]","parameterId":"mp-07_odp.02","default":"[Selection: restrict; prohibit]"},{"constraints":"","displayName":"","guidance":"","uuid":"f0b7983d-0d7b-4498-88db-328c4caf9906","text":"systems or system components","parameterId":"mp-07_odp.03","default":" [Assignment: organization defined systems or system components] "},{"constraints":"","displayName":"","guidance":"","uuid":"3e3b5471-3179-44e8-8a1e-689d33e75ca0","text":"controls","parameterId":"mp-07_odp.04","default":" [Assignment: organization defined controls] "}],"subControls":"","tests":[{"testId":"MP-07a.","uuid":"966a70cb-c017-4094-8280-1eb3e4a4c76c","test":"Determine if the use of [SELECTED PARAMETER VALUE(S): types of system media ] is [SELECTED PARAMETER VALUE(S): [Selection: restrict; prohibit] ] on [SELECTED PARAMETER VALUE(S): systems or system components ] using [SELECTED PARAMETER VALUE(S): controls ];Sanitization resistance refers to how resistant media are to non-destructive sanitization techniques with respect to the capability to purge information from media. Certain types of media do not support sanitization commands, or if supported, the interfaces are not supported in a standardized way across these devices. Sanitization-resistant media includes compact flash, embedded flash on boards and devices, solid state drives, and USB removable media.
","uuid":"e74fae65-b572-443c-8a0c-f58195369bcd","family":"Media Protection","parameters":[],"subControls":"","tests":[{"testId":"MP-07(02)[01]","uuid":"fee8807f-5d08-4f90-9cc9-364a1bc129b1","test":"Determine if sanitization-resistant media is identified;Media downgrading applies to digital and non-digital media subject to release outside of the organization, whether the media is considered removable or not. When applied to system media, the downgrading process removes information from the media, typically by security category or classification level, such that the information cannot be retrieved or reconstructed. Downgrading of media includes redacting information to enable wider release and distribution. Downgrading ensures that empty space on the media is devoid of information.
","uuid":"be0c5f4c-7051-4a44-bd26-d8d469d509fc","family":"Media Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"e577572e-938c-4ed8-a343-536a6bd41715","text":"system media downgrading process","parameterId":"mp-08_odp.01","default":" [Assignment: organization defined system media downgrading process] "},{"constraints":"","displayName":"","guidance":"","uuid":"293f4346-fd21-42c4-a7ea-b4c0d2021ee8","text":"system media requiring downgrading","parameterId":"mp-08_odp.02","default":" [Assignment: organization defined system media requiring downgrading] "}],"subControls":"","tests":[{"testId":"MP-08a.[01]","uuid":"6af7c58b-4e7f-44e7-a5df-2bee3784b735","test":"Determine if a [SELECTED PARAMETER VALUE(S): system media downgrading process ] is established;Organizations can document the media downgrading process by providing information, such as the downgrading technique employed, the identification number of the downgraded media, and the identity of the individual that authorized and/or performed the downgrading action.
","uuid":"8c7793d9-f541-40e7-879c-104c7cb4965f","family":"Media Protection","parameters":[],"subControls":"","tests":[{"testId":"MP-08(01)","uuid":"e02c58e4-e8d4-4ecd-8a1f-b090d85d5110","test":"Determine if system media downgrading actions are documented.None.
","uuid":"551c89e0-9076-4313-82d5-cbfa25d8e6bb","family":"Media Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"fd1c8924-e4bf-4a45-a01b-18300c215030","text":"organization-defined frequency","parameterId":"mp-8.2_prm_1","default":" [Assignment: organization-defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"0080f093-7451-4d81-ae8a-6e8a1c3cb02f","text":"frequency","parameterId":"mp-08.02_odp.01","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"e541d8d1-f546-41c7-b380-567a5f9d28f0","text":"frequency","parameterId":"mp-08.02_odp.02","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"MP-08(02)[01]","uuid":"6249bbb4-c44b-4e4b-a921-b8de6339bd42","test":"Determine if downgrading equipment is tested [SELECTED PARAMETER VALUE(S): frequency ] to ensure that downgrading actions are being achieved;The downgrading of controlled unclassified information uses approved sanitization tools, techniques, and procedures.
","uuid":"9e8ac2e1-f0e8-49dc-88d8-18a7297ef5b4","family":"Media Protection","parameters":[],"subControls":"","tests":[{"testId":"MP-08(03)[01]","uuid":"25c8d688-9e0d-48bd-a933-31e369a91060","test":"Determine if system media containing controlled unclassified information is identified;Downgrading of classified information uses approved sanitization tools, techniques, and procedures to transfer information confirmed to be unclassified from classified systems to unclassified media.
","uuid":"1c18398a-10ea-4c2c-a4e4-533e4a763d98","family":"Media Protection","parameters":[],"subControls":"","tests":[{"testId":"MP-08(04)[01]","uuid":"309e95fb-12fa-4cc1-90dc-5f7a8b2b4711","test":"Determine if system media containing classified information is identified;Physical and environmental protection policy and procedures address the controls in the PE family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of physical and environmental protection policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission or business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to physical and environmental protection policy and procedures include assessment or audit findings, security incidents or breaches, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure.
","uuid":"ef7d1f0e-a946-49a9-87ba-5385d27094fc","family":"Physical and Environmental Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"93a2345f-578b-4b2c-8646-4390ee4e4c8e","text":"organization-defined personnel or roles","parameterId":"pe-1_prm_1","default":" [Assignment: organization-defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"565dbcd4-c48a-4cb8-884b-d2dc29cb266a","text":"personnel or roles","parameterId":"pe-01_odp.01","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"d7a64ce9-920d-4484-bfcd-28b41d9a3ba2","text":"personnel or roles","parameterId":"pe-01_odp.02","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"66d75305-a654-49e2-a3c3-a47c7a9dab8c","text":"[Selection (one or more): organization-level; mission/business process-level; system-level]","parameterId":"pe-01_odp.03","default":"[Selection (one or more): organization-level; mission/business process-level; system-level]"},{"constraints":"","displayName":"","guidance":"","uuid":"c4e286a3-ed52-4f67-b57d-3a4cc47ca403","text":"official","parameterId":"pe-01_odp.04","default":" [Assignment: organization defined official] "},{"constraints":"","displayName":"","guidance":"","uuid":"2ac54449-7c1e-4c79-b422-ac7359d1c0da","text":"frequency","parameterId":"pe-01_odp.05","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"ea6fbd5e-dfd4-48c3-b1c7-fdfcd66a1fc2","text":"events","parameterId":"pe-01_odp.06","default":" [Assignment: organization defined events] "},{"constraints":"","displayName":"","guidance":"","uuid":"3e4224ad-54bc-4e56-8c12-03761870b53f","text":"frequency","parameterId":"pe-01_odp.07","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"0ce6313a-f14c-4ab4-a30f-1b50601b4d8b","text":"events","parameterId":"pe-01_odp.08","default":" [Assignment: organization defined events] "}],"subControls":"","tests":[{"testId":"PE-01a.[01]","uuid":"e793948c-0f19-4e77-9068-91874d06461d","test":"Determine if a physical and environmental protection policy is developed and documented;Physical access authorizations apply to employees and visitors. Individuals with permanent physical access authorization credentials are not considered visitors. Authorization credentials include ID badges, identification cards, and smart cards. Organizations determine the strength of authorization credentials needed consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Physical access authorizations may not be necessary to access certain areas within facilities that are designated as publicly accessible.
","uuid":"d68e2a7b-b0c5-4064-bf9e-87d42dc75c8a","family":"Physical and Environmental Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"59de8b80-681d-4c73-9df5-8a83bca719cb","text":"frequency","parameterId":"pe-02_odp","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"PE-02a.[01]","uuid":"211f42e2-5f5d-43af-bd7c-d747e5794d9c","test":"Determine if a list of individuals with authorized access to the facility where the system resides has been developed;Role-based facility access includes access by authorized permanent and regular/routine maintenance personnel, duty officers, and emergency medical staff.
","uuid":"04aa7072-b8d2-46e4-9324-26ed80d6b423","family":"Physical and Environmental Protection","parameters":[],"subControls":"","tests":[{"testId":"PE-02(01)","uuid":"40960d04-fa85-431d-a5ff-1b2e14c75e7f","test":"Determine if physical access to the facility where the system resides is authorized based on position or role.Acceptable forms of identification include passports, REAL ID-compliant drivers’ licenses, and Personal Identity Verification (PIV) cards. For gaining access to facilities using automated mechanisms, organizations may use PIV cards, key cards, PINs, and biometrics.
","uuid":"df1f3346-8739-41c4-bcea-feddfe60ec50","family":"Physical and Environmental Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"2847adcb-0bd4-43eb-9246-10f71466b704","text":"list of acceptable forms of identification","parameterId":"pe-02.02_odp","default":" [Assignment: organization defined list of acceptable forms of identification] "}],"subControls":"","tests":[{"testId":"PE-02(02)","uuid":"67f02724-f572-404d-b754-0b4361bd8067","test":"Determine if two forms of identification are required from [SELECTED PARAMETER VALUE(S): list of acceptable forms of identification ] for visitor access to the facility where the system resides.Individuals without required security clearances, access approvals, or need to know are escorted by individuals with appropriate physical access authorizations to ensure that information is not exposed or otherwise compromised.
","uuid":"3172f680-1882-485e-8083-b746544ae450","family":"Physical and Environmental Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"b85d879d-494f-4336-a36e-dcbd3960a4f7","text":"[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; [(NESTED PARAMETER) Assignment for pe-02.03_odp.02: physical access authorizations]]","parameterId":"pe-02.03_odp.01","default":"[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; [(NESTED PARAMETER) Assignment for pe-02.03_odp.02: physical access authorizations]]"},{"constraints":"","displayName":"","guidance":"","uuid":"6a7d3e61-e647-4b02-bcc3-1afb7d8ccb81","text":"physical access authorizations","parameterId":"pe-02.03_odp.02","default":" [Assignment: organization defined physical access authorizations] "}],"subControls":"","tests":[{"testId":"PE-02(03)","uuid":"69d8e81e-7d3a-4bc5-9efc-b7c159f9fddc","test":"Determine if unescorted access to the facility where the system resides is restricted to personnel with [SELECTED PARAMETER VALUE(S): [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; [(NESTED PARAMETER) Assignment for pe-02.03_odp.02: physical access authorizations]] ].Physical access control applies to employees and visitors. Individuals with permanent physical access authorizations are not considered visitors. Physical access controls for publicly accessible areas may include physical access control logs/records, guards, or physical access devices and barriers to prevent movement from publicly accessible areas to non-public areas. Organizations determine the types of guards needed, including professional security staff, system users, or administrative staff. Physical access devices include keys, locks, combinations, biometric readers, and card readers. Physical access control systems comply with applicable laws, executive orders, directives, policies, regulations, standards, and guidelines. Organizations have flexibility in the types of audit logs employed. Audit logs can be procedural, automated, or some combination thereof. Physical access points can include facility access points, interior access points to systems that require supplemental access controls, or both. Components of systems may be in areas designated as publicly accessible with organizations controlling access to the components.
","uuid":"e991b07f-de60-478e-8c9c-1c6e71addea0","family":"Physical and Environmental Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"ca1aea4d-9bc6-4084-89d1-9bc4ac9897ac","text":"organization-defined frequency","parameterId":"pe-3_prm_9","default":" [Assignment: organization-defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"eeda1fd1-adc6-4487-81a7-8986e8c66c59","text":"entry and exit points","parameterId":"pe-03_odp.01","default":" [Assignment: organization defined entry and exit points] "},{"constraints":"","displayName":"","guidance":"","uuid":"233e10c5-df9b-4674-a14a-6a974d2dceb4","text":"[Selection (one or more): [(NESTED PARAMETER) Assignment for pe-03_odp.03: systems or devices]; guards]","parameterId":"pe-03_odp.02","default":"[Selection (one or more): [(NESTED PARAMETER) Assignment for pe-03_odp.03: systems or devices]; guards]"},{"constraints":"","displayName":"","guidance":"","uuid":"0ae975aa-210a-4b3f-838f-5eb27b907c0a","text":"systems or devices","parameterId":"pe-03_odp.03","default":" [Assignment: organization defined systems or devices] "},{"constraints":"","displayName":"","guidance":"","uuid":"302226be-bbdb-406a-bb3b-507a91197fe6","text":"entry or exit points","parameterId":"pe-03_odp.04","default":" [Assignment: organization defined entry or exit points] "},{"constraints":"","displayName":"","guidance":"","uuid":"f1436b7d-826d-4511-89e4-ea4d0c9a784d","text":"physical access controls","parameterId":"pe-03_odp.05","default":" [Assignment: organization defined physical access controls] "},{"constraints":"","displayName":"","guidance":"","uuid":"9d58ba0f-9143-459b-9cc7-de710fe70c82","text":"circumstances","parameterId":"pe-03_odp.06","default":" [Assignment: organization defined circumstances] "},{"constraints":"","displayName":"","guidance":"","uuid":"853dd72d-c157-4bc1-b31f-00ca7e82cbaa","text":"physical access devices","parameterId":"pe-03_odp.07","default":" [Assignment: organization defined physical access devices] "},{"constraints":"","displayName":"","guidance":"","uuid":"73fdbb46-9447-4e15-a84a-404879d346a7","text":"frequency","parameterId":"pe-03_odp.08","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"5edb634b-862a-4e61-89b6-d423afb1ebc9","text":"frequency","parameterId":"pe-03_odp.09","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"776498af-1b71-45a5-8a98-8026b106e6d3","text":"frequency","parameterId":"pe-03_odp.10","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"PE-03a.01","uuid":"58d792c7-4d25-4886-b459-2fe511c2f86d","test":"Determine if physical access authorizations are enforced at [SELECTED PARAMETER VALUE(S): entry and exit points ] by verifying individual access authorizations before granting access to the facility;Control of physical access to the system provides additional physical security for those areas within facilities where there is a concentration of system components.
","uuid":"004c334e-4551-42c8-80f3-05cdb84f05c8","family":"Physical and Environmental Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"b4351173-efcf-49b1-adf7-3cd3a5918b02","text":"physical spaces","parameterId":"pe-03.01_odp","default":" [Assignment: organization defined physical spaces] "}],"subControls":"","tests":[{"testId":"PE-03(01)[01]","uuid":"d82fb5dd-042b-4214-a2c7-6ae7c03d4149","test":"Determine if physical access authorizations to the system are enforced;Organizations determine the extent, frequency, and/or randomness of security checks to adequately mitigate risk associated with exfiltration.
","uuid":"4fd9bcc9-cfcf-406a-a68e-1453f092657e","family":"Physical and Environmental Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"bcb9a804-31bc-4f47-ae45-57770016893a","text":"frequency","parameterId":"pe-03.02_odp","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"PE-03(02)","uuid":"e394256f-a748-49aa-8e39-1faedd7bc64d","test":"Determine if security checks are performed [SELECTED PARAMETER VALUE(S): frequency ] at the physical perimeter of the facility or system for exfiltration of information or removal of system components.Employing guards at selected physical access points to the facility provides a more rapid response capability for organizations. Guards also provide the opportunity for human surveillance in areas of the facility not covered by video surveillance.
","uuid":"9e82a521-1747-4f19-90d3-eb0296fd881f","family":"Physical and Environmental Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"2cfcb519-94a9-4121-8542-b558c8400911","text":"physical access points","parameterId":"pe-03.03_odp","default":" [Assignment: organization defined physical access points] "}],"subControls":"","tests":[{"testId":"PE-03(03)","uuid":"f027172d-3bff-4f2c-82c9-ea6bdb48e697","test":"Determine if guards are employed to control [SELECTED PARAMETER VALUE(S): physical access points ] to the facility where the system resides 24 hours per day, 7 days per week.The greatest risk from the use of portable devices—such as smart phones, tablets, and notebook computers—is theft. Organizations can employ lockable, physical casings to reduce or eliminate the risk of equipment theft. Such casings come in a variety of sizes, from units that protect a single notebook computer to full cabinets that can protect multiple servers, computers, and peripherals. Lockable physical casings can be used in conjunction with cable locks or lockdown plates to prevent the theft of the locked casing containing the computer equipment.
","uuid":"82c3ef33-43f5-4c73-8c12-722a8da85511","family":"Physical and Environmental Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"7d4d519f-823f-4117-a1bf-c26c6dde06e9","text":"system components","parameterId":"pe-03.04_odp","default":" [Assignment: organization defined system components] "}],"subControls":"","tests":[{"testId":"PE-03(04)","uuid":"97291998-87f2-4bec-8594-0777623886e1","test":"Determine if lockable physical casings are used to protect [SELECTED PARAMETER VALUE(S): system components ] from unauthorized access.Organizations can implement tamper detection and prevention at selected hardware components or implement tamper detection at some components and tamper prevention at other components. Detection and prevention activities can employ many types of anti-tamper technologies, including tamper-detection seals and anti-tamper coatings. Anti-tamper programs help to detect hardware alterations through counterfeiting and other supply chain-related risks.
","uuid":"1e08d72d-a84a-47f2-8f7e-34baaae84a18","family":"Physical and Environmental Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"779a4a8f-cf3c-4d4b-a226-1f207f44ed22","text":"anti-tamper technologies","parameterId":"pe-03.05_odp.01","default":" [Assignment: organization defined anti-tamper technologies] "},{"constraints":"","displayName":"","guidance":"","uuid":"456206b7-3a33-41b2-b4aa-aa921ba5561e","text":"[Selection (one or more): detect; prevent]","parameterId":"pe-03.05_odp.02","default":"[Selection (one or more): detect; prevent]"},{"constraints":"","displayName":"","guidance":"","uuid":"fe6370fc-685c-4da2-ab9c-3df73f908627","text":"hardware components","parameterId":"pe-03.05_odp.03","default":" [Assignment: organization defined hardware components] "}],"subControls":"","tests":[{"testId":"PE-03(05)","uuid":"b15b6b12-4826-4839-a0d0-e20fdf52befa","test":"Determine if [SELECTED PARAMETER VALUE(S): anti-tamper technologies ] are employed to [SELECTED PARAMETER VALUE(S): [Selection (one or more): detect; prevent] ] physical tampering or alteration of [SELECTED PARAMETER VALUE(S): hardware components ] within the system.Physical barriers include bollards, concrete slabs, jersey walls, and hydraulic active vehicle barriers.
","uuid":"34eecd0b-6511-4209-b56e-ae002756f0d1","family":"Physical and Environmental Protection","parameters":[],"subControls":"","tests":[{"testId":"PE-03(07)","uuid":"1600f30e-6247-428f-a8de-71d251fc1538","test":"Determine if physical barriers are used to limit access.An access control vestibule is part of a physical access control system that typically provides a space between two sets of interlocking doors. Vestibules are designed to prevent unauthorized individuals from following authorized individuals into facilities with controlled access. This activity, also known as piggybacking or tailgating, results in unauthorized access to the facility. Interlocking door controllers can be used to limit the number of individuals who enter controlled access points and to provide containment areas while authorization for physical access is verified. Interlocking door controllers can be fully automated (i.e., controlling the opening and closing of the doors) or partially automated (i.e., using security guards to control the number of individuals entering the containment area).
","uuid":"d94b43d6-7d0d-4574-b892-a10cb7b134eb","family":"Physical and Environmental Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"8102cd85-8856-4071-a581-f4a353fb8a26","text":"locations","parameterId":"pe-03.08_odp","default":" [Assignment: organization defined locations] "}],"subControls":"","tests":[{"testId":"PE-03(08)","uuid":"6b3f6e00-782a-4edb-a537-296a2cd9a7d9","test":"Determine if access control vestibules are employed at [SELECTED PARAMETER VALUE(S): locations ].Security controls applied to system distribution and transmission lines prevent accidental damage, disruption, and physical tampering. Such controls may also be necessary to prevent eavesdropping or modification of unencrypted transmissions. Security controls used to control physical access to system distribution and transmission lines include disconnected or locked spare jacks, locked wiring closets, protection of cabling by conduit or cable trays, and wiretapping sensors.
","uuid":"31c030bc-1fe5-4837-b234-1b9e72d9f677","family":"Physical and Environmental Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"ec96ce69-f621-43bc-84ad-ff841dbdb80c","text":"system distribution and transmission lines","parameterId":"pe-04_odp.01","default":" [Assignment: organization defined system distribution and transmission lines] "},{"constraints":"","displayName":"","guidance":"","uuid":"0972d061-9d20-43cc-8d41-0f16fce9df63","text":"security controls","parameterId":"pe-04_odp.02","default":" [Assignment: organization defined security controls] "}],"subControls":"","tests":[{"testId":"PE-04","uuid":"9c929719-39d7-4108-be4d-9ea375eeee85","test":"Determine if physical access to [SELECTED PARAMETER VALUE(S): system distribution and transmission lines ] within organizational facilities is controlled using [SELECTED PARAMETER VALUE(S): security controls ].Controlling physical access to output devices includes placing output devices in locked rooms or other secured areas with keypad or card reader access controls and allowing access to authorized individuals only, placing output devices in locations that can be monitored by personnel, installing monitor or screen filters, and using headphones. Examples of output devices include monitors, printers, scanners, audio devices, facsimile machines, and copiers.
","uuid":"c228def9-eb1e-4ebb-bfbb-36c5ef5c47ef","family":"Physical and Environmental Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"bce6fe45-1cbc-472f-937b-a17bf399bf4f","text":"output devices","parameterId":"pe-05_odp","default":" [Assignment: organization defined output devices] "}],"subControls":"","tests":[{"testId":"PE-05","uuid":"0466c783-bb12-4110-a7b6-bbe2293a5e0d","test":"Determine if physical access to output from [SELECTED PARAMETER VALUE(S): output devices ] is controlled to prevent unauthorized individuals from obtaining the output.Methods for linking individual identity to the receipt of output from output devices include installing security functionality on facsimile machines, copiers, and printers. Such functionality allows organizations to implement authentication on output devices prior to the release of output to individuals.
","uuid":"b3cda6b6-2e4d-4942-903a-a5ed056f3263","family":"Physical and Environmental Protection","parameters":[],"subControls":"","tests":[{"testId":"PE-05(02)","uuid":"aae90c4b-898f-466d-9467-a58deb6bdd4f","test":"Determine if individual identity is linked to the receipt of output from output devices.Physical access monitoring includes publicly accessible areas within organizational facilities. Examples of physical access monitoring include the employment of guards, video surveillance equipment (i.e., cameras), and sensor devices. Reviewing physical access logs can help identify suspicious activity, anomalous events, or potential threats. The reviews can be supported by audit logging controls, such as AU-2 , if the access logs are part of an automated system. Organizational incident response capabilities include investigations of physical security incidents and responses to the incidents. Incidents include security violations or suspicious physical access activities. Suspicious physical access activities include accesses outside of normal work hours, repeated accesses to areas not normally accessed, accesses for unusual lengths of time, and out-of-sequence accesses.
","uuid":"5f00f037-534b-443d-bad5-a861c0d6792f","family":"Physical and Environmental Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"a44744ad-b101-4623-bd2f-caedbb1b892a","text":"frequency","parameterId":"pe-06_odp.01","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"de9c3064-dea7-48d5-918c-828f1b80bb4f","text":"events","parameterId":"pe-06_odp.02","default":" [Assignment: organization defined events] "}],"subControls":"","tests":[{"testId":"PE-06a.","uuid":"ee56ecd0-3224-4cdf-b119-32dc2a83410d","test":"Determine if physical access to the facility where the system resides is monitored to detect and respond to physical security incidents;Physical intrusion alarms can be employed to alert security personnel when unauthorized access to the facility is attempted. Alarm systems work in conjunction with physical barriers, physical access control systems, and security guards by triggering a response when these other forms of security have been compromised or breached. Physical intrusion alarms can include different types of sensor devices, such as motion sensors, contact sensors, and broken glass sensors. Surveillance equipment includes video cameras installed at strategic locations throughout the facility.
","uuid":"b796233a-c05e-491b-9b2b-388d4d13e5c0","family":"Physical and Environmental Protection","parameters":[],"subControls":"","tests":[{"testId":"PE-06(01)[01]","uuid":"4b130efa-d8c0-47b5-b1cf-2bbdc068767e","test":"Determine if physical access to the facility where the system resides is monitored using physical intrusion alarms;Response actions can include notifying selected organizational personnel or law enforcement personnel. Automated mechanisms implemented to initiate response actions include system alert notifications, email and text messages, and activating door locking mechanisms. Physical access monitoring can be coordinated with intrusion detection systems and system monitoring capabilities to provide integrated threat coverage for the organization.
","uuid":"e832c51e-b1cd-4084-8348-351e88c69421","family":"Physical and Environmental Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"c5095831-b8e1-4da0-842a-5212f4bbb2e1","text":"classes or types of intrusions","parameterId":"pe-06.02_odp.01","default":" [Assignment: organization defined classes or types of intrusions] "},{"constraints":"","displayName":"","guidance":"","uuid":"839e88f0-a6d2-4def-8f39-8013d166ecb7","text":"response actions","parameterId":"pe-06.02_odp.02","default":" [Assignment: organization defined response actions] "},{"constraints":"","displayName":"","guidance":"","uuid":"f3de2e3c-6d4a-48c7-9295-f2ef4f580662","text":"automated mechanisms","parameterId":"pe-06.02_odp.03","default":" [Assignment: organization defined automated mechanisms] "}],"subControls":"","tests":[{"testId":"PE-06(02)[01]","uuid":"c852e2ad-cd8b-48e7-b3ae-cf56fbb9eff5","test":"Determine if [SELECTED PARAMETER VALUE(S): classes or types of intrusions ] are recognized;Video surveillance focuses on recording activity in specified areas for the purposes of subsequent review, if circumstances so warrant. Video recordings are typically reviewed to detect anomalous events or incidents. Monitoring the surveillance video is not required, although organizations may choose to do so. There may be legal considerations when performing and retaining video surveillance, especially if such surveillance is in a public location.
","uuid":"1abcc763-c3ad-4e90-8d2b-d0d157786f97","family":"Physical and Environmental Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"94100174-35a2-4eef-a44f-e77e530716b6","text":"operational areas","parameterId":"pe-06.03_odp.01","default":" [Assignment: organization defined operational areas] "},{"constraints":"","displayName":"","guidance":"","uuid":"b992d0a3-271e-45bb-bf1c-fb26856cbf9e","text":"frequency","parameterId":"pe-06.03_odp.02","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"f7bf1a95-93b7-42fc-b01d-d09552c37139","text":"time period","parameterId":"pe-06.03_odp.03","default":" [Assignment: organization defined time period] "}],"subControls":"","tests":[{"testId":"PE-06(03)(a)","uuid":"31583ba0-0ab9-4255-ac56-6d078c67e3ff","test":"Determine if video surveillance of [SELECTED PARAMETER VALUE(S): operational areas ] is employed;Monitoring physical access to systems provides additional monitoring for those areas within facilities where there is a concentration of system components, including server rooms, media storage areas, and communications centers. Physical access monitoring can be coordinated with intrusion detection systems and system monitoring capabilities to provide comprehensive and integrated threat coverage for the organization.
","uuid":"dc27c579-ca2b-4506-af87-426f9e95948e","family":"Physical and Environmental Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"f5866405-9d21-46a3-ab27-9830abbff728","text":"physical spaces","parameterId":"pe-06.04_odp","default":" [Assignment: organization defined physical spaces] "}],"subControls":"","tests":[{"testId":"PE-06(04)","uuid":"14dff5bd-faa9-4a8a-9c6f-703319421a52","test":"Determine if physical access to the system is monitored in addition to the physical access monitoring of the facility at [SELECTED PARAMETER VALUE(S): physical spaces ].Visitor access records include the names and organizations of individuals visiting, visitor signatures, forms of identification, dates of access, entry and departure times, purpose of visits, and the names and organizations of individuals visited. Access record reviews determine if access authorizations are current and are still required to support organizational mission and business functions. Access records are not required for publicly accessible areas.
","uuid":"1f8879dc-54e4-425f-94b1-43a4ee28cc4d","family":"Physical and Environmental Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"0252fd78-9aa7-4132-a299-726191c08769","text":"time period","parameterId":"pe-08_odp.01","default":" [Assignment: organization defined time period] "},{"constraints":"","displayName":"","guidance":"","uuid":"9136783e-662e-4dbe-b50b-75f12a3c2d14","text":"frequency","parameterId":"pe-08_odp.02","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"de4fcf7a-c2ba-472f-985d-5c32ba00e896","text":"personnel","parameterId":"pe-08_odp.03","default":" [Assignment: organization defined personnel] "}],"subControls":"","tests":[{"testId":"PE-08a.","uuid":"bac35a0f-f2b0-4463-a0a6-d88cb1bea13f","test":"Determine if visitor access records for the facility where the system resides are maintained for [SELECTED PARAMETER VALUE(S): time period ];Visitor access records may be stored and maintained in a database management system that is accessible by organizational personnel. Automated access to such records facilitates record reviews on a regular basis to determine if access authorizations are current and still required to support organizational mission and business functions.
","uuid":"29a1c5a0-8439-4648-a97a-a35342e7bb28","family":"Physical and Environmental Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"77fe3ffe-1ab0-4c6a-81af-f6b79a25a0b2","text":"organization-defined automated mechanisms","parameterId":"pe-8.1_prm_1","default":" [Assignment: organization-defined automated mechanisms] "},{"constraints":"","displayName":"","guidance":"","uuid":"90b2618b-4605-42c8-96a2-e81f999a5e78","text":"automated mechanisms","parameterId":"pe-08.01_odp.01","default":" [Assignment: organization defined automated mechanisms] "},{"constraints":"","displayName":"","guidance":"","uuid":"700bbe94-7d8c-4ca2-bd82-19e281d982d2","text":"automated mechanisms","parameterId":"pe-08.01_odp.02","default":" [Assignment: organization defined automated mechanisms] "}],"subControls":"","tests":[{"testId":"PE-08(01)[01]","uuid":"64e380f5-3004-43d2-9a0b-16fd9391d844","test":"Determine if visitor access records are maintained using [SELECTED PARAMETER VALUE(S): automated mechanisms ];Organizations may have requirements that specify the contents of visitor access records. Limiting personally identifiable information in visitor access records when such information is not needed for operational purposes helps reduce the level of privacy risk created by a system.
","uuid":"48f87dd8-18a7-4451-a064-b324cc830d23","family":"Physical and Environmental Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"f2d9bc36-1653-4f01-8cc1-177ba8b64677","text":"elements","parameterId":"pe-08.03_odp","default":" [Assignment: organization defined elements] "}],"subControls":"","tests":[{"testId":"PE-08(03)","uuid":"11546ed5-97a1-4bc9-8a1a-6221bc331524","test":"Determine if personally identifiable information contained in visitor access records is limited to [SELECTED PARAMETER VALUE(S): elements ] identified in the privacy risk assessment.Organizations determine the types of protection necessary for the power equipment and cabling employed at different locations that are both internal and external to organizational facilities and environments of operation. Types of power equipment and cabling include internal cabling and uninterruptable power sources in offices or data centers, generators and power cabling outside of buildings, and power sources for self-contained components such as satellites, vehicles, and other deployable systems.
","uuid":"090ba8f2-0f9e-43f9-8e4d-4416d3d13c43","family":"Physical and Environmental Protection","parameters":[],"subControls":"","tests":[{"testId":"PE-09[01]","uuid":"c3b10b85-4428-4ff4-be07-48c08dd8d027","test":"Determine if power equipment for the system is protected from damage and destruction;Physically separate and redundant power cables ensure that power continues to flow in the event that one of the cables is cut or otherwise damaged.
","uuid":"dd1d923c-22fd-42c9-8332-f670d605eb87","family":"Physical and Environmental Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"dd35e5fa-96b9-44d6-a189-47d757e18e72","text":"distance","parameterId":"pe-09.01_odp","default":" [Assignment: organization defined distance] "}],"subControls":"","tests":[{"testId":"PE-09(01)","uuid":"87effd2d-e2bd-47d9-bebc-cd6763a390b8","test":"Determine if redundant power cabling paths that are physically separated by [SELECTED PARAMETER VALUE(S): distance ] are employed.Automatic voltage controls can monitor and control voltage. Such controls include voltage regulators, voltage conditioners, and voltage stabilizers.
","uuid":"ef05b030-70f5-44c2-868d-273942520550","family":"Physical and Environmental Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"748b3967-1e7b-494f-baf9-1af6656102ab","text":"critical system components","parameterId":"pe-09.02_odp","default":" [Assignment: organization defined critical system components] "}],"subControls":"","tests":[{"testId":"PE-09(02)","uuid":"337d43df-4f6c-44e0-87b1-156f70db6682","test":"Determine if automatic voltage controls for [SELECTED PARAMETER VALUE(S): critical system components ] are employed.Emergency power shutoff primarily applies to organizational facilities that contain concentrations of system resources, including data centers, mainframe computer rooms, server rooms, and areas with computer-controlled machinery.
","uuid":"5ec53bd7-f2be-4309-8302-6e2628628599","family":"Physical and Environmental Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"14446f2e-8eab-4d60-8781-16bb49eed822","text":"system or individual system components","parameterId":"pe-10_odp.01","default":" [Assignment: organization defined system or individual system components] "},{"constraints":"","displayName":"","guidance":"","uuid":"f5169b93-c0aa-47ce-88bd-aa5a3293a507","text":"location","parameterId":"pe-10_odp.02","default":" [Assignment: organization defined location] "}],"subControls":"","tests":[{"testId":"PE-10a.","uuid":"a2e8837d-d83b-46c8-a7f4-2207f5f9f926","test":"Determine if the capability to shut off power to [SELECTED PARAMETER VALUE(S): system or individual system components ] in emergency situations is provided;An uninterruptible power supply (UPS) is an electrical system or mechanism that provides emergency power when there is a failure of the main power source. A UPS is typically used to protect computers, data centers, telecommunication equipment, or other electrical equipment where an unexpected power disruption could cause injuries, fatalities, serious mission or business disruption, or loss of data or information. A UPS differs from an emergency power system or backup generator in that the UPS provides near-instantaneous protection from unanticipated power interruptions from the main power source by providing energy stored in batteries, supercapacitors, or flywheels. The battery duration of a UPS is relatively short but provides sufficient time to start a standby power source, such as a backup generator, or properly shut down the system.
","uuid":"fa9d417f-61a2-45b8-8dd2-06dce33ec75c","family":"Physical and Environmental Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"0c80ca8c-0c75-4dc4-b613-62d8b996a5ff","text":"[Selection: an orderly shutdown of the system; transition of the system to long-term alternate power]","parameterId":"pe-11_odp","default":"[Selection: an orderly shutdown of the system; transition of the system to long-term alternate power]"}],"subControls":"","tests":[{"testId":"PE-11","uuid":"7dc48029-890d-42bd-8deb-ee7937b84771","test":"Determine if an uninterruptible power supply is provided to facilitate [SELECTED PARAMETER VALUE(S): [Selection: an orderly shutdown of the system; transition of the system to long-term alternate power] ] in the event of a primary power source loss.Provision of an alternate power supply with minimal operating capability can be satisfied by accessing a secondary commercial power supply or other external power supply.
","uuid":"85779311-8014-453d-98d1-ee5720726989","family":"Physical and Environmental Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"13732408-6b56-42d1-bdd9-f606927f8800","text":"[Selection: manually; automatically]","parameterId":"pe-11.01_odp","default":"[Selection: manually; automatically]"}],"subControls":"","tests":[{"testId":"PE-11(01)[01]","uuid":"e4139b1d-144d-44ec-b01e-f532a36bad86","test":"Determine if an alternate power supply provided for the system is activated [SELECTED PARAMETER VALUE(S): [Selection: manually; automatically] ];The provision of a long-term, self-contained power supply can be satisfied by using one or more generators with sufficient capacity to meet the needs of the organization.
","uuid":"b7d37a80-76e7-409f-ae96-bae2f6992db4","family":"Physical and Environmental Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"9a1bf574-fec5-4b20-b711-53da693a70cf","text":"[Selection: manually; automatically]","parameterId":"pe-11.02_odp.01","default":"[Selection: manually; automatically]"},{"constraints":"","displayName":"","guidance":"","uuid":"03bd2e05-276d-4799-9952-fc9177b92b83","text":"[Selection: minimally required operational capability; full operational capability]","parameterId":"pe-11.02_odp.02","default":"[Selection: minimally required operational capability; full operational capability]"}],"subControls":"","tests":[{"testId":"PE-11(02)(a)","uuid":"a2501976-c688-4975-b645-788519886411","test":"Determine if the alternate power supply provided for the system is self-contained;The provision of emergency lighting applies primarily to organizational facilities that contain concentrations of system resources, including data centers, server rooms, and mainframe computer rooms. Emergency lighting provisions for the system are described in the contingency plan for the organization. If emergency lighting for the system fails or cannot be provided, organizations consider alternate processing sites for power-related contingencies.
","uuid":"be674b1b-7aa9-4a6e-9f89-11b0253d85b7","family":"Physical and Environmental Protection","parameters":[],"subControls":"","tests":[{"testId":"PE-12[01]","uuid":"0275e8ca-8963-4c40-96e3-a4610b4ec2c1","test":"Determine if automatic emergency lighting that activates in the event of a power outage or disruption is employed for the system;Organizations define their essential missions and functions.
","uuid":"4bb36f54-49ac-41df-a217-6b2814a05e24","family":"Physical and Environmental Protection","parameters":[],"subControls":"","tests":[{"testId":"PE-12(01)","uuid":"ecba3293-f1d9-42cb-8302-640563befb57","test":"Determine if emergency lighting is provided for all areas within the facility supporting essential mission and business functions.The provision of fire detection and suppression systems applies primarily to organizational facilities that contain concentrations of system resources, including data centers, server rooms, and mainframe computer rooms. Fire detection and suppression systems that may require an independent energy source include sprinkler systems and smoke detectors. An independent energy source is an energy source, such as a microgrid, that is separate, or can be separated, from the energy sources providing power for the other parts of the facility.
","uuid":"9e0c3d51-e525-4e86-8d7c-99647a2c1e8c","family":"Physical and Environmental Protection","parameters":[],"subControls":"","tests":[{"testId":"PE-13[01]","uuid":"66808ab9-cc57-43c3-989c-7d9a814bcd71","test":"Determine if fire detection systems are employed;Organizations can identify personnel, roles, and emergency responders if individuals on the notification list need to have access authorizations or clearances (e.g., to enter to facilities where access is restricted due to the classification or impact level of information within the facility). Notification mechanisms may require independent energy sources to ensure that the notification capability is not adversely affected by the fire.
","uuid":"97a916af-b501-4112-92e2-347e9349430b","family":"Physical and Environmental Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"f7204917-77ff-4e18-b521-8fa637befc40","text":"personnel or roles","parameterId":"pe-13.01_odp.01","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"57ad77f5-8bb1-4176-96a4-d79f5a5fb0f7","text":"emergency responders","parameterId":"pe-13.01_odp.02","default":" [Assignment: organization defined emergency responders] "}],"subControls":"","tests":[{"testId":"PE-13(01)[01]","uuid":"f306dbfe-cc30-4644-b998-bdfb13ea0f8c","test":"Determine if fire detection systems that activate automatically are employed in the event of a fire;Organizations can identify specific personnel, roles, and emergency responders if individuals on the notification list need to have appropriate access authorizations and/or clearances (e.g., to enter to facilities where access is restricted due to the impact level or classification of information within the facility). Notification mechanisms may require independent energy sources to ensure that the notification capability is not adversely affected by the fire.
","uuid":"362f2d8a-2e98-407d-8f40-c99ba78b4f8d","family":"Physical and Environmental Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"bd6dce20-8035-4ceb-9188-36b5ce82886f","text":"personnel or roles","parameterId":"pe-13.02_odp.01","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"4429cf2d-cee2-47ed-85a3-e04556c8a035","text":"emergency responders","parameterId":"pe-13.02_odp.02","default":" [Assignment: organization defined emergency responders] "}],"subControls":"","tests":[{"testId":"PE-13(02)(a)[01]","uuid":"1ed9cf80-94ee-4e2d-aa73-d9acfd6eb6ba","test":"Determine if fire suppression systems that activate automatically are employed;Authorized and qualified personnel within the jurisdiction of the organization include state, county, and city fire inspectors and fire marshals. Organizations provide escorts during inspections in situations where the systems that reside within the facilities contain sensitive information.
","uuid":"2c8f8963-bdd5-494e-915a-7ec7af8d2b47","family":"Physical and Environmental Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"b9ebde33-2d98-40eb-b883-4c64d1b45a01","text":"frequency","parameterId":"pe-13.04_odp.01","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"14596d28-403b-48d2-8f13-1f094402f9fa","text":"time period","parameterId":"pe-13.04_odp.02","default":" [Assignment: organization defined time period] "}],"subControls":"","tests":[{"testId":"PE-13(04)[01]","uuid":"8619ccdd-3f79-4380-bca8-170f528399c2","test":"Determine if the facility undergoes fire protection inspections [SELECTED PARAMETER VALUE(S): frequency ] by authorized and qualified inspectors;The provision of environmental controls applies primarily to organizational facilities that contain concentrations of system resources (e.g., data centers, mainframe computer rooms, and server rooms). Insufficient environmental controls, especially in very harsh environments, can have a significant adverse impact on the availability of systems and system components that are needed to support organizational mission and business functions.
","uuid":"ac77d6be-04b2-43ed-834a-2df9c533b931","family":"Physical and Environmental Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"6e04ded7-2610-46a9-be16-16e19e9d46a4","text":"[Selection (one or more): temperature; humidity; pressure; radiation; [(NESTED PARAMETER) Assignment for pe-14_odp.02: environmental control]]","parameterId":"pe-14_odp.01","default":"[Selection (one or more): temperature; humidity; pressure; radiation; [(NESTED PARAMETER) Assignment for pe-14_odp.02: environmental control]]"},{"constraints":"","displayName":"","guidance":"","uuid":"3126803d-6576-4542-bd05-f063b0e5f0d9","text":"environmental control","parameterId":"pe-14_odp.02","default":" [Assignment: organization defined environmental control] "},{"constraints":"","displayName":"","guidance":"","uuid":"be510cb3-7aeb-4f7c-8d2e-650d952cb056","text":"acceptable levels","parameterId":"pe-14_odp.03","default":" [Assignment: organization defined acceptable levels] "},{"constraints":"","displayName":"","guidance":"","uuid":"15b0671d-df26-492a-97b0-71d63b78aaa4","text":"frequency","parameterId":"pe-14_odp.04","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"PE-14a.","uuid":"a8498991-4908-44fa-a584-1542e72842ef","test":"Determine if [SELECTED PARAMETER VALUE(S): [Selection (one or more): temperature; humidity; pressure; radiation; [(NESTED PARAMETER) Assignment for pe-14_odp.02: environmental control]] ] levels are maintained at [SELECTED PARAMETER VALUE(S): acceptable levels ] within the facility where the system resides;The implementation of automatic environmental controls provides an immediate response to environmental conditions that can damage, degrade, or destroy organizational systems or systems components.
","uuid":"150cc9fe-0a2a-4cee-8196-46c5341cc07b","family":"Physical and Environmental Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"56291175-f803-48e4-bafb-ae6bf2757b7d","text":"automatic environmental controls","parameterId":"pe-14.01_odp","default":" [Assignment: organization defined automatic environmental controls] "}],"subControls":"","tests":[{"testId":"PE-14(01)","uuid":"82d5d582-1825-46e0-b93f-383c90e13d14","test":"Determine if [SELECTED PARAMETER VALUE(S): automatic environmental controls ] are employed in the facility to prevent fluctuations that are potentially harmful to the system.The alarm or notification may be an audible alarm or a visual message in real time to personnel or roles defined by the organization. Such alarms and notifications can help minimize harm to individuals and damage to organizational assets by facilitating a timely incident response.
","uuid":"d9181300-5a55-4ff9-a5e3-a0810e7b593f","family":"Physical and Environmental Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"3bb6e9e4-5efb-4ba0-9093-e72aa644537d","text":"personnel or roles","parameterId":"pe-14.02_odp","default":" [Assignment: organization defined personnel or roles] "}],"subControls":"","tests":[{"testId":"PE-14(02)[01]","uuid":"dea165d3-f586-41c7-8835-9a5dfec20d33","test":"Determine if environmental control monitoring is employed;The provision of water damage protection primarily applies to organizational facilities that contain concentrations of system resources, including data centers, server rooms, and mainframe computer rooms. Isolation valves can be employed in addition to or in lieu of master shutoff valves to shut off water supplies in specific areas of concern without affecting entire organizations.
","uuid":"9cb9107c-51e0-4bca-8534-35893c2cb4dd","family":"Physical and Environmental Protection","parameters":[],"subControls":"","tests":[{"testId":"PE-15[01]","uuid":"778239f9-3dbd-414f-8745-88ea16382ee3","test":"Determine if the system is protected from damage resulting from water leakage by providing master shutoff or isolation valves;Automated mechanisms include notification systems, water detection sensors, and alarms.
","uuid":"4b5efcb6-2b21-46f3-9850-95f369ca42d7","family":"Physical and Environmental Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"9e987455-a13c-43fa-a1da-7dbb99032027","text":"personnel or roles","parameterId":"pe-15.01_odp.01","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"0b104f6f-66eb-4135-b24e-6c050992d725","text":"automated mechanisms","parameterId":"pe-15.01_odp.02","default":" [Assignment: organization defined automated mechanisms] "}],"subControls":"","tests":[{"testId":"PE-15(01)[01]","uuid":"1ce3c9fb-9d2d-4f92-b71d-61cc104ad024","test":"Determine if the presence of water near the system can be detected automatically;Enforcing authorizations for entry and exit of system components may require restricting access to delivery areas and isolating the areas from the system and media libraries.
","uuid":"5b7257b8-c562-4013-8647-135ffa014f9f","family":"Physical and Environmental Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"578345c1-5361-40c3-89bb-42090f491de9","text":"organization-defined types of system components","parameterId":"pe-16_prm_1","default":" [Assignment: organization-defined types of system components] "},{"constraints":"","displayName":"","guidance":"","uuid":"310016c9-29a4-41c2-9117-34923b3c5c56","text":"types of system components","parameterId":"pe-16_odp.01","default":" [Assignment: organization defined types of system components] "},{"constraints":"","displayName":"","guidance":"","uuid":"c88f574c-12ad-4d4a-bc37-cdb01cff1137","text":"types of system components","parameterId":"pe-16_odp.02","default":" [Assignment: organization defined types of system components] "}],"subControls":"","tests":[{"testId":"PE-16a.[01]","uuid":"1cc5a920-bf29-4f93-a704-a61344216808","test":"Determine if [SELECTED PARAMETER VALUE(S): types of system components ] are authorized when entering the facility;Alternate work sites include government facilities or the private residences of employees. While distinct from alternative processing sites, alternate work sites can provide readily available alternate locations during contingency operations. Organizations can define different sets of controls for specific alternate work sites or types of sites depending on the work-related activities conducted at the sites. Implementing and assessing the effectiveness of organization-defined controls and providing a means to communicate incidents at alternate work sites supports the contingency planning activities of organizations.
","uuid":"a8e461a0-a38f-46c1-bf35-061eb0e62b2a","family":"Physical and Environmental Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"81b2c03b-d611-41bc-975d-ace5240cb5a3","text":"alternate work sites","parameterId":"pe-17_odp.01","default":" [Assignment: organization defined alternate work sites] "},{"constraints":"","displayName":"","guidance":"","uuid":"becd73da-22f0-40bc-9e20-517084690b54","text":"controls","parameterId":"pe-17_odp.02","default":" [Assignment: organization defined controls] "}],"subControls":"","tests":[{"testId":"PE-17a.","uuid":"8eca72ce-d5d8-4547-bc68-734728dd42b5","test":"Determine if [SELECTED PARAMETER VALUE(S): alternate work sites ] are determined and documented;Physical and environmental hazards include floods, fires, tornadoes, earthquakes, hurricanes, terrorism, vandalism, an electromagnetic pulse, electrical interference, and other forms of incoming electromagnetic radiation. Organizations consider the location of entry points where unauthorized individuals, while not being granted access, might nonetheless be near systems. Such proximity can increase the risk of unauthorized access to organizational communications using wireless packet sniffers or microphones, or unauthorized disclosure of information.
","uuid":"91b63f97-68a3-47a4-bd75-25d2f4144ba3","family":"Physical and Environmental Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"06b2980c-e302-47cc-ba23-4767d078dc21","text":"physical and environmental hazards","parameterId":"pe-18_odp","default":" [Assignment: organization defined physical and environmental hazards] "}],"subControls":"","tests":[{"testId":"PE-18","uuid":"114075b7-f5d3-4af3-a84c-10fdddaa6cd6","test":"Determine if system components are positioned within the facility to minimize potential damage from [SELECTED PARAMETER VALUE(S): physical and environmental hazards ] and to minimize the opportunity for unauthorized access.Information leakage is the intentional or unintentional release of data or information to an untrusted environment from electromagnetic signals emanations. The security categories or classifications of systems (with respect to confidentiality), organizational security policies, and risk tolerance guide the selection of controls employed to protect systems against information leakage due to electromagnetic signals emanations.
","uuid":"4a619887-ec27-457e-8c57-aa65a4f99927","family":"Physical and Environmental Protection","parameters":[],"subControls":"","tests":[{"testId":"PE-19","uuid":"2943f010-9cf9-4e30-b85a-1eed9603ad3c","test":"Determine if the system is protected from information leakage due to electromagnetic signal emanations.Emissions Security (EMSEC) policies include the former TEMPEST policies.
","uuid":"e750f1bf-cf68-4d9d-aa41-8381cdf82e5a","family":"Physical and Environmental Protection","parameters":[],"subControls":"","tests":[{"testId":"PE-19(01)[01]","uuid":"43a65cf6-49e0-4655-8093-9b28f64b669c","test":"Determine if system components are protected in accordance with national emissions security policies and procedures based on the security category or classification of the information;Asset location technologies can help ensure that critical assets—including vehicles, equipment, and system components—remain in authorized locations. Organizations consult with the Office of the General Counsel and senior agency official for privacy regarding the deployment and use of asset location technologies to address potential privacy concerns.
","uuid":"91d1d699-807a-41d9-a98b-0a1498331645","family":"Physical and Environmental Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"6c2f68a7-87e6-40cb-a28d-4dfbd25c75a5","text":"asset location technologies","parameterId":"pe-20_odp.01","default":" [Assignment: organization defined asset location technologies] "},{"constraints":"","displayName":"","guidance":"","uuid":"5418aa94-d10b-43e8-8160-86869ea0e92e","text":"assets","parameterId":"pe-20_odp.02","default":" [Assignment: organization defined assets] "},{"constraints":"","displayName":"","guidance":"","uuid":"3bdaf279-376b-4269-ad19-28890e407df6","text":"controlled areas","parameterId":"pe-20_odp.03","default":" [Assignment: organization defined controlled areas] "}],"subControls":"","tests":[{"testId":"PE-20","uuid":"17f9f49e-4327-4ad8-87ea-7111b5c00949","test":"Determine if [SELECTED PARAMETER VALUE(S): asset location technologies ] are employed to track and monitor the location and movement of [SELECTED PARAMETER VALUE(S): assets ] within [SELECTED PARAMETER VALUE(S): controlled areas ].An electromagnetic pulse (EMP) is a short burst of electromagnetic energy that is spread over a range of frequencies. Such energy bursts may be natural or man-made. EMP interference may be disruptive or damaging to electronic equipment. Protective measures used to mitigate EMP risk include shielding, surge suppressors, ferro-resonant transformers, and earth grounding. EMP protection may be especially significant for systems and applications that are part of the U.S. critical infrastructure.
","uuid":"da16924d-61c1-4017-afa6-0847cf4d9d29","family":"Physical and Environmental Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"d35cad16-75dc-42ec-ac2b-aba46aa9eee1","text":"protective measures","parameterId":"pe-21_odp.01","default":" [Assignment: organization defined protective measures] "},{"constraints":"","displayName":"","guidance":"","uuid":"1bea8087-7e58-43ac-bfc1-c47c3fe6bfa9","text":"system and system components","parameterId":"pe-21_odp.02","default":" [Assignment: organization defined system and system components] "}],"subControls":"","tests":[{"testId":"PE-21","uuid":"d9b87787-677f-4295-b82b-186f50892d88","test":"Determine if [SELECTED PARAMETER VALUE(S): protective measures ] are employed against electromagnetic pulse damage for [SELECTED PARAMETER VALUE(S): system and system components ].Hardware components that may require marking include input and output devices. Input devices include desktop and notebook computers, keyboards, tablets, and smart phones. Output devices include printers, monitors/video displays, facsimile machines, scanners, copiers, and audio devices. Permissions controlling output to the output devices are addressed in AC-3 or AC-4 . Components are marked to indicate the impact level or classification level of the system to which the devices are connected, or the impact level or classification level of the information permitted to be output. Security marking refers to the use of human-readable security attributes. Security labeling refers to the use of security attributes for internal system data structures. Security marking is generally not required for hardware components that process, store, or transmit information determined by organizations to be in the public domain or to be publicly releasable. However, organizations may require markings for hardware components that process, store, or transmit public information in order to indicate that such information is publicly releasable. Marking of system hardware components reflects applicable laws, executive orders, directives, policies, regulations, and standards.
","uuid":"db72444d-db26-4a99-b370-26fa579f3130","family":"Physical and Environmental Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"f235d7fb-a999-4e4b-8fb9-1f2382cacef6","text":"system hardware components","parameterId":"pe-22_odp","default":" [Assignment: organization defined system hardware components] "}],"subControls":"","tests":[{"testId":"PE-22","uuid":"187f64e8-5f76-4f29-9e5e-687bb0beda2d","test":"Determine if [SELECTED PARAMETER VALUE(S): system hardware components ] are marked indicating the impact level or classification level of the information permitted to be processed, stored, or transmitted by the hardware component.Physical and environmental hazards include floods, fires, tornadoes, earthquakes, hurricanes, terrorism, vandalism, an electromagnetic pulse, electrical interference, and other forms of incoming electromagnetic radiation. The location of system components within the facility is addressed in PE-18.
","uuid":"7d9f68af-f152-43b5-94ec-4df96c49f87a","family":"Physical and Environmental Protection","parameters":[],"subControls":"","tests":[{"testId":"PE-23a.","uuid":"5bbca6e0-1647-406a-a160-033d1b39d0b7","test":"Determine if the location or site of the facility where the system resides is planned considering physical and environmental hazards;Planning policy and procedures for the controls in the PL family implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on their development. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission level or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission/business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to planning policy and procedures include, but are not limited to, assessment or audit findings, security incidents or breaches, or changes in laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure.
","uuid":"08d0cefd-96b1-4db6-9ed6-3047a9004734","family":"Planning","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"46e4f480-2a02-4208-b065-6ab3a5703a2c","text":"organization-defined personnel or roles","parameterId":"pl-1_prm_1","default":" [Assignment: organization-defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"90ba628a-8c5d-4356-9cde-7e94512ab206","text":"personnel or roles","parameterId":"pl-01_odp.01","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"d3c5f840-5527-42a2-8ce2-06b2d13608c2","text":"personnel or roles","parameterId":"pl-01_odp.02","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"ed9425c5-5f35-4aeb-8a40-1eb28e1a8996","text":"[Selection (one or more): organization-level; mission/business process-level; system-level]","parameterId":"pl-01_odp.03","default":"[Selection (one or more): organization-level; mission/business process-level; system-level]"},{"constraints":"","displayName":"","guidance":"","uuid":"5dbbb7bc-7f66-4ee2-bf1a-a4088279add3","text":"official","parameterId":"pl-01_odp.04","default":" [Assignment: organization defined official] "},{"constraints":"","displayName":"","guidance":"","uuid":"24c6b47f-45cb-432d-bf67-7d808154ec80","text":"frequency","parameterId":"pl-01_odp.05","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"140614b6-10a0-40bb-8526-27672e2fb510","text":"events","parameterId":"pl-01_odp.06","default":" [Assignment: organization defined events] "},{"constraints":"","displayName":"","guidance":"","uuid":"2cf632d5-b638-4cd4-bd4b-e7987e21563f","text":"frequency","parameterId":"pl-01_odp.07","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"013c6e4e-6dff-4ca7-9b85-5c39cd166519","text":"events","parameterId":"pl-01_odp.08","default":" [Assignment: organization defined events] "}],"subControls":"","tests":[{"testId":"PL-01a.[01]","uuid":"afb258e4-380f-43d9-a3f3-31493e4986ea","test":"Determine if a planning policy is developed and documented.System security and privacy plans are scoped to the system and system components within the defined authorization boundary and contain an overview of the security and privacy requirements for the system and the controls selected to satisfy the requirements. The plans describe the intended application of each selected control in the context of the system with a sufficient level of detail to correctly implement the control and to subsequently assess the effectiveness of the control. The control documentation describes how system-specific and hybrid controls are implemented and the plans and expectations regarding the functionality of the system. System security and privacy plans can also be used in the design and development of systems in support of life cycle-based security and privacy engineering processes. System security and privacy plans are living documents that are updated and adapted throughout the system development life cycle (e.g., during capability determination, analysis of alternatives, requests for proposal, and design reviews). Section 2.1 describes the different types of requirements that are relevant to organizations during the system development life cycle and the relationship between requirements and controls.
Organizations may develop a single, integrated security and privacy plan or maintain separate plans. Security and privacy plans relate security and privacy requirements to a set of controls and control enhancements. The plans describe how the controls and control enhancements meet the security and privacy requirements but do not provide detailed, technical descriptions of the design or implementation of the controls and control enhancements. Security and privacy plans contain sufficient information (including specifications of control parameter values for selection and assignment operations explicitly or by reference) to enable a design and implementation that is unambiguously compliant with the intent of the plans and subsequent determinations of risk to organizational operations and assets, individuals, other organizations, and the Nation if the plan is implemented.
Security and privacy plans need not be single documents. The plans can be a collection of various documents, including documents that already exist. Effective security and privacy plans make extensive use of references to policies, procedures, and additional documents, including design and implementation specifications where more detailed information can be obtained. The use of references helps reduce the documentation associated with security and privacy programs and maintains the security- and privacy-related information in other established management and operational areas, including enterprise architecture, system development life cycle, systems engineering, and acquisition. Security and privacy plans need not contain detailed contingency plan or incident response plan information but can instead provide—explicitly or by reference—sufficient information to define what needs to be accomplished by those plans.
Security- and privacy-related activities that may require coordination and planning with other individuals or groups within the organization include assessments, audits, inspections, hardware and software maintenance, acquisition and supply chain risk management, patch management, and contingency plan testing. Planning and coordination include emergency and nonemergency (i.e., planned or non-urgent unplanned) situations. The process defined by organizations to plan and coordinate security- and privacy-related activities can also be included in other documents, as appropriate.
","uuid":"67877581-b877-4007-93d7-d7a97dc4e99a","family":"Planning","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"70a0add1-f0f5-4fd7-a2df-0d0b9480d352","text":"individuals or groups","parameterId":"pl-02_odp.01","default":" [Assignment: organization defined individuals or groups] "},{"constraints":"","displayName":"","guidance":"","uuid":"761f3b98-79aa-471b-83df-84ebe6d68cf0","text":"personnel or roles","parameterId":"pl-02_odp.02","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"5d912f57-e19e-4776-b6fc-74911e7a6ed4","text":"frequency","parameterId":"pl-02_odp.03","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"PL-02a.01[01]","uuid":"a6afc843-68dc-4bf4-a4ed-7b6bf56c3480","test":"Determine if a security plan for the system is developed that is consistent with the organization’s enterprise architecture;Rules of behavior represent a type of access agreement for organizational users. Other types of access agreements include nondisclosure agreements, conflict-of-interest agreements, and acceptable use agreements (see PS-6 ). Organizations consider rules of behavior based on individual user roles and responsibilities and differentiate between rules that apply to privileged users and rules that apply to general users. Establishing rules of behavior for some types of non-organizational users, including individuals who receive information from federal systems, is often not feasible given the large number of such users and the limited nature of their interactions with the systems. Rules of behavior for organizational and non-organizational users can also be established in AC-8 . The related controls section provides a list of controls that are relevant to organizational rules of behavior. PL-4b , the documented acknowledgment portion of the control, may be satisfied by the literacy training and awareness and role-based training programs conducted by organizations if such training includes rules of behavior. Documented acknowledgements for rules of behavior include electronic or physical signatures and electronic agreement check boxes or radio buttons.
","uuid":"0fab75ea-c282-46d0-a68b-c5a7aa0359f4","family":"Planning","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"afcf7550-1e24-4a90-8cb6-61b74d06702d","text":"frequency","parameterId":"pl-04_odp.01","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"6998b2ef-9b03-4b88-89ce-3a2cb28f811d","text":"[Selection (one or more): [(NESTED PARAMETER) Assignment for pl-04_odp.03: frequency]; when the rules are revised or updated]","parameterId":"pl-04_odp.02","default":"[Selection (one or more): [(NESTED PARAMETER) Assignment for pl-04_odp.03: frequency]; when the rules are revised or updated]"},{"constraints":"","displayName":"","guidance":"","uuid":"9e95cd63-6c3a-4802-a190-9a40eb315cd0","text":"frequency","parameterId":"pl-04_odp.03","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"PL-04a.[01]","uuid":"ea4817cc-ea1d-4df5-abe2-c165b69c237e","test":"Determine if rules that describe responsibilities and expected behavior for information and system usage, security, and privacy are established for individuals requiring access to the system;Social media, social networking, and external site/application usage restrictions address rules of behavior related to the use of social media, social networking, and external sites when organizational personnel are using such sites for official duties or in the conduct of official business, when organizational information is involved in social media and social networking transactions, and when personnel access social media and networking sites from organizational systems. Organizations also address specific rules that prevent unauthorized entities from obtaining non-public organizational information from social media and networking sites either directly or through inference. Non-public information includes personally identifiable information and system account information.
","uuid":"140a5bf6-28c0-43a1-b142-3a74c7fb6895","family":"Planning","parameters":[],"subControls":"","tests":[{"testId":"PL-04(01)(a)","uuid":"be141198-757e-48f4-98da-5e0026fce683","test":"Determine if the rules of behavior include restrictions on the use of social media, social networking sites, and external sites/applications;The CONOPS may be included in the security or privacy plans for the system or in other system development life cycle documents. The CONOPS is a living document that requires updating throughout the system development life cycle. For example, during system design reviews, the concept of operations is checked to ensure that it remains consistent with the design for controls, the system architecture, and the operational procedures. Changes to the CONOPS are reflected in ongoing updates to the security and privacy plans, security and privacy architectures, and other organizational documents, such as procurement specifications, system development life cycle documents, and systems engineering documents.
","uuid":"52f83e5b-2441-4d62-ab4e-b2534869a3fe","family":"Planning","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"4cfc8649-1f59-4e5d-be2f-db9b8b08c919","text":"frequency","parameterId":"pl-07_odp","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"PL-07a.","uuid":"780ee5c9-38cb-4527-80df-13fd52b78387","test":"Determine if a conops for the system describing how the organization intends to operate the system from the perspective of information security and privacy is developed;The security and privacy architectures at the system level are consistent with the organization-wide security and privacy architectures described in PM-7 , which are integral to and developed as part of the enterprise architecture. The architectures include an architectural description, the allocation of security and privacy functionality (including controls), security- and privacy-related information for external interfaces, information being exchanged across the interfaces, and the protection mechanisms associated with each interface. The architectures can also include other information, such as user roles and the access privileges assigned to each role; security and privacy requirements; types of information processed, stored, and transmitted by the system; supply chain risk management requirements; restoration priorities of information and system services; and other protection needs.
SP 800-160-1 provides guidance on the use of security architectures as part of the system development life cycle process. OMB M-19-03 requires the use of the systems security engineering concepts described in SP 800-160-1 for high value assets. Security and privacy architectures are reviewed and updated throughout the system development life cycle, from analysis of alternatives through review of the proposed architecture in the RFP responses to the design reviews before and during implementation (e.g., during preliminary design reviews and critical design reviews).
In today’s modern computing architectures, it is becoming less common for organizations to control all information resources. There may be key dependencies on external information services and service providers. Describing such dependencies in the security and privacy architectures is necessary for developing a comprehensive mission and business protection strategy. Establishing, developing, documenting, and maintaining under configuration control a baseline configuration for organizational systems is critical to implementing and maintaining effective architectures. The development of the architectures is coordinated with the senior agency information security officer and the senior agency official for privacy to ensure that the controls needed to support security and privacy requirements are identified and effectively implemented. In many circumstances, there may be no distinction between the security and privacy architecture for a system. In other circumstances, security objectives may be adequately satisfied, but privacy objectives may only be partially satisfied by the security requirements. In these cases, consideration of the privacy requirements needed to achieve satisfaction will result in a distinct privacy architecture. The documentation, however, may simply reflect the combined architectures.
PL-8 is primarily directed at organizations to ensure that architectures are developed for the system and, moreover, that the architectures are integrated with or tightly coupled to the enterprise architecture. In contrast, SA-17 is primarily directed at the external information technology product and system developers and integrators. SA-17 , which is complementary to PL-8 , is selected when organizations outsource the development of systems or components to external entities and when there is a need to demonstrate consistency with the organization’s enterprise architecture and security and privacy architectures.
","uuid":"546716ef-c718-4467-a128-ea5008a280b5","family":"Planning","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"27950226-90f0-442b-9ea3-57d5c194fd58","text":"frequency","parameterId":"pl-08_odp","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"PL-08a.01","uuid":"eb9f2646-aa33-41be-8513-d13b2da576b5","test":"Determine if a security architecture for the system describes the requirements and approach to be taken for protecting the confidentiality, integrity, and availability of organizational information;Organizations strategically allocate security and privacy controls in the security and privacy architectures so that adversaries must overcome multiple controls to achieve their objective. Requiring adversaries to defeat multiple controls makes it more difficult to attack information resources by increasing the work factor of the adversary; it also increases the likelihood of detection. The coordination of allocated controls is essential to ensure that an attack that involves one control does not create adverse, unintended consequences by interfering with other controls. Unintended consequences can include system lockout and cascading alarms. The placement of controls in systems and organizations is an important activity that requires thoughtful analysis. The value of organizational assets is an important consideration in providing additional layering. Defense-in-depth architectural approaches include modularity and layering (see SA-8(3) ), separation of system and user functionality (see SC-2 ), and security function isolation (see SC-3).
","uuid":"dfa63af8-fa4b-487a-9778-ece6b652c78a","family":"Planning","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"09d45449-d35b-434f-9456-b4864ed0c00b","text":"controls","parameterId":"pl-08.01_odp.01","default":" [Assignment: organization defined controls] "},{"constraints":"","displayName":"","guidance":"","uuid":"934b0f6d-369a-45b6-a2de-fbf556153b36","text":"locations and architectural layers","parameterId":"pl-08.01_odp.02","default":" [Assignment: organization defined locations and architectural layers] "}],"subControls":"","tests":[{"testId":"PL-08(01)(a)[01]","uuid":"8ce697da-20d6-4fe3-b993-d0369f68b79d","test":"Determine if the security architecture for the system is designed using a defense-in-depth approach that allocates [SELECTED PARAMETER VALUE(S): controls ] to [SELECTED PARAMETER VALUE(S): locations and architectural layers ];Information technology products have different strengths and weaknesses. Providing a broad spectrum of products complements the individual offerings. For example, vendors offering malicious code protection typically update their products at different times, often developing solutions for known viruses, Trojans, or worms based on their priorities and development schedules. By deploying different products at different locations, there is an increased likelihood that at least one of the products will detect the malicious code. With respect to privacy, vendors may offer products that track personally identifiable information in systems. Products may use different tracking methods. Using multiple products may result in more assurance that personally identifiable information is inventoried.
","uuid":"5427ae62-2f8e-4853-b123-7186a2ff0581","family":"Planning","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"8b35ebff-90c0-4596-a4d4-e73c92d3e9e8","text":"controls","parameterId":"pl-08.02_odp.01","default":" [Assignment: organization defined controls] "},{"constraints":"","displayName":"","guidance":"","uuid":"be7d1fc2-b6cf-4c95-926a-0dd85717008b","text":"locations and architectural layers","parameterId":"pl-08.02_odp.02","default":" [Assignment: organization defined locations and architectural layers] "}],"subControls":"","tests":[{"testId":"PL-08(02)","uuid":"0c10d374-2aaa-4dcf-9445-49daf2aeaccc","test":"Determine if [SELECTED PARAMETER VALUE(S): controls ] that are allocated to [SELECTED PARAMETER VALUE(S): locations and architectural layers ] are required to be obtained from different suppliers.Central management refers to organization-wide management and implementation of selected controls and processes. This includes planning, implementing, assessing, authorizing, and monitoring the organization-defined, centrally managed controls and processes. As the central management of controls is generally associated with the concept of common (inherited) controls, such management promotes and facilitates standardization of control implementations and management and the judicious use of organizational resources. Centrally managed controls and processes may also meet independence requirements for assessments in support of initial and ongoing authorizations to operate and as part of organizational continuous monitoring.
Automated tools (e.g., security information and event management tools or enterprise security monitoring and management tools) can improve the accuracy, consistency, and availability of information associated with centrally managed controls and processes. Automation can also provide data aggregation and data correlation capabilities; alerting mechanisms; and dashboards to support risk-based decision-making within the organization.
As part of the control selection processes, organizations determine the controls that may be suitable for central management based on resources and capabilities. It is not always possible to centrally manage every aspect of a control. In such cases, the control can be treated as a hybrid control with the control managed and implemented centrally or at the system level. The controls and control enhancements that are candidates for full or partial central management include but are not limited to: AC-2(1), AC-2(2), AC-2(3), AC-2(4), AC-4(all), AC-17(1), AC-17(2), AC-17(3), AC-17(9), AC-18(1), AC-18(3), AC-18(4), AC-18(5), AC-19(4), AC-22, AC-23, AT-2(1), AT-2(2), AT-3(1), AT-3(2), AT-3(3), AT-4, AU-3, AU-6(1), AU-6(3), AU-6(5), AU-6(6), AU-6(9), AU-7(1), AU-7(2), AU-11, AU-13, AU-16, CA-2(1), CA-2(2), CA-2(3), CA-3(1), CA-3(2), CA-3(3), CA-7(1), CA-9, CM-2(2), CM-3(1), CM-3(4), CM-4, CM-6, CM-6(1), CM-7(2), CM-7(4), CM-7(5), CM-8(all), CM-9(1), CM-10, CM-11, CP-7(all), CP-8(all), SC-43, SI-2, SI-3, SI-4(all), SI-7, SI-8.
","uuid":"c313338b-b86e-4d0a-bd74-4292b58cc1fd","family":"Planning","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"cb0e5a31-3ab7-4501-bf3d-25fcee7a2993","text":"controls and related processes","parameterId":"pl-09_odp","default":" [Assignment: organization defined controls and related processes] "}],"subControls":"","tests":[{"testId":"PL-09","uuid":"bc970573-7fdb-4cea-918a-6dda15bf463d","test":"Determine if [SELECTED PARAMETER VALUE(S): controls and related processes ] are centrally managed.Control baselines are predefined sets of controls specifically assembled to address the protection needs of a group, organization, or community of interest. Controls are chosen for baselines to either satisfy mandates imposed by laws, executive orders, directives, regulations, policies, standards, and guidelines or address threats common to all users of the baseline under the assumptions specific to the baseline. Baselines represent a starting point for the protection of individuals’ privacy, information, and information systems with subsequent tailoring actions to manage risk in accordance with mission, business, or other constraints (see PL-11 ). Federal control baselines are provided in SP 800-53B . The selection of a control baseline is determined by the needs of stakeholders. Stakeholder needs consider mission and business requirements as well as mandates imposed by applicable laws, executive orders, directives, policies, regulations, standards, and guidelines. For example, the control baselines in SP 800-53B are based on the requirements from FISMA and PRIVACT . The requirements, along with the NIST standards and guidelines implementing the legislation, direct organizations to select one of the control baselines after the reviewing the information types and the information that is processed, stored, and transmitted on the system; analyzing the potential adverse impact of the loss or compromise of the information or system on the organization’s operations and assets, individuals, other organizations, or the Nation; and considering the results from system and organizational risk assessments. CNSSI 1253 provides guidance on control baselines for national security systems.
","uuid":"8b35abe0-b262-4e50-b8ab-50267b52e470","family":"Planning","parameters":[],"subControls":"","tests":[{"testId":"PL-10","uuid":"6c8f2219-1960-447e-996f-3282d1632647","test":"Determine if a control baseline for the system is selected.The concept of tailoring allows organizations to specialize or customize a set of baseline controls by applying a defined set of tailoring actions. Tailoring actions facilitate such specialization and customization by allowing organizations to develop security and privacy plans that reflect their specific mission and business functions, the environments where their systems operate, the threats and vulnerabilities that can affect their systems, and any other conditions or situations that can impact their mission or business success. Tailoring guidance is provided in SP 800-53B . Tailoring a control baseline is accomplished by identifying and designating common controls, applying scoping considerations, selecting compensating controls, assigning values to control parameters, supplementing the control baseline with additional controls as needed, and providing information for control implementation. The general tailoring actions in SP 800-53B can be supplemented with additional actions based on the needs of organizations. Tailoring actions can be applied to the baselines in SP 800-53B in accordance with the security and privacy requirements from FISMA, PRIVACT , and OMB A-130 . Alternatively, other communities of interest adopting different control baselines can apply the tailoring actions in SP 800-53B to specialize or customize the controls that represent the specific needs and concerns of those entities.
","uuid":"ed49b92c-c217-4701-9b8d-cbf58ea57825","family":"Planning","parameters":[],"subControls":"","tests":[{"testId":"PL-11","uuid":"6488747c-25be-4c51-9596-895f2e59e71b","test":"Determine if the selected control baseline is tailored by applying specified tailoring actions.An information security program plan is a formal document that provides an overview of the security requirements for an organization-wide information security program and describes the program management controls and common controls in place or planned for meeting those requirements. An information security program plan can be represented in a single document or compilations of documents. Privacy program plans and supply chain risk management plans are addressed separately in PM-18 and SR-2 , respectively.
An information security program plan documents implementation details about program management and common controls. The plan provides sufficient information about the controls (including specification of parameters for assignment and selection operations, explicitly or by reference) to enable implementations that are unambiguously compliant with the intent of the plan and a determination of the risk to be incurred if the plan is implemented as intended. Updates to information security program plans include organizational changes and problems identified during plan implementation or control assessments.
Program management controls may be implemented at the organization level or the mission or business process level, and are essential for managing the organization’s information security program. Program management controls are distinct from common, system-specific, and hybrid controls because program management controls are independent of any particular system. Together, the individual system security plans and the organization-wide information security program plan provide complete coverage for the security controls employed within the organization.
Common controls available for inheritance by organizational systems are documented in an appendix to the organization’s information security program plan unless the controls are included in a separate security plan for a system. The organization-wide information security program plan indicates which separate security plans contain descriptions of common controls.
Events that may precipitate an update to the information security program plan include, but are not limited to, organization-wide assessment or audit findings, security incidents or breaches, or changes in laws, executive orders, directives, regulations, policies, standards, and guidelines.
","uuid":"e23b20b5-e65f-41f3-b888-1ac5e38e020d","family":"Program Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"456890a9-0ff5-4c74-9a13-ffb0f11b7e84","text":"frequency","parameterId":"pm-01_odp.01","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"cc766865-4707-48dd-bdaf-d0f0529b58a0","text":"events","parameterId":"pm-01_odp.02","default":" [Assignment: organization defined events] "}],"subControls":"","tests":[{"testId":"PM-01a.[01]","uuid":"f3b6dffc-538c-4693-8021-1d73223f9ab0","test":"Determine if an organization-wide information security program plan is developed;The senior agency information security officer is an organizational official. For federal agencies (as defined by applicable laws, executive orders, regulations, directives, policies, and standards), this official is the senior agency information security officer. Organizations may also refer to this official as the senior information security officer or chief information security officer.
","uuid":"9c0f53ca-4c7a-439b-8fd2-c06950b672cc","family":"Program Management","parameters":[],"subControls":"","tests":[{"testId":"PM-02[01]","uuid":"6f9fb257-8f5d-4773-b9e2-be5f11438fd0","test":"Determine if a senior agency information security officer is appointed;Organizations consider establishing champions for information security and privacy and, as part of including the necessary resources, assign specialized expertise and resources as needed. Organizations may designate and empower an Investment Review Board or similar group to manage and provide oversight for the information security and privacy aspects of the capital planning and investment control process.
","uuid":"76fd4a64-5e67-492f-9ea2-84621ee5d5b4","family":"Program Management","parameters":[],"subControls":"","tests":[{"testId":"PM-03a.[01]","uuid":"3109260c-e21f-44c1-abf1-a0258879c202","test":"Determine if the resources needed to implement the information security program are included in capital planning and investment requests, and all exceptions are documented;The plan of action and milestones is a key organizational document and is subject to reporting requirements established by the Office of Management and Budget. Organizations develop plans of action and milestones with an organization-wide perspective, prioritizing risk response actions and ensuring consistency with the goals and objectives of the organization. Plan of action and milestones updates are based on findings from control assessments and continuous monitoring activities. There can be multiple plans of action and milestones corresponding to the information system level, mission/business process level, and organizational/governance level. While plans of action and milestones are required for federal organizations, other types of organizations can help reduce risk by documenting and tracking planned remediations. Specific guidance on plans of action and milestones at the system level is provided in CA-5.
","uuid":"2a4d577d-3f2e-432c-891a-3bf0dccbab6e","family":"Program Management","parameters":[],"subControls":"","tests":[{"testId":"PM-04a.01[01]","uuid":"10ae1be2-6ad6-4e64-bbe1-add3c4562f13","test":"Determine if a process to ensure that plans of action and milestones for the information security program and associated organizational systems are developed;OMB A-130 provides guidance on developing systems inventories and associated reporting requirements. System inventory refers to an organization-wide inventory of systems, not system components as described in CM-8.
","uuid":"18d51750-f2b1-413a-8795-d33871de0bfa","family":"Program Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"7dea8faf-f9d3-4235-a9fb-8d7ee4291879","text":"frequency","parameterId":"pm-05_odp","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"PM-05[01]","uuid":"7d5cf99d-7a90-47eb-882c-48704decce98","test":"Determine if an inventory of organizational systems is developed;An inventory of systems, applications, and projects that process personally identifiable information supports the mapping of data actions, providing individuals with privacy notices, maintaining accurate personally identifiable information, and limiting the processing of personally identifiable information when such information is not needed for operational purposes. Organizations may use this inventory to ensure that systems only process the personally identifiable information for authorized purposes and that this processing is still relevant and necessary for the purpose specified therein.
","uuid":"f5cc5bdc-6d4b-49f2-9031-7fa19d88036d","family":"Program Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"e4a7d665-8b87-4a3d-96f9-47a8f5532652","text":"frequency","parameterId":"pm-05.01_odp","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"PM-05(01)[01]","uuid":"d756c570-7d30-4dbc-9343-61023fc49a53","test":"Determine if an inventory of all systems, applications, and projects that process personally identifiable information is established;Measures of performance are outcome-based metrics used by an organization to measure the effectiveness or efficiency of the information security and privacy programs and the controls employed in support of the program. To facilitate security and privacy risk management, organizations consider aligning measures of performance with the organizational risk tolerance as defined in the risk management strategy.
","uuid":"98ac16dd-b1bf-4ac8-a8fa-9ee73f0c542e","family":"Program Management","parameters":[],"subControls":"","tests":[{"testId":"PM-06[01]","uuid":"28b4c9e1-4dc5-4c66-af1d-9e58573ce948","test":"Determine if information security measures of performance are developed;The integration of security and privacy requirements and controls into the enterprise architecture helps to ensure that security and privacy considerations are addressed throughout the system development life cycle and are explicitly related to the organization’s mission and business processes. The process of security and privacy requirements integration also embeds into the enterprise architecture and the organization’s security and privacy architectures consistent with the organizational risk management strategy. For PM-7, security and privacy architectures are developed at a system-of-systems level, representing all organizational systems. For PL-8 , the security and privacy architectures are developed at a level that represents an individual system. The system-level architectures are consistent with the security and privacy architectures defined for the organization. Security and privacy requirements and control integration are most effectively accomplished through the rigorous application of the Risk Management Framework SP 800-37 and supporting security standards and guidelines.
","uuid":"221a3e72-eb88-4c5d-8256-72c542362d60","family":"Program Management","parameters":[],"subControls":"","tests":[{"testId":"PM-07[01]","uuid":"d5007d1a-103b-43b8-b6c0-b628294f02e7","test":"Determine if an enterprise architecture is developed with consideration for information security;Not every function or service that a system provides is essential to organizational mission or business functions. Printing or copying is an example of a non-essential but supporting service for an organization. Whenever feasible, such supportive but non-essential functions or services are not co-located with the functions or services that support essential mission or business functions. Maintaining such functions on the same system or system component increases the attack surface of the organization’s mission-essential functions or services. Moving supportive but non-essential functions to a non-critical system, system component, or external provider can also increase efficiency by putting those functions or services under the control of individuals or providers who are subject matter experts in the functions or services.
","uuid":"a0d451d9-a648-416b-ae42-a8e2276ae6d2","family":"Program Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"36d4fd85-3148-41e1-99ab-d4b272d0be74","text":"non-essential functions or services","parameterId":"pm-07.01_odp","default":" [Assignment: organization defined non-essential functions or services] "}],"subControls":"","tests":[{"testId":"PM-07(01)","uuid":"a4e9dce0-3f60-4cf3-8a2f-6408d5065752","test":"Determine if [SELECTED PARAMETER VALUE(S): non-essential functions or services ] are offloaded to other systems, system components, or an external provider.Protection strategies are based on the prioritization of critical assets and resources. The requirement and guidance for defining critical infrastructure and key resources and for preparing an associated critical infrastructure protection plan are found in applicable laws, executive orders, directives, policies, regulations, standards, and guidelines.
","uuid":"5f8bf4e7-b76e-4b04-8ed6-271fa7562f2b","family":"Program Management","parameters":[],"subControls":"","tests":[{"testId":"PM-08[01]","uuid":"70003389-730f-4b8d-b7e7-e5038c1b59e7","test":"Determine if information security issues are addressed in the development of a critical infrastructure and key resources protection plan;An organization-wide risk management strategy includes an expression of the security and privacy risk tolerance for the organization, security and privacy risk mitigation strategies, acceptable risk assessment methodologies, a process for evaluating security and privacy risk across the organization with respect to the organization’s risk tolerance, and approaches for monitoring risk over time. The senior accountable official for risk management (agency head or designated official) aligns information security management processes with strategic, operational, and budgetary planning processes. The risk executive function, led by the senior accountable official for risk management, can facilitate consistent application of the risk management strategy organization-wide. The risk management strategy can be informed by security and privacy risk-related inputs from other sources, both internal and external to the organization, to ensure that the strategy is broad-based and comprehensive. The supply chain risk management strategy described in PM-30 can also provide useful inputs to the organization-wide risk management strategy.
","uuid":"6b1e3a45-b445-4f65-b8aa-dfdf4cc6bb21","family":"Program Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"7c677e2a-4e7e-447f-aa02-ccc167ae5985","text":"frequency","parameterId":"pm-09_odp","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"PM-09a.01","uuid":"27664044-5b2f-47fa-a15d-8dbcb77d2986","test":"Determine if a comprehensive strategy is developed to manage security risk to organizational operations and assets, individuals, other organizations, and the nation associated with the operation and use of organizational systems;Authorization processes for organizational systems and environments of operation require the implementation of an organization-wide risk management process and associated security and privacy standards and guidelines. Specific roles for risk management processes include a risk executive (function) and designated authorizing officials for each organizational system and common control provider. The authorization processes for the organization are integrated with continuous monitoring processes to facilitate ongoing understanding and acceptance of security and privacy risks to organizational operations, organizational assets, individuals, other organizations, and the Nation.
","uuid":"b8ccef5b-6697-4092-a0a0-6ad88955315e","family":"Program Management","parameters":[],"subControls":"","tests":[{"testId":"PM-10a.[01]","uuid":"c55b36a8-1baf-40ff-9e45-7b3616c61e52","test":"Determine if the security state of organizational systems and the environments in which those systems operate are managed through authorization processes;Protection needs are technology-independent capabilities that are required to counter threats to organizations, individuals, systems, and the Nation through the compromise of information (i.e., loss of confidentiality, integrity, availability, or privacy). Information protection and personally identifiable information processing needs are derived from the mission and business needs defined by organizational stakeholders, the mission and business processes designed to meet those needs, and the organizational risk management strategy. Information protection and personally identifiable information processing needs determine the required controls for the organization and the systems. Inherent to defining protection and personally identifiable information processing needs is an understanding of the adverse impact that could result if a compromise or breach of information occurs. The categorization process is used to make such potential impact determinations. Privacy risks to individuals can arise from the compromise of personally identifiable information, but they can also arise as unintended consequences or a byproduct of the processing of personally identifiable information at any stage of the information life cycle. Privacy risk assessments are used to prioritize the risks that are created for individuals from system processing of personally identifiable information. These risk assessments enable the selection of the required privacy controls for the organization and systems. Mission and business process definitions and the associated protection requirements are documented in accordance with organizational policies and procedures.
","uuid":"1e9d02b0-582b-4c30-93ae-78be3fd590da","family":"Program Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"ffff7eee-7ab3-4c1b-9c75-f6bcafbe6be2","text":"frequency","parameterId":"pm-11_odp","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"PM-11a.[01]","uuid":"b7c9c5b4-9d1c-4430-932c-42ab5b052a66","test":"Determine if organizational mission and business processes are defined with consideration for information security;Organizations that handle classified information are required, under Executive Order 13587 EO 13587 and the National Insider Threat Policy ODNI NITP , to establish insider threat programs. The same standards and guidelines that apply to insider threat programs in classified environments can also be employed effectively to improve the security of controlled unclassified and other information in non-national security systems. Insider threat programs include controls to detect and prevent malicious insider activity through the centralized integration and analysis of both technical and nontechnical information to identify potential insider threat concerns. A senior official is designated by the department or agency head as the responsible individual to implement and provide oversight for the program. In addition to the centralized integration and analysis capability, insider threat programs require organizations to prepare department or agency insider threat policies and implementation plans, conduct host-based user monitoring of individual employee activities on government-owned classified computers, provide insider threat awareness training to employees, receive access to information from offices in the department or agency for insider threat analysis, and conduct self-assessments of department or agency insider threat posture.
Insider threat programs can leverage the existence of incident handling teams that organizations may already have in place, such as computer security incident response teams. Human resources records are especially important in this effort, as there is compelling evidence to show that some types of insider crimes are often preceded by nontechnical behaviors in the workplace, including ongoing patterns of disgruntled behavior and conflicts with coworkers and other colleagues. These precursors can guide organizational officials in more focused, targeted monitoring efforts. However, the use of human resource records could raise significant concerns for privacy. The participation of a legal team, including consultation with the senior agency official for privacy, ensures that monitoring activities are performed in accordance with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines.
","uuid":"883c8e07-731c-4115-b289-4917532fe970","family":"Program Management","parameters":[],"subControls":"","tests":[{"testId":"PM-12","uuid":"6444a65e-2477-4fa8-95c4-525ba6f9a027","test":"Determine if an insider threat program that includes a cross-discipline insider threat incident handling team is implemented.Security and privacy workforce development and improvement programs include defining the knowledge, skills, and abilities needed to perform security and privacy duties and tasks; developing role-based training programs for individuals assigned security and privacy roles and responsibilities; and providing standards and guidelines for measuring and building individual qualifications for incumbents and applicants for security- and privacy-related positions. Such workforce development and improvement programs can also include security and privacy career paths to encourage security and privacy professionals to advance in the field and fill positions with greater responsibility. The programs encourage organizations to fill security- and privacy-related positions with qualified personnel. Security and privacy workforce development and improvement programs are complementary to organizational security awareness and training programs and focus on developing and institutionalizing the core security and privacy capabilities of personnel needed to protect organizational operations, assets, and individuals.
","uuid":"91873113-8b2c-47d0-b733-c046f7b9f266","family":"Program Management","parameters":[],"subControls":"","tests":[{"testId":"PM-13[01]","uuid":"9589e18b-8a20-41d1-800e-8926d218021a","test":"Determine if a security workforce development and improvement program is established;A process for organization-wide security and privacy testing, training, and monitoring helps ensure that organizations provide oversight for testing, training, and monitoring activities and that those activities are coordinated. With the growing importance of continuous monitoring programs, the implementation of information security and privacy across the three levels of the risk management hierarchy and the widespread use of common controls, organizations coordinate and consolidate the testing and monitoring activities that are routinely conducted as part of ongoing assessments supporting a variety of controls. Security and privacy training activities, while focused on individual systems and specific roles, require coordination across all organizational elements. Testing, training, and monitoring plans and activities are informed by current threat and vulnerability assessments.
","uuid":"f9980f11-0e38-4c3e-9ffb-c72923f27ef0","family":"Program Management","parameters":[],"subControls":"","tests":[{"testId":"PM-14a.01[01]","uuid":"5ee48175-1bbe-447b-b1ec-c8db750ecb4d","test":"Determine if a process is implemented for ensuring that organizational plans for conducting security testing, training, and monitoring activities associated with organizational systems are developed;Ongoing contact with security and privacy groups and associations is important in an environment of rapidly changing technologies and threats. Groups and associations include special interest groups, professional associations, forums, news groups, users’ groups, and peer groups of security and privacy professionals in similar organizations. Organizations select security and privacy groups and associations based on mission and business functions. Organizations share threat, vulnerability, and incident information as well as contextual insights, compliance techniques, and privacy problems consistent with applicable laws, executive orders, directives, policies, regulations, standards, and guidelines.
","uuid":"824e9f08-0fa8-4a2d-9adb-68df56bed15a","family":"Program Management","parameters":[],"subControls":"","tests":[{"testId":"PM-15a.[01]","uuid":"540a9ec5-24a2-4e3d-897b-a8393a8ba2ca","test":"Determine if contact is established and institutionalized with selected groups and associations within the security community to facilitate ongoing security education and training for organizational personnel;Because of the constantly changing and increasing sophistication of adversaries, especially the advanced persistent threat (APT), it may be more likely that adversaries can successfully breach or compromise organizational systems. One of the best techniques to address this concern is for organizations to share threat information, including threat events (i.e., tactics, techniques, and procedures) that organizations have experienced, mitigations that organizations have found are effective against certain types of threats, and threat intelligence (i.e., indications and warnings about threats). Threat information sharing may be bilateral or multilateral. Bilateral threat sharing includes government-to-commercial and government-to-government cooperatives. Multilateral threat sharing includes organizations taking part in threat-sharing consortia. Threat information may require special agreements and protection, or it may be freely shared.
","uuid":"7ff81978-5865-43e2-8f6e-aa503913ed0d","family":"Program Management","parameters":[],"subControls":"","tests":[{"testId":"PM-16","uuid":"d0ecc8f2-75f5-4cd3-869c-d8db10876a1d","test":"Determine if a threat awareness program that includes a cross-organization information-sharing capability for threat intelligence is implemented.To maximize the effectiveness of monitoring, it is important to know what threat observables and indicators the sensors need to be searching for. By using well-established frameworks, services, and automated tools, organizations improve their ability to rapidly share and feed the relevant threat detection signatures into monitoring tools.
","uuid":"a46b6c3e-ae38-46c6-bfac-4eda2de2bc1f","family":"Program Management","parameters":[],"subControls":"","tests":[{"testId":"PM-16(01)","uuid":"48127bb9-d86a-4435-a09e-9f682cd8d4b0","test":"Determine if automated mechanisms are employed to maximize the effectiveness of sharing threat intelligence information.Controlled unclassified information is defined by the National Archives and Records Administration along with the safeguarding and dissemination requirements for such information and is codified in 32 CFR 2002 and, specifically for systems external to the federal organization, 32 CFR 2002.14h . The policy prescribes the specific use and conditions to be implemented in accordance with organizational procedures, including via its contracting processes.
","uuid":"0be34fec-1463-4485-ae23-d2e980730f94","family":"Program Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"509abd04-b4d3-4806-9132-5042914c45ba","text":"organization-defined frequency","parameterId":"pm-17_prm_1","default":" [Assignment: organization-defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"c3822509-d304-4592-b85e-9d177345f18b","text":"frequency","parameterId":"pm-17_odp.01","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"d9dc6527-e06e-4c10-aac0-df5dc8f8f885","text":"frequency","parameterId":"pm-17_odp.02","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"PM-17a.[01]","uuid":"94f3c076-653c-4a97-9a5c-be888aad0ce1","test":"Determine if policy is established 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;A privacy program plan is a formal document that provides an overview of an organization’s privacy program, including a description of the structure of the privacy program, the resources dedicated to the privacy program, the role of the senior agency official for privacy and other privacy officials and staff, the strategic goals and objectives of the privacy program, and the program management controls and common controls in place or planned for meeting applicable privacy requirements and managing privacy risks. Privacy program plans can be represented in single documents or compilations of documents.
The senior agency official for privacy is responsible for designating which privacy controls the organization will treat as program management, common, system-specific, and hybrid controls. Privacy program plans provide sufficient information about the privacy program management and common controls (including the specification of parameters and assignment and selection operations explicitly or by reference) to enable control implementations that are unambiguously compliant with the intent of the plans and a determination of the risk incurred if the plans are implemented as intended.
Program management controls are generally implemented at the organization level and are essential for managing the organization’s privacy program. Program management controls are distinct from common, system-specific, and hybrid controls because program management controls are independent of any particular information system. Together, the privacy plans for individual systems and the organization-wide privacy program plan provide complete coverage for the privacy controls employed within the organization.
Common controls are documented in an appendix to the organization’s privacy program plan unless the controls are included in a separate privacy plan for a system. The organization-wide privacy program plan indicates which separate privacy plans contain descriptions of privacy controls.
","uuid":"96b88451-385f-4c79-b208-8bc3bcdf887b","family":"Program Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"742034ff-7325-4802-98bf-efa19f520147","text":"frequency","parameterId":"pm-18_odp","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"PM-18a.[01]","uuid":"49a5ad89-2e07-4696-968a-4c1264065d01","test":"Determine if an organization-wide privacy program plan that provides an overview of the agency’s privacy program is developed;The privacy officer is an organizational official. For federal agencies—as defined by applicable laws, executive orders, directives, regulations, policies, standards, and guidelines—this official is designated as the senior agency official for privacy. Organizations may also refer to this official as the chief privacy officer. The senior agency official for privacy also has roles on the data management board (see PM-23 ) and the data integrity board (see PM-24).
","uuid":"ec840e29-0acd-4b0e-ba33-bd059e69ce84","family":"Program Management","parameters":[],"subControls":"","tests":[{"testId":"PM-19[01]","uuid":"870b78fa-e53e-4b1f-b942-6e796f07d075","test":"Determine if a senior agency official for privacy with authority, mission, accountability, and resources is appointed;For federal agencies, the webpage is located at www.[agency].gov/privacy. Federal agencies include public privacy impact assessments, system of records notices, computer matching notices and agreements, PRIVACT exemption and implementation rules, privacy reports, privacy policies, instructions for individuals making an access or amendment request, email addresses for questions/complaints, blogs, and periodic publications.
","uuid":"6294342d-3993-43d3-9258-2cdb9e4667b8","family":"Program Management","parameters":[],"subControls":"","tests":[{"testId":"PM-20[01]","uuid":"a825050b-fa0b-470b-b00c-af62a848dc3b","test":"Determine if a central resource webpage is maintained on the organization’s principal public website;Organizations post privacy policies on all external-facing websites, mobile applications, and other digital services. Organizations post a link to the relevant privacy policy on any known, major entry points to the website, application, or digital service. In addition, organizations provide a link to the privacy policy on any webpage that collects personally identifiable information. Organizations may be subject to applicable laws, executive orders, directives, regulations, or policies that require the provision of specific information to the public. Organizational personnel consult with the senior agency official for privacy and legal counsel regarding such requirements.
","uuid":"67713367-04df-4da0-9f38-04d52b4542dc","family":"Program Management","parameters":[],"subControls":"","tests":[{"testId":"PM-20(01)[01]","uuid":"91939c1d-e3a8-4c33-a545-92e57e279b7b","test":"Determine if privacy policies are developed and posted on all external-facing websites;The purpose of accounting of disclosures is to allow individuals to learn to whom their personally identifiable information has been disclosed, to provide a basis for subsequently advising recipients of any corrected or disputed personally identifiable information, and to provide an audit trail for subsequent reviews of organizational compliance with conditions for disclosures. For federal agencies, keeping an accounting of disclosures is required by the PRIVACT ; agencies should consult with their senior agency official for privacy and legal counsel on this requirement and be aware of the statutory exceptions and OMB guidance relating to the provision.
Organizations can use any system for keeping notations of disclosures, if it can construct from such a system, a document listing of all disclosures along with the required information. Automated mechanisms can be used by organizations to determine when personally identifiable information is disclosed, including commercial services that provide notifications and alerts. Accounting of disclosures may also be used to help organizations verify compliance with applicable privacy statutes and policies governing the disclosure or dissemination of information and dissemination restrictions.
","uuid":"2d5395e9-e54f-49b1-994c-59f4173d644e","family":"Program Management","parameters":[],"subControls":"","tests":[{"testId":"PM-21a.","uuid":"68abf8a4-6ea5-4374-b815-f635eeec3317","test":"Determine if an accurate accounting of disclosures of personally identifiable information is developed and maintained;Personally identifiable information quality management includes steps that organizations take to confirm the accuracy and relevance of personally identifiable information throughout the information life cycle. The information life cycle includes the creation, collection, use, processing, storage, maintenance, dissemination, disclosure, and disposition of personally identifiable information. Organizational policies and procedures for personally identifiable information quality management are important because inaccurate or outdated personally identifiable information maintained by organizations may cause problems for individuals. Organizations consider the quality of personally identifiable information involved in business functions where inaccurate information may result in adverse decisions or the denial of benefits and services, or the disclosure of the information may cause stigmatization. Correct information, in certain circumstances, can cause problems for individuals that outweigh the benefits of organizations maintaining the information. Organizations consider creating policies and procedures for the removal of such information.
The senior agency official for privacy ensures that practical means and mechanisms exist and are accessible for individuals or their authorized representatives to seek the correction or deletion of personally identifiable information. Processes for correcting or deleting data are clearly defined and publicly available. Organizations use discretion in determining whether data is to be deleted or corrected based on the scope of requests, the changes sought, and the impact of the changes. Additionally, processes include the provision of responses to individuals of decisions to deny requests for correction or deletion. The responses include the reasons for the decisions, a means to record individual objections to the decisions, and a means of requesting reviews of the initial determinations.
Organizations notify individuals or their designated representatives when their personally identifiable information is corrected or deleted to provide transparency and confirm the completed action. Due to the complexity of data flows and storage, other entities may need to be informed of the correction or deletion. Notice supports the consistent correction and deletion of personally identifiable information across the data ecosystem.
","uuid":"9317165a-6b9c-4449-a04d-2c34fa0504c1","family":"Program Management","parameters":[],"subControls":"","tests":[{"testId":"PM-22[01]","uuid":"49962757-3413-439e-9d63-82372631dc5f","test":"Determine if organization-wide policies for personally identifiable information quality management are developed and documented;A Data Governance Body can help ensure that the organization has coherent policies and the ability to balance the utility of data with security and privacy requirements. The Data Governance Body establishes policies, procedures, and standards that facilitate data governance so that data, including personally identifiable information, is effectively managed and maintained in accordance with applicable laws, executive orders, directives, regulations, policies, standards, and guidance. Responsibilities can include developing and implementing guidelines that support data modeling, quality, integrity, and the de-identification needs of personally identifiable information across the information life cycle as well as reviewing and approving applications to release data outside of the organization, archiving the applications and the released data, and performing post-release monitoring to ensure that the assumptions made as part of the data release continue to be valid. Members include the chief information officer, senior agency information security officer, and senior agency official for privacy. Federal agencies are required to establish a Data Governance Body with specific roles and responsibilities in accordance with the EVIDACT and policies set forth under OMB M-19-23.
","uuid":"ce357d1d-6da5-4ed3-9e20-cc166dc63f72","family":"Program Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"1957521f-c9d0-4288-ab8e-bf0ea6867470","text":"roles","parameterId":"pm-23_odp.01","default":" [Assignment: organization defined roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"c428b4be-530b-4e34-89a5-8622073c3746","text":"responsibilities","parameterId":"pm-23_odp.02","default":" [Assignment: organization defined responsibilities] "}],"subControls":"","tests":[{"testId":"PM-23","uuid":"2f0d0d97-a855-4d27-aaca-796c6462722f","test":"Determine if a data governance body consisting of [SELECTED PARAMETER VALUE(S): roles ] with [SELECTED PARAMETER VALUE(S): responsibilities ] is established.A Data Integrity Board is the board of senior officials designated by the head of a federal agency and is responsible for, among other things, reviewing the agency’s proposals to conduct or participate in a matching program and conducting an annual review of all matching programs in which the agency has participated. As a general matter, a matching program is a computerized comparison of records from two or more automated PRIVACT systems of records or an automated system of records and automated records maintained by a non-federal agency (or agent thereof). A matching program either pertains to Federal benefit programs or Federal personnel or payroll records. At a minimum, the Data Integrity Board includes the Inspector General of the agency, if any, and the senior agency official for privacy.
","uuid":"22719ee2-2774-4fbe-b3ad-565421ea3d1c","family":"Program Management","parameters":[],"subControls":"","tests":[{"testId":"PM-24a.","uuid":"78029316-cdd2-4930-8dac-bdd1971a9384","test":"Determine if the data integrity board reviews proposals to conduct or participate in a matching program;The use of personally identifiable information in testing, research, and training increases the risk of unauthorized disclosure or misuse of such information. Organizations consult with the senior agency official for privacy and/or legal counsel to ensure that the use of personally identifiable information in testing, training, and research is compatible with the original purpose for which it was collected. When possible, organizations use placeholder data to avoid exposure of personally identifiable information when conducting testing, training, and research.
","uuid":"262af9d5-d84e-413d-ba86-8077cd0b331a","family":"Program Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"189c6886-ab3f-4162-b2da-ac1a48b77ae5","text":"organization-defined frequency","parameterId":"pm-25_prm_1","default":" [Assignment: organization-defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"c1977fad-df19-457c-8bb4-e69c63e0e3b3","text":"frequency","parameterId":"pm-25_odp.01","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"efecb4fb-28a6-4b87-9855-e95e793d0864","text":"frequency","parameterId":"pm-25_odp.02","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"5a467587-4abf-4d29-b2e3-a985c9b46b35","text":"frequency","parameterId":"pm-25_odp.03","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"921b2d3e-7553-48ae-ac0c-2a7d75261a8d","text":"frequency","parameterId":"pm-25_odp.04","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"PM-25a.[01]","uuid":"ac244947-d15f-4cb2-ae6a-408799fe0e9d","test":"Determine if policies that address the use of personally identifiable information for internal testing are developed and documented;Complaints, concerns, and questions from individuals can serve as valuable sources of input to organizations and ultimately improve operational models, uses of technology, data collection practices, and controls. Mechanisms that can be used by the public include telephone hotline, email, or web-based forms. The information necessary for successfully filing complaints includes contact information for the senior agency official for privacy or other official designated to receive complaints. Privacy complaints may also include personally identifiable information which is handled in accordance with relevant policies and processes.
","uuid":"60f60219-63a3-4252-94f9-2a28fcfa2b46","family":"Program Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"9e7cac63-6e8b-4de4-98c0-5a30dc67514d","text":"organization-defined time period","parameterId":"pm-26_prm_1","default":" [Assignment: organization-defined time period] "},{"constraints":"","displayName":"","guidance":"","uuid":"e310608a-f693-42b5-874d-e780796a37f6","text":"time period","parameterId":"pm-26_odp.01","default":" [Assignment: organization defined time period] "},{"constraints":"","displayName":"","guidance":"","uuid":"9af34c53-6b5a-4338-a082-c466e86be8d9","text":"time period","parameterId":"pm-26_odp.02","default":" [Assignment: organization defined time period] "},{"constraints":"","displayName":"","guidance":"","uuid":"0aff223c-f737-4656-8b52-1c41360ec80e","text":"time period","parameterId":"pm-26_odp.03","default":" [Assignment: organization defined time period] "},{"constraints":"","displayName":"","guidance":"","uuid":"13c73f39-281a-45a2-843a-e76f9f173390","text":"time period","parameterId":"pm-26_odp.04","default":" [Assignment: organization defined time period] "}],"subControls":"","tests":[{"testId":"PM-26[01]","uuid":"6c11fab3-1987-40be-b2fb-2fff28943dbb","test":"Determine if a process for receiving complaints, concerns, or questions from individuals about organizational security and privacy practices is implemented;Through internal and external reporting, organizations promote accountability and transparency in organizational privacy operations. Reporting can also help organizations to determine progress in meeting privacy compliance requirements and privacy controls, compare performance across the federal government, discover vulnerabilities, identify gaps in policy and implementation, and identify models for success. For federal agencies, privacy reports include annual senior agency official for privacy reports to OMB, reports to Congress required by Implementing Regulations of the 9/11 Commission Act, and other public reports required by law, regulation, or policy, including internal policies of organizations. The senior agency official for privacy consults with legal counsel, where appropriate, to ensure that organizations meet all applicable privacy reporting requirements.
","uuid":"9c9d41bc-1430-4c78-9800-870db78ee5ca","family":"Program Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"262c5594-26a2-4f11-a165-4805d9a1cc48","text":"privacy reports","parameterId":"pm-27_odp.01","default":" [Assignment: organization defined privacy reports] "},{"constraints":"","displayName":"","guidance":"","uuid":"9145bc19-b3d8-426a-8442-bccd46d2d538","text":"oversight bodies","parameterId":"pm-27_odp.02","default":" [Assignment: organization defined oversight bodies] "},{"constraints":"","displayName":"","guidance":"","uuid":"977b901b-74e0-488f-b3b9-ebd08963ff5a","text":"officials","parameterId":"pm-27_odp.03","default":" [Assignment: organization defined officials] "},{"constraints":"","displayName":"","guidance":"","uuid":"60ca597f-9ffb-465e-811c-8f002bb37196","text":"frequency","parameterId":"pm-27_odp.04","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"PM-27a.","uuid":"802260cc-c8fa-4f88-b3c5-8c73897e17ef","test":"Determine if [SELECTED PARAMETER VALUE(S): privacy reports ] are developed;Risk framing is most effective when conducted at the organization level and in consultation with stakeholders throughout the organization including mission, business, and system owners. The assumptions, constraints, risk tolerance, priorities, and trade-offs identified as part of the risk framing process inform the risk management strategy, which in turn informs the conduct of risk assessment, risk response, and risk monitoring activities. Risk framing results are shared with organizational personnel, including mission and business owners, information owners or stewards, system owners, authorizing officials, senior agency information security officer, senior agency official for privacy, and senior accountable official for risk management.
","uuid":"bf47ac2f-c3a4-417a-935d-7f8f3123647f","family":"Program Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"9c63c02e-310b-4a29-9b77-cc4e93bb1775","text":"personnel","parameterId":"pm-28_odp.01","default":" [Assignment: organization defined personnel] "},{"constraints":"","displayName":"","guidance":"","uuid":"93af07a1-c10e-432e-91ff-0071499f0738","text":"frequency","parameterId":"pm-28_odp.02","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"PM-28a.01[01]","uuid":"492fc0de-8fc6-4655-8cc5-d2ccb0a9b790","test":"Determine if assumptions affecting risk assessments are identified and documented;The senior accountable official for risk management leads the risk executive (function) in organization-wide risk management activities.
","uuid":"5a9e77db-0546-4dbb-897d-352ab1f7fc50","family":"Program Management","parameters":[],"subControls":"","tests":[{"testId":"PM-29a.[01]","uuid":"05f53bc1-bf51-4d2b-ba34-3cdcb186f0db","test":"Determine if a senior accountable official for risk management is appointed;An organization-wide supply chain risk management strategy includes an unambiguous expression of the supply chain risk appetite and tolerance for the organization, acceptable supply chain risk mitigation strategies or controls, a process for consistently evaluating and monitoring supply chain risk, approaches for implementing and communicating the supply chain risk management strategy, and the associated roles and responsibilities. Supply chain risk management includes considerations of the security and privacy risks associated with the development, acquisition, maintenance, and disposal of systems, system components, and system services. The supply chain risk management strategy can be incorporated into the organization’s overarching risk management strategy and can guide and inform supply chain policies and system-level supply chain risk management plans. In addition, the use of a risk executive function can facilitate a consistent, organization-wide application of the supply chain risk management strategy. The supply chain risk management strategy is implemented at the organization and mission/business levels, whereas the supply chain risk management plan (see SR-2 ) is implemented at the system level.
","uuid":"f13cd0a9-d814-430e-a9d8-16c213234d19","family":"Program Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"5645b411-2c56-4ead-b76a-93c957e6bf35","text":"frequency","parameterId":"pm-30_odp","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"PM-30a.[01]","uuid":"bd7b12f7-1d36-447f-8abe-ad316bd2b0a6","test":"Determine if an organization-wide strategy for managing supply chain risks is developed;The identification and prioritization of suppliers of critical or mission-essential technologies, products, and services is paramount to the mission/business success of organizations. The assessment of suppliers is conducted using supplier reviews (see SR-6 ) and supply chain risk assessment processes (see RA-3(1) ). An analysis of supply chain risk can help an organization identify systems or components for which additional supply chain risk mitigations are required.
","uuid":"e96bf3b2-37e2-41d2-a926-a3d682725433","family":"Program Management","parameters":[],"subControls":"","tests":[{"testId":"PM-30(01)[01]","uuid":"9c0885d4-129e-409a-9c56-20a574cb4d1e","test":"Determine if suppliers of critical or mission-essential technologies, products, and services are identified;Continuous monitoring at the organization level facilitates ongoing awareness of the security and privacy posture across the organization to support organizational risk management decisions. The terms continuous
and ongoing
imply that organizations assess and monitor their controls and risks at a frequency sufficient to support risk-based decisions. Different types of controls may require different monitoring frequencies. The results of continuous monitoring guide and inform risk response actions by organizations. Continuous monitoring programs allow organizations to maintain the authorizations of systems and common controls in highly dynamic environments of operation with changing mission and business needs, threats, vulnerabilities, and technologies. Having access to security- and privacy-related information on a continuing basis through reports and dashboards gives organizational officials the capability to make effective, timely, and informed risk management decisions, including ongoing authorization decisions. To further facilitate security and privacy risk management, organizations consider aligning organization-defined monitoring metrics with organizational risk tolerance as defined in the risk management strategy. Monitoring requirements, including the need for monitoring, may be referenced in other controls and control enhancements such as, AC-2g, AC-2(7), AC-2(12)(a), AC-2(7)(b), AC-2(7)(c), AC-17(1), AT-4a, AU-13, AU-13(1), AU-13(2), CA-7, CM-3f, CM-6d, CM-11c, IR-5, MA-2b, MA-3a, MA-4a, PE-3d, PE-6, PE-14b, PE-16, PE-20, PM-6, PM-23, PS-7e, SA-9c, SC-5(3)(b), SC-7a, SC-7(24)(b), SC-18b, SC-43b, SI-4.
Systems are designed to support a specific mission or business function. However, over time, systems and system components may be used to support services and functions that are outside of the scope of the intended mission or business functions. This can result in exposing information resources to unintended environments and uses that can significantly increase threat exposure. In doing so, the systems are more vulnerable to compromise, which can ultimately impact the services and functions for which they were intended. This is especially impactful for mission-essential services and functions. By analyzing resource use, organizations can identify such potential exposures.
","uuid":"00ad07a4-7388-43b7-bf2f-433186e8644b","family":"Program Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"0317010f-ca4f-4ec8-b23f-6df33e003803","text":"systems or system components","parameterId":"pm-32_odp","default":" [Assignment: organization defined systems or system components] "}],"subControls":"","tests":[{"testId":"PM-32","uuid":"ce02e970-6b42-4457-90e7-a3a2508e1fb2","test":"Determine if [SELECTED PARAMETER VALUE(S): systems or system components ] supporting mission-essential services or functions are analyzed to ensure that the information resources are being used in a manner that is consistent with their intended purpose.Personnel security policy and procedures for the controls in the PS family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on their development. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission level or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies reflecting the complex nature of organizations. Procedures can be established for security and privacy programs, for mission/business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to personnel security policy and procedures include, but are not limited to, assessment or audit findings, security incidents or breaches, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure.
","uuid":"dc5f7f79-3ac6-44b9-aea2-3f8e8b97cb1c","family":"Personnel Security","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"fa000895-276d-4b11-ad66-9721dafef4f3","text":"organization-defined personnel or roles","parameterId":"ps-1_prm_1","default":" [Assignment: organization-defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"79d64284-8694-4e49-8399-e2f5f4830206","text":"personnel or roles","parameterId":"ps-01_odp.01","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"ae185e86-d007-423e-9e4b-dbc87f245909","text":"personnel or roles","parameterId":"ps-01_odp.02","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"ee8a6b6e-7272-4895-90ae-6b14b07d8f12","text":"[Selection (one or more): organization-level; mission/business process-level; system-level]","parameterId":"ps-01_odp.03","default":"[Selection (one or more): organization-level; mission/business process-level; system-level]"},{"constraints":"","displayName":"","guidance":"","uuid":"a6a6e419-6342-4835-baf1-8c60635f6df8","text":"official","parameterId":"ps-01_odp.04","default":" [Assignment: organization defined official] "},{"constraints":"","displayName":"","guidance":"","uuid":"b187b5f2-aee6-4fa9-b721-81dc08bb0f37","text":"frequency","parameterId":"ps-01_odp.05","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"f21aee7b-31cf-49f8-9c01-c22b42977409","text":"events","parameterId":"ps-01_odp.06","default":" [Assignment: organization defined events] "},{"constraints":"","displayName":"","guidance":"","uuid":"c8e4d7a1-e9cc-42d8-acb4-6786a42c11bc","text":"frequency","parameterId":"ps-01_odp.07","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"c620e1a3-5add-4830-9a38-0f1e328103d2","text":"events","parameterId":"ps-01_odp.08","default":" [Assignment: organization defined events] "}],"subControls":"","tests":[{"testId":"PS-01a.[01]","uuid":"059da387-cf6d-4f26-95cc-b64784c62de0","test":"Determine if a personnel security policy is developed and documented;Position risk designations reflect Office of Personnel Management (OPM) policy and guidance. Proper position designation is the foundation of an effective and consistent suitability and personnel security program. The Position Designation System (PDS) assesses the duties and responsibilities of a position to determine the degree of potential damage to the efficiency or integrity of the service due to misconduct of an incumbent of a position and establishes the risk level of that position. The PDS assessment also determines if the duties and responsibilities of the position present the potential for position incumbents to bring about a material adverse effect on national security and the degree of that potential effect, which establishes the sensitivity level of a position. The results of the assessment determine what level of investigation is conducted for a position. Risk designations can guide and inform the types of authorizations that individuals receive when accessing organizational information and information systems. Position screening criteria include explicit information security role appointment requirements. Parts 1400 and 731 of Title 5, Code of Federal Regulations, establish the requirements for organizations to evaluate relevant covered positions for a position sensitivity and position risk designation commensurate with the duties and responsibilities of those positions.
","uuid":"3b1e58c4-d58c-4eda-8d29-500d14e4f867","family":"Personnel Security","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"10b9901c-ae98-4daf-b67c-20a09907de30","text":"frequency","parameterId":"ps-02_odp","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"PS-02a.","uuid":"5a6d4aa4-e827-4045-b46f-cfbbfeb0d308","test":"Determine if a risk designation is assigned to all organizational positions;Personnel screening and rescreening activities reflect applicable laws, executive orders, directives, regulations, policies, standards, guidelines, and specific criteria established for the risk designations of assigned positions. Examples of personnel screening include background investigations and agency checks. Organizations may define different rescreening conditions and frequencies for personnel accessing systems based on types of information processed, stored, or transmitted by the systems.
","uuid":"9b1b73b9-88c3-4d8d-b450-628903dbe6cd","family":"Personnel Security","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"ac69baec-6c74-4e6f-b672-86dbf4a4e428","text":"organization-defined conditions requiring rescreening and, where rescreening is so indicated, the frequency of rescreening","parameterId":"ps-3_prm_1","default":" [Assignment: organization-defined conditions requiring rescreening and, where rescreening is so indicated, the frequency of rescreening] "},{"constraints":"","displayName":"","guidance":"","uuid":"9c896734-91c6-46dd-b7a2-17e20cede590","text":"conditions requiring rescreening","parameterId":"ps-03_odp.01","default":" [Assignment: organization defined conditions requiring rescreening] "},{"constraints":"","displayName":"","guidance":"","uuid":"82b441fa-dabf-4779-81bd-1cba0cd92faf","text":"frequency","parameterId":"ps-03_odp.02","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"PS-03a.","uuid":"ff7772a8-42c6-467a-bd2d-fdb1a738cb4c","test":"Determine if individuals are screened prior to authorizing access to the system;Classified information is the most sensitive information that the Federal Government processes, stores, or transmits. It is imperative that individuals have the requisite security clearances and system access authorizations prior to gaining access to such information. Access authorizations are enforced by system access controls (see AC-3 ) and flow controls (see AC-4).
","uuid":"fa098e5c-b094-47cd-8ec4-2b5a4f446d76","family":"Personnel Security","parameters":[],"subControls":"","tests":[{"testId":"PS-03(01)[01]","uuid":"f63906b9-cfed-4dce-b8ed-6cab8daf7ade","test":"Determine if individuals accessing a system processing, storing, or transmitting classified information are cleared;Types of classified information that require formal indoctrination include Special Access Program (SAP), Restricted Data (RD), and Sensitive Compartmented Information (SCI).
","uuid":"61768a9a-0e3f-410f-9280-6c70546c34a1","family":"Personnel Security","parameters":[],"subControls":"","tests":[{"testId":"PS-03(02)","uuid":"6627d2fa-6cf2-45d0-82bb-fc924ec83f02","test":"Determine if individuals accessing a system processing, storing, or transmitting types of classified information that require formal indoctrination are formally indoctrinated for all of the relevant types of information to which they have access on the system.Organizational information that requires special protection includes controlled unclassified information. Personnel security criteria include position sensitivity background screening requirements.
","uuid":"ea1977f9-d38b-497b-bfb5-fe554ee74d55","family":"Personnel Security","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"377dad32-c940-464a-8a8b-09b992acbde7","text":"additional personnel screening criteria","parameterId":"ps-03.03_odp","default":" [Assignment: organization defined additional personnel screening criteria] "}],"subControls":"","tests":[{"testId":"PS-03(03)(a)","uuid":"87bc7b84-3514-49a7-97b7-bb07e8d4c1f5","test":"Determine if individuals accessing a system processing, storing, or transmitting information requiring special protection have valid access authorizations that are demonstrated by assigned official government duties;None.
","uuid":"4ee43127-8ba7-4f33-b792-44239ff92e0b","family":"Personnel Security","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"f38ecf53-3455-4cbb-80af-e5e2988638a4","text":"information types","parameterId":"ps-03.04_odp.01","default":" [Assignment: organization defined information types] "},{"constraints":"","displayName":"","guidance":"","uuid":"4f0cf938-acd7-44c5-a27a-4f9520759b1a","text":"citizenship requirements","parameterId":"ps-03.04_odp.02","default":" [Assignment: organization defined citizenship requirements] "}],"subControls":"","tests":[{"testId":"PS-03(04)","uuid":"5737eafb-bf24-46a9-a769-eba1067f677b","test":"Determine if individuals accessing a system processing, storing, or transmitting [SELECTED PARAMETER VALUE(S): information types ] meet [SELECTED PARAMETER VALUE(S): citizenship requirements ].System property includes hardware authentication tokens, system administration technical manuals, keys, identification cards, and building passes. Exit interviews ensure that terminated individuals understand the security constraints imposed by being former employees and that proper accountability is achieved for system-related property. Security topics at exit interviews include reminding individuals of nondisclosure agreements and potential limitations on future employment. Exit interviews may not always be possible for some individuals, including in cases related to the unavailability of supervisors, illnesses, or job abandonment. Exit interviews are important for individuals with security clearances. The timely execution of termination actions is essential for individuals who have been terminated for cause. In certain situations, organizations consider disabling the system accounts of individuals who are being terminated prior to the individuals being notified.
","uuid":"97315a76-c0f3-4874-bfab-e098e2d02137","family":"Personnel Security","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"7ff39a36-8922-45c5-9b2a-c707a0777abd","text":"time period","parameterId":"ps-04_odp.01","default":" [Assignment: organization defined time period] "},{"constraints":"","displayName":"","guidance":"","uuid":"6a9f9507-2f94-431e-93aa-801bce146edf","text":"information security topics","parameterId":"ps-04_odp.02","default":" [Assignment: organization defined information security topics] "}],"subControls":"","tests":[{"testId":"PS-04a.","uuid":"7a107285-198f-4689-9700-56543189b4a5","test":"Determine if upon termination of individual employment, system access is disabled within [SELECTED PARAMETER VALUE(S): time period ];Organizations consult with the Office of the General Counsel regarding matters of post-employment requirements on terminated individuals.
","uuid":"682420cd-6c66-42d6-9c28-2c2b5833227f","family":"Personnel Security","parameters":[],"subControls":"","tests":[{"testId":"PS-04(01)(a)","uuid":"3dfc3f06-eb4f-4a21-9d28-ed69145bcf2b","test":"Determine if terminated individuals are notified of applicable, legally binding post-employment requirements for the protection of organizational information;In organizations with many employees, not all personnel who need to know about termination actions receive the appropriate notifications, or if such notifications are received, they may not occur in a timely manner. Automated mechanisms can be used to send automatic alerts or notifications to organizational personnel or roles when individuals are terminated. Such automatic alerts or notifications can be conveyed in a variety of ways, including via telephone, electronic mail, text message, or websites. Automated mechanisms can also be employed to quickly and thoroughly disable access to system resources after an employee is terminated.
","uuid":"33168ea5-567b-4dbc-9260-c7b6e85074b5","family":"Personnel Security","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"9ecc3f94-fa9b-42b7-abdf-89e0e335d337","text":"automated mechanisms","parameterId":"ps-04.02_odp.01","default":" [Assignment: organization defined automated mechanisms] "},{"constraints":"","displayName":"","guidance":"","uuid":"499c6c39-8a10-45f2-b46f-a5c277211854","text":"[Selection (one or more): notify [(NESTED PARAMETER) Assignment for ps-04.02_odp.03: personnel or roles] of individual termination actions; disable access to system resources]","parameterId":"ps-04.02_odp.02","default":"[Selection (one or more): notify [(NESTED PARAMETER) Assignment for ps-04.02_odp.03: personnel or roles] of individual termination actions; disable access to system resources]"},{"constraints":"","displayName":"","guidance":"","uuid":"62e1c2e0-72bf-4dd0-a4a2-908998a74dfa","text":"personnel or roles","parameterId":"ps-04.02_odp.03","default":" [Assignment: organization defined personnel or roles] "}],"subControls":"","tests":[{"testId":"PS-04(02)","uuid":"1f2e0657-a0eb-49d0-8fe7-6265f0f63cbe","test":"Determine if [SELECTED PARAMETER VALUE(S): automated mechanisms ] are used to [SELECTED PARAMETER VALUE(S): [Selection (one or more): notify [(NESTED PARAMETER) Assignment for ps-04.02_odp.03: personnel or roles] of individual termination actions; disable access to system resources] ].Personnel transfer applies when reassignments or transfers of individuals are permanent or of such extended duration as to make the actions warranted. Organizations define actions appropriate for the types of reassignments or transfers, whether permanent or extended. Actions that may be required for personnel transfers or reassignments to other positions within organizations include returning old and issuing new keys, identification cards, and building passes; closing system accounts and establishing new accounts; changing system access authorizations (i.e., privileges); and providing for access to official records to which individuals had access at previous work locations and in previous system accounts.
","uuid":"55ca8ff9-a057-427e-b82d-c525a1d64b5e","family":"Personnel Security","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"e4fad8cf-ec9c-4387-8fe5-1e3847406dbe","text":"transfer or reassignment actions","parameterId":"ps-05_odp.01","default":" [Assignment: organization defined transfer or reassignment actions] "},{"constraints":"","displayName":"","guidance":"","uuid":"db766c3d-04c1-4855-8350-510f75e0dd04","text":"time period following the formal transfer action","parameterId":"ps-05_odp.02","default":" [Assignment: organization defined time period following the formal transfer action] "},{"constraints":"","displayName":"","guidance":"","uuid":"75b0d0f4-c3d6-45b4-ace9-dd6b79f45b68","text":"personnel or roles","parameterId":"ps-05_odp.03","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"2fc6c171-f726-4307-8dd1-e8895ec91d58","text":"time period","parameterId":"ps-05_odp.04","default":" [Assignment: organization defined time period] "}],"subControls":"","tests":[{"testId":"PS-05a.","uuid":"2424f708-c089-46fd-849e-d5a9f9ef0b2e","test":"Determine if the ongoing operational need for current logical and physical access authorizations to systems and facilities are reviewed and confirmed when individuals are reassigned or transferred to other positions within the organization;Access agreements include nondisclosure agreements, acceptable use agreements, rules of behavior, and conflict-of-interest agreements. Signed access agreements include an acknowledgement that individuals have read, understand, and agree to abide by the constraints associated with organizational systems to which access is authorized. Organizations can use electronic signatures to acknowledge access agreements unless specifically prohibited by organizational policy.
","uuid":"9e8c1729-9e70-4a62-beef-b14f4afa6115","family":"Personnel Security","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"1a332176-a34f-4ac5-9be4-ac0031456423","text":"frequency","parameterId":"ps-06_odp.01","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"121342c6-2420-4ff9-85bc-32ea84d62ea0","text":"frequency","parameterId":"ps-06_odp.02","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"PS-06a.","uuid":"106cce6a-85fc-4582-b3a6-2f07ae96ed86","test":"Determine if access agreements are developed and documented for organizational systems;Classified information that requires special protection includes collateral information, Special Access Program (SAP) information, and Sensitive Compartmented Information (SCI). Personnel security criteria reflect applicable laws, executive orders, directives, regulations, policies, standards, and guidelines.
","uuid":"d8362cee-d135-4ccd-bf25-510727b139de","family":"Personnel Security","parameters":[],"subControls":"","tests":[{"testId":"PS-06(02)(a)","uuid":"ca10d708-3dc8-4227-9783-54bf2141d1b0","test":"Determine if access to classified information requiring special protection is granted only to individuals who have a valid access authorization that is demonstrated by assigned official government duties;Organizations consult with the Office of the General Counsel regarding matters of post-employment requirements on terminated individuals.
","uuid":"42866a5c-2066-4389-8f0c-0192ea36e806","family":"Personnel Security","parameters":[],"subControls":"","tests":[{"testId":"PS-06(03)(a)","uuid":"3a80a951-30a3-46f2-944a-c778cfad5b4f","test":"Determine if individuals are notified of applicable, legally binding post-employment requirements for the protection of organizational information;External provider refers to organizations other than the organization operating or acquiring the system. External providers include service bureaus, contractors, and other organizations that provide system development, information technology services, testing or assessment services, outsourced applications, and network/security management. Organizations explicitly include personnel security requirements in acquisition-related documents. External providers may have personnel working at organizational facilities with credentials, badges, or system privileges issued by organizations. Notifications of external personnel changes ensure the appropriate termination of privileges and credentials. Organizations define the transfers and terminations deemed reportable by security-related characteristics that include functions, roles, and the nature of credentials or privileges associated with transferred or terminated individuals.
","uuid":"8c8834da-b1e0-46a5-a3c0-76fbed61fdff","family":"Personnel Security","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"dcd16eb8-e8f3-42ca-a0f4-71531f710b5e","text":"personnel or roles","parameterId":"ps-07_odp.01","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"0413b08e-998a-4b43-96e5-1c5767b8f586","text":"time period","parameterId":"ps-07_odp.02","default":" [Assignment: organization defined time period] "}],"subControls":"","tests":[{"testId":"PS-07a.","uuid":"adb447b0-ff79-40d2-b492-d639a731815e","test":"Determine if personnel security requirements are established, including security roles and responsibilities for external providers;Organizational sanctions reflect applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Sanctions processes are described in access agreements and can be included as part of general personnel policies for organizations and/or specified in security and privacy policies. Organizations consult with the Office of the General Counsel regarding matters of employee sanctions.
","uuid":"97fde01d-47cd-40a5-9726-9b00009a2406","family":"Personnel Security","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"8446d096-3b4e-4d37-ab99-0523f414ea11","text":"personnel or roles","parameterId":"ps-08_odp.01","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"c8509fcf-aa92-441f-8aa5-2a6117959da0","text":"time period","parameterId":"ps-08_odp.02","default":" [Assignment: organization defined time period] "}],"subControls":"","tests":[{"testId":"PS-08a.","uuid":"3adb1e5d-8de0-4adb-adee-db334a1f9fe7","test":"Determine if a formal sanctions process is employed for individuals failing to comply with established information security and privacy policies and procedures;Specification of security and privacy roles in individual organizational position descriptions facilitates clarity in understanding the security or privacy responsibilities associated with the roles and the role-based security and privacy training requirements for the roles.
","uuid":"8c24c99f-9fd9-4930-985a-28cb62bd6f88","family":"Personnel Security","parameters":[],"subControls":"","tests":[{"testId":"PS-09[01]","uuid":"a53f7d91-fb54-442a-bf63-07055f038858","test":"Determine if security roles and responsibilities are incorporated into organizational position descriptions;Personally identifiable information processing and transparency policy and procedures address the controls in the PT family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of personally identifiable information processing and transparency policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission or business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to personally identifiable information processing and transparency policy and procedures include assessment or audit findings, breaches, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure.
","uuid":"b3c1b3de-b434-431f-9c44-ee13315e1991","family":"Personally Identifiable Information Processing and Transparency","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"c7c16b94-6f44-44d7-beb8-c3e3882ac656","text":"organization-defined personnel or roles","parameterId":"pt-1_prm_1","default":" [Assignment: organization-defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"61843bd2-c6fd-43b7-b3df-1c9bb2491217","text":"personnel or roles","parameterId":"pt-01_odp.01","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"c16184c5-e2ef-4360-b7c2-f1c1a5d65f72","text":"personnel or roles","parameterId":"pt-01_odp.02","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"61c374ef-6082-401b-9fbd-f8015532e84e","text":"[Selection (one or more): organization-level; mission/business process-level; system-level]","parameterId":"pt-01_odp.03","default":"[Selection (one or more): organization-level; mission/business process-level; system-level]"},{"constraints":"","displayName":"","guidance":"","uuid":"bfa82fca-f8c8-446e-9554-047db5d60239","text":"official","parameterId":"pt-01_odp.04","default":" [Assignment: organization defined official] "},{"constraints":"","displayName":"","guidance":"","uuid":"f5116c92-e90a-45c9-83d7-59ecb930fcb6","text":"frequency","parameterId":"pt-01_odp.05","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"c46b3be4-bdc4-4b8a-bbd2-e0f56ad512ce","text":"events","parameterId":"pt-01_odp.06","default":" [Assignment: organization defined events] "},{"constraints":"","displayName":"","guidance":"","uuid":"d3e8fda6-0e89-4edf-bfd7-ae694fc188de","text":"frequency","parameterId":"pt-01_odp.07","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"9928585f-d7f6-4f30-bbd5-6e8426c9bf43","text":"events","parameterId":"pt-01_odp.08","default":" [Assignment: organization defined events] "}],"subControls":"","tests":[{"testId":"PT-01a.[01]","uuid":"8dd3c94b-abdf-4505-a962-70c9c62092f8","test":"Determine if a personally identifiable information processing and transparency policy is developed and documented;The processing of personally identifiable information is an operation or set of operations that the information system or organization performs with respect to personally identifiable information across the information life cycle. Processing includes but is not limited to creation, collection, use, processing, storage, maintenance, dissemination, disclosure, and disposal. Processing operations also include logging, generation, and transformation, as well as analysis techniques, such as data mining.
Organizations may be subject to laws, executive orders, directives, regulations, or policies that establish the organization’s authority and thereby limit certain types of processing of personally identifiable information or establish other requirements related to the processing. Organizational personnel consult with the senior agency official for privacy and legal counsel regarding such authority, particularly if the organization is subject to multiple jurisdictions or sources of authority. For organizations whose processing is not determined according to legal authorities, the organization’s policies and determinations govern how they process personally identifiable information. While processing of personally identifiable information may be legally permissible, privacy risks may still arise. Privacy risk assessments can identify the privacy risks associated with the authorized processing of personally identifiable information and support solutions to manage such risks.
Organizations consider applicable requirements and organizational policies to determine how to document this authority. For federal agencies, the authority to process personally identifiable information is documented in privacy policies and notices, system of records notices, privacy impact assessments, PRIVACT statements, computer matching agreements and notices, contracts, information sharing agreements, memoranda of understanding, and other documentation.
Organizations take steps to ensure that personally identifiable information is only processed for authorized purposes, including training organizational personnel on the authorized processing of personally identifiable information and monitoring and auditing organizational use of personally identifiable information.
","uuid":"99733f5b-05de-4a4e-a63c-33b6b45159de","family":"Personally Identifiable Information Processing and Transparency","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"dd65a2d0-555b-4189-998d-d4fc7721e47d","text":"authority","parameterId":"pt-02_odp.01","default":" [Assignment: organization defined authority] "},{"constraints":"","displayName":"","guidance":"","uuid":"99edae1c-9e2b-4cae-b2bb-cc80274cf721","text":"processing","parameterId":"pt-02_odp.02","default":" [Assignment: organization defined processing] "},{"constraints":"","displayName":"","guidance":"","uuid":"6f57a5f9-843c-4b96-bd2f-94dd4218f3c4","text":"processing","parameterId":"pt-02_odp.03","default":" [Assignment: organization defined processing] "}],"subControls":"","tests":[{"testId":"PT-02a.","uuid":"d80e830e-152b-45c4-b57c-f009385d4c48","test":"Determine if the [SELECTED PARAMETER VALUE(S): authority ] that permits the [SELECTED PARAMETER VALUE(S): processing ] of personally identifiable information is determined and documented;Data tags support the tracking and enforcement of authorized processing by conveying the types of processing that are authorized along with the relevant elements of personally identifiable information throughout the system. Data tags may also support the use of automated tools.
","uuid":"5d4c9271-a060-4b01-bdf4-48604bd267c9","family":"Personally Identifiable Information Processing and Transparency","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"24c33ff0-0617-43a1-8858-81b6921c2777","text":"authorized processing","parameterId":"pt-02.01_odp.01","default":" [Assignment: organization defined authorized processing] "},{"constraints":"","displayName":"","guidance":"","uuid":"d536a4f0-17de-4a0f-b823-3b2edc870781","text":"elements of personally identifiable information","parameterId":"pt-02.01_odp.02","default":" [Assignment: organization defined elements of personally identifiable information] "}],"subControls":"","tests":[{"testId":"PT-02(01)","uuid":"5efa4782-2613-4e35-938e-c84c32ff0832","test":"Determine if data tags containing [SELECTED PARAMETER VALUE(S): authorized processing ] are attached to [SELECTED PARAMETER VALUE(S): elements of personally identifiable information ].Automated mechanisms augment verification that only authorized processing is occurring.
","uuid":"f535beca-e31b-4615-ab03-6d94955dd5d7","family":"Personally Identifiable Information Processing and Transparency","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"8ca0929a-d001-4484-b9e2-887829eaa999","text":"automated mechanisms","parameterId":"pt-02.02_odp","default":" [Assignment: organization defined automated mechanisms] "}],"subControls":"","tests":[{"testId":"PT-02(02)","uuid":"191a27ac-6ff2-46d8-9b1a-d67851779e27","test":"Determine if enforcement of the authorized processing of personally identifiable information is managed using [SELECTED PARAMETER VALUE(S): automated mechanisms ].Identifying and documenting the purpose for processing provides organizations with a basis for understanding why personally identifiable information may be processed. The term process
includes every step of the information life cycle, including creation, collection, use, processing, storage, maintenance, dissemination, disclosure, and disposal. Identifying and documenting the purpose of processing is a prerequisite to enabling owners and operators of the system and individuals whose information is processed by the system to understand how the information will be processed. This enables individuals to make informed decisions about their engagement with information systems and organizations and to manage their privacy interests. Once the specific processing purpose has been identified, the purpose is described in the organization’s privacy notices, policies, and any related privacy compliance documentation, including privacy impact assessments, system of records notices, PRIVACT statements, computer matching notices, and other applicable Federal Register notices.
Organizations take steps to help ensure that personally identifiable information is processed only for identified purposes, including training organizational personnel and monitoring and auditing organizational processing of personally identifiable information.
Organizations monitor for changes in personally identifiable information processing. Organizational personnel consult with the senior agency official for privacy and legal counsel to ensure that any new purposes that arise from changes in processing are compatible with the purpose for which the information was collected, or if the new purpose is not compatible, implement mechanisms in accordance with defined requirements to allow for the new processing, if appropriate. Mechanisms may include obtaining consent from individuals, revising privacy policies, or other measures to manage privacy risks that arise from changes in personally identifiable information processing purposes.
","uuid":"825f1d6e-bc3b-45ad-a2ee-9d628491d120","family":"Personally Identifiable Information Processing and Transparency","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"a6487581-470c-4475-ac5b-abbad1905b4b","text":"purpose(s)","parameterId":"pt-03_odp.01","default":" [Assignment: organization defined purpose(s)] "},{"constraints":"","displayName":"","guidance":"","uuid":"4bf0b4db-90c0-4877-b466-0e7effeb812a","text":"processing","parameterId":"pt-03_odp.02","default":" [Assignment: organization defined processing] "},{"constraints":"","displayName":"","guidance":"","uuid":"5996718f-d897-4a87-9f28-5b3e705433fe","text":"mechanisms","parameterId":"pt-03_odp.03","default":" [Assignment: organization defined mechanisms] "},{"constraints":"","displayName":"","guidance":"","uuid":"43ba3cc8-f03e-4ef7-87b0-b263b3d148a1","text":"requirements","parameterId":"pt-03_odp.04","default":" [Assignment: organization defined requirements] "}],"subControls":"","tests":[{"testId":"PT-03a.","uuid":"a27ec32f-0a47-49a1-b6d1-170161cfbdab","test":"Determine if the [SELECTED PARAMETER VALUE(S): purpose(s) ] for processing personally identifiable information is/are identified and documented;Data tags support the tracking of processing purposes by conveying the purposes along with the relevant elements of personally identifiable information throughout the system. By conveying the processing purposes in a data tag along with the personally identifiable information as the information transits a system, a system owner or operator can identify whether a change in processing would be compatible with the identified and documented purposes. Data tags may also support the use of automated tools.
","uuid":"f7f0e47a-1d3b-4bcf-8c2f-b8f0da1c1480","family":"Personally Identifiable Information Processing and Transparency","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"1e52ce08-44c6-4f68-893e-15a0a95504d0","text":"processing purposes","parameterId":"pt-03.01_odp.01","default":" [Assignment: organization defined processing purposes] "},{"constraints":"","displayName":"","guidance":"","uuid":"baa1f7ab-e671-413d-b8c4-51ff6622c274","text":"elements of personally identifiable information","parameterId":"pt-03.01_odp.02","default":" [Assignment: organization defined elements of personally identifiable information] "}],"subControls":"","tests":[{"testId":"PT-03(01)","uuid":"1f76234b-b69c-4750-b701-45764161e1e7","test":"Determine if data tags containing [SELECTED PARAMETER VALUE(S): processing purposes ] are attached to [SELECTED PARAMETER VALUE(S): elements of personally identifiable information ].Automated mechanisms augment tracking of the processing purposes.
","uuid":"cc0b3384-baa1-4066-9de5-9d9c2b3a27b8","family":"Personally Identifiable Information Processing and Transparency","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"632fc2f5-d17c-4753-884e-dbbe89dd2a97","text":"automated mechanisms","parameterId":"pt-03.02_odp","default":" [Assignment: organization defined automated mechanisms] "}],"subControls":"","tests":[{"testId":"PT-03(02)","uuid":"0dfc9f4c-b696-4d2d-a057-0fb09cdb9072","test":"Determine if the processing purposes of personally identifiable information are tracked using [SELECTED PARAMETER VALUE(S): automated mechanisms ].Consent allows individuals to participate in making decisions about the processing of their information and transfers some of the risk that arises from the processing of personally identifiable information from the organization to an individual. Consent may be required by applicable laws, executive orders, directives, regulations, policies, standards, or guidelines. Otherwise, when selecting consent as a control, organizations consider whether individuals can be reasonably expected to understand and accept the privacy risks that arise from their authorization. Organizations consider whether other controls may more effectively mitigate privacy risk either alone or in conjunction with consent. Organizations also consider any demographic or contextual factors that may influence the understanding or behavior of individuals with respect to the processing carried out by the system or organization. When soliciting consent from individuals, organizations consider the appropriate mechanism for obtaining consent, including the type of consent (e.g., opt-in, opt-out), how to properly authenticate and identity proof individuals and how to obtain consent through electronic means. In addition, organizations consider providing a mechanism for individuals to revoke consent once it has been provided, as appropriate. Finally, organizations consider usability factors to help individuals understand the risks being accepted when providing consent, including the use of plain language and avoiding technical jargon.
","uuid":"98447add-94ed-4f07-9f55-9186613517ea","family":"Personally Identifiable Information Processing and Transparency","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"deedf2dc-100b-49e3-b08e-e06323133b00","text":"tools or mechanisms","parameterId":"pt-04_odp","default":" [Assignment: organization defined tools or mechanisms] "}],"subControls":"","tests":[{"testId":"PT-04","uuid":"8bfd3cf4-babf-482d-a780-87082f95927e","test":"Determine if the [SELECTED PARAMETER VALUE(S): tools or mechanisms ] are implemented for individuals to consent to the processing of their personally identifiable information prior to its collection that facilitate individuals’ informed decision-making.While some processing may be necessary for the basic functionality of the product or service, other processing may not. In these circumstances, organizations allow individuals to select how specific personally identifiable information elements may be processed. More tailored consent may help reduce privacy risk, increase individual satisfaction, and avoid adverse behaviors, such as abandonment of the product or service.
","uuid":"92f0ee0f-ec04-40ba-83a9-b01ee174d291","family":"Personally Identifiable Information Processing and Transparency","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"80203283-6ab9-45a9-bcca-2a6e16f0aa12","text":"mechanisms","parameterId":"pt-04.01_odp","default":" [Assignment: organization defined mechanisms] "}],"subControls":"","tests":[{"testId":"PT-04(01)","uuid":"131f624a-66a2-4a30-9797-352dbf4441e3","test":"Determine if [SELECTED PARAMETER VALUE(S): mechanisms ] are provided to allow individuals to tailor processing permissions to selected elements of personally identifiable information.Just-in-time consent enables individuals to participate in how their personally identifiable information is being processed at the time or in conjunction with specific types of data processing when such participation may be most useful to the individual. Individual assumptions about how personally identifiable information is being processed might not be accurate or reliable if time has passed since the individual last gave consent or the type of processing creates significant privacy risk. Organizations use discretion to determine when to use just-in-time consent and may use supporting information on demographics, focus groups, or surveys to learn more about individuals’ privacy interests and concerns.
","uuid":"3c4aed6e-ea2f-41c3-8d52-2164014644c7","family":"Personally Identifiable Information Processing and Transparency","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"27cd6184-a47b-4eef-ad13-2b77ff942d67","text":"consent mechanisms","parameterId":"pt-04.02_odp.01","default":" [Assignment: organization defined consent mechanisms] "},{"constraints":"","displayName":"","guidance":"","uuid":"b1297d74-1448-4edc-9f65-22c0f1436bc1","text":"frequency","parameterId":"pt-04.02_odp.02","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"f8ed890b-6313-4845-8843-e406219616ba","text":"personally identifiable information processing","parameterId":"pt-04.02_odp.03","default":" [Assignment: organization defined personally identifiable information processing] "}],"subControls":"","tests":[{"testId":"PT-04(02)","uuid":"57d47f98-d345-48c0-8915-3f038e87e0f3","test":"Determine if [SELECTED PARAMETER VALUE(S): consent mechanisms ] are presented to individuals [SELECTED PARAMETER VALUE(S): frequency ] and in conjunction with [SELECTED PARAMETER VALUE(S): personally identifiable information processing ].Revocation of consent enables individuals to exercise control over their initial consent decision when circumstances change. Organizations consider usability factors in enabling easy-to-use revocation capabilities.
","uuid":"6aca3114-9808-4809-bf67-e72543372063","family":"Personally Identifiable Information Processing and Transparency","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"6e8ce2d7-56aa-475a-b5a0-1120753f0782","text":"tools or mechanisms","parameterId":"pt-04.03_odp","default":" [Assignment: organization defined tools or mechanisms] "}],"subControls":"","tests":[{"testId":"PT-04(03)","uuid":"3a03d9f1-0535-4409-a525-a414e87f040b","test":"Determine if the [SELECTED PARAMETER VALUE(S): tools or mechanisms ] are implemented for individuals to revoke consent to the processing of their personally identifiable information.Privacy notices help inform individuals about how their personally identifiable information is being processed by the system or organization. Organizations use privacy notices to inform individuals about how, under what authority, and for what purpose their personally identifiable information is processed, as well as other information such as choices individuals might have with respect to that processing and other parties with whom information is shared. Laws, executive orders, directives, regulations, or policies may require that privacy notices include specific elements or be provided in specific formats. Federal agency personnel consult with the senior agency official for privacy and legal counsel regarding when and where to provide privacy notices, as well as elements to include in privacy notices and required formats. In circumstances where laws or government-wide policies do not require privacy notices, organizational policies and determinations may require privacy notices and may serve as a source of the elements to include in privacy notices.
Privacy risk assessments identify the privacy risks associated with the processing of personally identifiable information and may help organizations determine appropriate elements to include in a privacy notice to manage such risks. To help individuals understand how their information is being processed, organizations write materials in plain language and avoid technical jargon.
","uuid":"98ec0ae7-6a63-4f44-80eb-14ecbf44a28b","family":"Personally Identifiable Information Processing and Transparency","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"91e87b18-ebf5-4328-a96e-ba5c56dda904","text":"frequency","parameterId":"pt-05_odp.01","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"8e739043-0ea4-430c-83dd-8cd667a44e80","text":"information","parameterId":"pt-05_odp.02","default":" [Assignment: organization defined information] "}],"subControls":"","tests":[{"testId":"PT-05a.[01]","uuid":"8f13b48d-9f34-40e1-9011-137e4057693d","test":"Determine if a notice to individuals about the processing of personally identifiable information is provided such that the notice is available to individuals upon first interacting with an organization;Just-in-time notices inform individuals of how organizations process their personally identifiable information at a time when such notices may be most useful to the individuals. Individual assumptions about how personally identifiable information will be processed might not be accurate or reliable if time has passed since the organization last presented notice or the circumstances under which the individual was last provided notice have changed. A just-in-time notice can explain data actions that organizations have identified as potentially giving rise to greater privacy risk for individuals. Organizations can use a just-in-time notice to update or remind individuals about specific data actions as they occur or highlight specific changes that occurred since last presenting notice. A just-in-time notice can be used in conjunction with just-in-time consent to explain what will occur if consent is declined. Organizations use discretion to determine when to use a just-in-time notice and may use supporting information on user demographics, focus groups, or surveys to learn about users’ privacy interests and concerns.
","uuid":"0fbdac18-7950-4c28-9b65-8ac68f126a74","family":"Personally Identifiable Information Processing and Transparency","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"8067216d-3947-40a9-a306-dccb79c99d4f","text":"frequency","parameterId":"pt-05.01_odp","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"PT-05(01)","uuid":"b1ce8997-49e4-4977-9e02-7cdc635fb223","test":"Determine if a notice of personally identifiable information processing is presented to individuals at a time and location where the individual provides personally identifiable information, in conjunction with a data action, or [SELECTED PARAMETER VALUE(S): frequency ].If a federal agency asks individuals to supply information that will become part of a system of records, the agency is required to provide a PRIVACT statement on the form used to collect the information or on a separate form that can be retained by the individual. The agency provides a PRIVACT statement in such circumstances regardless of whether the information will be collected on a paper or electronic form, on a website, on a mobile application, over the telephone, or through some other medium. This requirement ensures that the individual is provided with sufficient information about the request for information to make an informed decision on whether or not to respond.
PRIVACT statements provide formal notice to individuals of the authority that authorizes the solicitation of the information; whether providing the information is mandatory or voluntary; the principal purpose(s) for which the information is to be used; the published routine uses to which the information is subject; the effects on the individual, if any, of not providing all or any part of the information requested; and an appropriate citation and link to the relevant system of records notice. Federal agency personnel consult with the senior agency official for privacy and legal counsel regarding the notice provisions of the PRIVACT.
","uuid":"c9c21514-cccf-4e39-94ec-cae655b1e618","family":"Personally Identifiable Information Processing and Transparency","parameters":[],"subControls":"","tests":[{"testId":"PT-05(02)","uuid":"42443b0b-ecf8-4366-b8f0-f31a38030f18","test":"Determine if privacy act statements are included on forms that collect information that will be maintained in a privacy act system of records, or privacy act statements are provided on separate forms that can be retained by individuals.The PRIVACT requires that federal agencies publish a system of records notice in the Federal Register upon the establishment and/or modification of a PRIVACT system of records. As a general matter, a system of records notice is required when an agency maintains a group of any records under the control of the agency from which information is retrieved by the name of an individual or by some identifying number, symbol, or other identifier. The notice describes the existence and character of the system and identifies the system of records, the purpose(s) of the system, the authority for maintenance of the records, the categories of records maintained in the system, the categories of individuals about whom records are maintained, the routine uses to which the records are subject, and additional details about the system as described in OMB A-108.
","uuid":"f18cf6ba-7326-4887-9996-39c3b96fd16f","family":"Personally Identifiable Information Processing and Transparency","parameters":[],"subControls":"","tests":[{"testId":"PT-06a.[01]","uuid":"60f8296b-ee81-438b-a280-b3eaced8f3e1","test":"Determine if system of records notices are drafted in accordance with omb guidance for systems that process information that will be maintained in a privacy act system of records;A PRIVACT routine use is a particular kind of disclosure of a record outside of the federal agency maintaining the system of records. A routine use is an exception to the PRIVACT prohibition on the disclosure of a record in a system of records without the prior written consent of the individual to whom the record pertains. To qualify as a routine use, the disclosure must be for a purpose that is compatible with the purpose for which the information was originally collected. The PRIVACT requires agencies to describe each routine use of the records maintained in the system of records, including the categories of users of the records and the purpose of the use. Agencies may only establish routine uses by explicitly publishing them in the relevant system of records notice.
","uuid":"78b60317-4e14-4315-b641-7eae6204426d","family":"Personally Identifiable Information Processing and Transparency","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"372e694e-5431-41dc-b4b2-87987145db13","text":"frequency","parameterId":"pt-06.01_odp","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"PT-06(01)","uuid":"dfc51c2d-c60d-4cfa-a26d-9c20ccbdcbf7","test":"Determine if all routine uses published in the system of records notice are reviewed [SELECTED PARAMETER VALUE(S): frequency ] to ensure continued accuracy, and to ensure that routine uses continue to be compatible with the purpose for which the information was collected.The PRIVACT includes two sets of provisions that allow federal agencies to claim exemptions from certain requirements in the statute. In certain circumstances, these provisions allow agencies to promulgate regulations to exempt a system of records from select provisions of the PRIVACT . At a minimum, organizations’ PRIVACT exemption regulations include the specific name(s) of any system(s) of records that will be exempt, the specific provisions of the PRIVACT from which the system(s) of records is to be exempted, the reasons for the exemption, and an explanation for why the exemption is both necessary and appropriate.
","uuid":"342141ee-9f92-4e62-9eaa-3685e5af2e75","family":"Personally Identifiable Information Processing and Transparency","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"809dfc3a-f167-4585-b4a9-b75e79874705","text":"frequency","parameterId":"pt-06.02_odp","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"PT-06(02)[01]","uuid":"2c1e563d-7393-49ca-8914-728692c8de32","test":"Determine if all privacy act exemptions claimed for the system of records are reviewed [SELECTED PARAMETER VALUE(S): frequency ] to ensure that they remain appropriate and necessary in accordance with law;Organizations apply any conditions or protections that may be necessary for specific categories of personally identifiable information. These conditions may be required by laws, executive orders, directives, regulations, policies, standards, or guidelines. The requirements may also come from the results of privacy risk assessments that factor in contextual changes that may result in an organizational determination that a particular category of personally identifiable information is particularly sensitive or raises particular privacy risks. Organizations consult with the senior agency official for privacy and legal counsel regarding any protections that may be necessary.
","uuid":"25d3da94-2fc7-4d20-9848-e206129e3662","family":"Personally Identifiable Information Processing and Transparency","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"781e31d5-82ce-4c3b-a470-b1964bab1dd8","text":"processing conditions","parameterId":"pt-07_odp","default":" [Assignment: organization defined processing conditions] "}],"subControls":"","tests":[{"testId":"PT-07","uuid":"d2abeab6-1070-4c3a-ba9a-2d44a53c5a45","test":"Determine if [SELECTED PARAMETER VALUE(S): processing conditions ] are applied for specific categories of personally identifiable information.Federal law and policy establish specific requirements for organizations’ processing of Social Security numbers. Organizations take steps to eliminate unnecessary uses of Social Security numbers and other sensitive information and observe any particular requirements that apply.
","uuid":"90019c31-7344-4873-a1cf-38a8f571696a","family":"Personally Identifiable Information Processing and Transparency","parameters":[],"subControls":"","tests":[{"testId":"PT-07(01)(a)[01]","uuid":"a2d1fbcf-5ea5-4e78-b607-a4d83889edba","test":"Determine if when a system processes social security numbers, the unnecessary collection, maintenance, and use of social security numbers are eliminated;The PRIVACT limits agencies’ ability to process information that describes how individuals exercise rights guaranteed by the First Amendment. Organizations consult with the senior agency official for privacy and legal counsel regarding these requirements.
","uuid":"8142f4ae-bda1-4902-8ad9-9bf7dba835c4","family":"Personally Identifiable Information Processing and Transparency","parameters":[],"subControls":"","tests":[{"testId":"PT-07(02)","uuid":"55f06289-7879-4aea-8d29-a19fc0ec0558","test":"Determine if the processing of information describing how any individual exercises rights guaranteed by the first amendment is prohibited unless expressly authorized by statute or by the individual or unless pertinent to and within the scope of an authorized law enforcement activity.The PRIVACT establishes requirements for federal and non-federal agencies if they engage in a matching program. In general, a matching program is a computerized comparison of records from two or more automated PRIVACT systems of records or an automated system of records and automated records maintained by a non-federal agency (or agent thereof). A matching program either pertains to federal benefit programs or federal personnel or payroll records. A federal benefit match is performed to determine or verify eligibility for payments under federal benefit programs or to recoup payments or delinquent debts under federal benefit programs. A matching program involves not just the matching activity itself but also the investigative follow-up and ultimate action, if any.
","uuid":"a6c440a6-ab70-44fc-abf2-d75e5a76bde1","family":"Personally Identifiable Information Processing and Transparency","parameters":[],"subControls":"","tests":[{"testId":"PT-08a.","uuid":"1bad1284-1560-4696-ab86-ae71576d1924","test":"Determine if approval to conduct the matching program is obtained from the data integrity board when a system or organization processes information for the purpose of conducting a matching program;Risk assessment policy and procedures address the controls in the RA family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of risk assessment policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies reflecting the complex nature of organizations. Procedures can be established for security and privacy programs, for mission or business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to risk assessment policy and procedures include assessment or audit findings, security incidents or breaches, or changes in laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure.
","uuid":"2b3f6bab-2ca8-4139-aa0c-ca4ab90dd432","family":"Risk Assessment","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"b3357d1e-b309-45d2-b79b-44b5835ba63b","text":"organization-defined personnel or roles","parameterId":"ra-1_prm_1","default":" [Assignment: organization-defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"b939069c-a3b9-4fea-89bd-3e3ba887a35c","text":"personnel or roles","parameterId":"ra-01_odp.01","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"5895f963-97ba-481a-9697-090999482753","text":"personnel or roles","parameterId":"ra-01_odp.02","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"3bbd89ac-5538-4413-ac6f-72ce1aa35e1a","text":"[Selection (one or more): organization-level; mission/business process-level; system-level]","parameterId":"ra-01_odp.03","default":"[Selection (one or more): organization-level; mission/business process-level; system-level]"},{"constraints":"","displayName":"","guidance":"","uuid":"0944d697-c3af-4ebc-baac-9f85dd060403","text":"official","parameterId":"ra-01_odp.04","default":" [Assignment: organization defined official] "},{"constraints":"","displayName":"","guidance":"","uuid":"ebfd3e37-873e-4562-ad53-1ff6858904a4","text":"frequency","parameterId":"ra-01_odp.05","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"46e788a2-16c5-47f7-a56f-2db0eb7a230f","text":"events","parameterId":"ra-01_odp.06","default":" [Assignment: organization defined events] "},{"constraints":"","displayName":"","guidance":"","uuid":"5d3c1fa8-bf6b-4620-83fe-d40d789e9123","text":"frequency","parameterId":"ra-01_odp.07","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"4b1b9909-c764-4b00-8371-2474ea3153e4","text":"events","parameterId":"ra-01_odp.08","default":" [Assignment: organization defined events] "}],"subControls":"","tests":[{"testId":"RA-01a.[01]","uuid":"a27a508b-6142-43c2-87ea-82ab2e264fe6","test":"Determine if a risk assessment policy is developed and documented;Security categories describe the potential adverse impacts or negative consequences to organizational operations, organizational assets, and individuals if organizational information and systems are compromised through a loss of confidentiality, integrity, or availability. Security categorization is also a type of asset loss characterization in systems security engineering processes that is carried out throughout the system development life cycle. Organizations can use privacy risk assessments or privacy impact assessments to better understand the potential adverse effects on individuals. CNSSI 1253 provides additional guidance on categorization for national security systems.
Organizations conduct the security categorization process as an organization-wide activity with the direct involvement of chief information officers, senior agency information security officers, senior agency officials for privacy, system owners, mission and business owners, and information owners or stewards. Organizations consider the potential adverse impacts to other organizations and, in accordance with USA PATRIOT and Homeland Security Presidential Directives, potential national-level adverse impacts.
Security categorization processes facilitate the development of inventories of information assets and, along with CM-8 , mappings to specific system components where information is processed, stored, or transmitted. The security categorization process is revisited throughout the system development life cycle to ensure that the security categories remain accurate and relevant.
","uuid":"d4ccc905-f3a4-4b04-bc53-9a0957db9b01","family":"Risk Assessment","parameters":[],"subControls":"","tests":[{"testId":"RA-02a.","uuid":"81e4e2cc-8bbd-4e14-b033-d34dc548ab44","test":"Determine if the system and the information it processes, stores, and transmits are categorized;Organizations apply the high-water mark
concept to each system categorized in accordance with FIPS 199 , resulting in systems designated as low impact, moderate impact, or high impact. Organizations that desire additional granularity in the system impact designations for risk-based decision-making, can further partition the systems into sub-categories of the initial system categorization. For example, an impact-level prioritization on a moderate-impact system can produce three new sub-categories: low-moderate systems, moderate-moderate systems, and high-moderate systems. Impact-level prioritization and the resulting sub-categories of the system give organizations an opportunity to focus their investments related to security control selection and the tailoring of control baselines in responding to identified risks. Impact-level prioritization can also be used to determine those systems that may be of heightened interest or value to adversaries or represent a critical loss to the federal enterprise, sometimes described as high value assets. For such high value assets, organizations may be more focused on complexity, aggregation, and information exchanges. Systems with high value assets can be prioritized by partitioning high-impact systems into low-high systems, moderate-high systems, and high-high systems. Alternatively, organizations can apply the guidance in CNSSI 1253 for security objective-related categorization.
Risk assessments consider threats, vulnerabilities, likelihood, and impact to organizational operations and assets, individuals, other organizations, and the Nation. Risk assessments also consider risk from external parties, including contractors who operate systems on behalf of the organization, individuals who access organizational systems, service providers, and outsourcing entities.
Organizations can conduct risk assessments at all three levels in the risk management hierarchy (i.e., organization level, mission/business process level, or information system level) and at any stage in the system development life cycle. Risk assessments can also be conducted at various steps in the Risk Management Framework, including preparation, categorization, control selection, control implementation, control assessment, authorization, and control monitoring. Risk assessment is an ongoing activity carried out throughout the system development life cycle.
Risk assessments can also address information related to the system, including system design, the intended use of the system, testing results, and supply chain-related information or artifacts. Risk assessments can play an important role in control selection processes, particularly during the application of tailoring guidance and in the earliest phases of capability determination.
","uuid":"0898808e-7d27-4327-8fbc-7c302e7623ac","family":"Risk Assessment","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"8d6b09b5-4f02-4025-8f68-c683764aa84b","text":"[Selection: security and privacy plans; risk assessment report; [(NESTED PARAMETER) Assignment for ra-03_odp.02: document]]","parameterId":"ra-03_odp.01","default":"[Selection: security and privacy plans; risk assessment report; [(NESTED PARAMETER) Assignment for ra-03_odp.02: document]]"},{"constraints":"","displayName":"","guidance":"","uuid":"0c3b8829-f9d4-450f-b10d-1abaf64da720","text":"document","parameterId":"ra-03_odp.02","default":" [Assignment: organization defined document] "},{"constraints":"","displayName":"","guidance":"","uuid":"ea8565d2-9168-46f2-a4b4-90bed784cb33","text":"frequency","parameterId":"ra-03_odp.03","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"a4039080-b02a-496d-ba29-ddf5ca108215","text":"personnel or roles","parameterId":"ra-03_odp.04","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"565c5f8e-0e2a-437e-8417-ace3f0c52b5e","text":"frequency","parameterId":"ra-03_odp.05","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"RA-03a.01","uuid":"54791c66-39d8-4d2e-9b04-a386e377d36b","test":"Determine if a risk assessment is conducted to identify threats to and vulnerabilities in the system;Supply chain-related events include disruption, use of defective components, insertion of counterfeits, theft, malicious development practices, improper delivery practices, and insertion of malicious code. These events can have a significant impact on the confidentiality, integrity, or availability of a system and its information and, therefore, can also adversely impact organizational operations (including mission, functions, image, or reputation), organizational assets, individuals, other organizations, and the Nation. The supply chain-related events may be unintentional or malicious and can occur at any point during the system life cycle. An analysis of supply chain risk can help an organization identify systems or components for which additional supply chain risk mitigations are required.
","uuid":"a15fca0d-36b7-4a50-9c20-dd7a788fffa1","family":"Risk Assessment","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"15e95e9b-e96e-42a5-bcbe-ac56b0c333c4","text":"systems, system components, and system services","parameterId":"ra-03.01_odp.01","default":" [Assignment: organization defined systems, system components, and system services] "},{"constraints":"","displayName":"","guidance":"","uuid":"1a45b61f-c6f4-41ea-a439-77742c1c2ec7","text":"frequency","parameterId":"ra-03.01_odp.02","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"RA-03(01)(a)","uuid":"9965a411-ff0e-4ed8-9194-695d458befe4","test":"Determine if supply chain risks associated with [SELECTED PARAMETER VALUE(S): systems, system components, and system services ] are assessed;Organizations employ all-source intelligence to inform engineering, acquisition, and risk management decisions. All-source intelligence consists of information derived from all available sources, including publicly available or open-source information, measurement and signature intelligence, human intelligence, signals intelligence, and imagery intelligence. All-source intelligence is used to analyze the risk of vulnerabilities (both intentional and unintentional) from development, manufacturing, and delivery processes, people, and the environment. The risk analysis may be performed on suppliers at multiple tiers in the supply chain sufficient to manage risks. Organizations may develop agreements to share all-source intelligence information or resulting decisions with other organizations, as appropriate.
","uuid":"78fa3c52-3a3a-422f-b411-03c5b7430a77","family":"Risk Assessment","parameters":[],"subControls":"","tests":[{"testId":"RA-03(02)","uuid":"9c2f2559-2b0d-4938-a116-c8c4cd6c276b","test":"Determine if all-source intelligence is used to assist in the analysis of risk.The threat awareness information that is gathered feeds into the organization’s information security operations to ensure that procedures are updated in response to the changing threat environment. For example, at higher threat levels, organizations may change the privilege or authentication thresholds required to perform certain operations.
","uuid":"38b72449-dedb-4520-b7da-c52b47461a2c","family":"Risk Assessment","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"91459e1f-50f8-4280-be7b-a88254c20a31","text":"means","parameterId":"ra-03.03_odp","default":" [Assignment: organization defined means] "}],"subControls":"","tests":[{"testId":"RA-03(03)","uuid":"5e848163-0f07-404e-aaf9-c7d1765c9f2d","test":"Determine if the current cyber threat environment is determined on an ongoing basis using [SELECTED PARAMETER VALUE(S): means ].A properly resourced Security Operations Center (SOC) or Computer Incident Response Team (CIRT) may be overwhelmed by the volume of information generated by the proliferation of security tools and appliances unless it employs advanced automation and analytics to analyze the data. Advanced automation and analytics capabilities are typically supported by artificial intelligence concepts, including machine learning. Examples include Automated Threat Discovery and Response (which includes broad-based collection, context-based analysis, and adaptive response capabilities), automated workflow operations, and machine assisted decision tools. Note, however, that sophisticated adversaries may be able to extract information related to analytic parameters and retrain the machine learning to classify malicious activity as benign. Accordingly, machine learning is augmented by human monitoring to ensure that sophisticated adversaries are not able to conceal their activities.
","uuid":"3c2c0489-4426-46db-b0c0-ed3f0e0bf1b7","family":"Risk Assessment","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"230fc7d9-2184-411a-b074-78a5a0ee1b96","text":"organization-defined advanced automation and analytics capabilities","parameterId":"ra-3.4_prm_2","default":" [Assignment: organization-defined advanced automation and analytics capabilities] "},{"constraints":"","displayName":"","guidance":"","uuid":"82af9275-6704-49d5-9ed2-0bb716e61491","text":"advanced automation capabilities","parameterId":"ra-03.04_odp.01","default":" [Assignment: organization defined advanced automation capabilities] "},{"constraints":"","displayName":"","guidance":"","uuid":"d021bbe5-2e13-49e1-ab05-e7e6aa47e63d","text":"systems or system components","parameterId":"ra-03.04_odp.02","default":" [Assignment: organization defined systems or system components] "},{"constraints":"","displayName":"","guidance":"","uuid":"880cb1bc-439f-4219-a0a2-2dba41aefbf8","text":"advanced analytics capabilities","parameterId":"ra-03.04_odp.03","default":" [Assignment: organization defined advanced analytics capabilities] "}],"subControls":"","tests":[{"testId":"RA-03(04)[01]","uuid":"ab39131b-7801-451c-a4ab-06538c2c1dce","test":"Determine if [SELECTED PARAMETER VALUE(S): advanced automation capabilities ] are employed to predict and identify risks to [SELECTED PARAMETER VALUE(S): systems or system components ];Security categorization of information and systems guides the frequency and comprehensiveness of vulnerability monitoring (including scans). Organizations determine the required vulnerability monitoring for system components, ensuring that the potential sources of vulnerabilities—such as infrastructure components (e.g., switches, routers, guards, sensors), networked printers, scanners, and copiers—are not overlooked. The capability to readily update vulnerability monitoring tools as new vulnerabilities are discovered and announced and as new scanning methods are developed helps to ensure that new vulnerabilities are not missed by employed vulnerability monitoring tools. The vulnerability monitoring tool update process helps to ensure that potential vulnerabilities in the system are identified and addressed as quickly as possible. Vulnerability monitoring and analyses for custom software may require additional approaches, such as static analysis, dynamic analysis, binary analysis, or a hybrid of the three approaches. Organizations can use these analysis approaches in source code reviews and in a variety of tools, including web-based application scanners, static analysis tools, and binary analyzers.
Vulnerability monitoring includes scanning for patch levels; scanning for functions, ports, protocols, and services that should not be accessible to users or devices; and scanning for flow control mechanisms that are improperly configured or operating incorrectly. Vulnerability monitoring may also include continuous vulnerability monitoring tools that use instrumentation to continuously analyze components. Instrumentation-based tools may improve accuracy and may be run throughout an organization without scanning. Vulnerability monitoring tools that facilitate interoperability include tools that are Security Content Automated Protocol (SCAP)-validated. Thus, organizations consider using scanning tools that express vulnerabilities in the Common Vulnerabilities and Exposures (CVE) naming convention and that employ the Open Vulnerability Assessment Language (OVAL) to determine the presence of vulnerabilities. Sources for vulnerability information include the Common Weakness Enumeration (CWE) listing and the National Vulnerability Database (NVD). Control assessments, such as red team exercises, provide additional sources of potential vulnerabilities for which to scan. Organizations also consider using scanning tools that express vulnerability impact by the Common Vulnerability Scoring System (CVSS).
Vulnerability monitoring includes a channel and process for receiving reports of security vulnerabilities from the public at-large. Vulnerability disclosure programs can be as simple as publishing a monitored email address or web form that can receive reports, including notification authorizing good-faith research and disclosure of security vulnerabilities. Organizations generally expect that such research is happening with or without their authorization and can use public vulnerability disclosure channels to increase the likelihood that discovered vulnerabilities are reported directly to the organization for remediation.
Organizations may also employ the use of financial incentives (also known as bug bounties
) to further encourage external security researchers to report discovered vulnerabilities. Bug bounty programs can be tailored to the organization’s needs. Bounties can be operated indefinitely or over a defined period of time and can be offered to the general public or to a curated group. Organizations may run public and private bounties simultaneously and could choose to offer partially credentialed access to certain participants in order to evaluate security vulnerabilities from privileged vantage points.
Due to the complexity of modern software, systems, and other factors, new vulnerabilities are discovered on a regular basis. It is important that newly discovered vulnerabilities are added to the list of vulnerabilities to be scanned to ensure that the organization can take steps to mitigate those vulnerabilities in a timely manner.
","uuid":"92fb5225-e389-435f-b346-8186d9c8f9a1","family":"Risk Assessment","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"553d6368-d8a1-4cfc-be08-89465ac34ab4","text":"[Selection (one or more): [(NESTED PARAMETER) Assignment for ra-05.02_odp.02: frequency]; prior to a new scan; when new vulnerabilities are identified and reported]","parameterId":"ra-05.02_odp.01","default":"[Selection (one or more): [(NESTED PARAMETER) Assignment for ra-05.02_odp.02: frequency]; prior to a new scan; when new vulnerabilities are identified and reported]"},{"constraints":"","displayName":"","guidance":"","uuid":"1e3b359c-adee-4d6c-99f6-a7c5e24730e1","text":"frequency","parameterId":"ra-05.02_odp.02","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"RA-05(02)","uuid":"e5d548e0-f029-4e23-beb4-04af637504d9","test":"Determine if the system vulnerabilities to be scanned are updated [SELECTED PARAMETER VALUE(S): [Selection (one or more): [(NESTED PARAMETER) Assignment for ra-05.02_odp.02: frequency]; prior to a new scan; when new vulnerabilities are identified and reported] ].The breadth of vulnerability scanning coverage can be expressed as a percentage of components within the system, by the particular types of systems, by the criticality of systems, or by the number of vulnerabilities to be checked. Conversely, the depth of vulnerability scanning coverage can be expressed as the level of the system design that the organization intends to monitor (e.g., component, module, subsystem, element). Organizations can determine the sufficiency of vulnerability scanning coverage with regard to its risk tolerance and other factors. Scanning tools and how the tools are configured may affect the depth and coverage. Multiple scanning tools may be needed to achieve the desired depth and coverage. SP 800-53A provides additional information on the breadth and depth of coverage.
","uuid":"aaaaa3a8-d112-42ad-9b45-2667771adab6","family":"Risk Assessment","parameters":[],"subControls":"","tests":[{"testId":"RA-05(03)","uuid":"e9a32374-f0f6-4ba6-9bf0-4fabfea702a7","test":"Determine if the breadth and depth of vulnerability scanning coverage are defined.Discoverable information includes information that adversaries could obtain without compromising or breaching the system, such as by collecting information that the system is exposing or by conducting extensive web searches. Corrective actions include notifying appropriate organizational personnel, removing designated information, or changing the system to make the designated information less relevant or attractive to adversaries. This enhancement excludes intentionally discoverable information that may be part of a decoy capability (e.g., honeypots, honeynets, or deception nets) deployed by the organization.
","uuid":"6bdc4272-b213-4c5a-8ce6-139fc3e724b7","family":"Risk Assessment","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"8e2e5e54-f3bc-409b-9525-ec0b86d3fc72","text":"corrective actions","parameterId":"ra-05.04_odp","default":" [Assignment: organization defined corrective actions] "}],"subControls":"","tests":[{"testId":"RA-05(04)[01]","uuid":"c3afcc0e-b2c6-4a83-8d5c-3ba081a82e1a","test":"Determine if information about the system is discoverable;In certain situations, the nature of the vulnerability scanning may be more intrusive, or the system component that is the subject of the scanning may contain classified or controlled unclassified information, such as personally identifiable information. Privileged access authorization to selected system components facilitates more thorough vulnerability scanning and protects the sensitive nature of such scanning.
","uuid":"82f90cb8-e6cd-44c7-b4e0-80a2a88e8970","family":"Risk Assessment","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"5e327a96-9851-44d6-b6ea-6087df64ccf9","text":"system components","parameterId":"ra-05.05_odp.01","default":" [Assignment: organization defined system components] "},{"constraints":"","displayName":"","guidance":"","uuid":"45583797-a03f-4968-afcf-d01e4192876f","text":"vulnerability scanning activities","parameterId":"ra-05.05_odp.02","default":" [Assignment: organization defined vulnerability scanning activities] "}],"subControls":"","tests":[{"testId":"RA-05(05)","uuid":"7b89c2fa-015f-4eb2-94ae-44ed700afe9a","test":"Determine if privileged access authorization is implemented to [SELECTED PARAMETER VALUE(S): system components ] for [SELECTED PARAMETER VALUE(S): vulnerability scanning activities ].Using automated mechanisms to analyze multiple vulnerability scans over time can help determine trends in system vulnerabilities and identify patterns of attack.
","uuid":"45211cc1-9a90-4916-8d6b-f1682a5c1953","family":"Risk Assessment","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"0e795eff-9643-44fa-9c04-8e5beef6605d","text":"automated mechanisms","parameterId":"ra-05.06_odp","default":" [Assignment: organization defined automated mechanisms] "}],"subControls":"","tests":[{"testId":"RA-05(06)","uuid":"e43e70e4-44ee-4ae0-ba00-333152efed74","test":"Determine if the results of multiple vulnerability scans are compared using [SELECTED PARAMETER VALUE(S): automated mechanisms ].Reviewing historic audit logs to determine if a recently detected vulnerability in a system has been previously exploited by an adversary can provide important information for forensic analyses. Such analyses can help identify, for example, the extent of a previous intrusion, the trade craft employed during the attack, organizational information exfiltrated or modified, mission or business capabilities affected, and the duration of the attack.
","uuid":"b78f752e-9837-4a1c-af37-a6af5254e9a1","family":"Risk Assessment","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"e1c0c0fa-4cb9-42bb-9a2b-c20a1ab853dd","text":"system","parameterId":"ra-05.08_odp.01","default":" [Assignment: organization defined system] "},{"constraints":"","displayName":"","guidance":"","uuid":"1bd41148-b78f-4eb4-98ac-166e7fc51c4a","text":"time period","parameterId":"ra-05.08_odp.02","default":" [Assignment: organization defined time period] "}],"subControls":"","tests":[{"testId":"RA-05(08)","uuid":"578087bf-4af5-49ae-8e0a-6b4b62e50b48","test":"Determine if historic audit logs are reviewed to determine if a vulnerability identified in a [SELECTED PARAMETER VALUE(S): system ] has been previously exploited within [SELECTED PARAMETER VALUE(S): time period ].An attack vector is a path or means by which an adversary can gain access to a system in order to deliver malicious code or exfiltrate information. Organizations can use attack trees to show how hostile activities by adversaries interact and combine to produce adverse impacts or negative consequences to systems and organizations. Such information, together with correlated data from vulnerability scanning tools, can provide greater clarity regarding multi-vulnerability and multi-hop attack vectors. The correlation of vulnerability scanning information is especially important when organizations are transitioning from older technologies to newer technologies (e.g., transitioning from IPv4 to IPv6 network protocols). During such transitions, some system components may inadvertently be unmanaged and create opportunities for adversary exploitation.
","uuid":"e939c8f1-8d41-4df9-bd65-2e4e6faa6973","family":"Risk Assessment","parameters":[],"subControls":"","tests":[{"testId":"RA-05(10)","uuid":"bb974f45-c836-41f2-830b-49eb8b0146f6","test":"Determine if the output from vulnerability scanning tools is correlated to determine the presence of multi-vulnerability and multi-hop attack vectors.The reporting channel is publicly discoverable and contains clear language authorizing good-faith research and the disclosure of vulnerabilities to the organization. The organization does not condition its authorization on an expectation of indefinite non-disclosure to the public by the reporting entity but may request a specific time period to properly remediate the vulnerability.
","uuid":"d070a87d-efed-4f37-8805-b0e887d09f97","family":"Risk Assessment","parameters":[],"subControls":"","tests":[{"testId":"RA-05(11)","uuid":"71669673-7ccb-4be7-93ab-d5d1ef0f31a1","test":"Determine if a public reporting channel is established for receiving reports of vulnerabilities in organizational systems and system components.A technical surveillance countermeasures survey is a service provided by qualified personnel to detect the presence of technical surveillance devices and hazards and to identify technical security weaknesses that could be used in the conduct of a technical penetration of the surveyed facility. Technical surveillance countermeasures surveys also provide evaluations of the technical security posture of organizations and facilities and include visual, electronic, and physical examinations of surveyed facilities, internally and externally. The surveys also provide useful input for risk assessments and information regarding organizational exposure to potential adversaries.
","uuid":"3b58f5cb-8517-4cbd-87c8-2890984b377e","family":"Risk Assessment","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"df7e1bf5-fb48-4426-91cf-bfcc7199e780","text":"locations","parameterId":"ra-06_odp.01","default":" [Assignment: organization defined locations] "},{"constraints":"","displayName":"","guidance":"","uuid":"f3cab7d0-8674-4067-b716-e83fb523fce8","text":"[Selection (one or more): [(NESTED PARAMETER) Assignment for ra-06_odp.03: frequency]; when [(NESTED PARAMETER) Assignment for ra-06_odp.04: events or indicators]]","parameterId":"ra-06_odp.02","default":"[Selection (one or more): [(NESTED PARAMETER) Assignment for ra-06_odp.03: frequency]; when [(NESTED PARAMETER) Assignment for ra-06_odp.04: events or indicators]]"},{"constraints":"","displayName":"","guidance":"","uuid":"e1419540-21ec-40ac-a265-cb93f0e530ee","text":"frequency","parameterId":"ra-06_odp.03","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"541e7aa4-e1f0-4ed2-bd32-3d11dceebd89","text":"events or indicators","parameterId":"ra-06_odp.04","default":" [Assignment: organization defined events or indicators] "}],"subControls":"","tests":[{"testId":"RA-06","uuid":"ad21ec4e-2b9d-42d6-950f-8ec8fcebd89d","test":"Determine if a technical surveillance countermeasures survey is employed at [SELECTED PARAMETER VALUE(S): locations ], [SELECTED PARAMETER VALUE(S): [Selection (one or more): [(NESTED PARAMETER) Assignment for ra-06_odp.03: frequency]; when [(NESTED PARAMETER) Assignment for ra-06_odp.04: events or indicators]] ].Organizations have many options for responding to risk including mitigating risk by implementing new controls or strengthening existing controls, accepting risk with appropriate justification or rationale, sharing or transferring risk, or avoiding risk. The risk tolerance of the organization influences risk response decisions and actions. Risk response addresses the need to determine an appropriate response to risk before generating a plan of action and milestones entry. For example, the response may be to accept risk or reject risk, or it may be possible to mitigate the risk immediately so that a plan of action and milestones entry is not needed. However, if the risk response is to mitigate the risk, and the mitigation cannot be completed immediately, a plan of action and milestones entry is generated.
","uuid":"fd4479d4-cfce-4da6-8be0-531c4018beb7","family":"Risk Assessment","parameters":[],"subControls":"","tests":[{"testId":"RA-07[01]","uuid":"a0aa445e-6fc4-40b8-987b-7fc78b6cb44a","test":"Determine if findings from security assessments are responded to in accordance with organizational risk tolerance;A privacy impact assessment is an analysis of how personally identifiable information is handled to ensure that handling conforms to applicable privacy requirements, determine the privacy risks associated with an information system or activity, and evaluate ways to mitigate privacy risks. A privacy impact assessment is both an analysis and a formal document that details the process and the outcome of the analysis.
Organizations conduct and develop a privacy impact assessment with sufficient clarity and specificity to demonstrate that the organization fully considered privacy and incorporated appropriate privacy protections from the earliest stages of the organization’s activity and throughout the information life cycle. In order to conduct a meaningful privacy impact assessment, the organization’s senior agency official for privacy works closely with program managers, system owners, information technology experts, security officials, counsel, and other relevant organization personnel. Moreover, a privacy impact assessment is not a time-restricted activity that is limited to a particular milestone or stage of the information system or personally identifiable information life cycles. Rather, the privacy analysis continues throughout the system and personally identifiable information life cycles. Accordingly, a privacy impact assessment is a living document that organizations update whenever changes to the information technology, changes to the organization’s practices, or other factors alter the privacy risks associated with the use of such information technology.
To conduct the privacy impact assessment, organizations can use security and privacy risk assessments. Organizations may also use other related processes that may have different names, including privacy threshold analyses. A privacy impact assessment can also serve as notice to the public regarding the organization’s practices with respect to privacy. Although conducting and publishing privacy impact assessments may be required by law, organizations may develop such policies in the absence of applicable laws. For federal agencies, privacy impact assessments may be required by EGOV ; agencies should consult with their senior agency official for privacy and legal counsel on this requirement and be aware of the statutory exceptions and OMB guidance relating to the provision.
","uuid":"e932cb5a-5cab-445e-8219-60e79bb0b94f","family":"Risk Assessment","parameters":[],"subControls":"","tests":[{"testId":"RA-08a.","uuid":"3d3be40c-2bef-48c5-ba3e-06f13a9dcbc4","test":"Determine if privacy impact assessments are conducted for systems, programs, or other activities before developing or procuring information technology that processes personally identifiable information;Not all system components, functions, or services necessarily require significant protections. For example, criticality analysis is a key tenet of supply chain risk management and informs the prioritization of protection activities. The identification of critical system components and functions considers applicable laws, executive orders, regulations, directives, policies, standards, system functionality requirements, system and component interfaces, and system and component dependencies. Systems engineers conduct a functional decomposition of a system to identify mission-critical functions and components. The functional decomposition includes the identification of organizational missions supported by the system, decomposition into the specific functions to perform those missions, and traceability to the hardware, software, and firmware components that implement those functions, including when the functions are shared by many components within and external to the system.
The operational environment of a system or a system component may impact the criticality, including the connections to and dependencies on cyber-physical systems, devices, system-of-systems, and outsourced IT services. System components that allow unmediated access to critical system components or functions are considered critical due to the inherent vulnerabilities that such components create. Component and function criticality are assessed in terms of the impact of a component or function failure on the organizational missions that are supported by the system that contains the components and functions.
Criticality analysis is performed when an architecture or design is being developed, modified, or upgraded. If such analysis is performed early in the system development life cycle, organizations may be able to modify the system design to reduce the critical nature of these components and functions, such as by adding redundancy or alternate paths into the system design. Criticality analysis can also influence the protection measures required by development contractors. In addition to criticality analysis for systems, system components, and system services, criticality analysis of information is an important consideration. Such analysis is conducted as part of security categorization in RA-2.
","uuid":"37cb5478-1773-4d0b-84c1-35e12ea98f36","family":"Risk Assessment","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"7441ff47-be48-4019-9b9d-496141bb7570","text":"systems, system components, or system services","parameterId":"ra-09_odp.01","default":" [Assignment: organization defined systems, system components, or system services] "},{"constraints":"","displayName":"","guidance":"","uuid":"96775e10-4af5-4475-b9cc-7db22679b41a","text":"decision points in the system development life cycle","parameterId":"ra-09_odp.02","default":" [Assignment: organization defined decision points in the system development life cycle] "}],"subControls":"","tests":[{"testId":"RA-09","uuid":"0136d48e-2739-4b8e-9e06-1d66efdd69b9","test":"Determine if critical system components and functions are identified by performing a criticality analysis for [SELECTED PARAMETER VALUE(S): systems, system components, or system services ] at [SELECTED PARAMETER VALUE(S): decision points in the system development life cycle ].Threat hunting is an active means of cyber defense in contrast to traditional protection measures, such as firewalls, intrusion detection and prevention systems, quarantining malicious code in sandboxes, and Security Information and Event Management technologies and systems. Cyber threat hunting involves proactively searching organizational systems, networks, and infrastructure for advanced threats. The objective is to track and disrupt cyber adversaries as early as possible in the attack sequence and to measurably improve the speed and accuracy of organizational responses. Indications of compromise include unusual network traffic, unusual file changes, and the presence of malicious code. Threat hunting teams leverage existing threat intelligence and may create new threat intelligence, which is shared with peer organizations, Information Sharing and Analysis Organizations (ISAO), Information Sharing and Analysis Centers (ISAC), and relevant government departments and agencies.
","uuid":"ed6dbad7-70a6-4f69-95ac-c1626b0826e8","family":"Risk Assessment","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"652ca747-0ce7-4b82-b75f-803c47b7fc74","text":"frequency","parameterId":"ra-10_odp","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"RA-10a.01","uuid":"b7a62f58-432a-4179-b25c-b84b4633ca47","test":"Determine if a cyber threat capability is established and maintained to search for indicators of compromise in organizational systems;System and services acquisition policy and procedures address the controls in the SA family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of system and services acquisition policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission or business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to system and services acquisition policy and procedures include assessment or audit findings, security incidents or breaches, or changes in laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure.
","uuid":"42f7073e-3fa6-45af-8abd-24638100dd29","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"08c3d762-fb80-4855-9f5f-4d2507a8b7d2","text":"organization-defined personnel or roles","parameterId":"sa-1_prm_1","default":" [Assignment: organization-defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"7ef7558c-c4e5-4c85-a82c-f89de6edaac4","text":"personnel or roles","parameterId":"sa-01_odp.01","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"3257edeb-53f2-4122-b16a-d6e24ceb11ad","text":"personnel or roles","parameterId":"sa-01_odp.02","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"b0c70025-e828-45da-9a3e-0a23821b8f9c","text":"[Selection (one or more): organization-level; mission/business process-level; system-level]","parameterId":"sa-01_odp.03","default":"[Selection (one or more): organization-level; mission/business process-level; system-level]"},{"constraints":"","displayName":"","guidance":"","uuid":"b715b08f-56e2-4b46-b590-8c1b381af71e","text":"official","parameterId":"sa-01_odp.04","default":" [Assignment: organization defined official] "},{"constraints":"","displayName":"","guidance":"","uuid":"f1344c63-46b3-45f1-abd5-2ba94308eeb0","text":"frequency","parameterId":"sa-01_odp.05","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"9d109b67-201a-4187-92bf-caa231d15255","text":"events","parameterId":"sa-01_odp.06","default":" [Assignment: organization defined events] "},{"constraints":"","displayName":"","guidance":"","uuid":"f18fa623-707c-4f87-a96c-800cb6f1c3e3","text":"frequency","parameterId":"sa-01_odp.07","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"94c1fe70-c17f-4eef-a5c2-b6ca52069a32","text":"events","parameterId":"sa-01_odp.08","default":" [Assignment: organization defined events] "}],"subControls":"","tests":[{"testId":"SA-01a.[01]","uuid":"d0d593b1-7942-4fd5-9d9e-f9b30b836143","test":"Determine if a system and services acquisition policy is developed and documented;Resource allocation for information security and privacy includes funding for system and services acquisition, sustainment, and supply chain-related risks throughout the system development life cycle.
","uuid":"dd354f83-6f30-48a3-94c1-06e6588a3410","family":"System and Services Acquisition","parameters":[],"subControls":"","tests":[{"testId":"SA-02a.[01]","uuid":"94dd8d8e-5020-400a-bb14-32395b08d54e","test":"Determine if the high-level information security requirements for the system or system service are determined in mission and business process planning;A system development life cycle process provides the foundation for the successful development, implementation, and operation of organizational systems. The integration of security and privacy considerations early in the system development life cycle is a foundational principle of systems security engineering and privacy engineering. To apply the required controls within the system development life cycle requires a basic understanding of information security and privacy, threats, vulnerabilities, adverse impacts, and risk to critical mission and business functions. The security engineering principles in SA-8 help individuals properly design, code, and test systems and system components. Organizations include qualified personnel (e.g., senior agency information security officers, senior agency officials for privacy, security and privacy architects, and security and privacy engineers) in system development life cycle processes to ensure that established security and privacy requirements are incorporated into organizational systems. Role-based security and privacy training programs can ensure that individuals with key security and privacy roles and responsibilities have the experience, skills, and expertise to conduct assigned system development life cycle activities.
The effective integration of security and privacy requirements into enterprise architecture also helps to ensure that important security and privacy considerations are addressed throughout the system life cycle and that those considerations are directly related to organizational mission and business processes. This process also facilitates the integration of the information security and privacy architectures into the enterprise architecture, consistent with the risk management strategy of the organization. Because the system development life cycle involves multiple organizations, (e.g., external suppliers, developers, integrators, service providers), acquisition and supply chain risk management functions and controls play significant roles in the effective management of the system during the life cycle.
","uuid":"aff6e481-3b77-40fc-83ea-7ee6db9a8ad2","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"73f3b8a9-d13d-40f3-8c7c-059c221cb09e","text":"system-development life cycle","parameterId":"sa-03_odp","default":" [Assignment: organization defined system-development life cycle] "}],"subControls":"","tests":[{"testId":"SA-03a.[01]","uuid":"891daafa-20ba-40e3-afb3-ad53d77e55c0","test":"Determine if the system is acquired, developed, and managed using [SELECTED PARAMETER VALUE(S): system-development life cycle ] that incorporates information security considerations;The preproduction environment includes development, test, and integration environments. The program protection planning processes established by the Department of Defense are examples of managing the preproduction environment for defense contractors. Criticality analysis and the application of controls on developers also contribute to a more secure system development environment.
","uuid":"cb5ea7b5-6bca-45b0-9a82-f351323706c7","family":"System and Services Acquisition","parameters":[],"subControls":"","tests":[{"testId":"SA-03(01)","uuid":"a6b63d33-616c-4d58-9d55-6e440973c4d7","test":"Determine if system pre-production environments are protected commensurate with risk throughout the system development life cycle for the system, system component, or system service.Live data is also referred to as operational data. The use of live or operational data in preproduction (i.e., development, test, and integration) environments can result in significant risks to organizations. In addition, the use of personally identifiable information in testing, research, and training increases the risk of unauthorized disclosure or misuse of such information. Therefore, it is important for the organization to manage any additional risks that may result from the use of live or operational data. Organizations can minimize such risks by using test or dummy data during the design, development, and testing of systems, system components, and system services. Risk assessment techniques may be used to determine if the risk of using live or operational data is acceptable.
","uuid":"c4bce626-4d6b-4839-b82b-4bdf58635a03","family":"System and Services Acquisition","parameters":[],"subControls":"","tests":[{"testId":"SA-03(02)a.[01]","uuid":"f38f7ceb-7915-4580-92bc-2a40ebae2873","test":"Determine if the use of live data in pre-production environments is approved for the system, system component, or system service;Technology refresh planning may encompass hardware, software, firmware, processes, personnel skill sets, suppliers, service providers, and facilities. The use of obsolete or nearing obsolete technology may increase the security and privacy risks associated with unsupported components, counterfeit or repurposed components, components unable to implement security or privacy requirements, slow or inoperable components, components from untrusted sources, inadvertent personnel error, or increased complexity. Technology refreshes typically occur during the operations and maintenance stage of the system development life cycle.
","uuid":"e5f5e2e1-2868-4dba-a82a-80289a3cc541","family":"System and Services Acquisition","parameters":[],"subControls":"","tests":[{"testId":"SA-03(03)[01]","uuid":"4d840fd7-6b06-4907-9120-f7cda2f566df","test":"Determine if a technology refresh schedule is planned for the system throughout the system development life cycle;Security and privacy functional requirements are typically derived from the high-level security and privacy requirements described in SA-2 . The derived requirements include security and privacy capabilities, functions, and mechanisms. Strength requirements associated with such capabilities, functions, and mechanisms include degree of correctness, completeness, resistance to tampering or bypass, and resistance to direct attack. Assurance requirements include development processes, procedures, and methodologies as well as the evidence from development and assessment activities that provide grounds for confidence that the required functionality is implemented and possesses the required strength of mechanism. SP 800-160-1 describes the process of requirements engineering as part of the system development life cycle.
Controls can be viewed as descriptions of the safeguards and protection capabilities appropriate for achieving the particular security and privacy objectives of the organization and for reflecting the security and privacy requirements of stakeholders. Controls are selected and implemented in order to satisfy system requirements and include developer and organizational responsibilities. Controls can include technical, administrative, and physical aspects. In some cases, the selection and implementation of a control may necessitate additional specification by the organization in the form of derived requirements or instantiated control parameter values. The derived requirements and control parameter values may be necessary to provide the appropriate level of implementation detail for controls within the system development life cycle.
Security and privacy documentation requirements address all stages of the system development life cycle. Documentation provides user and administrator guidance for the implementation and operation of controls. The level of detail required in such documentation is based on the security categorization or classification level of the system and the degree to which organizations depend on the capabilities, functions, or mechanisms to meet risk response expectations. Requirements can include mandated configuration settings that specify allowed functions, ports, protocols, and services. Acceptance criteria for systems, system components, and system services are defined in the same manner as the criteria for any organizational acquisition or procurement.
","uuid":"877f536b-119e-48fc-bc06-5f8394b88dc6","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"439ef027-d29d-402a-8dfc-09b8a9db94e7","text":"[Selection (one or more): standardized contract language; [(NESTED PARAMETER) Assignment for sa-04_odp.02: contract language]]","parameterId":"sa-04_odp.01","default":"[Selection (one or more): standardized contract language; [(NESTED PARAMETER) Assignment for sa-04_odp.02: contract language]]"},{"constraints":"","displayName":"","guidance":"","uuid":"b7e35d8b-cc28-4e87-9cce-b42e5de31b9f","text":"contract language","parameterId":"sa-04_odp.02","default":" [Assignment: organization defined contract language] "}],"subControls":"","tests":[{"testId":"SA-04a.[01]","uuid":"447a85dc-d98f-42c8-8f8a-0542713beebc","test":"Determine if security functional requirements, descriptions, and criteria are included explicitly or by reference using [SELECTED PARAMETER VALUE(S): [Selection (one or more): standardized contract language; [(NESTED PARAMETER) Assignment for sa-04_odp.02: contract language]] ] in the acquisition contract for the system, system component, or system service;Functional properties of security and privacy controls describe the functionality (i.e., security or privacy capability, functions, or mechanisms) visible at the interfaces of the controls and specifically exclude functionality and data structures internal to the operation of the controls.
","uuid":"506ccf24-67bd-4e26-b78f-ff0c8baafb25","family":"System and Services Acquisition","parameters":[],"subControls":"","tests":[{"testId":"SA-04(01)","uuid":"1584dcaa-c177-4b21-8d6f-179039baf751","test":"Determine if the developer of the system, system component, or system service is required to provide a description of the functional properties of the controls to be implemented.Organizations may require different levels of detail in the documentation for the design and implementation of controls in organizational systems, system components, or system services based on mission and business requirements, requirements for resiliency and trustworthiness, and requirements for analysis and testing. Systems can be partitioned into multiple subsystems. Each subsystem within the system can contain one or more modules. The high-level design for the system is expressed in terms of subsystems and the interfaces between subsystems providing security-relevant functionality. The low-level design for the system is expressed in terms of modules and the interfaces between modules providing security-relevant functionality. Design and implementation documentation can include manufacturer, version, serial number, verification hash signature, software libraries used, date of purchase or download, and the vendor or download source. Source code and hardware schematics are referred to as the implementation representation of the system.
","uuid":"97922704-b4ba-45ab-85b2-42474841eafa","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"8dbfb7f2-ff57-487a-ba1d-977180ca7763","text":"[Selection (one or more): security-relevant external system interfaces; high-level design; low-level design; source code or hardware schematics; [(NESTED PARAMETER) Assignment for sa-04.02_odp.02: design and implementation information]]","parameterId":"sa-04.02_odp.01","default":"[Selection (one or more): security-relevant external system interfaces; high-level design; low-level design; source code or hardware schematics; [(NESTED PARAMETER) Assignment for sa-04.02_odp.02: design and implementation information]]"},{"constraints":"","displayName":"","guidance":"","uuid":"e66bfe7a-1e62-48e3-a3d4-81d5e4173619","text":"design and implementation information","parameterId":"sa-04.02_odp.02","default":" [Assignment: organization defined design and implementation information] "},{"constraints":"","displayName":"","guidance":"","uuid":"24226331-0796-4051-80bb-f6b3766ac0e9","text":"level of detail","parameterId":"sa-04.02_odp.03","default":" [Assignment: organization defined level of detail] "}],"subControls":"","tests":[{"testId":"SA-04(02)","uuid":"ff04784a-4854-4ae0-bac8-63385d5160a0","test":"Determine if the developer of the system, system component, or system service is required to provide design and implementation information for the controls that includes using [SELECTED PARAMETER VALUE(S): [Selection (one or more): security-relevant external system interfaces; high-level design; low-level design; source code or hardware schematics; [(NESTED PARAMETER) Assignment for sa-04.02_odp.02: design and implementation information]] ] at [SELECTED PARAMETER VALUE(S): level of detail ].Following a system development life cycle that includes state-of-the-practice software development methods, systems engineering methods, systems security and privacy engineering methods, and quality control processes helps to reduce the number and severity of latent errors within systems, system components, and system services. Reducing the number and severity of such errors reduces the number of vulnerabilities in those systems, components, and services. Transparency in the methods and techniques that developers select and implement for systems engineering, systems security and privacy engineering, software development, component and system assessments, and quality control processes provides an increased level of assurance in the trustworthiness of the system, system component, or system service being acquired.
","uuid":"c6c934b0-d117-4b67-9fdf-3516dcd4cd29","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"9e48a17f-d280-4176-8f21-e18500373c53","text":"systems engineering methods","parameterId":"sa-04.03_odp.01","default":" [Assignment: organization defined systems engineering methods] "},{"constraints":"","displayName":"","guidance":"","uuid":"b323d852-4804-4814-95e3-50074dce8a4c","text":"[Selection (one or more): [(NESTED PARAMETER) Assignment for sa-04.03_odp.03: system security engineering methods]; [(NESTED PARAMETER) Assignment for sa-04.03_odp.04: privacy engineering methods]]","parameterId":"sa-04.03_odp.02","default":"[Selection (one or more): [(NESTED PARAMETER) Assignment for sa-04.03_odp.03: system security engineering methods]; [(NESTED PARAMETER) Assignment for sa-04.03_odp.04: privacy engineering methods]]"},{"constraints":"","displayName":"","guidance":"","uuid":"81040d39-5286-4431-b030-41dcd591d4e0","text":"system security engineering methods","parameterId":"sa-04.03_odp.03","default":" [Assignment: organization defined system security engineering methods] "},{"constraints":"","displayName":"","guidance":"","uuid":"1b04cac4-ee4f-45b2-b629-10c78235cd26","text":"privacy engineering methods","parameterId":"sa-04.03_odp.04","default":" [Assignment: organization defined privacy engineering methods] "},{"constraints":"","displayName":"","guidance":"","uuid":"4c304ef0-7335-4a06-a42a-eac8135ad927","text":"[Selection (one or more): [(NESTED PARAMETER) Assignment for sa-04.03_odp.06: software development methods]; [(NESTED PARAMETER) Assignment for sa-04.03_odp.07: testing, evaluation, assessment, verification, and validation methods]; [(NESTED PARAMETER) Assignment for sa-04.03_odp.08: quality control processes]]","parameterId":"sa-04.03_odp.05","default":"[Selection (one or more): [(NESTED PARAMETER) Assignment for sa-04.03_odp.06: software development methods]; [(NESTED PARAMETER) Assignment for sa-04.03_odp.07: testing, evaluation, assessment, verification, and validation methods]; [(NESTED PARAMETER) Assignment for sa-04.03_odp.08: quality control processes]]"},{"constraints":"","displayName":"","guidance":"","uuid":"5d4e34d2-3c49-48ca-8d52-723a1c353093","text":"software development methods","parameterId":"sa-04.03_odp.06","default":" [Assignment: organization defined software development methods] "},{"constraints":"","displayName":"","guidance":"","uuid":"52399380-973e-45ed-9cc6-5c6e27a08c7e","text":"testing, evaluation, assessment, verification, and validation methods","parameterId":"sa-04.03_odp.07","default":" [Assignment: organization defined testing, evaluation, assessment, verification, and validation methods] "},{"constraints":"","displayName":"","guidance":"","uuid":"12ac50cc-a176-476e-ba40-c62f7ee23bf2","text":"quality control processes","parameterId":"sa-04.03_odp.08","default":" [Assignment: organization defined quality control processes] "}],"subControls":"","tests":[{"testId":"SA-04(03)(a)","uuid":"296c0ebb-418b-4b2a-b57a-a20b721bb593","test":"Determine if the developer of the system, system component, or system service is required to demonstrate the use of a system development life cycle process that includes [SELECTED PARAMETER VALUE(S): systems engineering methods ];Examples of security configurations include the U.S. Government Configuration Baseline (USGCB), Security Technical Implementation Guides (STIGs), and any limitations on functions, ports, protocols, and services. Security characteristics can include requiring that default passwords have been changed.
","uuid":"9134f092-948c-413a-a05d-d97a5d8287c4","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"ea8351f7-60fa-480f-95bd-73c8832ef9b4","text":"security configurations","parameterId":"sa-04.05_odp","default":" [Assignment: organization defined security configurations] "}],"subControls":"","tests":[{"testId":"SA-04(05)(a)","uuid":"687fbef1-256a-4250-8183-5694fcd35bc9","test":"Determine if the developer of the system, system component, or system service is required to deliver the system, component, or service with [SELECTED PARAMETER VALUE(S): security configurations ] implemented;Commercial off-the-shelf IA or IA-enabled information technology products used to protect classified information by cryptographic means may be required to use NSA-approved key management. See NSA CSFC.
","uuid":"a9c74071-76cb-4fdc-a840-0bdfda9f0722","family":"System and Services Acquisition","parameters":[],"subControls":"","tests":[{"testId":"SA-04(06)(a)","uuid":"18cf449a-65fb-424d-8792-9648b894f41a","test":"Determine if 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 are employed;See NIAP CCEVS for additional information on NIAP. See NIST CMVP for additional information on FIPS-validated cryptographic modules.
","uuid":"6111ff0a-e103-40b4-9dbc-d6f056783121","family":"System and Services Acquisition","parameters":[],"subControls":"","tests":[{"testId":"SA-04(07)(a)","uuid":"5e4bbecc-8f6c-4353-907c-36621bd10f40","test":"Determine if the use of commercially provided information assurance and information assurance-enabled information technology products is limited 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;The objective of continuous monitoring plans is to determine if the planned, required, and deployed controls within the system, system component, or system service continue to be effective over time based on the inevitable changes that occur. Developer continuous monitoring plans include a sufficient level of detail such that the information can be incorporated into continuous monitoring programs implemented by organizations. Continuous monitoring plans can include the types of control assessment and monitoring activities planned, frequency of control monitoring, and actions to be taken when controls fail or become ineffective.
","uuid":"371eec4b-c43a-4d0c-b2f5-2a286bb23719","family":"System and Services Acquisition","parameters":[],"subControls":"","tests":[{"testId":"SA-04(08)","uuid":"f53b83ad-4dc9-4c64-8bb4-c0ac04a299ab","test":"Determine if the developer of the system, system component, or system service is required to produce a plan for the continuous monitoring of control effectiveness that is consistent with the continuous monitoring program of the organization.The identification of functions, ports, protocols, and services early in the system development life cycle (e.g., during the initial requirements definition and design stages) allows organizations to influence the design of the system, system component, or system service. This early involvement in the system development life cycle helps organizations avoid or minimize the use of functions, ports, protocols, or services that pose unnecessarily high risks and understand the trade-offs involved in blocking specific ports, protocols, or services or requiring system service providers to do so. Early identification of functions, ports, protocols, and services avoids costly retrofitting of controls after the system, component, or system service has been implemented. SA-9 describes the requirements for external system services. Organizations identify which functions, ports, protocols, and services are provided from external sources.
","uuid":"191bac60-bb4e-4a05-a5a7-2a0abc73a6bd","family":"System and Services Acquisition","parameters":[],"subControls":"","tests":[{"testId":"SA-04(09)[01]","uuid":"c59ee903-5c1f-436c-9f34-c32e1c6c3d95","test":"Determine if the developer of the system, system component, or system service is required to identify the functions intended for organizational use;Products on the FIPS 201-approved products list meet NIST requirements for Personal Identity Verification (PIV) of Federal Employees and Contractors. PIV cards are used for multi-factor authentication in systems and organizations.
","uuid":"484eed52-53ef-4f43-abdf-9dd736c8a568","family":"System and Services Acquisition","parameters":[],"subControls":"","tests":[{"testId":"SA-04(10)","uuid":"9eb46058-fee7-4530-a434-492b52dcc26f","test":"Determine if only information technology products on the fips 201-approved products list for the personal identity verification (piv) capability implemented within organizational systems are employed.When, by contract, an organization provides for the operation of a system of records to accomplish an organizational mission or function, the organization, consistent with its authority, causes the requirements of the PRIVACT to be applied to the system of records.
","uuid":"5db34e1c-9ce8-41da-887e-f29dce15ec91","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"0b77826d-2aa5-4341-9ef4-ab35afb0b90c","text":"Privacy Act requirements","parameterId":"sa-04.11_odp","default":" [Assignment: organization defined Privacy Act requirements] "}],"subControls":"","tests":[{"testId":"SA-04(11)","uuid":"01a3cd67-f9f0-4a37-825f-cde2412ad6c1","test":"Determine if [SELECTED PARAMETER VALUE(S): Privacy Act requirements ] are defined in the acquisition contract for the operation of a system of records on behalf of an organization to accomplish an organizational mission or function.Contractors who operate a system that contains data owned by an organization initiating the contract have policies and procedures in place to remove the data from their systems and/or return the data in a time frame defined by the contract.
","uuid":"a805e509-ca5d-47f5-ad2a-02896b8eff82","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"d6f2595c-0a88-440f-8863-8948f1e9778d","text":"time frame","parameterId":"sa-04.12_odp","default":" [Assignment: organization defined time frame] "}],"subControls":"","tests":[{"testId":"SA-04(12)(a)","uuid":"b96ba940-5681-4f90-9709-7c1bc7b73ea4","test":"Determine if organizational data ownership requirements are included in the acquisition contract;System documentation helps personnel understand the implementation and operation of controls. Organizations consider establishing specific measures to determine the quality and completeness of the content provided. System documentation may be used to support the management of supply chain risk, incident response, and other functions. Personnel or roles that require documentation include system owners, system security officers, and system administrators. Attempts to obtain documentation include contacting manufacturers or suppliers and conducting web-based searches. The inability to obtain documentation may occur due to the age of the system or component or the lack of support from developers and contractors. When documentation cannot be obtained, organizations may need to recreate the documentation if it is essential to the implementation or operation of the controls. The protection provided for the documentation is commensurate with the security category or classification of the system. Documentation that addresses system vulnerabilities may require an increased level of protection. Secure operation of the system includes initially starting the system and resuming secure system operation after a lapse in system operation.
","uuid":"d5a21c71-6f7d-49bb-9879-19364c76ffd6","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"3d702e7c-d823-4e29-88e6-ebd7c8a5b248","text":"actions","parameterId":"sa-05_odp.01","default":" [Assignment: organization defined actions] "},{"constraints":"","displayName":"","guidance":"","uuid":"d2e53d6a-e154-4b93-9f31-e3724c6e697a","text":"personnel or roles","parameterId":"sa-05_odp.02","default":" [Assignment: organization defined personnel or roles] "}],"subControls":"","tests":[{"testId":"SA-05a.01[01]","uuid":"50224c4c-8785-4d14-9862-8593d2fa091b","test":"Determine if administrator documentation for the system, system component, or system service that describes the secure configuration of the system, component, or service is obtained or developed;Systems security and privacy engineering principles are closely related to and implemented throughout the system development life cycle (see SA-3 ). Organizations can apply systems security and privacy engineering principles to new systems under development or to systems undergoing upgrades. For existing systems, organizations apply systems security and privacy engineering principles to system upgrades and modifications to the extent feasible, given the current state of hardware, software, and firmware components within those systems.
The application of systems security and privacy engineering principles helps organizations develop trustworthy, secure, and resilient systems and reduces the susceptibility to disruptions, hazards, threats, and the creation of privacy problems for individuals. Examples of system security engineering principles include: developing layered protections; establishing security and privacy policies, architecture, and controls as the foundation for design and development; incorporating security and privacy requirements into the system development life cycle; delineating physical and logical security boundaries; ensuring that developers are trained on how to build secure software; tailoring controls to meet organizational needs; and performing threat modeling to identify use cases, threat agents, attack vectors and patterns, design patterns, and compensating controls needed to mitigate risk.
Organizations that apply systems security and privacy engineering concepts and principles can facilitate the development of trustworthy, secure systems, system components, and system services; reduce risk to acceptable levels; and make informed risk management decisions. System security engineering principles can also be used to protect against certain supply chain risks, including incorporating tamper-resistant hardware into a design.
","uuid":"c04121c8-f26c-4b33-9520-4dd6ec58a2e7","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"906c45a3-5038-4a21-844a-a554ec6239b0","text":"organization-defined systems security and privacy engineering principles","parameterId":"sa-8_prm_1","default":" [Assignment: organization-defined systems security and privacy engineering principles] "},{"constraints":"","displayName":"","guidance":"","uuid":"16aea79e-33be-4e3e-945d-8a98394d0f95","text":"systems security engineering principles","parameterId":"sa-08_odp.01","default":" [Assignment: organization defined systems security engineering principles] "},{"constraints":"","displayName":"","guidance":"","uuid":"4f56ccf7-35dc-46b9-a09b-a557175fb874","text":"privacy engineering principles","parameterId":"sa-08_odp.02","default":" [Assignment: organization defined privacy engineering principles] "}],"subControls":"","tests":[{"testId":"SA-08[01]","uuid":"c0511e86-eb32-4751-b315-34761abd0d95","test":"Determine if [SELECTED PARAMETER VALUE(S): systems security engineering principles ] are applied in the specification of the system and system components;The principle of clear abstractions states that a system has simple, well-defined interfaces and functions that provide a consistent and intuitive view of the data and how the data is managed. The clarity, simplicity, necessity, and sufficiency of the system interfaces— combined with a precise definition of their functional behavior—promotes ease of analysis, inspection, and testing as well as the correct and secure use of the system. The clarity of an abstraction is subjective. Examples that reflect the application of this principle include avoidance of redundant, unused interfaces; information hiding; and avoidance of semantic overloading of interfaces or their parameters. Information hiding (i.e., representation-independent programming), is a design discipline used to ensure that the internal representation of information in one system component is not visible to another system component invoking or calling the first component, such that the published abstraction is not influenced by how the data may be managed internally.
","uuid":"814b19ce-9465-48ae-a083-8ccc991db7d7","family":"System and Services Acquisition","parameters":[],"subControls":"","tests":[{"testId":"SA-08(01)","uuid":"c6ece6e5-e2c3-4ca9-becd-a7ae4848280b","test":"Determine if the security design principle of clear abstractions is implemented.The principle of least common mechanism states that the amount of mechanism common to more than one user and depended on by all users is minimized POPEK74 . Mechanism minimization implies that different components of a system refrain from using the same mechanism to access a system resource. Every shared mechanism (especially a mechanism involving shared variables) represents a potential information path between users and is designed with care to ensure that it does not unintentionally compromise security SALTZER75 . Implementing the principle of least common mechanism helps to reduce the adverse consequences of sharing the system state among different programs. A single program that corrupts a shared state (including shared variables) has the potential to corrupt other programs that are dependent on the state. The principle of least common mechanism also supports the principle of simplicity of design and addresses the issue of covert storage channels LAMPSON73.
","uuid":"577811e5-d8bc-4f2e-b2c1-49495a52bd5a","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"020588e9-69cc-46eb-a39a-c50fd8a0a977","text":"systems or system components","parameterId":"sa-08.02_odp","default":" [Assignment: organization defined systems or system components] "}],"subControls":"","tests":[{"testId":"SA-08(02)","uuid":"9e741456-eca4-4a0a-8fa0-f8015e73435d","test":"Determine if [SELECTED PARAMETER VALUE(S): systems or system components ] implement the security design principle of least common mechanism.The principles of modularity and layering are fundamental across system engineering disciplines. Modularity and layering derived from functional decomposition are effective in managing system complexity by making it possible to comprehend the structure of the system. Modular decomposition, or refinement in system design, is challenging and resists general statements of principle. Modularity serves to isolate functions and related data structures into well-defined logical units. Layering allows the relationships of these units to be better understood so that dependencies are clear and undesired complexity can be avoided. The security design principle of modularity extends functional modularity to include considerations based on trust, trustworthiness, privilege, and security policy. Security-informed modular decomposition includes the allocation of policies to systems in a network, separation of system applications into processes with distinct address spaces, allocation of system policies to layers, and separation of processes into subjects with distinct privileges based on hardware-supported privilege domains.
","uuid":"3a005967-7c5a-40bf-9de4-60a5aa2f3323","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"41e69932-d807-4eb2-b70f-fada9c4c5009","text":"organization-defined systems or system components","parameterId":"sa-8.3_prm_1","default":" [Assignment: organization-defined systems or system components] "},{"constraints":"","displayName":"","guidance":"","uuid":"c5ac8db4-4b0c-4eae-88a1-44d6da584b52","text":"systems or system components","parameterId":"sa-08.03_odp.01","default":" [Assignment: organization defined systems or system components] "},{"constraints":"","displayName":"","guidance":"","uuid":"bc50c7c0-8f45-4da4-821f-7e66cb74beac","text":"systems or system components","parameterId":"sa-08.03_odp.02","default":" [Assignment: organization defined systems or system components] "}],"subControls":"","tests":[{"testId":"SA-08(03)[01]","uuid":"e9ca6f73-fb26-4092-95c7-fb67c411244f","test":"Determine if [SELECTED PARAMETER VALUE(S): systems or system components ] implement the security design principle of modularity;The principle of partially ordered dependencies states that the synchronization, calling, and other dependencies in the system are partially ordered. A fundamental concept in system design is layering, whereby the system is organized into well-defined, functionally related modules or components. The layers are linearly ordered with respect to inter-layer dependencies, such that higher layers are dependent on lower layers. While providing functionality to higher layers, some layers can be self-contained and not dependent on lower layers. While a partial ordering of all functions in a given system may not be possible, if circular dependencies are constrained to occur within layers, the inherent problems of circularity can be more easily managed. Partially ordered dependencies and system layering contribute significantly to the simplicity and coherency of the system design. Partially ordered dependencies also facilitate system testing and analysis.
","uuid":"02db75f4-7689-442d-a144-c604b633b3c1","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"e65f0b49-7111-4ae3-854a-4f896a0d3003","text":"systems or system components","parameterId":"sa-08.04_odp","default":" [Assignment: organization defined systems or system components] "}],"subControls":"","tests":[{"testId":"SA-08(04)","uuid":"cc1d4ae2-b588-4ae5-8449-c627d0613915","test":"Determine if [SELECTED PARAMETER VALUE(S): systems or system components ] implement the security design principle of partially ordered dependencies.The principle of efficiently mediated access states that policy enforcement mechanisms utilize the least common mechanism available while satisfying stakeholder requirements within expressed constraints. The mediation of access to system resources (i.e., CPU, memory, devices, communication ports, services, infrastructure, data, and information) is often the predominant security function of secure systems. It also enables the realization of protections for the capability provided to stakeholders by the system. Mediation of resource access can result in performance bottlenecks if the system is not designed correctly. For example, by using hardware mechanisms, efficiently mediated access can be achieved. Once access to a low-level resource such as memory has been obtained, hardware protection mechanisms can ensure that out-of-bounds access does not occur.
","uuid":"d781d8f6-8adf-433d-a4ca-2dadc517e928","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"946eb320-e369-48db-b395-986d99d6b5f3","text":"systems or system components","parameterId":"sa-08.05_odp","default":" [Assignment: organization defined systems or system components] "}],"subControls":"","tests":[{"testId":"SA-08(05)","uuid":"e2a6812e-1498-443c-82fc-58742a0edfc7","test":"Determine if [SELECTED PARAMETER VALUE(S): systems or system components ] implement the security design principle of efficiently mediated access.The principle of minimized sharing states that no computer resource is shared between system components (e.g., subjects, processes, functions) unless it is absolutely necessary to do so. Minimized sharing helps to simplify system design and implementation. In order to protect user-domain resources from arbitrary active entities, no resource is shared unless that sharing has been explicitly requested and granted. The need for resource sharing can be motivated by the design principle of least common mechanism in the case of internal entities or driven by stakeholder requirements. However, internal sharing is carefully designed to avoid performance and covert storage and timing channel problems. Sharing via common mechanism can increase the susceptibility of data and information to unauthorized access, disclosure, use, or modification and can adversely affect the inherent capability provided by the system. To minimize sharing induced by common mechanisms, such mechanisms can be designed to be reentrant or virtualized to preserve separation. Moreover, the use of global data to share information is carefully scrutinized. The lack of encapsulation may obfuscate relationships among the sharing entities.
","uuid":"4ec25cf2-a634-4765-aee1-53520106f279","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"28e20581-7add-4006-becb-946fa8d38409","text":"systems or system components","parameterId":"sa-08.06_odp","default":" [Assignment: organization defined systems or system components] "}],"subControls":"","tests":[{"testId":"SA-08(06)","uuid":"8d9ff71b-19e9-4253-b338-7695e79a9452","test":"Determine if [SELECTED PARAMETER VALUE(S): systems or system components ] implement the security design principle of minimized sharing.The principle of reduced complexity states that the system design is as simple and small as possible. A small and simple design is more understandable, more analyzable, and less prone to error. The reduced complexity principle applies to any aspect of a system, but it has particular importance for security due to the various analyses performed to obtain evidence about the emergent security property of the system. For such analyses to be successful, a small and simple design is essential. Application of the principle of reduced complexity contributes to the ability of system developers to understand the correctness and completeness of system security functions. It also facilitates the identification of potential vulnerabilities. The corollary of reduced complexity states that the simplicity of the system is directly related to the number of vulnerabilities it will contain; that is, simpler systems contain fewer vulnerabilities. An benefit of reduced complexity is that it is easier to understand whether the intended security policy has been captured in the system design and that fewer vulnerabilities are likely to be introduced during engineering development. An additional benefit is that any such conclusion about correctness, completeness, and the existence of vulnerabilities can be reached with a higher degree of assurance in contrast to conclusions reached in situations where the system design is inherently more complex. Transitioning from older technologies to newer technologies (e.g., transitioning from IPv4 to IPv6) may require implementing the older and newer technologies simultaneously during the transition period. This may result in a temporary increase in system complexity during the transition.
","uuid":"ad54d31f-da52-441b-a71f-b7c5c390755e","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"dc3c52ee-9450-4eef-9c9f-e4d75691cc77","text":"systems or system components","parameterId":"sa-08.07_odp","default":" [Assignment: organization defined systems or system components] "}],"subControls":"","tests":[{"testId":"SA-08(07)","uuid":"c2d02900-94c8-4e89-9afa-cf4b46717278","test":"Determine if [SELECTED PARAMETER VALUE(S): systems or system components ] implement the security design principle of reduced complexity.The principle of secure evolvability states that a system is developed to facilitate the maintenance of its security properties when there are changes to the system’s structure, interfaces, interconnections (i.e., system architecture), functionality, or configuration (i.e., security policy enforcement). Changes include a new, enhanced, or upgraded system capability; maintenance and sustainment activities; and reconfiguration. Although it is not possible to plan for every aspect of system evolution, system upgrades and changes can be anticipated by analyses of mission or business strategic direction, anticipated changes in the threat environment, and anticipated maintenance and sustainment needs. It is unrealistic to expect that complex systems remain secure in contexts not envisioned during development, whether such contexts are related to the operational environment or to usage. A system may be secure in some new contexts, but there is no guarantee that its emergent behavior will always be secure. It is easier to build trustworthiness into a system from the outset, and it follows that the sustainment of system trustworthiness requires planning for change as opposed to adapting in an ad hoc or non-methodical manner. The benefits of this principle include reduced vendor life cycle costs, reduced cost of ownership, improved system security, more effective management of security risk, and less risk uncertainty.
","uuid":"2efd2b6e-d4ab-455d-bb9a-01bd4749d9b3","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"08723b52-6871-4cce-ac2d-4c9934ea94a3","text":"systems or system components","parameterId":"sa-08.08_odp","default":" [Assignment: organization defined systems or system components] "}],"subControls":"","tests":[{"testId":"SA-08(08)","uuid":"46bb54bd-e964-4f22-b0fc-e4e7d2acd5ac","test":"Determine if [SELECTED PARAMETER VALUE(S): systems or system components ] implement the security design principle of secure evolvability.The principle of trusted components states that a component is trustworthy to at least a level commensurate with the security dependencies it supports (i.e., how much it is trusted to perform its security functions by other components). This principle enables the composition of components such that trustworthiness is not inadvertently diminished and the trust is not consequently misplaced. Ultimately, this principle demands some metric by which the trust in a component and the trustworthiness of a component can be measured on the same abstract scale. The principle of trusted components is particularly relevant when considering systems and components in which there are complex chains of trust dependencies. A trust dependency is also referred to as a trust relationship and there may be chains of trust relationships.
The principle of trusted components also applies to a compound component that consists of subcomponents (e.g., a subsystem), which may have varying levels of trustworthiness. The conservative assumption is that the trustworthiness of a compound component is that of its least trustworthy subcomponent. It may be possible to provide a security engineering rationale that the trustworthiness of a particular compound component is greater than the conservative assumption. However, any such rationale reflects logical reasoning based on a clear statement of the trustworthiness objectives as well as relevant and credible evidence. The trustworthiness of a compound component is not the same as increased application of defense-in-depth layering within the component or a replication of components. Defense-in-depth techniques do not increase the trustworthiness of the whole above that of the least trustworthy component.
","uuid":"7447782b-3ec4-4f3f-aa45-a0a4f35885d0","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"d291a763-6eeb-450d-a533-3511f94df93c","text":"systems or system components","parameterId":"sa-08.09_odp","default":" [Assignment: organization defined systems or system components] "}],"subControls":"","tests":[{"testId":"SA-08(09)","uuid":"d647dac0-7d67-48e7-905f-84a21a8087ba","test":"Determine if [SELECTED PARAMETER VALUE(S): systems or system components ] implement the security design principle of trusted components.The principle of hierarchical trust for components builds on the principle of trusted components and states that the security dependencies in a system will form a partial ordering if they preserve the principle of trusted components. The partial ordering provides the basis for trustworthiness reasoning or an assurance case (assurance argument) when composing a secure system from heterogeneously trustworthy components. To analyze a system composed of heterogeneously trustworthy components for its trustworthiness, it is essential to eliminate circular dependencies with regard to the trustworthiness. If a more trustworthy component located in a lower layer of the system were to depend on a less trustworthy component in a higher layer, this would, in effect, put the components in the same less trustworthy
equivalence class per the principle of trusted components. Trust relationships, or chains of trust, can have various manifestations. For example, the root certificate of a certificate hierarchy is the most trusted node in the hierarchy, whereas the leaves in the hierarchy may be the least trustworthy nodes. Another example occurs in a layered high-assurance system where the security kernel (including the hardware base), which is located at the lowest layer of the system, is the most trustworthy component. The principle of hierarchical trust, however, does not prohibit the use of overly trustworthy components. There may be cases in a system of low trustworthiness where it is reasonable to employ a highly trustworthy component rather than one that is less trustworthy (e.g., due to availability or other cost-benefit driver). For such a case, any dependency of the highly trustworthy component upon a less trustworthy component does not degrade the trustworthiness of the resulting low-trust system.
The principle of inverse modification threshold builds on the principle of trusted components and the principle of hierarchical trust and states that the degree of protection provided to a component is commensurate with its trustworthiness. As the trust placed in a component increases, the protection against unauthorized modification of the component also increases to the same degree. Protection from unauthorized modification can come in the form of the component’s own self-protection and innate trustworthiness, or it can come from the protections afforded to the component from other elements or attributes of the security architecture (to include protections in the environment of operation).
","uuid":"519763f8-c0ab-423d-8d6c-8191e802df80","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"71276a5e-b4bc-498d-ad86-93eab02a71a3","text":"systems or system components","parameterId":"sa-08.11_odp","default":" [Assignment: organization defined systems or system components] "}],"subControls":"","tests":[{"testId":"SA-08(11)","uuid":"b1f23b84-e111-49db-be64-c541076d9e4b","test":"Determine if [SELECTED PARAMETER VALUE(S): systems or system components ] implement the security design principle of inverse modification threshold.The principle of hierarchical protection states that a component need not be protected from more trustworthy components. In the degenerate case of the most trusted component, it protects itself from all other components. For example, if an operating system kernel is deemed the most trustworthy component in a system, then it protects itself from all untrusted applications it supports, but the applications, conversely, do not need to protect themselves from the kernel. The trustworthiness of users is a consideration for applying the principle of hierarchical protection. A trusted system need not protect itself from an equally trustworthy user, reflecting use of untrusted systems in system high
environments where users are highly trustworthy and where other protections are put in place to bound and protect the system high
execution environment.
The principle of minimized security elements states that the system does not have extraneous trusted components. The principle of minimized security elements has two aspects: the overall cost of security analysis and the complexity of security analysis. Trusted components are generally costlier to construct and implement, owing to the increased rigor of development processes. Trusted components require greater security analysis to qualify their trustworthiness. Thus, to reduce the cost and decrease the complexity of the security analysis, a system contains as few trustworthy components as possible. The analysis of the interaction of trusted components with other components of the system is one of the most important aspects of system security verification. If the interactions between components are unnecessarily complex, the security of the system will also be more difficult to ascertain than one whose internal trust relationships are simple and elegantly constructed. In general, fewer trusted components result in fewer internal trust relationships and a simpler system.
","uuid":"b7084907-0eb0-46a1-a642-e3b9b8cd2239","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"140eb679-4bee-42f6-b364-e8c8a380f0a1","text":"systems or system components","parameterId":"sa-08.13_odp","default":" [Assignment: organization defined systems or system components] "}],"subControls":"","tests":[{"testId":"SA-08(13)","uuid":"cb412a56-824b-4280-a26e-69790abad7a5","test":"Determine if [SELECTED PARAMETER VALUE(S): systems or system components ] implement the security design principle of minimized security elements.The principle of least privilege states that each system component is allocated sufficient privileges to accomplish its specified functions but no more. Applying the principle of least privilege limits the scope of the component’s actions, which has two desirable effects: the security impact of a failure, corruption, or misuse of the component will have a minimized security impact, and the security analysis of the component will be simplified. Least privilege is a pervasive principle that is reflected in all aspects of the secure system design. Interfaces used to invoke component capability are available to only certain subsets of the user population, and component design supports a sufficiently fine granularity of privilege decomposition. For example, in the case of an audit mechanism, there may be an interface for the audit manager, who configures the audit settings; an interface for the audit operator, who ensures that audit data is safely collected and stored; and, finally, yet another interface for the audit reviewer, who only has need to view the audit data that has been collected but no need to perform operations on that data.
In addition to its manifestations at the system interface, least privilege can be used as a guiding principle for the internal structure of the system itself. One aspect of internal least privilege is to construct modules so that only the elements encapsulated by the module are directly operated on by the functions within the module. Elements external to a module that may be affected by the module’s operation are indirectly accessed through interaction (e.g., via a function call) with the module that contains those elements. Another aspect of internal least privilege is that the scope of a given module or component includes only those system elements that are necessary for its functionality and that the access modes for the elements (e.g., read, write) are minimal.
","uuid":"f34f4f09-9c7a-48ca-8ca8-477ede5fba05","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"ae74a325-ef32-4a30-a47c-4c16788ab31d","text":"systems or system components","parameterId":"sa-08.14_odp","default":" [Assignment: organization defined systems or system components] "}],"subControls":"","tests":[{"testId":"SA-08(14)","uuid":"2d0873fa-a84d-4a63-926c-4871402d7745","test":"Determine if [SELECTED PARAMETER VALUE(S): systems or system components ] implement the security design principle of least privilege.The principle of predicate permission states that system designers consider requiring multiple authorized entities to provide consent before a highly critical operation or access to highly sensitive data, information, or resources is allowed to proceed. SALTZER75 originally named predicate permission the separation of privilege. It is also equivalent to separation of duty. The division of privilege among multiple parties decreases the likelihood of abuse and provides the safeguard that no single accident, deception, or breach of trust is sufficient to enable an unrecoverable action that can lead to significantly damaging effects. The design options for such a mechanism may require simultaneous action (e.g., the firing of a nuclear weapon requires two different authorized individuals to give the correct command within a small time window) or a sequence of operations where each successive action is enabled by some prior action, but no single individual is able to enable more than one action.
","uuid":"359393fd-f3ec-4596-bf59-b917c51da831","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"4a81fc07-dadf-400a-99fb-e377977249b2","text":"systems or system components","parameterId":"sa-08.15_odp","default":" [Assignment: organization defined systems or system components] "}],"subControls":"","tests":[{"testId":"SA-08(15)","uuid":"57edc327-9c33-432a-918b-c18b298222d5","test":"Determine if [SELECTED PARAMETER VALUE(S): systems or system components ] implement the security design principle of predicate permission.The principle of self-reliant trustworthiness states that systems minimize their reliance on other systems for their own trustworthiness. A system is trustworthy by default, and any connection to an external entity is used to supplement its function. If a system were required to maintain a connection with another external entity in order to maintain its trustworthiness, then that system would be vulnerable to malicious and non-malicious threats that could result in the loss or degradation of that connection. The benefit of the principle of self-reliant trustworthiness is that the isolation of a system will make it less vulnerable to attack. A corollary to this principle relates to the ability of the system (or system component) to operate in isolation and then resynchronize with other components when it is rejoined with them.
","uuid":"f328092b-bba4-4d30-af83-46f9182b0500","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"399a2823-f6c2-4ae4-adfc-352258d06b81","text":"systems or system components","parameterId":"sa-08.16_odp","default":" [Assignment: organization defined systems or system components] "}],"subControls":"","tests":[{"testId":"SA-08(16)","uuid":"47710349-7093-4134-b2bc-0743fb4efc3e","test":"Determine if [SELECTED PARAMETER VALUE(S): systems or system components ] implement the security design principle of self-reliant trustworthiness.The principle of secure distributed composition states that the composition of distributed components that enforce the same system security policy result in a system that enforces that policy at least as well as the individual components do. Many of the design principles for secure systems deal with how components can or should interact. The need to create or enable a capability from the composition of distributed components can magnify the relevancy of these principles. In particular, the translation of security policy from a stand-alone to a distributed system or a system-of-systems can have unexpected or emergent results. Communication protocols and distributed data consistency mechanisms help to ensure consistent policy enforcement across a distributed system. To ensure a system-wide level of assurance of correct policy enforcement, the security architecture of a distributed composite system is thoroughly analyzed.
","uuid":"58e8be43-53cb-4229-981d-f64c1aee7a80","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"24cf478c-7175-4ba9-8050-39b735f05af3","text":"systems or system components","parameterId":"sa-08.17_odp","default":" [Assignment: organization defined systems or system components] "}],"subControls":"","tests":[{"testId":"SA-08(17)","uuid":"b803c8b1-b1aa-496f-8121-66e287278a6c","test":"Determine if [SELECTED PARAMETER VALUE(S): systems or system components ] implement the security design principle of secure distributed composition.The principle of trusted communication channels states that when composing a system where there is a potential threat to communications between components (i.e., the interconnections between components), each communication channel is trustworthy to a level commensurate with the security dependencies it supports (i.e., how much it is trusted by other components to perform its security functions). Trusted communication channels are achieved by a combination of restricting access to the communication channel (to ensure an acceptable match in the trustworthiness of the endpoints involved in the communication) and employing end-to-end protections for the data transmitted over the communication channel (to protect against interception and modification and to further increase the assurance of proper end-to-end communication).
","uuid":"7ab20d2c-b678-48d9-b4bb-30c81680fe3a","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"cfbe8215-bcb3-4f96-bca1-6a95c42d008b","text":"systems or system components","parameterId":"sa-08.18_odp","default":" [Assignment: organization defined systems or system components] "}],"subControls":"","tests":[{"testId":"SA-08(18)","uuid":"55ef8383-72dd-4508-981a-b568afe12c4e","test":"Determine if [SELECTED PARAMETER VALUE(S): systems or system components ] implement the security design principle of trusted communications channels.The principle of continuous protection states that components and data used to enforce the security policy have uninterrupted protection that is consistent with the security policy and the security architecture assumptions. No assurances that the system can provide the confidentiality, integrity, availability, and privacy protections for its design capability can be made if there are gaps in the protection. Any assurances about the ability to secure a delivered capability require that data and information are continuously protected. That is, there are no periods during which data and information are left unprotected while under control of the system (i.e., during the creation, storage, processing, or communication of the data and information, as well as during system initialization, execution, failure, interruption, and shutdown). Continuous protection requires adherence to the precepts of the reference monitor concept (i.e., every request is validated by the reference monitor; the reference monitor is able to protect itself from tampering; and sufficient assurance of the correctness and completeness of the mechanism can be ascertained from analysis and testing) and the principle of secure failure and recovery (i.e., preservation of a secure state during error, fault, failure, and successful attack; preservation of a secure state during recovery to normal, degraded, or alternative operational modes).
Continuous protection also applies to systems designed to operate in varying configurations, including those that deliver full operational capability and degraded-mode configurations that deliver partial operational capability. The continuous protection principle requires that changes to the system security policies be traceable to the operational need that drives the configuration and be verifiable (i.e., it is possible to verify that the proposed changes will not put the system into an insecure state). Insufficient traceability and verification may lead to inconsistent states or protection discontinuities due to the complex or undecidable nature of the problem. The use of pre-verified configuration definitions that reflect the new security policy enables analysis to determine that a transition from old to new policies is essentially atomic and that any residual effects from the old policy are guaranteed to not conflict with the new policy. The ability to demonstrate continuous protection is rooted in the clear articulation of life cycle protection needs as stakeholder security requirements.
","uuid":"df8d1844-68d1-486d-8ea0-5e31c4bd095a","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"4feff3ea-3ef6-4d52-a8d9-5600e42b61c3","text":"systems or system components","parameterId":"sa-08.19_odp","default":" [Assignment: organization defined systems or system components] "}],"subControls":"","tests":[{"testId":"SA-08(19)","uuid":"c0d66c73-94ca-40f5-bdf2-3f2a4ebc6fbe","test":"Determine if [SELECTED PARAMETER VALUE(S): systems or system components ] implement the security design principle of continuous protection.The principle of secure metadata management states that metadata are first class
objects with respect to security policy when the policy requires either complete protection of information or that the security subsystem be self-protecting. The principle of secure metadata management is driven by the recognition that a system, subsystem, or component cannot achieve self-protection unless it protects the data it relies on for correct execution. Data is generally not interpreted by the system that stores it. It may have semantic value (i.e., it comprises information) to users and programs that process the data. In contrast, metadata is information about data, such as a file name or the date when the file was created. Metadata is bound to the target data that it describes in a way that the system can interpret, but it need not be stored inside of or proximate to its target data. There may be metadata whose target is itself metadata (e.g., the classification level or impact level of a file name), including self-referential metadata.
The apparent secondary nature of metadata can lead to neglect of its legitimate need for protection, resulting in a violation of the security policy that includes the exfiltration of information. A particular concern associated with insufficient protections for metadata is associated with multilevel secure (MLS) systems. MLS systems mediate access by a subject to an object based on relative sensitivity levels. It follows that all subjects and objects in the scope of control of the MLS system are either directly labeled or indirectly attributed with sensitivity levels. The corollary of labeled metadata for MLS systems states that objects containing metadata are labeled. As with protection needs assessments for data, attention is given to ensure that the confidentiality and integrity protections are individually assessed, specified, and allocated to metadata, as would be done for mission, business, and system data.
","uuid":"7947c226-23da-4dda-a201-b9843db10608","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"e08c8999-bb0d-4855-9b8b-e11258c41b5e","text":"systems or system components","parameterId":"sa-08.20_odp","default":" [Assignment: organization defined systems or system components] "}],"subControls":"","tests":[{"testId":"SA-08(20)","uuid":"ff2d9559-c1b0-4e61-8dfd-e383fd68a1a6","test":"Determine if [SELECTED PARAMETER VALUE(S): systems or system components ] implement the security design principle of secure metadata management.The principle of self-analysis states that a system component is able to assess its internal state and functionality to a limited extent at various stages of execution, and that this self-analysis capability is commensurate with the level of trustworthiness invested in the system. At the system level, self-analysis can be achieved through hierarchical assessments of trustworthiness established in a bottom-up fashion. In this approach, the lower-level components check for data integrity and correct functionality (to a limited extent) of higher-level components. For example, trusted boot sequences involve a trusted lower-level component that attests to the trustworthiness of the next higher-level components so that a transitive chain of trust can be established. At the root, a component attests to itself, which usually involves an axiomatic or environmentally enforced assumption about its integrity. Results of the self-analyses can be used to guard against externally induced errors, internal malfunction, or transient errors. By following this principle, some simple malfunctions or errors can be detected without allowing the effects of the error or malfunction to propagate outside of the component. Further, the self-test can be used to attest to the configuration of the component, detecting any potential conflicts in configuration with respect to the expected configuration.
","uuid":"ec04fe6c-d106-4cad-ba9e-f4410f7d35e1","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"3c4742fa-483f-46f9-ba70-8821afc5789a","text":"systems or system components","parameterId":"sa-08.21_odp","default":" [Assignment: organization defined systems or system components] "}],"subControls":"","tests":[{"testId":"SA-08(21)","uuid":"623ce5de-116d-4d04-aaab-7a3dfeaf284d","test":"Determine if [SELECTED PARAMETER VALUE(S): systems or system components ] implement the security design principle of self-analysis.The principle of accountability and traceability states that it is possible to trace security-relevant actions (i.e., subject-object interactions) to the entity on whose behalf the action is being taken. The principle of accountability and traceability requires a trustworthy infrastructure that can record details about actions that affect system security (e.g., an audit subsystem). To record the details about actions, the system is able to uniquely identify the entity on whose behalf the action is being carried out and also record the relevant sequence of actions that are carried out. The accountability policy also requires that audit trail itself be protected from unauthorized access and modification. The principle of least privilege assists in tracing the actions to particular entities, as it increases the granularity of accountability. Associating specific actions with system entities, and ultimately with users, and making the audit trail secure against unauthorized access and modifications provide non-repudiation because once an action is recorded, it is not possible to change the audit trail. Another important function that accountability and traceability serves is in the routine and forensic analysis of events associated with the violation of security policy. Analysis of audit logs may provide additional information that may be helpful in determining the path or component that allowed the violation of the security policy and the actions of individuals associated with the violation of the security policy.
","uuid":"e381e87e-209b-487e-9ce9-1caa38e96498","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"814b13d4-c4a5-4c0e-9003-59c1068a8ed6","text":"organization-defined systems or system components","parameterId":"sa-8.22_prm_1","default":" [Assignment: organization-defined systems or system components] "},{"constraints":"","displayName":"","guidance":"","uuid":"5eb8a6f4-ba15-463f-9d49-e4faf4ea5421","text":"systems or system components","parameterId":"sa-08.22_odp.01","default":" [Assignment: organization defined systems or system components] "},{"constraints":"","displayName":"","guidance":"","uuid":"075c8cce-2850-4cf8-b14c-0e733e0977da","text":"systems or system components","parameterId":"sa-08.22_odp.02","default":" [Assignment: organization defined systems or system components] "}],"subControls":"","tests":[{"testId":"SA-08(22)[01]","uuid":"3a58a916-e744-498d-8271-b6c96f89d741","test":"Determine if [SELECTED PARAMETER VALUE(S): systems or system components ] implement the security design principle of accountability;The principle of secure defaults states that the default configuration of a system (including its constituent subsystems, components, and mechanisms) reflects a restrictive and conservative enforcement of security policy. The principle of secure defaults applies to the initial (i.e., default) configuration of a system as well as to the security engineering and design of access control and other security functions that follow a deny unless explicitly authorized
strategy. The initial configuration aspect of this principle requires that any as shipped
configuration of a system, subsystem, or system component does not aid in the violation of the security policy and can prevent the system from operating in the default configuration for those cases where the security policy itself requires configuration by the operational user.
Restrictive defaults mean that the system will operate as-shipped
with adequate self-protection and be able to prevent security breaches before the intended security policy and system configuration is established. In cases where the protection provided by the as-shipped
product is inadequate, stakeholders assess the risk of using it prior to establishing a secure initial state. Adherence to the principle of secure defaults guarantees that a system is established in a secure state upon successfully completing initialization. In situations where the system fails to complete initialization, either it will perform a requested operation using secure defaults or it will not perform the operation. Refer to the principles of continuous protection and secure failure and recovery that parallel this principle to provide the ability to detect and recover from failure.
The security engineering approach to this principle states that security mechanisms deny requests unless the request is found to be well-formed and consistent with the security policy. The insecure alternative is to allow a request unless it is shown to be inconsistent with the policy. In a large system, the conditions that are satisfied to grant a request that is denied by default are often far more compact and complete than those that would need to be checked in order to deny a request that is granted by default.
","uuid":"fbadd4b4-56bd-4972-80af-6d42439acbe0","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"0e57d521-39ca-4625-8feb-2558eddfa431","text":"systems or system components","parameterId":"sa-08.23_odp","default":" [Assignment: organization defined systems or system components] "}],"subControls":"","tests":[{"testId":"SA-08(23)","uuid":"057c5b46-49b0-4bad-97d0-1a01630ff698","test":"Determine if [SELECTED PARAMETER VALUE(S): systems or system components ] implement the security design principle of secure defaults.The principle of secure failure and recovery states that neither a failure in a system function or mechanism nor any recovery action in response to failure leads to a violation of security policy. The principle of secure failure and recovery parallels the principle of continuous protection to ensure that a system is capable of detecting (within limits) actual and impending failure at any stage of its operation (i.e., initialization, normal operation, shutdown, and maintenance) and to take appropriate steps to ensure that security policies are not violated. In addition, when specified, the system is capable of recovering from impending or actual failure to resume normal, degraded, or alternative secure operations while ensuring that a secure state is maintained such that security policies are not violated.
Failure is a condition in which the behavior of a component deviates from its specified or expected behavior for an explicitly documented input. Once a failed security function is detected, the system may reconfigure itself to circumvent the failed component while maintaining security and provide all or part of the functionality of the original system, or it may completely shut itself down to prevent any further violation of security policies. For this to occur, the reconfiguration functions of the system are designed to ensure continuous enforcement of security policy during the various phases of reconfiguration.
Another technique that can be used to recover from failures is to perform a rollback to a secure state (which may be the initial state) and then either shutdown or replace the service or component that failed such that secure operations may resume. Failure of a component may or may not be detectable to the components using it. The principle of secure failure indicates that components fail in a state that denies rather than grants access. For example, a nominally atomic
operation interrupted before completion does not violate security policy and is designed to handle interruption events by employing higher-level atomicity and rollback mechanisms (e.g., transactions). If a service is being used, its atomicity properties are well-documented and characterized so that the component availing itself of that service can detect and handle interruption events appropriately. For example, a system is designed to gracefully respond to disconnection and support resynchronization and data consistency after disconnection.
Failure protection strategies that employ replication of policy enforcement mechanisms, sometimes called defense in depth, can allow the system to continue in a secure state even when one mechanism has failed to protect the system. If the mechanisms are similar, however, the additional protection may be illusory, as the adversary can simply attack in series. Similarly, in a networked system, breaking the security on one system or service may enable an attacker to do the same on other similar replicated systems and services. By employing multiple protection mechanisms whose features are significantly different, the possibility of attack replication or repetition can be reduced. Analyses are conducted to weigh the costs and benefits of such redundancy techniques against increased resource usage and adverse effects on the overall system performance. Additional analyses are conducted as the complexity of these mechanisms increases, as could be the case for dynamic behaviors. Increased complexity generally reduces trustworthiness. When a resource cannot be continuously protected, it is critical to detect and repair any security breaches before the resource is once again used in a secure context.
","uuid":"725e5bd8-4151-4c45-9d40-cad57ebf2932","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"fb9f1a46-330b-4428-b063-8872e6e8bbac","text":"organization-defined systems or system components","parameterId":"sa-8.24_prm_1","default":" [Assignment: organization-defined systems or system components] "},{"constraints":"","displayName":"","guidance":"","uuid":"3e8f2043-1656-47d9-8758-3358c2474171","text":"systems or system components","parameterId":"sa-08.24_odp.01","default":" [Assignment: organization defined systems or system components] "},{"constraints":"","displayName":"","guidance":"","uuid":"95b40839-7c2b-4313-8562-c4a9d9500533","text":"systems or system components","parameterId":"sa-08.24_odp.02","default":" [Assignment: organization defined systems or system components] "}],"subControls":"","tests":[{"testId":"SA-08(24)[01]","uuid":"a336aca0-32ac-47f7-82ce-63a35b86a524","test":"Determine if [SELECTED PARAMETER VALUE(S): systems or system components ] implement the security design principle of secure failure;The principle of economic security states that security mechanisms are not costlier than the potential damage that could occur from a security breach. This is the security-relevant form of the cost-benefit analyses used in risk management. The cost assumptions of cost-benefit analysis prevent the system designer from incorporating security mechanisms of greater strength than necessary, where strength of mechanism is proportional to cost. The principle of economic security also requires analysis of the benefits of assurance relative to the cost of that assurance in terms of the effort expended to obtain relevant and credible evidence as well as the necessary analyses to assess and draw trustworthiness and risk conclusions from the evidence.
","uuid":"a0977497-5940-4047-8203-3e2fa581dc61","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"66dc8e34-64f0-4713-92a4-b9a5fb0dd208","text":"systems or system components","parameterId":"sa-08.25_odp","default":" [Assignment: organization defined systems or system components] "}],"subControls":"","tests":[{"testId":"SA-08(25)","uuid":"4aa23bdb-0474-4969-a8cb-233414d77caf","test":"Determine if [SELECTED PARAMETER VALUE(S): systems or system components ] implement the security design principle of economic security.The principle of performance security states that security mechanisms are constructed so that they do not degrade system performance unnecessarily. Stakeholder and system design requirements for performance and security are precisely articulated and prioritized. For the system implementation to meet its design requirements and be found acceptable to stakeholders (i.e., validation against stakeholder requirements), the designers adhere to the specified constraints that capability performance needs place on protection needs. The overall impact of computationally intensive security services (e.g., cryptography) are assessed and demonstrated to pose no significant impact to higher-priority performance considerations or are deemed to provide an acceptable trade-off of performance for trustworthy protection. The trade-off considerations include less computationally intensive security services unless they are unavailable or insufficient. The insufficiency of a security service is determined by functional capability and strength of mechanism. The strength of mechanism is selected with respect to security requirements, performance-critical overhead issues (e.g., cryptographic key management), and an assessment of the capability of the threat.
The principle of performance security leads to the incorporation of features that help in the enforcement of security policy but incur minimum overhead, such as low-level hardware mechanisms upon which higher-level services can be built. Such low-level mechanisms are usually very specific, have very limited functionality, and are optimized for performance. For example, once access rights to a portion of memory is granted, many systems use hardware mechanisms to ensure that all further accesses involve the correct memory address and access mode. Application of this principle reinforces the need to design security into the system from the ground up and to incorporate simple mechanisms at the lower layers that can be used as building blocks for higher-level mechanisms.
","uuid":"28dfe021-4125-4693-beed-ec42b7c3531a","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"a641e246-3577-4c3a-b27e-400b2af121b8","text":"systems or system components","parameterId":"sa-08.26_odp","default":" [Assignment: organization defined systems or system components] "}],"subControls":"","tests":[{"testId":"SA-08(26)","uuid":"96c44d1c-140f-44ec-bf39-63a025aba9e7","test":"Determine if [SELECTED PARAMETER VALUE(S): systems or system components ] implement the security design principle of performance security.The principle of human factored security states that the user interface for security functions and supporting services is intuitive, user-friendly, and provides feedback for user actions that affect such policy and its enforcement. The mechanisms that enforce security policy are not intrusive to the user and are designed not to degrade user efficiency. Security policy enforcement mechanisms also provide the user with meaningful, clear, and relevant feedback and warnings when insecure choices are being made. Particular attention is given to interfaces through which personnel responsible for system administration and operation configure and set up the security policies. Ideally, these personnel are able to understand the impact of their choices. Personnel with system administrative and operational responsibilities are able to configure systems before start-up and administer them during runtime with confidence that their intent is correctly mapped to the system’s mechanisms. Security services, functions, and mechanisms do not impede or unnecessarily complicate the intended use of the system. There is a trade-off between system usability and the strictness necessary for security policy enforcement. If security mechanisms are frustrating or difficult to use, then users may disable them, avoid them, or use them in ways inconsistent with the security requirements and protection needs that the mechanisms were designed to satisfy.
","uuid":"31206971-79e5-4c65-92a7-cd6afac45f87","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"3257aec5-35dd-4ee4-9472-ddaabafcf719","text":"systems or system components","parameterId":"sa-08.27_odp","default":" [Assignment: organization defined systems or system components] "}],"subControls":"","tests":[{"testId":"SA-08(27)","uuid":"39b3151f-ee85-4ed0-9ee2-11b19d00fd60","test":"Determine if [SELECTED PARAMETER VALUE(S): systems or system components ] implement the security design principle of human factored security.The principle of acceptable security requires that the level of privacy and performance that the system provides is consistent with the users’ expectations. The perception of personal privacy may affect user behavior, morale, and effectiveness. Based on the organizational privacy policy and the system design, users should be able to restrict their actions to protect their privacy. When systems fail to provide intuitive interfaces or meet privacy and performance expectations, users may either choose to completely avoid the system or use it in ways that may be inefficient or even insecure.
","uuid":"dee22d11-b582-4ddf-b322-bf4232c868dd","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"55025a1b-6bb2-4b35-a960-742a7d4a9649","text":"systems or system components","parameterId":"sa-08.28_odp","default":" [Assignment: organization defined systems or system components] "}],"subControls":"","tests":[{"testId":"SA-08(28)","uuid":"cb69a220-aaba-421e-beab-034a919371f8","test":"Determine if [SELECTED PARAMETER VALUE(S): systems or system components ] implement the security design principle of acceptable security.The principle of repeatable and documented procedures states that the techniques and methods employed to construct a system component permit the same component to be completely and correctly reconstructed at a later time. Repeatable and documented procedures support the development of a component that is identical to the component created earlier, which may be in widespread use. In the case of other system artifacts (e.g., documentation and testing results), repeatability supports consistency and the ability to inspect the artifacts. Repeatable and documented procedures can be introduced at various stages within the system development life cycle and contribute to the ability to evaluate assurance claims for the system. Examples include systematic procedures for code development and review, procedures for the configuration management of development tools and system artifacts, and procedures for system delivery.
","uuid":"901f301b-3a2a-410e-921d-26ea241fbda1","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"6b1ae30d-778f-4daf-98e2-59d3fee1fe49","text":"systems or system components","parameterId":"sa-08.29_odp","default":" [Assignment: organization defined systems or system components] "}],"subControls":"","tests":[{"testId":"SA-08(29)","uuid":"79856f66-53ea-41d8-9558-8abb032d7384","test":"Determine if [SELECTED PARAMETER VALUE(S): systems or system components ] implement the security design principle of repeatable and documented procedures.The principle of procedural rigor states that the rigor of a system life cycle process is commensurate with its intended trustworthiness. Procedural rigor defines the scope, depth, and detail of the system life cycle procedures. Rigorous system life cycle procedures contribute to the assurance that the system is correct and free of unintended functionality in several ways. First, the procedures impose checks and balances on the life cycle process such that the introduction of unspecified functionality is prevented.
Second, rigorous procedures applied to systems security engineering activities that produce specifications and other system design documents contribute to the ability to understand the system as it has been built rather than trusting that the component, as implemented, is the authoritative (and potentially misleading) specification.
Finally, modifications to an existing system component are easier when there are detailed specifications that describe its current design instead of studying source code or schematics to try to understand how it works. Procedural rigor helps ensure that security functional and assurance requirements have been satisfied, and it contributes to a better-informed basis for the determination of trustworthiness and risk posture. Procedural rigor is commensurate with the degree of assurance desired for the system. If the required trustworthiness of the system is low, a high level of procedural rigor may add unnecessary cost, whereas when high trustworthiness is critical, the cost of high procedural rigor is merited.
","uuid":"c8baacab-62e0-436c-968c-4e2fed2d12c9","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"734a153b-aeba-47e3-b651-110c9e1f95b8","text":"systems or system components","parameterId":"sa-08.30_odp","default":" [Assignment: organization defined systems or system components] "}],"subControls":"","tests":[{"testId":"SA-08(30)","uuid":"0e652165-5c1c-49d8-9b80-ddb8dcfac716","test":"Determine if [SELECTED PARAMETER VALUE(S): systems or system components ] implement the security design principle of procedural rigor.The principle of secure system modification states that system modification maintains system security with respect to the security requirements and risk tolerance of stakeholders. Upgrades or modifications to systems can transform secure systems into systems that are not secure. The procedures for system modification ensure that if the system is to maintain its trustworthiness, the same rigor that was applied to its initial development is applied to any system changes. Because modifications can affect the ability of the system to maintain its secure state, a careful security analysis of the modification is needed prior to its implementation and deployment. This principle parallels the principle of secure evolvability.
","uuid":"b2711b34-aeb0-49a1-b2fc-49da8eb269dd","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"18d03cd7-5b92-4b53-88c0-7a83d33c3755","text":"systems or system components","parameterId":"sa-08.31_odp","default":" [Assignment: organization defined systems or system components] "}],"subControls":"","tests":[{"testId":"SA-08(31)","uuid":"5e154507-6a4d-45f4-bad9-866340b18678","test":"Determine if [SELECTED PARAMETER VALUE(S): systems or system components ] implement the security design principle of secure system modification.The principle of sufficient documentation states that organizational personnel with responsibilities to interact with the system are provided with adequate documentation and other information such that the personnel contribute to rather than detract from system security. Despite attempts to comply with principles such as human factored security and acceptable security, systems are inherently complex, and the design intent for the use of security mechanisms and the ramifications of the misuse or misconfiguration of security mechanisms are not always intuitively obvious. Uninformed and insufficiently trained users can introduce vulnerabilities due to errors of omission and commission. The availability of documentation and training can help to ensure a knowledgeable cadre of personnel, all of whom have a critical role in the achievement of principles such as continuous protection. Documentation is written clearly and supported by training that provides security awareness and understanding of security-relevant responsibilities.
","uuid":"c13cbae7-0b33-4783-8b0d-30c94f57ea6c","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"1eab18c5-0635-473f-ae5e-bc1ce8a1c287","text":"systems or system components","parameterId":"sa-08.32_odp","default":" [Assignment: organization defined systems or system components] "}],"subControls":"","tests":[{"testId":"SA-08(32)","uuid":"203d4c9a-0170-477c-ad41-0bb6391d2b23","test":"Determine if [SELECTED PARAMETER VALUE(S): systems or system components ] implement the security design principle of sufficient documentation.The principle of minimization states that organizations should only process personally identifiable information that is directly relevant and necessary to accomplish an authorized purpose and should only maintain personally identifiable information for as long as is necessary to accomplish the purpose. Organizations have processes in place, consistent with applicable laws and policies, to implement the principle of minimization.
","uuid":"534e554d-6913-4851-86b0-f480702bb143","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"227a81b6-dd62-4f54-88ab-33957ad059f2","text":"processes","parameterId":"sa-08.33_odp","default":" [Assignment: organization defined processes] "}],"subControls":"","tests":[{"testId":"SA-08(33)","uuid":"00161bba-0b20-4c82-893d-200ecee90dc5","test":"Determine if the privacy principle of minimization is implemented using [SELECTED PARAMETER VALUE(S): processes ].External system services are provided by an external provider, and the organization has no direct control over the implementation of the required controls or the assessment of control effectiveness. Organizations establish relationships with external service providers in a variety of ways, including through business partnerships, contracts, interagency agreements, lines of business arrangements, licensing agreements, joint ventures, and supply chain exchanges. The responsibility for managing risks from the use of external system services remains with authorizing officials. For services external to organizations, a chain of trust requires that organizations establish and retain a certain level of confidence that each provider in the consumer-provider relationship provides adequate protection for the services rendered. The extent and nature of this chain of trust vary based on relationships between organizations and the external providers. Organizations document the basis for the trust relationships so that the relationships can be monitored. External system services documentation includes government, service providers, end user security roles and responsibilities, and service-level agreements. Service-level agreements define the expectations of performance for implemented controls, describe measurable outcomes, and identify remedies and response requirements for identified instances of noncompliance.
","uuid":"1584448c-8d0f-4300-9e64-14109f728013","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"77f767f5-30f7-4237-814c-4e7cc07c83b2","text":"controls","parameterId":"sa-09_odp.01","default":" [Assignment: organization defined controls] "},{"constraints":"","displayName":"","guidance":"","uuid":"abe9f37f-7636-4987-b0fc-db2c5aa2b57f","text":"processes, methods, and techniques","parameterId":"sa-09_odp.02","default":" [Assignment: organization defined processes, methods, and techniques] "}],"subControls":"","tests":[{"testId":"SA-09a.[01]","uuid":"3152a0ee-e24e-47c9-b41d-5f24426d6520","test":"Determine if providers of external system services comply with organizational security requirements;Information security services include the operation of security devices, such as firewalls or key management services as well as incident monitoring, analysis, and response. Risks assessed can include system, mission or business, security, privacy, or supply chain risks.
","uuid":"c587f89c-5f00-4923-b3af-46502040c536","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"830680ee-d53e-4db7-af1c-9cf1180fcfe5","text":"personnel or roles","parameterId":"sa-09.01_odp","default":" [Assignment: organization defined personnel or roles] "}],"subControls":"","tests":[{"testId":"SA-09(01)(a)","uuid":"dc6819e7-0b4e-426c-bca3-680c6d91d4d4","test":"Determine if an organizational assessment of risk is conducted prior to the acquisition or outsourcing of information security services;Information from external service providers regarding the specific functions, ports, protocols, and services used in the provision of such services can be useful when the need arises to understand the trade-offs involved in restricting certain functions and services or blocking certain ports and protocols.
","uuid":"e1ad30ef-8d94-4c39-a180-d7ecb8f9b91a","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"fd460948-9ca0-4427-ac53-e2444df4af24","text":"external system services","parameterId":"sa-09.02_odp","default":" [Assignment: organization defined external system services] "}],"subControls":"","tests":[{"testId":"SA-09(02)","uuid":"01e935a8-15f4-4783-8409-d0d65c41d723","test":"Determine if providers of [SELECTED PARAMETER VALUE(S): external system services ] are required to identify the functions, ports, protocols, and other services required for the use of such services.Trust relationships between organizations and external service providers reflect the degree of confidence that the risk from using external services is at an acceptable level. Trust relationships can help organizations gain increased levels of confidence that service providers are providing adequate protection for the services rendered and can also be useful when conducting incident response or when planning for upgrades or obsolescence. Trust relationships can be complicated due to the potentially large number of entities participating in the consumer-provider interactions, subordinate relationships and levels of trust, and types of interactions between the parties. In some cases, the degree of trust is based on the level of control that organizations can exert on external service providers regarding the controls necessary for the protection of the service, information, or individual privacy and the evidence brought forth as to the effectiveness of the implemented controls. The level of control is established by the terms and conditions of the contracts or service-level agreements.
","uuid":"67e2c3d5-7de7-48e4-b034-f2956a47730c","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"984d6cf9-45cb-46ac-8f0d-2736e1dc8221","text":"organization-defined security and privacy requirements, properties, factors, or conditions defining acceptable trust relationships","parameterId":"sa-9.3_prm_1","default":" [Assignment: organization-defined security and privacy requirements, properties, factors, or conditions defining acceptable trust relationships] "},{"constraints":"","displayName":"","guidance":"","uuid":"77426c70-3f73-471f-8336-c2af7a4851b8","text":"security requirements, properties, factors, or conditions","parameterId":"sa-09.03_odp.01","default":" [Assignment: organization defined security requirements, properties, factors, or conditions] "},{"constraints":"","displayName":"","guidance":"","uuid":"d8bcb8b3-fb34-4d5d-86cc-781abf765d9d","text":"privacy requirements, properties, factors, or conditions","parameterId":"sa-09.03_odp.02","default":" [Assignment: organization defined privacy requirements, properties, factors, or conditions] "}],"subControls":"","tests":[{"testId":"SA-09(03)[01]","uuid":"0426ba1f-c17c-4c04-8e44-a3fe53c9cf77","test":"Determine if trust relationships with external service provides based on [SELECTED PARAMETER VALUE(S): security requirements, properties, factors, or conditions ] are established and documented;As organizations increasingly use external service providers, it is possible that the interests of the service providers may diverge from organizational interests. In such situations, simply having the required technical, management, or operational controls in place may not be sufficient if the providers that implement and manage those controls are not operating in a manner consistent with the interests of the consuming organizations. Actions that organizations take to address such concerns include requiring background checks for selected service provider personnel; examining ownership records; employing only trustworthy service providers, such as providers with which organizations have had successful trust relationships; and conducting routine, periodic, unscheduled visits to service provider facilities.
","uuid":"c9ce6b1a-489d-4be7-acbd-3daafc74b73e","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"b4711014-06f2-415d-a5b8-e8759a5abca7","text":"external service providers","parameterId":"sa-09.04_odp.01","default":" [Assignment: organization defined external service providers] "},{"constraints":"","displayName":"","guidance":"","uuid":"cb5895b0-a39d-45a3-8b85-1c78d4c6599c","text":"actions","parameterId":"sa-09.04_odp.02","default":" [Assignment: organization defined actions] "}],"subControls":"","tests":[{"testId":"SA-09(04)","uuid":"b313c231-a91d-4506-976e-757dddb6404c","test":"Determine if [SELECTED PARAMETER VALUE(S): actions ] are taken to verify that the interests of [SELECTED PARAMETER VALUE(S): external service providers ] are consistent with and reflect organizational interests.The location of information processing, information and data storage, or system services can have a direct impact on the ability of organizations to successfully execute their mission and business functions. The impact occurs when external providers control the location of processing, storage, or services. The criteria that external providers use for the selection of processing, storage, or service locations may be different from the criteria that organizations use. For example, organizations may desire that data or information storage locations be restricted to certain locations to help facilitate incident response activities in case of information security incidents or breaches. Incident response activities, including forensic analyses and after-the-fact investigations, may be adversely affected by the governing laws, policies, or protocols in the locations where processing and storage occur and/or the locations from which system services emanate.
","uuid":"96a81508-4ff9-482d-86d6-11a74ef4d6d7","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"1ce5c496-0d50-4e43-9a60-a08e987fddf3","text":"[Selection (one or more): information processing; information or data; system services]","parameterId":"sa-09.05_odp.01","default":"[Selection (one or more): information processing; information or data; system services]"},{"constraints":"","displayName":"","guidance":"","uuid":"a46fc258-91dd-46de-affa-491aa7ab2087","text":"locations","parameterId":"sa-09.05_odp.02","default":" [Assignment: organization defined locations] "},{"constraints":"","displayName":"","guidance":"","uuid":"5cb4a775-d5c3-478d-833b-f3e86afb5b5b","text":"requirements","parameterId":"sa-09.05_odp.03","default":" [Assignment: organization defined requirements] "}],"subControls":"","tests":[{"testId":"SA-09(05)","uuid":"b8ea6beb-d279-4aa1-970c-dd4cb2ae0157","test":"Determine if based on [SELECTED PARAMETER VALUE(S): requirements ], [SELECTED PARAMETER VALUE(S): [Selection (one or more): information processing; information or data; system services] ] is/are restricted to [SELECTED PARAMETER VALUE(S): locations ].Maintaining exclusive control of cryptographic keys in an external system prevents decryption of organizational data by external system staff. Organizational control of cryptographic keys can be implemented by encrypting and decrypting data inside the organization as data is sent to and received from the external system or by employing a component that permits encryption and decryption functions to be local to the external system but allows exclusive organizational access to the encryption keys.
","uuid":"31122a29-1a32-4c23-96d2-a61ef5661dcb","family":"System and Services Acquisition","parameters":[],"subControls":"","tests":[{"testId":"SA-09(06)","uuid":"f43a1d34-7c59-4b40-a8fa-3cb3e4bcba7f","test":"Determine if exclusive control of cryptographic keys is maintained for encrypted material stored or transmitted through an external system.Storage of organizational information in an external system could limit visibility into the security status of its data. The ability of the organization to verify and validate the integrity of its stored data without transferring it out of the external system provides such visibility.
","uuid":"b283c521-7c42-4028-8405-b8c88d74357d","family":"System and Services Acquisition","parameters":[],"subControls":"","tests":[{"testId":"SA-09(07)","uuid":"22bfdc80-785b-48ad-b630-aa9c094b7d64","test":"Determine if the capability is provided to check the integrity of information while it resides in the external system.The geographic location of information processing and data storage can have a direct impact on the ability of organizations to successfully execute their mission and business functions. A compromise or breach of high impact information and systems can have severe or catastrophic adverse impacts on organizational assets and operations, individuals, other organizations, and the Nation. Restricting the processing and storage of high-impact information to facilities within the legal jurisdictional boundary of the United States provides greater control over such processing and storage.
","uuid":"adbaac97-19c7-42b0-8458-628a8eda9ab4","family":"System and Services Acquisition","parameters":[],"subControls":"","tests":[{"testId":"SA-09(08)","uuid":"1ff7fdb1-20b2-40d5-b20f-578221c66cd3","test":"Determine if the geographic location of information processing and data storage is restricted to facilities located within the legal jurisdictional boundary of the united states.Organizations consider the quality and completeness of configuration management activities conducted by developers as direct evidence of applying effective security controls. Controls include protecting the master copies of material used to generate security-relevant portions of the system hardware, software, and firmware from unauthorized modification or destruction. Maintaining the integrity of changes to the system, system component, or system service requires strict configuration control throughout the system development life cycle to track authorized changes and prevent unauthorized changes.
The configuration items that are placed under configuration management include the formal model; the functional, high-level, and low-level design specifications; other design data; implementation documentation; source code and hardware schematics; the current running version of the object code; tools for comparing new versions of security-relevant hardware descriptions and source code with previous versions; and test fixtures and documentation. Depending on the mission and business needs of organizations and the nature of the contractual relationships in place, developers may provide configuration management support during the operations and maintenance stage of the system development life cycle.
","uuid":"b6dec4a3-156f-4a20-b572-64ba124bdd92","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"fa86cbc9-64a6-41d6-a6c1-574ec1fd29c6","text":"[Selection (one or more): design; development; implementation; operation; disposal]","parameterId":"sa-10_odp.01","default":"[Selection (one or more): design; development; implementation; operation; disposal]"},{"constraints":"","displayName":"","guidance":"","uuid":"b52f909e-eaaf-4cc4-b1f6-0207ba1fb0fc","text":"configuration items","parameterId":"sa-10_odp.02","default":" [Assignment: organization defined configuration items] "},{"constraints":"","displayName":"","guidance":"","uuid":"f4ddc310-610e-4b0f-ad5a-fdab08b8e043","text":"personnel","parameterId":"sa-10_odp.03","default":" [Assignment: organization defined personnel] "}],"subControls":"","tests":[{"testId":"SA-10a.","uuid":"d23ed084-5a36-481d-918e-991d3c030fb0","test":"Determine if the developer of the system, system component, or system service is required to perform configuration management during system, component, or service [SELECTED PARAMETER VALUE(S): [Selection (one or more): design; development; implementation; operation; disposal] ];Software and firmware integrity verification allows organizations to detect unauthorized changes to software and firmware components using developer-provided tools, techniques, and mechanisms. The integrity checking mechanisms can also address counterfeiting of software and firmware components. Organizations verify the integrity of software and firmware components, for example, through secure one-way hashes provided by developers. Delivered software and firmware components also include any updates to such components.
","uuid":"fc660a55-cd7e-4608-9369-cc8e557aba86","family":"System and Services Acquisition","parameters":[],"subControls":"","tests":[{"testId":"SA-10(01)","uuid":"f5161847-66c5-4ccf-9a06-b9fbc7ca1262","test":"Determine if the developer of the system, system component, or system service is required to enable integrity verification of software and firmware components.Alternate configuration management processes may be required when organizations use commercial off-the-shelf information technology products. Alternate configuration management processes include organizational personnel who review and approve proposed changes to systems, system components, and system services and conduct security and privacy impact analyses prior to the implementation of changes to systems, components, or services.
","uuid":"7edef2d9-c617-4b91-ad5f-765262f93328","family":"System and Services Acquisition","parameters":[],"subControls":"","tests":[{"testId":"SA-10(02)","uuid":"1f71123d-3cd3-41ea-bd7f-be04c5671a56","test":"Determine if an alternate configuration management process has been provided using organizational personnel in the absence of a dedicated developer configuration management team.Hardware integrity verification allows organizations to detect unauthorized changes to hardware components using developer-provided tools, techniques, methods, and mechanisms. Organizations may verify the integrity of hardware components with hard-to-copy labels, verifiable serial numbers provided by developers, and by requiring the use of anti-tamper technologies. Delivered hardware components also include hardware and firmware updates to such components.
","uuid":"77fc6c49-6bd6-4ac3-a234-54d9c4af4dad","family":"System and Services Acquisition","parameters":[],"subControls":"","tests":[{"testId":"SA-10(03)","uuid":"4d5f92e8-2fd9-4779-9777-e727975b8510","test":"Determine if the developer of the system, system component, or system service is required to enable integrity verification of hardware components.The trusted generation of descriptions, source code, and object code addresses authorized changes to hardware, software, and firmware components between versions during development. The focus is on the efficacy of the configuration management process by the developer to ensure that newly generated versions of security-relevant hardware descriptions, source code, and object code continue to enforce the security policy for the system, system component, or system service. In contrast, SA-10(1) and SA-10(3) allow organizations to detect unauthorized changes to hardware, software, and firmware components using tools, techniques, or mechanisms provided by developers.
","uuid":"d6847b9f-711a-4b6a-a52d-b0cc1be4acf7","family":"System and Services Acquisition","parameters":[],"subControls":"","tests":[{"testId":"SA-10(04)[01]","uuid":"15020d3b-0702-4990-8409-6bc51689368f","test":"Determine if the developer of the system, system component, or system service is required to employ tools for comparing newly generated versions of security-relevant hardware descriptions with previous versions;Mapping integrity for version control addresses changes to hardware, software, and firmware components during both initial development and system development life cycle updates. Maintaining the integrity between the master copies of security-relevant hardware, software, and firmware (including designs, hardware drawings, source code) and the equivalent data in master copies in operational environments is essential to ensuring the availability of organizational systems that support critical mission and business functions.
","uuid":"a772f2ad-b341-40bc-9fbe-6754378cb005","family":"System and Services Acquisition","parameters":[],"subControls":"","tests":[{"testId":"SA-10(05)","uuid":"5e32303d-825f-4389-a8de-02413afadfe4","test":"Determine if the developer of the system, system component, or system service is required 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.The trusted distribution of security-relevant hardware, software, and firmware updates help to ensure that the updates are correct representations of the master copies maintained by the developer and have not been tampered with during distribution.
","uuid":"ed13a078-09cb-40c4-9eaf-9bd2f6e83dce","family":"System and Services Acquisition","parameters":[],"subControls":"","tests":[{"testId":"SA-10(06)","uuid":"19fd559c-a64d-4087-bb6d-a13e6d11a422","test":"Determine if the developer of the system, system component, or system service is required 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.Information security and privacy representatives can include system security officers, senior agency information security officers, senior agency officials for privacy, and system privacy officers. Representation by personnel with information security and privacy expertise is important because changes to system configurations can have unintended side effects, some of which may be security- or privacy-relevant. Detecting such changes early in the process can help avoid unintended, negative consequences that could ultimately affect the security and privacy posture of systems. The configuration change management and control process in this control enhancement refers to the change management and control process defined by organizations in SA-10b.
","uuid":"bc50d171-998f-4b92-bab2-b5f3b3666251","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"bd26acca-73c1-461a-96b9-c1f1b0a4d42e","text":"organization-defined security and privacy representatives","parameterId":"sa-10.7_prm_1","default":" [Assignment: organization-defined security and privacy representatives] "},{"constraints":"","displayName":"","guidance":"","uuid":"8f435a9f-174f-4c64-a359-6a33861645d9","text":"organization-defined configuration change management and control process","parameterId":"sa-10.7_prm_2","default":" [Assignment: organization-defined configuration change management and control process] "},{"constraints":"","displayName":"","guidance":"","uuid":"d57d1f5b-720f-46be-8538-a9e2aff7de99","text":"security representatives","parameterId":"sa-10.07_odp.01","default":" [Assignment: organization defined security representatives] "},{"constraints":"","displayName":"","guidance":"","uuid":"10100c8c-2a20-4e62-9a35-7313a062ae33","text":"privacy representatives","parameterId":"sa-10.07_odp.02","default":" [Assignment: organization defined privacy representatives] "},{"constraints":"","displayName":"","guidance":"","uuid":"94afc079-a1e8-474f-88b9-bfd1065404f9","text":"configuration change management and control processes","parameterId":"sa-10.07_odp.03","default":" [Assignment: organization defined configuration change management and control processes] "},{"constraints":"","displayName":"","guidance":"","uuid":"172bcd33-9023-4947-95b6-2b037aa935ba","text":"configuration change management and control processes","parameterId":"sa-10.07_odp.04","default":" [Assignment: organization defined configuration change management and control processes] "}],"subControls":"","tests":[{"testId":"SA-10(07)[01]","uuid":"eb7a5f11-5b74-4361-8084-7047fcb63032","test":"Determine if [SELECTED PARAMETER VALUE(S): security representatives ] are required to be included in the [SELECTED PARAMETER VALUE(S): configuration change management and control processes ];Developmental testing and evaluation confirms that the required controls are implemented correctly, operating as intended, enforcing the desired security and privacy policies, and meeting established security and privacy requirements. Security properties of systems and the privacy of individuals may be affected by the interconnection of system components or changes to those components. The interconnections or changes—including upgrading or replacing applications, operating systems, and firmware—may adversely affect previously implemented controls. Ongoing assessment during development allows for additional types of testing and evaluation that developers can conduct to reduce or eliminate potential flaws. Testing custom software applications may require approaches such as manual code review, security architecture review, and penetration testing, as well as and static analysis, dynamic analysis, binary analysis, or a hybrid of the three analysis approaches.
Developers can use the analysis approaches, along with security instrumentation and fuzzing, in a variety of tools and in source code reviews. The security and privacy assessment plans include the specific activities that developers plan to carry out, including the types of analyses, testing, evaluation, and reviews of software and firmware components; the degree of rigor to be applied; the frequency of the ongoing testing and evaluation; and the types of artifacts produced during those processes. The depth of testing and evaluation refers to the rigor and level of detail associated with the assessment process. The coverage of testing and evaluation refers to the scope (i.e., number and type) of the artifacts included in the assessment process. Contracts specify the acceptance criteria for security and privacy assessment plans, flaw remediation processes, and the evidence that the plans and processes have been diligently applied. Methods for reviewing and protecting assessment plans, evidence, and documentation are commensurate with the security category or classification level of the system. Contracts may specify protection requirements for documentation.
","uuid":"7ed93183-d583-4b35-a3c5-1a1e23cce7d6","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"3090f166-2e65-45bb-b10e-b335cb92635b","text":"[Selection (one or more): unit; integration; system; regression]","parameterId":"sa-11_odp.01","default":"[Selection (one or more): unit; integration; system; regression]"},{"constraints":"","displayName":"","guidance":"","uuid":"2a72a66d-a95e-4181-9a31-a4adaa7199fa","text":"frequency to conduct","parameterId":"sa-11_odp.02","default":" [Assignment: organization defined frequency to conduct] "},{"constraints":"","displayName":"","guidance":"","uuid":"3c26ecd0-88f6-44da-872c-49cd8759dc75","text":"depth and coverage","parameterId":"sa-11_odp.03","default":" [Assignment: organization defined depth and coverage] "}],"subControls":"","tests":[{"testId":"SA-11a.[01]","uuid":"dffab592-1bf4-45e5-bc70-9ce41598885c","test":"Determine if the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to develop a plan for ongoing security assessments;Static code analysis provides a technology and methodology for security reviews and includes checking for weaknesses in the code as well as for the incorporation of libraries or other included code with known vulnerabilities or that are out-of-date and not supported. Static code analysis can be used to identify vulnerabilities and enforce secure coding practices. It is most effective when used early in the development process, when each code change can automatically be scanned for potential weaknesses. Static code analysis can provide clear remediation guidance and identify defects for developers to fix. Evidence of the correct implementation of static analysis can include aggregate defect density for critical defect types, evidence that defects were inspected by developers or security professionals, and evidence that defects were remediated. A high density of ignored findings, commonly referred to as false positives, indicates a potential problem with the analysis process or the analysis tool. In such cases, organizations weigh the validity of the evidence against evidence from other sources.
","uuid":"834c7651-2779-40a3-9916-59b228019de5","family":"System and Services Acquisition","parameters":[],"subControls":"","tests":[{"testId":"SA-11(01)[01]","uuid":"08295a12-7b99-4869-a445-089906e98eca","test":"Determine if the developer of the system, system component, or system service is required to employ static code analysis tools to identify common flaws;Systems, system components, and system services may deviate significantly from the functional and design specifications created during the requirements and design stages of the system development life cycle. Therefore, updates to threat modeling and vulnerability analyses of those systems, system components, and system services during development and prior to delivery are critical to the effective operation of those systems, components, and services. Threat modeling and vulnerability analyses at this stage of the system development life cycle ensure that design and implementation changes have been accounted for and that vulnerabilities created because of those changes have been reviewed and mitigated.
","uuid":"4ad9f61b-a564-4950-aa39-ce69c378bbef","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"e449fa74-8762-4e55-bad3-aac410c84039","text":"organization-defined breadth and depth of modeling and analyses","parameterId":"sa-11.2_prm_3","default":" [Assignment: organization-defined breadth and depth of modeling and analyses] "},{"constraints":"","displayName":"","guidance":"","uuid":"210951ec-62a5-46fc-94ee-7c5dc47f6978","text":"organization-defined acceptance criteria","parameterId":"sa-11.2_prm_4","default":" [Assignment: organization-defined acceptance criteria] "},{"constraints":"","displayName":"","guidance":"","uuid":"279e775e-f284-44ca-9a66-e200409b367d","text":"information","parameterId":"sa-11.02_odp.01","default":" [Assignment: organization defined information] "},{"constraints":"","displayName":"","guidance":"","uuid":"9423093b-1006-458f-97c2-3116523e76f7","text":"tools and methods","parameterId":"sa-11.02_odp.02","default":" [Assignment: organization defined tools and methods] "},{"constraints":"","displayName":"","guidance":"","uuid":"cb1c0878-ab21-45be-95da-6b8425ce4043","text":"breadth and depth","parameterId":"sa-11.02_odp.03","default":" [Assignment: organization defined breadth and depth] "},{"constraints":"","displayName":"","guidance":"","uuid":"aebbd1af-b961-425f-95bb-7857cbb14ba3","text":"breadth and depth","parameterId":"sa-11.02_odp.04","default":" [Assignment: organization defined breadth and depth] "},{"constraints":"","displayName":"","guidance":"","uuid":"b1c9badc-98bf-4225-8dcb-13bd191d8ffe","text":"acceptance criteria","parameterId":"sa-11.02_odp.05","default":" [Assignment: organization defined acceptance criteria] "},{"constraints":"","displayName":"","guidance":"","uuid":"dd1fcb75-7c67-4457-9433-27c9c17e6a40","text":"acceptance criteria","parameterId":"sa-11.02_odp.06","default":" [Assignment: organization defined acceptance criteria] "}],"subControls":"","tests":[{"testId":"SA-11(02)(a)[01]","uuid":"64b2d6c8-f96c-41e9-b7fa-9cb492c06000","test":"Determine if the developer of the system, system component, or system service is required to perform threat modeling during development of the system, component, or service that uses [SELECTED PARAMETER VALUE(S): information ];Independent agents have the qualifications—including the expertise, skills, training, certifications, and experience—to verify the correct implementation of developer security and privacy assessment plans.
","uuid":"ea90ada7-042d-423f-b653-d227a30ea43f","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"06e3a229-86b0-4e21-b959-385fe18d3a09","text":"independence criteria","parameterId":"sa-11.03_odp","default":" [Assignment: organization defined independence criteria] "}],"subControls":"","tests":[{"testId":"SA-11(03)(a)[01]","uuid":"4f1209db-503f-4eb7-a635-3dfa492ef59c","test":"Determine if an independent agent is required to satisfy [SELECTED PARAMETER VALUE(S): independence criteria ] to verify the correct implementation of the developer security assessment plan and the evidence produced during testing and evaluation;Manual code reviews are usually reserved for the critical software and firmware components of systems. Manual code reviews are effective at identifying weaknesses that require knowledge of the application’s requirements or context that, in most cases, is unavailable to automated analytic tools and techniques, such as static and dynamic analysis. The benefits of manual code review include the ability to verify access control matrices against application controls and review detailed aspects of cryptographic implementations and controls.
","uuid":"5843aac8-b3c8-4c93-a524-23c1583eef51","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"60e13330-f75a-4833-9148-faad075f7088","text":"specific code","parameterId":"sa-11.04_odp.01","default":" [Assignment: organization defined specific code] "},{"constraints":"","displayName":"","guidance":"","uuid":"226f6a4c-f34b-4003-9621-8a64b4febe6b","text":"processes, procedures, and/or techniques","parameterId":"sa-11.04_odp.02","default":" [Assignment: organization defined processes, procedures, and/or techniques] "}],"subControls":"","tests":[{"testId":"SA-11(04)","uuid":"42f9dcac-3591-4066-ab9b-e1885e94b3f0","test":"Determine if the developer of the system, system component, or system service is required to perform a manual code review of [SELECTED PARAMETER VALUE(S): specific code ] using [SELECTED PARAMETER VALUE(S): processes, procedures, and/or techniques ].Penetration testing is an assessment methodology in which assessors, using all available information technology product or system documentation and working under specific constraints, attempt to circumvent the implemented security and privacy features of information technology products and systems. Useful information for assessors who conduct penetration testing includes product and system design specifications, source code, and administrator and operator manuals. Penetration testing can include white-box, gray-box, or black-box testing with analyses performed by skilled professionals who simulate adversary actions. The objective of penetration testing is to discover vulnerabilities in systems, system components, and services that result from implementation errors, configuration faults, or other operational weaknesses or deficiencies. Penetration tests can be performed in conjunction with automated and manual code reviews to provide a greater level of analysis than would ordinarily be possible. When user session information and other personally identifiable information is captured or recorded during penetration testing, such information is handled appropriately to protect privacy.
","uuid":"8b6f85bf-b443-45cb-97d6-c1417bba498b","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"4085b890-a240-4b63-a420-6b7c5cd270ff","text":"organization-defined breadth and depth of testing","parameterId":"sa-11.5_prm_1","default":" [Assignment: organization-defined breadth and depth of testing] "},{"constraints":"","displayName":"","guidance":"","uuid":"fa67b06c-6873-43e8-aa49-196617a621fc","text":"breadth","parameterId":"sa-11.05_odp.01","default":" [Assignment: organization defined breadth] "},{"constraints":"","displayName":"","guidance":"","uuid":"75d780ae-116d-4732-8209-748a8929def6","text":"depth","parameterId":"sa-11.05_odp.02","default":" [Assignment: organization defined depth] "},{"constraints":"","displayName":"","guidance":"","uuid":"989b72f5-f576-402a-9d76-02d70c326a74","text":"constraints","parameterId":"sa-11.05_odp.03","default":" [Assignment: organization defined constraints] "}],"subControls":"","tests":[{"testId":"SA-11(05)(a)[01]","uuid":"c326fd24-f362-423b-b2c6-76d5249d7416","test":"Determine if the developer of the system, system component, or system service is required to perform penetration testing at the following level of rigor: [SELECTED PARAMETER VALUE(S): breadth ];Attack surfaces of systems and system components are exposed areas that make those systems more vulnerable to attacks. Attack surfaces include any accessible areas where weaknesses or deficiencies in the hardware, software, and firmware components provide opportunities for adversaries to exploit vulnerabilities. Attack surface reviews ensure that developers analyze the design and implementation changes to systems and mitigate attack vectors generated as a result of the changes. The correction of identified flaws includes deprecation of unsafe functions.
","uuid":"987415f4-deb6-453d-b9b8-ea8aab452816","family":"System and Services Acquisition","parameters":[],"subControls":"","tests":[{"testId":"SA-11(06)","uuid":"2829c423-2014-43f3-a19c-9af03fb0913a","test":"Determine if the developer of the system, system component, or system service is required to perform attack surface reviews.Verifying that testing and evaluation provides complete coverage of required controls can be accomplished by a variety of analytic techniques ranging from informal to formal. Each of these techniques provides an increasing level of assurance that corresponds to the degree of formality of the analysis. Rigorously demonstrating control coverage at the highest levels of assurance can be achieved using formal modeling and analysis techniques, including correlation between control implementation and corresponding test cases.
","uuid":"17de8938-3244-406b-a296-4e7cb5779294","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"0276135d-65f3-41e5-b453-f3dc3b7ec4d6","text":"organization-defined breadth and depth of testing and evaluation","parameterId":"sa-11.7_prm_1","default":" [Assignment: organization-defined breadth and depth of testing and evaluation] "},{"constraints":"","displayName":"","guidance":"","uuid":"84be85f8-6cff-4277-bf75-4c27a2570c72","text":"breadth","parameterId":"sa-11.07_odp.01","default":" [Assignment: organization defined breadth] "},{"constraints":"","displayName":"","guidance":"","uuid":"6dbea8ec-e82c-4057-9957-72bcbcf07cff","text":"depth","parameterId":"sa-11.07_odp.02","default":" [Assignment: organization defined depth] "}],"subControls":"","tests":[{"testId":"SA-11(07)[01]","uuid":"d7f08d86-f37a-4360-ad01-bf7084ef193e","test":"Determine if the developer of the system, system component, or system service is required to verify that the scope of testing and evaluation provides complete coverage of the required controls at [SELECTED PARAMETER VALUE(S): breadth ];Dynamic code analysis provides runtime verification of software programs using tools capable of monitoring programs for memory corruption, user privilege issues, and other potential security problems. Dynamic code analysis employs runtime tools to ensure that security functionality performs in the way it was designed. A type of dynamic analysis, known as fuzz testing, induces program failures by deliberately introducing malformed or random data into software programs. Fuzz testing strategies are derived from the intended use of applications and the functional and design specifications for the applications. To understand the scope of dynamic code analysis and the assurance provided, organizations may also consider conducting code coverage analysis (i.e., checking the degree to which the code has been tested using metrics such as percent of subroutines tested or percent of program statements called during execution of the test suite) and/or concordance analysis (i.e., checking for words that are out of place in software code, such as non-English language words or derogatory terms).
","uuid":"d3fa936b-5c9a-48de-9aec-3fa1220c28ad","family":"System and Services Acquisition","parameters":[],"subControls":"","tests":[{"testId":"SA-11(08)[01]","uuid":"0f8c355c-8175-4dfa-acf1-4c2a205ec2d9","test":"Determine if the developer of the system, system component, or system service is required to employ dynamic code analysis tools to identify common flaws;Interactive (also known as instrumentation-based) application security testing is a method of detecting vulnerabilities by observing applications as they run during testing. The use of instrumentation relies on direct measurements of the actual running applications and uses access to the code, user interaction, libraries, frameworks, backend connections, and configurations to directly measure control effectiveness. When combined with analysis techniques, interactive application security testing can identify a broad range of potential vulnerabilities and confirm control effectiveness. Instrumentation-based testing works in real time and can be used continuously throughout the system development life cycle.
","uuid":"a0b7f39a-0da7-4f9c-89bf-74ddd86d0e10","family":"System and Services Acquisition","parameters":[],"subControls":"","tests":[{"testId":"SA-11(09)[01]","uuid":"32423555-a044-4640-b17a-f5932924611a","test":"Determine if the developer of the system, system component, or system service is required to employ interactive application security testing tools to identify flaws;Development tools include programming languages and computer-aided design systems. Reviews of development processes include the use of maturity models to determine the potential effectiveness of such processes. Maintaining the integrity of changes to tools and processes facilitates effective supply chain risk assessment and mitigation. Such integrity requires configuration control throughout the system development life cycle to track authorized changes and prevent unauthorized changes.
","uuid":"af73f0cb-e6c7-45e0-a4c6-c7fc64cc1a01","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"198486d4-ec90-4eb8-a230-5b2cf220ce1e","text":"organization-defined security and privacy requirements","parameterId":"sa-15_prm_2","default":" [Assignment: organization-defined security and privacy requirements] "},{"constraints":"","displayName":"","guidance":"","uuid":"ec0a54f1-3f82-4791-bdf5-d7015e700a7e","text":"frequency","parameterId":"sa-15_odp.01","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"1530d30a-f5c4-42f2-a908-3342f6feaa9b","text":"security requirements","parameterId":"sa-15_odp.02","default":" [Assignment: organization defined security requirements] "},{"constraints":"","displayName":"","guidance":"","uuid":"4b890102-7401-4c10-9f7f-1ceecad76e78","text":"privacy requirements","parameterId":"sa-15_odp.03","default":" [Assignment: organization defined privacy requirements] "}],"subControls":"","tests":[{"testId":"SA-15a.01[01]","uuid":"55e8f38c-2995-4f50-bae3-b7f2f759a2f4","test":"Determine if the developer of the system, system component, or system service is required to follow a documented development process that explicitly addresses security requirements;Organizations use quality metrics to establish acceptable levels of system quality. Metrics can include quality gates, which are collections of completion criteria or sufficiency standards that represent the satisfactory execution of specific phases of the system development project. For example, a quality gate may require the elimination of all compiler warnings or a determination that such warnings have no impact on the effectiveness of required security or privacy capabilities. During the execution phases of development projects, quality gates provide clear, unambiguous indications of progress. Other metrics apply to the entire development project. Metrics can include defining the severity thresholds of vulnerabilities in accordance with organizational risk tolerance, such as requiring no known vulnerabilities in the delivered system with a Common Vulnerability Scoring System (CVSS) severity of medium or high.
","uuid":"b896d9c9-1e56-4321-b65c-d331f7981965","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"994b247a-1fa9-439d-8bf1-4693518b5b69","text":"[Selection (one or more): [(NESTED PARAMETER) Assignment for sa-15.01_odp.02: frequency]; [(NESTED PARAMETER) Assignment for sa-15.01_odp.03: program review]; upon delivery]","parameterId":"sa-15.01_odp.01","default":"[Selection (one or more): [(NESTED PARAMETER) Assignment for sa-15.01_odp.02: frequency]; [(NESTED PARAMETER) Assignment for sa-15.01_odp.03: program review]; upon delivery]"},{"constraints":"","displayName":"","guidance":"","uuid":"2a3e1071-4603-4e9d-adf0-292a556a7def","text":"frequency","parameterId":"sa-15.01_odp.02","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"a5cd8c0e-c844-4375-82e8-f2fddbb8abe4","text":"program review","parameterId":"sa-15.01_odp.03","default":" [Assignment: organization defined program review] "}],"subControls":"","tests":[{"testId":"SA-15(01)(a)","uuid":"828b747b-963d-4e66-be5f-38cfb7c7f307","test":"Determine if the developer of the system, system component, or system service is required to define quality metrics at the beginning of the development process;System development teams select and deploy security and privacy tracking tools, including vulnerability or work item tracking systems that facilitate assignment, sorting, filtering, and tracking of completed work items or tasks associated with development processes.
","uuid":"e8ef8410-75a0-4f21-83bd-d009a4e964b8","family":"System and Services Acquisition","parameters":[],"subControls":"","tests":[{"testId":"SA-15(02)[01]","uuid":"ef973c94-ccbb-4575-97a2-00e6a6e95691","test":"Determine if the developer of the system, system component, or system service is required to select and employ security tracking tools for use during the development process;Criticality analysis performed by the developer provides input to the criticality analysis performed by organizations. Developer input is essential to organizational criticality analysis because organizations may not have access to detailed design documentation for system components that are developed as commercial off-the-shelf products. Such design documentation includes functional specifications, high-level designs, low-level designs, source code, and hardware schematics. Criticality analysis is important for organizational systems that are designated as high value assets. High value assets can be moderate- or high-impact systems due to heightened adversarial interest or potential adverse effects on the federal enterprise. Developer input is especially important when organizations conduct supply chain criticality analyses.
","uuid":"4b1beafa-fd83-46a7-8508-685c9a887043","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"98d3e72c-ca3c-40f8-aa0d-2beea53e7f6a","text":"organization-defined breadth and depth of criticality analysis","parameterId":"sa-15.3_prm_2","default":" [Assignment: organization-defined breadth and depth of criticality analysis] "},{"constraints":"","displayName":"","guidance":"","uuid":"cfa36af0-3bb7-42d3-9586-1daf26fa75b1","text":"decision points","parameterId":"sa-15.03_odp.01","default":" [Assignment: organization defined decision points] "},{"constraints":"","displayName":"","guidance":"","uuid":"c734ccc0-c373-4f85-8a9f-8667cda3eff3","text":"breadth","parameterId":"sa-15.03_odp.02","default":" [Assignment: organization defined breadth] "},{"constraints":"","displayName":"","guidance":"","uuid":"01acd7a0-c4ff-4d50-a721-a8eab7ad0282","text":"depth","parameterId":"sa-15.03_odp.03","default":" [Assignment: organization defined depth] "}],"subControls":"","tests":[{"testId":"SA-15(03)(a)","uuid":"d61131a9-0dd9-4318-8c7f-710888a8deee","test":"Determine if the developer of the system, system component, or system service is required to perform a criticality analysis at [SELECTED PARAMETER VALUE(S): decision points ] in the system development life cycle;Attack surface reduction is closely aligned with threat and vulnerability analyses and system architecture and design. Attack surface reduction is a means of reducing risk to organizations by giving attackers less opportunity to exploit weaknesses or deficiencies (i.e., potential vulnerabilities) within systems, system components, and system services. Attack surface reduction includes implementing the concept of layered defenses, applying the principles of least privilege and least functionality, applying secure software development practices, deprecating unsafe functions, reducing entry points available to unauthorized users, reducing the amount of code that executes, and eliminating application programming interfaces (APIs) that are vulnerable to attacks.
","uuid":"39653da7-b736-4f43-ac1e-7e3dc5ec6fe8","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"78c09dc7-3a4d-42db-950f-f26c667623f8","text":"thresholds","parameterId":"sa-15.05_odp","default":" [Assignment: organization defined thresholds] "}],"subControls":"","tests":[{"testId":"SA-15(05)","uuid":"29ff2bc0-a37b-4860-ba3c-c339818cbbb9","test":"Determine if the developer of the system, system component, or system service is required to reduce attack surfaces to [SELECTED PARAMETER VALUE(S): thresholds ].Developers of systems, system components, and system services consider the effectiveness and efficiency of their development processes for meeting quality objectives and addressing the security and privacy capabilities in current threat environments.
","uuid":"04db1155-5d53-45a1-bef4-75210ce33d55","family":"System and Services Acquisition","parameters":[],"subControls":"","tests":[{"testId":"SA-15(06)","uuid":"53d69d77-ed52-45a1-8cf2-216cf846d832","test":"Determine if the developer of the system, system component, or system service is required to implement an explicit process to continuously improve the development process.Automated tools can be more effective at analyzing exploitable weaknesses or deficiencies in large and complex systems, prioritizing vulnerabilities by severity, and providing recommendations for risk mitigations.
","uuid":"89eaafb7-d5d7-464a-9990-4f018c93c578","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"79cfd8b2-6448-4b07-af5b-0879501dafca","text":"frequency","parameterId":"sa-15.07_odp.01","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"2666add0-dc80-4db5-8164-f8bf4df7c144","text":"tools","parameterId":"sa-15.07_odp.02","default":" [Assignment: organization defined tools] "},{"constraints":"","displayName":"","guidance":"","uuid":"7155043a-07c6-4c94-b0a0-d53f10eb34cf","text":"personnel or roles","parameterId":"sa-15.07_odp.03","default":" [Assignment: organization defined personnel or roles] "}],"subControls":"","tests":[{"testId":"SA-15(07)(a)","uuid":"ecd1eed7-2e2b-44b8-821b-70188dda12f9","test":"Determine if the developer of the system, system component, or system service is required to perform automated vulnerability analysis [SELECTED PARAMETER VALUE(S): frequency ] using [SELECTED PARAMETER VALUE(S): tools ];Analysis of vulnerabilities found in similar software applications can inform potential design and implementation issues for systems under development. Similar systems or system components may exist within developer organizations. Vulnerability information is available from a variety of public and private sector sources, including the NIST National Vulnerability Database.
","uuid":"67928f68-d0c7-4fea-9187-ae9f8008f7c2","family":"System and Services Acquisition","parameters":[],"subControls":"","tests":[{"testId":"SA-15(08)[01]","uuid":"36cca6c2-6f76-400b-a9a8-dd4924eced1c","test":"Determine if the developer of the system, system component, or system service is required to use threat modeling from similar systems, components, or services to inform the current development process;The incident response plan provided by developers may provide information not readily available to organizations and be incorporated into organizational incident response plans. Developer information may also be extremely helpful, such as when organizations respond to vulnerabilities in commercial off-the-shelf products.
","uuid":"cd510b43-a8d2-41dd-9641-3efc3d308146","family":"System and Services Acquisition","parameters":[],"subControls":"","tests":[{"testId":"SA-15(10)[01]","uuid":"2f77c342-dbcf-4659-afc9-1f826754c2f6","test":"Determine if the developer of the system, system component, or system service is required to provide an incident response plan;Archiving system or system components requires the developer to retain key development artifacts, including hardware specifications, source code, object code, and relevant documentation from the development process that can provide a readily available configuration baseline for system and component upgrades or modifications.
","uuid":"2a588a7a-757a-4acc-92b0-c6006096e7c4","family":"System and Services Acquisition","parameters":[],"subControls":"","tests":[{"testId":"SA-15(11)","uuid":"638f6933-3caf-4580-9e29-6629510142fa","test":"Determine if the developer of the system or system component is required to archive the system or component to be released or delivered together with the corresponding evidence supporting the final security and privacy review.Organizations can minimize the risk to an individual’s privacy by using techniques such as de-identification or synthetic data. Limiting the use of personally identifiable information in development and test environments helps reduce the level of privacy risk created by a system.
","uuid":"9b1a1767-7102-44d9-aa61-da25ca481f79","family":"System and Services Acquisition","parameters":[],"subControls":"","tests":[{"testId":"SA-15(12)","uuid":"21717d01-c5d1-4fae-9267-896b92c4c60c","test":"Determine if the developer of the system or system component is required to minimize the use of personally identifiable information in development and test environments.Developer-provided training applies to external and internal (in-house) developers. Training personnel is essential to ensuring the effectiveness of the controls implemented within organizational systems. Types of training include web-based and computer-based training, classroom-style training, and hands-on training (including micro-training). Organizations can also request training materials from developers to conduct in-house training or offer self-training to organizational personnel. Organizations determine the type of training necessary and may require different types of training for different security and privacy functions, controls, and mechanisms.
","uuid":"1830363a-d4f2-4237-aecc-f58cc7f5cd9d","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"b42b1a88-0638-4a06-8930-23dca93b055b","text":"training","parameterId":"sa-16_odp","default":" [Assignment: organization defined training] "}],"subControls":"","tests":[{"testId":"SA-16","uuid":"9fafb234-c30d-4e3e-a5d5-d65799afb6fc","test":"Determine if the developer of the system, system component, or system service is required to provide [SELECTED PARAMETER VALUE(S): training ] on the correct use and operation of the implemented security and privacy functions, controls, and/or mechanisms.Developer security and privacy architecture and design are directed at external developers, although they could also be applied to internal (in-house) development. In contrast, PL-8 is directed at internal developers to ensure that organizations develop a security and privacy architecture that is integrated with the enterprise architecture. The distinction between SA-17 and PL-8 is especially important when organizations outsource the development of systems, system components, or system services and when there is a requirement to demonstrate consistency with the enterprise architecture and security and privacy architecture of the organization. ISO 15408-2, ISO 15408-3 , and SP 800-160-1 provide information on security architecture and design, including formal policy models, security-relevant components, formal and informal correspondence, conceptually simple design, and structuring for least privilege and testing.
","uuid":"b5117987-4596-4fe2-afe2-652695ccf7ca","family":"System and Services Acquisition","parameters":[],"subControls":"","tests":[{"testId":"SA-17(a)[01]","uuid":"ff97dc8b-bd2f-4511-b297-7cba8975bdbd","test":"Determine if the developer of the system, system component, or system service is required to produce a design specification and security architecture that are consistent with the organization’s security architecture, which is an integral part the organization’s enterprise architecture;Formal models describe specific behaviors or security and privacy policies using formal languages, thus enabling the correctness of those behaviors and policies to be formally proven. Not all components of systems can be modeled. Generally, formal specifications are scoped to the behaviors or policies of interest, such as nondiscretionary access control policies. Organizations choose the formal modeling language and approach based on the nature of the behaviors and policies to be described and the available tools.
","uuid":"c4a2788d-4169-4a3a-accd-68c83e0b9b8e","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"d181e751-d9cd-4ece-ad90-beecc1f7527e","text":"organization-defined elements of organizational security and privacy policy","parameterId":"sa-17.1_prm_1","default":" [Assignment: organization-defined elements of organizational security and privacy policy] "},{"constraints":"","displayName":"","guidance":"","uuid":"188108a0-38ab-4698-93f7-1ea2ca927aac","text":"organizational security policy","parameterId":"sa-17.01_odp.01","default":" [Assignment: organization defined organizational security policy] "},{"constraints":"","displayName":"","guidance":"","uuid":"140cdb03-649b-4cef-8f6a-ae0750e6ceda","text":"organizational privacy policy","parameterId":"sa-17.01_odp.02","default":" [Assignment: organization defined organizational privacy policy] "}],"subControls":"","tests":[{"testId":"SA-17(01)(a)[01]","uuid":"4c177fab-42b3-4c02-af67-19f51d63d437","test":"Determine if as an integral part of the development process, the developer of the system, system component, or system service is required to produce a formal policy model describing the [SELECTED PARAMETER VALUE(S): organizational security policy ] to be enforced;The security-relevant hardware, software, and firmware represent the portion of the system, component, or service that is trusted to perform correctly to maintain required security properties.
","uuid":"87abdf69-f177-44ac-8934-de20dba4bb8c","family":"System and Services Acquisition","parameters":[],"subControls":"","tests":[{"testId":"SA-17(02)(a)[01]","uuid":"3a4623ce-5122-46cd-a595-bd6b3f70fe67","test":"Determine if the developer of the system, system component, or system service is required to define security-relevant hardware;Correspondence is an important part of the assurance gained through modeling. It demonstrates that the implementation is an accurate transformation of the model, and that any additional code or implementation details that are present have no impact on the behaviors or policies being modeled. Formal methods can be used to show that the high-level security properties are satisfied by the formal system description, and that the formal system description is correctly implemented by a description of some lower level, including a hardware description. Consistency between the formal top-level specification and the formal policy models is generally not amenable to being fully proven. Therefore, a combination of formal and informal methods may be needed to demonstrate such consistency. Consistency between the formal top-level specification and the actual implementation may require the use of an informal demonstration due to limitations on the applicability of formal methods to prove that the specification accurately reflects the implementation. Hardware, software, and firmware mechanisms internal to security-relevant components include mapping registers and direct memory input and output.
","uuid":"8291ae46-35fe-40e8-aae6-5f37a1af5c12","family":"System and Services Acquisition","parameters":[],"subControls":"","tests":[{"testId":"SA-17(03)(a)[01]","uuid":"959aaf17-cf90-47f2-b8ca-8514d2646755","test":"Determine if as an integral part of the development process, the developer of the system, system component, or system service is required to produce a formal top-level specification that specifies the interfaces to security-relevant hardware, software, and firmware in terms of exceptions;Correspondence is an important part of the assurance gained through modeling. It demonstrates that the implementation is an accurate transformation of the model, and that additional code or implementation detail has no impact on the behaviors or policies being modeled. Consistency between the descriptive top-level specification (i.e., high-level/low-level design) and the formal policy model is generally not amenable to being fully proven. Therefore, a combination of formal and informal methods may be needed to show such consistency. Hardware, software, and firmware mechanisms strictly internal to security-relevant hardware, software, and firmware include mapping registers and direct memory input and output.
","uuid":"5032116a-b967-4d5f-b7e0-6d08b01aa985","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"a67d10f1-ee69-4ff8-a562-a86bb0d2c879","text":"[Selection: informal demonstration, convincing argument with formal methods as feasible]","parameterId":"sa-17.04_odp","default":"[Selection: informal demonstration, convincing argument with formal methods as feasible]"}],"subControls":"","tests":[{"testId":"SA-17(04)(a)[01]","uuid":"0ba07c34-506c-4d14-a1df-21f6c18a6a38","test":"Determine if as an integral part of the development process, the developer of the system, system component, or system service is required to produce an informal, descriptive top-level specification that specifies the interfaces to security-relevant hardware, software, and firmware in terms of exceptions;The principle of reduced complexity states that the system design is as simple and small as possible (see SA-8(7) ). A small and simple design is easier to understand and analyze and is also less prone to error (see AC-25, SA-8(13) ). The principle of reduced complexity applies to any aspect of a system, but it has particular importance for security due to the various analyses performed to obtain evidence about the emergent security property of the system. For such analyses to be successful, a small and simple design is essential. Application of the principle of reduced complexity contributes to the ability of system developers to understand the correctness and completeness of system security functions and facilitates the identification of potential vulnerabilities. The corollary of reduced complexity states that the simplicity of the system is directly related to the number of vulnerabilities it will contain. That is, simpler systems contain fewer vulnerabilities. An important benefit of reduced complexity is that it is easier to understand whether the security policy has been captured in the system design and that fewer vulnerabilities are likely to be introduced during engineering development. An additional benefit is that any such conclusion about correctness, completeness, and existence of vulnerabilities can be reached with a higher degree of assurance in contrast to conclusions reached in situations where the system design is inherently more complex.
","uuid":"2c59ac6f-da51-408b-a889-fd769a659db4","family":"System and Services Acquisition","parameters":[],"subControls":"","tests":[{"testId":"SA-17(05)(a)","uuid":"600f5aed-be92-49fa-a781-a6ac37c14f3f","test":"Determine if the developer of the system, system component, or system service is required to design and structure the security-relevant hardware, software, and firmware to use a complete, conceptually simple protection mechanism with precisely defined semantics;Applying the security design principles in SP 800-160-1 promotes complete, consistent, and comprehensive testing and evaluation of systems, system components, and services. The thoroughness of such testing contributes to the evidence produced to generate an effective assurance case or argument as to the trustworthiness of the system, system component, or service.
","uuid":"f0f57bf7-fba8-4404-b268-0e462bb5306c","family":"System and Services Acquisition","parameters":[],"subControls":"","tests":[{"testId":"SA-17(06)","uuid":"2e69bdb7-a799-447e-bb66-0eb05effbdbc","test":"Determine if the developer of the system, system component, or system service is required to structure security-relevant hardware, software, and firmware to facilitate testing.The principle of least privilege states that each component is allocated sufficient privileges to accomplish its specified functions but no more (see SA-8(14) ). Applying the principle of least privilege limits the scope of the component’s actions, which has two desirable effects. First, the security impact of a failure, corruption, or misuse of the system component results in a minimized security impact. Second, the security analysis of the component is simplified. Least privilege is a pervasive principle that is reflected in all aspects of the secure system design. Interfaces used to invoke component capability are available to only certain subsets of the user population, and component design supports a sufficiently fine granularity of privilege decomposition. For example, in the case of an audit mechanism, there may be an interface for the audit manager, who configures the audit settings; an interface for the audit operator, who ensures that audit data is safely collected and stored; and, finally, yet another interface for the audit reviewer, who only has a need to view the audit data that has been collected but no need to perform operations on that data.
In addition to its manifestations at the system interface, least privilege can be used as a guiding principle for the internal structure of the system itself. One aspect of internal least privilege is to construct modules so that only the elements encapsulated by the module are directly operated upon by the functions within the module. Elements external to a module that may be affected by the module’s operation are indirectly accessed through interaction (e.g., via a function call) with the module that contains those elements. Another aspect of internal least privilege is that the scope of a given module or component includes only those system elements that are necessary for its functionality, and the access modes to the elements (e.g., read, write) are minimal.
","uuid":"82fc6161-de2b-444c-bbf1-4b8f7809811e","family":"System and Services Acquisition","parameters":[],"subControls":"","tests":[{"testId":"SA-17(07)","uuid":"fffa1810-4871-4085-9633-2d4478c0b291","test":"Determine if the developer of the system, system component, or system service is required to structure security-relevant hardware, software, and firmware to facilitate controlling access with least privilege.Security resources that are distributed, located at different layers or in different system elements, or are implemented to support different aspects of trustworthiness can interact in unforeseen or incorrect ways. Adverse consequences can include cascading failures, interference, or coverage gaps. Coordination of the behavior of security resources (e.g., by ensuring that one patch is installed across all resources before making a configuration change that assumes that the patch is propagated) can avert such negative interactions.
","uuid":"0a2bb066-dbcd-4590-8287-211ee10f97f5","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"e16b19b5-98e3-4b0c-b2df-aabcd18cd53f","text":"critical systems","parameterId":"sa-17.08_odp.01","default":" [Assignment: organization defined critical systems] "},{"constraints":"","displayName":"","guidance":"","uuid":"776e93f7-b9bd-4e3a-b754-44aa1ee82e58","text":"capabilities","parameterId":"sa-17.08_odp.02","default":" [Assignment: organization defined capabilities] "}],"subControls":"","tests":[{"testId":"SA-17(08)","uuid":"f7a4b15a-ac8b-422d-bee5-1f8cf77b8129","test":"Determine if [SELECTED PARAMETER VALUE(S): critical systems ] are designed with coordinated behavior to implement [SELECTED PARAMETER VALUE(S): capabilities ].Design diversity is achieved by supplying the same requirements specification to multiple developers, each of whom is responsible for developing a variant of the system or system component that meets the requirements. Variants can be in software design, in hardware design, or in both hardware and a software design. Differences in the designs of the variants can result from developer experience (e.g., prior use of a design pattern), design style (e.g., when decomposing a required function into smaller tasks, determining what constitutes a separate task and how far to decompose tasks into sub-tasks), selection of libraries to incorporate into the variant, and the development environment (e.g., different design tools make some design patterns easier to visualize). Hardware design diversity includes making different decisions about what information to keep in analog form and what information to convert to digital form, transmitting the same information at different times, and introducing delays in sampling (temporal diversity). Design diversity is commonly used to support fault tolerance.
","uuid":"ef22622d-9a1d-4dfc-881a-742b75293d1e","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"c884f113-b56c-490c-b1e1-740ee5449814","text":"critical systems","parameterId":"sa-17.09_odp","default":" [Assignment: organization defined critical systems] "}],"subControls":"","tests":[{"testId":"SA-17(09)","uuid":"2ea37166-7900-4ad2-a697-e9cedfd2b461","test":"Determine if different designs are used for [SELECTED PARAMETER VALUE(S): critical systems ] to satisfy a common set of requirements or to provide equivalent functionality.Organizations determine that certain system components likely cannot be trusted due to specific threats to and vulnerabilities in those components for which there are no viable security controls to adequately mitigate risk. Reimplementation or custom development of such components may satisfy requirements for higher assurance and is carried out by initiating changes to system components (including hardware, software, and firmware) such that the standard attacks by adversaries are less likely to succeed. In situations where no alternative sourcing is available and organizations choose not to reimplement or custom develop critical system components, additional controls can be employed. Controls include enhanced auditing, restrictions on source code and system utility access, and protection from deletion of system and application files.
","uuid":"0bb844f1-c158-4e64-b276-b8528e01bcd2","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"96cfabdc-1f03-4141-81b1-f2ffeba2a27e","text":"critical system","parameterId":"sa-20_odp","default":" [Assignment: organization defined critical system] "}],"subControls":"","tests":[{"testId":"SA-20","uuid":"73b76429-69af-424a-8f52-d2799294de4b","test":"Determine if [SELECTED PARAMETER VALUE(S): critical system ] are reimplemented or custom-developed.Developer screening is directed at external developers. Internal developer screening is addressed by PS-3 . Because the system, system component, or system service may be used in critical activities essential to the national or economic security interests of the United States, organizations have a strong interest in ensuring that developers are trustworthy. The degree of trust required of developers may need to be consistent with that of the individuals who access the systems, system components, or system services once deployed. Authorization and personnel screening criteria include clearances, background checks, citizenship, and nationality. Developer trustworthiness may also include a review and analysis of company ownership and relationships that the company has with entities that may potentially affect the quality and reliability of the systems, components, or services being developed. Satisfying the required access authorizations and personnel screening criteria includes providing a list of all individuals who are authorized to perform development activities on the selected system, system component, or system service so that organizations can validate that the developer has satisfied the authorization and screening requirements.
","uuid":"71299626-9fa1-4c1f-976d-5bab87fd7bd4","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"4fe1dee2-45fc-4371-a3b3-29f05f69ec58","text":"system, systems component, or system service","parameterId":"sa-21_odp.01","default":" [Assignment: organization defined system, systems component, or system service] "},{"constraints":"","displayName":"","guidance":"","uuid":"a32bf78c-2a53-48ac-bef3-7852c09248e6","text":"official government duties","parameterId":"sa-21_odp.02","default":" [Assignment: organization defined official government duties] "},{"constraints":"","displayName":"","guidance":"","uuid":"82e23845-5bb8-4a72-bdf1-920ebc140468","text":"additional personnel screening criteria","parameterId":"sa-21_odp.03","default":" [Assignment: organization defined additional personnel screening criteria] "}],"subControls":"","tests":[{"testId":"SA-21a.","uuid":"44562b18-e43d-49ca-989f-667da4f4e5f4","test":"Determine if the developer of [SELECTED PARAMETER VALUE(S): system, systems component, or system service ] is required to have appropriate access authorizations as determined by assigned [SELECTED PARAMETER VALUE(S): official government duties ];Support for system components includes software patches, firmware updates, replacement parts, and maintenance contracts. An example of unsupported components includes when vendors no longer provide critical software patches or product updates, which can result in an opportunity for adversaries to exploit weaknesses in the installed components. Exceptions to replacing unsupported system components include systems that provide critical mission or business capabilities where newer technologies are not available or where the systems are so isolated that installing replacement components is not an option.
Alternative sources for support address the need to provide continued support for system components that are no longer supported by the original manufacturers, developers, or vendors when such components remain essential to organizational mission and business functions. If necessary, organizations can establish in-house support by developing customized patches for critical software components or, alternatively, obtain the services of external providers who provide ongoing support for the designated unsupported components through contractual relationships. Such contractual relationships can include open-source software value-added vendors. The increased risk of using unsupported system components can be mitigated, for example, by prohibiting the connection of such components to public or uncontrolled networks, or implementing other forms of isolation.
","uuid":"ea953155-28b4-4459-9411-e3996ed3aee9","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"f3e1083b-c0a1-4529-b7c0-fc381c22937a","text":"[Selection (one or more): in-house support; [(NESTED PARAMETER) Assignment for sa-22_odp.02: support from external providers]]","parameterId":"sa-22_odp.01","default":"[Selection (one or more): in-house support; [(NESTED PARAMETER) Assignment for sa-22_odp.02: support from external providers]]"},{"constraints":"","displayName":"","guidance":"","uuid":"84bdabe6-2d2d-4baa-afbf-edb111360f4c","text":"support from external providers","parameterId":"sa-22_odp.02","default":" [Assignment: organization defined support from external providers] "}],"subControls":"","tests":[{"testId":"SA-22a.","uuid":"bee1e4de-11fe-4f82-abf6-ecf4adb59d10","test":"Determine if system components are replaced when support for the components is no longer available from the developer, vendor, or manufacturer;It is often necessary for a system or system component that supports mission-essential services or functions to be enhanced to maximize the trustworthiness of the resource. Sometimes this enhancement is done at the design level. In other instances, it is done post-design, either through modifications of the system in question or by augmenting the system with additional components. For example, supplemental authentication or non-repudiation functions may be added to the system to enhance the identity of critical resources to other resources that depend on the organization-defined resources.
","uuid":"16a59fc0-6969-46e1-ba38-821929c932e4","family":"System and Services Acquisition","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"9030589a-1077-47a4-b398-5dda4d2439f8","text":"[Selection (one or more): design modification; augmentation; reconfiguration]","parameterId":"sa-23_odp.01","default":"[Selection (one or more): design modification; augmentation; reconfiguration]"},{"constraints":"","displayName":"","guidance":"","uuid":"8aa3f020-0d7e-4da2-92aa-1202f63d9024","text":"systems or system components","parameterId":"sa-23_odp.02","default":" [Assignment: organization defined systems or system components] "}],"subControls":"","tests":[{"testId":"SA-23","uuid":"266cca24-124e-4468-a26d-5c9f70b31d0c","test":"Determine if [SELECTED PARAMETER VALUE(S): [Selection (one or more): design modification; augmentation; reconfiguration] ] is employed on [SELECTED PARAMETER VALUE(S): systems or system components ] supporting essential services or functions to increase the trustworthiness in those systems or components.System and communications protection policy and procedures address the controls in the SC family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of system and communications protection policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission or business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to system and communications protection policy and procedures include assessment or audit findings, security incidents or breaches, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure.
","uuid":"ea1e5e29-0e12-46ec-a456-609996f31466","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"60379fd0-3573-4542-a719-b5c2a86cf2b8","text":"organization-defined personnel or roles","parameterId":"sc-1_prm_1","default":" [Assignment: organization-defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"24492cc9-40c9-4b65-b908-c226fde634a1","text":"personnel or roles","parameterId":"sc-01_odp.01","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"a66eb88e-5a8d-4a2b-b082-5bab9c80e249","text":"personnel or roles","parameterId":"sc-01_odp.02","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"7cdc0168-6ace-4812-a3d1-b6d94e8a8527","text":"[Selection (one or more): organization-level; mission/business-process-level; system-level]","parameterId":"sc-01_odp.03","default":"[Selection (one or more): organization-level; mission/business-process-level; system-level]"},{"constraints":"","displayName":"","guidance":"","uuid":"fecc58f8-51e2-49fe-a156-29868cdf5906","text":"official","parameterId":"sc-01_odp.04","default":" [Assignment: organization defined official] "},{"constraints":"","displayName":"","guidance":"","uuid":"d5816eea-bd2c-4cdb-9267-35e9f2c2258b","text":"frequency","parameterId":"sc-01_odp.05","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"c1d9f9cb-56a0-44e4-88ec-213cf1d64014","text":"events","parameterId":"sc-01_odp.06","default":" [Assignment: organization defined events] "},{"constraints":"","displayName":"","guidance":"","uuid":"8b65ed3b-726f-4555-8e90-96b17c03b31c","text":"frequency","parameterId":"sc-01_odp.07","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"86d40550-e0ee-4674-99ec-c2f2f736d874","text":"events","parameterId":"sc-01_odp.08","default":" [Assignment: organization defined events] "}],"subControls":"","tests":[{"testId":"SC-01a.[01]","uuid":"76dff272-e9e8-4666-b8e8-5e9fea6092d7","test":"Determine if a system and communications protection policy is developed and documented;System management functionality includes functions that are necessary to administer databases, network components, workstations, or servers. These functions typically require privileged user access. The separation of user functions from system management functions is physical or logical. Organizations may separate system management functions from user functions by using different computers, instances of operating systems, central processing units, or network addresses; by employing virtualization techniques; or some combination of these or other methods. Separation of system management functions from user functions includes web administrative interfaces that employ separate authentication methods for users of any other system resources. Separation of system and user functions may include isolating administrative interfaces on different domains and with additional access controls. The separation of system and user functionality can be achieved by applying the systems security engineering design principles in SA-8 , including SA-8(1), SA-8(3), SA-8(4), SA-8(10), SA-8(12), SA-8(13), SA-8(14) , and SA-8(18).
","uuid":"12c24f1e-d49e-40c2-8adf-860fc3f959d7","family":"System and Communications Protection","parameters":[],"subControls":"","tests":[{"testId":"SC-02","uuid":"291016c5-ce65-4c0f-b781-22f34eadf714","test":"Determine if user functionality, including user interface services, is separated from system management functionality.Preventing the presentation of system management functionality at interfaces to non-privileged users ensures that system administration options, including administrator privileges, are not available to the general user population. Restricting user access also prohibits the use of the grey-out option commonly used to eliminate accessibility to such information. One potential solution is to withhold system administration options until users establish sessions with administrator privileges.
","uuid":"1a1f78f5-6ebe-4948-8dbe-2ac630931947","family":"System and Communications Protection","parameters":[],"subControls":"","tests":[{"testId":"SC-02(01)","uuid":"3c167861-7f8f-4d5c-ae7a-f35a72291199","test":"Determine if the presentation of system management functionality is prevented at interfaces to non-privileged users.If a system is compromised, storing applications and software separately from state information about users’ interactions with an application may better protect individuals’ privacy.
","uuid":"1ef07fd1-5707-4d5c-af4a-0c34082072bc","family":"System and Communications Protection","parameters":[],"subControls":"","tests":[{"testId":"SC-02(02)","uuid":"482afadc-ddbd-4edf-8296-c582fc4977cf","test":"Determine if state information is stored separately from applications and software.Security functions are isolated from nonsecurity functions by means of an isolation boundary implemented within a system via partitions and domains. The isolation boundary controls access to and protects the integrity of the hardware, software, and firmware that perform system security functions. Systems implement code separation in many ways, such as through the provision of security kernels via processor rings or processor modes. For non-kernel code, security function isolation is often achieved through file system protections that protect the code on disk and address space protections that protect executing code. Systems can restrict access to security functions using access control mechanisms and by implementing least privilege capabilities. While the ideal is for all code within the defined security function isolation boundary to only contain security-relevant code, it is sometimes necessary to include nonsecurity functions as an exception. The isolation of security functions from nonsecurity functions can be achieved by applying the systems security engineering design principles in SA-8 , including SA-8(1), SA-8(3), SA-8(4), SA-8(10), SA-8(12), SA-8(13), SA-8(14) , and SA-8(18).
","uuid":"09d0d760-d84e-4cdb-af02-bd273c602df3","family":"System and Communications Protection","parameters":[],"subControls":"","tests":[{"testId":"SC-03","uuid":"0d32328e-d701-463f-b61b-e4a7391daf3f","test":"Determine if security functions are isolated from non-security functions.Hardware separation mechanisms include hardware ring architectures that are implemented within microprocessors and hardware-enforced address segmentation used to support logically distinct storage objects with separate attributes (i.e., readable, writeable).
","uuid":"834aaf8f-f417-4116-ba79-8254f48b6af6","family":"System and Communications Protection","parameters":[],"subControls":"","tests":[{"testId":"SC-03(01)","uuid":"0fbc12ca-0ff6-43c1-9289-0cc0fc1a0cbe","test":"Determine if hardware separation mechanisms are employed to implement security function isolation.Security function isolation occurs because of implementation. The functions can still be scanned and monitored. Security functions that are potentially isolated from access and flow control enforcement functions include auditing, intrusion detection, and malicious code protection functions.
","uuid":"da9ddb70-6800-4f98-a549-dd44e63243f2","family":"System and Communications Protection","parameters":[],"subControls":"","tests":[{"testId":"SC-03(02)[01]","uuid":"3e2dec6d-4e42-4713-b076-53c4b29f5763","test":"Determine if security functions enforcing access control are isolated from non-security functions;Where it is not feasible to achieve strict isolation of nonsecurity functions from security functions, it is necessary to take actions to minimize nonsecurity-relevant functions within the security function boundary. Nonsecurity functions contained within the isolation boundary are considered security-relevant because errors or malicious code in the software can directly impact the security functions of systems. The fundamental design objective is that the specific portions of systems that provide information security are of minimal size and complexity. Minimizing the number of nonsecurity functions in the security-relevant system components allows designers and implementers to focus only on those functions which are necessary to provide the desired security capability (typically access enforcement). By minimizing the nonsecurity functions within the isolation boundaries, the amount of code that is trusted to enforce security policies is significantly reduced, thus contributing to understandability.
","uuid":"a28f2481-38b6-4bb0-8377-04c31db4de7a","family":"System and Communications Protection","parameters":[],"subControls":"","tests":[{"testId":"SC-03(03)","uuid":"6059c0f6-da8d-480b-8121-9405211c15a3","test":"Determine if the number of non-security functions included within the isolation boundary containing security functions is minimized.The reduction of inter-module interactions helps to constrain security functions and manage complexity. The concepts of coupling and cohesion are important with respect to modularity in software design. Coupling refers to the dependencies that one module has on other modules. Cohesion refers to the relationship between functions within a module. Best practices in software engineering and systems security engineering rely on layering, minimization, and modular decomposition to reduce and manage complexity. This produces software modules that are highly cohesive and loosely coupled.
","uuid":"67943564-3147-47f7-bf9b-13225cb0404d","family":"System and Communications Protection","parameters":[],"subControls":"","tests":[{"testId":"SC-03(04)[01]","uuid":"07016efd-1c24-4b34-ab87-a964fcf0358e","test":"Determine if security functions are implemented as largely independent modules that maximize internal cohesiveness within modules;The implementation of layered structures with minimized interactions among security functions and non-looping layers (i.e., lower-layer functions do not depend on higher-layer functions) enables the isolation of security functions and the management of complexity.
","uuid":"688afcf4-06d7-4316-9447-b1422a12adc7","family":"System and Communications Protection","parameters":[],"subControls":"","tests":[{"testId":"SC-03(05)","uuid":"3f50d799-c707-44bd-a668-74a2786f6f26","test":"Determine if security functions are implemented 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.Preventing unauthorized and unintended information transfer via shared system resources stops information produced by the actions of prior users or roles (or the actions of processes acting on behalf of prior users or roles) from being available to current users or roles (or current processes acting on behalf of current users or roles) that obtain access to shared system resources after those resources have been released back to the system. Information in shared system resources also applies to encrypted representations of information. In other contexts, control of information in shared system resources is referred to as object reuse and residual information protection. Information in shared system resources does not address information remanence, which refers to the residual representation of data that has been nominally deleted; covert channels (including storage and timing channels), where shared system resources are manipulated to violate information flow restrictions; or components within systems for which there are only single users or roles.
","uuid":"61fddbed-74dc-4e92-9420-2edbfef0870d","family":"System and Communications Protection","parameters":[],"subControls":"","tests":[{"testId":"SC-04[01]","uuid":"c8d05186-f8b2-4f09-bd62-d57eff1e50fe","test":"Determine if unauthorized information transfer via shared system resources is prevented;Changes in processing levels can occur during multilevel or periods processing with information at different classification levels or security categories. It can also occur during serial reuse of hardware components at different classification levels. Organization-defined procedures can include approved sanitization processes for electronically stored information.
","uuid":"8b3d85c1-4d9e-456b-9038-86e0fde4e42b","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"73ce3944-c4eb-4c2f-933e-0cdc448c5e71","text":"procedures","parameterId":"sc-04.02_odp","default":" [Assignment: organization defined procedures] "}],"subControls":"","tests":[{"testId":"SC-04(02)","uuid":"6c1414fb-090b-4025-96f7-493d998425f4","test":"Determine if unauthorized information transfer via shared resources is prevented in accordance with [SELECTED PARAMETER VALUE(S): procedures ] when system processing explicitly switches between different information classification levels or security categories.Denial-of-service events may occur due to a variety of internal and external causes, such as an attack by an adversary or a lack of planning to support organizational needs with respect to capacity and bandwidth. Such attacks can occur across a wide range of network protocols (e.g., IPv4, IPv6). A variety of technologies are available to limit or eliminate the origination and effects of denial-of-service events. For example, boundary protection devices can filter certain types of packets to protect system components on internal networks from being directly affected by or the source of denial-of-service attacks. Employing increased network capacity and bandwidth combined with service redundancy also reduces the susceptibility to denial-of-service events.
","uuid":"3c3d0a34-3ddd-4ab5-8d4f-7b50dc108017","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"2ae6573f-0139-4d85-9ad6-2514d3f2a20e","text":"types of denial-of-service events","parameterId":"sc-05_odp.01","default":" [Assignment: organization defined types of denial-of-service events] "},{"constraints":"","displayName":"","guidance":"","uuid":"06b10879-5b17-4067-82ad-d586aae93efe","text":"[Selection: protect against; limit]","parameterId":"sc-05_odp.02","default":"[Selection: protect against; limit]"},{"constraints":"","displayName":"","guidance":"","uuid":"4f0ad693-035a-4953-9d66-355469a01faf","text":"controls by type of denial-of-service event","parameterId":"sc-05_odp.03","default":" [Assignment: organization defined controls by type of denial-of-service event] "}],"subControls":"","tests":[{"testId":"SC-05a.","uuid":"3b6626a5-1c03-4044-9fd8-93794bfbde31","test":"Determine if the effects of [SELECTED PARAMETER VALUE(S): types of denial-of-service events ] are [SELECTED PARAMETER VALUE(S): [Selection: protect against; limit] ];Restricting the ability of individuals to launch denial-of-service attacks requires the mechanisms commonly used for such attacks to be unavailable. Individuals of concern include hostile insiders or external adversaries who have breached or compromised the system and are using it to launch a denial-of-service attack. Organizations can restrict the ability of individuals to connect and transmit arbitrary information on the transport medium (i.e., wired networks, wireless networks, spoofed Internet protocol packets). Organizations can also limit the ability of individuals to use excessive system resources. Protection against individuals having the ability to launch denial-of-service attacks may be implemented on specific systems or boundary devices that prohibit egress to potential target systems.
","uuid":"089dfba3-3597-458d-bdb0-1fb4d235135b","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"c45053e9-2e46-4325-b708-cc6852961d19","text":"denial-of-service attacks","parameterId":"sc-05.01_odp","default":" [Assignment: organization defined denial-of-service attacks] "}],"subControls":"","tests":[{"testId":"SC-05(01)","uuid":"1a152f8c-ede3-4aeb-9b4c-ef7650713be3","test":"Determine if the ability of individuals to launch [SELECTED PARAMETER VALUE(S): denial-of-service attacks ] against other systems is restricted.Managing capacity ensures that sufficient capacity is available to counter flooding attacks. Managing capacity includes establishing selected usage priorities, quotas, partitioning, or load balancing.
","uuid":"541d4ed1-814e-4969-9471-83ef18e741d3","family":"System and Communications Protection","parameters":[],"subControls":"","tests":[{"testId":"SC-05(02)","uuid":"ce107194-246c-4585-bd60-2e77772d03c2","test":"Determine if capacity, bandwidth, or other redundancies to limit the effects of information flooding denial-of-service attacks are managed.Organizations consider the utilization and capacity of system resources when managing risk associated with a denial of service due to malicious attacks. Denial-of-service attacks can originate from external or internal sources. System resources that are sensitive to denial of service include physical disk storage, memory, and CPU cycles. Techniques used to prevent denial-of-service attacks related to storage utilization and capacity include instituting disk quotas, configuring systems to automatically alert administrators when specific storage capacity thresholds are reached, using file compression technologies to maximize available storage space, and imposing separate partitions for system and user data.
","uuid":"1760c442-aff3-44de-b825-b515b4251215","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"1d313a1d-d0ad-4ba4-b716-71628e90c08f","text":"monitoring tools","parameterId":"sc-05.03_odp.01","default":" [Assignment: organization defined monitoring tools] "},{"constraints":"","displayName":"","guidance":"","uuid":"330ac7da-2f54-4f49-8aaf-b1b350509b6b","text":"system resources","parameterId":"sc-05.03_odp.02","default":" [Assignment: organization defined system resources] "}],"subControls":"","tests":[{"testId":"SC-05(03)(a)","uuid":"fe58a479-e434-41a2-af84-36dc66d3f418","test":"Determine if [SELECTED PARAMETER VALUE(S): monitoring tools ] are employed to detect indicators of denial-of-service attacks against or launched from the system;Priority protection prevents lower-priority processes from delaying or interfering with the system that services higher-priority processes. Quotas prevent users or processes from obtaining more than predetermined amounts of resources.
","uuid":"2960bbe1-f9c5-4b71-b7e7-b434716dc8b3","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"da5ab052-0cbe-457e-abab-a2661325076a","text":"resources","parameterId":"sc-06_odp.01","default":" [Assignment: organization defined resources] "},{"constraints":"","displayName":"","guidance":"","uuid":"1a632b48-5d66-432e-9f87-00d72970b698","text":"[Selection (one or more): priority; quota; [(NESTED PARAMETER) Assignment for sc-06_odp.03: controls]]","parameterId":"sc-06_odp.02","default":"[Selection (one or more): priority; quota; [(NESTED PARAMETER) Assignment for sc-06_odp.03: controls]]"},{"constraints":"","displayName":"","guidance":"","uuid":"11a8512a-b35c-408c-9094-d8196af56bd0","text":"controls","parameterId":"sc-06_odp.03","default":" [Assignment: organization defined controls] "}],"subControls":"","tests":[{"testId":"SC-06","uuid":"32b114b2-e044-4a9e-9967-cc1cfd6df00b","test":"Determine if the availability of resources is protected by allocating [SELECTED PARAMETER VALUE(S): resources ] by [SELECTED PARAMETER VALUE(S): [Selection (one or more): priority; quota; [(NESTED PARAMETER) Assignment for sc-06_odp.03: controls]] ].Managed interfaces include gateways, routers, firewalls, guards, network-based malicious code analysis, virtualization systems, or encrypted tunnels implemented within a security architecture. Subnetworks that are physically or logically separated from internal networks are referred to as demilitarized zones or DMZs. Restricting or prohibiting interfaces within organizational systems includes restricting external web traffic to designated web servers within managed interfaces, prohibiting external traffic that appears to be spoofing internal addresses, and prohibiting internal traffic that appears to be spoofing external addresses. SP 800-189 provides additional information on source address validation techniques to prevent ingress and egress of traffic with spoofed addresses. Commercial telecommunications services are provided by network components and consolidated management systems shared by customers. These services may also include third party-provided access lines and other service elements. Such services may represent sources of increased risk despite contract security provisions. Boundary protection may be implemented as a common control for all or part of an organizational network such that the boundary to be protected is greater than a system-specific boundary (i.e., an authorization boundary).
","uuid":"4e721639-a78d-4152-ae84-08dd757643c6","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"66a8e2c5-e8ea-41cd-9f28-29bfc784d6cf","text":"[Selection: physically; logically]","parameterId":"sc-07_odp","default":"[Selection: physically; logically]"}],"subControls":"","tests":[{"testId":"SC-07a.[01]","uuid":"0d16841e-fc88-4b3d-9908-8b017a9d175d","test":"Determine if communications at external managed interfaces to the system are monitored;Limiting the number of external network connections facilitates monitoring of inbound and outbound communications traffic. The Trusted Internet Connection DHS TIC initiative is an example of a federal guideline that requires limits on the number of external network connections. Limiting the number of external network connections to the system is important during transition periods from older to newer technologies (e.g., transitioning from IPv4 to IPv6 network protocols). Such transitions may require implementing the older and newer technologies simultaneously during the transition period and thus increase the number of access points to the system.
","uuid":"de3f2133-d612-416f-b09e-acd4aba40332","family":"System and Communications Protection","parameters":[],"subControls":"","tests":[{"testId":"SC-07(03)","uuid":"37b971e6-f8d8-4379-b029-b441b3ce0d61","test":"Determine if the number of external network connections to the system is limited.External telecommunications services can provide data and/or voice communications services. Examples of control plane traffic include Border Gateway Protocol (BGP) routing, Domain Name System (DNS), and management protocols. See SP 800-189 for additional information on the use of the resource public key infrastructure (RPKI) to protect BGP routes and detect unauthorized BGP announcements.
","uuid":"86a9603e-233b-43df-8dc2-68784bdfc88d","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"b80d89e0-f85f-48d4-b4b2-9dae9d342624","text":"frequency","parameterId":"sc-07.04_odp","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"SC-07(04)(a)","uuid":"5fc0ff2b-1689-4c7b-8304-129f654af3d0","test":"Determine if a managed interface is implemented for each external telecommunication service;Denying by default and allowing by exception applies to inbound and outbound network communications traffic. A deny-all, permit-by-exception network communications traffic policy ensures that only those system connections that are essential and approved are allowed. Deny by default, allow by exception also applies to a system that is connected to an external system.
","uuid":"acb123c4-2445-4382-9bc0-892b77b08732","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"22ac8660-bb06-404e-b2f6-70f1f418de44","text":"[Selection (one or more): at managed interfaces; for [(NESTED PARAMETER) Assignment for sc-07.05_odp.02: systems]]","parameterId":"sc-07.05_odp.01","default":"[Selection (one or more): at managed interfaces; for [(NESTED PARAMETER) Assignment for sc-07.05_odp.02: systems]]"},{"constraints":"","displayName":"","guidance":"","uuid":"59c7799b-6e02-4e53-abe6-417cf1b47968","text":"systems","parameterId":"sc-07.05_odp.02","default":" [Assignment: organization defined systems] "}],"subControls":"","tests":[{"testId":"SC-07(05)[01]","uuid":"fe1826cf-fb29-4117-b362-548a9bd428f7","test":"Determine if network communications traffic is denied by default [SELECTED PARAMETER VALUE(S): [Selection (one or more): at managed interfaces; for [(NESTED PARAMETER) Assignment for sc-07.05_odp.02: systems]] ];Split tunneling is the process of allowing a remote user or device to establish a non-remote connection with a system and simultaneously communicate via some other connection to a resource in an external network. This method of network access enables a user to access remote devices and simultaneously, access uncontrolled networks. Split tunneling might be desirable by remote users to communicate with local system resources, such as printers or file servers. However, split tunneling can facilitate unauthorized external connections, making the system vulnerable to attack and to exfiltration of organizational information. Split tunneling can be prevented by disabling configuration settings that allow such capability in remote devices and by preventing those configuration settings from being configurable by users. Prevention can also be achieved by the detection of split tunneling (or of configuration settings that allow split tunneling) in the remote device, and by prohibiting the connection if the remote device is using split tunneling. A virtual private network (VPN) can be used to securely provision a split tunnel. A securely provisioned VPN includes locking connectivity to exclusive, managed, and named environments, or to a specific set of pre-approved addresses, without user control.
","uuid":"e02021a1-039b-439c-a3ab-3a60b9f4f50e","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"6804f819-b4f2-45eb-a345-e25593c59c88","text":"safeguards","parameterId":"sc-07.07_odp","default":" [Assignment: organization defined safeguards] "}],"subControls":"","tests":[{"testId":"SC-07(07)","uuid":"d839faaf-ff3a-4fbd-8914-dfa191d729d3","test":"Determine if split tunneling is prevented for remote devices connecting to organizational systems unless the split tunnel is securely provisioned using [SELECTED PARAMETER VALUE(S): safeguards ].External networks are networks outside of organizational control. A proxy server is a server (i.e., system or application) that acts as an intermediary for clients requesting system resources from non-organizational or other organizational servers. System resources that may be requested include files, connections, web pages, or services. Client requests established through a connection to a proxy server are assessed to manage complexity and provide additional protection by limiting direct connectivity. Web content filtering devices are one of the most common proxy servers that provide access to the Internet. Proxy servers can support the logging of Transmission Control Protocol sessions and the blocking of specific Uniform Resource Locators, Internet Protocol addresses, and domain names. Web proxies can be configured with organization-defined lists of authorized and unauthorized websites. Note that proxy servers may inhibit the use of virtual private networks (VPNs) and create the potential for man-in-the-middle
attacks (depending on the implementation).
Detecting outgoing communications traffic from internal actions that may pose threats to external systems is known as extrusion detection. Extrusion detection is carried out within the system at managed interfaces. Extrusion detection includes the analysis of incoming and outgoing communications traffic while searching for indications of internal threats to the security of external systems. Internal threats to external systems include traffic indicative of denial-of-service attacks, traffic with spoofed source addresses, and traffic that contains malicious code. Organizations have criteria to determine, update, and manage identified threats related to extrusion detection.
","uuid":"e18db108-24e3-4281-9be7-48c2ab981788","family":"System and Communications Protection","parameters":[],"subControls":"","tests":[{"testId":"SC-07(09)(a)[01]","uuid":"ec2b21ec-6403-46c9-8202-838ab0c3466a","test":"Determine if outgoing communications traffic posing a threat to external systems is detected;Prevention of exfiltration applies to both the intentional and unintentional exfiltration of information. Techniques used to prevent the exfiltration of information from systems may be implemented at internal endpoints, external boundaries, and across managed interfaces and include adherence to protocol formats, monitoring for beaconing activity from systems, disconnecting external network interfaces except when explicitly needed, employing traffic profile analysis to detect deviations from the volume and types of traffic expected, call backs to command and control centers, conducting penetration testing, monitoring for steganography, disassembling and reassembling packet headers, and using data loss and data leakage prevention tools. Devices that enforce strict adherence to protocol formats include deep packet inspection firewalls and Extensible Markup Language (XML) gateways. The devices verify adherence to protocol formats and specifications at the application layer and identify vulnerabilities that cannot be detected by devices that operate at the network or transport layers. The prevention of exfiltration is similar to data loss prevention or data leakage prevention and is closely associated with cross-domain solutions and system guards that enforce information flow requirements.
","uuid":"4f1bc08d-ff4f-43ed-a4e0-11b3f1587e53","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"d242c232-4dfc-4a75-a4cb-474cfb196376","text":"frequency","parameterId":"sc-07.10_odp","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"SC-07(10)(a)","uuid":"daccd90b-428f-4201-99e6-06b3aed99040","test":"Determine if the exfiltration of information is prevented;General source address validation techniques are applied to restrict the use of illegal and unallocated source addresses as well as source addresses that should only be used within the system. The restriction of incoming communications traffic provides determinations that source and destination address pairs represent authorized or allowed communications. Determinations can be based on several factors, including the presence of such address pairs in the lists of authorized or allowed communications, the absence of such address pairs in lists of unauthorized or disallowed pairs, or meeting more general rules for authorized or allowed source and destination pairs. Strong authentication of network addresses is not possible without the use of explicit security protocols, and thus, addresses can often be spoofed. Further, identity-based incoming traffic restriction methods can be employed, including router access control lists and firewall rules.
","uuid":"f7099105-4612-4da1-b4f6-8184956b3aba","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"28ca6948-4c95-443c-a011-bb817eac4e47","text":"authorized sources","parameterId":"sc-07.11_odp.01","default":" [Assignment: organization defined authorized sources] "},{"constraints":"","displayName":"","guidance":"","uuid":"44eed881-b9b9-44de-a8aa-26d04a6d1098","text":"authorized destinations","parameterId":"sc-07.11_odp.02","default":" [Assignment: organization defined authorized destinations] "}],"subControls":"","tests":[{"testId":"SC-07(11)","uuid":"6825aca5-f324-46d6-a6af-6fec4c22157c","test":"Determine if only incoming communications from [SELECTED PARAMETER VALUE(S): authorized sources ] are allowed to be routed to [SELECTED PARAMETER VALUE(S): authorized destinations ].Host-based boundary protection mechanisms include host-based firewalls. System components that employ host-based boundary protection mechanisms include servers, workstations, notebook computers, and mobile devices.
","uuid":"3f47f4d5-d7b3-438d-bee5-764bd577e588","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"9d79178f-8c6e-4bb4-9c60-ade2aa9ee085","text":"host-based boundary protection mechanisms","parameterId":"sc-07.12_odp.01","default":" [Assignment: organization defined host-based boundary protection mechanisms] "},{"constraints":"","displayName":"","guidance":"","uuid":"6b88db67-2f10-4283-9ea7-37b5159f2a07","text":"system components","parameterId":"sc-07.12_odp.02","default":" [Assignment: organization defined system components] "}],"subControls":"","tests":[{"testId":"SC-07(12)","uuid":"af595890-a478-4515-8213-2cb0bc48f693","test":"Determine if [SELECTED PARAMETER VALUE(S): host-based boundary protection mechanisms ] are implemented at [SELECTED PARAMETER VALUE(S): system components ].Physically separate subnetworks with managed interfaces are useful in isolating computer network defenses from critical operational processing networks to prevent adversaries from discovering the analysis and forensics techniques employed by organizations.
","uuid":"720dfa61-8ef6-4e3b-85a2-02b3f0554052","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"f6de7cf0-8c83-49eb-aaba-7ffce579537e","text":"information security tools, mechanisms, and support components","parameterId":"sc-07.13_odp","default":" [Assignment: organization defined information security tools, mechanisms, and support components] "}],"subControls":"","tests":[{"testId":"SC-07(13)","uuid":"10d68136-4964-4ee3-a8c6-96194048617c","test":"Determine if [SELECTED PARAMETER VALUE(S): information security tools, mechanisms, and support components ] are isolated from other internal system components by implementing physically separate subnetworks with managed interfaces to other components of the system.Systems that operate at different security categories or classification levels may share common physical and environmental controls, since the systems may share space within the same facilities. In practice, it is possible that these separate systems may share common equipment rooms, wiring closets, and cable distribution paths. Protection against unauthorized physical connections can be achieved by using clearly identified and physically separated cable trays, connection frames, and patch panels for each side of managed interfaces with physical access controls that enforce limited authorized access to these items.
","uuid":"d9f4317d-4816-4cd3-b65f-96b50ca91207","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"72d4aeb4-a63d-4343-8172-28516b3b18b5","text":"managed interfaces","parameterId":"sc-07.14_odp","default":" [Assignment: organization defined managed interfaces] "}],"subControls":"","tests":[{"testId":"SC-07(14)","uuid":"81e19fe2-655f-4d59-920e-b2fa8b021892","test":"Determine if [SELECTED PARAMETER VALUE(S): managed interfaces ] are protected against unauthorized physical connections.Privileged access provides greater accessibility to system functions, including security functions. Adversaries attempt to gain privileged access to systems through remote access to cause adverse mission or business impacts, such as by exfiltrating information or bringing down a critical system capability. Routing networked, privileged access requests through a dedicated, managed interface further restricts privileged access for increased access control and auditing.
","uuid":"33049be2-2b2b-41dc-8192-00c6e6f5f6e9","family":"System and Communications Protection","parameters":[],"subControls":"","tests":[{"testId":"SC-07(15)[01]","uuid":"25802787-b5de-45bc-a9b7-35892fe40947","test":"Determine if networked, privileged accesses are routed through a dedicated, managed interface for purposes of access control;Preventing the discovery of system components representing a managed interface helps protect network addresses of those components from discovery through common tools and techniques used to identify devices on networks. Network addresses are not available for discovery and require prior knowledge for access. Preventing the discovery of components and devices can be accomplished by not publishing network addresses, using network address translation, or not entering the addresses in domain name systems. Another prevention technique is to periodically change network addresses.
","uuid":"29e893c4-7cdd-46f4-933c-25b3b1a1d621","family":"System and Communications Protection","parameters":[],"subControls":"","tests":[{"testId":"SC-07(16)","uuid":"53a02343-1dc7-4e59-93b1-b2afe7a6d755","test":"Determine if the discovery of specific system components that represent a managed interface is prevented.System components that enforce protocol formats include deep packet inspection firewalls and XML gateways. The components verify adherence to protocol formats and specifications at the application layer and identify vulnerabilities that cannot be detected by devices operating at the network or transport layers.
","uuid":"afc37208-2357-4ae9-a7c6-5e4be2f5921c","family":"System and Communications Protection","parameters":[],"subControls":"","tests":[{"testId":"SC-07(17)","uuid":"35d08515-7ac3-4911-8187-5872e0884d67","test":"Determine if adherence to protocol formats is enforced.Fail secure is a condition achieved by employing mechanisms to ensure that in the event of operational failures of boundary protection devices at managed interfaces, systems do not enter into unsecure states where intended security properties no longer hold. Managed interfaces include routers, firewalls, and application gateways that reside on protected subnetworks (commonly referred to as demilitarized zones). Failures of boundary protection devices cannot lead to or cause information external to the devices to enter the devices nor can failures permit unauthorized information releases.
","uuid":"ece755cb-f3c2-432b-a1ae-5c32137c501c","family":"System and Communications Protection","parameters":[],"subControls":"","tests":[{"testId":"SC-07(18)","uuid":"fcedf207-c1e0-4e83-a3ea-81d5e6aad0c7","test":"Determine if systems are prevented from entering unsecure states in the event of an operational failure of a boundary protection device.Communication clients independently configured by end users and external service providers include instant messaging clients and video conferencing software and applications. Traffic blocking does not apply to communication clients that are configured by organizations to perform authorized functions.
","uuid":"c44f6ce2-0a32-4d81-b9fe-53fa8802c606","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"b57da39e-e98b-4ad2-8d22-5f03f4c5157d","text":"communication clients","parameterId":"sc-07.19_odp","default":" [Assignment: organization defined communication clients] "}],"subControls":"","tests":[{"testId":"SC-07(19)[01]","uuid":"81c473dd-3546-4d0d-91c3-c5e572d4d4bb","test":"Determine if inbound communications traffic is blocked between [SELECTED PARAMETER VALUE(S): communication clients ] that are independently configured by end users and external service providers;The capability to dynamically isolate certain internal system components is useful when it is necessary to partition or separate system components of questionable origin from components that possess greater trustworthiness. Component isolation reduces the attack surface of organizational systems. Isolating selected system components can also limit the damage from successful attacks when such attacks occur.
","uuid":"e5c249ce-283d-4394-a2cc-12935b789e01","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"d7fe0550-ddb4-4a35-a714-2daa42e991ce","text":"system components","parameterId":"sc-07.20_odp","default":" [Assignment: organization defined system components] "}],"subControls":"","tests":[{"testId":"SC-07(20)","uuid":"e9332ea1-e809-4995-a3c6-ba50e19fb07a","test":"Determine if the capability to dynamically isolate [SELECTED PARAMETER VALUE(S): system components ] from other system components is provided.Organizations can isolate system components that perform different mission or business functions. Such isolation limits unauthorized information flows among system components and provides the opportunity to deploy greater levels of protection for selected system components. Isolating system components with boundary protection mechanisms provides the capability for increased protection of individual system components and to more effectively control information flows between those components. Isolating system components provides enhanced protection that limits the potential harm from hostile cyber-attacks and errors. The degree of isolation varies depending upon the mechanisms chosen. Boundary protection mechanisms include routers, gateways, and firewalls that separate system components into physically separate networks or subnetworks; cross-domain devices that separate subnetworks; virtualization techniques; and the encryption of information flows among system components using distinct encryption keys.
","uuid":"5c2f9ee3-8cf7-4e75-bfde-b4ff04009567","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"c5515da9-3884-4eca-95b0-6c47301916b3","text":"system components","parameterId":"sc-07.21_odp.01","default":" [Assignment: organization defined system components] "},{"constraints":"","displayName":"","guidance":"","uuid":"d1aa3f34-d12d-440d-b909-7fcee62e0f89","text":"missions and/or business functions","parameterId":"sc-07.21_odp.02","default":" [Assignment: organization defined missions and/or business functions] "}],"subControls":"","tests":[{"testId":"SC-07(21)","uuid":"37519e61-8504-4841-98d1-993d443e5f57","test":"Determine if boundary protection mechanisms are employed to isolate [SELECTED PARAMETER VALUE(S): system components ] supporting [SELECTED PARAMETER VALUE(S): missions and/or business functions ].The decomposition of systems into subnetworks (i.e., subnets) helps to provide the appropriate level of protection for network connections to different security domains that contain information with different security categories or classification levels.
","uuid":"71b3c2e3-6fb9-472e-a615-d17ac5132e9a","family":"System and Communications Protection","parameters":[],"subControls":"","tests":[{"testId":"SC-07(22)","uuid":"d71b4e4f-7480-4a8a-bcb9-94949f2faaa8","test":"Determine if separate network addresses are implemented to connect to systems in different security domains.Disabling feedback to senders when there is a failure in protocol validation format prevents adversaries from obtaining information that would otherwise be unavailable.
","uuid":"7e9e9212-c863-4611-9812-e3797affed80","family":"System and Communications Protection","parameters":[],"subControls":"","tests":[{"testId":"SC-07(23)","uuid":"d13cad85-1376-4c65-aea2-bcbbe1d0ae87","test":"Determine if feedback to senders is disabled on protocol format validation failure.Managing the processing of personally identifiable information is an important aspect of protecting an individual’s privacy. Applying, monitoring for, and documenting exceptions to processing rules ensure that personally identifiable information is processed only in accordance with established privacy requirements.
","uuid":"afc00ded-0672-4f78-bb3b-fd65a241f281","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"649944ab-139c-4d09-b211-71c46b20aa19","text":"processing rules","parameterId":"sc-07.24_odp","default":" [Assignment: organization defined processing rules] "}],"subControls":"","tests":[{"testId":"SC-07(24)(a)","uuid":"8282ff5f-886d-4d64-83d2-d891cb638c51","test":"Determine if [SELECTED PARAMETER VALUE(S): processing rules ] are applied to data elements of personally identifiable information on systems that process personally identifiable information;A direct connection is a dedicated physical or virtual connection between two or more systems. Organizations typically do not have complete control over external networks, including the Internet. Boundary protection devices (e.g., firewalls, gateways, and routers) mediate communications and information flows between unclassified national security systems and external networks.
","uuid":"f49ee47f-cfa7-45e3-82e5-2510288524ca","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"a40be680-d241-4a6c-bba9-696c01d40ce6","text":"unclassified national security system","parameterId":"sc-07.25_odp.01","default":" [Assignment: organization defined unclassified national security system] "},{"constraints":"","displayName":"","guidance":"","uuid":"098b424d-403a-4991-b8a6-9411cdb0a2a8","text":"boundary protection device","parameterId":"sc-07.25_odp.02","default":" [Assignment: organization defined boundary protection device] "}],"subControls":"","tests":[{"testId":"SC-07(25)","uuid":"79f13113-bf07-49fd-a295-bc05b5beeffe","test":"Determine if the direct connection of [SELECTED PARAMETER VALUE(S): unclassified national security system ] to an external network without the use of [SELECTED PARAMETER VALUE(S): boundary protection device ] is prohibited.A direct connection is a dedicated physical or virtual connection between two or more systems. Organizations typically do not have complete control over external networks, including the Internet. Boundary protection devices (e.g., firewalls, gateways, and routers) mediate communications and information flows between classified national security systems and external networks. In addition, approved boundary protection devices (typically managed interface or cross-domain systems) provide information flow enforcement from systems to external networks.
","uuid":"3ab8c791-f6a6-4019-89c1-5d352276619d","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"8ac91fe9-0980-4b39-9ded-3bf810c3dc5d","text":"boundary protection device","parameterId":"sc-07.26_odp","default":" [Assignment: organization defined boundary protection device] "}],"subControls":"","tests":[{"testId":"SC-07(26)","uuid":"3cd0f7a4-81a6-45d9-9d6c-692a8435a5ac","test":"Determine if the direct connection of classified national security system to an external network without the use of a [SELECTED PARAMETER VALUE(S): boundary protection device ] is prohibited.A direct connection is a dedicated physical or virtual connection between two or more systems. Organizations typically do not have complete control over external networks, including the Internet. Boundary protection devices (e.g., firewalls, gateways, and routers) mediate communications and information flows between unclassified non-national security systems and external networks.
","uuid":"127cfc9d-b8ee-450e-82fa-35e4e1199095","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"00b733b1-b41a-49cd-9543-6afb93c5ef19","text":"unclassified, non-national security system","parameterId":"sc-07.27_odp.01","default":" [Assignment: organization defined unclassified, non-national security system] "},{"constraints":"","displayName":"","guidance":"","uuid":"6e1ae65f-e6f0-4610-90bb-df3d16f74006","text":"boundary protection device","parameterId":"sc-07.27_odp.02","default":" [Assignment: organization defined boundary protection device] "}],"subControls":"","tests":[{"testId":"SC-07(27)","uuid":"aa21fbc2-0c0d-458b-9e1a-6caedb7322c6","test":"Determine if the direct connection of [SELECTED PARAMETER VALUE(S): unclassified, non-national security system ] to an external network without the use of a [SELECTED PARAMETER VALUE(S): boundary protection device ] is prohibited.A direct connection is a dedicated physical or virtual connection between two or more systems. A public network is a network accessible to the public, including the Internet and organizational extranets with public access.
","uuid":"5dafa6bf-4d45-4b36-a215-15289c793e35","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"ca002fb0-3839-4c85-b298-b4de9d2ad2cd","text":"system","parameterId":"sc-07.28_odp","default":" [Assignment: organization defined system] "}],"subControls":"","tests":[{"testId":"SC-07(28)","uuid":"feda4ec3-3be4-4caf-9e6f-dd25e748a1de","test":"Determine if the direct connection of the [SELECTED PARAMETER VALUE(S): system ] to a public network is prohibited.Separating critical system components and functions from other noncritical system components and functions through separate subnetworks may be necessary to reduce susceptibility to a catastrophic or debilitating breach or compromise that results in system failure. For example, physically separating the command and control function from the in-flight entertainment function through separate subnetworks in a commercial aircraft provides an increased level of assurance in the trustworthiness of critical system functions.
","uuid":"aed20b9e-e40f-4fb0-a621-18f56da797f2","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"d88bbde1-3681-4841-8442-ae560bb94a99","text":"[Selection: physically; logically]","parameterId":"sc-07.29_odp.01","default":"[Selection: physically; logically]"},{"constraints":"","displayName":"","guidance":"","uuid":"e400d2f3-071c-40ea-9a23-86649e2a2062","text":"critical system components and functions","parameterId":"sc-07.29_odp.02","default":" [Assignment: organization defined critical system components and functions] "}],"subControls":"","tests":[{"testId":"SC-07(29)","uuid":"2b49e199-c4b3-455d-80e4-d066a779d0c2","test":"Determine if subnetworks are separated [SELECTED PARAMETER VALUE(S): [Selection: physically; logically] ] to isolate [SELECTED PARAMETER VALUE(S): critical system components and functions ].Protecting the confidentiality and integrity of transmitted information applies to internal and external networks as well as any system components that can transmit information, including servers, notebook computers, desktop computers, mobile devices, printers, copiers, scanners, facsimile machines, and radios. Unprotected communication paths are exposed to the possibility of interception and modification. Protecting the confidentiality and integrity of information can be accomplished by physical or logical means. Physical protection can be achieved by using protected distribution systems. A protected distribution system is a wireline or fiber-optics telecommunications system that includes terminals and adequate electromagnetic, acoustical, electrical, and physical controls to permit its use for the unencrypted transmission of classified information. Logical protection can be achieved by employing encryption techniques.
Organizations that rely on commercial providers who offer transmission services as commodity services rather than as fully dedicated services may find it difficult to obtain the necessary assurances regarding the implementation of needed controls for transmission confidentiality and integrity. In such situations, organizations determine what types of confidentiality or integrity services are available in standard, commercial telecommunications service packages. If it is not feasible to obtain the necessary controls and assurances of control effectiveness through appropriate contracting vehicles, organizations can implement appropriate compensating controls.
","uuid":"862a06ea-c93b-42da-82ad-8f460f9ff195","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"310036cd-6292-4d24-ab91-f68252b45cf5","text":"[Selection (one or more): confidentiality; integrity]","parameterId":"sc-08_odp","default":"[Selection (one or more): confidentiality; integrity]"}],"subControls":"","tests":[{"testId":"SC-08","uuid":"ff4b8e44-d270-4eaa-856d-cc591b7099a6","test":"Determine if the [SELECTED PARAMETER VALUE(S): [Selection (one or more): confidentiality; integrity] ] of transmitted information is/are protected.Encryption protects information from unauthorized disclosure and modification during transmission. Cryptographic mechanisms that protect the confidentiality and integrity of information during transmission include TLS and IPSec. Cryptographic mechanisms used to protect information integrity include cryptographic hash functions that have applications in digital signatures, checksums, and message authentication codes.
","uuid":"100bd46e-2a60-43f0-9ea7-62ee55589200","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"1ef0edb9-459a-4328-861a-5f876f48dd93","text":"[Selection (one or more): prevent unauthorized disclosure of information; detect changes to information]","parameterId":"sc-08.01_odp","default":"[Selection (one or more): prevent unauthorized disclosure of information; detect changes to information]"}],"subControls":"","tests":[{"testId":"SC-08(01)","uuid":"902dc153-bad6-431d-8338-e3c2b07f4cd6","test":"Determine if cryptographic mechanisms are implemented to [SELECTED PARAMETER VALUE(S): [Selection (one or more): prevent unauthorized disclosure of information; detect changes to information] ] during transmission.Information can be unintentionally or maliciously disclosed or modified during preparation for transmission or during reception, including during aggregation, at protocol transformation points, and during packing and unpacking. Such unauthorized disclosures or modifications compromise the confidentiality or integrity of the information.
","uuid":"357ccb85-9e25-4dac-9697-7f71cdf3e654","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"0009db91-3bf9-4d98-bf6d-e2051631be66","text":"[Selection (one or more): confidentiality; integrity]","parameterId":"sc-08.02_odp","default":"[Selection (one or more): confidentiality; integrity]"}],"subControls":"","tests":[{"testId":"SC-08(02)[01]","uuid":"f0364898-789e-4bd0-b433-bcc67b5d8378","test":"Determine if information [SELECTED PARAMETER VALUE(S): [Selection (one or more): confidentiality; integrity] ] is/are maintained during preparation for transmission;Cryptographic protection for message externals addresses protection from the unauthorized disclosure of information. Message externals include message headers and routing information. Cryptographic protection prevents the exploitation of message externals and applies to internal and external networks or links that may be visible to individuals who are not authorized users. Header and routing information is sometimes transmitted in clear text (i.e., unencrypted) because the information is not identified by organizations as having significant value or because encrypting the information can result in lower network performance or higher costs. Alternative physical controls include protected distribution systems.
","uuid":"8cc8c23c-9c55-422a-bffa-8fba0dc71bf6","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"7713eadc-d896-4103-af43-1605e7a310be","text":"alternative physical controls","parameterId":"sc-08.03_odp","default":" [Assignment: organization defined alternative physical controls] "}],"subControls":"","tests":[{"testId":"SC-08(03)","uuid":"fed71b93-415a-476d-a7de-ddc6b5e5aafe","test":"Determine if cryptographic mechanisms are implemented to protect message externals unless otherwise protected by [SELECTED PARAMETER VALUE(S): alternative physical controls ].Concealing or randomizing communication patterns addresses protection from unauthorized disclosure of information. Communication patterns include frequency, periods, predictability, and amount. Changes to communications patterns can reveal information with intelligence value, especially when combined with other available information related to the mission and business functions of the organization. Concealing or randomizing communications prevents the derivation of intelligence based on communications patterns and applies to both internal and external networks or links that may be visible to individuals who are not authorized users. Encrypting the links and transmitting in continuous, fixed, or random patterns prevents the derivation of intelligence from the system communications patterns. Alternative physical controls include protected distribution systems.
","uuid":"abec173b-302a-4034-85fd-390d280ed626","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"072d3e22-fb4c-48cf-b00a-7cf16a633bd5","text":"alternative physical controls","parameterId":"sc-08.04_odp","default":" [Assignment: organization defined alternative physical controls] "}],"subControls":"","tests":[{"testId":"SC-08(04)","uuid":"6523c778-3313-40cf-a741-6e19bc730ba2","test":"Determine if cryptographic mechanisms are implemented to conceal or randomize communication patterns unless otherwise protected by [SELECTED PARAMETER VALUE(S): alternative physical controls ].The purpose of a protected distribution system is to deter, detect, and/or make difficult physical access to the communication lines that carry national security information.
","uuid":"94b3f521-3589-4468-b2d9-cab5f44db58e","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"fdc27548-c056-4fbd-bac2-826f70945bb8","text":"protected distribution system","parameterId":"sc-08.05_odp.01","default":" [Assignment: organization defined protected distribution system] "},{"constraints":"","displayName":"","guidance":"","uuid":"3c4ab318-9016-484b-995e-fdfee0414fe7","text":"[Selection (one or more): prevent unauthorized disclosure of information; detect changes to information]","parameterId":"sc-08.05_odp.02","default":"[Selection (one or more): prevent unauthorized disclosure of information; detect changes to information]"}],"subControls":"","tests":[{"testId":"SC-08(05)","uuid":"6fe23682-a370-41b1-885e-395f539c775c","test":"Determine if the [SELECTED PARAMETER VALUE(S): protected distribution system ] is implemented to [SELECTED PARAMETER VALUE(S): [Selection (one or more): prevent unauthorized disclosure of information; detect changes to information] ] during transmission.Network disconnect applies to internal and external networks. Terminating network connections associated with specific communications sessions includes de-allocating TCP/IP address or port pairs at the operating system level and de-allocating the networking assignments at the application level if multiple application sessions are using a single operating system-level network connection. Periods of inactivity may be established by organizations and include time periods by type of network access or for specific network accesses.
","uuid":"227c1312-dfb2-47b5-b6d6-94fb903f892f","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"f826e66a-a80a-4eca-8ca3-c0fdf60724d2","text":"time period","parameterId":"sc-10_odp","default":" [Assignment: organization defined time period] "}],"subControls":"","tests":[{"testId":"SC-10","uuid":"a7487001-dc41-4a60-a1ea-0a929a14f0c0","test":"Determine if the network connection associated with a communication session is terminated at the end of the session or after [SELECTED PARAMETER VALUE(S): time period ] of inactivity.Trusted paths are mechanisms by which users can communicate (using input devices such as keyboards) directly with the security functions of systems with the requisite assurance to support security policies. Trusted path mechanisms can only be activated by users or the security functions of organizational systems. User responses that occur via trusted paths are protected from modification by and disclosure to untrusted applications. Organizations employ trusted paths for trustworthy, high-assurance connections between security functions of systems and users, including during system logons. The original implementations of trusted paths employed an out-of-band signal to initiate the path, such as using the <BREAK> key, which does not transmit characters that can be spoofed. In later implementations, a key combination that could not be hijacked was used (e.g., the <CTRL> + <ALT> + <DEL> keys). Such key combinations, however, are platform-specific and may not provide a trusted path implementation in every case. The enforcement of trusted communications paths is provided by a specific implementation that meets the reference monitor concept.
","uuid":"9f0e5826-8cac-4afc-a50f-0e1d24792649","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"c3311746-7a09-439d-ba26-3223da02c962","text":"[Selection: physically; logically]","parameterId":"sc-11_odp.01","default":"[Selection: physically; logically]"},{"constraints":"","displayName":"","guidance":"","uuid":"c4f08e7d-0484-45da-a773-d2a51649c9ea","text":"security functions","parameterId":"sc-11_odp.02","default":" [Assignment: organization defined security functions] "}],"subControls":"","tests":[{"testId":"SC-11a.","uuid":"237a0bda-333a-4a41-aa9a-67c96c384244","test":"Determine if a [SELECTED PARAMETER VALUE(S): [Selection: physically; logically] ] isolated trusted communication path is provided for communications between the user and the trusted components of the system;An irrefutable communications path permits the system to initiate a trusted path, which necessitates that the user can unmistakably recognize the source of the communication as a trusted system component. For example, the trusted path may appear in an area of the display that other applications cannot access or be based on the presence of an identifier that cannot be spoofed.
","uuid":"675c4e29-9968-469d-8e65-50d8658e2cee","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"295f9b26-49fb-4208-ad29-f3842900ee98","text":"security functions","parameterId":"sc-11.01_odp","default":" [Assignment: organization defined security functions] "}],"subControls":"","tests":[{"testId":"SC-11(01)(a)","uuid":"819d01d4-d045-44f4-85fe-99955d8f2709","test":"Determine if a trusted communication path that is irrefutably distinguishable from other communication paths is provided;Cryptographic key management and establishment can be performed using manual procedures or automated mechanisms with supporting manual procedures. Organizations define key management requirements in accordance with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines and specify appropriate options, parameters, and levels. Organizations manage trust stores to ensure that only approved trust anchors are part of such trust stores. This includes certificates with visibility external to organizational systems and certificates related to the internal operations of systems. NIST CMVP and NIST CAVP provide additional information on validated cryptographic modules and algorithms that can be used in cryptographic key management and establishment.
","uuid":"e80e9fe4-6769-42c5-88dd-3ccca6c36c9c","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"1733f085-e421-427d-ac77-c42d2d00718a","text":"requirements","parameterId":"sc-12_odp","default":" [Assignment: organization defined requirements] "}],"subControls":"","tests":[{"testId":"SC-12[01]","uuid":"5d002c78-2ef6-4d96-b829-9cfbe3d3edbd","test":"Determine if cryptographic keys are established when cryptography is employed within the system in accordance with [SELECTED PARAMETER VALUE(S): requirements ];Escrowing of encryption keys is a common practice for ensuring availability in the event of key loss. A forgotten passphrase is an example of losing a cryptographic key.
","uuid":"83682380-8ddb-4f40-82b7-856d33a9e5cc","family":"System and Communications Protection","parameters":[],"subControls":"","tests":[{"testId":"SC-12(01)","uuid":"1f4eb842-a667-4789-aa99-ec6d8a6bbbf4","test":"Determine if information availability is maintained in the event of the loss of cryptographic keys by users.SP 800-56A, SP 800-56B , and SP 800-56C provide guidance on cryptographic key establishment schemes and key derivation methods. SP 800-57-1, SP 800-57-2 , and SP 800-57-3 provide guidance on cryptographic key management.
","uuid":"1f0ca59b-88ba-44d6-8836-046054404130","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"5f0c2e94-239f-471d-8d04-d7b76e817080","text":"[Selection: NIST FIPS-validated; NSA-approved]","parameterId":"sc-12.02_odp","default":"[Selection: NIST FIPS-validated; NSA-approved]"}],"subControls":"","tests":[{"testId":"SC-12(02)[01]","uuid":"3d2ed8f0-d14d-4c76-9cba-abc1b4a20d77","test":"Determine if symmetric cryptographic keys are produced using [SELECTED PARAMETER VALUE(S): [Selection: NIST FIPS-validated; NSA-approved] ] key management technology and processes;SP 800-56A, SP 800-56B , and SP 800-56C provide guidance on cryptographic key establishment schemes and key derivation methods. SP 800-57-1, SP 800-57-2 , and SP 800-57-3 provide guidance on cryptographic key management.
","uuid":"996e4a31-0887-4be8-9ee4-8121af82d478","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"01da5b3d-d68b-4438-8546-231b473f3d03","text":"[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]","parameterId":"sc-12.03_odp","default":"[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]"}],"subControls":"","tests":[{"testId":"SC-12(03)[01]","uuid":"86199ccf-0217-452d-a7a8-f9d524548dc2","test":"Determine if asymmetric cryptographic keys are produced using [SELECTED PARAMETER VALUE(S): [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] ];For organizations that use external service providers (e.g., cloud service or data center providers), physical control of cryptographic keys provides additional assurance that information stored by such external providers is not subject to unauthorized disclosure or modification.
","uuid":"3c5b9e02-cc7b-49cd-803e-d5bb35b30d5b","family":"System and Communications Protection","parameters":[],"subControls":"","tests":[{"testId":"SC-12(06)","uuid":"02488e83-cfa5-4e65-aa3e-1a9354e0a111","test":"Determine if physical control of cryptographic keys is maintained when stored information is encrypted by external service providers.Cryptography can be employed to support a variety of security solutions, including the protection of classified information and controlled unclassified information, the provision and implementation of digital signatures, and the enforcement of information separation when authorized individuals have the necessary clearances but lack the necessary formal access approvals. Cryptography can also be used to support random number and hash generation. Generally applicable cryptographic standards include FIPS-validated cryptography and NSA-approved cryptography. For example, organizations that need to protect classified information may specify the use of NSA-approved cryptography. Organizations that need to provision and implement digital signatures may specify the use of FIPS-validated cryptography. Cryptography is implemented in accordance with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines.
","uuid":"1ae613e9-a5f6-4e87-ba6d-a09ee5114064","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"8bd5e7da-6ed6-47ed-a3dc-840fd760c784","text":"cryptographic uses","parameterId":"sc-13_odp.01","default":" [Assignment: organization defined cryptographic uses] "},{"constraints":"","displayName":"","guidance":"","uuid":"524d0a47-35fd-44c6-ae61-f4a576275129","text":"types of cryptography","parameterId":"sc-13_odp.02","default":" [Assignment: organization defined types of cryptography] "}],"subControls":"","tests":[{"testId":"SC-13a.","uuid":"202ef5dc-6a4b-4134-bee6-4628ef0ef9a7","test":"Determine if [SELECTED PARAMETER VALUE(S): cryptographic uses ] are identified;Collaborative computing devices and applications include remote meeting devices and applications, networked white boards, cameras, and microphones. The explicit indication of use includes signals to users when collaborative computing devices and applications are activated.
","uuid":"c47a651c-47ca-4cad-aa01-bfb01668990f","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"78063a73-c4f0-4d50-8822-ebaaf85c51d6","text":"exceptions where remote activation is to be allowed","parameterId":"sc-15_odp","default":" [Assignment: organization defined exceptions where remote activation is to be allowed] "}],"subControls":"","tests":[{"testId":"SC-15a.","uuid":"f00e8c49-51bc-45fa-b0e1-2847b6ed70d3","test":"Determine if remote activation of collaborative computing devices and applications is prohibited except [SELECTED PARAMETER VALUE(S): exceptions where remote activation is to be allowed ];Failing to disconnect from collaborative computing devices can result in subsequent compromises of organizational information. Providing easy methods to disconnect from such devices after a collaborative computing session ensures that participants carry out the disconnect activity without having to go through complex and tedious procedures. Disconnect from collaborative computing devices can be manual or automatic.
","uuid":"613bd581-a9f3-411a-8bb3-86c5a06e6dca","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"505559a7-693d-4152-88ad-ca36601c949e","text":"[Selection (one or more): physical; logical]","parameterId":"sc-15.01_odp","default":"[Selection (one or more): physical; logical]"}],"subControls":"","tests":[{"testId":"SC-15(01)","uuid":"c1111d1a-8d94-45cf-a6bc-290eaf274b24","test":"Determine if the [SELECTED PARAMETER VALUE(S): [Selection (one or more): physical; logical] ] disconnect of collaborative computing devices is/are provided in a manner that supports ease of use.Failing to disable or remove collaborative computing devices and applications from systems or system components can result in compromises of information, including eavesdropping on conversations. A Sensitive Compartmented Information Facility (SCIF) is an example of a secure work area.
","uuid":"cc17d892-9bf8-4aa3-9e1d-bfc26c832637","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"0b1e74c4-1d60-401b-bac2-cbf8ae7274cf","text":"systems or system components","parameterId":"sc-15.03_odp.01","default":" [Assignment: organization defined systems or system components] "},{"constraints":"","displayName":"","guidance":"","uuid":"9ecd9a39-7ee7-484d-9e71-03fe8d97b0cb","text":"secure work areas","parameterId":"sc-15.03_odp.02","default":" [Assignment: organization defined secure work areas] "}],"subControls":"","tests":[{"testId":"SC-15(03)","uuid":"31ca215b-7649-409b-acb0-93ec7af9dd73","test":"Determine if collaborative computing devices and applications are disabled or removed from [SELECTED PARAMETER VALUE(S): systems or system components ] in [SELECTED PARAMETER VALUE(S): secure work areas ].Explicitly indicating current participants prevents unauthorized individuals from participating in collaborative computing sessions without the explicit knowledge of other participants.
","uuid":"20545ba6-291d-4814-9e0b-d2d6ea7fc394","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"1afbd9cb-d02c-41ed-b54b-282bec41dd92","text":"online meetings and teleconferences","parameterId":"sc-15.04_odp","default":" [Assignment: organization defined online meetings and teleconferences] "}],"subControls":"","tests":[{"testId":"SC-15(04)","uuid":"c18aacde-c1a8-4e07-a05b-183a2beb3ae1","test":"Determine if an explicit indication of current participants in [SELECTED PARAMETER VALUE(S): online meetings and teleconferences ] is provided.Security and privacy attributes can be explicitly or implicitly associated with the information contained in organizational systems or system components. Attributes are abstractions that represent the basic properties or characteristics of an entity with respect to protecting information or the management of personally identifiable information. Attributes are typically associated with internal data structures, including records, buffers, and files within the system. Security and privacy attributes are used to implement access control and information flow control policies; reflect special dissemination, management, or distribution instructions, including permitted uses of personally identifiable information; or support other aspects of the information security and privacy policies. Privacy attributes may be used independently or in conjunction with security attributes.
","uuid":"46643b75-5c45-4353-a869-31fee4daf050","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"055c5cd3-6412-46f8-92d7-25714f7082b3","text":"organization-defined security and privacy attributes","parameterId":"sc-16_prm_1","default":" [Assignment: organization-defined security and privacy attributes] "},{"constraints":"","displayName":"","guidance":"","uuid":"8d818b3a-10be-4117-9e9b-93cb7365fe04","text":"security attributes","parameterId":"sc-16_odp.01","default":" [Assignment: organization defined security attributes] "},{"constraints":"","displayName":"","guidance":"","uuid":"42c722ac-4fcb-40f1-a796-bcc47896893a","text":"privacy attributes","parameterId":"sc-16_odp.02","default":" [Assignment: organization defined privacy attributes] "}],"subControls":"","tests":[{"testId":"SC-16[01]","uuid":"7eaf4e14-486e-42cc-8591-9c15c9607dc1","test":"Determine if [SELECTED PARAMETER VALUE(S): security attributes ] are associated with information exchanged between systems;Part of verifying the integrity of transmitted information is ensuring that security and privacy attributes that are associated with such information have not been modified in an unauthorized manner. Unauthorized modification of security or privacy attributes can result in a loss of integrity for transmitted information.
","uuid":"a3d0ea60-a6f2-45fc-b3ef-486d07ca99d7","family":"System and Communications Protection","parameters":[],"subControls":"","tests":[{"testId":"SC-16(01)[01]","uuid":"bc5a1d7b-4533-4d11-b5d5-c38be078e9cd","test":"Determine if the integrity of transmitted security attributes is verified;Some attack vectors operate by altering the security attributes of an information system to intentionally and maliciously implement an insufficient level of security within the system. The alteration of attributes leads organizations to believe that a greater number of security functions are in place and operational than have actually been implemented.
","uuid":"7898b080-dace-4277-b2a9-c5b860fe6ca2","family":"System and Communications Protection","parameters":[],"subControls":"","tests":[{"testId":"SC-16(02)","uuid":"e649eaa6-1c09-4b50-86d4-9c91b236acfd","test":"Determine if anti-spoofing mechanisms are implemented to prevent adversaries from falsifying the security attributes indicating the successful application of the security process.Cryptographic mechanisms and techniques can provide strong security and privacy attribute binding to transmitted information to help ensure the integrity of such information.
","uuid":"d08bd850-c429-4367-9b60-833a47c476c9","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"4c11675b-81b3-4edb-be03-506826c17a68","text":"mechanisms or techniques","parameterId":"sc-16.03_odp","default":" [Assignment: organization defined mechanisms or techniques] "}],"subControls":"","tests":[{"testId":"SC-16(03)","uuid":"473e9cfe-8e8f-4bfc-b0a3-664f177f81e8","test":"Determine if [SELECTED PARAMETER VALUE(S): mechanisms or techniques ] are implemented to bind security and privacy attributes to transmitted information.Public key infrastructure (PKI) certificates are certificates with visibility external to organizational systems and certificates related to the internal operations of systems, such as application-specific time services. In cryptographic systems with a hierarchical structure, a trust anchor is an authoritative source (i.e., a certificate authority) for which trust is assumed and not derived. A root certificate for a PKI system is an example of a trust anchor. A trust store or certificate store maintains a list of trusted root certificates.
","uuid":"931459ba-75eb-4a7c-a03b-e994398f7b20","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"a173be98-19cd-4511-abd2-300392c8cb04","text":"certificate policy","parameterId":"sc-17_odp","default":" [Assignment: organization defined certificate policy] "}],"subControls":"","tests":[{"testId":"SC-17a.","uuid":"58633104-1348-47f9-98ec-12e2ebc4b2c2","test":"Determine if public key certificates are issued under [SELECTED PARAMETER VALUE(S): certificate policy ] , or public key certificates are obtained from an approved service provider;Mobile code includes any program, application, or content that can be transmitted across a network (e.g., embedded in an email, document, or website) and executed on a remote system. Decisions regarding the use of mobile code within organizational systems are based on the potential for the code to cause damage to the systems if used maliciously. Mobile code technologies include Java applets, JavaScript, HTML5, WebGL, and VBScript. Usage restrictions and implementation guidelines apply to both the selection and use of mobile code installed on servers and mobile code downloaded and executed on individual workstations and devices, including notebook computers and smart phones. Mobile code policy and procedures address specific actions taken to prevent the development, acquisition, and introduction of unacceptable mobile code within organizational systems, including requiring mobile code to be digitally signed by a trusted source.
","uuid":"9145e3dc-2067-4002-a21c-f900c3985abe","family":"System and Communications Protection","parameters":[],"subControls":"","tests":[{"testId":"SC-18a.[01]","uuid":"2b447f01-bd67-451d-bf60-add88caef5d2","test":"Determine if acceptable mobile code is defined;Corrective actions when unacceptable mobile code is detected include blocking, quarantine, or alerting administrators. Blocking includes preventing the transmission of word processing files with embedded macros when such macros have been determined to be unacceptable mobile code.
","uuid":"3b55d68c-7651-4f50-b9ac-4a0b16c0dba3","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"4e2d86d1-7d8c-44a2-8518-57dae70b2790","text":"unacceptable mobile code","parameterId":"sc-18.01_odp.01","default":" [Assignment: organization defined unacceptable mobile code] "},{"constraints":"","displayName":"","guidance":"","uuid":"01ac79f6-2a63-4165-9362-20f4db56980a","text":"corrective actions","parameterId":"sc-18.01_odp.02","default":" [Assignment: organization defined corrective actions] "}],"subControls":"","tests":[{"testId":"SC-18(01)[01]","uuid":"c0cb5339-349a-4ed5-829a-e22d7c2bec80","test":"Determine if [SELECTED PARAMETER VALUE(S): unacceptable mobile code ] is identified;None.
","uuid":"789963bd-9993-4c71-8033-79f2896024eb","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"ed9bc946-93c8-4d5a-9e01-8f4d439483e4","text":"mobile code requirements","parameterId":"sc-18.02_odp","default":" [Assignment: organization defined mobile code requirements] "}],"subControls":"","tests":[{"testId":"SC-18(02)[01]","uuid":"9f096402-af1a-402a-8406-e8d387b08f44","test":"Determine if the acquisition of mobile code to be deployed in the system meets [SELECTED PARAMETER VALUE(S): mobile code requirements ];None.
","uuid":"6975fefb-2821-4d1e-9de0-05298ac8aaae","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"1a11ed0b-70a7-442f-bdf9-b75e7afac016","text":"unacceptable mobile code","parameterId":"sc-18.03_odp","default":" [Assignment: organization defined unacceptable mobile code] "}],"subControls":"","tests":[{"testId":"SC-18(03)[01]","uuid":"6efdf690-e6be-4d11-a721-1ffbee01b083","test":"Determine if the download of [SELECTED PARAMETER VALUE(S): unacceptable mobile code ] is prevented;Actions enforced before executing mobile code include prompting users prior to opening email attachments or clicking on web links. Preventing the automatic execution of mobile code includes disabling auto-execute features on system components that employ portable storage devices, such as compact discs, digital versatile discs, and universal serial bus devices.
","uuid":"fb3e7dcd-4fb0-4378-a123-13077df6a14b","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"ee2ce609-8d5e-4a88-8fd5-03694869a51b","text":"software applications","parameterId":"sc-18.04_odp.01","default":" [Assignment: organization defined software applications] "},{"constraints":"","displayName":"","guidance":"","uuid":"714a4281-b027-4c5c-b507-62f2d8f89061","text":"actions","parameterId":"sc-18.04_odp.02","default":" [Assignment: organization defined actions] "}],"subControls":"","tests":[{"testId":"SC-18(04)[01]","uuid":"d324e011-2093-4e4c-b36a-2ca69d604782","test":"Determine if the automatic execution of mobile code in [SELECTED PARAMETER VALUE(S): software applications ] is prevented;Permitting the execution of mobile code only in confined virtual machine environments helps prevent the introduction of malicious code into other systems and system components.
","uuid":"379ca916-7960-446c-a4b8-e4534471b94f","family":"System and Communications Protection","parameters":[],"subControls":"","tests":[{"testId":"SC-18(05)","uuid":"c646d3f5-e0dd-4f93-9abd-5a0849da56ee","test":"Determine if execution of permitted mobile code is allowed only in confined virtual machine environments.Providing authoritative source information enables external clients, including remote Internet clients, to obtain origin authentication and integrity verification assurances for the host/service name to network address resolution information obtained through the service. Systems that provide name and address resolution services include domain name system (DNS) servers. Additional artifacts include DNS Security Extensions (DNSSEC) digital signatures and cryptographic keys. Authoritative data includes DNS resource records. The means for indicating the security status of child zones include the use of delegation signer resource records in the DNS. Systems that use technologies other than the DNS to map between host and service names and network addresses provide other means to assure the authenticity and integrity of response data.
","uuid":"1b59b77d-00bb-40fc-8bf7-fe1434352893","family":"System and Communications Protection","parameters":[],"subControls":"","tests":[{"testId":"SC-20a.[01]","uuid":"f9dcefef-ef8a-499c-a78d-005b21e74678","test":"Determine if additional data origin authentication is provided along with the authoritative name resolution data that the system returns in response to external name/address resolution queries;None.
","uuid":"55269fe6-cabc-4731-983e-75af6a7e320b","family":"System and Communications Protection","parameters":[],"subControls":"","tests":[{"testId":"SC-20(02)[01]","uuid":"684b3bed-392e-41de-8045-e2d927907736","test":"Determine if data origin artifacts are provided for internal name/address resolution queries;Each client of name resolution services either performs this validation on its own or has authenticated channels to trusted validation providers. Systems that provide name and address resolution services for local clients include recursive resolving or caching domain name system (DNS) servers. DNS client resolvers either perform validation of DNSSEC signatures, or clients use authenticated channels to recursive resolvers that perform such validations. Systems that use technologies other than the DNS to map between host and service names and network addresses provide some other means to enable clients to verify the authenticity and integrity of response data.
","uuid":"b9c517c4-7cb1-4be6-bbc8-667efe70f026","family":"System and Communications Protection","parameters":[],"subControls":"","tests":[{"testId":"SC-21[01]","uuid":"1bb5c8a6-d85c-477c-b093-7a1742c40589","test":"Determine if data origin authentication is requested for the name/address resolution responses that the system receives from authoritative sources;Systems that provide name and address resolution services include domain name system (DNS) servers. To eliminate single points of failure in systems and enhance redundancy, organizations employ at least two authoritative domain name system servers—one configured as the primary server and the other configured as the secondary server. Additionally, organizations typically deploy the servers in two geographically separated network subnetworks (i.e., not located in the same physical facility). For role separation, DNS servers with internal roles only process name and address resolution requests from within organizations (i.e., from internal clients). DNS servers with external roles only process name and address resolution information requests from clients external to organizations (i.e., on external networks, including the Internet). Organizations specify clients that can access authoritative DNS servers in certain roles (e.g., by address ranges and explicit lists).
","uuid":"7f8f62e9-ec23-48c6-97b9-752c6e7d795e","family":"System and Communications Protection","parameters":[],"subControls":"","tests":[{"testId":"SC-22[01]","uuid":"935f4b69-1387-41df-83b4-bae58760854d","test":"Determine if the systems that collectively provide name/address resolution services for an organization are fault-tolerant;Protecting session authenticity addresses communications protection at the session level, not at the packet level. Such protection establishes grounds for confidence at both ends of communications sessions in the ongoing identities of other parties and the validity of transmitted information. Authenticity protection includes protecting against man-in-the-middle
attacks, session hijacking, and the insertion of false information into sessions.
Invalidating session identifiers at logout curtails the ability of adversaries to capture and continue to employ previously valid session IDs.
","uuid":"17abb509-859f-40d2-be26-508dca222bcd","family":"System and Communications Protection","parameters":[],"subControls":"","tests":[{"testId":"SC-23(01)","uuid":"406852ff-47ed-4689-96d2-96b706f49c8d","test":"Determine if session identifiers are invalidated upon user logout or other session termination.Generating unique session identifiers curtails the ability of adversaries to reuse previously valid session IDs. Employing the concept of randomness in the generation of unique session identifiers protects against brute-force attacks to determine future session identifiers.
","uuid":"4146bff7-13e3-42a5-9ee3-077c5c84ea18","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"61448cba-a3ae-4100-918b-624fa9d98bae","text":"randomness requirements","parameterId":"sc-23.03_odp","default":" [Assignment: organization defined randomness requirements] "}],"subControls":"","tests":[{"testId":"SC-23(03)[01]","uuid":"0e7dd21f-ed47-46d7-96ad-a3122fcd7d33","test":"Determine if a unique session identifier is generated for each session with [SELECTED PARAMETER VALUE(S): randomness requirements ];Reliance on certificate authorities for the establishment of secure sessions includes the use of Transport Layer Security (TLS) certificates. These certificates, after verification by their respective certificate authorities, facilitate the establishment of protected sessions between web clients and web servers.
","uuid":"d669ddca-da2d-4e85-b631-9687a13b1d6f","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"4a9f8c4c-9c0f-4edb-aa25-07c19b356ace","text":"certificated authorities","parameterId":"sc-23.05_odp","default":" [Assignment: organization defined certificated authorities] "}],"subControls":"","tests":[{"testId":"SC-23(05)","uuid":"feccf851-c727-499e-a389-ec64cf15c2d8","test":"Determine if only the use of [SELECTED PARAMETER VALUE(S): certificated authorities ] for verification of the establishment of protected sessions is allowed.Failure in a known state addresses security concerns in accordance with the mission and business needs of organizations. Failure in a known state prevents the loss of confidentiality, integrity, or availability of information in the event of failures of organizational systems or system components. Failure in a known safe state helps to prevent systems from failing to a state that may cause injury to individuals or destruction to property. Preserving system state information facilitates system restart and return to the operational mode with less disruption of mission and business processes.
","uuid":"350f7a95-6d62-484c-8c9d-a0eb9485febe","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"faa8d22e-5250-47f2-a5bc-693bb27b82c4","text":"types of system failures on system components","parameterId":"sc-24_odp.01","default":" [Assignment: organization defined types of system failures on system components] "},{"constraints":"","displayName":"","guidance":"","uuid":"a64ebd03-4837-4730-8024-9cb05b234778","text":"known system state","parameterId":"sc-24_odp.02","default":" [Assignment: organization defined known system state] "},{"constraints":"","displayName":"","guidance":"","uuid":"77544fc9-c219-4b81-a827-c0b9cea2c63c","text":"system state information","parameterId":"sc-24_odp.03","default":" [Assignment: organization defined system state information] "}],"subControls":"","tests":[{"testId":"SC-24","uuid":"ffdbf2e2-89e0-4475-97f8-ab2b510c4a4f","test":"Determine if [SELECTED PARAMETER VALUE(S): types of system failures on system components ] fail to a [SELECTED PARAMETER VALUE(S): known system state ] while preserving [SELECTED PARAMETER VALUE(S): system state information ] in failure.The deployment of system components with minimal functionality reduces the need to secure every endpoint and may reduce the exposure of information, systems, and services to attacks. Reduced or minimal functionality includes diskless nodes and thin client technologies.
","uuid":"c95086c1-02da-4851-8019-5d8f04489703","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"41d9a172-d73a-4a88-b2ed-c659f8d5e791","text":"system components","parameterId":"sc-25_odp","default":" [Assignment: organization defined system components] "}],"subControls":"","tests":[{"testId":"SC-25[01]","uuid":"ca66ea84-714f-44a4-a3f7-f3c7a13623db","test":"Determine if minimal functionality for [SELECTED PARAMETER VALUE(S): system components ] is employed;Decoys (i.e., honeypots, honeynets, or deception nets) are established to attract adversaries and deflect attacks away from the operational systems that support organizational mission and business functions. Use of decoys requires some supporting isolation measures to ensure that any deflected malicious code does not infect organizational systems. Depending on the specific usage of the decoy, consultation with the Office of the General Counsel before deployment may be needed.
","uuid":"abb067b7-cc2f-442d-afee-f1253e187440","family":"System and Communications Protection","parameters":[],"subControls":"","tests":[{"testId":"SC-26[01]","uuid":"d3287e38-ac4d-4f1b-97e8-78eb8d85b28f","test":"Determine if components within organizational systems specifically designed to be the target of malicious attacks are included to detect such attacks;Platforms are combinations of hardware, firmware, and software components used to execute software applications. Platforms include operating systems, the underlying computer architectures, or both. Platform-independent applications are applications with the capability to execute on multiple platforms. Such applications promote portability and reconstitution on different platforms. Application portability and the ability to reconstitute on different platforms increase the availability of mission-essential functions within organizations in situations where systems with specific operating systems are under attack.
","uuid":"af019d33-3fe9-4d6c-8529-c1ee58ad0770","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"b3a454d9-2038-4ef6-a461-c7dbb22338fb","text":"platform-independent applications","parameterId":"sc-27_odp","default":" [Assignment: organization defined platform-independent applications] "}],"subControls":"","tests":[{"testId":"SC-27","uuid":"2d9f30d3-73f6-4393-9f39-30166677a8e6","test":"Determine if [SELECTED PARAMETER VALUE(S): platform-independent applications ] are included within organizational systems.Information at rest refers to the state of information when it is not in process or in transit and is located on system components. Such components include internal or external hard disk drives, storage area network devices, or databases. However, the focus of protecting information at rest is not on the type of storage device or frequency of access but rather on the state of the information. Information at rest addresses the confidentiality and integrity of information and covers user information and system information. System-related information that requires protection includes configurations or rule sets for firewalls, intrusion detection and prevention systems, filtering routers, and authentication information. Organizations may employ different mechanisms to achieve confidentiality and integrity protections, including the use of cryptographic mechanisms and file share scanning. Integrity protection can be achieved, for example, by implementing write-once-read-many (WORM) technologies. When adequate protection of information at rest cannot otherwise be achieved, organizations may employ other controls, including frequent scanning to identify malicious code at rest and secure offline storage in lieu of online storage.
","uuid":"05da20c7-45fc-4018-a790-0e3baad4f5af","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"e0f85cec-014a-49f0-be21-13001c70e033","text":"[Selection (one or more): confidentiality; integrity]","parameterId":"sc-28_odp.01","default":"[Selection (one or more): confidentiality; integrity]"},{"constraints":"","displayName":"","guidance":"","uuid":"8e18cf2a-7bf3-40c3-ad54-faa5f76c6300","text":"information at rest","parameterId":"sc-28_odp.02","default":" [Assignment: organization defined information at rest] "}],"subControls":"","tests":[{"testId":"SC-28","uuid":"a96ba116-1124-4b10-86cc-ea44badf2035","test":"Determine if the [SELECTED PARAMETER VALUE(S): [Selection (one or more): confidentiality; integrity] ] of [SELECTED PARAMETER VALUE(S): information at rest ] is/are protected.The selection of cryptographic mechanisms is based on the need to protect the confidentiality and integrity of organizational information. The strength of mechanism is commensurate with the security category or classification of the information. Organizations have the flexibility to encrypt information on system components or media or encrypt data structures, including files, records, or fields.
","uuid":"05a71224-59ef-49bd-9388-0f7e7783eb26","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"e852a84a-54d0-42d1-903c-6d581845740b","text":"information","parameterId":"sc-28.01_odp.01","default":" [Assignment: organization defined information] "},{"constraints":"","displayName":"","guidance":"","uuid":"a376858f-7aba-4c9c-b5b5-4f8cabc0bfd1","text":"system components or media","parameterId":"sc-28.01_odp.02","default":" [Assignment: organization defined system components or media] "}],"subControls":"","tests":[{"testId":"SC-28(01)[01]","uuid":"26391e11-1d67-45e9-873f-47e021f15fcf","test":"Determine if cryptographic mechanisms are implemented to prevent unauthorized disclosure of [SELECTED PARAMETER VALUE(S): information ] at rest on [SELECTED PARAMETER VALUE(S): system components or media ];Removing organizational information from online storage to offline storage eliminates the possibility of individuals gaining unauthorized access to the information through a network. Therefore, organizations may choose to move information to offline storage in lieu of protecting such information in online storage.
","uuid":"33bb8b38-6ad9-4d1e-8b94-0968aca36dac","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"0c2706a7-79f4-4f37-83df-c89b12c2feb0","text":"information","parameterId":"sc-28.02_odp","default":" [Assignment: organization defined information] "}],"subControls":"","tests":[{"testId":"SC-28(02)[01]","uuid":"f6ffc1e9-81b5-467f-8e4d-8305a20abe31","test":"Determine if [SELECTED PARAMETER VALUE(S): information ] is removed from online storage;A Trusted Platform Module (TPM) is an example of a hardware-protected data store that can be used to protect cryptographic keys.
","uuid":"9a4738de-05ed-4b9e-b87e-0fc3cedc252e","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"f09e6e6f-c6f7-4b5a-980a-e052a03cafbd","text":"[Selection: [(NESTED PARAMETER) Assignment for sc-28.03_odp.02: safeguards]; hardware-protected key store]","parameterId":"sc-28.03_odp.01","default":"[Selection: [(NESTED PARAMETER) Assignment for sc-28.03_odp.02: safeguards]; hardware-protected key store]"},{"constraints":"","displayName":"","guidance":"","uuid":"4100f81e-74b8-494c-b3ca-4b4462887c17","text":"safeguards","parameterId":"sc-28.03_odp.02","default":" [Assignment: organization defined safeguards] "}],"subControls":"","tests":[{"testId":"SC-28(03)","uuid":"a4ae4c1a-3db6-41bd-bfec-f13603b9bcc4","test":"Determine if protected storage for cryptographic keys is provided using [SELECTED PARAMETER VALUE(S): [Selection: [(NESTED PARAMETER) Assignment for sc-28.03_odp.02: safeguards]; hardware-protected key store] ].Increasing the diversity of information technologies within organizational systems reduces the impact of potential exploitations or compromises of specific technologies. Such diversity protects against common mode failures, including those failures induced by supply chain attacks. Diversity in information technologies also reduces the likelihood that the means adversaries use to compromise one system component will be effective against other system components, thus further increasing the adversary work factor to successfully complete planned attacks. An increase in diversity may add complexity and management overhead that could ultimately lead to mistakes and unauthorized configurations.
","uuid":"a0894250-2908-4c96-bff4-4ca3e8fba585","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"eb248fb3-5e0b-40ea-91ed-6398cb32ffdc","text":"system components","parameterId":"sc-29_odp","default":" [Assignment: organization defined system components] "}],"subControls":"","tests":[{"testId":"SC-29","uuid":"b8828d02-1220-4bbe-a022-7f56dfcdcefe","test":"Determine if a diverse set of information technologies is employed for [SELECTED PARAMETER VALUE(S): system components ] in the implementation of the system.While frequent changes to operating systems and applications can pose significant configuration management challenges, the changes can result in an increased work factor for adversaries to conduct successful attacks. Changing virtual operating systems or applications, as opposed to changing actual operating systems or applications, provides virtual changes that impede attacker success while reducing configuration management efforts. Virtualization techniques can assist in isolating untrustworthy software or software of dubious provenance into confined execution environments.
","uuid":"f669730a-a460-471a-bf77-5ef87d43f7f2","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"1fe3898a-8d11-4b69-8481-c27dc741f6fa","text":"frequency","parameterId":"sc-29.01_odp","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"SC-29(01)","uuid":"b5829b02-9bb2-4860-961b-bd83e9397331","test":"Determine if virtualization techniques are employed to support the deployment of a diverse range of operating systems and applications that are changed [SELECTED PARAMETER VALUE(S): frequency ].Concealment and misdirection techniques can significantly reduce the targeting capabilities of adversaries (i.e., window of opportunity and available attack surface) to initiate and complete attacks. For example, virtualization techniques provide organizations with the ability to disguise systems, potentially reducing the likelihood of successful attacks without the cost of having multiple platforms. The increased use of concealment and misdirection techniques and methods—including randomness, uncertainty, and virtualization—may sufficiently confuse and mislead adversaries and subsequently increase the risk of discovery and/or exposing tradecraft. Concealment and misdirection techniques may provide additional time to perform core mission and business functions. The implementation of concealment and misdirection techniques may add to the complexity and management overhead required for the system.
","uuid":"f52565df-87f8-497c-9af5-c23392b80814","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"dbd57d70-11b5-4587-9727-f6e9a1a18ace","text":"concealment and misdirection techniques","parameterId":"sc-30_odp.01","default":" [Assignment: organization defined concealment and misdirection techniques] "},{"constraints":"","displayName":"","guidance":"","uuid":"1e142d88-8f6d-40ca-a107-8ca4d8dc48b7","text":"systems","parameterId":"sc-30_odp.02","default":" [Assignment: organization defined systems] "},{"constraints":"","displayName":"","guidance":"","uuid":"2539dac3-8320-4d92-bad1-767572f15849","text":"time periods","parameterId":"sc-30_odp.03","default":" [Assignment: organization defined time periods] "}],"subControls":"","tests":[{"testId":"SC-30","uuid":"b8b05a0a-ea71-4565-a413-eccd5ffd4b96","test":"Determine if [SELECTED PARAMETER VALUE(S): concealment and misdirection techniques ] are employed for [SELECTED PARAMETER VALUE(S): systems ] for [SELECTED PARAMETER VALUE(S): time periods ] to confuse and mislead adversaries.Randomness introduces increased levels of uncertainty for adversaries regarding the actions that organizations take to defend their systems against attacks. Such actions may impede the ability of adversaries to correctly target information resources of organizations that support critical missions or business functions. Uncertainty may also cause adversaries to hesitate before initiating or continuing attacks. Misdirection techniques that involve randomness include performing certain routine actions at different times of day, employing different information technologies, using different suppliers, and rotating roles and responsibilities of organizational personnel.
","uuid":"b5e13555-7474-4ac7-8b9b-df1181a38bf3","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"63b6630b-588c-4198-8056-96dc55576c39","text":"techniques","parameterId":"sc-30.02_odp","default":" [Assignment: organization defined techniques] "}],"subControls":"","tests":[{"testId":"SC-30(02)","uuid":"13734854-5727-4de1-8747-5dea04a008a7","test":"Determine if [SELECTED PARAMETER VALUE(S): techniques ] are employed to introduce randomness into organizational operations and assets.Adversaries target critical mission and business functions and the systems that support those mission and business functions while also trying to minimize the exposure of their existence and tradecraft. The static, homogeneous, and deterministic nature of organizational systems targeted by adversaries make such systems more susceptible to attacks with less adversary cost and effort to be successful. Changing processing and storage locations (also referred to as moving target defense) addresses the advanced persistent threat using techniques such as virtualization, distributed processing, and replication. This enables organizations to relocate the system components (i.e., processing, storage) that support critical mission and business functions. Changing the locations of processing activities and/or storage sites introduces a degree of uncertainty into the targeting activities of adversaries. The targeting uncertainty increases the work factor of adversaries and makes compromises or breaches of the organizational systems more difficult and time-consuming. It also increases the chances that adversaries may inadvertently disclose certain aspects of their tradecraft while attempting to locate critical organizational resources.
","uuid":"bf15f9a3-86a8-4d93-ae15-119f9cd9047b","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"f1ea6fca-9ec9-497b-9a6e-5535ee1dd8c6","text":"processing and/or storage","parameterId":"sc-30.03_odp.01","default":" [Assignment: organization defined processing and/or storage] "},{"constraints":"","displayName":"","guidance":"","uuid":"f7f6ab0e-74e4-4ff2-af4f-8289707fb59f","text":"[Selection: [(NESTED PARAMETER) Assignment for sc-30.03_odp.03: time frequency]; random time intervals]","parameterId":"sc-30.03_odp.02","default":"[Selection: [(NESTED PARAMETER) Assignment for sc-30.03_odp.03: time frequency]; random time intervals]"},{"constraints":"","displayName":"","guidance":"","uuid":"d8735211-d7ee-4b00-afea-c6fa0a4bb6e1","text":"time frequency","parameterId":"sc-30.03_odp.03","default":" [Assignment: organization defined time frequency] "}],"subControls":"","tests":[{"testId":"SC-30(03)","uuid":"8443b6bc-3764-4268-ae49-2192274756dd","test":"Determine if the location of [SELECTED PARAMETER VALUE(S): processing and/or storage ] is changed [SELECTED PARAMETER VALUE(S): [Selection: [(NESTED PARAMETER) Assignment for sc-30.03_odp.03: time frequency]; random time intervals] ].Employing misleading information is intended to confuse potential adversaries regarding the nature and extent of controls deployed by organizations. Thus, adversaries may employ incorrect and ineffective attack techniques. One technique for misleading adversaries is for organizations to place misleading information regarding the specific controls deployed in external systems that are known to be targeted by adversaries. Another technique is the use of deception nets that mimic actual aspects of organizational systems but use, for example, out-of-date software configurations.
","uuid":"35e886ad-b1da-4bd8-9139-e9f2f55fdab5","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"01d094a5-6526-4928-8bec-b28264fc069a","text":"system components","parameterId":"sc-30.04_odp","default":" [Assignment: organization defined system components] "}],"subControls":"","tests":[{"testId":"SC-30(04)","uuid":"dd876b8e-88e5-4fb6-b4b3-e17db06f01ac","test":"Determine if realistic but misleading information about the security state or posture of [SELECTED PARAMETER VALUE(S): system components ] is employed.By hiding, disguising, or concealing critical system components, organizations may be able to decrease the probability that adversaries target and successfully compromise those assets. Potential means to hide, disguise, or conceal system components include the configuration of routers or the use of encryption or virtualization techniques.
","uuid":"6ca3770f-c107-4ef8-88e3-b299ef0ed008","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"63f43420-67f4-4021-a429-80f9201dda61","text":"techniques","parameterId":"sc-30.05_odp.01","default":" [Assignment: organization defined techniques] "},{"constraints":"","displayName":"","guidance":"","uuid":"a65a8ca3-8ee7-4cee-98dc-9b9b21238a24","text":"system components","parameterId":"sc-30.05_odp.02","default":" [Assignment: organization defined system components] "}],"subControls":"","tests":[{"testId":"SC-30(05)","uuid":"e9d409ba-4887-4796-9f75-41b586693cca","test":"Determine if [SELECTED PARAMETER VALUE(S): techniques ] are employed to hide or conceal [SELECTED PARAMETER VALUE(S): system components ].Developers are in the best position to identify potential areas within systems that might lead to covert channels. Covert channel analysis is a meaningful activity when there is the potential for unauthorized information flows across security domains, such as in the case of systems that contain export-controlled information and have connections to external networks (i.e., networks that are not controlled by organizations). Covert channel analysis is also useful for multilevel secure systems, multiple security level systems, and cross-domain systems.
","uuid":"53e81736-545e-455e-8527-092eb9b3bf44","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"cecad757-005c-433f-b6f3-a32f457c6e64","text":"[Selection (one or more): storage; timing]","parameterId":"sc-31_odp","default":"[Selection (one or more): storage; timing]"}],"subControls":"","tests":[{"testId":"SC-31a.","uuid":"aa33e98a-4f55-4416-b397-b523abf72957","test":"Determine if a covert channel analysis is performed to identify those aspects of communications within the system that are potential avenues for covert [SELECTED PARAMETER VALUE(S): [Selection (one or more): storage; timing] ] channels;None.
","uuid":"05733aba-6f67-4a35-82cd-5156a64abd0a","family":"System and Communications Protection","parameters":[],"subControls":"","tests":[{"testId":"SC-31(01)","uuid":"540b31c3-354d-4d09-94b8-a6b21e399500","test":"Determine if a subset of the identified covert channels is tested to determine the channels that are exploitable.The complete elimination of covert channels, especially covert timing channels, is usually not possible without significant performance impacts.
","uuid":"2488822f-e6df-4390-be6b-f8a0f89f25bb","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"5fe3ba79-2651-48c6-865e-71e4bff20b7a","text":"[Selection (one or more): storage; timing]","parameterId":"sc-31.02_odp.01","default":"[Selection (one or more): storage; timing]"},{"constraints":"","displayName":"","guidance":"","uuid":"3cf63612-e8d3-4526-b81b-15976a67c403","text":"values","parameterId":"sc-31.02_odp.02","default":" [Assignment: organization defined values] "}],"subControls":"","tests":[{"testId":"SC-31(02)","uuid":"b1a0448c-5182-4071-bb16-86b208616e33","test":"Determine if the maximum bandwidth for identified covert [SELECTED PARAMETER VALUE(S): [Selection (one or more): storage; timing] ] channels is reduced to [SELECTED PARAMETER VALUE(S): values ].Measuring covert channel bandwidth in specified operational environments helps organizations determine how much information can be covertly leaked before such leakage adversely affects mission or business functions. Covert channel bandwidth may be significantly different when measured in settings that are independent of the specific environments of operation, including laboratories or system development environments.
","uuid":"a73f5daa-04e0-42b9-9a40-79cf2c55819f","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"f9b73835-bd14-4c41-a5f1-4e9a4763651d","text":"subset of identified covert channels","parameterId":"sc-31.03_odp","default":" [Assignment: organization defined subset of identified covert channels] "}],"subControls":"","tests":[{"testId":"SC-31(03)","uuid":"e56a8f06-9add-4546-af37-ea549d71b2b6","test":"Determine if the bandwidth of [SELECTED PARAMETER VALUE(S): subset of identified covert channels ] is measured in the operational environment of the system.System partitioning is part of a defense-in-depth protection strategy. Organizations determine the degree of physical separation of system components. Physical separation options include physically distinct components in separate racks in the same room, critical components in separate rooms, and geographical separation of critical components. Security categorization can guide the selection of candidates for domain partitioning. Managed interfaces restrict or prohibit network access and information flow among partitioned system components.
","uuid":"37e27fb8-94f3-43dd-9b51-4f2f19650a1d","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"a1d42c5e-d947-43de-bce6-bb43f92e9937","text":"system components","parameterId":"sc-32_odp.01","default":" [Assignment: organization defined system components] "},{"constraints":"","displayName":"","guidance":"","uuid":"8df99e30-8b9d-4943-8ce3-85673e0545af","text":"[Selection: physical; logical]","parameterId":"sc-32_odp.02","default":"[Selection: physical; logical]"},{"constraints":"","displayName":"","guidance":"","uuid":"657decc2-33a2-4388-8ce5-91c50330692a","text":"circumstances for the physical or logical separation of components","parameterId":"sc-32_odp.03","default":" [Assignment: organization defined circumstances for the physical or logical separation of components] "}],"subControls":"","tests":[{"testId":"SC-32","uuid":"73252093-b102-44bf-94ae-5e41f8219346","test":"Determine if the system is partitioned into [SELECTED PARAMETER VALUE(S): system components ] residing in separate [SELECTED PARAMETER VALUE(S): [Selection: physical; logical] ] domains or environments based on [SELECTED PARAMETER VALUE(S): circumstances for the physical or logical separation of components ].Privileged functions that operate in a single physical domain may represent a single point of failure if that domain becomes compromised or experiences a denial of service.
","uuid":"b0162586-413e-4108-a6b5-28d2aa4d045a","family":"System and Communications Protection","parameters":[],"subControls":"","tests":[{"testId":"SC-32(01)","uuid":"70990e5e-fd3f-4cd8-bbbe-b451bd8d7b10","test":"Determine if privileged functions are partitioned into separate physical domains.The operating environment for a system contains the code that hosts applications, including operating systems, executives, or virtual machine monitors (i.e., hypervisors). It can also include certain applications that run directly on hardware platforms. Hardware-enforced, read-only media include Compact Disc-Recordable (CD-R) and Digital Versatile Disc-Recordable (DVD-R) disk drives as well as one-time, programmable, read-only memory. The use of non-modifiable storage ensures the integrity of software from the point of creation of the read-only image. The use of reprogrammable, read-only memory can be accepted as read-only media provided that integrity can be adequately protected from the point of initial writing to the insertion of the memory into the system, and there are reliable hardware protections against reprogramming the memory while installed in organizational systems.
","uuid":"dd4cffc0-0eb3-495c-8ec5-fde68a91899e","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"b82c90c9-e6de-4ea1-89de-dea977475029","text":"system components","parameterId":"sc-34_odp.01","default":" [Assignment: organization defined system components] "},{"constraints":"","displayName":"","guidance":"","uuid":"e57caffa-2b40-40ce-a7fd-19759b87e772","text":"applications","parameterId":"sc-34_odp.02","default":" [Assignment: organization defined applications] "}],"subControls":"","tests":[{"testId":"SC-34a.","uuid":"85ee47f8-b082-4d3e-a54b-fcf94ff69401","test":"Determine if the operating environment for [SELECTED PARAMETER VALUE(S): system components ] is loaded and executed from hardware-enforced, read-only media;Disallowing writeable storage eliminates the possibility of malicious code insertion via persistent, writeable storage within the designated system components. The restriction applies to fixed and removable storage, with the latter being addressed either directly or as specific restrictions imposed through access controls for mobile devices.
","uuid":"bd3cf8e3-b225-49df-a2fc-971770894bd7","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"4f6fb007-0714-45fb-bcb2-bdc3679ed0d6","text":"system components","parameterId":"sc-34.01_odp","default":" [Assignment: organization defined system components] "}],"subControls":"","tests":[{"testId":"SC-34(01)","uuid":"8de7798a-d0a9-4b28-b66f-76fd24bc0c6c","test":"Determine if [SELECTED PARAMETER VALUE(S): system components ] are employed with no writeable storage that is persistent across component restart or power on/off.Controls prevent the substitution of media into systems or the reprogramming of programmable read-only media prior to installation into the systems. Integrity protection controls include a combination of prevention, detection, and response.
","uuid":"b213c6ac-7c45-43cf-b67d-d2ebea9eed0e","family":"System and Communications Protection","parameters":[],"subControls":"","tests":[{"testId":"SC-34(02)[01]","uuid":"db602d7f-55f0-4227-b7ff-27acb63fc6d1","test":"Determine if the integrity of information is protected prior to storage on read-only media;External malicious code identification differs from decoys in SC-26 in that the components actively probe networks, including the Internet, in search of malicious code contained on external websites. Like decoys, the use of external malicious code identification techniques requires some supporting isolation measures to ensure that any malicious code discovered during the search and subsequently executed does not infect organizational systems. Virtualization is a common technique for achieving such isolation.
","uuid":"8c8ee6ac-432d-40d1-814a-10bd91e83ac2","family":"System and Communications Protection","parameters":[],"subControls":"","tests":[{"testId":"SC-35","uuid":"ec265370-db5e-4c7a-a8a7-a22f74cbf604","test":"Determine if system components that proactively seek to identify network-based malicious code or malicious websites are included.Distributing processing and storage across multiple physical locations or logical domains provides a degree of redundancy or overlap for organizations. The redundancy and overlap increase the work factor of adversaries to adversely impact organizational operations, assets, and individuals. The use of distributed processing and storage does not assume a single primary processing or storage location. Therefore, it allows for parallel processing and storage.
","uuid":"3d130131-86a9-4a58-b1a6-dfee9c1e027b","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"11fc2672-beb5-4e80-befa-79a55f19f125","text":"[Selection: physical locations; logical domains]","parameterId":"sc-36_prm_1","default":" [Assignment: [Selection: physical locations; logical domains]] "},{"constraints":"","displayName":"","guidance":"","uuid":"8315bbd8-612f-41e8-b957-05b7079562cd","text":"organization-defined processing and storage components","parameterId":"sc-36_prm_2","default":" [Assignment: organization-defined processing and storage components] "},{"constraints":"","displayName":"","guidance":"","uuid":"8b51c233-4ed6-4b22-b9a0-1195a0b3106d","text":"processing components","parameterId":"sc-36_odp.01","default":" [Assignment: organization defined processing components] "},{"constraints":"","displayName":"","guidance":"","uuid":"cbb578a7-f378-4a73-aaf6-b5d005872df9","text":"[Selection: physical locations; logical domains]","parameterId":"sc-36_odp.02","default":"[Selection: physical locations; logical domains]"},{"constraints":"","displayName":"","guidance":"","uuid":"52b89a65-2dd6-4d15-90df-bc1950a80dbd","text":"storage components","parameterId":"sc-36_odp.03","default":" [Assignment: organization defined storage components] "},{"constraints":"","displayName":"","guidance":"","uuid":"7b583954-ca54-4530-b437-8020ea5f9f85","text":"[Selection: physical locations; logical domains]","parameterId":"sc-36_odp.04","default":"[Selection: physical locations; logical domains]"}],"subControls":"","tests":[{"testId":"SC-36[01]","uuid":"50710140-cfb8-4622-9984-ce3d1947ba0c","test":"Determine if [SELECTED PARAMETER VALUE(S): processing components ] are distributed across [SELECTED PARAMETER VALUE(S): [Selection: physical locations; logical domains] ];Distributed processing and/or storage may be used to reduce opportunities for adversaries to compromise the confidentiality, integrity, or availability of organizational information and systems. However, the distribution of processing and storage components does not prevent adversaries from compromising one or more of the components. Polling compares the processing results and/or storage content from the distributed components and subsequently votes on the outcomes. Polling identifies potential faults, compromises, or errors in the distributed processing and storage components.
","uuid":"151051a1-1c92-4d9a-82a0-3beb7a634ab9","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"bd7f98a0-b4f5-4fd5-975f-7a43ace4e51e","text":"distributed processing and storage components","parameterId":"sc-36.01_odp.01","default":" [Assignment: organization defined distributed processing and storage components] "},{"constraints":"","displayName":"","guidance":"","uuid":"f84dc644-ebe7-4d47-95ba-94cc10fcdd1a","text":"actions","parameterId":"sc-36.01_odp.02","default":" [Assignment: organization defined actions] "}],"subControls":"","tests":[{"testId":"SC-36(01)(a)","uuid":"7b9ca009-48cb-45d5-8777-d86561864a3b","test":"Determine if polling techniques are employed to identify potential faults, errors, or compromises to [SELECTED PARAMETER VALUE(S): distributed processing and storage components ];SC-36 and CP-9(6) require the duplication of systems or system components in distributed locations. The synchronization of duplicated and redundant services and data helps to ensure that information contained in the distributed locations can be used in the mission or business functions of organizations, as needed.
","uuid":"da15e222-30bb-4f26-a7ff-35154078b859","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"ea5db69f-9c73-4b53-963b-7a4f55572153","text":"duplicate systems or system components","parameterId":"sc-36.02_odp","default":" [Assignment: organization defined duplicate systems or system components] "}],"subControls":"","tests":[{"testId":"SC-36(02)","uuid":"f77fe61e-8b72-4cb0-baad-e7639f7b8695","test":"Determine if [SELECTED PARAMETER VALUE(S): duplicate systems or system components ] are synchronized.Out-of-band channels include local, non-network accesses to systems; network paths physically separate from network paths used for operational traffic; or non-electronic paths, such as the U.S. Postal Service. The use of out-of-band channels is contrasted with the use of in-band channels (i.e., the same channels) that carry routine operational traffic. Out-of-band channels do not have the same vulnerability or exposure as in-band channels. Therefore, the confidentiality, integrity, or availability compromises of in-band channels will not compromise or adversely affect the out-of-band channels. Organizations may employ out-of-band channels in the delivery or transmission of organizational items, including authenticators and credentials; cryptographic key management information; system and data backups; configuration management changes for hardware, firmware, or software; security updates; maintenance information; and malicious code protection updates.
","uuid":"936c64af-b523-4df8-bd53-1e34b9b38b10","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"ec733954-9c19-4d7e-87cc-96946ca0cebc","text":"out-of-band channels","parameterId":"sc-37_odp.01","default":" [Assignment: organization defined out-of-band channels] "},{"constraints":"","displayName":"","guidance":"","uuid":"b6db75b4-5084-4659-a131-e90794808b58","text":"information, system components, or devices","parameterId":"sc-37_odp.02","default":" [Assignment: organization defined information, system components, or devices] "},{"constraints":"","displayName":"","guidance":"","uuid":"7fc480e1-d09b-4a03-aac9-ce1b5d6a8bee","text":"individuals or systems","parameterId":"sc-37_odp.03","default":" [Assignment: organization defined individuals or systems] "}],"subControls":"","tests":[{"testId":"SC-37","uuid":"e322d7e1-f2ab-4baa-8861-b259ff6769fe","test":"Determine if [SELECTED PARAMETER VALUE(S): out-of-band channels ] are employed for the physical delivery or electronic transmission of [SELECTED PARAMETER VALUE(S): information, system components, or devices ] to [SELECTED PARAMETER VALUE(S): individuals or systems ].Techniques employed by organizations to ensure that only designated systems or individuals receive certain information, system components, or devices include sending authenticators via an approved courier service but requiring recipients to show some form of government-issued photographic identification as a condition of receipt.
","uuid":"d64ed3da-4323-4c9c-b652-eb6d42e527d7","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"7feb7724-44d7-4a9e-890b-e257de6a94f9","text":"controls","parameterId":"sc-37.01_odp.01","default":" [Assignment: organization defined controls] "},{"constraints":"","displayName":"","guidance":"","uuid":"54f74dcb-e32d-4c40-b24a-d911f5a7e9b3","text":"individuals or systems","parameterId":"sc-37.01_odp.02","default":" [Assignment: organization defined individuals or systems] "},{"constraints":"","displayName":"","guidance":"","uuid":"1ec96bb1-7b14-4284-b7e3-32af04eb4c74","text":"information, system components, or devices","parameterId":"sc-37.01_odp.03","default":" [Assignment: organization defined information, system components, or devices] "}],"subControls":"","tests":[{"testId":"SC-37(01)","uuid":"44f4b814-bec0-4a53-b7ee-d24ea1d8dd52","test":"Determine if [SELECTED PARAMETER VALUE(S): controls ] are employed to ensure that only [SELECTED PARAMETER VALUE(S): individuals or systems ] receive [SELECTED PARAMETER VALUE(S): information, system components, or devices ].Operations security (OPSEC) is a systematic process by which potential adversaries can be denied information about the capabilities and intentions of organizations by identifying, controlling, and protecting generally unclassified information that specifically relates to the planning and execution of sensitive organizational activities. The OPSEC process involves five steps: identification of critical information, analysis of threats, analysis of vulnerabilities, assessment of risks, and the application of appropriate countermeasures. OPSEC controls are applied to organizational systems and the environments in which those systems operate. OPSEC controls protect the confidentiality of information, including limiting the sharing of information with suppliers, potential suppliers, and other non-organizational elements and individuals. Information critical to organizational mission and business functions includes user identities, element uses, suppliers, supply chain processes, functional requirements, security requirements, system design specifications, testing and evaluation protocols, and security control implementation details.
","uuid":"4a4af2ba-1ddb-4671-ba9b-65c8d2b3bff2","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"ae8bad47-9ded-4a96-b8b7-d0999ae62f87","text":"operations security controls","parameterId":"sc-38_odp","default":" [Assignment: organization defined operations security controls] "}],"subControls":"","tests":[{"testId":"SC-38","uuid":"01cf4ad8-ba7f-45c6-903a-5a035328e42c","test":"Determine if [SELECTED PARAMETER VALUE(S): operations security controls ] are employed to protect key organizational information throughout the system development life cycle.Systems can maintain separate execution domains for each executing process by assigning each process a separate address space. Each system process has a distinct address space so that communication between processes is performed in a manner controlled through the security functions, and one process cannot modify the executing code of another process. Maintaining separate execution domains for executing processes can be achieved, for example, by implementing separate address spaces. Process isolation technologies, including sandboxing or virtualization, logically separate software and firmware from other software, firmware, and data. Process isolation helps limit the access of potentially untrusted software to other system resources. The capability to maintain separate execution domains is available in commercial operating systems that employ multi-state processor technologies.
","uuid":"bb0d61bb-a483-43a7-a00b-3fae465fa76d","family":"System and Communications Protection","parameters":[],"subControls":"","tests":[{"testId":"SC-39","uuid":"4f99f794-6ddb-4e34-bac2-b5619cd5a2b5","test":"Determine if a separate execution domain is maintained for each executing system process.Hardware-based separation of system processes is generally less susceptible to compromise than software-based separation, thus providing greater assurance that the separation will be enforced. Hardware separation mechanisms include hardware memory management.
","uuid":"e55f8618-265b-4141-9506-4a2166b8219d","family":"System and Communications Protection","parameters":[],"subControls":"","tests":[{"testId":"SC-39(01)","uuid":"252ae5c4-de76-4f3d-94fd-2940ca5caad3","test":"Determine if hardware separation is implemented to facilitate process isolation.None.
","uuid":"4a813b50-3578-4b6d-8db8-e3b6778bd922","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"3750831a-4d63-4c1c-8732-8c22ad99d896","text":"multi-threaded processing","parameterId":"sc-39.02_odp","default":" [Assignment: organization defined multi-threaded processing] "}],"subControls":"","tests":[{"testId":"SC-39(02)","uuid":"88045a7d-0e93-4e2b-b596-925f3c652a68","test":"Determine if a separate execution domain is maintained for each thread in [SELECTED PARAMETER VALUE(S): multi-threaded processing ].Wireless link protection applies to internal and external wireless communication links that may be visible to individuals who are not authorized system users. Adversaries can exploit the signal parameters of wireless links if such links are not adequately protected. There are many ways to exploit the signal parameters of wireless links to gain intelligence, deny service, or spoof system users. Protection of wireless links reduces the impact of attacks that are unique to wireless systems. If organizations rely on commercial service providers for transmission services as commodity items rather than as fully dedicated services, it may not be possible to implement wireless link protections to the extent necessary to meet organizational security requirements.
","uuid":"be83571d-0df1-497b-9588-d89fb0e3303c","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"ab874264-2b27-444e-b2a8-973f8626fe6d","text":"organization-defined wireless links","parameterId":"sc-40_prm_1","default":" [Assignment: organization-defined wireless links] "},{"constraints":"","displayName":"","guidance":"","uuid":"5cfec222-9dbc-42d1-a034-1b8fbde478a7","text":"organization-defined types of signal parameter attacks or references to sources for such attacks","parameterId":"sc-40_prm_2","default":" [Assignment: organization-defined types of signal parameter attacks or references to sources for such attacks] "},{"constraints":"","displayName":"","guidance":"","uuid":"3f9ce57d-ed7f-451b-9138-6d23e05bea78","text":"wireless links","parameterId":"sc-40_odp.01","default":" [Assignment: organization defined wireless links] "},{"constraints":"","displayName":"","guidance":"","uuid":"92e95de1-c742-4091-adf1-ec9d17debf61","text":"types of signal parameter attacks or references to sources for such attacks","parameterId":"sc-40_odp.02","default":" [Assignment: organization defined types of signal parameter attacks or references to sources for such attacks] "},{"constraints":"","displayName":"","guidance":"","uuid":"d95f3b6a-40ca-4c44-a98b-869ff9fd4a09","text":"wireless links","parameterId":"sc-40_odp.03","default":" [Assignment: organization defined wireless links] "},{"constraints":"","displayName":"","guidance":"","uuid":"36fb200a-2434-43a0-90e7-7cc142a101b3","text":"types of signal parameter attacks or references to sources for such attacks","parameterId":"sc-40_odp.04","default":" [Assignment: organization defined types of signal parameter attacks or references to sources for such attacks] "}],"subControls":"","tests":[{"testId":"SC-40[01]","uuid":"918e7c70-bc89-4e30-bf85-ce212de290aa","test":"Determine if external [SELECTED PARAMETER VALUE(S): wireless links ] are protected from [SELECTED PARAMETER VALUE(S): types of signal parameter attacks or references to sources for such attacks ].The implementation of cryptographic mechanisms for electromagnetic interference protects systems against intentional jamming that might deny or impair communications by ensuring that wireless spread spectrum waveforms used to provide anti-jam protection are not predictable by unauthorized individuals. The implementation of cryptographic mechanisms may also coincidentally mitigate the effects of unintentional jamming due to interference from legitimate transmitters that share the same spectrum. Mission requirements, projected threats, concept of operations, and laws, executive orders, directives, regulations, policies, and standards determine levels of wireless link availability, cryptography needed, and performance.
","uuid":"f0fb16be-b174-4369-bad7-2182534e1c2a","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"e234832d-42eb-47a2-842d-079da7b9f1b7","text":"level of protection","parameterId":"sc-40.01_odp","default":" [Assignment: organization defined level of protection] "}],"subControls":"","tests":[{"testId":"SC-40(01)","uuid":"6edf7790-1bee-4e1c-8e45-8906453c5da7","test":"Determine if cryptographic mechanisms that achieve [SELECTED PARAMETER VALUE(S): level of protection ] against the effects of intentional electromagnetic interference are implemented.The implementation of cryptographic mechanisms to reduce detection potential is used for covert communications and to protect wireless transmitters from geo-location. It also ensures that the spread spectrum waveforms used to achieve a low probability of detection are not predictable by unauthorized individuals. Mission requirements, projected threats, concept of operations, and applicable laws, executive orders, directives, regulations, policies, and standards determine the levels to which wireless links are undetectable.
","uuid":"741236f4-e4ed-4dba-a819-68a8ca981a76","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"9b2039eb-f143-4afb-87b6-bd9adcfe07b4","text":"level of reduction","parameterId":"sc-40.02_odp","default":" [Assignment: organization defined level of reduction] "}],"subControls":"","tests":[{"testId":"SC-40(02)","uuid":"f8ceb5b5-5aaa-4c6e-bbb4-d27bfb5a7b81","test":"Determine if cryptographic mechanisms to reduce the detection potential of wireless links to [SELECTED PARAMETER VALUE(S): level of reduction ] are implemented.The implementation of cryptographic mechanisms to identify and reject imitative or manipulative communications ensures that the signal parameters of wireless transmissions are not predictable by unauthorized individuals. Such unpredictability reduces the probability of imitative or manipulative communications deception based on signal parameters alone.
","uuid":"b8944382-757d-4d99-99fa-9c99be75ecf2","family":"System and Communications Protection","parameters":[],"subControls":"","tests":[{"testId":"SC-40(03)","uuid":"169b56f8-a7b9-4e0c-a38f-d4f0cff59738","test":"Determine if cryptographic mechanisms are implemented to identify and reject wireless transmissions that are deliberate attempts to achieve imitative or manipulative communications deception based on signal parameters.The implementation of cryptographic mechanisms to prevent the identification of wireless transmitters protects against the unique identification of wireless transmitters for the purposes of intelligence exploitation by ensuring that anti-fingerprinting alterations to signal parameters are not predictable by unauthorized individuals. It also provides anonymity when required. Radio fingerprinting techniques identify the unique signal parameters of transmitters to fingerprint such transmitters for purposes of tracking and mission or user identification.
","uuid":"712921d6-3aed-4889-8bfe-e9a182cfe876","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"25b290ed-28ca-42fc-9305-14271fdc2b46","text":"wireless transmitters","parameterId":"sc-40.04_odp","default":" [Assignment: organization defined wireless transmitters] "}],"subControls":"","tests":[{"testId":"SC-40(04)","uuid":"7f575047-14c2-4e29-8cb7-47a1e35c26ec","test":"Determine if cryptographic mechanisms are implemented to prevent the identification of [SELECTED PARAMETER VALUE(S): wireless transmitters ] by using the transmitter signal parameters.Connection ports include Universal Serial Bus (USB), Thunderbolt, and Firewire (IEEE 1394). Input/output (I/O) devices include compact disc and digital versatile disc drives. Disabling or removing such connection ports and I/O devices helps prevent the exfiltration of information from systems and the introduction of malicious code from those ports or devices. Physically disabling or removing ports and/or devices is the stronger action.
","uuid":"44f6a213-e54e-451c-8393-d5a0e83ead92","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"a578030a-b9ad-4750-a246-3ee35f775d4f","text":"connection ports or input/output devices","parameterId":"sc-41_odp.01","default":" [Assignment: organization defined connection ports or input/output devices] "},{"constraints":"","displayName":"","guidance":"","uuid":"0b03cc8b-65d0-4b92-9326-36e663271a6f","text":"[Selection: physically; logically]","parameterId":"sc-41_odp.02","default":"[Selection: physically; logically]"},{"constraints":"","displayName":"","guidance":"","uuid":"1316f7fb-bde1-453a-b041-6d232ed1f016","text":"systems or system components","parameterId":"sc-41_odp.03","default":" [Assignment: organization defined systems or system components] "}],"subControls":"","tests":[{"testId":"SC-41","uuid":"e3208b3a-3167-49cf-84f4-080d7aa94e33","test":"Determine if [SELECTED PARAMETER VALUE(S): connection ports or input/output devices ] are [SELECTED PARAMETER VALUE(S): [Selection: physically; logically] ] disabled or removed on [SELECTED PARAMETER VALUE(S): systems or system components ].Sensor capability and data applies to types of systems or system components characterized as mobile devices, such as cellular telephones, smart phones, and tablets. Mobile devices often include sensors that can collect and record data regarding the environment where the system is in use. Sensors that are embedded within mobile devices include microphones, cameras, Global Positioning System (GPS) mechanisms, and accelerometers. While the sensors on mobiles devices provide an important function, if activated covertly, such devices can potentially provide a means for adversaries to learn valuable information about individuals and organizations. For example, remotely activating the GPS function on a mobile device could provide an adversary with the ability to track the movements of an individual. Organizations may prohibit individuals from bringing cellular telephones or digital cameras into certain designated facilities or controlled areas within facilities where classified information is stored or sensitive conversations are taking place.
","uuid":"9c8254f3-a78e-41b5-bcc9-66f58181ad3a","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"717acca8-f738-4822-8042-00786059922a","text":"[Selection (one or more): the use of devices possessing [(NESTED PARAMETER) Assignment for sc-42_odp.02: environmental sensing capabilities] in [(NESTED PARAMETER) Assignment for sc-42_odp.03: facilities, areas, or systems]; the remote activation of environmental sensing capabilities on organizational systems or system components with the following exceptions: [(NESTED PARAMETER) Assignment for sc-42_odp.04: exceptions where remote activation of sensors is allowed]]","parameterId":"sc-42_odp.01","default":"[Selection (one or more): the use of devices possessing [(NESTED PARAMETER) Assignment for sc-42_odp.02: environmental sensing capabilities] in [(NESTED PARAMETER) Assignment for sc-42_odp.03: facilities, areas, or systems]; the remote activation of environmental sensing capabilities on organizational systems or system components with the following exceptions: [(NESTED PARAMETER) Assignment for sc-42_odp.04: exceptions where remote activation of sensors is allowed]]"},{"constraints":"","displayName":"","guidance":"","uuid":"b70ba393-59d8-4e32-8352-3aea07fd4e54","text":"environmental sensing capabilities","parameterId":"sc-42_odp.02","default":" [Assignment: organization defined environmental sensing capabilities] "},{"constraints":"","displayName":"","guidance":"","uuid":"31aa5d34-682d-4c5e-b244-d39948801ebe","text":"facilities, areas, or systems","parameterId":"sc-42_odp.03","default":" [Assignment: organization defined facilities, areas, or systems] "},{"constraints":"","displayName":"","guidance":"","uuid":"bbf7f01b-839f-498e-be40-c018c004e2c7","text":"exceptions where remote activation of sensors is allowed","parameterId":"sc-42_odp.04","default":" [Assignment: organization defined exceptions where remote activation of sensors is allowed] "},{"constraints":"","displayName":"","guidance":"","uuid":"8e4ab4bc-80f4-4323-867e-2355687cf127","text":"group of users","parameterId":"sc-42_odp.05","default":" [Assignment: organization defined group of users] "}],"subControls":"","tests":[{"testId":"SC-42a.","uuid":"984a1023-c530-42c2-8945-35827558fa51","test":"Determine if [SELECTED PARAMETER VALUE(S): [Selection (one or more): the use of devices possessing [(NESTED PARAMETER) Assignment for sc-42_odp.02: environmental sensing capabilities] in [(NESTED PARAMETER) Assignment for sc-42_odp.03: facilities, areas, or systems]; the remote activation of environmental sensing capabilities on organizational systems or system components with the following exceptions: [(NESTED PARAMETER) Assignment for sc-42_odp.04: exceptions where remote activation of sensors is allowed]] ] is/are prohibited;In situations where sensors are activated by authorized individuals, it is still possible that the data or information collected by the sensors will be sent to unauthorized entities.
","uuid":"2f358dc1-85e3-4253-a264-bf7c990f211a","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"0dd8bb6c-cb6e-4269-b192-3048d90ade12","text":"sensors","parameterId":"sc-42.01_odp","default":" [Assignment: organization defined sensors] "}],"subControls":"","tests":[{"testId":"SC-42(01)","uuid":"66ed219b-9934-404c-b4d4-88a61da416b2","test":"Determine if the system is configured so that data or information collected by the [SELECTED PARAMETER VALUE(S): sensors ] is only reported to authorized individuals or roles.Information collected by sensors for a specific authorized purpose could be misused for some unauthorized purpose. For example, GPS sensors that are used to support traffic navigation could be misused to track the movements of individuals. Measures to mitigate such activities include additional training to help ensure that authorized individuals do not abuse their authority and, in the case where sensor data is maintained by external parties, contractual restrictions on the use of such data.
","uuid":"346e49b3-cc9a-4a11-80cf-ca447b201b41","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"8ba7bff3-fa0f-485c-a7a3-49db3111b6cc","text":"measures","parameterId":"sc-42.02_odp","default":" [Assignment: organization defined measures] "}],"subControls":"","tests":[{"testId":"SC-42(02)","uuid":"04b64ce6-44a5-4403-aa6b-5eeb80704e96","test":"Determine if [SELECTED PARAMETER VALUE(S): measures ] are employed so that data or information collected by [SELECTED PARAMETER VALUE(S): sensors ] is only used for authorized purposes.Awareness that organizational sensors are collecting data enables individuals to more effectively engage in managing their privacy. Measures can include conventional written notices and sensor configurations that make individuals directly or indirectly aware through other devices that the sensor is collecting information. The usability and efficacy of the notice are important considerations.
","uuid":"d0f61700-94c8-46ee-a53d-a1b312727c5b","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"20c01c20-5d4c-4e46-aa40-3c4b599ee52a","text":"measures","parameterId":"sc-42.04_odp.01","default":" [Assignment: organization defined measures] "},{"constraints":"","displayName":"","guidance":"","uuid":"c0ebdc13-15ed-4494-937d-c99d3057cf4e","text":"sensors","parameterId":"sc-42.04_odp.02","default":" [Assignment: organization defined sensors] "}],"subControls":"","tests":[{"testId":"SC-42(04)","uuid":"2275cd5f-c86b-497a-8267-85b4eab6aa6c","test":"Determine if [SELECTED PARAMETER VALUE(S): measures ] are employed to facilitate an individual’s awareness that personally identifiable information is being collected by [SELECTED PARAMETER VALUE(S): sensors ],Although policies to control for authorized use can be applied to information once it is collected, minimizing the collection of information that is not needed mitigates privacy risk at the system entry point and mitigates the risk of policy control failures. Sensor configurations include the obscuring of human features, such as blurring or pixelating flesh tones.
","uuid":"b95da380-55a8-4945-93b8-3eb792745c0b","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"744d2a59-4d3d-4288-a853-88082d0ad051","text":"sensors","parameterId":"sc-42.05_odp","default":" [Assignment: organization defined sensors] "}],"subControls":"","tests":[{"testId":"SC-42(05)","uuid":"02502282-7385-4e31-9c98-538ce4c482d0","test":"Determine if the [SELECTED PARAMETER VALUE(S): sensors ] configured to minimize the collection of information about individuals that is not needed are employed.Usage restrictions apply to all system components including but not limited to mobile code, mobile devices, wireless access, and wired and wireless peripheral components (e.g., copiers, printers, scanners, optical devices, and other similar technologies). The usage restrictions and implementation guidelines are based on the potential for system components to cause damage to the system and help to ensure that only authorized system use occurs.
","uuid":"e5e6e965-9d03-4365-8a5d-9644c8229c48","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"bffd8ff7-a530-4229-85c3-1696a9b0720a","text":"components","parameterId":"sc-43_odp","default":" [Assignment: organization defined components] "}],"subControls":"","tests":[{"testId":"SC-43a.","uuid":"79eac902-9bca-4d47-b4bb-b0019563ade1","test":"Determine if usage restrictions and implementation guidelines are established for [SELECTED PARAMETER VALUE(S): components ];Detonation chambers, also known as dynamic execution environments, allow organizations to open email attachments, execute untrusted or suspicious applications, and execute Universal Resource Locator requests in the safety of an isolated environment or a virtualized sandbox. Protected and isolated execution environments provide a means of determining whether the associated attachments or applications contain malicious code. While related to the concept of deception nets, the employment of detonation chambers is not intended to maintain a long-term environment in which adversaries can operate and their actions can be observed. Rather, detonation chambers are intended to quickly identify malicious code and either reduce the likelihood that the code is propagated to user environments of operation or prevent such propagation completely.
","uuid":"f1d91a26-2824-4111-805b-4c4263cca1a1","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"af3ef2cf-944b-4cdf-87fd-0ebbf84102a7","text":"system, system component, or location","parameterId":"sc-44_odp","default":" [Assignment: organization defined system, system component, or location] "}],"subControls":"","tests":[{"testId":"SC-44","uuid":"b50c7723-fc0f-422b-92bb-dfe7a876f54d","test":"Determine if a detonation chamber capability is employed within the [SELECTED PARAMETER VALUE(S): system, system component, or location ].Time synchronization of system clocks is essential for the correct execution of many system services, including identification and authentication processes that involve certificates and time-of-day restrictions as part of access control. Denial of service or failure to deny expired credentials may result without properly synchronized clocks within and between systems and system components. Time is commonly expressed in Coordinated Universal Time (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC. The granularity of time measurements refers to the degree of synchronization between system clocks and reference clocks, such as clocks synchronizing within hundreds of milliseconds or tens of milliseconds. Organizations may define different time granularities for system components. Time service can be critical to other security capabilities—such as access control and identification and authentication—depending on the nature of the mechanisms used to support the capabilities.
","uuid":"a5db139d-64a1-4896-b487-08a7a3e56832","family":"System and Communications Protection","parameters":[],"subControls":"","tests":[{"testId":"SC-45","uuid":"b40ed106-2268-446c-9ea2-8010045ce5de","test":"Determine if system clocks are synchronized within and between systems and system components.Synchronization of internal system clocks with an authoritative source provides uniformity of time stamps for systems with multiple system clocks and systems connected over a network.
","uuid":"f9e191ac-00ce-4be2-8140-357cefd5ad2a","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"4e1ebdd0-b986-45be-972f-a161fc605a48","text":"frequency","parameterId":"sc-45.01_odp.01","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"33148d90-8954-4a67-a60a-dcd5b80fba50","text":"authoritative time source","parameterId":"sc-45.01_odp.02","default":" [Assignment: organization defined authoritative time source] "},{"constraints":"","displayName":"","guidance":"","uuid":"56f3268b-d410-43a3-9c9f-282755934e86","text":"time period","parameterId":"sc-45.01_odp.03","default":" [Assignment: organization defined time period] "}],"subControls":"","tests":[{"testId":"SC-45(01)(a)","uuid":"96252cd6-5f23-434f-bd6a-4023b9255128","test":"Determine if the internal system clocks are compared [SELECTED PARAMETER VALUE(S): frequency ] with [SELECTED PARAMETER VALUE(S): authoritative time source ];It may be necessary to employ geolocation information to determine that the secondary authoritative time source is in a different geographic region.
","uuid":"859cb47c-7f50-4280-b16a-e20ed921cf98","family":"System and Communications Protection","parameters":[],"subControls":"","tests":[{"testId":"SC-45(02)(a)","uuid":"ebed0238-ba48-4338-8c38-a6fffb82a700","test":"Determine if a secondary authoritative time source is identified that is in a different geographic region than the primary authoritative time source;For logical policy enforcement mechanisms, organizations avoid creating a logical path between interfaces to prevent the ability to bypass the policy enforcement mechanism. For physical policy enforcement mechanisms, the robustness of physical isolation afforded by the physical implementation of policy enforcement to preclude the presence of logical covert channels penetrating the security domain may be needed. Contact ncdsmo@nsa.gov for more information.
","uuid":"f325cda0-dacb-4b4a-816f-1de1c1a14e24","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"b027bda1-3346-4cd7-9ade-159b2b77884b","text":"[Selection: physically; logically]","parameterId":"sc-46_odp","default":"[Selection: physically; logically]"}],"subControls":"","tests":[{"testId":"SC-46","uuid":"98340a29-6d14-4793-8527-6c41a84fdd66","test":"Determine if a policy enforcement mechanism is [SELECTED PARAMETER VALUE(S): [Selection: physically; logically] ] implemented between the physical and/or network interfaces for the connecting security domains.An incident, whether adversarial- or nonadversarial-based, can disrupt established communications paths used for system operations and organizational command and control. Alternate communications paths reduce the risk of all communications paths being affected by the same incident. To compound the problem, the inability of organizational officials to obtain timely information about disruptions or to provide timely direction to operational elements after a communications path incident, can impact the ability of the organization to respond to such incidents in a timely manner. Establishing alternate communications paths for command and control purposes, including designating alternative decision makers if primary decision makers are unavailable and establishing the extent and limitations of their actions, can greatly facilitate the organization’s ability to continue to operate and take appropriate actions during an incident.
","uuid":"a7fdf655-f38f-4345-aa3f-4551cbbff82d","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"29d1efa8-5da4-4925-af01-c459554a40ca","text":"alternate communication paths","parameterId":"sc-47_odp","default":" [Assignment: organization defined alternate communication paths] "}],"subControls":"","tests":[{"testId":"SC-47","uuid":"85030f83-98ae-4633-b965-656cedc35dbc","test":"Determine if [SELECTED PARAMETER VALUE(S): alternate communication paths ] are established for system operations and operational command and control.Adversaries may take various paths and use different approaches as they move laterally through an organization (including its systems) to reach their target or as they attempt to exfiltrate information from the organization. The organization often only has a limited set of monitoring and detection capabilities, and they may be focused on the critical or likely infiltration or exfiltration paths. By using communications paths that the organization typically does not monitor, the adversary can increase its chances of achieving its desired goals. By relocating its sensors or monitoring capabilities to new locations, the organization can impede the adversary’s ability to achieve its goals. The relocation of the sensors or monitoring capabilities might be done based on threat information that the organization has acquired or randomly to confuse the adversary and make its lateral transition through the system or organization more challenging.
","uuid":"f636f663-0fca-4602-9a1e-63d7fa77d4b0","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"adf8646a-a55b-49e1-b1eb-510fd86631fb","text":"sensors and monitoring capabilities","parameterId":"sc-48_odp.01","default":" [Assignment: organization defined sensors and monitoring capabilities] "},{"constraints":"","displayName":"","guidance":"","uuid":"9af39b63-420d-468a-8458-224959cfc5ae","text":"locations","parameterId":"sc-48_odp.02","default":" [Assignment: organization defined locations] "},{"constraints":"","displayName":"","guidance":"","uuid":"b5571888-2b7f-4055-8847-f39095a58c66","text":"conditions or circumstances","parameterId":"sc-48_odp.03","default":" [Assignment: organization defined conditions or circumstances] "}],"subControls":"","tests":[{"testId":"SC-48","uuid":"84e1b5cc-1324-4159-9fcc-cf984334973e","test":"Determine if [SELECTED PARAMETER VALUE(S): sensors and monitoring capabilities ] are relocated to [SELECTED PARAMETER VALUE(S): locations ] under [SELECTED PARAMETER VALUE(S): conditions or circumstances ].None.
","uuid":"d27d1c26-b3a6-45ed-b33f-f5d895db4ad5","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"3196abab-016c-4d13-87ad-03299428b56a","text":"sensors and monitoring capabilities","parameterId":"sc-48.01_odp.01","default":" [Assignment: organization defined sensors and monitoring capabilities] "},{"constraints":"","displayName":"","guidance":"","uuid":"32e69a8c-05bc-4ecd-8377-9b4f27be7e13","text":"locations","parameterId":"sc-48.01_odp.02","default":" [Assignment: organization defined locations] "},{"constraints":"","displayName":"","guidance":"","uuid":"9f5b86d0-efd3-49e4-af11-6d8b74c1ea99","text":"conditions or circumstances","parameterId":"sc-48.01_odp.03","default":" [Assignment: organization defined conditions or circumstances] "}],"subControls":"","tests":[{"testId":"SC-48(01)","uuid":"0fff068f-04a3-4427-bc56-75a4e666e332","test":"Determine if [SELECTED PARAMETER VALUE(S): sensors and monitoring capabilities ] are dynamically relocated to [SELECTED PARAMETER VALUE(S): locations ] under [SELECTED PARAMETER VALUE(S): conditions or circumstances ].System owners may require additional strength of mechanism and robustness to ensure domain separation and policy enforcement for specific types of threats and environments of operation. Hardware-enforced separation and policy enforcement provide greater strength of mechanism than software-enforced separation and policy enforcement.
","uuid":"e2c757fc-b541-4a95-b72c-3f882b713f45","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"5ace927b-c108-479d-87c5-4347142712a7","text":"security domains","parameterId":"sc-49_odp","default":" [Assignment: organization defined security domains] "}],"subControls":"","tests":[{"testId":"SC-49","uuid":"481d8518-63db-4897-87fc-685e728a662e","test":"Determine if hardware-enforced separation and policy enforcement mechanisms are implemented between [SELECTED PARAMETER VALUE(S): security domains ].System owners may require additional strength of mechanism to ensure domain separation and policy enforcement for specific types of threats and environments of operation.
","uuid":"8fba447d-e500-471b-8390-5c8aae511e04","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"1b595abc-a303-47f6-8fca-758795742785","text":"security domains","parameterId":"sc-50_odp","default":" [Assignment: organization defined security domains] "}],"subControls":"","tests":[{"testId":"SC-50","uuid":"2de5ff4c-6385-4d6f-9fae-eaa157cc39d0","test":"Determine if software-enforced separation and policy enforcement mechanisms are implemented between [SELECTED PARAMETER VALUE(S): security domains ].None.
","uuid":"505f501a-e0cb-4850-954c-3e88de3c7394","family":"System and Communications Protection","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"04f64921-ca5b-47a8-a396-73eea7fbf04f","text":"system firmware components","parameterId":"sc-51_odp.01","default":" [Assignment: organization defined system firmware components] "},{"constraints":"","displayName":"","guidance":"","uuid":"e7756be5-ef74-42b9-8f21-1a01bd72e5d0","text":"authorized individuals","parameterId":"sc-51_odp.02","default":" [Assignment: organization defined authorized individuals] "}],"subControls":"","tests":[{"testId":"SC-51a.","uuid":"19f51c8a-6c43-47f4-9d41-f6700d442c24","test":"Determine if hardware-based write-protect for [SELECTED PARAMETER VALUE(S): system firmware components ] is employed;System and information integrity policy and procedures address the controls in the SI family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of system and information integrity policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission or business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to system and information integrity policy and procedures include assessment or audit findings, security incidents or breaches, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure.
","uuid":"92abb9fd-0038-4772-9c6a-81f6e204ab3f","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"f50ea35c-409d-4d67-8165-213873b75eae","text":"organization-defined personnel or roles","parameterId":"si-1_prm_1","default":" [Assignment: organization-defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"b40444c4-942b-4fd6-bef0-ca1750951e90","text":"personnel or roles","parameterId":"si-01_odp.01","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"0622606a-c89f-427c-b047-0d72b194a513","text":"personnel or roles","parameterId":"si-01_odp.02","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"6a472295-c156-4e60-b1a4-d18f43efa030","text":"[Selection (one or more): organization-level; mission/business process-level; system-level]","parameterId":"si-01_odp.03","default":"[Selection (one or more): organization-level; mission/business process-level; system-level]"},{"constraints":"","displayName":"","guidance":"","uuid":"fe3cc851-afbd-45f5-9e30-2dacf8586d48","text":"official","parameterId":"si-01_odp.04","default":" [Assignment: organization defined official] "},{"constraints":"","displayName":"","guidance":"","uuid":"b690d9ee-e339-4c96-89ac-5d0fdbb92f43","text":"frequency","parameterId":"si-01_odp.05","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"3b3fce60-be76-4985-98b7-688349f2594f","text":"events","parameterId":"si-01_odp.06","default":" [Assignment: organization defined events] "},{"constraints":"","displayName":"","guidance":"","uuid":"7238e475-219c-44cc-8301-5a55888e5af4","text":"frequency","parameterId":"si-01_odp.07","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"680d297d-1b19-4e9b-a587-fd93f3b479ca","text":"events","parameterId":"si-01_odp.08","default":" [Assignment: organization defined events] "}],"subControls":"","tests":[{"testId":"SI-01a.[01]","uuid":"5511191d-eef2-4f35-a5b6-8a570731e5f9","test":"Determine if a system and information integrity policy is developed and documented;The need to remediate system flaws applies to all types of software and firmware. Organizations identify systems affected by software flaws, including potential vulnerabilities resulting from those flaws, and report this information to designated organizational personnel with information security and privacy responsibilities. Security-relevant updates include patches, service packs, and malicious code signatures. Organizations also address flaws discovered during assessments, continuous monitoring, incident response activities, and system error handling. By incorporating flaw remediation into configuration management processes, required remediation actions can be tracked and verified.
Organization-defined time periods for updating security-relevant software and firmware may vary based on a variety of risk factors, including the security category of the system, the criticality of the update (i.e., severity of the vulnerability related to the discovered flaw), the organizational risk tolerance, the mission supported by the system, or the threat environment. Some types of flaw remediation may require more testing than other types. Organizations determine the type of testing needed for the specific type of flaw remediation activity under consideration and the types of changes that are to be configuration-managed. In some situations, organizations may determine that the testing of software or firmware updates is not necessary or practical, such as when implementing simple malicious code signature updates. In testing decisions, organizations consider whether security-relevant software or firmware updates are obtained from authorized sources with appropriate digital signatures.
","uuid":"c6f06954-1669-4ebc-b8bc-cb47bc3bf3bf","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"eb69c2f4-11ba-4186-b632-996b09a03f16","text":"time period","parameterId":"si-02_odp","default":" [Assignment: organization defined time period] "}],"subControls":"","tests":[{"testId":"SI-02a.[01]","uuid":"ab7d545a-c2db-4f8b-9a75-c82629ca4889","test":"Determine if system flaws are identified;Automated mechanisms can track and determine the status of known flaws for system components.
","uuid":"9449ac9d-1fc8-461c-9dfb-94c89c09b93d","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"e18f45c0-9553-40ee-a916-c39de52e2f5d","text":"automated mechanisms","parameterId":"si-02.02_odp.01","default":" [Assignment: organization defined automated mechanisms] "},{"constraints":"","displayName":"","guidance":"","uuid":"10c77d48-0a4a-4084-bfe7-f969e433d829","text":"frequency","parameterId":"si-02.02_odp.02","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"SI-02(02)","uuid":"96f2ae4b-506d-4483-83ee-a3296b38f3df","test":"Determine if system components have applicable security-relevant software and firmware updates installed [SELECTED PARAMETER VALUE(S): frequency ] using [SELECTED PARAMETER VALUE(S): automated mechanisms ].Organizations determine the time it takes on average to correct system flaws after such flaws have been identified and subsequently establish organizational benchmarks (i.e., time frames) for taking corrective actions. Benchmarks can be established by the type of flaw or the severity of the potential vulnerability if the flaw can be exploited.
","uuid":"87e46824-a0d2-4b09-aeed-faa9725e034f","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"153fe5a1-ef94-489b-853e-b8aed46b6c6f","text":"benchmarks","parameterId":"si-02.03_odp","default":" [Assignment: organization defined benchmarks] "}],"subControls":"","tests":[{"testId":"SI-02(03)(a)","uuid":"0099cb30-db65-4455-80cd-9f0a01cda1fe","test":"Determine if the time between flaw identification and flaw remediation is measured;Using automated tools to support patch management helps to ensure the timeliness and completeness of system patching operations.
","uuid":"c6b37be3-2ad6-43ed-82c2-d04d8c98570f","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"3bdfc3fb-8951-4e41-95ff-4b05cc158e24","text":"components","parameterId":"si-02.04_odp","default":" [Assignment: organization defined components] "}],"subControls":"","tests":[{"testId":"SI-02(04)","uuid":"c702bc74-5a46-481b-8a24-f1f7b32e5152","test":"Determine if automated patch management tools are employed to facilitate flaw remediation to [SELECTED PARAMETER VALUE(S): components ].Due to system integrity and availability concerns, organizations consider the methodology used to carry out automatic updates. Organizations balance the need to ensure that the updates are installed as soon as possible with the need to maintain configuration management and control with any mission or operational impacts that automatic updates might impose.
","uuid":"b089eea5-228d-4ef4-9851-e03ac890d646","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"28b97c08-1de8-4d6c-81e4-e12943dc4185","text":"security-relevant software and firmware updates","parameterId":"si-02.05_odp.01","default":" [Assignment: organization defined security-relevant software and firmware updates] "},{"constraints":"","displayName":"","guidance":"","uuid":"4a3f8062-ca30-47ea-874b-c093be17eb21","text":"system components","parameterId":"si-02.05_odp.02","default":" [Assignment: organization defined system components] "}],"subControls":"","tests":[{"testId":"SI-02(05)","uuid":"919f507e-f9f0-4a68-92ee-30ce0c881cdc","test":"Determine if [SELECTED PARAMETER VALUE(S): security-relevant software and firmware updates ] are installed automatically to [SELECTED PARAMETER VALUE(S): system components ].Previous versions of software or firmware components that are not removed from the system after updates have been installed may be exploited by adversaries. Some products may automatically remove previous versions of software and firmware from the system.
","uuid":"9d4590bb-f0a7-4377-b43f-9cc47dfb7aaa","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"900330be-97de-4660-b8bf-e65c25ae00a4","text":"software and firmware components","parameterId":"si-02.06_odp","default":" [Assignment: organization defined software and firmware components] "}],"subControls":"","tests":[{"testId":"SI-02(06)","uuid":"79976efb-dcd5-497b-bcaf-99170c3da502","test":"Determine if previous versions of [SELECTED PARAMETER VALUE(S): software and firmware components ] are removed after updated versions have been installed.System entry and exit points include firewalls, remote access servers, workstations, electronic mail servers, web servers, proxy servers, notebook computers, and mobile devices. Malicious code includes viruses, worms, Trojan horses, and spyware. Malicious code can also be encoded in various formats contained within compressed or hidden files or hidden in files using techniques such as steganography. Malicious code can be inserted into systems in a variety of ways, including by electronic mail, the world-wide web, and portable storage devices. Malicious code insertions occur through the exploitation of system vulnerabilities. A variety of technologies and methods exist to limit or eliminate the effects of malicious code.
Malicious code protection mechanisms include both signature- and nonsignature-based technologies. Nonsignature-based detection mechanisms include artificial intelligence techniques that use heuristics to detect, analyze, and describe the characteristics or behavior of malicious code and to provide controls against such code for which signatures do not yet exist or for which existing signatures may not be effective. Malicious code for which active signatures do not yet exist or may be ineffective includes polymorphic malicious code (i.e., code that changes signatures when it replicates). Nonsignature-based mechanisms also include reputation-based technologies. In addition to the above technologies, pervasive configuration management, comprehensive software integrity controls, and anti-exploitation software may be effective in preventing the execution of unauthorized code. Malicious code may be present in commercial off-the-shelf software as well as custom-built software and could include logic bombs, backdoors, and other types of attacks that could affect organizational mission and business functions.
In situations where malicious code cannot be detected by detection methods or technologies, organizations rely on other types of controls, including secure coding practices, configuration management and control, trusted procurement processes, and monitoring practices to ensure that software does not perform functions other than the functions intended. Organizations may determine that, in response to the detection of malicious code, different actions may be warranted. For example, organizations can define actions in response to malicious code detection during periodic scans, the detection of malicious downloads, or the detection of maliciousness when attempting to open or execute files.
","uuid":"3c94d63e-34e0-4b6c-82d1-cfcf8c035735","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"38394961-05d7-41f2-864b-caa12bf791eb","text":"[Selection (one or more): signature-based; non-signature-based]","parameterId":"si-03_odp.01","default":"[Selection (one or more): signature-based; non-signature-based]"},{"constraints":"","displayName":"","guidance":"","uuid":"c61eed3b-fe3b-4548-9c57-e78aecddd400","text":"frequency","parameterId":"si-03_odp.02","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"c1376d75-0a66-4114-8e9d-96db04bfb635","text":"[Selection (one or more): endpoint; network entry and exit points]","parameterId":"si-03_odp.03","default":"[Selection (one or more): endpoint; network entry and exit points]"},{"constraints":"","displayName":"","guidance":"","uuid":"0280cd56-6f48-4d8e-be03-90d1ea290ba2","text":"[Selection (one or more): block malicious code; quarantine malicious code; take [(NESTED PARAMETER) Assignment for si-03_odp.05: action]]","parameterId":"si-03_odp.04","default":"[Selection (one or more): block malicious code; quarantine malicious code; take [(NESTED PARAMETER) Assignment for si-03_odp.05: action]]"},{"constraints":"","displayName":"","guidance":"","uuid":"a6885d6d-f8fb-4f9d-a271-82548c42698c","text":"action","parameterId":"si-03_odp.05","default":" [Assignment: organization defined action] "},{"constraints":"","displayName":"","guidance":"","uuid":"a23b9320-aac5-434b-b07a-e4ff9c6073ce","text":"personnel or roles","parameterId":"si-03_odp.06","default":" [Assignment: organization defined personnel or roles] "}],"subControls":"","tests":[{"testId":"SI-03a.[01]","uuid":"1a49af8d-9c1d-40f8-9847-c1ef6b02c371","test":"Determine if [SELECTED PARAMETER VALUE(S): [Selection (one or more): signature-based; non-signature-based] ] malicious code protection mechanisms are implemented at system entry and exit points to detect malicious code;Protection mechanisms for malicious code are typically categorized as security-related software and, as such, are only updated by organizational personnel with appropriate access privileges.
","uuid":"aea29473-dd92-4e92-a29f-1351f8e36dd2","family":"System and Information Integrity","parameters":[],"subControls":"","tests":[{"testId":"SI-03(04)","uuid":"28a4ccc1-9728-4d19-a61a-6ecb2bbd840f","test":"Determine if malicious code protection mechanisms are updated only when directed by a privileged user.None.
","uuid":"a0e6f271-badf-4892-979b-9e6faa78c335","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"c7c6550f-ca64-42b3-b32d-b1264e97e199","text":"frequency","parameterId":"si-03.06_odp","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"SI-03(06)(a)","uuid":"f2eec2e2-f210-4cf5-b8dc-60a7ad69fffd","test":"Determine if malicious code protection mechanisms are tested [SELECTED PARAMETER VALUE(S): frequency ] by introducing known benign code into the system;Detecting unauthorized commands can be applied to critical interfaces other than kernel-based interfaces, including interfaces with virtual machines and privileged applications. Unauthorized operating system commands include commands for kernel functions from system processes that are not trusted to initiate such commands as well as commands for kernel functions that are suspicious even though commands of that type are reasonable for processes to initiate. Organizations can define the malicious commands to be detected by a combination of command types, command classes, or specific instances of commands. Organizations can also define hardware components by component type, component, component location in the network, or a combination thereof. Organizations may select different actions for different types, classes, or instances of malicious commands.
","uuid":"d850bdb8-1edb-42cc-b8c9-3d68dfa18def","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"c4b62b40-2fbe-46d0-a3d2-8b935482a74d","text":"unauthorized operating system commands","parameterId":"si-03.08_odp.01","default":" [Assignment: organization defined unauthorized operating system commands] "},{"constraints":"","displayName":"","guidance":"","uuid":"0d1dd0d1-f879-4699-b591-06e30c383c09","text":"system hardware components","parameterId":"si-03.08_odp.02","default":" [Assignment: organization defined system hardware components] "},{"constraints":"","displayName":"","guidance":"","uuid":"40b7d11b-4e64-4c37-a1bf-12d306755f43","text":"[Selection (one or more): issue a warning; audit the command execution; prevent the execution of the command]","parameterId":"si-03.08_odp.03","default":"[Selection (one or more): issue a warning; audit the command execution; prevent the execution of the command]"}],"subControls":"","tests":[{"testId":"SI-03(08)(a)","uuid":"31a02885-6875-49fb-858a-a398d62ab611","test":"Determine if [SELECTED PARAMETER VALUE(S): unauthorized operating system commands ] are detected through the kernel application programming interface on [SELECTED PARAMETER VALUE(S): system hardware components ];The use of malicious code analysis tools provides organizations with a more in-depth understanding of adversary tradecraft (i.e., tactics, techniques, and procedures) and the functionality and purpose of specific instances of malicious code. Understanding the characteristics of malicious code facilitates effective organizational responses to current and future threats. Organizations can conduct malicious code analyses by employing reverse engineering techniques or by monitoring the behavior of executing code.
","uuid":"426e2129-b721-47f5-9d13-44099ab156d8","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"e43b56d9-b49d-4a92-9200-e65c5244b57b","text":"tools and techniques","parameterId":"si-03.10_odp","default":" [Assignment: organization defined tools and techniques] "}],"subControls":"","tests":[{"testId":"SI-03(10)(a)","uuid":"0141d00a-0291-4642-88ed-e62de6f089ab","test":"Determine if [SELECTED PARAMETER VALUE(S): tools and techniques ] are employed to analyze the characteristics and behavior of malicious code;System monitoring includes external and internal monitoring. External monitoring includes the observation of events occurring at external interfaces to the system. Internal monitoring includes the observation of events occurring within the system. Organizations monitor systems by observing audit activities in real time or by observing other system aspects such as access patterns, characteristics of access, and other actions. The monitoring objectives guide and inform the determination of the events. System monitoring capabilities are achieved through a variety of tools and techniques, including intrusion detection and prevention systems, malicious code protection software, scanning tools, audit record monitoring software, and network monitoring software.
Depending on the security architecture, the distribution and configuration of monitoring devices may impact throughput at key internal and external boundaries as well as at other locations across a network due to the introduction of network throughput latency. If throughput management is needed, such devices are strategically located and deployed as part of an established organization-wide security architecture. Strategic locations for monitoring devices include selected perimeter locations and near key servers and server farms that support critical applications. Monitoring devices are typically employed at the managed interfaces associated with controls SC-7 and AC-17 . The information collected is a function of the organizational monitoring objectives and the capability of systems to support such objectives. Specific types of transactions of interest include Hypertext Transfer Protocol (HTTP) traffic that bypasses HTTP proxies. System monitoring is an integral part of organizational continuous monitoring and incident response programs, and output from system monitoring serves as input to those programs. System monitoring requirements, including the need for specific types of system monitoring, may be referenced in other controls (e.g., AC-2g, AC-2(7), AC-2(12)(a), AC-17(1), AU-13, AU-13(1), AU-13(2), CM-3f, CM-6d, MA-3a, MA-4a, SC-5(3)(b), SC-7a, SC-7(24)(b), SC-18b, SC-43b ). Adjustments to levels of system monitoring are based on law enforcement information, intelligence information, or other sources of information. The legality of system monitoring activities is based on applicable laws, executive orders, directives, regulations, policies, standards, and guidelines.
","uuid":"a681be71-9a8f-4186-940c-feaf379f14a3","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"7d6558cc-60be-489d-98d2-9b4c898d3546","text":"monitoring objectives","parameterId":"si-04_odp.01","default":" [Assignment: organization defined monitoring objectives] "},{"constraints":"","displayName":"","guidance":"","uuid":"142e44e4-6446-455e-8082-6bb4f12b81b9","text":"techniques and methods","parameterId":"si-04_odp.02","default":" [Assignment: organization defined techniques and methods] "},{"constraints":"","displayName":"","guidance":"","uuid":"af5b3cb3-43c6-4ae1-b653-daef5ecd4563","text":"system monitoring information","parameterId":"si-04_odp.03","default":" [Assignment: organization defined system monitoring information] "},{"constraints":"","displayName":"","guidance":"","uuid":"1ab05dea-8539-4966-82f2-727cddfae06d","text":"personnel or roles","parameterId":"si-04_odp.04","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"234f01d5-18a9-449d-9534-6d3f33231178","text":"[Selection (one or more): as needed; [(NESTED PARAMETER) Assignment for si-04_odp.06: frequency]]","parameterId":"si-04_odp.05","default":"[Selection (one or more): as needed; [(NESTED PARAMETER) Assignment for si-04_odp.06: frequency]]"},{"constraints":"","displayName":"","guidance":"","uuid":"4a233ad6-fc5a-46b4-b4c6-2b55125f2507","text":"frequency","parameterId":"si-04_odp.06","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"SI-04a.01","uuid":"15bb0b88-891a-4db2-bfed-b4fbcf12075f","test":"Determine if the system is monitored to detect attacks and indicators of potential attacks in accordance with [SELECTED PARAMETER VALUE(S): monitoring objectives ];Linking individual intrusion detection tools into a system-wide intrusion detection system provides additional coverage and effective detection capabilities. The information contained in one intrusion detection tool can be shared widely across the organization, making the system-wide detection capability more robust and powerful.
","uuid":"c89f5b25-5379-4c2b-bc55-d291ba5646db","family":"System and Information Integrity","parameters":[],"subControls":"","tests":[{"testId":"SI-04(01)[01]","uuid":"d519d547-0026-4767-a07f-2338863516d8","test":"Determine if individual intrusion detection tools are connected to a system-wide intrusion detection system;Automated tools and mechanisms include host-based, network-based, transport-based, or storage-based event monitoring tools and mechanisms or security information and event management (SIEM) technologies that provide real-time analysis of alerts and notifications generated by organizational systems. Automated monitoring techniques can create unintended privacy risks because automated controls may connect to external or otherwise unrelated systems. The matching of records between these systems may create linkages with unintended consequences. Organizations assess and document these risks in their privacy impact assessment and make determinations that are in alignment with their privacy program plan.
","uuid":"17f7b5da-42a9-4d06-9c89-c7cd3127840b","family":"System and Information Integrity","parameters":[],"subControls":"","tests":[{"testId":"SI-04(02)","uuid":"22bfbc17-eaf4-4f91-896f-32a5070a5dd0","test":"Determine if automated tools and mechanisms are employed to support a near real-time analysis of events.Using automated tools and mechanisms to integrate intrusion detection tools and mechanisms into access and flow control mechanisms facilitates a rapid response to attacks by enabling the reconfiguration of mechanisms in support of attack isolation and elimination.
","uuid":"7d63ab5f-062d-4ac7-aafc-041763cb80f7","family":"System and Information Integrity","parameters":[],"subControls":"","tests":[{"testId":"SI-04(03)[01]","uuid":"030df089-911d-4d7c-b7f8-d8fea67b31fd","test":"Determine if automated tools and mechanisms are employed to integrate intrusion detection tools and mechanisms into access control mechanisms;Unusual or unauthorized activities or conditions related to system inbound and outbound communications traffic includes internal traffic that indicates the presence of malicious code or unauthorized use of legitimate code or credentials within organizational systems or propagating among system components, signaling to external systems, and the unauthorized exporting of information. Evidence of malicious code or unauthorized use of legitimate code or credentials is used to identify potentially compromised systems or system components.
","uuid":"b0d7fad5-83bc-4dbc-aaa3-d87c3463d769","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"8f4c7fd6-52ed-4a41-91d6-ad77968b838b","text":"organization-defined frequency","parameterId":"si-4.4_prm_1","default":" [Assignment: organization-defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"5734d1e9-e0f2-425f-8103-41005601ca45","text":"organization-defined unusual or unauthorized activities or conditions","parameterId":"si-4.4_prm_2","default":" [Assignment: organization-defined unusual or unauthorized activities or conditions] "},{"constraints":"","displayName":"","guidance":"","uuid":"2ec43a71-809b-47ea-aec1-81a2cb7a7477","text":"frequency","parameterId":"si-04.04_odp.01","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"60c0908f-f2f8-4109-8dab-5af393255710","text":"unusual or unauthorized activities or conditions","parameterId":"si-04.04_odp.02","default":" [Assignment: organization defined unusual or unauthorized activities or conditions] "},{"constraints":"","displayName":"","guidance":"","uuid":"5309ee33-f333-4945-8cb1-852e350354f0","text":"frequency","parameterId":"si-04.04_odp.03","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"062f7ef7-e9db-48c5-892e-e2c0bfdba30e","text":"unusual or unauthorized activities or conditions","parameterId":"si-04.04_odp.04","default":" [Assignment: organization defined unusual or unauthorized activities or conditions] "}],"subControls":"","tests":[{"testId":"SI-04(04)(a)[01]","uuid":"7e7483ff-9404-491a-b61c-603895085c13","test":"Determine if criteria for unusual or unauthorized activities or conditions for inbound communications traffic are defined;Alerts may be generated from a variety of sources, including audit records or inputs from malicious code protection mechanisms, intrusion detection or prevention mechanisms, or boundary protection devices such as firewalls, gateways, and routers. Alerts can be automated and may be transmitted telephonically, by electronic mail messages, or by text messaging. Organizational personnel on the alert notification list can include system administrators, mission or business owners, system owners, information owners/stewards, senior agency information security officers, senior agency officials for privacy, system security officers, or privacy officers. In contrast to alerts generated by the system, alerts generated by organizations in SI-4(12) focus on information sources external to the system, such as suspicious activity reports and reports on potential insider threats.
","uuid":"014d703b-505e-447f-96fc-88b0ef7e9be5","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"c8cad872-ad48-46a1-9fde-b0f37261749d","text":"personnel or roles","parameterId":"si-04.05_odp.01","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"47ee33d9-49e8-4de3-b79a-435e9ffd8019","text":"compromise indicators","parameterId":"si-04.05_odp.02","default":" [Assignment: organization defined compromise indicators] "}],"subControls":"","tests":[{"testId":"SI-04(05)","uuid":"3c6d4a50-7410-484b-84d2-8c7c52cecc48","test":"Determine if [SELECTED PARAMETER VALUE(S): personnel or roles ] are alerted when system-generated [SELECTED PARAMETER VALUE(S): compromise indicators ] occur.Least-disruptive actions include initiating requests for human responses.
","uuid":"8b147121-2906-4cee-9580-11f45eb0d869","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"bfbb4c50-a32c-42b4-8689-1515d2122be4","text":"incident response personnel","parameterId":"si-04.07_odp.01","default":" [Assignment: organization defined incident response personnel] "},{"constraints":"","displayName":"","guidance":"","uuid":"6626b337-0b1f-42f0-bb06-d24f0bfc16a4","text":"least-disruptive actions","parameterId":"si-04.07_odp.02","default":" [Assignment: organization defined least-disruptive actions] "}],"subControls":"","tests":[{"testId":"SI-04(07)(a)","uuid":"d1d72727-b03d-4509-9e13-f714ea0138e1","test":"Determine if [SELECTED PARAMETER VALUE(S): incident response personnel ] are notified of detected suspicious events;Testing intrusion-monitoring tools and mechanisms is necessary to ensure that the tools and mechanisms are operating correctly and continue to satisfy the monitoring objectives of organizations. The frequency and depth of testing depends on the types of tools and mechanisms used by organizations and the methods of deployment.
","uuid":"a27d2d5d-0cc2-4b8e-87e3-db815901004a","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"7eb1b2c6-42e3-4f11-a1f1-eed68c14227d","text":"frequency","parameterId":"si-04.09_odp","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"SI-04(09)","uuid":"46cc1b5b-eacd-43ff-9e58-e3c197f7b791","test":"Determine if intrusion-monitoring tools and mechanisms are tested [SELECTED PARAMETER VALUE(S): frequency ].Organizations balance the need to encrypt communications traffic to protect data confidentiality with the need to maintain visibility into such traffic from a monitoring perspective. Organizations determine whether the visibility requirement applies to internal encrypted traffic, encrypted traffic intended for external destinations, or a subset of the traffic types.
","uuid":"9d917e07-571b-44d1-97b9-9caa1044ffd0","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"49a35f73-923a-4702-863b-ba8ee33cb3a4","text":"encrypted communications traffic","parameterId":"si-04.10_odp.01","default":" [Assignment: organization defined encrypted communications traffic] "},{"constraints":"","displayName":"","guidance":"","uuid":"dc44e50f-e345-4f3e-874b-c89f222b9bc6","text":"system monitoring tools and mechanisms","parameterId":"si-04.10_odp.02","default":" [Assignment: organization defined system monitoring tools and mechanisms] "}],"subControls":"","tests":[{"testId":"SI-04(10)","uuid":"abe4edb8-735f-4ab6-b443-c7db0dd938d3","test":"Determine if provisions are made so that [SELECTED PARAMETER VALUE(S): encrypted communications traffic ] is visible to [SELECTED PARAMETER VALUE(S): system monitoring tools and mechanisms ].Organization-defined interior points include subnetworks and subsystems. Anomalies within organizational systems include large file transfers, long-time persistent connections, attempts to access information from unexpected locations, the use of unusual protocols and ports, the use of unmonitored network protocols (e.g., IPv6 usage during IPv4 transition), and attempted communications with suspected malicious external addresses.
","uuid":"919d49fb-1690-4796-9853-62406b8fab29","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"bd2c2b8a-58ef-4a03-9346-7f3ea56ad7fd","text":"interior points","parameterId":"si-04.11_odp","default":" [Assignment: organization defined interior points] "}],"subControls":"","tests":[{"testId":"SI-04(11)[01]","uuid":"f2c82335-db38-40b6-b762-6c460a23ed6a","test":"Determine if outbound communications traffic at the external interfaces to the system is analyzed to discover anomalies;Organizational personnel on the system alert notification list include system administrators, mission or business owners, system owners, senior agency information security officer, senior agency official for privacy, system security officers, or privacy officers. Automated organization-generated alerts are the security alerts generated by organizations and transmitted using automated means. The sources for organization-generated alerts are focused on other entities such as suspicious activity reports and reports on potential insider threats. In contrast to alerts generated by the organization, alerts generated by the system in SI-4(5) focus on information sources that are internal to the systems, such as audit records.
","uuid":"acb070d9-8879-4d99-968d-72793689ae35","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"5af04ece-4252-4f53-8581-c369053c177f","text":"personnel or roles","parameterId":"si-04.12_odp.01","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"b06c4f35-df02-4e27-ace7-144f89f79ade","text":"automated mechanisms","parameterId":"si-04.12_odp.02","default":" [Assignment: organization defined automated mechanisms] "},{"constraints":"","displayName":"","guidance":"","uuid":"89ffc617-d105-4ec7-9d13-2db445831ea1","text":"activities that trigger alerts","parameterId":"si-04.12_odp.03","default":" [Assignment: organization defined activities that trigger alerts] "}],"subControls":"","tests":[{"testId":"SI-04(12)","uuid":"a7afe00e-d22c-4af1-b0e2-d1802f5876e7","test":"Determine if [SELECTED PARAMETER VALUE(S): personnel or roles ] is/are alerted using [SELECTED PARAMETER VALUE(S): automated mechanisms ] when [SELECTED PARAMETER VALUE(S): activities that trigger alerts ] indicate inappropriate or unusual activities with security or privacy implications.Identifying and understanding common communications traffic and event patterns help organizations provide useful information to system monitoring devices to more effectively identify suspicious or anomalous traffic and events when they occur. Such information can help reduce the number of false positives and false negatives during system monitoring.
","uuid":"f71410bd-1467-41f4-b9b2-efbf39608a58","family":"System and Information Integrity","parameters":[],"subControls":"","tests":[{"testId":"SI-04(13)(a)[01]","uuid":"f1379a5b-1312-43f4-b889-a11a09ea968b","test":"Determine if communications traffic for the system is analyzed;Wireless signals may radiate beyond organizational facilities. Organizations proactively search for unauthorized wireless connections, including the conduct of thorough scans for unauthorized wireless access points. Wireless scans are not limited to those areas within facilities containing systems but also include areas outside of facilities to verify that unauthorized wireless access points are not connected to organizational systems.
","uuid":"beb301f6-838c-4d08-bc8d-53462e51d400","family":"System and Information Integrity","parameters":[],"subControls":"","tests":[{"testId":"SI-04(14)[01]","uuid":"ec52ba77-cf1a-4fc8-aa3a-13c1a2b598d3","test":"Determine if a wireless intrusion detection system is employed to identify rogue wireless devices;Wireless networks are inherently less secure than wired networks. For example, wireless networks are more susceptible to eavesdroppers or traffic analysis than wireline networks. When wireless to wireline communications exist, the wireless network could become a port of entry into the wired network. Given the greater facility of unauthorized network access via wireless access points compared to unauthorized wired network access from within the physical boundaries of the system, additional monitoring of transitioning traffic between wireless and wired networks may be necessary to detect malicious activities. Employing intrusion detection systems to monitor wireless communications traffic helps to ensure that the traffic does not contain malicious code prior to transitioning to the wireline network.
","uuid":"953ca165-4d67-4a43-b803-6f3b8d59e1c5","family":"System and Information Integrity","parameters":[],"subControls":"","tests":[{"testId":"SI-04(15)","uuid":"6e41fb06-20b1-4058-b577-31f46193acf0","test":"Determine if an intrusion detection system is employed to monitor wireless communications traffic as the traffic passes from wireless to wireline networks.Correlating information from different system monitoring tools and mechanisms can provide a more comprehensive view of system activity. Correlating system monitoring tools and mechanisms that typically work in isolation—including malicious code protection software, host monitoring, and network monitoring—can provide an organization-wide monitoring view and may reveal otherwise unseen attack patterns. Understanding the capabilities and limitations of diverse monitoring tools and mechanisms and how to maximize the use of information generated by those tools and mechanisms can help organizations develop, operate, and maintain effective monitoring programs. The correlation of monitoring information is especially important during the transition from older to newer technologies (e.g., transitioning from IPv4 to IPv6 network protocols).
","uuid":"e39f4c84-1f78-462a-bf11-4943eaa29aa8","family":"System and Information Integrity","parameters":[],"subControls":"","tests":[{"testId":"SI-04(16)","uuid":"f6ad593b-e081-4f90-ac61-0b247a59ea42","test":"Determine if information from monitoring tools and mechanisms employed throughout the system is correlated.Correlating monitoring information from a more diverse set of information sources helps to achieve integrated situational awareness. Integrated situational awareness from a combination of physical, cyber, and supply chain monitoring activities enhances the capability of organizations to more quickly detect sophisticated attacks and investigate the methods and techniques employed to carry out such attacks. In contrast to SI-4(16) , which correlates the various cyber monitoring information, integrated situational awareness is intended to correlate monitoring beyond the cyber domain. Correlation of monitoring information from multiple activities may help reveal attacks on organizations that are operating across multiple attack vectors.
","uuid":"bc928bae-f58e-4417-a496-6b3717e54d27","family":"System and Information Integrity","parameters":[],"subControls":"","tests":[{"testId":"SI-04(17)","uuid":"a18969a8-79c6-4232-8f37-2cee5c8201a5","test":"Determine if information from monitoring physical, cyber, and supply chain activities are correlated to achieve integrated, organization-wide situational awareness.Organization-defined interior points include subnetworks and subsystems. Covert means that can be used to exfiltrate information include steganography.
","uuid":"b66d6e4c-90a0-4e63-8b29-79186389a4af","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"b9c3796e-a1a5-45b6-b484-ae06f3cd55e0","text":"interior points","parameterId":"si-04.18_odp","default":" [Assignment: organization defined interior points] "}],"subControls":"","tests":[{"testId":"SI-04(18)[01]","uuid":"47f95999-be65-4048-9ceb-97bd41d69ad8","test":"Determine if outbound communications traffic is analyzed at interfaces external to the system to detect covert exfiltration of information;Indications of increased risk from individuals can be obtained from different sources, including personnel records, intelligence agencies, law enforcement organizations, and other sources. The monitoring of individuals is coordinated with the management, legal, security, privacy, and human resource officials who conduct such monitoring. Monitoring is conducted in accordance with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines.
","uuid":"91265c2b-5881-4f15-b381-3fa0397b208a","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"87d1cb7d-c62a-4e8b-8745-c596d5cb9e57","text":"additional monitoring","parameterId":"si-04.19_odp.01","default":" [Assignment: organization defined additional monitoring] "},{"constraints":"","displayName":"","guidance":"","uuid":"7e01c1e8-69e1-4890-9e32-967610e84414","text":"sources","parameterId":"si-04.19_odp.02","default":" [Assignment: organization defined sources] "}],"subControls":"","tests":[{"testId":"SI-04(19)","uuid":"62ad706c-1820-4ab1-a783-4bc16541d92d","test":"Determine if [SELECTED PARAMETER VALUE(S): additional monitoring ] is implemented on individuals who have been identified by [SELECTED PARAMETER VALUE(S): sources ] as posing an increased level of risk.Privileged users have access to more sensitive information, including security-related information, than the general user population. Access to such information means that privileged users can potentially do greater damage to systems and organizations than non-privileged users. Therefore, implementing additional monitoring on privileged users helps to ensure that organizations can identify malicious activity at the earliest possible time and take appropriate actions.
","uuid":"ebc1f911-95db-4319-9f1d-a6d29ae24a4c","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"c0605203-c244-4402-a191-f51e0b76d911","text":"additional monitoring","parameterId":"si-04.20_odp","default":" [Assignment: organization defined additional monitoring] "}],"subControls":"","tests":[{"testId":"SI-04(20)","uuid":"792ff668-5fc0-424a-9890-864b42b47f7b","test":"Determine if [SELECTED PARAMETER VALUE(S): additional monitoring ] of privileged users is implemented.During probationary periods, employees do not have permanent employment status within organizations. Without such status or access to information that is resident on the system, additional monitoring can help identify any potentially malicious activity or inappropriate behavior.
","uuid":"f25082be-d1d6-4486-ab66-f27a3140a442","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"c1106945-2cd5-416b-83ae-bcfbac604635","text":"additional monitoring","parameterId":"si-04.21_odp.01","default":" [Assignment: organization defined additional monitoring] "},{"constraints":"","displayName":"","guidance":"","uuid":"065d6ad0-b66c-48f0-8f02-e1eed8b485e6","text":"probationary period","parameterId":"si-04.21_odp.02","default":" [Assignment: organization defined probationary period] "}],"subControls":"","tests":[{"testId":"SI-04(21)","uuid":"9ef54b1d-78ed-4fe8-951c-cf4297acef16","test":"Determine if [SELECTED PARAMETER VALUE(S): additional monitoring ] of individuals is implemented during [SELECTED PARAMETER VALUE(S): probationary period ].Unauthorized or unapproved network services include services in service-oriented architectures that lack organizational verification or validation and may therefore be unreliable or serve as malicious rogues for valid services.
","uuid":"931a6e7b-d555-4751-b21c-c853181a96da","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"c9949908-696a-47c2-ba3e-7524982d325d","text":"authorization or approval processes","parameterId":"si-04.22_odp.01","default":" [Assignment: organization defined authorization or approval processes] "},{"constraints":"","displayName":"","guidance":"","uuid":"cd2e52f0-9323-4cd7-9f78-ebabebfa66df","text":"[Selection (one or more): audit; alert [(NESTED PARAMETER) Assignment for si-04.22_odp.03: personnel or roles]]","parameterId":"si-04.22_odp.02","default":"[Selection (one or more): audit; alert [(NESTED PARAMETER) Assignment for si-04.22_odp.03: personnel or roles]]"},{"constraints":"","displayName":"","guidance":"","uuid":"16bd7fdd-7d09-466b-a0d1-00e2b0b4bd74","text":"personnel or roles","parameterId":"si-04.22_odp.03","default":" [Assignment: organization defined personnel or roles] "}],"subControls":"","tests":[{"testId":"SI-04(22)(a)","uuid":"948999e0-8e41-44fe-8c79-4e1a2588890b","test":"Determine if network services that have not been authorized or approved by [SELECTED PARAMETER VALUE(S): authorization or approval processes ] are detected;Host-based monitoring collects information about the host (or system in which it resides). System components in which host-based monitoring can be implemented include servers, notebook computers, and mobile devices. Organizations may consider employing host-based monitoring mechanisms from multiple product developers or vendors.
","uuid":"adf413d6-e784-4216-8cca-88c826c8fdc7","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"f2a4157b-46a5-479b-80d1-bc909f72e64b","text":"host-based monitoring mechanisms","parameterId":"si-04.23_odp.01","default":" [Assignment: organization defined host-based monitoring mechanisms] "},{"constraints":"","displayName":"","guidance":"","uuid":"caf887ea-2c07-40c8-81f6-723f9096367f","text":"system components","parameterId":"si-04.23_odp.02","default":" [Assignment: organization defined system components] "}],"subControls":"","tests":[{"testId":"SI-04(23)","uuid":"9ea6f01d-8d2d-45ab-99e7-7a6e66a05778","test":"Determine if [SELECTED PARAMETER VALUE(S): host-based monitoring mechanisms ] are implemented on [SELECTED PARAMETER VALUE(S): system components ].Indicators of compromise (IOC) are forensic artifacts from intrusions that are identified on organizational systems at the host or network level. IOCs provide valuable information on systems that have been compromised. IOCs can include the creation of registry key values. IOCs for network traffic include Universal Resource Locator or protocol elements that indicate malicious code command and control servers. The rapid distribution and adoption of IOCs can improve information security by reducing the time that systems and organizations are vulnerable to the same exploit or attack. Threat indicators, signatures, tactics, techniques, procedures, and other indicators of compromise may be available via government and non-government cooperatives, including the Forum of Incident Response and Security Teams, the United States Computer Emergency Readiness Team, the Defense Industrial Base Cybersecurity Information Sharing Program, and the CERT Coordination Center.
","uuid":"68c8efff-71bf-4952-8e6d-f9389d5fea4d","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"1e87c004-fd20-4639-b5cd-9e66b193cf1e","text":"sources","parameterId":"si-04.24_odp.01","default":" [Assignment: organization defined sources] "},{"constraints":"","displayName":"","guidance":"","uuid":"d303b865-e81d-4958-9224-9f28daa27959","text":"personnel or roles","parameterId":"si-04.24_odp.02","default":" [Assignment: organization defined personnel or roles] "}],"subControls":"","tests":[{"testId":"SI-04(24)[01]","uuid":"18a0b1ea-d000-47ea-bf1d-e76846e2bf2f","test":"Determine if indicators of compromise provided by [SELECTED PARAMETER VALUE(S): sources ] are discovered;Encrypted traffic, asymmetric routing architectures, capacity and latency limitations, and transitioning from older to newer technologies (e.g., IPv4 to IPv6 network protocol transition) may result in blind spots for organizations when analyzing network traffic. Collecting, decrypting, pre-processing, and distributing only relevant traffic to monitoring devices can streamline the efficiency and use of devices and optimize traffic analysis.
","uuid":"bf585e2d-e40f-49c8-a343-621472bdab83","family":"System and Information Integrity","parameters":[],"subControls":"","tests":[{"testId":"SI-04(25)[01]","uuid":"ca84f6d1-3a16-4b2a-9fc9-511c33dc35b9","test":"Determine if visibility into network traffic at external system interfaces is provided to optimize the effectiveness of monitoring devices;The Cybersecurity and Infrastructure Security Agency (CISA) generates security alerts and advisories to maintain situational awareness throughout the Federal Government. Security directives are issued by OMB or other designated organizations with the responsibility and authority to issue such directives. Compliance with security directives is essential due to the critical nature of many of these directives and the potential (immediate) adverse effects on organizational operations and assets, individuals, other organizations, and the Nation should the directives not be implemented in a timely manner. External organizations include supply chain partners, external mission or business partners, external service providers, and other peer or supporting organizations.
","uuid":"6fa2390c-2353-4dbc-9ac0-69d9ce914086","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"771032d6-e3ab-44c6-909f-41f05492f5f1","text":"external organizations","parameterId":"si-05_odp.01","default":" [Assignment: organization defined external organizations] "},{"constraints":"","displayName":"","guidance":"","uuid":"c1fc9f93-bef0-4a53-8c55-c05bc9406f6a","text":"[Selection (one or more): [(NESTED PARAMETER) Assignment for si-05_odp.03: personnel or roles]; [(NESTED PARAMETER) Assignment for si-05_odp.04: elements]; [(NESTED PARAMETER) Assignment for si-05_odp.05: external organizations]]","parameterId":"si-05_odp.02","default":"[Selection (one or more): [(NESTED PARAMETER) Assignment for si-05_odp.03: personnel or roles]; [(NESTED PARAMETER) Assignment for si-05_odp.04: elements]; [(NESTED PARAMETER) Assignment for si-05_odp.05: external organizations]]"},{"constraints":"","displayName":"","guidance":"","uuid":"cc447358-5d7a-4012-939f-408b9a57b7d2","text":"personnel or roles","parameterId":"si-05_odp.03","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"77108566-39e7-4b23-ba08-e5424da42bdd","text":"elements","parameterId":"si-05_odp.04","default":" [Assignment: organization defined elements] "},{"constraints":"","displayName":"","guidance":"","uuid":"fbe29533-436a-45fd-a166-234a409c74f9","text":"external organizations","parameterId":"si-05_odp.05","default":" [Assignment: organization defined external organizations] "}],"subControls":"","tests":[{"testId":"SI-05a.","uuid":"74c31259-8bfd-4913-a1d8-2bf125f63d6d","test":"Determine if system security alerts, advisories, and directives are received from [SELECTED PARAMETER VALUE(S): external organizations ] on an ongoing basis;The significant number of changes to organizational systems and environments of operation requires the dissemination of security-related information to a variety of organizational entities that have a direct interest in the success of organizational mission and business functions. Based on information provided by security alerts and advisories, changes may be required at one or more of the three levels related to the management of risk, including the governance level, mission and business process level, and the information system level.
","uuid":"45dafab7-f6f2-48ff-b36a-6cb93d7a8f10","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"b1e616cd-6233-4190-9dac-46209cc5e5bf","text":"automated mechanisms","parameterId":"si-05.01_odp","default":" [Assignment: organization defined automated mechanisms] "}],"subControls":"","tests":[{"testId":"SI-05(01)","uuid":"0cc1d452-ac13-4f35-bbc8-ce93d1607585","test":"Determine if [SELECTED PARAMETER VALUE(S): automated mechanisms ] are used to broadcast security alert and advisory information throughout the organization.Transitional states for systems include system startup, restart, shutdown, and abort. System notifications include hardware indicator lights, electronic alerts to system administrators, and messages to local computer consoles. In contrast to security function verification, privacy function verification ensures that privacy functions operate as expected and are approved by the senior agency official for privacy or that privacy attributes are applied or used as expected.
","uuid":"4a4d5456-209e-4813-8600-4051fb0341e0","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"f93bc14d-d06b-40b5-888e-26846736e730","text":"organization-defined security and privacy functions","parameterId":"si-6_prm_1","default":" [Assignment: organization-defined security and privacy functions] "},{"constraints":"","displayName":"","guidance":"","uuid":"beda90d9-d3f5-402e-b2af-732a19a61260","text":"security functions","parameterId":"si-06_odp.01","default":" [Assignment: organization defined security functions] "},{"constraints":"","displayName":"","guidance":"","uuid":"543371b6-2a92-4b51-bc72-76662d51afcd","text":"privacy functions","parameterId":"si-06_odp.02","default":" [Assignment: organization defined privacy functions] "},{"constraints":"","displayName":"","guidance":"","uuid":"8f42f9bf-9530-41ac-8eb8-f590365b0271","text":"[Selection (one or more): [(NESTED PARAMETER) Assignment for si-06_odp.04: system transitional states]; upon command by user with appropriate privilege; [(NESTED PARAMETER) Assignment for si-06_odp.05: frequency]]","parameterId":"si-06_odp.03","default":"[Selection (one or more): [(NESTED PARAMETER) Assignment for si-06_odp.04: system transitional states]; upon command by user with appropriate privilege; [(NESTED PARAMETER) Assignment for si-06_odp.05: frequency]]"},{"constraints":"","displayName":"","guidance":"","uuid":"49c7d4b0-074d-4f48-9a6b-00326ab861a8","text":"system transitional states","parameterId":"si-06_odp.04","default":" [Assignment: organization defined system transitional states] "},{"constraints":"","displayName":"","guidance":"","uuid":"8fe2d76c-19ef-4f3c-ad3d-256c4a1d2c64","text":"frequency","parameterId":"si-06_odp.05","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"bf7fbb8d-9d29-42dd-9c9c-f6f9d2e96755","text":"personnel or roles","parameterId":"si-06_odp.06","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"ab4fb732-4d08-4ba2-ab88-2a3af407e137","text":"[Selection (one or more): shut the system down; restart the system; [(NESTED PARAMETER) Assignment for si-06_odp.08: alternative action(s)]]","parameterId":"si-06_odp.07","default":"[Selection (one or more): shut the system down; restart the system; [(NESTED PARAMETER) Assignment for si-06_odp.08: alternative action(s)]]"},{"constraints":"","displayName":"","guidance":"","uuid":"f9fd1acc-f3ef-44d0-8269-fb56c024c895","text":"alternative action(s)","parameterId":"si-06_odp.08","default":" [Assignment: organization defined alternative action(s)] "}],"subControls":"","tests":[{"testId":"SI-06a.[01]","uuid":"ebe8333f-10c8-494d-868b-2afad40c7a7a","test":"Determine if [SELECTED PARAMETER VALUE(S): security functions ] are verified to be operating correctly;The use of automated mechanisms to support the management of distributed function testing helps to ensure the integrity, timeliness, completeness, and efficacy of such testing.
","uuid":"70122b9d-aab3-4f5f-8650-be354bcf528c","family":"System and Information Integrity","parameters":[],"subControls":"","tests":[{"testId":"SI-06(02)[01]","uuid":"378a40d2-77b5-42d0-86d4-4ee17f290ae8","test":"Determine if automated mechanisms are implemented to support the management of distributed security function testing;Organizational personnel with potential interest in the results of the verification of security and privacy functions include systems security officers, senior agency information security officers, and senior agency officials for privacy.
","uuid":"bab48c45-e7e9-4dfd-9105-a43253aec470","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"fc10a16f-d523-4fa8-a052-93c3f4e1e035","text":"personnel or roles","parameterId":"si-06.03_odp","default":" [Assignment: organization defined personnel or roles] "}],"subControls":"","tests":[{"testId":"SI-06(03)[01]","uuid":"0a23776e-d298-49a0-8b71-f8f79bd7d4fc","test":"Determine if the results of security function verification are reported to [SELECTED PARAMETER VALUE(S): personnel or roles ];Unauthorized changes to software, firmware, and information can occur due to errors or malicious activity. Software includes operating systems (with key internal components, such as kernels or drivers), middleware, and applications. Firmware interfaces include Unified Extensible Firmware Interface (UEFI) and Basic Input/Output System (BIOS). Information includes personally identifiable information and metadata that contains security and privacy attributes associated with information. Integrity-checking mechanisms—including parity checks, cyclical redundancy checks, cryptographic hashes, and associated tools—can automatically monitor the integrity of systems and hosted applications.
","uuid":"c1a9c45f-af8f-47c6-b559-346b19b3bfd8","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"412408a6-bb0c-4b4c-bf82-66b17f6abc27","text":"organization-defined software, firmware, and information","parameterId":"si-7_prm_1","default":" [Assignment: organization-defined software, firmware, and information] "},{"constraints":"","displayName":"","guidance":"","uuid":"1ff31c12-3a8b-4bbd-a072-3047ca9d9e9b","text":"organization-defined actions","parameterId":"si-7_prm_2","default":" [Assignment: organization-defined actions] "},{"constraints":"","displayName":"","guidance":"","uuid":"7a605bdb-b9e2-4354-9791-0c332f5be78c","text":"software","parameterId":"si-07_odp.01","default":" [Assignment: organization defined software] "},{"constraints":"","displayName":"","guidance":"","uuid":"c07446ee-88e1-4b1b-9b96-a67a1a9a145c","text":"firmware","parameterId":"si-07_odp.02","default":" [Assignment: organization defined firmware] "},{"constraints":"","displayName":"","guidance":"","uuid":"58292c75-9915-47e3-b1b7-7b0ea32eccea","text":"information","parameterId":"si-07_odp.03","default":" [Assignment: organization defined information] "},{"constraints":"","displayName":"","guidance":"","uuid":"41a08632-afba-4af9-8269-a3f59c378aee","text":"actions","parameterId":"si-07_odp.04","default":" [Assignment: organization defined actions] "},{"constraints":"","displayName":"","guidance":"","uuid":"9911ded9-dec1-4065-80b9-1608651c73bf","text":"actions","parameterId":"si-07_odp.05","default":" [Assignment: organization defined actions] "},{"constraints":"","displayName":"","guidance":"","uuid":"2419204c-9cf9-4195-ad42-0f54ce1dffbe","text":"actions","parameterId":"si-07_odp.06","default":" [Assignment: organization defined actions] "}],"subControls":"","tests":[{"testId":"SI-07a.[01]","uuid":"7908673d-c6d1-4dfa-9aa4-c3e340a6e053","test":"Determine if integrity verification tools are employed to detect unauthorized changes to [SELECTED PARAMETER VALUE(S): software ];Security-relevant events include the identification of new threats to which organizational systems are susceptible and the installation of new hardware, software, or firmware. Transitional states include system startup, restart, shutdown, and abort.
","uuid":"d293b76b-5d9d-4c54-ae05-7e5e0ce7d857","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"2fb74d59-5e9e-4855-a79a-b44eccd20e91","text":"organization-defined software, firmware, and information","parameterId":"si-7.1_prm_1","default":" [Assignment: organization-defined software, firmware, and information] "},{"constraints":"","displayName":"","guidance":"","uuid":"0f94fa7c-a1d2-40f2-8aec-4a2b7f7fa02f","text":"[Selection (one or more): at startup; at [(NESTED PARAMETER) Assignment for si-7.1_prm_3: organization-defined transitional states or security-relevant events]; [(NESTED PARAMETER) Assignment for si-7.1_prm_4: organization-defined frequency]]","parameterId":"si-7.1_prm_2","default":" [Assignment: [Selection (one or more): at startup; at [(NESTED PARAMETER) Assignment for si-7.1_prm_3: organization-defined transitional states or security-relevant events]; [(NESTED PARAMETER) Assignment for si-7.1_prm_4: organization-defined frequency]]] "},{"constraints":"","displayName":"","guidance":"","uuid":"6f3780da-307c-48d2-81b0-1881f8bab103","text":"organization-defined transitional states or security-relevant events","parameterId":"si-7.1_prm_3","default":" [Assignment: organization-defined transitional states or security-relevant events] "},{"constraints":"","displayName":"","guidance":"","uuid":"01235ac6-7090-4050-980d-8917f4ac97f5","text":"organization-defined frequency","parameterId":"si-7.1_prm_4","default":" [Assignment: organization-defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"8088b7e5-714c-4cb1-8263-4c927bbdc904","text":"software","parameterId":"si-07.01_odp.01","default":" [Assignment: organization defined software] "},{"constraints":"","displayName":"","guidance":"","uuid":"79d9dcf2-4d80-4173-9e8c-d8debbd92599","text":"[Selection (one or more): at startup; at [(NESTED PARAMETER) Assignment for si-07.01_odp.03: transitional states or security-relevant events]; [(NESTED PARAMETER) Assignment for si-07.01_odp.04: frequency]]","parameterId":"si-07.01_odp.02","default":"[Selection (one or more): at startup; at [(NESTED PARAMETER) Assignment for si-07.01_odp.03: transitional states or security-relevant events]; [(NESTED PARAMETER) Assignment for si-07.01_odp.04: frequency]]"},{"constraints":"","displayName":"","guidance":"","uuid":"b9d21c71-6214-4fa6-b3ec-8305b2cf0ffa","text":"transitional states or security-relevant events","parameterId":"si-07.01_odp.03","default":" [Assignment: organization defined transitional states or security-relevant events] "},{"constraints":"","displayName":"","guidance":"","uuid":"feb7f239-7f8c-45bb-9622-2d423cabf62c","text":"frequency","parameterId":"si-07.01_odp.04","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"8c3c42ee-cb45-430c-999c-7c434ea09b8f","text":"firmware","parameterId":"si-07.01_odp.05","default":" [Assignment: organization defined firmware] "},{"constraints":"","displayName":"","guidance":"","uuid":"23ef7f9b-3f06-43e9-8199-b1098ff2f5f0","text":"[Selection (one or more): at startup; at [(NESTED PARAMETER) Assignment for si-07.01_odp.07: transitional states or security-relevant events]; [(NESTED PARAMETER) Assignment for si-07.01_odp.08: frequency]]","parameterId":"si-07.01_odp.06","default":"[Selection (one or more): at startup; at [(NESTED PARAMETER) Assignment for si-07.01_odp.07: transitional states or security-relevant events]; [(NESTED PARAMETER) Assignment for si-07.01_odp.08: frequency]]"},{"constraints":"","displayName":"","guidance":"","uuid":"b65a414d-f9fb-43b6-9675-6f00b3006a94","text":"transitional states or security-relevant events","parameterId":"si-07.01_odp.07","default":" [Assignment: organization defined transitional states or security-relevant events] "},{"constraints":"","displayName":"","guidance":"","uuid":"643adeb3-147e-43fb-a59c-c040ec5df2a2","text":"frequency","parameterId":"si-07.01_odp.08","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"e420e203-f39f-411d-8f73-ef954a5c22bd","text":"information","parameterId":"si-07.01_odp.09","default":" [Assignment: organization defined information] "},{"constraints":"","displayName":"","guidance":"","uuid":"f639b5d8-bd73-4f4f-80db-680cffd7d9bd","text":"[Selection (one or more): at startup; at [(NESTED PARAMETER) Assignment for si-07.01_odp.11: transitional states or security-relevant events]; [(NESTED PARAMETER) Assignment for si-07.01_odp.12: frequency]]","parameterId":"si-07.01_odp.10","default":"[Selection (one or more): at startup; at [(NESTED PARAMETER) Assignment for si-07.01_odp.11: transitional states or security-relevant events]; [(NESTED PARAMETER) Assignment for si-07.01_odp.12: frequency]]"},{"constraints":"","displayName":"","guidance":"","uuid":"37509946-ca0e-4d4c-b06b-105f3a1c77c4","text":"transitional states or security-relevant events","parameterId":"si-07.01_odp.11","default":" [Assignment: organization defined transitional states or security-relevant events] "},{"constraints":"","displayName":"","guidance":"","uuid":"8dfc0a6c-15ee-45dc-9ac7-4df9cabef118","text":"frequency","parameterId":"si-07.01_odp.12","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"SI-07(01)[01]","uuid":"1dc720c9-7760-470a-b780-5f8b6aebee04","test":"Determine if an integrity check of [SELECTED PARAMETER VALUE(S): software ] is performed [SELECTED PARAMETER VALUE(S): [Selection (one or more): at startup; at [(NESTED PARAMETER) Assignment for si-07.01_odp.03: transitional states or security-relevant events]; [(NESTED PARAMETER) Assignment for si-07.01_odp.04: frequency]] ];The employment of automated tools to report system and information integrity violations and to notify organizational personnel in a timely matter is essential to effective risk response. Personnel with an interest in system and information integrity violations include mission and business owners, system owners, senior agency information security official, senior agency official for privacy, system administrators, software developers, systems integrators, information security officers, and privacy officers.
","uuid":"6e3fab24-d835-492e-8ecf-69b1ebc6e177","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"8747842a-89cf-4998-b3ef-225f8555a8c9","text":"personnel or roles","parameterId":"si-07.02_odp","default":" [Assignment: organization defined personnel or roles] "}],"subControls":"","tests":[{"testId":"SI-07(02)","uuid":"9267a04e-78f3-4292-95fb-2fcd5b8dd6ae","test":"Determine if automated tools that provide notification to [SELECTED PARAMETER VALUE(S): personnel or roles ] upon discovering discrepancies during integrity verification are employed.Centrally managed integrity verification tools provides greater consistency in the application of such tools and can facilitate more comprehensive coverage of integrity verification actions.
","uuid":"1ccda20c-765d-496c-ba52-319037646a11","family":"System and Information Integrity","parameters":[],"subControls":"","tests":[{"testId":"SI-07(03)","uuid":"8865add6-cf33-44e3-802e-ea78753767f5","test":"Determine if centrally managed integrity verification tools are employed.Organizations may define different integrity-checking responses by type of information, specific information, or a combination of both. Types of information include firmware, software, and user data. Specific information includes boot firmware for certain types of machines. The automatic implementation of controls within organizational systems includes reversing the changes, halting the system, or triggering audit alerts when unauthorized modifications to critical security files occur.
","uuid":"a88a02c9-59f3-47c2-bf8f-681e8cc8c704","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"760178b0-da84-4f2e-bb51-63888a6d2ed2","text":"[Selection (one or more): shut down the system; restart the system; implement [(NESTED PARAMETER) Assignment for si-07.05_odp.02: controls]]","parameterId":"si-07.05_odp.01","default":"[Selection (one or more): shut down the system; restart the system; implement [(NESTED PARAMETER) Assignment for si-07.05_odp.02: controls]]"},{"constraints":"","displayName":"","guidance":"","uuid":"ebf53f61-3ae2-40e0-9a54-948835bb4bd0","text":"controls","parameterId":"si-07.05_odp.02","default":" [Assignment: organization defined controls] "}],"subControls":"","tests":[{"testId":"SI-07(05)","uuid":"904bcc50-9055-4719-bd16-7a85b19ac7f7","test":"Determine if [SELECTED PARAMETER VALUE(S): [Selection (one or more): shut down the system; restart the system; implement [(NESTED PARAMETER) Assignment for si-07.05_odp.02: controls]] ] are automatically performed when integrity violations are discovered.Cryptographic mechanisms used to protect integrity include digital signatures and the computation and application of signed hashes using asymmetric cryptography, protecting the confidentiality of the key used to generate the hash, and using the public key to verify the hash information. Organizations that employ cryptographic mechanisms also consider cryptographic key management solutions.
","uuid":"8947bde8-baca-4437-a90a-1ca8712b69a9","family":"System and Information Integrity","parameters":[],"subControls":"","tests":[{"testId":"SI-07(06)[01]","uuid":"37134256-9137-4df1-b5ae-45ffcd650bc9","test":"Determine if cryptographic mechanisms are implemented to detect unauthorized changes to software;Integrating detection and response helps to ensure that detected events are tracked, monitored, corrected, and available for historical purposes. Maintaining historical records is important for being able to identify and discern adversary actions over an extended time period and for possible legal actions. Security-relevant changes include unauthorized changes to established configuration settings or the unauthorized elevation of system privileges.
","uuid":"4a3366ce-3094-41ee-898d-b925a5de7252","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"10b0472e-8534-4626-9636-39edff70e01f","text":"changes","parameterId":"si-07.07_odp","default":" [Assignment: organization defined changes] "}],"subControls":"","tests":[{"testId":"SI-07(07)","uuid":"6a61416f-bf62-4944-8e79-16d73e2a15c8","test":"Determine if the detection of [SELECTED PARAMETER VALUE(S): changes ] are incorporated into the organizational incident response capability.Organizations select response actions based on types of software, specific software, or information for which there are potential integrity violations.
","uuid":"afb34dd7-d208-4d95-b317-9c5138bedc11","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"e628d166-d55e-4043-b9a2-4acc4ea684df","text":"[Selection (one or more): generate an audit record; alert current user; alert [(NESTED PARAMETER) Assignment for si-07.08_odp.02: personnel or roles]; [(NESTED PARAMETER) Assignment for si-07.08_odp.03: other actions]]","parameterId":"si-07.08_odp.01","default":"[Selection (one or more): generate an audit record; alert current user; alert [(NESTED PARAMETER) Assignment for si-07.08_odp.02: personnel or roles]; [(NESTED PARAMETER) Assignment for si-07.08_odp.03: other actions]]"},{"constraints":"","displayName":"","guidance":"","uuid":"aa30e2a0-a7ff-4c6b-8e81-cb1ac17c2421","text":"personnel or roles","parameterId":"si-07.08_odp.02","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"d9833fc1-4833-4de4-880d-4bd706a40e41","text":"other actions","parameterId":"si-07.08_odp.03","default":" [Assignment: organization defined other actions] "}],"subControls":"","tests":[{"testId":"SI-07(08)[01]","uuid":"7bd9563a-d199-4615-9856-8ce7a82107fb","test":"Determine if the capability to audit an event upon the detection of a potential integrity violation is provided;Ensuring the integrity of boot processes is critical to starting system components in known, trustworthy states. Integrity verification mechanisms provide a level of assurance that only trusted code is executed during boot processes.
","uuid":"14dee71f-476b-4203-99f9-bcfb70ab7363","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"006f0fac-6eb9-426f-af68-c4d686951c62","text":"system components","parameterId":"si-07.09_odp","default":" [Assignment: organization defined system components] "}],"subControls":"","tests":[{"testId":"SI-07(09)","uuid":"bacaf872-ec2b-4900-855c-bddbca05efce","test":"Determine if the integrity of the boot process of [SELECTED PARAMETER VALUE(S): system components ] is verified.Unauthorized modifications to boot firmware may indicate a sophisticated, targeted attack. These types of targeted attacks can result in a permanent denial of service or a persistent malicious code presence. These situations can occur if the firmware is corrupted or if the malicious code is embedded within the firmware. System components can protect the integrity of boot firmware in organizational systems by verifying the integrity and authenticity of all updates to the firmware prior to applying changes to the system component and preventing unauthorized processes from modifying the boot firmware.
","uuid":"4d7c4a5f-d08e-4193-9fcc-8d9931f70a81","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"0bfd514c-89aa-4a8b-8354-bb78a04cc26d","text":"mechanisms","parameterId":"si-07.10_odp.01","default":" [Assignment: organization defined mechanisms] "},{"constraints":"","displayName":"","guidance":"","uuid":"2b44f355-43fc-4751-a9e5-b299de424dc7","text":"system components","parameterId":"si-07.10_odp.02","default":" [Assignment: organization defined system components] "}],"subControls":"","tests":[{"testId":"SI-07(10)","uuid":"fd139333-35b8-4a42-953e-fb831d2573c2","test":"Determine if [SELECTED PARAMETER VALUE(S): mechanisms ] are implemented to protect the integrity of boot firmware in [SELECTED PARAMETER VALUE(S): system components ].Organizations verify the integrity of user-installed software prior to execution to reduce the likelihood of executing malicious code or programs that contains errors from unauthorized modifications. Organizations consider the practicality of approaches to verifying software integrity, including the availability of trustworthy checksums from software developers and vendors.
","uuid":"c65853e6-62e0-45bb-8d50-a504a2b6ab77","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"bcef5eb0-653e-4dc6-bac3-ac54a23637d0","text":"user-installed software","parameterId":"si-07.12_odp","default":" [Assignment: organization defined user-installed software] "}],"subControls":"","tests":[{"testId":"SI-07(12)","uuid":"ae327422-fb70-46cc-abd8-f92b5b0177f0","test":"Determine if the integrity of [SELECTED PARAMETER VALUE(S): user-installed software ] is verified prior to execution.Cryptographic authentication includes verifying that software or firmware components have been digitally signed using certificates recognized and approved by organizations. Code signing is an effective method to protect against malicious code. Organizations that employ cryptographic mechanisms also consider cryptographic key management solutions.
","uuid":"f3a5ff44-e5ae-4f5f-b188-0a1c2c00f9a8","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"74567646-6bb6-4c14-a034-fcff9a1648e4","text":"software or firmware components","parameterId":"si-07.15_odp","default":" [Assignment: organization defined software or firmware components] "}],"subControls":"","tests":[{"testId":"SI-07(15)","uuid":"062375b4-e373-4bc0-913c-6a2c7269d510","test":"Determine if cryptographic mechanisms are implemented to authenticate [SELECTED PARAMETER VALUE(S): software or firmware components ] prior to installation.Placing a time limit on process execution without supervision is intended to apply to processes for which typical or normal execution periods can be determined and situations in which organizations exceed such periods. Supervision includes timers on operating systems, automated responses, and manual oversight and response when system process anomalies occur.
","uuid":"c538149b-4431-48b5-9431-32cd1ce53f44","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"bb2d1b0d-43b6-40f8-98e0-e51aeb471f38","text":"time period","parameterId":"si-07.16_odp","default":" [Assignment: organization defined time period] "}],"subControls":"","tests":[{"testId":"SI-07(16)","uuid":"16721da0-c586-4be8-8d53-18023fae90df","test":"Determine if processes are prohibited from executing without supervision for more than [SELECTED PARAMETER VALUE(S): time period ].Runtime application self-protection employs runtime instrumentation to detect and block the exploitation of software vulnerabilities by taking advantage of information from the software in execution. Runtime exploit prevention differs from traditional perimeter-based protections such as guards and firewalls which can only detect and block attacks by using network information without contextual awareness. Runtime application self-protection technology can reduce the susceptibility of software to attacks by monitoring its inputs and blocking those inputs that could allow attacks. It can also help protect the runtime environment from unwanted changes and tampering. When a threat is detected, runtime application self-protection technology can prevent exploitation and take other actions (e.g., sending a warning message to the user, terminating the user's session, terminating the application, or sending an alert to organizational personnel). Runtime application self-protection solutions can be deployed in either a monitor or protection mode.
","uuid":"573ccef4-cd09-49dd-a92a-e1aeb99f4996","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"5c3e7f57-951d-4a7d-8ea1-c56b344ad09e","text":"controls","parameterId":"si-07.17_odp","default":" [Assignment: organization defined controls] "}],"subControls":"","tests":[{"testId":"SI-07(17)","uuid":"4e35320e-e2a0-42cb-a54b-f6febe2e685f","test":"Determine if [SELECTED PARAMETER VALUE(S): controls ] are implemented for application self-protection at runtime.System entry and exit points include firewalls, remote-access servers, electronic mail servers, web servers, proxy servers, workstations, notebook computers, and mobile devices. Spam can be transported by different means, including email, email attachments, and web accesses. Spam protection mechanisms include signature definitions.
","uuid":"2f4eefde-a3e8-4c20-8006-8238d0440ae0","family":"System and Information Integrity","parameters":[],"subControls":"","tests":[{"testId":"SI-08a.[01]","uuid":"3d52f29c-039f-44b9-800a-81ebac1407ba","test":"Determine if spam protection mechanisms are employed at system entry points to detect unsolicited messages;Using automated mechanisms to update spam protection mechanisms helps to ensure that updates occur on a regular basis and provide the latest content and protection capabilities.
","uuid":"1d4f5ff1-c448-4daa-a01b-9cfc351bc95a","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"186a41c8-e63e-4649-a8ce-1b5bedb93e37","text":"frequency","parameterId":"si-08.02_odp","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"SI-08(02)","uuid":"a6e952bf-9319-4817-97a7-c78a2d4dbfd7","test":"Determine if spam protection mechanisms are automatically updated [SELECTED PARAMETER VALUE(S): frequency ].Learning mechanisms include Bayesian filters that respond to user inputs that identify specific traffic as spam or legitimate by updating algorithm parameters and thereby more accurately separating types of traffic.
","uuid":"81a68acf-56e7-4a1c-bdab-b43dd135dcb6","family":"System and Information Integrity","parameters":[],"subControls":"","tests":[{"testId":"SI-08(03)","uuid":"1c0a35cb-023c-4e19-8c49-aa40e0a643a6","test":"Determine if spam protection mechanisms with a learning capability are implemented to more effectively identify legitimate communications traffic.Checking the valid syntax and semantics of system inputs—including character set, length, numerical range, and acceptable values—verifies that inputs match specified definitions for format and content. For example, if the organization specifies that numerical values between 1-100 are the only acceptable inputs for a field in a given application, inputs of 387,
\nabc,
or %K%
are invalid inputs and are not accepted as input to the system. Valid inputs are likely to vary from field to field within a software application. Applications typically follow well-defined protocols that use structured messages (i.e., commands or queries) to communicate between software modules or system components. Structured messages can contain raw or unstructured data interspersed with metadata or control information. If software applications use attacker-supplied inputs to construct structured messages without properly encoding such messages, then the attacker could insert malicious commands or special characters that can cause the data to be interpreted as control information or metadata. Consequently, the module or component that receives the corrupted output will perform the wrong operations or otherwise interpret the data incorrectly. Prescreening inputs prior to passing them to interpreters prevents the content from being unintentionally interpreted as commands. Input validation ensures accurate and correct inputs and prevents attacks such as cross-site scripting and a variety of injection attacks.
In certain situations, such as during events that are defined in contingency plans, a manual override capability for input validation may be needed. Manual overrides are used only in limited circumstances and with the inputs defined by the organization.
","uuid":"8e5d38a4-8b6d-472f-b283-97496be548c9","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"63a75051-c7e4-4456-af55-4d12cfa4fe40","text":"authorized individuals","parameterId":"si-10.01_odp","default":" [Assignment: organization defined authorized individuals] "}],"subControls":"","tests":[{"testId":"SI-10(01)(a)","uuid":"e2682d74-8e48-4f98-9267-cbc003dbcf03","test":"Determine if a manual override capability for the validation of [SELECTED PARAMETER VALUE(S): information inputs ] is provided;Resolution of input validation errors includes correcting systemic causes of errors and resubmitting transactions with corrected input. Input validation errors are those related to the information inputs defined by the organization in the base control ( SI-10).
","uuid":"c55cd499-f7d9-4669-9825-1ebd76fb0073","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"02c8f0d1-ce3d-4510-a65e-1d6e1de66565","text":"organization-defined time period","parameterId":"si-10.2_prm_1","default":" [Assignment: organization-defined time period] "},{"constraints":"","displayName":"","guidance":"","uuid":"57d19c6e-e918-4135-9855-05b526ea3bb0","text":"time period","parameterId":"si-10.02_odp.01","default":" [Assignment: organization defined time period] "},{"constraints":"","displayName":"","guidance":"","uuid":"8bcf3366-d2a1-40da-9233-bfb038b4cb49","text":"time period","parameterId":"si-10.02_odp.02","default":" [Assignment: organization defined time period] "}],"subControls":"","tests":[{"testId":"SI-10(02)[01]","uuid":"e28c50a5-712b-490f-9438-08d20cc8cda5","test":"Determine if input validation errors are reviewed within [SELECTED PARAMETER VALUE(S): time period ];A common vulnerability in organizational systems is unpredictable behavior when invalid inputs are received. Verification of system predictability helps ensure that the system behaves as expected when invalid inputs are received. This occurs by specifying system responses that allow the system to transition to known states without adverse, unintended side effects. The invalid inputs are those related to the information inputs defined by the organization in the base control ( SI-10).
","uuid":"e9ebce86-5535-47c6-91e2-eff7a3f41be1","family":"System and Information Integrity","parameters":[],"subControls":"","tests":[{"testId":"SI-10(03)[01]","uuid":"71fab462-b7f7-44b5-b9c8-f1a23b83d74b","test":"Determine if the system behaves in a predictable manner when invalid inputs are received;In addressing invalid system inputs received across protocol interfaces, timing interactions become relevant, where one protocol needs to consider the impact of the error response on other protocols in the protocol stack. For example, 802.11 standard wireless network protocols do not interact well with Transmission Control Protocols (TCP) when packets are dropped (which could be due to invalid packet input). TCP assumes packet losses are due to congestion, while packets lost over 802.11 links are typically dropped due to noise or collisions on the link. If TCP makes a congestion response, it takes the wrong action in response to a collision event. Adversaries may be able to use what appear to be acceptable individual behaviors of the protocols in concert to achieve adverse effects through suitable construction of invalid input. The invalid inputs are those related to the information inputs defined by the organization in the base control ( SI-10).
","uuid":"6d635709-972b-43f2-bf1c-fb58aed7d1d6","family":"System and Information Integrity","parameters":[],"subControls":"","tests":[{"testId":"SI-10(04)","uuid":"18f7d272-d4bc-4f8a-994b-5922f7bc102f","test":"Determine if timing interactions among system components are accounted for in determining appropriate responses for invalid inputs.Restricting the use of inputs to trusted sources and in trusted formats applies the concept of authorized or permitted software to information inputs. Specifying known trusted sources for information inputs and acceptable formats for such inputs can reduce the probability of malicious activity. The information inputs are those defined by the organization in the base control ( SI-10).
","uuid":"6aa33008-c6d2-41fd-8803-1c914769b83a","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"b3c2ddbf-1683-401f-b5a9-1370f2e30db9","text":"trusted sources","parameterId":"si-10.05_odp.01","default":" [Assignment: organization defined trusted sources] "},{"constraints":"","displayName":"","guidance":"","uuid":"845af5cc-f49b-458c-a17d-e08a5b8f9556","text":"formats","parameterId":"si-10.05_odp.02","default":" [Assignment: organization defined formats] "}],"subControls":"","tests":[{"testId":"SI-10(05)","uuid":"5e46e4f2-1066-4812-8a89-8739e033d88f","test":"Determine if the use of information inputs is restricted to [SELECTED PARAMETER VALUE(S): trusted sources ] and/or [SELECTED PARAMETER VALUE(S): formats ].Untrusted data injections may be prevented using a parameterized interface or output escaping (output encoding). Parameterized interfaces separate data from code so that injections of malicious or unintended data cannot change the semantics of commands being sent. Output escaping uses specified characters to inform the interpreter’s parser whether data is trusted. Prevention of untrusted data injections are with respect to the information inputs defined by the organization in the base control ( SI-10).
","uuid":"dadf7265-c393-4756-9e31-5728c4a59947","family":"System and Information Integrity","parameters":[],"subControls":"","tests":[{"testId":"SI-10(06)","uuid":"0865e603-ba25-4afb-8443-684b44305c4a","test":"Determine if untrusted data injections are prevented.Organizations consider the structure and content of error messages. The extent to which systems can handle error conditions is guided and informed by organizational policy and operational requirements. Exploitable information includes stack traces and implementation details; erroneous logon attempts with passwords mistakenly entered as the username; mission or business information that can be derived from, if not stated explicitly by, the information recorded; and personally identifiable information, such as account numbers, social security numbers, and credit card numbers. Error messages may also provide a covert channel for transmitting information.
","uuid":"f03c8661-e3b9-46f8-b53d-67c941d767f1","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"c9ba0225-fcbc-4f41-b415-2adb4154e32f","text":"personnel or roles","parameterId":"si-11_odp","default":" [Assignment: organization defined personnel or roles] "}],"subControls":"","tests":[{"testId":"SI-11a.","uuid":"b0c4ca28-b5e0-49f0-9c61-bcbdce1d6f14","test":"Determine if error messages that provide the information necessary for corrective actions are generated without revealing information that could be exploited;Information management and retention requirements cover the full life cycle of information, in some cases extending beyond system disposal. Information to be retained may also include policies, procedures, plans, reports, data output from control implementation, and other types of administrative information. The National Archives and Records Administration (NARA) provides federal policy and guidance on records retention and schedules. If organizations have a records management office, consider coordinating with records management personnel. Records produced from the output of implemented controls that may require management and retention include, but are not limited to: All XX-1, AC-6(9), AT-4, AU-12, CA-2, CA-3, CA-5, CA-6, CA-7, CA-8, CA-9, CM-2, CM-3, CM-4, CM-6, CM-8, CM-9, CM-12, CM-13, CP-2, IR-6, IR-8, MA-2, MA-4, PE-2, PE-8, PE-16, PE-17, PL-2, PL-4, PL-7, PL-8, PM-5, PM-8, PM-9, PM-18, PM-21, PM-27, PM-28, PM-30, PM-31, PS-2, PS-6, PS-7, PT-2, PT-3, PT-7, RA-2, RA-3, RA-5, RA-8, SA-4, SA-5, SA-8, SA-10, SI-4, SR-2, SR-4, SR-8.
","uuid":"d8d3351b-0b34-42a0-9d4a-a1cabe310a75","family":"System and Information Integrity","parameters":[],"subControls":"","tests":[{"testId":"SI-12[01]","uuid":"b0c26629-5365-4ce0-924c-a8d5f6ab2543","test":"Determine if information within the system is managed in accordance with applicable laws, executive orders, directives, regulations, policies, standards, guidelines, and operational requirements;Limiting the use of personally identifiable information throughout the information life cycle when the information is not needed for operational purposes helps to reduce the level of privacy risk created by a system. The information life cycle includes information creation, collection, use, processing, storage, maintenance, dissemination, disclosure, and disposition. Risk assessments as well as applicable laws, regulations, and policies can provide useful inputs to determining which elements of personally identifiable information may create risk.
","uuid":"989dd1b3-cff7-4d09-9158-e1336a3427de","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"bfe86513-64a7-4da8-a29e-ecbe164f7179","text":"elements of personally identifiable information","parameterId":"si-12.01_odp","default":" [Assignment: organization defined elements of personally identifiable information] "}],"subControls":"","tests":[{"testId":"SI-12(01)","uuid":"3ba6c04c-843d-41a8-95dd-aabdf6014710","test":"Determine if personally identifiable information being processed in the information life cycle is limited to [SELECTED PARAMETER VALUE(S): elements of personally identifiable information ].Organizations can minimize the risk to an individual’s privacy by employing techniques such as de-identification or synthetic data. Limiting the use of personally identifiable information throughout the information life cycle when the information is not needed for research, testing, or training helps reduce the level of privacy risk created by a system. Risk assessments as well as applicable laws, regulations, and policies can provide useful inputs to determining the techniques to use and when to use them.
","uuid":"4636dc5d-3794-483e-908c-7068bfb88da8","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"480e0b3d-edfb-4435-aed8-9cc538b9d071","text":"organization-defined techniques","parameterId":"si-12.2_prm_1","default":" [Assignment: organization-defined techniques] "},{"constraints":"","displayName":"","guidance":"","uuid":"e1c80e23-8a66-4432-a1f6-9ff0faa25e01","text":"techniques","parameterId":"si-12.02_odp.01","default":" [Assignment: organization defined techniques] "},{"constraints":"","displayName":"","guidance":"","uuid":"cab334fe-3592-4603-9e3d-82ec81c2e2d4","text":"techniques","parameterId":"si-12.02_odp.02","default":" [Assignment: organization defined techniques] "},{"constraints":"","displayName":"","guidance":"","uuid":"5c0350b7-7be4-44ac-a7a7-aa9b341428c3","text":"techniques","parameterId":"si-12.02_odp.03","default":" [Assignment: organization defined techniques] "}],"subControls":"","tests":[{"testId":"SI-12(02)[01]","uuid":"2a240ec5-0bf9-4d82-9eca-77c444c1441c","test":"Determine if [SELECTED PARAMETER VALUE(S): techniques ] are used to minimize the use of personally identifiable information for research;Organizations can minimize both security and privacy risks by disposing of information when it is no longer needed. The disposal or destruction of information applies to originals as well as copies and archived records, including system logs that may contain personally identifiable information.
","uuid":"6e23e89b-93da-4dcd-ad58-73f4865d34fb","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"d79521b1-849e-42c8-8ef0-b441d84b304d","text":"organization-defined techniques","parameterId":"si-12.3_prm_1","default":" [Assignment: organization-defined techniques] "},{"constraints":"","displayName":"","guidance":"","uuid":"d7eee9e8-543d-4135-8da3-bf87a135af6c","text":"techniques","parameterId":"si-12.03_odp.01","default":" [Assignment: organization defined techniques] "},{"constraints":"","displayName":"","guidance":"","uuid":"d2509502-c3f8-49c9-8c38-f95fc538b927","text":"techniques","parameterId":"si-12.03_odp.02","default":" [Assignment: organization defined techniques] "},{"constraints":"","displayName":"","guidance":"","uuid":"4ebdb148-1819-4e0c-8353-cc245e0ef6d8","text":"techniques","parameterId":"si-12.03_odp.03","default":" [Assignment: organization defined techniques] "}],"subControls":"","tests":[{"testId":"SI-12(03)[01]","uuid":"ca9e90c8-6cba-44a3-afb6-cf7175ebd62e","test":"Determine if [SELECTED PARAMETER VALUE(S): techniques ] are used to dispose of information following the retention period;While MTTF is primarily a reliability issue, predictable failure prevention is intended to address potential failures of system components that provide security capabilities. Failure rates reflect installation-specific consideration rather than the industry-average. Organizations define the criteria for the substitution of system components based on the MTTF value with consideration for the potential harm from component failures. The transfer of responsibilities between active and standby components does not compromise safety, operational readiness, or security capabilities. The preservation of system state variables is also critical to help ensure a successful transfer process. Standby components remain available at all times except for maintenance issues or recovery failures in progress.
","uuid":"cca5e328-96ce-4842-a06c-225656331571","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"813552f3-683e-4718-81c1-064047a241e2","text":"system components","parameterId":"si-13_odp.01","default":" [Assignment: organization defined system components] "},{"constraints":"","displayName":"","guidance":"","uuid":"7cfa4b05-aad7-4b58-827c-7b20e199b53a","text":"mean time to failure (MTTF) substitution criteria","parameterId":"si-13_odp.02","default":" [Assignment: organization defined mean time to failure (MTTF) substitution criteria] "}],"subControls":"","tests":[{"testId":"SI-13a.","uuid":"b1f37e98-24ed-4f8c-b7e4-f9ed6335fc2e","test":"Determine if mean time to failure (mttf) is determined for [SELECTED PARAMETER VALUE(S): system components ] in specific environments of operation;Transferring primary system component responsibilities to other substitute components prior to primary component failure is important to reduce the risk of degraded or debilitated mission or business functions. Making such transfers based on a percentage of mean time to failure allows organizations to be proactive based on their risk tolerance. However, the premature replacement of system components can result in the increased cost of system operations.
","uuid":"9153dce7-f5b0-41dc-bf56-ba05ce586e4e","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"ce9133a3-231a-4cce-aeb3-b76ad367cec7","text":"fraction or percentage","parameterId":"si-13.01_odp","default":" [Assignment: organization defined fraction or percentage] "}],"subControls":"","tests":[{"testId":"SI-13(01)","uuid":"15163a1b-80e6-4df6-a878-d78e2b3f8ab9","test":"Determine if system components are taken out of service by transferring component responsibilities to substitute components no later than [SELECTED PARAMETER VALUE(S): fraction or percentage ] of mean time to failure.For example, if the MTTF for a system component is 100 days and the MTTF percentage defined by the organization is 90 percent, the manual transfer would occur after 90 days.
","uuid":"d8567d94-394a-4019-85e8-e04702a61a17","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"556ac41d-4196-41a1-a798-6e1f5005dfed","text":"percentage","parameterId":"si-13.03_odp","default":" [Assignment: organization defined percentage] "}],"subControls":"","tests":[{"testId":"SI-13(03)","uuid":"d0ffcfe9-234a-41fb-97b9-7e4ea4f95904","test":"Determine if transfers are initiated manually between active and standby system components when the use of the active component reaches [SELECTED PARAMETER VALUE(S): percentage ] of the mean time to failure.Automatic or manual transfer of components from standby to active mode can occur upon the detection of component failures.
","uuid":"9b18066d-bdf6-4f63-8557-1b25086dfc14","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"17d3de9c-0577-43e9-8314-ee84511edf89","text":"time period","parameterId":"si-13.04_odp.01","default":" [Assignment: organization defined time period] "},{"constraints":"","displayName":"","guidance":"","uuid":"68cc06d5-7df6-476d-9869-afc8cf72dc4d","text":"[Selection (one or more): activate [(NESTED PARAMETER) Assignment for si-13.04_odp.03: alarm]; automatically shut down the system; [(NESTED PARAMETER) Assignment for si-13.04_odp.04: action]]","parameterId":"si-13.04_odp.02","default":"[Selection (one or more): activate [(NESTED PARAMETER) Assignment for si-13.04_odp.03: alarm]; automatically shut down the system; [(NESTED PARAMETER) Assignment for si-13.04_odp.04: action]]"},{"constraints":"","displayName":"","guidance":"","uuid":"60d69912-625d-4f77-88e3-f82510517ae2","text":"alarm","parameterId":"si-13.04_odp.03","default":" [Assignment: organization defined alarm] "},{"constraints":"","displayName":"","guidance":"","uuid":"a6dbbc7c-08c7-4b69-95ca-f88b57bca274","text":"action","parameterId":"si-13.04_odp.04","default":" [Assignment: organization defined action] "}],"subControls":"","tests":[{"testId":"SI-13(04)(a)","uuid":"710affd3-fa92-4175-a5af-cb4f900c30ea","test":"Determine if the standby components are successfully and transparently installed within [SELECTED PARAMETER VALUE(S): time period ] if system component failures are detected;Failover refers to the automatic switchover to an alternate system upon the failure of the primary system. Failover capability includes incorporating mirrored system operations at alternate processing sites or periodic data mirroring at regular intervals defined by the recovery time periods of organizations.
","uuid":"1285d341-4677-4d35-9f8f-bb39a264e49f","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"c761798a-a43b-489e-b2b2-68c46c04b21d","text":"[Selection: real-time; near real-time]","parameterId":"si-13.05_odp.01","default":"[Selection: real-time; near real-time]"},{"constraints":"","displayName":"","guidance":"","uuid":"628baecc-fc8c-4495-a688-f614c90a4cd7","text":"failover capability","parameterId":"si-13.05_odp.02","default":" [Assignment: organization defined failover capability] "}],"subControls":"","tests":[{"testId":"SI-13(05)","uuid":"78925001-a3a7-4ed9-aea5-69bec350f778","test":"Determine if [SELECTED PARAMETER VALUE(S): [Selection: real-time; near real-time] ], [SELECTED PARAMETER VALUE(S): failover capability ] is provided for the system.Implementation of non-persistent components and services mitigates risk from advanced persistent threats (APTs) by reducing the targeting capability of adversaries (i.e., window of opportunity and available attack surface) to initiate and complete attacks. By implementing the concept of non-persistence for selected system components, organizations can provide a trusted, known state computing resource for a specific time period that does not give adversaries sufficient time to exploit vulnerabilities in organizational systems or operating environments. Since the APT is a high-end, sophisticated threat with regard to capability, intent, and targeting, organizations assume that over an extended period, a percentage of attacks will be successful. Non-persistent system components and services are activated as required using protected information and terminated periodically or at the end of sessions. Non-persistence increases the work factor of adversaries attempting to compromise or breach organizational systems.
Non-persistence can be achieved by refreshing system components, periodically reimaging components, or using a variety of common virtualization techniques. Non-persistent services can be implemented by using virtualization techniques as part of virtual machines or as new instances of processes on physical machines (either persistent or non-persistent). The benefit of periodic refreshes of system components and services is that it does not require organizations to first determine whether compromises of components or services have occurred (something that may often be difficult to determine). The refresh of selected system components and services occurs with sufficient frequency to prevent the spread or intended impact of attacks, but not with such frequency that it makes the system unstable. Refreshes of critical components and services may be done periodically to hinder the ability of adversaries to exploit optimum windows of vulnerabilities.
","uuid":"aaef145f-7bcb-4d90-baaf-cc60a6ac3f12","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"4cdaf5e8-2489-462f-85ec-3cb9acd30816","text":"system components and services","parameterId":"si-14_odp.01","default":" [Assignment: organization defined system components and services] "},{"constraints":"","displayName":"","guidance":"","uuid":"bacadd78-a9ae-4087-8ef0-64e41afb3e09","text":"[Selection (one or more): upon end of session of use; [(NESTED PARAMETER) Assignment for si-14_odp.03: frequency]]","parameterId":"si-14_odp.02","default":"[Selection (one or more): upon end of session of use; [(NESTED PARAMETER) Assignment for si-14_odp.03: frequency]]"},{"constraints":"","displayName":"","guidance":"","uuid":"d01ecd67-7e5a-4341-96e1-aac57c7ac58b","text":"frequency","parameterId":"si-14_odp.03","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"SI-14[01]","uuid":"64814f19-29e4-4da9-a84f-dadea1c713fb","test":"Determine if non-persistent [SELECTED PARAMETER VALUE(S): system components and services ] that are initiated in a known state are implemented;Trusted sources include software and data from write-once, read-only media or from selected offline secure storage facilities.
","uuid":"b934aa8b-2f87-44d9-bfe9-1a108015ca4b","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"819b04b9-ff57-41aa-9f9d-46711291d8d8","text":"trusted sources","parameterId":"si-14.01_odp","default":" [Assignment: organization defined trusted sources] "}],"subControls":"","tests":[{"testId":"SI-14(01)","uuid":"48c67451-c574-4108-901e-44ba369c51f5","test":"Determine if the software and data employed during system component and service refreshes are obtained from [SELECTED PARAMETER VALUE(S): trusted sources ].Retaining information longer than is needed makes the information a potential target for advanced adversaries searching for high value assets to compromise through unauthorized disclosure, unauthorized modification, or exfiltration. For system-related information, unnecessary retention provides advanced adversaries information that can assist in their reconnaissance and lateral movement through the system.
","uuid":"bd3ab5c1-8757-477b-936e-0c4f6caf6b29","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"157deec9-a94c-49ce-9a3f-43d3afc9da67","text":"[Selection: refresh [(NESTED PARAMETER) Assignment for si-14.02_odp.02: information][(NESTED PARAMETER) Assignment for si-14.02_odp.03: frequency]; generate [(NESTED PARAMETER) Assignment for si-14.02_odp.04: information] on demand]","parameterId":"si-14.02_odp.01","default":"[Selection: refresh [(NESTED PARAMETER) Assignment for si-14.02_odp.02: information][(NESTED PARAMETER) Assignment for si-14.02_odp.03: frequency]; generate [(NESTED PARAMETER) Assignment for si-14.02_odp.04: information] on demand]"},{"constraints":"","displayName":"","guidance":"","uuid":"e3ba2e73-69b2-4aed-80c2-b289ca87f898","text":"information","parameterId":"si-14.02_odp.02","default":" [Assignment: organization defined information] "},{"constraints":"","displayName":"","guidance":"","uuid":"877afef8-3998-434f-ace6-7a2ff5e19407","text":"frequency","parameterId":"si-14.02_odp.03","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"aac1f9d5-4b0d-49cd-8ca0-0c8ddd3aff11","text":"information","parameterId":"si-14.02_odp.04","default":" [Assignment: organization defined information] "}],"subControls":"","tests":[{"testId":"SI-14(02)(a)","uuid":"73bd2195-7c31-4e51-a444-10278c990f98","test":"Determine if [SELECTED PARAMETER VALUE(S): [Selection: refresh [(NESTED PARAMETER) Assignment for si-14.02_odp.02: information][(NESTED PARAMETER) Assignment for si-14.02_odp.03: frequency]; generate [(NESTED PARAMETER) Assignment for si-14.02_odp.04: information] on demand] ] is performed;Persistent connections to systems can provide advanced adversaries with paths to move laterally through systems and potentially position themselves closer to high value assets. Limiting the availability of such connections impedes the adversary’s ability to move freely through organizational systems.
","uuid":"d85ebc6b-de98-49b5-82b6-848bb2368794","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"f510b0a0-f019-4d49-91d1-a1aabd91beef","text":"[Selection: completion of a request; a period of non-use]","parameterId":"si-14.03_odp","default":"[Selection: completion of a request; a period of non-use]"}],"subControls":"","tests":[{"testId":"SI-14(03)[01]","uuid":"7842b8ff-e102-451e-90c9-72ed2f48965e","test":"Determine if connections to the system are established on demand;Certain types of attacks, including SQL injections, produce output results that are unexpected or inconsistent with the output results that would be expected from software programs or applications. Information output filtering focuses on detecting extraneous content, preventing such extraneous content from being displayed, and then alerting monitoring tools that anomalous behavior has been discovered.
","uuid":"dd1f8a5f-67f7-4d1f-9e60-f71ad2f393d7","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"b0f8b8ac-ad0c-4577-8e64-17ec9d9fae9c","text":"software programs and/or applications","parameterId":"si-15_odp","default":" [Assignment: organization defined software programs and/or applications] "}],"subControls":"","tests":[{"testId":"SI-15","uuid":"80433d78-c41c-41c4-bf4b-66c3792e614c","test":"Determine if information output from [SELECTED PARAMETER VALUE(S): software programs and/or applications ] is validated to ensure that the information is consistent with the expected content.Some adversaries launch attacks with the intent of executing code in non-executable regions of memory or in memory locations that are prohibited. Controls employed to protect memory include data execution prevention and address space layout randomization. Data execution prevention controls can either be hardware-enforced or software-enforced with hardware enforcement providing the greater strength of mechanism.
","uuid":"fa0ab909-074e-4660-8369-9fb09d0f6c4e","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"c8053918-0bd9-4ae2-942b-a212a0a2c6d9","text":"controls","parameterId":"si-16_odp","default":" [Assignment: organization defined controls] "}],"subControls":"","tests":[{"testId":"SI-16","uuid":"bdbd961b-52bf-4096-aed1-4f8d9196b7ff","test":"Determine if [SELECTED PARAMETER VALUE(S): controls ] are implemented to protect the system memory from unauthorized code execution.Failure conditions include the loss of communications among critical system components or between system components and operational facilities. Fail-safe procedures include alerting operator personnel and providing specific instructions on subsequent steps to take. Subsequent steps may include doing nothing, reestablishing system settings, shutting down processes, restarting the system, or contacting designated organizational personnel.
","uuid":"a2e1ec3b-effd-4f40-8166-40b4680333b1","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"02e058b5-a351-47d4-92d6-16620272de19","text":"organization-defined list of failure conditions and associated fail-safe procedures","parameterId":"si-17_prm_1","default":" [Assignment: organization-defined list of failure conditions and associated fail-safe procedures] "},{"constraints":"","displayName":"","guidance":"","uuid":"9d00fac3-a7a8-4913-90cc-ac379b3a49d1","text":"fail-safe procedures","parameterId":"si-17_odp.01","default":" [Assignment: organization defined fail-safe procedures] "},{"constraints":"","displayName":"","guidance":"","uuid":"df139ba4-70c0-413c-81da-41287769718b","text":"list of failure conditions","parameterId":"si-17_odp.02","default":" [Assignment: organization defined list of failure conditions] "}],"subControls":"","tests":[{"testId":"SI-17","uuid":"8bf7163a-573e-487c-bfde-ab950b39e384","test":"Determine if [SELECTED PARAMETER VALUE(S): fail-safe procedures ] are implemented when [SELECTED PARAMETER VALUE(S): list of failure conditions ] occur.Personally identifiable information quality operations include the steps that organizations take to confirm the accuracy and relevance of personally identifiable information throughout the information life cycle. The information life cycle includes the creation, collection, use, processing, storage, maintenance, dissemination, disclosure, and disposal of personally identifiable information. Personally identifiable information quality operations include editing and validating addresses as they are collected or entered into systems using automated address verification look-up application programming interfaces. Checking personally identifiable information quality includes the tracking of updates or changes to data over time, which enables organizations to know how and what personally identifiable information was changed should erroneous information be identified. The measures taken to protect personally identifiable information quality are based on the nature and context of the personally identifiable information, how it is to be used, how it was obtained, and the potential de-identification methods employed. The measures taken to validate the accuracy of personally identifiable information used to make determinations about the rights, benefits, or privileges of individuals covered under federal programs may be more comprehensive than the measures used to validate personally identifiable information used for less sensitive purposes.
","uuid":"4670bb3d-ad19-4d01-b144-c28310d8480b","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"c917246e-7479-4a4c-aeab-1a3d39733038","text":"organization-defined frequency","parameterId":"si-18_prm_1","default":" [Assignment: organization-defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"ba32b5f1-1619-4549-afc9-2d9c1c3dc9a8","text":"frequency","parameterId":"si-18_odp.01","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"3a2e960f-1af9-44d2-a352-9d54b6783e12","text":"frequency","parameterId":"si-18_odp.02","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"d1726cc6-d761-4ad6-bfe7-d8441f1be4d0","text":"frequency","parameterId":"si-18_odp.03","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"c9ee4f05-7edb-4bd5-8ed3-3fd0cd08d51e","text":"frequency","parameterId":"si-18_odp.04","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"SI-18a.[01]","uuid":"7718f9bc-5cea-449c-b841-5c5ed6beb108","test":"Determine if the accuracy of personally identifiable information across the information life cycle is checked [SELECTED PARAMETER VALUE(S): frequency ];The use of automated mechanisms to improve data quality may inadvertently create privacy risks. Automated tools may connect to external or otherwise unrelated systems, and the matching of records between these systems may create linkages with unintended consequences. Organizations assess and document these risks in their privacy impact assessments and make determinations that are in alignment with their privacy program plans.
As data is obtained and used across the information life cycle, it is important to confirm the accuracy and relevance of personally identifiable information. Automated mechanisms can augment existing data quality processes and procedures and enable an organization to better identify and manage personally identifiable information in large-scale systems. For example, automated tools can greatly improve efforts to consistently normalize data or identify malformed data. Automated tools can also be used to improve the auditing of data and detect errors that may incorrectly alter personally identifiable information or incorrectly associate such information with the wrong individual. Automated capabilities backstop processes and procedures at-scale and enable more fine-grained detection and correction of data quality errors.
","uuid":"2c78c9d4-5882-4711-ab90-0e3fa64cc02f","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"97bdc89b-6379-40b6-bfa8-c7c974c60acd","text":"automated mechanisms","parameterId":"si-18.01_odp","default":" [Assignment: organization defined automated mechanisms] "}],"subControls":"","tests":[{"testId":"SI-18(01)","uuid":"0ca90767-de68-4afb-acec-94b0165d8111","test":"Determine if [SELECTED PARAMETER VALUE(S): automated mechanisms ] are used to correct or delete personally identifiable information that is inaccurate, outdated, incorrectly determined regarding impact, or incorrectly de-identified.Data tagging personally identifiable information includes tags that note processing permissions, authority to process, de-identification, impact level, information life cycle stage, and retention or last updated dates. Employing data tags for personally identifiable information can support the use of automation tools to correct or delete relevant personally identifiable information.
","uuid":"968a5ce7-7ec7-4fa0-96e2-ae97ef1ec134","family":"System and Information Integrity","parameters":[],"subControls":"","tests":[{"testId":"SI-18(02)","uuid":"bda70ab1-68c7-40b6-9dd3-8b0ead705200","test":"Determine if data tags are employed to automate the correction or deletion of personally identifiable information across the information life cycle within organizational systems.Individuals or their designated representatives can be sources of correct personally identifiable information. Organizations consider contextual factors that may incentivize individuals to provide correct data versus false data. Additional steps may be necessary to validate collected information based on the nature and context of the personally identifiable information, how it is to be used, and how it was obtained. The measures taken to validate the accuracy of personally identifiable information used to make determinations about the rights, benefits, or privileges of individuals under federal programs may be more comprehensive than the measures taken to validate less sensitive personally identifiable information.
","uuid":"dd25ee40-f901-4971-83f5-003caf0ce96b","family":"System and Information Integrity","parameters":[],"subControls":"","tests":[{"testId":"SI-18(03)","uuid":"a7b1c696-6409-412d-882f-c9d310b85da0","test":"Determine if personally identifiable information is collected directly from the individual.Inaccurate personally identifiable information maintained by organizations may cause problems for individuals, especially in those business functions where inaccurate information may result in inappropriate decisions or the denial of benefits and services to individuals. Even correct information, in certain circumstances, can cause problems for individuals that outweigh the benefits of an organization maintaining the information. Organizations use discretion when determining if personally identifiable information is to be corrected or deleted based on the scope of requests, the changes sought, the impact of the changes, and laws, regulations, and policies. Organizational personnel consult with the senior agency official for privacy and legal counsel regarding appropriate instances of correction or deletion.
","uuid":"30c1db7d-bf05-4430-93e2-149d76d44455","family":"System and Information Integrity","parameters":[],"subControls":"","tests":[{"testId":"SI-18(04)","uuid":"0f7954e0-a92f-4852-8733-f46ceecafe27","test":"Determine if personally identifiable information is corrected or deleted upon request by individuals or their designated representatives.When personally identifiable information is corrected or deleted, organizations take steps to ensure that all authorized recipients of such information, and the individual with whom the information is associated or their designated representatives, are informed of the corrected or deleted information.
","uuid":"696275f7-cdb5-4287-ad50-01a572f2eb04","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"97cc4b78-954b-419c-84df-3aa1edc38b56","text":"recipients","parameterId":"si-18.05_odp","default":" [Assignment: organization defined recipients] "}],"subControls":"","tests":[{"testId":"SI-18(05)","uuid":"ae157fed-4b0f-4331-a523-cdd17f7dd7dc","test":"Determine if [SELECTED PARAMETER VALUE(S): recipients ] and individuals are notified when the personally identifiable information has been corrected or deleted.De-identification is the general term for the process of removing the association between a set of identifying data and the data subject. Many datasets contain information about individuals that can be used to distinguish or trace an individual’s identity, such as name, social security number, date and place of birth, mother’s maiden name, or biometric records. Datasets may also contain other information that is linked or linkable to an individual, such as medical, educational, financial, and employment information. Personally identifiable information is removed from datasets by trained individuals when such information is not (or no longer) necessary to satisfy the requirements envisioned for the data. For example, if the dataset is only used to produce aggregate statistics, the identifiers that are not needed for producing those statistics are removed. Removing identifiers improves privacy protection since information that is removed cannot be inadvertently disclosed or improperly used. Organizations may be subject to specific de-identification definitions or methods under applicable laws, regulations, or policies. Re-identification is a residual risk with de-identified data. Re-identification attacks can vary, including combining new datasets or other improvements in data analytics. Maintaining awareness of potential attacks and evaluating for the effectiveness of the de-identification over time support the management of this residual risk.
","uuid":"dfefac1b-0a80-4a44-83c3-57e49f49f2d3","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"07f12a4a-7b3f-4e66-82cd-198ccdcb2197","text":"elements","parameterId":"si-19_odp.01","default":" [Assignment: organization defined elements] "},{"constraints":"","displayName":"","guidance":"","uuid":"e5114b84-c8c6-4698-9151-d97f00009342","text":"frequency","parameterId":"si-19_odp.02","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"SI-19a.","uuid":"4c8e5d64-9ff9-47a9-b90b-2b4389c175b3","test":"Determine if [SELECTED PARAMETER VALUE(S): elements ] are removed from datasets;If a data source contains personally identifiable information but the information will not be used, the dataset can be de-identified when it is created by not collecting the data elements that contain the personally identifiable information. For example, if an organization does not intend to use the social security number of an applicant, then application forms do not ask for a social security number.
","uuid":"d9942e8a-9f08-410e-85fc-28d2d0b3bc34","family":"System and Information Integrity","parameters":[],"subControls":"","tests":[{"testId":"SI-19(01)","uuid":"dc95527a-5ef1-4111-8c91-ea4ff9c22d6e","test":"Determine if the dataset is de-identified upon collection by not collecting personally identifiable information.Datasets can be archived for many reasons. The envisioned purposes for the archived dataset are specified, and if personally identifiable information elements are not required, the elements are not archived. For example, social security numbers may have been collected for record linkage, but the archived dataset may include the required elements from the linked records. In this case, it is not necessary to archive the social security numbers.
","uuid":"78852ba6-a648-4fbe-b31f-c73eb0514106","family":"System and Information Integrity","parameters":[],"subControls":"","tests":[{"testId":"SI-19(02)","uuid":"656685e5-21dd-4133-a714-1710aee684fa","test":"Determine if the archiving of personally identifiable information elements is prohibited if those elements in a dataset will not be needed after the dataset is archived.Prior to releasing a dataset, a data custodian considers the intended uses of the dataset and determines if it is necessary to release personally identifiable information. If the personally identifiable information is not necessary, the information can be removed using de-identification techniques.
","uuid":"21a82075-3ef4-4407-9a27-ac36b66eaac1","family":"System and Information Integrity","parameters":[],"subControls":"","tests":[{"testId":"SI-19(03)","uuid":"81f4326a-bd6f-4156-b065-1cb0b9460985","test":"Determine if personally identifiable information elements are removed from a dataset prior to its release if those elements in the dataset do not need to be part of the data release.There are many possible processes for removing direct identifiers from a dataset. Columns in a dataset that contain a direct identifier can be removed. In masking, the direct identifier is transformed into a repeating character, such as XXXXXX or 999999. Identifiers can be encrypted or hashed so that the linked records remain linked. In the case of encryption or hashing, algorithms are employed that require the use of a key, including the Advanced Encryption Standard or a Hash-based Message Authentication Code. Implementations may use the same key for all identifiers or use a different key for each identifier. Using a different key for each identifier provides a higher degree of security and privacy. Identifiers can alternatively be replaced with a keyword, including transforming George Washington
to PATIENT
or replacing it with a surrogate value, such as transforming George Washington
to Abraham Polk.
\n
Many types of statistical analyses can result in the disclosure of information about individuals even if only summary information is provided. For example, if a school that publishes a monthly table with the number of minority students enrolled, reports that it has 10-19 such students in January, and subsequently reports that it has 20-29 such students in March, then it can be inferred that the student who enrolled in February was a minority.
","uuid":"b03d9941-fad0-4965-9bf3-ed2506722544","family":"System and Information Integrity","parameters":[],"subControls":"","tests":[{"testId":"SI-19(05)[01]","uuid":"bec85323-1294-4e6a-b8e9-e9ba3fa3db9a","test":"Determine if numerical data is manipulated so that no individual or organization is identifiable in the results of the analysis;The mathematical definition for differential privacy holds that the result of a dataset analysis should be approximately the same before and after the addition or removal of a single data record (which is assumed to be the data from a single individual). In its most basic form, differential privacy applies only to online query systems. However, it can also be used to produce machine-learning statistical classifiers and synthetic data. Differential privacy comes at the cost of decreased accuracy of results, forcing organizations to quantify the trade-off between privacy protection and the overall accuracy, usefulness, and utility of the de-identified dataset. Non-deterministic noise can include adding small, random values to the results of mathematical operations in dataset analysis.
","uuid":"64cd6ac4-14f0-44d9-8c45-a615e8f36385","family":"System and Information Integrity","parameters":[],"subControls":"","tests":[{"testId":"SI-19(06)","uuid":"53969a02-8d62-48d9-9ad3-6ed25c68cd6b","test":"Determine if the disclosure of personally identifiable information is prevented by adding non-deterministic noise to the results of mathematical operations before the results are reported.Algorithms that appear to remove personally identifiable information from a dataset may in fact leave information that is personally identifiable or data that is re-identifiable. Software that is claimed to implement a validated algorithm may contain bugs or implement a different algorithm. Software may de-identify one type of data, such as integers, but not de-identify another type of data, such as floating point numbers. For these reasons, de-identification is performed using algorithms and software that are validated.
","uuid":"8e9343f1-8d0f-4763-85f7-8ecc14ec4f8e","family":"System and Information Integrity","parameters":[],"subControls":"","tests":[{"testId":"SI-19(07)[01]","uuid":"3864a4a8-843e-47a7-bce5-626f411902b4","test":"Determine if de-identification is performed using validated algorithms;A motivated intruder test is a test in which an individual or group takes a data release and specified resources and attempts to re-identify one or more individuals in the de-identified dataset. Such tests specify the amount of inside knowledge, computational resources, financial resources, data, and skills that intruders possess to conduct the tests. A motivated intruder test can determine if the de-identification is insufficient. It can also be a useful diagnostic tool to assess if de-identification is likely to be sufficient. However, the test alone cannot prove that de-identification is sufficient.
","uuid":"4a9ceb03-b284-4ffd-844e-dc75fb098185","family":"System and Information Integrity","parameters":[],"subControls":"","tests":[{"testId":"SI-19(08)","uuid":"de879c15-e9bb-4edd-969b-872927c7cc64","test":"Determine if a motivated intruder test is performed on the de-identified dataset to determine if the identified data remains or if the de-identified data can be re-identified.Many cyber-attacks target organizational information, or information that the organization holds on behalf of other entities (e.g., personally identifiable information), and exfiltrate that data. In addition, insider attacks and erroneous user procedures can remove information from the system that is in violation of the organizational policies. Tainting approaches can range from passive to active. A passive tainting approach can be as simple as adding false email names and addresses to an internal database. If the organization receives email at one of the false email addresses, it knows that the database has been compromised. Moreover, the organization knows that the email was sent by an unauthorized entity, so any packets it includes potentially contain malicious code, and that the unauthorized entity may have potentially obtained a copy of the database. Another tainting approach can include embedding false data or steganographic data in files to enable the data to be found via open-source analysis. Finally, an active tainting approach can include embedding software in the data that is able to call home,
thereby alerting the organization to its capture,
and possibly its location, and the path by which it was exfiltrated or removed.
Retaining information for longer than it is needed makes it an increasingly valuable and enticing target for adversaries. Keeping information available for the minimum period of time needed to support organizational missions or business functions reduces the opportunity for adversaries to compromise, capture, and exfiltrate that information.
","uuid":"0b25cc43-4ff6-4942-b322-80599ee6714e","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"39373ed0-1e92-4e2c-afc0-eb6ebf95a2c9","text":"information","parameterId":"si-21_odp.01","default":" [Assignment: organization defined information] "},{"constraints":"","displayName":"","guidance":"","uuid":"0f99c321-5560-4736-9545-2aa8ebcb4182","text":"frequencies","parameterId":"si-21_odp.02","default":" [Assignment: organization defined frequencies] "}],"subControls":"","tests":[{"testId":"SI-21","uuid":"0f615f22-aee8-48fc-936f-4481d4a7083e","test":"Determine if the [SELECTED PARAMETER VALUE(S): information ] is refreshed [SELECTED PARAMETER VALUE(S): frequencies ] or is generated on demand and deleted when no longer needed.Actions taken by a system service or a function are often driven by the information it receives. Corruption, fabrication, modification, or deletion of that information could impact the ability of the service function to properly carry out its intended actions. By having multiple sources of input, the service or function can continue operation if one source is corrupted or no longer available. It is possible that the alternative sources of information may be less precise or less accurate than the primary source of information. But having such sub-optimal information sources may still provide a sufficient level of quality that the essential service or function can be carried out, even in a degraded or debilitated manner.
","uuid":"da637311-1dae-40e0-8306-cc5af7555e65","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"9fb7afe6-8835-41dc-84a6-fb9f32b06386","text":"alternative information sources","parameterId":"si-22_odp.01","default":" [Assignment: organization defined alternative information sources] "},{"constraints":"","displayName":"","guidance":"","uuid":"db581741-c19f-40e9-a523-5ebdde967bd8","text":"essential functions and services","parameterId":"si-22_odp.02","default":" [Assignment: organization defined essential functions and services] "},{"constraints":"","displayName":"","guidance":"","uuid":"255795be-4c14-4fac-ab57-f13de0ae7429","text":"systems or system components","parameterId":"si-22_odp.03","default":" [Assignment: organization defined systems or system components] "}],"subControls":"","tests":[{"testId":"SI-22a.","uuid":"26dfb9f2-a074-45c8-a6c6-ef8021da966a","test":"Determine if [SELECTED PARAMETER VALUE(S): alternative information sources ] for [SELECTED PARAMETER VALUE(S): essential functions and services ] are identified;One objective of the advanced persistent threat is to exfiltrate valuable information. Once exfiltrated, there is generally no way for the organization to recover the lost information. Therefore, organizations may consider dividing the information into disparate elements and distributing those elements across multiple systems or system components and locations. Such actions will increase the adversary’s work factor to capture and exfiltrate the desired information and, in so doing, increase the probability of detection. The fragmentation of information impacts the organization’s ability to access the information in a timely manner. The extent of the fragmentation is dictated by the impact or classification level (and value) of the information, threat intelligence information received, and whether data tainting is used (i.e., data tainting-derived information about the exfiltration of some information could result in the fragmentation of the remaining information).
","uuid":"81fd4a30-1970-4cb2-b77f-4d3da7b26d85","family":"System and Information Integrity","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"7d2fb2f0-1b97-4a8d-9a46-f113926e255d","text":"circumstances","parameterId":"si-23_odp.01","default":" [Assignment: organization defined circumstances] "},{"constraints":"","displayName":"","guidance":"","uuid":"2140c9b7-53f3-470f-aee4-9c17c2b9bff7","text":"information","parameterId":"si-23_odp.02","default":" [Assignment: organization defined information] "},{"constraints":"","displayName":"","guidance":"","uuid":"e73a3a92-38c7-44cd-8895-f8758ac2ad10","text":"systems or system components","parameterId":"si-23_odp.03","default":" [Assignment: organization defined systems or system components] "}],"subControls":"","tests":[{"testId":"SI-23a.","uuid":"483fb050-e7b3-4580-bed3-183bb57f98e1","test":"Determine if under [SELECTED PARAMETER VALUE(S): circumstances ], [SELECTED PARAMETER VALUE(S): information ] is fragmented;Supply chain risk management policy and procedures address the controls in the SR family as well as supply chain-related controls in other families that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of supply chain risk management policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission or business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to supply chain risk management policy and procedures include assessment or audit findings, security incidents or breaches, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure.
","uuid":"66e90d71-60ec-40ba-801c-3229c79195fb","family":"Supply Chain Risk Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"45a4e5aa-305b-4e14-85bf-6f8fd0a0fcf0","text":"organization-defined personnel or roles","parameterId":"sr-1_prm_1","default":" [Assignment: organization-defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"eb03af06-9cd3-41f1-9942-2b3ecf4dd88c","text":"personnel or roles","parameterId":"sr-01_odp.01","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"feca90c4-4eac-4eaf-86c4-8f827f63bb45","text":"personnel or roles","parameterId":"sr-01_odp.02","default":" [Assignment: organization defined personnel or roles] "},{"constraints":"","displayName":"","guidance":"","uuid":"adc05a17-bd46-45fa-a284-237adfab7a68","text":"[Selection (one or more): organization-level; mission/business process-level; system-level]","parameterId":"sr-01_odp.03","default":"[Selection (one or more): organization-level; mission/business process-level; system-level]"},{"constraints":"","displayName":"","guidance":"","uuid":"b73d5c2a-7bb3-4a9f-a63f-59046e539ca3","text":"official","parameterId":"sr-01_odp.04","default":" [Assignment: organization defined official] "},{"constraints":"","displayName":"","guidance":"","uuid":"1ca51107-6c8c-478a-a1e7-6098a50bfaf2","text":"frequency","parameterId":"sr-01_odp.05","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"5bec85de-a84d-4379-b929-c29d3b07eb77","text":"events","parameterId":"sr-01_odp.06","default":" [Assignment: organization defined events] "},{"constraints":"","displayName":"","guidance":"","uuid":"8f5dfc39-ab7b-4f0a-bdbd-89c775a20730","text":"frequency","parameterId":"sr-01_odp.07","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"6b5163d1-304e-4b88-aa20-a1fdda4ef4ce","text":"events","parameterId":"sr-01_odp.08","default":" [Assignment: organization defined events] "}],"subControls":"","tests":[{"testId":"SR-01a.[01]","uuid":"b6edb1dd-de30-47f1-a233-fb05e80805c6","test":"Determine if a supply chain risk management policy is developed and documented;The dependence on products, systems, and services from external providers, as well as the nature of the relationships with those providers, present an increasing level of risk to an organization. Threat actions that may increase security or privacy risks include unauthorized production, the insertion or use of counterfeits, tampering, theft, insertion of malicious software and hardware, and poor manufacturing and development practices in the supply chain. Supply chain risks can be endemic or systemic within a system element or component, a system, an organization, a sector, or the Nation. Managing supply chain risk is a complex, multifaceted undertaking that requires a coordinated effort across an organization to build trust relationships and communicate with internal and external stakeholders. Supply chain risk management (SCRM) activities include identifying and assessing risks, determining appropriate risk response actions, developing SCRM plans to document response actions, and monitoring performance against plans. The SCRM plan (at the system-level) is implementation specific, providing policy implementation, requirements, constraints and implications. It can either be stand-alone, or incorporated into system security and privacy plans. The SCRM plan addresses managing, implementation, and monitoring of SCRM controls and the development/sustainment of systems across the SDLC to support mission and business functions.
Because supply chains can differ significantly across and within organizations, SCRM plans are tailored to the individual program, organizational, and operational contexts. Tailored SCRM plans provide the basis for determining whether a technology, service, system component, or system is fit for purpose, and as such, the controls need to be tailored accordingly. Tailored SCRM plans help organizations focus their resources on the most critical mission and business functions based on mission and business requirements and their risk environment. Supply chain risk management plans include an expression of the supply chain risk tolerance for the organization, acceptable supply chain risk mitigation strategies or controls, a process for consistently evaluating and monitoring supply chain risk, approaches for implementing and communicating the plan, a description of and justification for supply chain risk mitigation measures taken, and associated roles and responsibilities. Finally, supply chain risk management plans address requirements for developing trustworthy, secure, privacy-protective, and resilient system components and systems, including the application of the security design principles implemented as part of life cycle-based systems security engineering processes (see SA-8).
","uuid":"16aa3826-c280-4e34-a98c-124ae64c30d1","family":"Supply Chain Risk Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"338b267d-e9bc-4396-8ef6-d848f9e7abdb","text":"systems, system components, or system services","parameterId":"sr-02_odp.01","default":" [Assignment: organization defined systems, system components, or system services] "},{"constraints":"","displayName":"","guidance":"","uuid":"74e79711-b5d7-4082-a493-59e860bd3e68","text":"frequency","parameterId":"sr-02_odp.02","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"SR-02a.[01]","uuid":"490fb3b8-dea0-4ac0-b1bd-4cb7968f6b05","test":"Determine if a plan for managing supply chain risks is developed;To implement supply chain risk management plans, organizations establish a coordinated, team-based approach to identify and assess supply chain risks and manage these risks by using programmatic and technical mitigation techniques. The team approach enables organizations to conduct an analysis of their supply chain, communicate with internal and external partners or stakeholders, and gain broad consensus regarding the appropriate resources for SCRM. The SCRM team consists of organizational personnel with diverse roles and responsibilities for leading and supporting SCRM activities, including risk executive, information technology, contracting, information security, privacy, mission or business, legal, supply chain and logistics, acquisition, business continuity, and other relevant functions. Members of the SCRM team are involved in various aspects of the SDLC and, collectively, have an awareness of and provide expertise in acquisition processes, legal practices, vulnerabilities, threats, and attack vectors, as well as an understanding of the technical aspects and dependencies of systems. The SCRM team can be an extension of the security and privacy risk management processes or be included as part of an organizational risk management team.
","uuid":"2c344031-62b5-4386-81f9-008b360cd789","family":"Supply Chain Risk Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"2435a2ab-a831-48a0-a4ea-7a491cc2b249","text":"personnel, roles and responsibilities","parameterId":"sr-02.01_odp.01","default":" [Assignment: organization defined personnel, roles and responsibilities] "},{"constraints":"","displayName":"","guidance":"","uuid":"0d616c3d-42d4-4415-bfd4-dd7fa2c389cd","text":"supply chain risk management activities","parameterId":"sr-02.01_odp.02","default":" [Assignment: organization defined supply chain risk management activities] "}],"subControls":"","tests":[{"testId":"SR-02(01)","uuid":"d08a9c73-061a-47d6-b1d9-a12477d7ad64","test":"Determine if a supply chain risk management team consisting of [SELECTED PARAMETER VALUE(S): personnel, roles and responsibilities ] is established to lead and support [SELECTED PARAMETER VALUE(S): supply chain risk management activities ].Supply chain elements include organizations, entities, or tools employed for the research and development, design, manufacturing, acquisition, delivery, integration, operations and maintenance, and disposal of systems and system components. Supply chain processes include hardware, software, and firmware development processes; shipping and handling procedures; personnel security and physical security programs; configuration management tools, techniques, and measures to maintain provenance; or other programs, processes, or procedures associated with the development, acquisition, maintenance and disposal of systems and system components. Supply chain elements and processes may be provided by organizations, system integrators, or external providers. Weaknesses or deficiencies in supply chain elements or processes represent potential vulnerabilities that can be exploited by adversaries to cause harm to the organization and affect its ability to carry out its core missions or business functions. Supply chain personnel are individuals with roles and responsibilities in the supply chain.
","uuid":"60b10cbc-91ae-4cff-b051-d6ee1912afcd","family":"Supply Chain Risk Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"458954a7-9f02-44fa-8521-12e06c952b30","text":"system or system component","parameterId":"sr-03_odp.01","default":" [Assignment: organization defined system or system component] "},{"constraints":"","displayName":"","guidance":"","uuid":"49b0500a-f11d-401b-88e1-c5001a0d6e3a","text":"supply chain personnel","parameterId":"sr-03_odp.02","default":" [Assignment: organization defined supply chain personnel] "},{"constraints":"","displayName":"","guidance":"","uuid":"e7f70d16-fdc5-428d-ba16-5cedd1dc1fb7","text":"supply chain controls","parameterId":"sr-03_odp.03","default":" [Assignment: organization defined supply chain controls] "},{"constraints":"","displayName":"","guidance":"","uuid":"44bdd413-bd53-4c31-a900-a09c327b8388","text":"[Selection (one or more): security and privacy plans; supply chain risk management plan; [(NESTED PARAMETER) Assignment for sr-03_odp.05: document]]","parameterId":"sr-03_odp.04","default":"[Selection (one or more): security and privacy plans; supply chain risk management plan; [(NESTED PARAMETER) Assignment for sr-03_odp.05: document]]"},{"constraints":"","displayName":"","guidance":"","uuid":"90a20a0d-e1ed-4aa5-9c14-dfea5c1442d8","text":"document","parameterId":"sr-03_odp.05","default":" [Assignment: organization defined document] "}],"subControls":"","tests":[{"testId":"SR-03a.[01]","uuid":"fc490ebf-616b-4f14-8e5a-82223d85b115","test":"Determine if a process or processes is/are established to identify and address weaknesses or deficiencies in the supply chain elements and processes of [SELECTED PARAMETER VALUE(S): system or system component ];Diversifying the supply of systems, system components, and services can reduce the probability that adversaries will successfully identify and target the supply chain and can reduce the impact of a supply chain event or compromise. Identifying multiple suppliers for replacement components can reduce the probability that the replacement component will become unavailable. Employing a diverse set of developers or logistics service providers can reduce the impact of a natural disaster or other supply chain event. Organizations consider designing the system to include diverse materials and components.
","uuid":"30a4b38d-5cf8-45c8-943d-68ee15664c05","family":"Supply Chain Risk Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"734ae43f-b28a-468f-a01a-34022cbf11f9","text":"organization-defined system components and services","parameterId":"sr-3.1_prm_1","default":" [Assignment: organization-defined system components and services] "},{"constraints":"","displayName":"","guidance":"","uuid":"3d45468d-7b62-4528-9e7b-5048060dc1ca","text":"system components","parameterId":"sr-03.01_odp.01","default":" [Assignment: organization defined system components] "},{"constraints":"","displayName":"","guidance":"","uuid":"8c95b99f-79a6-4914-b09e-023f69071103","text":"services","parameterId":"sr-03.01_odp.02","default":" [Assignment: organization defined services] "}],"subControls":"","tests":[{"testId":"SR-03(01)[01]","uuid":"1f4b630e-61c8-40e8-9434-6ea4667116d0","test":"Determine if a diverse set of sources is employed for [SELECTED PARAMETER VALUE(S): system components ];Controls that can be implemented to reduce the probability of adversaries successfully identifying and targeting the supply chain include avoiding the purchase of custom or non-standardized configurations, employing approved vendor lists with standing reputations in industry, following pre-agreed maintenance schedules and update and patch delivery mechanisms, maintaining a contingency plan in case of a supply chain event, using procurement carve-outs that provide exclusions to commitments or obligations, using diverse delivery routes, and minimizing the time between purchase decisions and delivery.
","uuid":"29d7d046-585e-431d-80db-5d485c427b57","family":"Supply Chain Risk Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"b150a721-4b30-4326-872a-f5a93695a9a7","text":"controls","parameterId":"sr-03.02_odp","default":" [Assignment: organization defined controls] "}],"subControls":"","tests":[{"testId":"SR-03(02)","uuid":"84792e34-930a-4e65-ab27-7536904d165e","test":"Determine if [SELECTED PARAMETER VALUE(S): controls ] are employed to limit harm from potential adversaries identifying and targeting the organizational supply chain.To manage supply chain risk effectively and holistically, it is important that organizations ensure that supply chain risk management controls are included at all tiers in the supply chain. This includes ensuring that Tier 1 (prime) contractors have implemented processes to facilitate the flow down
of supply chain risk management controls to sub-tier contractors. The controls subject to flow down are identified in SR-3b.
Every system and system component has a point of origin and may be changed throughout its existence. Provenance is the chronology of the origin, development, ownership, location, and changes to a system or system component and associated data. It may also include personnel and processes used to interact with or make modifications to the system, component, or associated data. Organizations consider developing procedures (see SR-1 ) for allocating responsibilities for the creation, maintenance, and monitoring of provenance for systems and system components; transferring provenance documentation and responsibility between organizations; and preventing and monitoring for unauthorized changes to the provenance records. Organizations have methods to document, monitor, and maintain valid provenance baselines for systems, system components, and related data. These actions help track, assess, and document any changes to the provenance, including changes in supply chain elements or configuration, and help ensure non-repudiation of provenance information and the provenance change records. Provenance considerations are addressed throughout the system development life cycle and incorporated into contracts and other arrangements, as appropriate.
","uuid":"f021a858-da87-455f-a544-b921ee9cd649","family":"Supply Chain Risk Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"b0b92fe0-1780-4a85-9f0b-656ce3ca3ded","text":"systems, system components, and associated data","parameterId":"sr-04_odp","default":" [Assignment: organization defined systems, system components, and associated data] "}],"subControls":"","tests":[{"testId":"SR-04[01]","uuid":"3d1caf4a-1fd7-44e7-95d5-a114821a651c","test":"Determine if valid provenance is documented for [SELECTED PARAMETER VALUE(S): systems, system components, and associated data ];Knowing who and what is in the supply chains of organizations is critical to gaining visibility into supply chain activities. Visibility into supply chain activities is also important for monitoring and identifying high-risk events and activities. Without reasonable visibility into supply chains elements, processes, and personnel, it is very difficult for organizations to understand and manage risk and reduce their susceptibility to adverse events. Supply chain elements include organizations, entities, or tools used for the research and development, design, manufacturing, acquisition, delivery, integration, operations, maintenance, and disposal of systems and system components. Supply chain processes include development processes for hardware, software, and firmware; shipping and handling procedures; configuration management tools, techniques, and measures to maintain provenance; personnel and physical security programs; or other programs, processes, or procedures associated with the production and distribution of supply chain elements. Supply chain personnel are individuals with specific roles and responsibilities related to the secure the research and development, design, manufacturing, acquisition, delivery, integration, operations and maintenance, and disposal of a system or system component. Identification methods are sufficient to support an investigation in case of a supply chain change (e.g. if a supply company is purchased), compromise, or event.
","uuid":"643cc048-d1ec-411f-b940-385c3d7605c8","family":"Supply Chain Risk Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"54ceaf7d-99db-415f-8be1-f073063e49f6","text":"supply chain elements, processes, and personnel","parameterId":"sr-04.01_odp","default":" [Assignment: organization defined supply chain elements, processes, and personnel] "}],"subControls":"","tests":[{"testId":"SR-04(01)[01]","uuid":"0edcfcc6-7a5c-4798-810c-4a3c71d9639e","test":"Determine if unique identification of [SELECTED PARAMETER VALUE(S): supply chain elements, processes, and personnel ] is established;Tracking the unique identification of systems and system components during development and transport activities provides a foundational identity structure for the establishment and maintenance of provenance. For example, system components may be labeled using serial numbers or tagged using radio-frequency identification tags. Labels and tags can help provide better visibility into the provenance of a system or system component. A system or system component may have more than one unique identifier. Identification methods are sufficient to support a forensic investigation after a supply chain compromise or event.
","uuid":"aefc4324-f45d-4a8c-9ac6-be865a45aaa3","family":"Supply Chain Risk Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"123c8e00-3e62-4a00-a284-2337f13eec36","text":"systems and critical system components","parameterId":"sr-04.02_odp","default":" [Assignment: organization defined systems and critical system components] "}],"subControls":"","tests":[{"testId":"SR-04(02)[01]","uuid":"2313fb20-5380-41af-ac2d-cd6299e5874f","test":"Determine if the unique identification of [SELECTED PARAMETER VALUE(S): systems and critical system components ] is established for tracking through the supply chain;For many systems and system components, especially hardware, there are technical means to determine if the items are genuine or have been altered, including optical and nanotechnology tagging, physically unclonable functions, side-channel analysis, cryptographic hash verifications or digital signatures, and visible anti-tamper labels or stickers. Controls can also include monitoring for out of specification performance, which can be an indicator of tampering or counterfeits. Organizations may leverage supplier and contractor processes for validating that a system or component is genuine and has not been altered and for replacing a suspect system or component. Some indications of tampering may be visible and addressable before accepting delivery, such as inconsistent packaging, broken seals, and incorrect labels. When a system or system component is suspected of being altered or counterfeit, the supplier, contractor, or original equipment manufacturer may be able to replace the item or provide a forensic capability to determine the origin of the counterfeit or altered item. Organizations can provide training to personnel on how to identify suspicious system or component deliveries.
","uuid":"d0c98597-16d2-40e8-b38f-cc13b6e19754","family":"Supply Chain Risk Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"a225bcde-8397-4f0a-9aaa-280002e7373b","text":"organization-defined controls","parameterId":"sr-4.3_prm_1","default":" [Assignment: organization-defined controls] "},{"constraints":"","displayName":"","guidance":"","uuid":"32a6cd9c-4518-4559-90b1-aa117ed6c5a1","text":"controls","parameterId":"sr-04.03_odp.01","default":" [Assignment: organization defined controls] "},{"constraints":"","displayName":"","guidance":"","uuid":"929af14c-b6b0-4bfa-a0f2-a940771d0bb1","text":"controls","parameterId":"sr-04.03_odp.02","default":" [Assignment: organization defined controls] "}],"subControls":"","tests":[{"testId":"SR-04(03)[01]","uuid":"cf344be4-0671-4663-ba47-7065581463ba","test":"Determine if [SELECTED PARAMETER VALUE(S): controls ] are employed to validate that the system or system component received is genuine;Authoritative information regarding the internal composition of system components and the provenance of technology, products, and services provides a strong basis for trust. The validation of the internal composition and provenance of technologies, products, and services is referred to as the pedigree. For microelectronics, this includes material composition of components. For software this includes the composition of open-source and proprietary code, including the version of the component at a given point in time. Pedigrees increase the assurance that the claims suppliers assert about the internal composition and provenance of the products, services, and technologies they provide are valid. The validation of the internal composition and provenance can be achieved by various evidentiary artifacts or records that manufacturers and suppliers produce during the research and development, design, manufacturing, acquisition, delivery, integration, operations and maintenance, and disposal of technology, products, and services. Evidentiary artifacts include, but are not limited to, software identification (SWID) tags, software component inventory, the manufacturers’ declarations of platform attributes (e.g., serial numbers, hardware component inventory), and measurements (e.g., firmware hashes) that are tightly bound to the hardware itself.
","uuid":"ea9d4671-f499-4751-a972-d4e198caecbd","family":"Supply Chain Risk Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"093b76f9-df29-4980-944c-881f78818faa","text":"controls","parameterId":"sr-04.04_odp.01","default":" [Assignment: organization defined controls] "},{"constraints":"","displayName":"","guidance":"","uuid":"fd0f7e9d-27e5-4569-ad5b-94b990b18e09","text":"analysis method","parameterId":"sr-04.04_odp.02","default":" [Assignment: organization defined analysis method] "}],"subControls":"","tests":[{"testId":"SR-04(04)[01]","uuid":"7fde3b2a-5fb0-429e-86c1-721fdfcf73a2","test":"Determine if [SELECTED PARAMETER VALUE(S): controls ] are employed to ensure the integrity of the system and system components;The use of the acquisition process provides an important vehicle to protect the supply chain. There are many useful tools and techniques available, including obscuring the end use of a system or system component, using blind or filtered buys, requiring tamper-evident packaging, or using trusted or controlled distribution. The results from a supply chain risk assessment can guide and inform the strategies, tools, and methods that are most applicable to the situation. Tools and techniques may provide protections against unauthorized production, theft, tampering, insertion of counterfeits, insertion of malicious software or backdoors, and poor development practices throughout the system development life cycle. Organizations also consider providing incentives for suppliers who implement controls, promote transparency into their processes and security and privacy practices, provide contract language that addresses the prohibition of tainted or counterfeit components, and restrict purchases from untrustworthy suppliers. Organizations consider providing training, education, and awareness programs for personnel regarding supply chain risk, available mitigation strategies, and when the programs should be employed. Methods for reviewing and protecting development plans, documentation, and evidence are commensurate with the security and privacy requirements of the organization. Contracts may specify documentation protection requirements.
","uuid":"be8976a6-e0aa-4d25-9154-9b20b092deb4","family":"Supply Chain Risk Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"bf834ec1-5e0a-478a-8a78-3468bfc7264b","text":"strategies, tools, and methods","parameterId":"sr-05_odp","default":" [Assignment: organization defined strategies, tools, and methods] "}],"subControls":"","tests":[{"testId":"SR-05[01]","uuid":"f65ba78c-c502-43bf-abcb-a7a32a64769a","test":"Determine if [SELECTED PARAMETER VALUE(S): strategies, tools, and methods ] are employed to protect against supply chain risks;Adversaries can attempt to impede organizational operations by disrupting the supply of critical system components or corrupting supplier operations. Organizations may track systems and component mean time to failure to mitigate the loss of temporary or permanent system function. Controls to ensure that adequate supplies of critical system components include the use of multiple suppliers throughout the supply chain for the identified critical components, stockpiling spare components to ensure operation during mission-critical times, and the identification of functionally identical or similar components that may be used, if necessary.
","uuid":"496b68ad-cf16-4b76-869c-c2e6c2147f28","family":"Supply Chain Risk Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"075b057c-a98e-49b9-ad80-d8013b71d4d7","text":"controls","parameterId":"sr-05.01_odp.01","default":" [Assignment: organization defined controls] "},{"constraints":"","displayName":"","guidance":"","uuid":"e6c8e850-b192-4029-ab4e-50a98863befa","text":"critical system components","parameterId":"sr-05.01_odp.02","default":" [Assignment: organization defined critical system components] "}],"subControls":"","tests":[{"testId":"SR-05(01)","uuid":"ecd7764b-d30a-401b-8f39-c6af4f81219b","test":"Determine if [SELECTED PARAMETER VALUE(S): controls ] are employed to ensure an adequate supply of [SELECTED PARAMETER VALUE(S): critical system components ].Organizational personnel or independent, external entities conduct assessments of systems, components, products, tools, and services to uncover evidence of tampering, unintentional and intentional vulnerabilities, or evidence of non-compliance with supply chain controls. These include malicious code, malicious processes, defective software, backdoors, and counterfeits. Assessments can include evaluations; design proposal reviews; visual or physical inspection; static and dynamic analyses; visual, x-ray, or magnetic particle inspections; simulations; white, gray, or black box testing; fuzz testing; stress testing; and penetration testing (see SR-6(1) ). Evidence generated during assessments is documented for follow-on actions by organizations. The evidence generated during the organizational or independent assessments of supply chain elements may be used to improve supply chain processes and inform the supply chain risk management process. The evidence can be leveraged in follow-on assessments. Evidence and other documentation may be shared in accordance with organizational agreements.
","uuid":"506d741f-0899-4ab0-a159-2b7337866a59","family":"Supply Chain Risk Management","parameters":[],"subControls":"","tests":[{"testId":"SR-05(02)[01]","uuid":"865b877b-4a4e-4479-9938-fb24564dd1a2","test":"Determine if the system, system component, or system service is assessed prior to selection;An assessment and review of supplier risk includes security and supply chain risk management processes, foreign ownership, control or influence (FOCI), and the ability of the supplier to effectively assess subordinate second-tier and third-tier suppliers and contractors. The reviews may be conducted by the organization or by an independent third party. The reviews consider documented processes, documented controls, all-source intelligence, and publicly available information related to the supplier or contractor. Organizations can use open-source information to monitor for indications of stolen information, poor development and quality control practices, information spillage, or counterfeits. In some cases, it may be appropriate or required to share assessment and review results with other organizations in accordance with any applicable rules, policies, or inter-organizational agreements or contracts.
","uuid":"1149a74c-19f3-4761-9201-060e5751a074","family":"Supply Chain Risk Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"df6ae9dd-b775-4d82-97ea-28860060d8a1","text":"frequency","parameterId":"sr-06_odp","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"SR-06","uuid":"e8e4540b-1738-4e78-ba40-1bf722651a66","test":"Determine if the supply chain-related risks associated with suppliers or contractors and the systems, system components, or system services they provide are assessed and reviewed [SELECTED PARAMETER VALUE(S): frequency ].Relationships between entities and procedures within the supply chain, including development and delivery, are considered. Supply chain elements include organizations, entities, or tools that are used for the research and development, design, manufacturing, acquisition, delivery, integration, operations, maintenance, and disposal of systems, system components, or system services. Supply chain processes include supply chain risk management programs; SCRM strategies and implementation plans; personnel and physical security programs; hardware, software, and firmware development processes; configuration management tools, techniques, and measures to maintain provenance; shipping and handling procedures; and programs, processes, or procedures associated with the production and distribution of supply chain elements. Supply chain actors are individuals with specific roles and responsibilities in the supply chain. The evidence generated and collected during analyses and testing of supply chain elements, processes, and actors is documented and used to inform organizational risk management activities and decisions.
","uuid":"e50e94ed-f61d-48df-ab5f-6c40d0ed9e7b","family":"Supply Chain Risk Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"5c055cfc-8ef5-42d0-b34f-45ec1d7043ac","text":"[Selection (one or more): organizational analysis; independent third-party analysis; organizational testing; independent third-party testing]","parameterId":"sr-06.01_odp.01","default":"[Selection (one or more): organizational analysis; independent third-party analysis; organizational testing; independent third-party testing]"},{"constraints":"","displayName":"","guidance":"","uuid":"4a163016-1f78-4b15-87c4-2058cc5a98da","text":"supply chain elements, processes, and actors","parameterId":"sr-06.01_odp.02","default":" [Assignment: organization defined supply chain elements, processes, and actors] "}],"subControls":"","tests":[{"testId":"SR-06(01)","uuid":"71b0200c-466c-43da-85f9-d3a4584328ad","test":"Determine if [SELECTED PARAMETER VALUE(S): [Selection (one or more): organizational analysis; independent third-party analysis; organizational testing; independent third-party testing] ] is/are employed on [SELECTED PARAMETER VALUE(S): supply chain elements, processes, and actors ] associated with the system, system component, or system service.Supply chain OPSEC expands the scope of OPSEC to include suppliers and potential suppliers. OPSEC is a process that includes identifying critical information, analyzing friendly actions related to operations and other activities to identify actions that can be observed by potential adversaries, determining indicators that potential adversaries might obtain that could be interpreted or pieced together to derive information in sufficient time to cause harm to organizations, implementing safeguards or countermeasures to eliminate or reduce exploitable vulnerabilities and risk to an acceptable level, and considering how aggregated information may expose users or specific uses of the supply chain. Supply chain information includes user identities; uses for systems, system components, and system services; supplier identities; security and privacy requirements; system and component configurations; supplier processes; design specifications; and testing and evaluation results. Supply chain OPSEC may require organizations to withhold mission or business information from suppliers and may include the use of intermediaries to hide the end use or users of systems, system components, or system services.
","uuid":"0088a61d-c12f-4f04-97d9-602ef71f5f7b","family":"Supply Chain Risk Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"e6f5886e-f1d3-41fb-a696-07a0b7a54a8b","text":"OPSEC controls","parameterId":"sr-07_odp","default":" [Assignment: organization defined OPSEC controls] "}],"subControls":"","tests":[{"testId":"SR-07","uuid":"8a9676f2-c95f-4206-b9c4-2d71f1379503","test":"Determine if [SELECTED PARAMETER VALUE(S): OPSEC controls ] are employed to protect supply chain-related information for the system, system component, or system service.The establishment of agreements and procedures facilitates communications among supply chain entities. Early notification of compromises and potential compromises in the supply chain that can potentially adversely affect or have adversely affected organizational systems or system components is essential for organizations to effectively respond to such incidents. The results of assessments or audits may include open-source information that contributed to a decision or result and could be used to help the supply chain entity resolve a concern or improve its processes.
","uuid":"fabb47f2-2d26-4c24-a7d1-436e3808810b","family":"Supply Chain Risk Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"f89f75a7-543e-45e3-bf1a-63830e6a2dbd","text":"[Selection (one or more): notification of supply chain compromises; [(NESTED PARAMETER) Assignment for sr-08_odp.02: results of assessments or audits]]","parameterId":"sr-08_odp.01","default":"[Selection (one or more): notification of supply chain compromises; [(NESTED PARAMETER) Assignment for sr-08_odp.02: results of assessments or audits]]"},{"constraints":"","displayName":"","guidance":"","uuid":"d8f444a7-0af4-42fa-bd31-65cbf763617b","text":"results of assessments or audits","parameterId":"sr-08_odp.02","default":" [Assignment: organization defined results of assessments or audits] "}],"subControls":"","tests":[{"testId":"SR-08","uuid":"8ef0b277-7353-492a-98f1-d43a66916e8e","test":"Determine if agreements and procedures are established with entities involved in the supply chain for the system, system components, or system service for [SELECTED PARAMETER VALUE(S): [Selection (one or more): notification of supply chain compromises; [(NESTED PARAMETER) Assignment for sr-08_odp.02: results of assessments or audits]] ].Anti-tamper technologies, tools, and techniques provide a level of protection for systems, system components, and services against many threats, including reverse engineering, modification, and substitution. Strong identification combined with tamper resistance and/or tamper detection is essential to protecting systems and components during distribution and when in use.
","uuid":"32695d95-e5ec-4932-98ca-db16eb4e2f04","family":"Supply Chain Risk Management","parameters":[],"subControls":"","tests":[{"testId":"SR-09","uuid":"c9909574-fe53-4951-b43c-11fd43c28147","test":"Determine if a tamper protection program is implemented for the system, system component, or system service.The system development life cycle includes research and development, design, manufacturing, acquisition, delivery, integration, operations and maintenance, and disposal. Organizations use a combination of hardware and software techniques for tamper resistance and detection. Organizations use obfuscation and self-checking to make reverse engineering and modifications more difficult, time-consuming, and expensive for adversaries. The customization of systems and system components can make substitutions easier to detect and therefore limit damage.
","uuid":"0da46c61-1862-4da7-bca9-1285fbd0b2d9","family":"Supply Chain Risk Management","parameters":[],"subControls":"","tests":[{"testId":"SR-09(01)","uuid":"d73c7c5b-3af9-4210-b6b8-7562a4377643","test":"Determine if anti-tamper technologies, tools, and techniques are employed throughout the system development life cycle.The inspection of systems or systems components for tamper resistance and detection addresses physical and logical tampering and is applied to systems and system components removed from organization-controlled areas. Indications of a need for inspection include changes in packaging, specifications, factory location, or entity in which the part is purchased, and when individuals return from travel to high-risk locations.
","uuid":"c0639fe5-613f-4076-aad7-c832c9a699af","family":"Supply Chain Risk Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"8601cb38-e79d-4eac-b5cf-a59ed57e2e7b","text":"systems or system components","parameterId":"sr-10_odp.01","default":" [Assignment: organization defined systems or system components] "},{"constraints":"","displayName":"","guidance":"","uuid":"2f550b53-bf01-4803-b219-bde11b430770","text":"[Selection (one or more): at random; at [(NESTED PARAMETER) Assignment for sr-10_odp.03: frequency]; upon [(NESTED PARAMETER) Assignment for sr-10_odp.04: indications of need for inspection]]","parameterId":"sr-10_odp.02","default":"[Selection (one or more): at random; at [(NESTED PARAMETER) Assignment for sr-10_odp.03: frequency]; upon [(NESTED PARAMETER) Assignment for sr-10_odp.04: indications of need for inspection]]"},{"constraints":"","displayName":"","guidance":"","uuid":"05b0a044-63a0-46e6-9152-05e15044e732","text":"frequency","parameterId":"sr-10_odp.03","default":" [Assignment: organization defined frequency] "},{"constraints":"","displayName":"","guidance":"","uuid":"66d9b55f-67e5-4491-b26b-100fa1b242c3","text":"indications of need for inspection","parameterId":"sr-10_odp.04","default":" [Assignment: organization defined indications of need for inspection] "}],"subControls":"","tests":[{"testId":"SR-10","uuid":"505c9a91-1da3-413f-acd6-d646f5400391","test":"Determine if [SELECTED PARAMETER VALUE(S): systems or system components ] are inspected [SELECTED PARAMETER VALUE(S): [Selection (one or more): at random; at [(NESTED PARAMETER) Assignment for sr-10_odp.03: frequency]; upon [(NESTED PARAMETER) Assignment for sr-10_odp.04: indications of need for inspection]] ] to detect tampering.Sources of counterfeit components include manufacturers, developers, vendors, and contractors. Anti-counterfeiting policies and procedures support tamper resistance and provide a level of protection against the introduction of malicious code. External reporting organizations include CISA.
","uuid":"a8a0c696-6025-4439-a5d3-c47271afe21d","family":"Supply Chain Risk Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"3dd65503-ed28-423e-a757-1ddff3b3ba5e","text":"[Selection (one or more): source of counterfeit component; [(NESTED PARAMETER) Assignment for sr-11_odp.02: external reporting organizations]; [(NESTED PARAMETER) Assignment for sr-11_odp.03: personnel or roles]]","parameterId":"sr-11_odp.01","default":"[Selection (one or more): source of counterfeit component; [(NESTED PARAMETER) Assignment for sr-11_odp.02: external reporting organizations]; [(NESTED PARAMETER) Assignment for sr-11_odp.03: personnel or roles]]"},{"constraints":"","displayName":"","guidance":"","uuid":"f1824cac-e46c-4bd6-936e-2087323eeb6f","text":"external reporting organizations","parameterId":"sr-11_odp.02","default":" [Assignment: organization defined external reporting organizations] "},{"constraints":"","displayName":"","guidance":"","uuid":"b9ad3831-b50c-413c-ac48-176cb815317e","text":"personnel or roles","parameterId":"sr-11_odp.03","default":" [Assignment: organization defined personnel or roles] "}],"subControls":"","tests":[{"testId":"SR-11a.[01]","uuid":"54e09c69-b3ba-4a03-b502-b3ed6093be69","test":"Determine if an anti-counterfeit policy is developed and implemented;None.
","uuid":"226b9b7e-1979-45c6-b1a1-2df5444df5bc","family":"Supply Chain Risk Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"d5d43311-1a3a-4bba-a095-df639ae4afed","text":"personnel or roles","parameterId":"sr-11.01_odp","default":" [Assignment: organization defined personnel or roles] "}],"subControls":"","tests":[{"testId":"SR-11(01)","uuid":"026b1897-2add-4e33-8a7c-97735f408e34","test":"Determine if [SELECTED PARAMETER VALUE(S): personnel or roles ] are trained to detect counterfeit system components (including hardware, software, and firmware).None.
","uuid":"ba61e2e8-716b-4e81-9be9-7200727b5aa5","family":"Supply Chain Risk Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"425b9e4d-eadb-415b-9854-972ed1a196d0","text":"system components","parameterId":"sr-11.02_odp","default":" [Assignment: organization defined system components] "}],"subControls":"","tests":[{"testId":"SR-11(02)[01]","uuid":"1ca17464-d4ed-48e4-bc85-001570b61fc8","test":"Determine if configuration control over [SELECTED PARAMETER VALUE(S): system components ] awaiting service or repair is maintained;The type of component determines the type of scanning to be conducted (e.g., web application scanning if the component is a web application).
","uuid":"f17343a0-6405-4faf-9de6-060ad9662792","family":"Supply Chain Risk Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"3261a85c-8d1e-42e4-b928-acb06c6e943e","text":"frequency","parameterId":"sr-11.03_odp","default":" [Assignment: organization defined frequency] "}],"subControls":"","tests":[{"testId":"SR-11(03)","uuid":"efc98b03-3f03-4c48-a3dc-94d74d3c55a5","test":"Determine if scanning for counterfeit system components is conducted [SELECTED PARAMETER VALUE(S): frequency ].Data, documentation, tools, or system components can be disposed of at any time during the system development life cycle (not only in the disposal or retirement phase of the life cycle). For example, disposal can occur during research and development, design, prototyping, or operations/maintenance and include methods such as disk cleaning, removal of cryptographic keys, partial reuse of components. Opportunities for compromise during disposal affect physical and logical data, including system documentation in paper-based or digital files; shipping and delivery documentation; memory sticks with software code; or complete routers or servers that include permanent media, which contain sensitive or proprietary information. Additionally, proper disposal of system components helps to prevent such components from entering the gray market.
","uuid":"34c9e836-3ec1-4c44-96c8-9ea97e153e7d","family":"Supply Chain Risk Management","parameters":[{"constraints":"","displayName":"","guidance":"","uuid":"14bd5f1c-c174-46e3-bb99-6b37f666cdc0","text":"data, documentation, tools, or system components","parameterId":"sr-12_odp.01","default":" [Assignment: organization defined data, documentation, tools, or system components] "},{"constraints":"","displayName":"","guidance":"","uuid":"bce79e3b-d65d-4aaa-bd34-2cae16c52a24","text":"techniques and methods","parameterId":"sr-12_odp.02","default":" [Assignment: organization defined techniques and methods] "}],"subControls":"","tests":[{"testId":"SR-12","uuid":"d6c1da2a-4e9c-4bba-9bb2-2ec4dac5116c","test":"Determine if [SELECTED PARAMETER VALUE(S): data, documentation, tools, or system components ] are disposed of using [SELECTED PARAMETER VALUE(S): techniques and methods ].