Mapping of ITSG-33 Security Controls to SP Revision 4 Security Controls

Transcription

1 1 April 2013 BD Pro Mapping of ITSG-33 Security Controls to SP Revision 4 Security Controls NIST SP Revision 4 is replacing the August 2009 Revision 3 version of the security controls catalogue. The SP Revision 4 security controls listed in table below are from the initial public draft which was released in February However, it should be noted that based on feedback from the private and government sectors, the catalogue has been updated again and that the final public draft of SP revision 4 1 was issued for further review in February It is anticipated that the official Revision 4 will be issued later in Additional controls and enhancements have been introduced into the SP Revision 4 catalogue to address issues such as: - New security controls and control enhancements addressing the advanced persistent threat (APT), supply chain, insider threat, application security, distributed systems, mobile and cloud computing, and developmental and operational assurance; - Clarification of security control language; - New tailoring guidance including the fundamental assumptions used to develop the security control baselines; - Significant expansion of supplemental guidance for security controls and enhancements; - Streamlined tailoring guidance to facilitate customization of baseline security controls; - New privacy controls and implementation guidance based on the internationally recognized Fair Information Practice Principles; - Updated security control baselines; - New summary tables for security controls and naming convention for control enhancements to facilitate ease-of-use; - New mapping tables for ISO/IEC (Common Criteria); - The concept of overlays, allowing organizations and communities of interest to develop specialized security plans that reflect specific missions/business functions, environments of operation, and information technologies; and - Designation of assurance-related controls for low-impact, moderate-impact, and high-impact information systems and additional controls for responding to high assurance requirements. With respect to the controls recorded in the earlier SP Revision 3 catalogue: the additions, withdrawals, and/or consolidations of individual controls introduced in the SP Revision 4 catalogue are highlighted in yellow in the table below. The ITSG-33 unique controls are similarly highlighted. The November 2012 ITSG-33 Annex 3 Security Controls Catalogue 2 was derived from the SP Revision 3 security controls catalogue. The ITSG-33 security controls listed in table below also includes the Tailoring and Implementation Guidance and References which have been consolidated, for ease of reference, from the spreadsheet Suggested Security Controls and Control Enhancements 3 which is provided with the ITSG-33 documents. The following table is intended to assist security risk analysts leverage the Revision 4 security controls when using the ITSG-33 Annex 3 security controls catalogue and related ITSG-33 guidance documents. In particular, this mapping table will allow security risk analysts to more easily identify and consider using relevant candidate controls from SP Revision 4 catalogue to be used: - as safeguards to help mitigate security risks to critical assets when conducting Threat and Risk Assessments (TRAs); and - in tailoring of ITSG-33 Annex 4 security control profiles to help satisfy enterprise, system-specific, business, operational, technical and threat related requirements. This table may also be useful to security risk analysts when leveraging work of other organizations and sectors that are using security standards, security guidance documents and tools based on the SP security controls catalogue and security control baselines Prepared by BD Pro Inc.

