ATTACHMENT B- MFLEETS Security Controls.xlsx
XLSX spreadsheet 205 KB Posted
- Solicitation number
- W9124J23R0006
- Issued by
-
Department of the Army
View the file
Other files
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Security Controls
| Exported On: 02/08/2023 |
| CNSS 1253 Security Controls |
Confidentiality: Moderate; Integrity: High; Availability: High Overlays Applied: PII Moderate Confidentiality Impact;
| Control Number | Family | Control Title | Control Text | Confidentiality | Integrity | Availability | Supplementary Guidance | Criticality |
| AC-1 | AC | ACCESS CONTROL POLICY AND PROCEDURES | The organization:a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. An access control policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the access control policy and associated access controls; andb. Reviews and updates the current: 1. Access control policy [Assignment: organization-defined frequency]; and 2. Access control procedures [Assignment: organization-defined frequency]. | High |
Moderate Low High Moderate Low High Moderate
| Low | This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the AC family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. | |||||
| PII Moderate Confidentiality Impact Overlay Supplemental Guidance: Privacy requirements commonly use the terms “adequate security” and “confidentiality” when referring to access controls and other security safeguards for PII. Applied together, these terms signify the need to make risk-based decisions based on the magnitude of harm (to both organizations and individuals) when determining applicable restrictions for PII. For the purpose of this overlay, refer to the definitions of “adequate security” in OMB Circular A-130, Appendix III, and “confidentiality” in NIST SP 800-37, Rev. 1, Appendix B. These definitions are consistent with CNSSI No. 4009. Related Controls: AR-4; AR-7. | White | |||||
| AC-2 | AC | ACCOUNT MANAGEMENT | The organization:a. Identifies and selects the following types of information system accounts to support organizational missions/business functions: [Assignment: organization-defined information system account types];b. Assigns account managers for information system accounts;c. Establishes conditions for group and role membership;d. Specifies authorized users of the information system, group and role membership, and access authorizations (i.e., privileges) and other attributes (as required) for each account;e. Requires approvals by [Assignment: organization-defined personnel or roles] for requests to create information system accounts;f. Creates, enables, modifies, disables, and removes information system accounts in accordance with [Assignment: organization-defined procedures or conditions];g. Monitors the use of information system accounts;h. Notifies account managers: 1. When accounts are no longer required; 2. When users are terminated or transferred; and 3. When individual information system usage or need-to-know changes;i. Authorizes access to the information system based on: 1. A valid access authorization; 2. Intended system usage; and 3. Other attributes as required by the organization or associated missions/business functions;j. Reviews accounts for compliance with account management requirements [Assignment: organization-defined frequency]; andk. Establishes a process for reissuing shared/group account credentials (if deployed) when individuals are removed from the group. | High |
Moderate Low High Moderate
| Low | Information system account types include, for example, individual, shared, group, system, guest/anonymous, emergency, developer/manufacturer/vendor, temporary, and service. Some of the account management requirements listed above can be implemented by organizational information systems. The identification of authorized users of the information system and the specification of access privileges reflects the requirements in other security controls in the security plan. Users requiring administrative privileges on information system accounts receive additional scrutiny by appropriate organizational personnel (e.g., system owner, mission/business owner, or chief information security officer) responsible for approving such accounts and privileged access. Organizations may choose to define access privileges or other attributes by account, by type of account, or a combination of both. Other attributes required for authorizing access include, for example, restrictions on time-of-day, day-of-week, and point-of-origin. In defining other account attributes, organizations consider system-related requirements (e.g., scheduled maintenance, system upgrades) and mission/business requirements, (e.g., time zone differences, customer requirements, remote access to support travel requirements). Failure to consider these factors could affect information system availability. Temporary and emergency accounts are accounts intended for short-term use. Organizations establish temporary accounts as a 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 (e.g., local logon accounts used for special tasks defined by organizations or when network resources are unavailable). Such accounts remain available and are not subject to automatic disabling or removal dates. Conditions for disabling or deactivating accounts include, for example: (i) when shared/group, emergency, or temporary accounts are no longer required; or (ii) when individuals are transferred or terminated. Some types of information system accounts may require specialized training. Related controls: AC-3, AC-4, AC-5, AC-6, AC-10, AC-17, AC-19, AC-20, AU-9, IA-2, IA-4, IA-5, IA-8, CM-5, CM-6, CM-11, MA-3, MA-4, MA-5, PL-4, SC-13. | |||||
| PII Moderate Confidentiality Impact Overlay Supplemental Guidance: Related Controls: AC-16, AC-3 | Yellow | |||||
| AC-2 (1) | AC | ACCOUNT MANAGEMENT | AUTOMATED SYSTEM ACCOUNT MANAGEMENT | The organization employs automated mechanisms to support the management of information system accounts. | High |
Moderate High Moderate
| The use of automated mechanisms can include, for example: using email or text messaging to automatically notify account managers when users are terminated or transferred; using the information system to monitor account usage; and using telephonic notification to report atypical system account usage. | White | |||
| AC-2 (2) | AC | ACCOUNT MANAGEMENT | REMOVAL OF TEMPORARY / EMERGENCY ACCOUNTS | The information system automatically [Selection: removes; disables] temporary and emergency accounts after [Assignment: organization-defined time period for each type of account]. | High |
Moderate High Moderate
| This control enhancement requires the removal of both temporary and emergency accounts automatically after a predefined period of time has elapsed, rather than at the convenience of the systems administrator. | White | |||
| AC-2 (3) | AC | ACCOUNT MANAGEMENT | DISABLE INACTIVE ACCOUNTS | The information system automatically disables inactive accounts after [Assignment: organization-defined time period]. | High |
Moderate High Moderate
| White | ||||
| AC-2 (4) | AC | ACCOUNT MANAGEMENT | AUTOMATED AUDIT ACTIONS | The information system automatically audits account creation, modification, enabling, disabling, and removal actions, and notifies [Assignment: organization-defined personnel or roles]. | High |
Moderate Low High Moderate
| Low | Related controls: AU-2, AU-12. | White | |||
| AC-2 (5) | AC | ACCOUNT MANAGEMENT | INACTIVITY LOGOUT | The organization requires that users log out when [Assignment: organization-defined time-period of expected inactivity or description of when to log out]. | High |
Moderate Low High Moderate Low High Moderate
| Low | Related control: SC-23. | White | ||||
| AC-2 (7) | AC | ACCOUNT MANAGEMENT | ROLE-BASED SCHEMES | The organization:(a) Establishes and administers privileged user accounts in accordance with a role-based access scheme that organizes allowed information system access and privileges into roles;(b) Monitors privileged role assignments; and(c) Takes [Assignment: organization-defined actions] when privileged role assignments are no longer appropriate. | High |
Moderate Low High Moderate
| Low | 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. These privileged roles include, for example, key management, account management, network and system administration, database administration, and web administration. | White | |||
| AC-2 (9) | AC | ACCOUNT MANAGEMENT | RESTRICTIONS ON USE OF SHARED GROUPS / ACCOUNTS | The organization only permits the use of shared/group accounts that meet [Assignment: organization-defined conditions for establishing shared/group accounts]. | High |
Moderate Low High Moderate
| Low | White | ||||
| AC-2 (10) | AC | ACCOUNT MANAGEMENT | SHARED / GROUP ACCOUNT CREDENTIAL TERMINATION | The information system terminates shared/group account credentials when members leave the group. | High |
Moderate Low High Moderate
| Low | Yellow | |||||
| AC-2 (11) | AC | ACCOUNT MANAGEMENT | USAGE CONDITIONS | The information system enforces [Assignment: organization-defined circumstances and/or usage conditions] for [Assignment: organization-defined information system accounts]. | High | ||
| High | ||||||
| Organizations can describe the specific conditions or circumstances under which information system accounts can be used, for example, by restricting usage to certain days of the week, time of day, or specific durations of time. | Yellow | |||||
| AC-2 (12) | AC | ACCOUNT MANAGEMENT | ACCOUNT MONITORING / ATYPICAL USAGE | The organization:(a) Monitors information system accounts for [Assignment: organization-defined atypical use]; and(b) Reports atypical usage of information system accounts to [Assignment: organization-defined personnel or roles]. | High |
Moderate Low High Moderate
| Low | Atypical usage includes, for example, accessing information systems at certain times of the day and from locations that are not consistent with the normal usage patterns of individuals working in organizations. Related control: CA-7. | White | |||
| AC-2 (13) | AC | ACCOUNT MANAGEMENT | DISABLE ACCOUNTS FOR HIGH-RISK INDIVIDUALS | The organization disables accounts of users posing a significant risk within [Assignment: organization-defined time period] of discovery of the risk. | High |
Moderate Low High Moderate
| Low | Users posing a significant risk to organizations include individuals for whom reliable evidence or intelligence indicates either the intention to use authorized access to information systems to cause harm or through whom adversaries will cause harm. Harm includes potential adverse impacts to organizational operations and assets, individuals, other organizations, or the Nation. Close coordination between authorizing officials, information system administrators, and human resource managers is essential in order for timely execution of this control enhancement. Related control: PS-4. | Yellow | |||
| AC-3 | AC | ACCESS ENFORCEMENT | The information system enforces approved authorizations for logical access to information and system resources in accordance with applicable access control policies. | High |
Moderate Low High Moderate
| Low | Access control policies (e.g., identity-based policies, role-based policies, attribute-based policies) and access enforcement mechanisms (e.g., access control lists, access control matrices, cryptography) control access between active entities or subjects (i.e., users or processes acting on behalf of users) and passive entities or objects (e.g., devices, files, records, domains) in information systems. In addition to enforcing authorized access at the information system level and recognizing that information systems can host many applications and services in support of organizational missions and business operations, access enforcement mechanisms can also be employed at the application and service level to provide increased information security. Related controls: AC-2, AC-4, AC-5, AC-6, AC-16, AC-17, AC-18, AC-19, AC-20, AC-21, AC-22, AU-9, CM-5, CM-6, CM-11, MA-3, MA-4, MA-5, PE-3. | |||||
| PII Moderate Confidentiality Impact Overlay Supplemental Guidance: Related Controls: AC-16, AC-2 | Yellow | |||||
| AC-3 (4) | AC | ACCESS ENFORCEMENT | DISCRETIONARY ACCESS CONTROL | The information system enforces [Assignment: organization-defined discretionary access control policies] over defined subjects and objects where the policy specifies that a subject that has been granted access to information can do one or more of the following:(a) Pass the information to any other subjects or objects;(b) Grant its privileges to other subjects;(c) Change security attributes on subjects, objects, the information system, or the information system’s components;(d) Choose the security attributes to be associated with newly created or revised objects; or(e) Change the rules governing access control. | High |
Moderate Low High Moderate
| Low | 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 (i.e., the subjects have the discretion to pass) the information to other subjects or objects. This control enhancement can operate in conjunction with AC-3 (3). A subject that is constrained in its operation by policies governed by AC-3 (3) is still able to operate under the less rigorous constraints of this control enhancement. Thus, while AC-3 (3) imposes constraints preventing a subject from passing information to another subject operating at a different sensitivity level, AC-3 (4) permits the subject to pass the information to any subject at the same sensitivity level. The policy is bounded by the information system boundary. Once the information is passed outside of the control of the information system, additional means may be required to ensure that the constraints remain in effect. While the older, more traditional definitions of discretionary access control require identity-based access control, that limitation is not required for this use of discretionary access control. | White | |||||
| AC-3 (9) | AC | ACCESS ENFORCEMENT | CONTROLLED RELEASE | The information system does not release information outside of the established system boundary unless:(a) The receiving [Assignment: organization-defined information system or system component] provides [Assignment: organization-defined security safeguards]; and(b) [Assignment: organization-defined security safeguards] are used to validate the appropriateness of the information designated for release. | Information systems can only protect organizational information within the confines of established system boundaries. Additional security safeguards may be needed to ensure that such information is adequately protected once it is passed beyond the established information system boundaries. Examples of information leaving the system boundary include transmitting information to an external information system or printing the information on one of its printers. In cases where the information system is unable to make a determination of the adequacy of the protections provided by entities outside its boundary, as a mitigating control, organizations determine procedurally whether the external information systems are providing adequate security. The means used to determine the adequacy of the security provided by external information systems include, for example, conducting inspections or periodic testing, 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 policy to protect the information. This control enhancement requires information systems to employ technical or procedural means to validate the information prior to releasing it to external systems. For example, if the information system passes information to another system controlled by another organization, technical means are employed to validate that the security attributes associated with the exported information are appropriate for the receiving system. Alternatively, if the information system passes information to a printer in organization-controlled space, procedural means can be employed to ensure that only appropriately authorized individuals gain access to the printer. This control enhancement is most applicable when there is some policy mandate (e.g., law, Executive Order, directive, or regulation) that establishes policy regarding access to the information, and that policy applies beyond the realm of a particular information system or organization. | White | ||
| AC-4 | AC | INFORMATION FLOW ENFORCEMENT | The information system enforces approved authorizations for controlling the flow of information within the system and between interconnected systems based on [Assignment: organization-defined information flow control policies]. | High |
Moderate High Moderate
| Information flow control regulates where information is allowed to travel within an information system and between information systems (as opposed to who is allowed to access the information) and without explicit regard to subsequent accesses to that information. Flow control restrictions include, for example, keeping export-controlled information from being transmitted in the clear to the Internet, blocking outside traffic that claims to be from within the organization, restricting web requests to the Internet that are not from the internal web proxy server, and limiting information transfers between organizations based on data structures and content. Transferring information between information systems representing different security domains with different security policies introduces risk that such transfers violate one or more domain security policies. In such situations, information owners/stewards provide guidance at designated policy enforcement points between interconnected systems. Organizations consider mandating specific architectural solutions when required to enforce specific security policies. Enforcement includes, for example: (i) prohibiting information transfers between interconnected systems (i.e., allowing access only); (ii) employing hardware mechanisms to enforce one-way information flows; and (iii) implementing trustworthy regrading mechanisms to reassign security attributes and security labels.Organizations commonly employ information flow control policies and enforcement mechanisms to control the flow of information between designated sources and destinations (e.g., networks, individuals, and devices) within information systems and between interconnected systems. Flow control is based on the characteristics of the information and/or the information path. Enforcement occurs, for example, in boundary protection devices (e.g., gateways, routers, guards, encrypted tunnels, firewalls) that employ rule sets or establish configuration settings that restrict information system services, provide a packet-filtering capability based on header information, or message-filtering capability based on message content (e.g., implementing key word searches or using document characteristics). Organizations also consider the trustworthiness of filtering/inspection mechanisms (i.e., hardware, firmware, and software components) that are critical to information flow enforcement. Control enhancements 3 through 22 primarily address cross-domain solution needs which focus on more advanced filtering techniques, in-depth analysis, and stronger flow enforcement mechanisms implemented in cross-domain products, for example, high-assurance guards. Such capabilities are generally not available in commercial off-the-shelf information technology products. Related controls: AC-3, AC-17, AC-19, AC-21, CM-6, CM-7, SA-8, SC-2, SC-5, SC-7, SC-18. | |||||||
| PII Moderate Confidentiality Impact Overlay Supplemental Guidance: Related Control: AC-16 | Yellow | ||||||
| AC-4 (15) | AC | INFORMATION FLOW ENFORCEMENT | DETECTION OF UNSANCTIONED INFORMATION | The information system, when transferring information between different security domains, examines the information for the presence of [Assignment: organized-defined unsanctioned information] and prohibits the transfer of such information in accordance with the [Assignment: organization-defined security policy]. | Detection of unsanctioned information includes, for example, checking all information to be transferred for malicious code and dirty words. Related control: SI-3. | |||
| PII Moderate Confidentiality Impact Overlay Supplemental Guidance: The organization ensures systems containing moderate and high PII confidentiality impact level information include the capability for the organization to centrally monitor for and detect unauthorized transfer of such PII across different security domains. Some technologies that would facilitate this include data-loss prevention, data-rights management, and key-word detection to prevent the unauthorized export of information from a network or to render such information unusable in the event of the unauthorized export of such information between security domains. Related Control: AC-16 | White | ||||||
| AC-4 (17) | AC | INFORMATION FLOW ENFORCEMENT | DOMAIN AUTHENTICATION | The information system uniquely identifies and authenticates source and destination points by [Selection (one or more): organization, system, application, individual] for information transfer. | Attribution is a critical component of a security concept of operations. The ability to identify source and destination points for information flowing in information systems, allows the forensic reconstruction of events when required, and encourages policy compliance by attributing policy violations to specific organizations/individuals. Successful domain authentication requires that information system labels distinguish among systems, organizations, and individuals involved in preparing, sending, receiving, or disseminating information. Related controls: IA-2, IA-3, IA-4, IA-5. | |||
| PII Moderate Confidentiality Impact Overlay Supplemental Guidance: Implement a higher level of granularity for identification and authentication based on sensitivity of the PII. This is not to determine permissibility of the transfer but to enable an audit capability. | White | ||||||
| AC-4 (18) | AC | INFORMATION FLOW ENFORCEMENT | SECURITY ATTRIBUTE BINDING | The information system binds security attributes to information using [Assignment: organization-defined binding techniques] to facilitate information flow policy enforcement. | Binding techniques implemented by information systems affect the strength of security attribute binding to information. Binding strength and the assurance associated with binding techniques play an important part in the trust organizations have in the information flow enforcement process. The binding techniques affect the number and degree of additional reviews required by organizations. Related controls: AC-16, SC-16. | |||
| PII Moderate Confidentiality Impact Overlay Supplemental Guidance: To ensure the protection of PII throughout its information flow, this control should be used to protect PII as it travels within and among information systems and information system components, such as database servers, application servers, shared storage environments, document repositories, and file folders. Related Control: AC-16. | White | ||||||
| AC-5 | AC | SEPARATION OF DUTIES | The organization:a. Separates [Assignment: organization-defined duties of individuals];b. Documents separation of duties of individuals; andc. Defines information system access authorizations to support separation of duties. | High |
Moderate Low High Moderate
| Low | 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, for example: (i) dividing mission functions and information system support functions among different individuals and/or roles; (ii) conducting information system support functions with different individuals (e.g., system management, programming, configuration management, quality assurance and testing, and network security); and (iii) ensuring security personnel administering access control functions do not also administer audit functions. Related controls: AC-3, AC-6, PE-3, PE-4, PS-2. | |||||
| PII Moderate Confidentiality Impact Overlay Supplemental Guidance: Separation of duties is implemented by designating a selected set of administrators the capability to set user permissions to PII and PHI information, while those administrators do not themselves have access to the PII and PHI. The principle of separation of duties is significant for developers as well as for operational system administrators. Related Control: AC-6 | White | |||||
| AC-6 | AC | LEAST PRIVILEGE | The organization employs the concept of least privilege, allowing only authorized accesses for users (and processes acting on behalf of users) which are necessary to accomplish assigned tasks in accordance with organizational missions and business functions. | High |
Moderate Low High Moderate
| Low | Organizations employ least privilege for specific duties and information systems. The principle of least privilege is also applied to information system processes, ensuring that the processes operate at privilege levels no higher than necessary to accomplish required organizational missions/business functions. Organizations consider the creation of additional processes, roles, and information system accounts as necessary, to achieve least privilege. Organizations also apply least privilege to the development, implementation, and operation of organizational information systems. Related controls: AC-2, AC-3, AC-5, CM-6, CM-7, PL-2. | |||||
| PII Moderate Confidentiality Impact Overlay Supplemental Guidance: The organization enforces the most restrictive set of rights/privileges or access needed by users (or processes acting on behalf of users) for the performance of specified tasks —increasing the level of restriction as PII confidentiality impact level rises. The organization ensures that users who must access records containing PII only have access to the minimum amount of PII, along with only those privileges (e.g., read, write, execute) necessary to perform their assigned tasks. | White | |||||
| AC-6 (1) | AC | LEAST PRIVILEGE | AUTHORIZE ACCESS TO SECURITY FUNCTIONS | The organization explicitly authorizes access to [Assignment: organization-defined security functions (deployed in hardware, software, and firmware) and security-relevant information]. | High |
Moderate Low High Moderate
| Low | Security functions include, for example, establishing system accounts, configuring access authorizations (i.e., permissions, privileges), setting events to be audited, and setting intrusion detection parameters. Security-relevant information includes, for example, filtering rules for routers/firewalls, cryptographic key management information, configuration parameters for security services, and access control lists. Explicitly authorized personnel include, for example, security administrators, system and network administrators, system security officers, system maintenance personnel, system programmers, and other privileged users. Related controls: AC-17, AC-18, AC-19. | Yellow | |||
| AC-6 (2) | AC | LEAST PRIVILEGE | NON-PRIVILEGED ACCESS FOR NONSECURITY FUNCTIONS | The organization requires that users of information system accounts, or roles, with access to [Assignment: organization-defined security functions or security-relevant information], use non-privileged accounts or roles, when accessing nonsecurity functions. | High |
Moderate Low High Moderate
| Low | This control enhancement 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 both the user and all processes acting on behalf of the user as would be provided by a change between a privileged and non-privileged account. Related control: PL-4. | |||||
| PII Moderate Confidentiality Impact Overlay Supplemental Guidance: Any access involving PII that is non-administrative in nature should require the user to use their non-privileged accounts to perform that function. | Yellow | |||||
| AC-6 (3) | AC | LEAST PRIVILEGE | NETWORK ACCESS TO PRIVILEGED COMMANDS | The organization authorizes network access to [Assignment: organization-defined privileged commands] only for [Assignment: organization-defined compelling operational needs] and documents the rationale for such access in the security plan for the information system. | High | ||
| High | ||||||
| Network access is any access across a network connection in lieu of local access (i.e., user being physically present at the device). Related control: AC-17. | Yellow | |||||
| AC-6 (5) | AC | LEAST PRIVILEGE | PRIVILEGED ACCOUNTS | The organization restricts privileged accounts on the information system to [Assignment: organization-defined personnel or roles]. | High |
Moderate Low High Moderate
| Low | 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 having access to privileged information/functions. Organizations may differentiate in the application of this control enhancement between allowed privileges for local accounts and for domain accounts provided organizations retain the ability to control information system configurations for key security parameters and as otherwise necessary to sufficiently mitigate risk. Related control: CM-6. | Yellow | |||
| AC-6 (7) | AC | LEAST PRIVILEGE | REVIEW OF USER PRIVILEGES | The organization:(a) Reviews [Assignment: organization-defined frequency] the privileges assigned to [Assignment: organization-defined roles or classes of users] to validate the need for such privileges; and(b) Reassigns or removes privileges, if necessary, to correctly reflect organizational mission/business needs. | High |
Moderate Low High Moderate
| Low | The need for certain assigned user privileges may change over time reflecting changes in organizational missions/business function, environments of operation, technologies, or threat. 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. Related control: CA-7. | Yellow | |||
| AC-6 (8) | AC | LEAST PRIVILEGE | PRIVILEGE LEVELS FOR CODE EXECUTION | The information system prevents [Assignment: organization-defined software] from executing at higher privilege levels than users executing the software. | High |
Moderate Low High Moderate
| Low | In certain situations, software applications/programs need to execute with elevated privileges to perform required functions. However, if the privileges required for execution are at a higher level than the privileges assigned to organizational users invoking such applications/programs, those users are indirectly provided with greater privileges than assigned by organizations. | Yellow | |||
| AC-6 (9) | AC | LEAST PRIVILEGE | AUDITING USE OF PRIVILEGED FUNCTIONS | The information system audits the execution of privileged functions. | High |
Moderate Low High Moderate
| Low | Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromised information system accounts, is a serious and ongoing concern and can have significant adverse impacts on organizations. Auditing 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 (APT). Related control: AU-2. | White | |||
| AC-6 (10) | AC | LEAST PRIVILEGE | PROHIBIT NON-PRIVILEGED USERS FROM EXECUTING PRIVILEGED FUNCTIONS | The information system prevents non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. | High |
Moderate Low High Moderate
| Low | Privileged functions include, for example, establishing information system accounts, performing system integrity checks, or administering cryptographic key management activities. Non-privileged users are individuals that do not possess appropriate authorizations. Circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms are examples of privileged functions that require protection from non-privileged users. | Yellow | |||
| AC-7 | AC | UNSUCCESSFUL LOGIN ATTEMPTS | The information system:a. Enforces a limit of [Assignment: organization-defined number] consecutive invalid logon attempts by a user during a [Assignment: organization-defined time period]; andb. Automatically [Selection: locks the account/node for an [Assignment: organization-defined time period]; locks the account/node until released by an administrator; delays next logon prompt according to [Assignment: organization-defined delay algorithm]] when the maximum number of unsuccessful attempts is exceeded. | High |
Moderate Low High Moderate Low High Moderate
| Low | This control 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 information systems are usually temporary and automatically release after a predetermined time period established by organizations. If a delay algorithm is selected, organizations may choose to employ different algorithms for different information system components based on the capabilities of those components. Responses to unsuccessful logon attempts may be implemented at both the operating system and the application levels. Related controls: AC-2, AC-9, AC-14, IA-5. | Yellow | ||||
| AC-8 | AC | SYSTEM USE NOTIFICATION | The information system:a. Displays to users [Assignment: organization-defined system use notification message or banner] before granting access to the system that provides privacy and security notices consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance and states that: 1. Users are accessing a U.S. Government information system; 2. Information system usage may be monitored, recorded, and subject to audit; 3. Unauthorized use of the information system is prohibited and subject to criminal and civil penalties; and 4. Use of the information system indicates consent to monitoring and recording;b. Retains 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 information system; andc. For publicly accessible systems: 1. Displays system use information [Assignment: organization-defined conditions], before granting further access; 2. Displays references, if any, to monitoring, recording, or auditing that are consistent with privacy accommodations for such systems that generally prohibit those activities; and 3. Includes a description of the authorized uses of the system. | High |
Moderate Low High Moderate
| Low | System use notifications can be implemented using messages or warning banners displayed before individuals log in to information systems. System use notifications are used only for access via logon interfaces with human users and are not required when such human interfaces do not exist. Organizations consider system use notification messages/banners displayed in multiple languages based on specific organizational needs and the demographics of information system users. Organizations also consult with the Office of the General Counsel for legal review and approval of warning banner content. | White | |||
| AC-10 | AC | CONCURRENT SESSION CONTROL | The information system limits the number of concurrent sessions for each [Assignment: organization-defined account and/or account type] to [Assignment: organization-defined number]. | High |
Moderate High Moderate High Moderate
| Organizations may define the maximum number of concurrent sessions for information system accounts globally, by account type (e.g., privileged user, non-privileged user, domain, specific application), by account, or a combination. For example, organizations may limit the number of concurrent sessions for system administrators or individuals working in particularly sensitive domains or mission-critical applications. This control addresses concurrent sessions for information system accounts and does not address concurrent sessions by single users via multiple system accounts. | White | ||||
| AC-11 | AC | SESSION LOCK | The information system:a. Prevents further access to the system by initiating a session lock after [Assignment: organization-defined time period] of inactivity or upon receiving a request from a user; andb. Retains the session lock until the user reestablishes access using established identification and authentication procedures. | ||
| PII Moderate Confidentiality Impact Overlay Control Extension: Period of inactivity shall be no more than 30 minutes before session lock occurs for remote and mobile devices and requires user re-authentication. As agencies continue to migrate to laptops and docking stations making clients increasingly mobile, this is a logical extension of that requirement. | High |
Moderate Low High Moderate
| Low | Session locks are temporary actions taken when users stop work and move away from the immediate vicinity of information systems but do not want to log out because of the temporary nature of their absences. Session locks are implemented where session activities can be determined. This is typically at the operating system level, but can also be at the application level. Session locks are not an acceptable substitute for logging out of information systems, for example, if organizations require users to log out at the end of workdays. Related control: AC-7. | White | |||
| AC-11 (1) | AC | SESSION LOCK | PATTERN-HIDING DISPLAYS | The information system conceals, via the session lock, information previously visible on the display with a publicly viewable image. | High |
Moderate
| Low | Publicly viewable images can include static or dynamic images, for example, patterns used with screen savers, photographic images, solid colors, clock, battery life indicator, or a blank screen, with the additional caveat that none of the images convey sensitive information. | White | |||
| AC-12 | AC | SESSION TERMINATION | The information system automatically terminates a user session after [Assignment: organization-defined conditions or trigger events requiring session disconnect]. | High |
Moderate High Moderate
| This control addresses the termination of user-initiated logical sessions in contrast to SC-10 which addresses the termination of network connections that are 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 information system. Such user sessions can be terminated (and thus terminate user access) without terminating network sessions. Session termination terminates all processes associated with a user’s logical session except those processes that are specifically created by the user (i.e., session owner) to continue after the session is terminated. Conditions or trigger events requiring automatic session termination can include, for example, organization-defined periods of user inactivity, targeted responses to certain types of incidents, time-of-day restrictions on information system use. Related controls: SC-10, SC-23. | Yellow | |||
| AC-12 (1) | AC | SESSION TERMINATION | USER-INITIATED LOGOUTS/ MESSAGE DISPLAYS | The information system:(a) Provides a logout capability for user-initiated communications sessions whenever authentication is used to gain access to [Assignment: organization-defined information resources]; and(b) Displays an explicit logout message to users indicating the reliable termination of authenticated communications sessions. | High |
Moderate High Moderate
| Information resources to which users gain access via authentication include, for example, local workstations, databases, and password-protected websites/web-based services. Logout messages for web page access, for example, can be displayed after authenticated sessions have been terminated. However, for some types of interactive sessions including, for example, file transfer protocol (FTP) sessions, information systems typically send logout messages as final messages prior to terminating sessions. | Yellow | |||
| AC-14 | AC | PERMITTED ACTIONS WITHOUT IDENTIFICATION OR AUTHENTICATION | The organization:a. Identifies [Assignment: organization-defined user actions] that can be performed on the information system without identification or authentication consistent with organizational missions/business functions; andb. Documents and provides supporting rationale in the security plan for the information system, user actions not requiring identification or authentication. | High |
Moderate Low High Moderate
| Low | This control addresses situations in which organizations determine that no identification or authentication is required in organizational information systems. Organizations may allow a limited number of user actions without identification or authentication including, for example, when individuals access public websites or other publicly accessible federal information systems, when individuals use mobile phones to receive calls, or when facsimiles are received. Organizations also identify actions that normally require identification or authentication but may under certain circumstances (e.g., emergencies), 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. This control 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 information systems without identification and authentication and thus, the values for assignment statements can be none. Related controls: CP-2, IA-2. | White | |||
| AC-16 | AC | SECURITY ATTRIBUTES | The organization:a. Provides the means to associate [Assignment: organization-defined types of security attributes] having [Assignment: organization-defined security attribute values] with information in storage, in process, and/or in transmission;b. Ensures that the security attribute associations are made and retained with the information;c. Establishes the permitted [Assignment: organization-defined security attributes] for [Assignment: organization-defined information systems]; andd. Determines the permitted [Assignment: organization-defined values or ranges] for each of the established security attributes. | High |
Moderate High Moderate
| Information is represented internally within information 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 representing the basic properties or characteristics of active and passive entities with respect to safeguarding information. These attributes may be associated with active entities (i.e., subjects) that have the potential to send or receive information, to cause information to flow among objects, or to change the information system state. These attributes may also be associated with passive entities (i.e., objects) that contain or receive information. The association of security attributes to subjects and objects is referred to as binding and is typically inclusive of setting the attribute value and the attribute type. Security attributes when bound to data/information, enables the enforcement of information security policies for access control and information flow control, either through organizational processes or information system functions or mechanisms. The content or assigned values of security attributes can directly affect the ability of individuals to access organizational information.Organizations can define the types of attributes needed for selected information systems to support missions/business functions. There is potentially a wide range of values that can be assigned to any given security attribute. Release markings could include, for example, US only, NATO, or NOFORN (not releasable to foreign nationals). By specifying permitted attribute ranges and values, organizations can ensure that the security attribute values are meaningful and relevant. The term security labeling refers to the association of security attributes with subjects and objects represented by internal data structures within organizational information systems, to enable information system-based enforcement of information security policies. Security labels include, for example, access authorizations, data life cycle protection (i.e., encryption and data expiration), nationality, affiliation as contractor, and classification of information in accordance with legal and compliance requirements. The term security marking refers to the association of security attributes with objects in a human-readable form, to enable organizational process-based enforcement of information security policies. The AC-16 base control represents the requirement for user-based attribute association (marking). The enhancements to AC-16 represent additional requirements including information system-based attribute association (labeling). Types of attributes include, for example, classification level for objects and clearance (access authorization) level for subjects. An example of a value for both of these attribute types is Top Secret. Related controls: AC-3, AC-4, AC-6, AC-21, AU-2, AU-10, SC-16, MP-3. | |||||||
| PII Moderate Confidentiality Impact Overlay Supplemental Guidance: Using the security attributes listed in this control's parameter values section enables cross system functionality and reciprocity through consistent security attribute interpretation. This control supports privacy protections by assigning security attributes that characterize information, devices, or processes (i.e., an “object”) as containing PII or associate an organization’s mandatory security/privacy training requirement with a user (i.e., a “subject”) of an information system containing PII. The terms “Subject” and “Object” are defined in NIST SP 800-53, Rev. 4, Appendix B, Glossary. Security attributes are meta-data about either a subject or an object. Other security attributes may exist for other requirements beyond privacy. If an organization creates security attributes they should be cognizant of the risk associated with including PII in that meta-data. However, PII is not included in the security attributes for the parameter values specified below. Related Controls: AC-2, AC-3, AC-4, AC-4(15), AC-4(18) | White | ||||||
| AC-16 (3) | AC | SECURITY ATTRIBUTES | MAINTENANCE OF ATTRIBUTE ASSOCIATIONS BY INFORMATION SYSTEM | The information system maintains the association and integrity of [Assignment: organization-defined security attributes] to [Assignment: organization-defined subjects and objects]. | Maintaining the association and integrity of security 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. Automated policy actions include, for example, access control decisions or information flow control decisions. | |||
| PII Moderate Confidentiality Impact Overlay Supplemental Guidance: Related Controls: AC-4, AC-4(15), AC-4(18) | White | ||||||
| AC-16 (6) | AC | SECURITY ATTRIBUTES | MAINTENANCE OF ATTRIBUTE ASSOCIATION BY ORGANIZATION | The organization allows personnel to associate, and maintain the association of [Assignment: organization-defined security attributes] with [Assignment: organization-defined subjects and objects] in accordance with [Assignment: organization-defined security policies]. | High |
Moderate High Moderate
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .