+AC Access Control
---+AC-01 Policy and Procedures
---+AC-02 Account Management
------+AC-02(01) Automated System Account Management
------+AC-02(02) Automated Temporary and Emergency Account Management
------+AC-02(03) Disable Accounts
------+AC-02(04) Automated Audit Actions
------+AC-02(05) Inactivity Logout
------+AC-02(06) Dynamic Privilege Management
------+AC-02(07) Privileged User Accounts
------+AC-02(08) Dynamic Account Management
------+AC-02(09) Restrictions on Use of Shared and Group Accounts
------+AC-02(11) Usage Conditions
------+AC-02(12) Account Monitoring for Atypical Usage
------+AC-02(13) Disable Accounts for High-risk Individuals
---+AC-03 Access Enforcement
------+AC-03(02) Dual Authorization
------+AC-03(03) Mandatory Access Control
------+AC-03(04) Discretionary Access Control
------+AC-03(05) Security-relevant Information
------+AC-03(07) Role-based Access Control
------+AC-03(08) Revocation of Access Authorizations
------+AC-03(09) Controlled Release
------+AC-03(10) Audited Override of Access Control Mechanisms
------+AC-03(11) Restrict Access to Specific Information Types
------+AC-03(12) Assert and Enforce Application Access
------+AC-03(13) Attribute-based Access Control
------+AC-03(14) Individual Access
------+AC-03(15) Discretionary and Mandatory Access Control
---+AC-04 Information Flow Enforcement
------+AC-04(01) Object Security and Privacy Attributes
------+AC-04(02) Processing Domains
------+AC-04(03) Dynamic Information Flow Control
------+AC-04(04) Flow Control of Encrypted Information
------+AC-04(05) Embedded Data Types
------+AC-04(06) Metadata
------+AC-04(07) One-way Flow Mechanisms
------+AC-04(08) Security and Privacy Policy Filters
------+AC-04(09) Human Reviews
------+AC-04(10) Enable and Disable Security or Privacy Policy Filters
------+AC-04(11) Configuration of Security or Privacy Policy Filters
------+AC-04(12) Data Type Identifiers
------+AC-04(13) Decomposition into Policy-relevant Subcomponents
------+AC-04(14) Security or Privacy Policy Filter Constraints
------+AC-04(15) Detection of Unsanctioned Information
------+AC-04(17) Domain Authentication
------+AC-04(19) Validation of Metadata
------+AC-04(20) Approved Solutions
------+AC-04(21) Physical or Logical Separation of Information Flows
------+AC-04(22) Access Only
------+AC-04(23) Modify Non-releasable Information
------+AC-04(24) Internal Normalized Format
------+AC-04(25) Data Sanitization
------+AC-04(26) Audit Filtering Actions
------+AC-04(27) Redundant/Independent Filtering Mechanisms
------+AC-04(28) Linear Filter Pipelines
------+AC-04(29) Filter Orchestration Engines
------+AC-04(30) Filter Mechanisms Using Multiple Processes
------+AC-04(31) Failed Content Transfer Prevention
------+AC-04(32) Process Requirements for Information Transfer
---+AC-05 Separation of Duties
---+AC-06 Least Privilege
------+AC-06(01) Authorize Access to Security Functions
------+AC-06(02) Non-privileged Access for Nonsecurity Functions
------+AC-06(03) Network Access to Privileged Commands
------+AC-06(04) Separate Processing Domains
------+AC-06(05) Privileged Accounts
------+AC-06(06) Privileged Access by Non-organizational Users
------+AC-06(07) Review of User Privileges
------+AC-06(08) Privilege Levels for Code Execution
------+AC-06(09) Log Use of Privileged Functions
------+AC-06(10) Prohibit Non-privileged Users from Executing Privileged Functions
---+AC-07 Unsuccessful Logon Attempts
------+AC-07(02) Purge or Wipe Mobile Device
------+AC-07(03) Biometric Attempt Limiting
------+AC-07(04) Use of Alternate Authentication Factor
---+AC-08 System Use Notification
---+AC-09 Previous Logon Notification
------+AC-09(01) Unsuccessful Logons
------+AC-09(02) Successful and Unsuccessful Logons
------+AC-09(03) Notification of Account Changes
------+AC-09(04) Additional Logon Information
---+AC-10 Concurrent Session Control
---+AC-11 Device Lock
------+AC-11(01) Pattern-hiding Displays
---+AC-12 Session Termination
------+AC-12(01) User-initiated Logouts
------+AC-12(02) Termination Message
------+AC-12(03) Timeout Warning Message
---+AC-13 Supervision and Review — Access Control
---+AC-14 Permitted Actions Without Identification or Authentication
---+AC-15 Automated Marking
---+AC-16 Security and Privacy Attributes
------+AC-16(01) Dynamic Attribute Association
------+AC-16(02) Attribute Value Changes by Authorized Individuals
------+AC-16(03) Maintenance of Attribute Associations by System
------+AC-16(04) Association of Attributes by Authorized Individuals
------+AC-16(05) Attribute Displays on Objects to Be Output
------+AC-16(06) Maintenance of Attribute Association
------+AC-16(07) Consistent Attribute Interpretation
------+AC-16(08) Association Techniques and Technologies
------+AC-16(09) Attribute Reassignment — Regrading Mechanisms
------+AC-16(10) Attribute Configuration by Authorized Individuals
---+AC-17 Remote Access
------+AC-17(01) Monitoring and Control
------+AC-17(02) Protection of Confidentiality and Integrity Using Encryption
------+AC-17(03) Managed Access Control Points
------+AC-17(04) Privileged Commands and Access
------+AC-17(06) Protection of Mechanism Information
------+AC-17(09) Disconnect or Disable Access
------+AC-17(10) Authenticate Remote Commands
---+AC-18 Wireless Access
------+AC-18(01) Authentication and Encryption
------+AC-18(03) Disable Wireless Networking
------+AC-18(04) Restrict Configurations by Users
------+AC-18(05) Antennas and Transmission Power Levels
---+AC-19 Access Control for Mobile Devices
------+AC-19(04) Restrictions for Classified Information
------+AC-19(05) Full Device or Container-based Encryption
---+AC-20 Use of External Systems
------+AC-20(01) Limits on Authorized Use
------+AC-20(02) Portable Storage Devices — Restricted Use
------+AC-20(03) Non-organizationally Owned Systems — Restricted Use
------+AC-20(04) Network Accessible Storage Devices — Prohibited Use
------+AC-20(05) Portable Storage Devices — Prohibited Use
---+AC-21 Information Sharing
------+AC-21(01) Automated Decision Support
------+AC-21(02) Information Search and Retrieval
---+AC-22 Publicly Accessible Content
---+AC-23 Data Mining Protection
---+AC-24 Access Control Decisions
------+AC-24(01) Transmit Access Authorization Information
------+AC-24(02) No User or Process Identity
---+AC-25 Reference Monitor