2 AC-1 Technical / Access Control / Policy and Procedures AC-1 Technical / Access Control / Policy and Procedures The organization develops, disseminates, and reviews/updates [Assignment: organization defined frequency]: a. A formal, documented access control policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and b. Formal, documented procedures to facilitate the implementation of the access control policy and associated access controls. Supplemental Guidance: 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. 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. AC-2 Technical / Access Control / Account Management AC-2 Technical / Access Control / Account Management The organization manages information system accounts, including: a. Identifying account types (e.g., individual, shared/group, system, application, guest/anonymous, emergency, and temporary); b. Establishing conditions for group and role membership; c. Specifying authorized users of the information system, group and role membership, and account access authorizations (i.e., privileges) for each account; d. Requiring approvals by [Assignment: organization-defined personnel] for requests to create accounts; e. Creating, enabling, modifying, disabling, and removing accounts (including adding and deleting members from groups or roles); f. Authorizing and monitoring the use of shared/group, guest/anonymous, emergency, and temporary accounts; g. Notifying account managers: - When accounts (including shared/group, emergency, and temporary accounts) are no longer required; - When users are terminated or transferred; or - When individual information system usage or need-to-know changes; Special Publication Security and Privacy Controls for Federal Information Systems and Organizations h. Associating access authorizations and other attributes as required by the organization with each information system account; i. Granting access to the system based on: - A valid access authorization; - Intended system usage; and - Other attributes as required by the organization or associated missions/business functions; j. Reviewing accounts for compliance with account management requirements [Assignment: organization-defined frequency]; and k. Establishing a process for modifying shared/group account credentials when individuals are removed from the group. AC-1 Technical / Access Control / Policy and Procedures (A) The organization develops, disseminates, and reviews/updates [Assignment: organizationdefined frequency] a formal, documented access control policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance. (B) The organization develops, disseminates, and reviews/updates [Assignment: organizationdefined frequency] formal, documented procedures to facilitate the implementation of the access control policy and associated access controls. Supplemental Guidance: This control is intended to produce the policy and procedures that are required for the effective implementation of selected security controls and control enhancements in the access control family. The access control policy and procedures are consistent with applicable GC legislation and TBS policies, directives and standards. Existing organizational policies and procedures may make additional specific policies and procedures unnecessary. The access control policy can be included as part of the general information security policy for the organization. Access control procedures can be developed for the security program in general and for a particular information system, when required. The organizational risk management strategy is a key factor in the development of the access control policy. References TBS Operational Security Standard - Management of Information Technology Security [Reference 8]. AC-2 Technical / Access Control / Account Management (A) The organization manages information system accounts, including identifying account types (i.e., individual, group, system, application, guest/anonymous, and temporary). (B) The organization manages information system accounts, including establishing conditions for group membership. (C) The organization manages information system accounts, including identifying authorized users of the information system and specifying access privileges. (D) The organization manages information system accounts, including requiring appropriate approvals for requests to establish accounts. (E) The organization manages information system accounts, including establishing, activating, modifying, disabling, and removing accounts. (F) The organization manages information system accounts, including specifically authorizing and monitoring the use of guest/anonymous and temporary accounts. (G) The organization manages information system accounts, including notifying account managers when temporary accounts are no longer required and when information system users are terminated, transferred, or information system usage or need-to-know/need-to-share changes. (H) The organization manages information system accounts, including deactivating: (i) temporary accounts that are no longer required; and (ii) accounts of terminated or transferred users. (I) The organization manages information system accounts, including granting access to the system based on: (i) a valid access authorization; (ii) intended system usage; and (iii) other attributes as required by the organization or associated missions/business functions. (J) The organization manages information system accounts, including reviewing accounts [Assignment: organization-defined frequency]. Supplemental Guidance: The identification of authorized users of the information system and the specification of access privileges is consistent with the requirements in other security controls in the security plan. Users requiring administrative privileges on information system accounts receive additional scrutiny by organizational officials responsible for approving such accounts and privileged access. Related controls: AC-3, AC-4, AC-5, AC-6, AC-10, AC-17, AC-19, AC-20, AU- 9, IA-4, IA-5, GC.ITSG33.11.CM-5, GC.ITSG33.11.CM-6, MA-3, MA-4, MA-5, SA-7, SC-13, SI-9 Prepared by BD Pro Inc. 2

