AC-16—Security and Privacy Attributes
>Control Description
Provide the means to associate ⚙organization-defined types of security and privacy attributes with ⚙organization-defined security and privacy attribute values for information in storage, in process, and/or in transmission;
Ensure that the attribute associations are made and retained with the information;
Establish the following permitted security and privacy attributes from the attributes defined in AC-16a for ⚙organization-defined systems: ⚙organization-defined security and privacy attributes;
Determine the following permitted attribute values or ranges for each of the established attributes: ⚙organization-defined attribute values or ranges for established attributes;
Audit changes to attributes; and
Review ⚙organization-defined security and privacy attributes for applicability ⚙organization-defined frequency.
>DoD Impact Level Requirements
No specific parameter values or requirements for this impact level.
>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 (Media Marking).
>Relevant Technologies
Technology-specific guidance with authoritative sources and verification commands.
>Related Controls
>Assessment Interview Topics
Questions assessors commonly ask
Process & Governance:
- •What formal policies and procedures govern the implementation of AC-16 (Security And Privacy Attributes)?
- •Who are the designated roles responsible for implementing, maintaining, and monitoring AC-16?
- •How frequently is the AC-16 policy reviewed and updated, and what triggers policy changes?
- •What training or awareness programs ensure personnel understand their responsibilities related to AC-16?
Technical Implementation:
- •Describe the specific technical mechanisms or controls used to enforce AC-16 requirements.
- •What automated tools, systems, or technologies are deployed to implement AC-16?
- •How is AC-16 integrated into your system architecture and overall security posture?
- •What configuration settings, parameters, or technical specifications enforce AC-16 requirements?
Evidence & Documentation:
- •What documentation demonstrates the complete implementation of AC-16?
- •What audit logs, records, reports, or monitoring data validate AC-16 compliance?
- •Can you provide evidence of periodic reviews, assessments, or testing of AC-16 effectiveness?
- •What artifacts would you present during a FedRAMP assessment to demonstrate AC-16 compliance?
Ask AI
Configure your API key to use AI features.