AC Access Control

Access Control

1. Yleiskatsaus

Otsikko Standardi
AC-01 Policy and Procedures

Control

  1. Develop, document, and disseminate to [Assignement: organization-defined personnel or roles]:
    1. [Selection(one-or-more): organization-level; mission/business process-level; system-level] access control policy that:
      1. Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
      2. Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
    2. Procedures to facilitate the implementation of the access control policy and the associated access controls;
  2. Designate an [Assignement: official] to manage the development, documentation, and dissemination of the access control policy and procedures; and
  3. Review and update the current access control:
    1. Policy [Assignement: frequency] and following [Assignement: events] ; and
    2. Procedures [Assignement: frequency] and following [Assignement: events].

Discussion

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.

Assessment Objective

    1. an access control policy is developed and documented;
    2. the access control policy is disseminated to [Assignement: personnel or roles];
    3. access control procedures to facilitate the implementation of the access control policy and associated controls are developed and documented;
    4. the access control procedures are disseminated to [Assignement: personnel or roles];
        1. the [Selection(one-or-more): organization-level; mission/business process-level; system-level] access control policy addresses purpose;
        2. the [Selection(one-or-more): organization-level; mission/business process-level; system-level] access control policy addresses scope;
        3. the [Selection(one-or-more): organization-level; mission/business process-level; system-level] access control policy addresses roles;
        4. the [Selection(one-or-more): organization-level; mission/business process-level; system-level] access control policy addresses responsibilities;
        5. the [Selection(one-or-more): organization-level; mission/business process-level; system-level] access control policy addresses management commitment;
        6. the [Selection(one-or-more): organization-level; mission/business process-level; system-level] access control policy addresses coordination among organizational entities;
        7. the [Selection(one-or-more): organization-level; mission/business process-level; system-level] access control policy addresses compliance;
      1. the [Selection(one-or-more): organization-level; mission/business process-level; system-level] access control policy is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines;
  1. the [Assignement: official] is designated to manage the development, documentation, and dissemination of the access control policy and procedures;
      1. the current access control policy is reviewed and updated [Assignement: frequency];
      2. the current access control policy is reviewed and updated following [Assignement: events];
      1. the current access control procedures are reviewed and updated [Assignement: frequency];
      2. the current access control procedures are reviewed and updated following [Assignement: events].