3 Supplemental Guidance: 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. 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 login accounts used for special tasks defined by organizations or when network resources are unavailable). Such accounts remain available and are not subject to automatic termination 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. 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, SI-9. SP r4 AC-2 and AU-8 incorporates r3 AC-13 AC-2 (1) Technical / Access Control / Account Management / Automated System Account Management The organization employs automated mechanisms to support the management of information system accounts. AC-2 (2) Technical / Access Control / Account Management / Removal of Temporary - Emergency Accounts The information system automatically removes temporary and emergency accounts after [Assignment: organization-defined time period for each type of account]. AC-2 (3) Technical / Access Control / Account Management / Disable Inactive Accounts The information system automatically disables inactive accounts after [Assignment: organization defined time period]. AC-2 (4) Technical / Access Control / Account Management / Automated Audit Actions The information system automatically audits account creation, modification, enabling, disabling, and removal actions and notifies, as required, [Assignment: organization-defined personnel]. Supplemental Guidance: Related controls: AU-2, AU-12. AC-2 (5) Technical / Access Control / Account Management / Inactivity Logout / Typical Usage Monitoring The organization requires that users log out when [Assignment: organization defined time-period of Tailoring and Implementation Guidance: Account review does not need to be a full reconciliation. An incremental (or differential) review from previous review may be sufficient. It is recommended these reviews be performed when physical access list reviews are performed (see PE-2). This security control/enhancement can be addressed by the organization using a combination of automated and procedural controls. The minimization of administrative privileges is an account management best-practice. AC-2 (1) Technical / Access Control / Account Management The organization employs automated mechanisms to support the management of information system accounts. Tailoring and Implementation Guidance: This security control/enhancement can be met using readily available Commercial-Off-The-Shelf (COTS) components. Consequently, inclusion of this security control/enhancement is strongly encouraged in most cases. AC-2 (2) Technical / Access Control / Account Management The information system automatically terminates temporary and emergency accounts after [Assignment: organization-defined time period for each type of account]. AC-2 (3) Technical / Access Control / Account Management The information system automatically disables inactive accounts after [Assignment: organizationdefined time period]. Tailoring and Implementation Guidance: This security control/enhancement requires careful balance between usability and security. Care needs to be taken to ensure that the appropriate balance between the two seemingly conflicting requirements is achieved. Disabling an account is understood to be the equivalent of locking an account. The account can easily be reactivated (unlocked) by an authorized administrator. AC-2 (4) Technical / Access Control / Account Management The information system automatically audits account creation, modification, disabling, and termination actions and notifies, as required, appropriate individuals. AC-2 (5) Technical / Access Control / Account Management (a) Requires that users log out when [Assignment: organization defined time-period of expected inactivity and/or description of when to log out]; Prepared by BD Pro Inc. 3

4 expected inactivity and/or description of when to log out]. Supplemental Guidance: Related control: SI-4. (b) Determines normal time-of-day and duration usage for information system accounts; (c) Monitors for atypical usage of information system accounts; and (d) Reports atypical usage to designated organizational officials. AC-2 (6) Technical / Access Control / Account Management / Dynamic Privilege Management The information system performs [Assignment: organization-defined dynamic management of user privileges and associated access authorizations] within [Assignment: organization-defined time period]. Supplemental Guidance: In contrast to conventional access control approaches which employ static information system accounts and predefined sets of user privileges, dynamic access control approaches (e.g., service-oriented architectures) rely on run time access control decisions facilitated by dynamic privilege management. While user identities may remain relatively constant over time, user privileges may change more frequently based on ongoing mission/business requirements and operational needs of organizations. Dynamic privilege management can include, for example, the immediate revocation of privileges from users, as opposed to requiring that users terminate and restart their sessions to reflect any changes in privileges. Dynamic privilege management can also refer to mechanisms that change the privileges of users based on dynamic rules as opposed to editing specific user profiles. This type of privilege management includes, for example, automatic adjustments of privileges if users are operating out of their normal work times, or if information systems are under duress or in emergency maintenance situations. This control enhancement also includes the ancillary effects of privilege changes, for example, the potential changes to encryption keys used for communications. Related control: AC-16. AC-2 (7) Technical / Access Control / Account Management / Role Based Schemes (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. Supplemental Guidance: 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. AC-2 (8) Technical / Access Control / Account Management / Dynamic Account Creation The information system creates accounts dynamically. Supplemental Guidance: Dynamic approaches for creating information system accounts (e.g., as implemented within service-oriented architectures) rely on establishing accounts (identities) at run time for entities that were previously unknown. Organizations plan for the dynamic creation of information system accounts by establishing trust relationships and mechanisms with appropriate authorities to validate related authorizations and privileges. Supplemental Guidance: Related control: AC-16. Tailoring and Implementation Guidance: Users should be required to log out at the end of the business day in order to enable the organization to apply the appropriate patches to the operating system. Organizations are typically unable to patch the operating system when a user has an active session. AC-2 (6) Technical / Access Control / Account Management The information system dynamically manages user privileges and associated access authorizations. Supplemental Guidance: In contrast to conventional access control approaches which employ static information system accounts and predefined sets of user privileges, many service-oriented architecture implementations rely on run time access control decisions facilitated by dynamic privilege management. While user identities remain relatively constant over time, user privileges may change more frequently based on the ongoing mission/business requirements and operational needs of the organization. Tailoring and Implementation Guidance: This security control/enhancement specifies a very specialized and/or advanced capability that is not required for all systems. Consequently, inclusion in a departmental profile is made on a case by case basis. AC-2 (7) Technical / Access Control / Account Management (a) Establishes and administers privileged user accounts in accordance with a role-based access scheme that organizes information system and network privileges into roles; and (b) Tracks and monitors privileged role assignments. Supplemental Guidance: Privileged roles include, for example, key management, network and system administration, database administration, web administration Tailoring and Implementation Guidance: This security control/enhancement can be met using readily available Commercial-Off-The-Shelf (COTS) components, and is considered to be best practice. Consequently, inclusion of this security control/enhancement is strongly encouraged in most cases. The minimization of administrative privileges is an account management best-practice. AC-2(8) new in SP r4 Prepared by BD Pro Inc. 4

5 AC-2 (9) Technical / Access Control / Account Management / Restrictions on Use of Shared Groups Accounts The organization prohibits the use of shared/group accounts that do not meet [Assignment: organization-defined conditions for establishing shared/group accounts]. AC-2 (10) Technical / Access Control / Account Management / Group Account Requests Approvals The organization employs automated mechanisms to request and approve membership and use of shared/group accounts. AC-2 (11) Technical / Access Control / Account Management / Group Account Credential Renewals The information system enforces the renewal of shared/group account credentials if members leave the group. AC-2 (12) Technical / Access Control / Account Management / Usage Conditions The organization determines [Assignment: organization-defined circumstances and/or usage conditions] for [Assignment: organization-defined information system accounts] AC-2(9) new in SP r4 AC-2(10) new in SP r4 AC-2(11) new in SP r4 AC-2(12) new in SP r4 Supplemental Guidance: 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. AC-2 (13) Technical / Access Control / Account Management / Account Reviews The organization conducts [Assignment: organization-defined frequency] reviews of information system accounts (including access authorizations and shared/group account memberships). AC-2 (14) Technical / Access Control / Account Management / Account Monitoring - Atypical Usage (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]. AC-2 (15) Technical / Access Control / Account Management / Disable Accounts for High-Risk Individuals The organization applies account management capabilities to expeditiously disable accounts of users posing a significant risk. AC-2(13) new in SP r4 AC-2(14) new in SP r4 AC-2(15) new in SP r4 Supplemental Guidance: 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. AC-3 Technical / Access Control / Access Enforcement AC-3 Technical / Access Control / Access Enforcement AC-3 Technical / Access Control / Access Enforcement Prepared by BD Pro Inc. 5

6 The information system enforces approved authorizations for logical access to information and system resources in accordance with applicable access control policies. Supplemental Guidance: Access enforcement includes controlling access to information system accounts during login (e.g., restricting login access by time of day, day of week, or location).subsequent to account access, access control policies (e.g., identity-based policies, rolebased 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. Organizations also consider implementing an audited, explicit override of automated mechanisms in the event of emergencies or other serious events. If organizations employ encryption of stored information (i.e., information at rest) as an access enforcement mechanism, the cryptography is FIPS 140 (as amended)-compliant. For classified information, the cryptography used depends on the classification level of the information and the clearances of the individuals having access to the information. 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, SC-13, SI-9. SP r4 AC-3 incorporates r3 AC-17(7) AC-3 (2) Technical / Access Control / Access Enforcement / Dual Authorization The information system enforces dual authorization for [Assignment: organization-defined privileged commands and/or other organization-defined actions]. Supplemental Guidance: This control enhancement addresses dual authorization. Dual authorization mechanisms require the approval of two authorized individuals in order to execute. Organizations do not require dual authorization mechanisms when immediate responses are necessary to ensure public and environmental safety. Related controls: CP-9, MP-6. AC-3 (3) Technical / Access Control / Access Enforcement / Nondiscretionary Access Control The information system enforces [Assignment: organization-defined nondiscretionary access control policies] over [Assignment: organization-defined users and information resources] where the policy rule set for each policy specifies: (a) Access control information (i.e., attributes) employed by the policy rule set; and (b) Required relationships among the access control information to permit access. Supplemental Guidance: Nondiscretionary access control is a type of access control that restricts access to objects based on the identity of subjects or groups to which the subjects belong. The access controls are nondiscretionary because subjects are restricted from passing privileges (i.e., access permissions) or information on to any other subjects or objects - that is, information systems strictly and uniformly enforce access control policies based on the rule sets established by the policies. Nondiscretionary policies include, for example, mandatory access control, type enforcement, and originator-controlled access control. (A) The information system enforces approved authorizations for logical access to the system in accordance with applicable policy. Supplemental Guidance: 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) are employed by organizations to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, domains) in the information system. In addition to enforcing authorized access at the information system level, access enforcement mechanisms are employed at the application level, when necessary, to provide increased information security for the organization. Consideration is given to the implementation of an audited, explicit override of automated mechanisms in the event of emergencies or other serious events. If encryption of stored information is employed as an access enforcement mechanism, the cryptography used must be compliant with the requirements of control SC-13. For classified information, the cryptography used is largely dependent on the classification level of the information and the clearances of the individuals having access to the information. Mechanisms implemented by AC-3 AC-3 (2) Technical / Access Control / Access Enforcement The information system enforces dual authorization, based on organizational policies and procedures for [Assignment: organization-defined privileged commands]. Supplemental Guidance: Dual authorization mechanisms require two forms of approval to execute. The organization does not employ dual authorization mechanisms when an immediate response is necessary to ensure public and environmental safety. Tailoring and Implementation Guidance: This security control/enhancement specifies a very specialized and/or advanced capability that is not required for all systems. Consequently, inclusion in a departmental profile is made on a case by case basis. Dual authorization mechanisms are applicable to specialized systems such as a key management system. AC-3 (3) Technical / Access Control / Access Enforcement The information system enforces [Assignment: organization-defined nondiscretionary access control policies] over [Assignment: organization-defined set of users and resources] where the policy rule set for each policy specifies: (a) Access control information (i.e., attributes) employed by the policy rule set (e.g., position, nationality, age, project, time of day); and (b) Required relationships among the access control information to permit access. For Mandatory Access Control (MAC): Policy establishes coverage over all subjects and objects under its control to ensure that each user receives only that information to which the user is authorized access based on classification of the information, and on user clearance and formal access authorization. The information system assigns appropriate security attributes (e.g., labels/security domains/types) to subjects and objects, and uses these attributes as the basis for MAC decisions. The Bell-LaPadula security model defines allowed access with regard to an organization-defined set of strictly hierarchical security levels as follows: A subject can read an object only if the security level of the subject dominates the security level of the object and a subject can write to an object only if two conditions are met: the security level of the object dominates the security level of the subject, and the security level of the user's clearance dominates the security level of the object (no read up, no write down). For Role-Based Access Control (RBAC): Policy establishes coverage over all users and Prepared by BD Pro Inc. 6

7 AC-3 (4) Technical / Access Control / Access Enforcement / Discretionary Access Control The information system enforces a discretionary access control policy. Supplemental Guidance: Discretionary access control is a type of access control that restricts access to objects based on the identity of subjects or groups to which subjects belong. The access controls are discretionary because subjects are not restricted from passing privileges (i.e., access permissions) or information to any other subjects or objects. Nondiscretionary access controls, in contrast, restrict this capability. AC-3 (5) Technical / Access Control / Access Enforcement / Security- Relevant Information The information system prevents access to [Assignment: organization-defined security-relevant information] except during secure, non-operable system states. Supplemental Guidance: Security-relevant information is any information within information systems that can potentially impact the operation of security functions or the provision of security services in a manner that could result in failure to enforce system security policies or maintain the isolation of code and data. Security-relevant information includes, for example, filtering rules for routers/firewalls, cryptographic key management information, configuration parameters for security services, and access control lists. Secure, non-operable system states include the times in which information systems are not performing mission/business-related processing (e.g., the system is off-line for maintenance, troubleshooting, boot-up, shut down). Related controls: CM-3, CM-6. Withdrawn Incorporated into SP r4 MP-4 and SC-28 AC-3 (7) Technical / Access Control / Access Enforcement / Mandatory Access Control The information system enforces a mandatory access control policy over [Assignment: organization-defined users and information resources] and controls access based on [Assignment: resources to ensure that access rights are grouped by role name, and access to resources is restricted to users who have been authorized to assume the associated role. Supplemental Guidance: Nondiscretionary access control policies that may be implemented by organizations include, for example, Attribute-Based Access Control, Mandatory Access Control, and Originator Controlled Access Control. Nondiscretionary access control policies may be employed by organizations in addition to the employment of discretionary access control policies. Tailoring and Implementation Guidance: This security control/enhancement specifies a very specialized and/or advanced capability that is not required for all systems. Consequently, inclusion in a departmental profile is made on a case by case basis. AC-3 (4) Technical / Access Control / Access Enforcement The information system enforces a Discretionary Access Control (DAC) policy that: (a) Allows users to specify and control sharing by named individuals or groups of individuals, or by both; (b) Limits propagation of access rights; and (c) Includes or excludes access to the granularity of a single user. Tailoring and Implementation Guidance: This security control/enhancement can be met using readily available Commercial-Off-The-Shelf (COTS) components. Consequently, inclusion of this security control/enhancement is strongly encouraged in most cases. AC-3 (5) Technical / Access Control / Access Enforcement The information system prevents access to [Assignment: organization-defined security-relevant information] except during secure, non-operable system states. Supplemental Guidance: Security-relevant information is any information within the information system that can potentially impact the operation of security functions in a manner that could result in failure to enforce the system security policy or maintain isolation of code and data. Filtering rules for routers and firewalls, cryptographic key management information, key configuration parameters for security services, and access control lists are examples of security-relevant information. Secure, non-operable system states are states in which the information system is not performing mission/business-related processing (e.g., the system is off-line for maintenance, troubleshooting, boot-up, shutdown). Tailoring and Implementation Guidance: This security control/enhancement specifies a very specialized and/or advanced capability, typically found in Type 1 devices or guards, that is not required for all systems. Consequently, inclusion in a departmental profile is made on a case by case basis. AC-3 (6) Technical / Access Control / Access Enforcement The organization encrypts or stores off-line in a secure location [Assignment: organizationdefined user and/or system information]. Supplemental Guidance: The use of encryption by the organization reduces the probability of unauthorized disclosure of information and can also detect unauthorized changes to information. Removing information from online storage to offline storage eliminates the possibility of individuals gaining unauthorized access via a network. Related control: MP-4. Tailoring and Implementation Guidance: This security control/enhancement is considered a compensating control that should be applied if the capability cannot be addressed using an alternate security control/enhancement. AC-3(7) new in SP r4 Prepared by BD Pro Inc. 7

8 organization-defined hierarchical security levels and formal access compartments]. Supplemental Guidance: Organizations implement mandatory access control policies using the Bell-LaPadula security model, or some variation of the security model, which defines allowed accesses to information resources based on hierarchical security levels and user privileges. Hierarchical security levels include, for example: (i) unclassified, confidential, secret, top secret; and (ii) public, sensitive, and senior-executive-only. Organizations also employ formal access compartments defining explicit information categories when applying mandatory access control policies with regard to hierarchical security levels. Organizations require formal access authorizations to specific compartments in order for access to be granted. AC-3 (8) Technical / Access Control / Access Enforcement / Role Based Access Control The information system enforces a role-based access control policy over [Assignment: organization-defined users and information resources] and controls access based upon [Assignment: organization-defined roles and users authorized to assume such roles]. Supplemental Guidance: Role-based access control is a type of nondiscretionary access control. AC-3 (9) Technical / Access Control / Access Enforcement / Revocation of Access Authorizations The information system revokes access authorizations resulting from changes to the security attributes of subjects and objects based on [Assignment: organization-defined rules governing revocation of access authorizations]. Supplemental Guidance: Revocation of access rules may differ based on the types of access revoked. For example, if a subject (i.e., user or process) is removed from a group, access may not be revoked until the next time the object (e.g., file) is opened or until the next time the subject attempts a new access to the object. Revocation based on changes to security labels may take effect immediately. Organizations can provide alternative approaches on how to make revocations immediate if information systems cannot provide such capability and immediate revocation is necessary. Related control: AC-16. AC-3 (10) Technical / Access Control / Access Enforcement / Network Access Security-Related Functions The organization ensures that network sessions for accessing [Assignment: organization-defined security functions and security-relevant information] employ [Assignment: organization-defined additional security safeguards] and are audited. Supplemental Guidance: Additional security safeguards typically include more than standard bulk or session layer encryption (e.g., Secure Shell [SSH], Virtual Private Networking [VPN] with blocking mode enabled) deployed by organizations. Related controls: AU-2, AU-12, SC-7, SC-8, SC-9. AC-3(8) new in SP r4 AC-3(9) new in SP r4 AC-3(10) new in SP r4 AC-4 Technical / Access Control / Information Flow Enforcement AC-4 Technical / Access Control / Information Flow Enforcement The information system enforces approved authorizations for controlling the flow of information within the system and between interconnected systems in accordance with applicable flow control policies. Supplemental Guidance: 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 AC-4 Technical / Access Control / Information Flow Enforcement (A) The information system enforces approved authorizations for controlling the flow of information within the system and between interconnected systems in accordance with applicable policy. Supplemental Guidance: 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. A few examples of flow control restrictions include: keeping export controlled information from being transmitted in the clear to the Internet, blocking outside traffic that claims to be from within the Prepared by BD Pro Inc. 8