Assessment Method

Examine

Access control policy and procedures system security plan privacy plan other relevant documents or records

Interview

Organizational personnel with access control responsibilities organizational personnel with information security with information security and privacy responsibilities
AC-02 Account Management

Control

  1. Define and document the types of accounts allowed and specifically prohibited for use within the system;
  2. Assign account managers;
  3. Require [Assignement: prerequisites and criteria] for group and role membership;
  4. Specify:
    1. Authorized users of the system;
    2. Group and role membership; and
    3. Access authorizations (i.e., privileges) and [Assignement: attributes (as required)] for each account;
  5. Require approvals by [Assignement: personnel or roles] for requests to create accounts;
  6. Create, enable, modify, disable, and remove accounts in accordance with [Assignement: policy, procedures, prerequisites, and criteria];
  7. Monitor the use of accounts;
  8. Notify account managers and [Assignement: personnel or roles] within:
    1. [Assignement: time period] when accounts are no longer required;
    2. [Assignement: time period] when users are terminated or transferred; and
    3. [Assignement: time period] when system usage or need-to-know changes for an individual;
  9. Authorize access to the system based on:
    1. A valid access authorization;
    2. Intended system usage; and
    3. [Assignement: attributes (as required)];
  10. Review accounts for compliance with account management requirements [Assignement: frequency];
  11. Establish and implement a process for changing shared or group account authenticators (if deployed) when individuals are removed from the group; and
  12. Align account management processes with personnel termination and transfer processes.

Discussion

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.

Assessment Objective

    1. account types allowed for use within the system are defined and documented;
    2. account types specifically prohibited for use within the system are defined and documented;
  1. account managers are assigned;
  2. [Assignement: prerequisites and criteria] for group and role membership are required;
    1. authorized users of the system are specified;
    2. group and role membership are specified;
      1. access authorizations (i.e., privileges) are specified for each account;
      2. [Assignement: attributes (as required)] are specified for each account;
  3. approvals are required by [Assignement: personnel or roles] for requests to create accounts;
    1. accounts are created in accordance with [Assignement: policy, procedures, prerequisites, and criteria];
    2. accounts are enabled in accordance with [Assignement: policy, procedures, prerequisites, and criteria];
    3. accounts are modified in accordance with [Assignement: policy, procedures, prerequisites, and criteria];
    4. accounts are disabled in accordance with [Assignement: policy, procedures, prerequisites, and criteria];
    5. accounts are removed in accordance with [Assignement: policy, procedures, prerequisites, and criteria];
  4. the use of accounts is monitored;
    1. account managers and [Assignement: personnel or roles] are notified within [Assignement: time period] when accounts are no longer required;
    2. account managers and [Assignement: personnel or roles] are notified within [Assignement: time period] when users are terminated or transferred;
    3. account managers and [Assignement: personnel or roles] are notified within [Assignement: time period] when system usage or the need to know changes for an individual;
    1. access to the system is authorized based on a valid access authorization;
    2. access to the system is authorized based on intended system usage;
    3. access to the system is authorized based on [Assignement: attributes (as required)];
  5. accounts are reviewed for compliance with account management requirements [Assignement: frequency];
    1. a process is established for changing shared or group account authenticators (if deployed) when individuals are removed from the group;
    2. a process is implemented for changing shared or group account authenticators (if deployed) when individuals are removed from the group;
    1. account management processes are aligned with personnel termination processes;
    2. account management processes are aligned with personnel transfer processes.

Assessment Method

Examine