9 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. 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, devices) within information systems and between interconnected systems. Flow control is based on the characteristics of the information and/or the information path. Flow 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 document characteristics). Organizations also consider the trustworthiness of filtering and inspection mechanisms (including hardware, firmware, and software components) that are critical to information flow enforcement. Control enhancements 3 through 21 are primarily intended to address cross-domain solution needs. Related controls: AC-17, AC-19, AC-21, CM-6, CM-7, SA- 8, SC-2, SC-5, SC-7, SC-18. AC-4 (1) Technical / Access Control / Information Flow Enforcement / Enforcement Object Security Attributes The information system enforces information flow control using explicit security attributes on information, source, and destination objects as a basis for flow control decisions. Supplemental Guidance: Information flow enforcement mechanisms compare security attributes on information (data content and data structure), source and destination objects, and respond appropriately (e.g., block, quarantine, alert administrator) when the mechanisms encounter information flows not explicitly allowed by information flow policies. Flow enforcement using explicit security attributes can be used, for example, to control the release of certain types of information. Related control: AC-16. AC-4 (2) Technical / Access Control / Information Flow Enforcement / Processing Domains The information system enforces information flow control using protected processing domains as a basis for flow control decisions. Supplemental Guidance: Protected processing domains are processing spaces with controlled interactions with other processing spaces, thus enabling control of information flows between these spaces and to/from data/information objects. A protected processing domain includes, for example, domain type enforcement where information system processes are assigned to domains, information is identified by types, and information flows are controlled based on allowed information accesses (determined by domain and type), allowed signaling among domains, and allowed process transitions to other domains. AC-4 (3) Technical / Access Control / Information Flow Enforcement / Operational Changes The information system enforces dynamic information flow control based on policy that allows or disallows information flows based on changing conditions or operational considerations. organization and not passing any web requests to the Internet that are not from the internal web proxy. Information flow control policies and enforcement mechanisms are commonly employed by organizations to control the flow of information between designated sources and destinations (e.g., networks, individuals, devices) within information systems and between interconnected systems. Flow control is based on the characteristics of the information and/or the information path. Specific examples of flow control enforcement can be found in boundary protection devices (e.g., proxies, gateways, guards, encrypted tunnels, firewalls, and routers) that employ rule sets or establish configuration settings that restrict information system services, provide a packetfiltering capability based on header information, or message-filtering capability based on content (e.g., using key word searches or document characteristics). Mechanisms implemented by AC-4 are configured to enforce authorizations determined by other security controls. Related controls: AC-17, AC-19, AC-21, CM-7, SA-8, SC-2, SC-5, SC-7, SC-18 References CSEC ITSG-22 Baseline Security Requirements for Network Security Zones in the Government of Canada [Reference 42]. Tailoring and Implementation Guidance: Examples of devices that can perform information flow enforcement include firewalls, gateways and virtual private networks. Example technologies of implement this control are the Sender Policy Framework (SPF), that can be used to help protect organizations from spoofed attacks, web content filtering devices that help protect organizations from malicious web traffic and deny users' access to unauthorized web sites, and Data Loss Prevention products. AC-4 (1) Technical / Access Control / Information Flow Enforcement The information system enforces information flow control using explicit security attributes on information, source, and destination objects as a basis for flow control decisions. Supplemental Guidance: Information flow enforcement mechanisms compare security attributes on all information (data content and data structure), source and destination objects, and respond appropriately (e.g., block, quarantine, alert administrator) when the mechanisms encounter information flows not explicitly allowed by the information flow policy. Information flow enforcement using explicit security attributes can be used, for example, to control the release of certain types of information. Tailoring and Implementation Guidance: This security control/enhancement specifies a very specialized and/or advanced capability, typically found in CDS, guards or XML firewalls, that is not required for all systems. Consequently, inclusion in a departmental profile is made on a case by case basis. AC-4 (2) Technical / Access Control / Information Flow Enforcement The information system enforces information flow control using protected processing domains (e.g., domain type-enforcement) as a basis for flow control decisions. Tailoring and Implementation Guidance: This security control/enhancement specifies a very specialized and/or advanced capability that is not required for all systems. Consequently, inclusion in a departmental profile is made on a case by case basis. AC-4 (3) Technical / Access Control / Information Flow Enforcement The information system enforces dynamic information flow control based on policy that allows or disallows information flows based on changing conditions or operational considerations. Tailoring and Implementation Guidance: This security control/enhancement specifies a very Prepared by BD Pro Inc. 9

10 Supplemental Guidance: Changing conditions include, for example, changes in organizational risk tolerance due to changes in the immediacy of mission/business needs, changes in threat environments, and detection of potentially harmful events. Related control: SI-4. AC-4 (4) Technical / Access Control / Information Flow Enforcement / Content Check Encrypted Data The information system prevents encrypted data from bypassing content-checking mechanisms. specialized and/or advanced capability that is not required for all systems. Consequently, inclusion in a departmental profile is made on a case by case basis. AC-4 (4) Technical / Access Control / Information Flow Enforcement The information system prevents encrypted data from bypassing content-checking mechanisms. Supplemental Guidance: Related control: SI-4. AC-4 (5) Technical / Access Control / Information Flow Enforcement / Embedded Data Types The information system enforces [Assignment: organization-defined limitations] on embedding data types within other data types. Supplemental Guidance: Embedding data types within other data types may result in reduced flow control effectiveness. Data type embedding includes, for example, inserting executable files as objects within word processing files or inserting references or descriptive information into a media file. AC-4 (6) Technical / Access Control / Information Flow Enforcement / Metadata The information system enforces information flow control based on [Assignment: organization defined metadata]. Supplemental Guidance: Metadata is information used to describe the characteristics of data. Metadata can include structural metadata describing data structures (e.g., data format, syntax, and semantics) or descriptive metadata describing data contents (e.g., age, location, telephone number). Enforcing allowed information flows based on metadata enables simpler and more effective flow control. Organizations consider the trustworthiness of metadata with regard to data integrity (i.e., protecting against unauthorized changes to metadata tags) and the binding of metadata to the data payload (i.e., ensuring sufficiently strong binding techniques with appropriate levels of assurance). Related controls: AC-16, SI-7. AC-4 (7) Technical / Access Control / Information Flow Enforcement / One- Way Flow Mechanisms The information system enforces [Assignment: organization-defined one-way flows] using hardware mechanisms. AC-4 (8) Technical / Access Control / Information Flow Enforcement / Security Policy Filters The information system enforces information flow control using [Assignment: organization-defined security policy filters] as a basis for flow control decisions for [Assignment: organization-defined information flows]. Supplemental Guidance: Organization-defined security policy filters can address data structures and content. For example, security policy filters for data structures can check for maximum file lengths, maximum field sizes, and data/file types (for structured and unstructured data). Security policy filters for data content can check for specific words (e.g., dirty/clean word filters), metadata content, and hidden content. Structured data permits the interpretation of data content by applications. Unstructured data typically refers to digital information without a particular data structure or with a data structure that does not facilitate the development of rule sets to address the particular sensitivity of the information conveyed by the data or the associated flow enforcement decisions. Unstructured data consists of: (i) bitmap objects that are inherently non- AC-4 (5) Technical / Access Control / Information Flow Enforcement The information system enforces [Assignment: organization-defined limitations on the embedding of data types within other data types]. Tailoring and Implementation Guidance: This security control/enhancement specifies a very specialized and/or advanced capability that is not required for all systems. Consequently, inclusion in a departmental profile is made on a case by case basis. AC-4 (6) Technical / Access Control / Information Flow Enforcement The information system enforces information flow control on metadata. Tailoring and Implementation Guidance: This security control/enhancement specifies a very specialized and/or advanced capability that is not required for all systems. Consequently, inclusion in a departmental profile is made on a case by case basis. AC-4 (7) Technical / Access Control / Information Flow Enforcement The information system enforces [Assignment: organization-defined one-way flows] using hardware mechanisms. Tailoring and Implementation Guidance: This security control/enhancement specifies a very specialized and/or advanced capability that is not required for all systems. Consequently, inclusion in a departmental profile is made on a case by case basis. AC-4 (8) Technical / Access Control / Information Flow Enforcement The information system enforces information flow control using [Assignment: organization-defined security policy filters] as a basis for flow control decisions. Supplemental Guidance: Organization-defined security policy filters include, for example, dirty word filters, file type checking filters, structured data filters, unstructured data filters, metadata content filters, and hidden content filters. Structured data permits the interpretation of its content by virtue of atomic elements that are understandable by an application and indivisible. Unstructured data refers to masses of (usually) digital information that does not have a data structure or has a data structure that is not easily readable by a machine. Unstructured data consists of two basic categories: (i) bitmap objects that are inherently non language-based (i.e., image, video, or audio files); and (ii) textual objects that are based on a written or printed language (i.e., commercial off-the-shelf word processing documents, spreadsheets, or s). Prepared by BD Pro Inc. 10