Access control policy personnel termination policy and procedure personnel transfer policy and procedure procedures for addressing account management system design documentation system configuration settings and associated documentation list of active system accounts along with the name of the individual associated with each account list of recently disabled system accounts and the name of the individual associated with each account list of conditions for group and role membership notifications of recent transfers, separations, or terminations of employees access authorization records account management compliance reviews system monitoring records system audit records system security plan privacy plan other relevant documents or records

Interview

Organizational personnel with account management responsibilities system/network administrators organizational personnel with information security with information security and privacy responsibilities
AC-03 Access Enforcement

Control

Enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.

Discussion

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](#pe) ) family.

Assessment Objective

approved authorizations for logical access to information and system resources are enforced in accordance with applicable access control policies.

Assessment Method

Examine

Access control policy procedures addressing access enforcement system design documentation system configuration settings and associated documentation list of approved authorizations (user privileges) system audit records system security plan privacy plan other relevant documents or records

Interview

Organizational personnel with access enforcement responsibilities system/network administrators organizational personnel with information security and privacy responsibilities system developers
AC-04 Information Flow Enforcement

Control

Enforce approved authorizations for controlling the flow of information within the system and between connected systems based on [Assignement: information flow control policies].

Discussion

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](#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).

Assessment Objective

approved authorizations are enforced for controlling the flow of information within the system and between connected systems based on [Assignement: information flow control policies].

Assessment Method

Examine

Access control policy information flow control policies procedures addressing information flow enforcement security architecture documentation privacy architecture documentation system design documentation system configuration settings and associated documentation system baseline configuration list of information flow authorizations system audit records system security plan privacy plan other relevant documents or records

Interview

System/network administrators organizational personnel with information security and privacy architecture development responsibilities organizational personnel with information security and privacy responsibilities system developers
AC-05 Separation of Duties

Control

  1. Identify and document [Assignement: duties of individuals] ; and
  2. Define system access authorizations to support separation of duties.

Discussion

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](#ac-2) , access control mechanisms in [AC-3](#ac-3) , and identity management activities in [IA-2](#ia-2), [IA-4](#ia-4) , and [IA-12](#ia-12).

Assessment Objective

  1. [Assignement: duties of individuals] are identified and documented;
  2. system access authorizations to support separation of duties are defined.

Assessment Method

Examine

Access control policy procedures addressing divisions of responsibility and separation of duties system configuration settings and associated documentation list of divisions of responsibility and separation of duties system access authorizations system audit records system security plan other relevant documents or records

Interview

Organizational personnel with responsibilities for defining appropriate divisions of responsibility and separation of duties organizational personnel with information security responsibilities system/network administrators
AC-06 Least Privilege

Control

Employ the principle of least privilege, allowing only authorized accesses for users (or processes acting on behalf of users) that are necessary to accomplish assigned organizational tasks.

Discussion

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.

Assessment Objective

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.

Assessment Method

Examine

Access control policy procedures addressing least privilege list of assigned access authorizations (user privileges) system configuration settings and associated documentation system audit records system security plan other relevant documents or records

Interview

Organizational personnel with responsibilities for defining least privileges necessary to accomplish specified tasks organizational personnel with information security responsibilities system/network administrators
AC-07 Unsuccessful Logon Attempts

Control

  1. Enforce a limit of [Assignement: number] consecutive invalid logon attempts by a user during a [Assignement: time period] ; and
  2. Automatically [Selection(one-or-more): lock the account or node for {{ insert: param, ac-07_odp.04 }} ; lock the account or node until released by an administrator; delay next logon prompt per {{ insert: param, ac-07_odp.05 }} ; notify system administrator; take other {{ insert: param, ac-07_odp.06 }} ] when the maximum number of unsuccessful attempts is exceeded.

Discussion

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.

Assessment Objective

  1. a limit of [Assignement: number] consecutive invalid logon attempts by a user during [Assignement: time period] is enforced;
  2. automatically [Selection(one-or-more): lock the account or node for {{ insert: param, ac-07_odp.04 }} ; lock the account or node until released by an administrator; delay next logon prompt per {{ insert: param, ac-07_odp.05 }} ; notify system administrator; take other {{ insert: param, ac-07_odp.06 }} ] when the maximum number of unsuccessful attempts is exceeded.

Assessment Method

Examine

Access control policy procedures addressing unsuccessful logon attempts system design documentation system configuration settings and associated documentation system audit records system security plan other relevant documents or records

Interview

Organizational personnel with information security responsibilities system developers system/network administrators
AC-08 System Use Notification

Control

  1. Display [Assignement: system use notification] to users before granting access to the system that provides privacy and security notices consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines and state that:
    1. Users are accessing a U.S. Government system;
    2. System usage may be monitored, recorded, and subject to audit;
    3. Unauthorized use of the system is prohibited and subject to criminal and civil penalties; and
    4. Use of the system indicates consent to monitoring and recording;
  2. Retain the notification message or banner on the screen until users acknowledge the usage conditions and take explicit actions to log on to or further access the system; and
  3. For publicly accessible systems:
    1. Display system use information [Assignement: conditions] , before granting further access to the publicly accessible system;
    2. Display references, if any, to monitoring, recording, or auditing that are consistent with privacy accommodations for such systems that generally prohibit those activities; and
    3. Include a description of the authorized uses of the system.

Discussion

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.

Assessment Objective

  1. [Assignement: 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;
    1. the system use notification states that users are accessing a U.S. Government system;
    2. the system use notification states that system usage may be monitored, recorded, and subject to audit;
    3. the system use notification states that unauthorized use of the system is prohibited and subject to criminal and civil penalties; and
    4. the system use notification states that use of the system indicates consent to monitoring and recording;
  2. the notification message or banner is retained on the screen until users acknowledge the usage conditions and take explicit actions to log on to or further access the system;
    1. for publicly accessible systems, system use information [Assignement: conditions] is displayed before granting further access to the publicly accessible system;
    2. for publicly accessible systems, any references to monitoring, recording, or auditing that are consistent with privacy accommodations for such systems that generally prohibit those activities are displayed;
    3. for publicly accessible systems, a description of the authorized uses of the system is included.

Assessment Method

Examine

Access control policy privacy and security policies, procedures addressing system use notification documented approval of system use notification messages or banners system audit records user acknowledgements of notification message or banner system design documentation system configuration settings and associated documentation system use notification messages system security plan privacy plan privacy impact assessment privacy assessment report other relevant documents or records

Interview

System/network administrators organizational personnel with information security and privacy responsibilities legal counsel system developers
AC-09 Previous Logon Notification

Control

Notify the user, upon successful logon to the system, of the date and time of the last logon.

Discussion

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.

Assessment Objective

the user is notified, upon successful logon to the system, of the date and time of the last logon.

Assessment Method

Examine

Access control policy procedures addressing previous logon notification system design documentation system configuration settings and associated documentation system notification messages system security plan other relevant documents or records

Interview

System/network administrators organizational personnel with information security responsibilities system developers
AC-10 Concurrent Session Control

Control

Limit the number of concurrent sessions for each [Assignement: account and/or account types] to [Assignement: number].

Discussion

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.

Assessment Objective

the number of concurrent sessions for each [Assignement: account and/or account types] is limited to [Assignement: number].

Assessment Method

Examine

Access control policy procedures addressing concurrent session control system design documentation system configuration settings and associated documentation security plan system security plan other relevant documents or records

Interview

System/network administrators organizational personnel with information security responsibilities system developers
AC-11 Device Lock

Control

  1. Prevent further access to the system by [Selection(one-or-more): initiating a device lock after {{ insert: param, ac-11_odp.02 }} of inactivity; requiring the user to initiate a device lock before leaving the system unattended] ; and
  2. Retain the device lock until the user reestablishes access using established identification and authentication procedures.

Discussion

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.

Assessment Objective

  1. further access to the system is prevented by [Selection(one-or-more): initiating a device lock after {{ insert: param, ac-11_odp.02 }} of inactivity; requiring the user to initiate a device lock before leaving the system unattended];
  2. device lock is retained until the user re-establishes access using established identification and authentication procedures.

Assessment Method

Examine

Access control policy procedures addressing session lock procedures addressing identification and authentication system design documentation system configuration settings and associated documentation security plan system security plan other relevant documents or records

Interview

System/network administrators organizational personnel with information security responsibilities system developers
AC-12 Session Termination

Control

Automatically terminate a user session after [Assignement: conditions or trigger events].

Discussion

Session termination addresses the termination of user-initiated logical sessions (in contrast to [SC-10](#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.

Assessment Objective

a user session is automatically terminated after [Assignement: conditions or trigger events].

Assessment Method

Examine

Access control policy procedures addressing session termination system design documentation system configuration settings and associated documentation list of conditions or trigger events requiring session disconnect system audit records system security plan other relevant documents or records

Interview

System/network administrators organizational personnel with information security responsibilities system developers
AC-13 Supervision and Review — Access Control

Control

Discussion

Assessment Objective

Assessment Method

Examine

Interview

AC-14 Permitted Actions Without Identification or Authentication

Control

  1. Identify [Assignement: user actions] that can be performed on the system without identification or authentication consistent with organizational mission and business functions; and
  2. Document and provide supporting rationale in the security plan for the system, user actions not requiring identification or authentication.

Discussion

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."

Assessment Objective

  1. [Assignement: user actions] that can be performed on the system without identification or authentication consistent with organizational mission and business functions are identified;
    1. user actions not requiring identification or authentication are documented in the security plan for the system;
    2. a rationale for user actions not requiring identification or authentication is provided in the security plan for the system.

Assessment Method

Examine

Access control policy procedures addressing permitted actions without identification or authentication system configuration settings and associated documentation security plan list of user actions that can be performed without identification or authentication system audit records system security plan other relevant documents or records

Interview

System/network administrators organizational personnel with information security responsibilities
AC-15 Automated Marking

Control

Discussion

Assessment Objective

Assessment Method

Examine

Interview

AC-16 Security and Privacy Attributes

Control

  1. Provide the means to associate [Assignement: organization-defined types of security and privacy attributes] with [Assignement: organization-defined security and privacy attribute values] for information in storage, in process, and/or in transmission;
  2. Ensure that the attribute associations are made and retained with the information;
  3. Establish the following permitted security and privacy attributes from the attributes defined in [AC-16a](#ac-16_smt.a) for [Assignement: organization-defined systems]: [Assignement: organization-defined security and privacy attributes];
  4. Determine the following permitted attribute values or ranges for each of the established attributes: [Assignement: attribute values or ranges];
  5. Audit changes to attributes; and
  6. Review [Assignement: organization-defined security and privacy attributes] for applicability [Assignement: organization-defined frequency].

Discussion

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](#mp-3) (Media Marking).

Assessment Objective

    1. the means to associate [Assignement: types of security attributes] with [Assignement: security attribute values] for information in storage, in process, and/or in transmission are provided;
    2. the means to associate [Assignement: types of privacy attributes] with [Assignement: privacy attribute values] for information in storage, in process, and/or in transmission are provided;
    1. attribute associations are made;
    2. attribute associations are retained with the information;
    1. the following permitted security attributes are established from the attributes defined in AC-16_ODP[01] for [Assignement: systems]: [Assignement: security attributes];
    2. the following permitted privacy attributes are established from the attributes defined in AC-16_ODP[02] for [Assignement: systems]: [Assignement: privacy attributes];
  1. the following permitted attribute values or ranges for each of the established attributes are determined: [Assignement: attribute values or ranges];
  2. changes to attributes are audited;
    1. [Assignement: security attributes] are reviewed for applicability [Assignement: frequency];
    2. [Assignement: privacy attributes] are reviewed for applicability [Assignement: frequency].

Assessment Method

Examine

Access control policy procedures addressing the association of security and privacy attributes to information in storage, in process, and in transmission system design documentation system configuration settings and associated documentation system audit records system security plan privacy plan other relevant documents or records

Interview

System/network administrators organizational personnel with information security and privacy responsibilities system developers
AC-17 Remote Access

Control

  1. Establish and document usage restrictions, configuration/connection requirements, and implementation guidance for each type of remote access allowed; and
  2. Authorize each type of remote access to the system prior to allowing such connections.

Discussion

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](#ca-3) . Enforcing access restrictions for remote access is addressed via [AC-3](#ac-3).

Assessment Objective

    1. usage restrictions are established and documented for each type of remote access allowed;
    2. configuration/connection requirements are established and documented for each type of remote access allowed;
    3. implementation guidance is established and documented for each type of remote access allowed;
  1. each type of remote access to the system is authorized prior to allowing such connections.

Assessment Method

Examine

Access control policy procedures addressing remote access implementation and usage (including restrictions) configuration management plan system configuration settings and associated documentation remote access authorizations system audit records system security plan other relevant documents or records

Interview

Organizational personnel with responsibilities for managing remote access connections system/network administrators organizational personnel with information security responsibilities
AC-18 Wireless Access

Control

  1. Establish configuration requirements, connection requirements, and implementation guidance for each type of wireless access; and
  2. Authorize each type of wireless access to the system prior to allowing such connections.

Discussion

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.

Assessment Objective

    1. configuration requirements are established for each type of wireless access;
    2. connection requirements are established for each type of wireless access;
    3. implementation guidance is established for each type of wireless access;
  1. each type of wireless access to the system is authorized prior to allowing such connections.

Assessment Method

Examine

Access control policy procedures addressing wireless access implementation and usage (including restrictions) configuration management plan system design documentation system configuration settings and associated documentation wireless access authorizations system audit records system security plan other relevant documents or records

Interview

Organizational personnel with responsibilities for managing wireless access connections organizational personnel with information security responsibilities
AC-19 Access Control for Mobile Devices

Control

  1. Establish configuration requirements, connection requirements, and implementation guidance for organization-controlled mobile devices, to include when such devices are outside of controlled areas; and
  2. Authorize the connection of mobile devices to organizational systems.

Discussion

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](#ac-19) . Many safeguards for mobile devices are reflected in other controls. [AC-20](#ac-20) addresses mobile devices that are not organization-controlled.

Assessment Objective

    1. configuration requirements are established for organization-controlled mobile devices, including when such devices are outside of the controlled area;
    2. connection requirements are established for organization-controlled mobile devices, including when such devices are outside of the controlled area;
    3. implementation guidance is established for organization-controlled mobile devices, including when such devices are outside of the controlled area;
  1. the connection of mobile devices to organizational systems is authorized.

Assessment Method

Examine

Access control policy procedures addressing access control for mobile device usage (including restrictions) configuration management plan system design documentation system configuration settings and associated documentation authorizations for mobile device connections to organizational systems system audit records system security plan other relevant documents or records

Interview

Organizational personnel using mobile devices to access organizational systems system/network administrators organizational personnel with information security responsibilities
AC-20 Use of External Systems

Control

  1. [Selection(one-or-more): establish {{ insert: param, ac-20_odp.02 }} ; identify {{ insert: param, ac-20_odp.03 }} ] , consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems, allowing authorized individuals to:
    1. Access the system from external systems; and
    2. Process, store, or transmit organization-controlled information using external systems; or
  2. Prohibit the use of [Assignement: prohibited types of external systems].

Discussion

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](#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.

Assessment Objective

    1. [Selection(one-or-more): establish {{ insert: param, ac-20_odp.02 }} ; identify {{ insert: param, ac-20_odp.03 }} ] 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);
    2. [Selection(one-or-more): establish {{ insert: param, ac-20_odp.02 }} ; identify {{ insert: param, ac-20_odp.03 }} ] is/are consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems, allowing authorized individuals to process, store, or transmit organization-controlled information using external systems (if applicable);
  1. the use of [Assignement: prohibited types of external systems] is prohibited (if applicable).

Assessment Method

Examine

Access control policy procedures addressing the use of external systems external systems terms and conditions list of types of applications accessible from external systems maximum security categorization for information processed, stored, or transmitted on external systems system configuration settings and associated documentation system security plan other relevant documents or records

Interview

Organizational personnel with responsibilities for defining terms and conditions for use of external systems to access organizational systems system/network administrators organizational personnel with information security responsibilities
AC-21 Information Sharing

Control

  1. Enable authorized users to determine whether access authorizations assigned to a sharing partner match the information’s access and use restrictions for [Assignement: information-sharing circumstances] ; and
  2. Employ [Assignement: automated mechanisms] to assist users in making information sharing and collaboration decisions.

Discussion

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.

Assessment Objective

  1. authorized users are enabled to determine whether access authorizations assigned to a sharing partner match the information’s access and use restrictions for [Assignement: information-sharing circumstances];
  2. [Assignement: automated mechanisms] are employed to assist users in making information-sharing and collaboration decisions.

Assessment Method

Examine

Access control policy procedures addressing user-based collaboration and information sharing (including restrictions) system design documentation system configuration settings and associated documentation list of users authorized to make information-sharing/collaboration decisions list of information-sharing circumstances requiring user discretion non-disclosure agreements acquisitions/contractual agreements system security plan privacy plan privacy impact assessment security and privacy risk assessments other relevant documents or records

Interview

Organizational personnel responsible for information-sharing/collaboration decisions organizational personnel with responsibility for acquisitions/contractual agreements system/network administrators organizational personnel with information security and privacy responsibilities
AC-22 Publicly Accessible Content

Control

  1. Designate individuals authorized to make information publicly accessible;
  2. Train authorized individuals to ensure that publicly accessible information does not contain nonpublic information;
  3. Review the proposed content of information prior to posting onto the publicly accessible system to ensure that nonpublic information is not included; and
  4. Review the content on the publicly accessible system for nonpublic information [Assignement: frequency] and remove such information, if discovered.

Discussion

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](#18e71fec-c6fd-475a-925a-5d8495cf8455) 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.

Assessment Objective

  1. designated individuals are authorized to make information publicly accessible;
  2. authorized individuals are trained to ensure that publicly accessible information does not contain non-public information;
  3. the proposed content of information is reviewed prior to posting onto the publicly accessible system to ensure that non-public information is not included;
    1. the content on the publicly accessible system is reviewed for non-public information [Assignement: frequency];
    2. non-public information is removed from the publicly accessible system, if discovered.

Assessment Method

Examine

Access control policy procedures addressing publicly accessible content list of users authorized to post publicly accessible content on organizational systems training materials and/or records records of publicly accessible information reviews records of response to non-public information on public websites system audit logs security awareness training records system security plan other relevant documents or records

Interview

Organizational personnel with responsibilities for managing publicly accessible information posted on organizational systems organizational personnel with information security responsibilities
AC-23 Data Mining Protection

Control

Employ [Assignement: techniques] for [Assignement: data storage objects] to detect and protect against unauthorized data mining.

Discussion

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](#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](#0af071a6-cf8e-48ee-8c82-fe91efa20f94) 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.

Assessment Objective

[Assignement: techniques] are employed for [Assignement: data storage objects] to detect and protect against unauthorized data mining.

Assessment Method

Examine

Access control policy procedures for preventing and detecting data mining policies and procedures addressing authorized data mining techniques procedures addressing protection of data storage objects against data mining system design documentation system configuration settings and associated documentation system audit logs system audit records procedures addressing differential privacy techniques notifications of atypical database queries or accesses documentation or reports of insider threat program system security plan privacy plan other relevant documents or records

Interview

Organizational personnel with responsibilities for implementing data mining detection and prevention techniques for data storage objects legal counsel organizational personnel with information security and privacy responsibilities system developers
AC-24 Access Control Decisions

Control

[Selection(one-or-more): establish procedures; implement mechanisms] to ensure [Assignement: access control decisions] are applied to each access request prior to access enforcement.

Discussion

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.

Assessment Objective

[Selection(one-or-more): establish procedures; implement mechanisms] are taken to ensure that [Assignement: access control decisions] are applied to each access request prior to access enforcement.

Assessment Method

Examine

Access control policy procedures addressing access control decisions system design documentation system configuration settings and associated documentation system audit records system security plan other relevant documents or records

Interview

Organizational personnel with responsibilities for establishing procedures regarding access control decisions to the system organizational personnel with information security responsibilities
AC-25 Reference Monitor

Control

Implement a reference monitor for [Assignement: access control policies] that is tamperproof, always invoked, and small enough to be subject to analysis and testing, the completeness of which can be assured.

Discussion

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.

Assessment Objective

a reference monitor is implemented for [Assignement: 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.

Assessment Method

Examine

Access control policy procedures addressing access enforcement system design documentation system configuration settings and associated documentation system audit records system security plan other relevant documents or records

Interview

Organizational personnel with access enforcement responsibilities system/network administrators organizational personnel with information security responsibilities system developers

1.1 Viittaukset

1.2 Tunnistetut vaatimukset

1.3 Liittyvät säädökset

2. Tunnistetut vaatimukset

Vaatimukset
Lähde Vaatimus

3. Liittyvät säädökset

Säädökset
Lähde Sääntely