Records 801–1,200 — Security and compliance controls, one provision at a time: NIST SP 800-53 and the HIPAA Security Rule in their own words
Records 801 to 1,200 of 2,022. Each links to its own page, which carries the source URL and the quoted line that states the value.
- IA-5eChanging default authenticators prior to first use;
- IA-5fChanging or refreshing authenticators {{ insert: param, ia-05_odp.01 }} or when {{ insert: param, ia-05_odp.02 }} occur;
- IA-5gProtecting authenticator content from unauthorized disclosure and modification;
- IA-5hRequiring individuals to take, and having devices implement, specific controls to protect authenticators; and
- IA-5iChanging authenticators for group or role accounts when membership to those accounts changes.
- IA-6Obscure feedback of authentication information during the authentication process to protect the information from possible exploitation and use by unauthorized individuals.
- IA-7Implement mechanisms for authentication to a cryptographic module that meet the requirements of applicable laws, executive orders, directives, policies, regulations, standards, and
- IA-8Uniquely identify and authenticate non-organizational users or processes acting on behalf of non-organizational users.
- IA-8(1)Accept and electronically verify Personal Identity Verification-compliant credentials from other federal agencies.
- IA-8(2)(a)Accept only external authenticators that are NIST-compliant; and
- IA-8(2)(b)Document and maintain a list of accepted external authenticators.
- IA-8(4)Conform to the following profiles for identity management {{ insert: param, ia-08.04_odp }}.
- IA-8(5)Accept and verify federated or PKI credentials that meet {{ insert: param, ia-08.05_odp }}.
- IA-8(6)Implement the following measures to disassociate user attributes or identifier assertion relationships among individuals, credential service providers, and relying parties: {{ inse
- IA-9Uniquely identify and authenticate {{ insert: param, ia-09_odp }} before establishing communications with devices, users, or other services or applications.
- IA-10Require individuals accessing the system to employ {{ insert: param, ia-10_odp.01 }} under specific {{ insert: param, ia-10_odp.02 }}.
- IA-11Require users to re-authenticate when {{ insert: param, ia-11_odp }}.
- IA-12(1)Require that the registration process to receive an account for logical access includes supervisor or sponsor authorization.
- IA-12(2)Require evidence of individual identification be presented to the registration authority.
- IA-12(3)Require that the presented identity evidence be validated and verified through {{ insert: param, ia-12.03_odp }}.
- IA-12(4)Require that the validation and verification of identity evidence be conducted in person before a designated registration authority.
- IA-12(5)Require that a {{ insert: param, ia-12.05_odp }} be delivered through an out-of-band channel to verify the users address (physical or digital) of record.
- IA-12(6)Accept externally-proofed identities at {{ insert: param, ia-12.06_odp }}.
- IA-12aIdentity proof users that require accounts for logical access to systems based on appropriate identity assurance level requirements as specified in applicable standards and guideli
- IA-12bResolve user identities to a unique individual; and
- IA-12cCollect, validate, and verify identity evidence.
- IA-13Employ identity providers and authorization servers to manage user, device, and non-person entity (NPE) identities, attributes, and access rights supporting authentication and auth
- IA-13(1)Cryptographic keys that protect access tokens are generated, managed, and protected from disclosure and misuse.
- IA-13(2)The source and integrity of identity assertions and access tokens are verified before granting access to system and information resources.
- IA-13(3)In accordance with {{ insert: param, ia-13_odp.01 }}, assertions and access tokens are:
- IA-13(3)(a)generated;
- IA-13(3)(c)refreshed;
- IA-13(3)(e)time-restricted; and
- IA-13(3)(f)audience-restricted.
- IR-1aDevelop, document, and disseminate to {{ insert: param, ir-1_prm_1 }}:
- IR-1a1{{ insert: param, ir-01_odp.03 }} incident response policy that:
- IR-1a1(a)Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
- IR-1a1(b)Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
- IR-1a2Procedures to facilitate the implementation of the incident response policy and the associated incident response controls;
- IR-1bDesignate an {{ insert: param, ir-01_odp.04 }} to manage the development, documentation, and dissemination of the incident response policy and procedures; and
- IR-1cReview and update the current incident response:
- IR-1c1Policy {{ insert: param, ir-01_odp.05 }} and following {{ insert: param, ir-01_odp.06 }} ; and
- IR-1c2Procedures {{ insert: param, ir-01_odp.07 }} and following {{ insert: param, ir-01_odp.08 }}.
- IR-2(1)Incorporate simulated events into incident response training to facilitate the required response by personnel in crisis situations.
- IR-2(2)Provide an incident response training environment using {{ insert: param, ir-02.02_odp }}.
- IR-2(3)Provide incident response training on how to identify and respond to a breach, including the organization’s process for reporting a breach.
- IR-2aProvide incident response training to system users consistent with assigned roles and responsibilities:
- IR-2a1Within {{ insert: param, ir-02_odp.01 }} of assuming an incident response role or responsibility or acquiring system access;
- IR-2a2When required by system changes; and
- IR-2a3{{ insert: param, ir-02_odp.02 }} thereafter; and
- IR-2bReview and update incident response training content {{ insert: param, ir-02_odp.03 }} and following {{ insert: param, ir-02_odp.04 }}.
- IR-3Test the effectiveness of the incident response capability for the system {{ insert: param, ir-03_odp.01 }} using the following tests: {{ insert: param, ir-03_odp.02 }}.
- IR-3(1)Test the incident response capability using {{ insert: param, ir-03.01_odp }}.
- IR-3(2)Coordinate incident response testing with organizational elements responsible for related plans.
- IR-3(3)Use qualitative and quantitative data from testing to:
- IR-3(3)(a)Determine the effectiveness of incident response processes;
- IR-3(3)(b)Continuously improve incident response processes; and
- IR-3(3)(c)Provide incident response measures and metrics that are accurate, consistent, and in a reproducible format.
- IR-4(1)Support the incident handling process using {{ insert: param, ir-04.01_odp }}.
- IR-4(2)Include the following types of dynamic reconfiguration for {{ insert: param, ir-04.02_odp.02 }} as part of the incident response capability: {{ insert: param, ir-04.02_odp.01 }}.
- IR-4(3)Identify {{ insert: param, ir-04.03_odp.01 }} and take the following actions in response to those incidents to ensure continuation of organizational mission and business functions:
- IR-4(4)Correlate incident information and individual incident responses to achieve an organization-wide perspective on incident awareness and response.
- IR-4(5)Implement a configurable capability to automatically disable the system if {{ insert: param, ir-04.05_odp }} are detected.
- IR-4(6)Implement an incident handling capability for incidents involving insider threats.
- IR-4(7)Coordinate an incident handling capability for insider threats that includes the following organizational entities {{ insert: param, ir-04.07_odp }}.
- IR-4(8)Coordinate with {{ insert: param, ir-04.08_odp.01 }} to correlate and share {{ insert: param, ir-04.08_odp.02 }} to achieve a cross-organization perspective on incident awareness a
- IR-4(9)Employ {{ insert: param, ir-04.09_odp }} to respond to incidents.
- IR-4(10)Coordinate incident handling activities involving supply chain events with other organizations involved in the supply chain.
- IR-4(11)Establish and maintain an integrated incident response team that can be deployed to any location identified by the organization in {{ insert: param, ir-04.11_odp }}.
- IR-4(12)Analyze malicious code and/or other residual artifacts remaining in the system after the incident.
- IR-4(13)Analyze anomalous or suspected adversarial behavior in or related to {{ insert: param, ir-04.13_odp }}.
- IR-4(14)Establish and maintain a security operations center.
- IR-4(15)(a)Manage public relations associated with an incident; and
- IR-4(15)(b)Employ measures to repair the reputation of the organization.
- IR-4aImplement an incident handling capability for incidents that is consistent with the incident response plan and includes preparation, detection and analysis, containment, eradicatio
- IR-4bCoordinate incident handling activities with contingency planning activities;
- IR-4cIncorporate lessons learned from ongoing incident handling activities into incident response procedures, training, and testing, and implement the resulting changes accordingly; and
- IR-4dEnsure the rigor, intensity, scope, and results of incident handling activities are comparable and predictable across the organization.
- IR-5Track and document incidents.
- IR-5(1)Track incidents and collect and analyze incident information using {{ insert: param, ir-5.1_prm_1 }}.
- IR-6(1)Report incidents using {{ insert: param, ir-06.01_odp }}.
- IR-6(2)Report system vulnerabilities associated with reported incidents to {{ insert: param, ir-06.02_odp }}.
- IR-6(3)Provide incident information to the provider of the product or service and other organizations involved in the supply chain or supply chain governance for systems or system compone
- IR-6aRequire personnel to report suspected incidents to the organizational incident response capability within {{ insert: param, ir-06_odp.01 }} ; and
- IR-6bReport incident information to {{ insert: param, ir-06_odp.02 }}.
- IR-7Provide an incident response support resource, integral to the organizational incident response capability, that offers advice and assistance to users of the system for the handlin
- IR-7(1)Increase the availability of incident response information and support using {{ insert: param, ir-07.01_odp }}.
- IR-7(2)(a)Establish a direct, cooperative relationship between its incident response capability and external providers of system protection capability; and
- IR-7(2)(b)Identify organizational incident response team members to the external providers.
- IR-8(1)Include the following in the Incident Response Plan for breaches involving personally identifiable information:
- IR-8(1)(a)A process to determine if notice to individuals or other organizations, including oversight organizations, is needed;
- IR-8(1)(b)An assessment process to determine the extent of the harm, embarrassment, inconvenience, or unfairness to affected individuals and any mechanisms to mitigate such harms; and
- IR-8(1)(c)Identification of applicable privacy requirements.
- IR-8aDevelop an incident response plan that:
- IR-8a1Provides the organization with a roadmap for implementing its incident response capability;
- IR-8a2Describes the structure and organization of the incident response capability;
- IR-8a3Provides a high-level approach for how the incident response capability fits into the overall organization;
- IR-8a4Meets the unique requirements of the organization, which relate to mission, size, structure, and functions;
- IR-8a5Defines reportable incidents;
- IR-8a6Provides metrics for measuring the incident response capability within the organization;
- IR-8a7Defines the resources and management support needed to effectively maintain and mature an incident response capability;
- IR-8a8Addresses the sharing of incident information;
- IR-8a9Is reviewed and approved by {{ insert: param, ir-08_odp.01 }} {{ insert: param, ir-08_odp.02 }} ; and
- IR-8a10Explicitly designates responsibility for incident response to {{ insert: param, ir-08_odp.03 }}.
- IR-8bDistribute copies of the incident response plan to {{ insert: param, ir-08_odp.04 }};
- IR-8cUpdate the incident response plan to address system and organizational changes or problems encountered during plan implementation, execution, or testing;
- IR-8dCommunicate incident response plan changes to {{ insert: param, ir-8_prm_5 }} ; and
- IR-8eProtect the incident response plan from unauthorized disclosure and modification.
- IR-9Respond to information spills by:
- IR-9(2)Provide information spillage response training {{ insert: param, ir-09.02_odp }}.
- IR-9(3)Implement the following procedures to ensure that organizational personnel impacted by information spills can continue to carry out assigned tasks while contaminated systems are un
- IR-9(4)Employ the following controls for personnel exposed to information not within assigned access authorizations: {{ insert: param, ir-09.04_odp }}.
- IR-9aAssigning {{ insert: param, ir-09_odp.01 }} with responsibility for responding to information spills;
- IR-9bIdentifying the specific information involved in the system contamination;
- IR-9cAlerting {{ insert: param, ir-09_odp.02 }} of the information spill using a method of communication not associated with the spill;
- IR-9dIsolating the contaminated system or system component;
- IR-9eEradicating the information from the contaminated system or component;
- IR-9fIdentifying other systems or system components that may have been subsequently contaminated; and
- IR-9gPerforming the following additional actions: {{ insert: param, ir-09_odp.03 }}.
- MA-1aDevelop, document, and disseminate to {{ insert: param, ma-1_prm_1 }}:
- MA-1a1{{ insert: param, ma-01_odp.03 }} maintenance policy that:
- MA-1a1(a)Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
- MA-1a1(b)Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
- MA-1a2Procedures to facilitate the implementation of the maintenance policy and the associated maintenance controls;
- MA-1bDesignate an {{ insert: param, ma-01_odp.04 }} to manage the development, documentation, and dissemination of the maintenance policy and procedures; and
- MA-1cReview and update the current maintenance:
- MA-1c1Policy {{ insert: param, ma-01_odp.05 }} and following {{ insert: param, ma-01_odp.06 }} ; and
- MA-1c2Procedures {{ insert: param, ma-01_odp.07 }} and following {{ insert: param, ma-01_odp.08 }}.
- MA-2(2)(a)Schedule, conduct, and document maintenance, repair, and replacement actions for the system using {{ insert: param, ma-2.2_prm_1 }} ; and
- MA-2(2)(b)Produce up-to date, accurate, and complete records of all maintenance, repair, and replacement actions requested, scheduled, in process, and completed.
- MA-2aSchedule, document, and review records of maintenance, repair, and replacement on system components in accordance with manufacturer or vendor specifications and/or organizational r
- MA-2bApprove and monitor all maintenance activities, whether performed on site or remotely and whether the system or system components are serviced on site or removed to another locatio
- MA-2cRequire that {{ insert: param, ma-02_odp.01 }} explicitly approve the removal of the system or system components from organizational facilities for off-site maintenance, repair, or
- MA-2dSanitize equipment to remove the following information from associated media prior to removal from organizational facilities for off-site maintenance, repair, or replacement: {{ in
- MA-2eCheck all potentially impacted controls to verify that the controls are still functioning properly following maintenance, repair, or replacement actions; and
- MA-2fInclude the following information in organizational maintenance records: {{ insert: param, ma-02_odp.03 }}.
- MA-3(1)Inspect the maintenance tools used by maintenance personnel for improper or unauthorized modifications.
- MA-3(2)Check media containing diagnostic and test programs for malicious code before the media are used in the system.
- MA-3(3)Prevent the removal of maintenance equipment containing organizational information by:
- MA-3(3)(a)Verifying that there is no organizational information contained on the equipment;
- MA-3(3)(b)Sanitizing or destroying the equipment;
- MA-3(3)(c)Retaining the equipment within the facility; or
- MA-3(3)(d)Obtaining an exemption from {{ insert: param, ma-03.03_odp }} explicitly authorizing removal of the equipment from the facility.
- MA-3(4)Restrict the use of maintenance tools to authorized personnel only.
- MA-3(5)Monitor the use of maintenance tools that execute with increased privilege.
- MA-3(6)Inspect maintenance tools to ensure the latest software updates and patches are installed.
- MA-3aApprove, control, and monitor the use of system maintenance tools; and
- MA-3bReview previously approved system maintenance tools {{ insert: param, ma-03_odp }}.
- MA-4(1)(a)Log {{ insert: param, ma-4.1_prm_1 }} for nonlocal maintenance and diagnostic sessions; and
- MA-4(1)(b)Review the audit records of the maintenance and diagnostic sessions to detect anomalous behavior.
- MA-4(3)(a)Require that nonlocal maintenance and diagnostic services be performed from a system that implements a security capability comparable to the capability implemented on the system be
- MA-4(3)(b)Remove the component to be serviced from the system prior to nonlocal maintenance or diagnostic services; sanitize the component (for organizational information); and after the ser
- MA-4(4)Protect nonlocal maintenance sessions by:
- MA-4(4)(a)Employing {{ insert: param, ma-04.04_odp }} ; and
- MA-4(4)(b)Separating the maintenance sessions from other network sessions with the system by either:
- MA-4(4)(b)(1)Physically separated communications paths; or
- MA-4(4)(b)(2)Logically separated communications paths.
- MA-4(5)(a)Require the approval of each nonlocal maintenance session by {{ insert: param, ma-04.05_odp.01 }} ; and
- MA-4(5)(b)Notify the following personnel or roles of the date and time of planned nonlocal maintenance: {{ insert: param, ma-04.05_odp.02 }}.
- MA-4(6)Implement the following cryptographic mechanisms to protect the integrity and confidentiality of nonlocal maintenance and diagnostic communications: {{ insert: param, ma-04.06_odp
- MA-4(7)Verify session and network connection termination after the completion of nonlocal maintenance and diagnostic sessions.
- MA-4aApprove and monitor nonlocal maintenance and diagnostic activities;
- MA-4bAllow the use of nonlocal maintenance and diagnostic tools only as consistent with organizational policy and documented in the security plan for the system;
- MA-4cEmploy strong authentication in the establishment of nonlocal maintenance and diagnostic sessions;
- MA-4dMaintain records for nonlocal maintenance and diagnostic activities; and
- MA-4eTerminate session and network connections when nonlocal maintenance is completed.
- MA-5(1)(a)Implement procedures for the use of maintenance personnel that lack appropriate security clearances or are not U.S. citizens, that include the following requirements:
- MA-5(1)(a)(1)Maintenance personnel who do not have needed access authorizations, clearances, or formal access approvals are escorted and supervised during the performance of maintenance and dia
- MA-5(1)(a)(2)Prior to initiating maintenance or diagnostic activities by personnel who do not have needed access authorizations, clearances or formal access approvals, all volatile information
- MA-5(1)(b)Develop and implement {{ insert: param, ma-05.01_odp }} in the event a system component cannot be sanitized, removed, or disconnected from the system.
- MA-5(2)Verify that personnel performing maintenance and diagnostic activities on a system processing, storing, or transmitting classified information possess security clearances and forma
- MA-5(3)Verify that personnel performing maintenance and diagnostic activities on a system processing, storing, or transmitting classified information are U.S. citizens.
- MA-5(4)Ensure that:
- MA-5(4)(a)Foreign nationals with appropriate security clearances are used to conduct maintenance and diagnostic activities on classified systems only when the systems are jointly owned and o
- MA-5(4)(b)Approvals, consents, and detailed operational conditions regarding the use of foreign nationals to conduct maintenance and diagnostic activities on classified systems are fully doc
- MA-5(5)Ensure that non-escorted personnel performing maintenance activities not directly associated with the system but in the physical proximity of the system, have required access autho
- MA-5aEstablish a process for maintenance personnel authorization and maintain a list of authorized maintenance organizations or personnel;
- MA-5bVerify that non-escorted personnel performing maintenance on the system possess the required access authorizations; and
- MA-5cDesignate organizational personnel with required access authorizations and technical competence to supervise the maintenance activities of personnel who do not possess the required
- MA-6Obtain maintenance support and/or spare parts for {{ insert: param, ma-06_odp.01 }} within {{ insert: param, ma-06_odp.02 }} of failure.
- MA-6(1)Perform preventive maintenance on {{ insert: param, ma-06.01_odp.01 }} at {{ insert: param, ma-06.01_odp.02 }}.
- MA-6(2)Perform predictive maintenance on {{ insert: param, ma-06.02_odp.01 }} at {{ insert: param, ma-06.02_odp.02 }}.
- MA-6(3)Transfer predictive maintenance data to a maintenance management system using {{ insert: param, ma-06.03_odp }}.
- MA-7Restrict or prohibit field maintenance on {{ insert: param, ma-07_odp.01 }} to {{ insert: param, ma-07_odp.02 }}.
- MP-1aDevelop, document, and disseminate to {{ insert: param, mp-1_prm_1 }}:
- MP-1a1{{ insert: param, mp-01_odp.03 }} media protection policy that:
- MP-1a1(a)Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
- MP-1a1(b)Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
- MP-1a2Procedures to facilitate the implementation of the media protection policy and the associated media protection controls;
- MP-1bDesignate an {{ insert: param, mp-01_odp.04 }} to manage the development, documentation, and dissemination of the media protection policy and procedures; and
- MP-1cReview and update the current media protection:
- MP-1c1Policy {{ insert: param, mp-01_odp.05 }} and following {{ insert: param, mp-01_odp.06 }} ; and
- MP-1c2Procedures {{ insert: param, mp-01_odp.07 }} and following {{ insert: param, mp-01_odp.08 }}.
- MP-2Restrict access to {{ insert: param, mp-2_prm_1 }} to {{ insert: param, mp-2_prm_2 }}.
- MP-3aMark system media indicating the distribution limitations, handling caveats, and applicable security markings (if any) of the information; and
- MP-3bExempt {{ insert: param, mp-03_odp.01 }} from marking if the media remain within {{ insert: param, mp-03_odp.02 }}.
- MP-4(2)Restrict access to media storage areas and log access attempts and access granted using {{ insert: param, mp-4.2_prm_1 }}.
- MP-4aPhysically control and securely store {{ insert: param, mp-4_prm_1 }} within {{ insert: param, mp-4_prm_2 }} ; and
- MP-4bProtect system media types defined in MP-4a until the media are destroyed or sanitized using approved equipment, techniques, and procedures.
- MP-5(3)Employ an identified custodian during transport of system media outside of controlled areas.
- MP-5aProtect and control {{ insert: param, mp-05_odp.01 }} during transport outside of controlled areas using {{ insert: param, mp-5_prm_2 }};
- MP-5bMaintain accountability for system media during transport outside of controlled areas;
- MP-5cDocument activities associated with the transport of system media; and
- MP-5dRestrict the activities associated with the transport of system media to authorized personnel.
- MP-6(1)Review, approve, track, document, and verify media sanitization and disposal actions.
- MP-6(2)Test sanitization equipment and procedures {{ insert: param, mp-6.2_prm_1 }} to ensure that the intended sanitization is being achieved.
- MP-6(3)Apply nondestructive sanitization techniques to portable storage devices prior to connecting such devices to the system under the following circumstances: {{ insert: param, mp-06.0
- MP-6(7)Enforce dual authorization for the sanitization of {{ insert: param, mp-06.07_odp }}.
- MP-6(8)Provide the capability to purge or wipe information from {{ insert: param, mp-06.08_odp.01 }} {{ insert: param, mp-06.08_odp.02 }}.
- MP-6aSanitize {{ insert: param, mp-6_prm_1 }} prior to disposal, release out of organizational control, or release for reuse using {{ insert: param, mp-6_prm_2 }} ; and
- MP-6bEmploy sanitization mechanisms with the strength and integrity commensurate with the security category or classification of the information.
- MP-7(2)Prohibit the use of sanitization-resistant media in organizational systems.
- MP-7a{{ insert: param, mp-07_odp.02 }} the use of {{ insert: param, mp-07_odp.01 }} on {{ insert: param, mp-07_odp.03 }} using {{ insert: param, mp-07_odp.04 }} ; and
- MP-7bProhibit the use of portable storage devices in organizational systems when such devices have no identifiable owner.
- MP-8(1)Document system media downgrading actions.
- MP-8(2)Test downgrading equipment and procedures {{ insert: param, mp-8.2_prm_1 }} to ensure that downgrading actions are being achieved.
- MP-8(3)Downgrade system media containing controlled unclassified information prior to public release.
- MP-8(4)Downgrade system media containing classified information prior to release to individuals without required access authorizations.
- MP-8aEstablish {{ insert: param, mp-08_odp.01 }} that includes employing downgrading mechanisms with strength and integrity commensurate with the security category or classification of
- MP-8bVerify that the system media downgrading process is commensurate with the security category and/or classification level of the information to be removed and the access authorizatio
- MP-8cIdentify {{ insert: param, mp-08_odp.02 }} ; and
- MP-8dDowngrade the identified system media using the established process.
- PE-1aDevelop, document, and disseminate to {{ insert: param, pe-1_prm_1 }}:
- PE-1a1{{ insert: param, pe-01_odp.03 }} physical and environmental protection policy that:
- PE-1a1(a)Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
- PE-1a1(b)Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
- PE-1a2Procedures to facilitate the implementation of the physical and environmental protection policy and the associated physical and environmental protection controls;
- PE-1bDesignate an {{ insert: param, pe-01_odp.04 }} to manage the development, documentation, and dissemination of the physical and environmental protection policy and procedures; and
- PE-1cReview and update the current physical and environmental protection:
- PE-1c1Policy {{ insert: param, pe-01_odp.05 }} and following {{ insert: param, pe-01_odp.06 }} ; and
- PE-1c2Procedures {{ insert: param, pe-01_odp.07 }} and following {{ insert: param, pe-01_odp.08 }}.
- PE-2(1)Authorize physical access to the facility where the system resides based on position or role.
- PE-2(2)Require two forms of identification from the following forms of identification for visitor access to the facility where the system resides: {{ insert: param, pe-02.02_odp }}.
- PE-2(3)Restrict unescorted access to the facility where the system resides to personnel with {{ insert: param, pe-02.03_odp.01 }}.
- PE-2aDevelop, approve, and maintain a list of individuals with authorized access to the facility where the system resides;
- PE-2bIssue authorization credentials for facility access;
- PE-2cReview the access list detailing authorized facility access by individuals {{ insert: param, pe-02_odp }} ; and
- PE-2dRemove individuals from the facility access list when access is no longer required.
- PE-3(1)Enforce physical access authorizations to the system in addition to the physical access controls for the facility at {{ insert: param, pe-03.01_odp }}.
- PE-3(2)Perform security checks {{ insert: param, pe-03.02_odp }} at the physical perimeter of the facility or system for exfiltration of information or removal of system components.
- PE-3(3)Employ guards to control {{ insert: param, pe-03.03_odp }} to the facility where the system resides 24 hours per day, 7 days per week.
- PE-3(4)Use lockable physical casings to protect {{ insert: param, pe-03.04_odp }} from unauthorized physical access.
- PE-3(5)Employ {{ insert: param, pe-03.05_odp.01 }} to {{ insert: param, pe-03.05_odp.02 }} physical tampering or alteration of {{ insert: param, pe-03.05_odp.03 }} within the system.
- PE-3(7)Limit access using physical barriers.
- PE-3(8)Employ access control vestibules at {{ insert: param, pe-03.08_odp }}.
- PE-3aEnforce physical access authorizations at {{ insert: param, pe-03_odp.01 }} by:
- PE-3a1Verifying individual access authorizations before granting access to the facility; and
- PE-3a2Controlling ingress and egress to the facility using {{ insert: param, pe-03_odp.02 }};
- PE-3bMaintain physical access audit logs for {{ insert: param, pe-03_odp.04 }};
- PE-3cControl access to areas within the facility designated as publicly accessible by implementing the following controls: {{ insert: param, pe-03_odp.05 }};
- PE-3dEscort visitors and control visitor activity {{ insert: param, pe-03_odp.06 }};
- PE-3eSecure keys, combinations, and other physical access devices;
- PE-3fInventory {{ insert: param, pe-03_odp.07 }} every {{ insert: param, pe-03_odp.08 }} ; and
- PE-3gChange combinations and keys {{ insert: param, pe-3_prm_9 }} and/or when keys are lost, combinations are compromised, or when individuals possessing the keys or combinations are tr
- PE-4Control physical access to {{ insert: param, pe-04_odp.01 }} within organizational facilities using {{ insert: param, pe-04_odp.02 }}.
- PE-5Control physical access to output from {{ insert: param, pe-05_odp }} to prevent unauthorized individuals from obtaining the output.
- PE-5(2)Link individual identity to receipt of output from output devices.
- PE-6(1)Monitor physical access to the facility where the system resides using physical intrusion alarms and surveillance equipment.
- PE-6(2)Recognize {{ insert: param, pe-06.02_odp.01 }} and initiate {{ insert: param, pe-06.02_odp.02 }} using {{ insert: param, pe-06.02_odp.03 }}.
- PE-6(3)(a)Employ video surveillance of {{ insert: param, pe-06.03_odp.01 }};
- PE-6(3)(b)Review video recordings {{ insert: param, pe-06.03_odp.02 }} ; and
- PE-6(3)(c)Retain video recordings for {{ insert: param, pe-06.03_odp.03 }}.
- PE-6(4)Monitor physical access to the system in addition to the physical access monitoring of the facility at {{ insert: param, pe-06.04_odp }}.
- PE-6aMonitor physical access to the facility where the system resides to detect and respond to physical security incidents;
- PE-6bReview physical access logs {{ insert: param, pe-06_odp.01 }} and upon occurrence of {{ insert: param, pe-06_odp.02 }} ; and
- PE-6cCoordinate results of reviews and investigations with the organizational incident response capability.
- PE-8(1)Maintain and review visitor access records using {{ insert: param, pe-8.1_prm_1 }}.
- PE-8(3)Limit personally identifiable information contained in visitor access records to the following elements identified in the privacy risk assessment: {{ insert: param, pe-08.03_odp }}
- PE-8aMaintain visitor access records to the facility where the system resides for {{ insert: param, pe-08_odp.01 }};
- PE-8bReview visitor access records {{ insert: param, pe-08_odp.02 }} ; and
- PE-8cReport anomalies in visitor access records to {{ insert: param, pe-08_odp.03 }}.
- PE-9Protect power equipment and power cabling for the system from damage and destruction.
- PE-9(1)Employ redundant power cabling paths that are physically separated by {{ insert: param, pe-09.01_odp }}.
- PE-9(2)Employ automatic voltage controls for {{ insert: param, pe-09.02_odp }}.
- PE-10aProvide the capability of shutting off power to {{ insert: param, pe-10_odp.01 }} in emergency situations;
- PE-10bPlace emergency shutoff switches or devices in {{ insert: param, pe-10_odp.02 }} to facilitate access for authorized personnel; and
- PE-10cProtect emergency power shutoff capability from unauthorized activation.
- PE-11Provide an uninterruptible power supply to facilitate {{ insert: param, pe-11_odp }} in the event of a primary power source loss.
- PE-11(1)Provide an alternate power supply for the system that is activated {{ insert: param, pe-11.01_odp }} and that can maintain minimally required operational capability in the event of
- PE-11(2)Provide an alternate power supply for the system that is activated {{ insert: param, pe-11.02_odp.01 }} and that is:
- PE-11(2)(a)Self-contained;
- PE-11(2)(b)Not reliant on external power generation; and
- PE-11(2)(c)Capable of maintaining {{ insert: param, pe-11.02_odp.02 }} in the event of an extended loss of the primary power source.
- PE-12Employ and maintain automatic emergency lighting for the system that activates in the event of a power outage or disruption and that covers emergency exits and evacuation routes wi
- PE-12(1)Provide emergency lighting for all areas within the facility supporting essential mission and business functions.
- PE-13Employ and maintain fire detection and suppression systems that are supported by an independent energy source.
- PE-13(1)Employ fire detection systems that activate automatically and notify {{ insert: param, pe-13.01_odp.01 }} and {{ insert: param, pe-13.01_odp.02 }} in the event of a fire.
- PE-13(2)(a)Employ fire suppression systems that activate automatically and notify {{ insert: param, pe-13.02_odp.01 }} and {{ insert: param, pe-13.02_odp.02 }} ; and
- PE-13(2)(b)Employ an automatic fire suppression capability when the facility is not staffed on a continuous basis.
- PE-13(4)Ensure that the facility undergoes {{ insert: param, pe-13.04_odp.01 }} fire protection inspections by authorized and qualified inspectors and identified deficiencies are resolved
- PE-14(1)Employ the following automatic environmental controls in the facility to prevent fluctuations potentially harmful to the system: {{ insert: param, pe-14.01_odp }}.
- PE-14(2)Employ environmental control monitoring that provides an alarm or notification of changes potentially harmful to personnel or equipment to {{ insert: param, pe-14.02_odp }}.
- PE-14aMaintain {{ insert: param, pe-14_odp.01 }} levels within the facility where the system resides at {{ insert: param, pe-14_odp.03 }} ; and
- PE-14bMonitor environmental control levels {{ insert: param, pe-14_odp.04 }}.
- PE-15Protect the system from damage resulting from water leakage by providing master shutoff or isolation valves that are accessible, working properly, and known to key personnel.
- PE-15(1)Detect the presence of water near the system and alert {{ insert: param, pe-15.01_odp.01 }} using {{ insert: param, pe-15.01_odp.02 }}.
- PE-16aAuthorize and control {{ insert: param, pe-16_prm_1 }} entering and exiting the facility; and
- PE-16bMaintain records of the system components.
- PE-17aDetermine and document the {{ insert: param, pe-17_odp.01 }} allowed for use by employees;
- PE-17bEmploy the following controls at alternate work sites: {{ insert: param, pe-17_odp.02 }};
- PE-17cAssess the effectiveness of controls at alternate work sites; and
- PE-17dProvide a means for employees to communicate with information security and privacy personnel in case of incidents.
- PE-18Position system components within the facility to minimize potential damage from {{ insert: param, pe-18_odp }} and to minimize the opportunity for unauthorized access.
- PE-19Protect the system from information leakage due to electromagnetic signals emanations.
- PE-19(1)Protect system components, associated data communications, and networks in accordance with national Emissions Security policies and procedures based on the security category or cla
- PE-20Employ {{ insert: param, pe-20_odp.01 }} to track and monitor the location and movement of {{ insert: param, pe-20_odp.02 }} within {{ insert: param, pe-20_odp.03 }}.
- PE-21Employ {{ insert: param, pe-21_odp.01 }} against electromagnetic pulse damage for {{ insert: param, pe-21_odp.02 }}.
- PE-22Mark {{ insert: param, pe-22_odp }} indicating the impact level or classification level of the information permitted to be processed, stored, or transmitted by the hardware compone
- PE-23aPlan the location or site of the facility where the system resides considering physical and environmental hazards; and
- PE-23bFor existing facilities, consider the physical and environmental hazards in the organizational risk management strategy.
- PL-1aDevelop, document, and disseminate to {{ insert: param, pl-1_prm_1 }}:
- PL-1a1{{ insert: param, pl-01_odp.03 }} planning policy that:
- PL-1a1(a)Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
- PL-1a1(b)Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
- PL-1a2Procedures to facilitate the implementation of the planning policy and the associated planning controls;
- PL-1bDesignate an {{ insert: param, pl-01_odp.04 }} to manage the development, documentation, and dissemination of the planning policy and procedures; and
- PL-1cReview and update the current planning:
- PL-1c1Policy {{ insert: param, pl-01_odp.05 }} and following {{ insert: param, pl-01_odp.06 }} ; and
- PL-1c2Procedures {{ insert: param, pl-01_odp.07 }} and following {{ insert: param, pl-01_odp.08 }}.
- PL-2aDevelop security and privacy plans for the system that:
- PL-2a1Are consistent with the organization’s enterprise architecture;
- PL-2a2Explicitly define the constituent system components;
- PL-2a3Describe the operational context of the system in terms of mission and business processes;
- PL-2a4Identify the individuals that fulfill system roles and responsibilities;
- PL-2a5Identify the information types processed, stored, and transmitted by the system;
- PL-2a6Provide the security categorization of the system, including supporting rationale;
- PL-2a7Describe any specific threats to the system that are of concern to the organization;
- PL-2a8Provide the results of a privacy risk assessment for systems processing personally identifiable information;
- PL-2a9Describe the operational environment for the system and any dependencies on or connections to other systems or system components;
- PL-2a10Provide an overview of the security and privacy requirements for the system;
- PL-2a11Identify any relevant control baselines or overlays, if applicable;
- PL-2a12Describe the controls in place or planned for meeting the security and privacy requirements, including a rationale for any tailoring decisions;
- PL-2a13Include risk determinations for security and privacy architecture and design decisions;
- PL-2a14Include security- and privacy-related activities affecting the system that require planning and coordination with {{ insert: param, pl-02_odp.01 }} ; and
- PL-2a15Are reviewed and approved by the authorizing official or designated representative prior to plan implementation.
- PL-2bDistribute copies of the plans and communicate subsequent changes to the plans to {{ insert: param, pl-02_odp.02 }};
- PL-2cReview the plans {{ insert: param, pl-02_odp.03 }};
- PL-2dUpdate the plans to address changes to the system and environment of operation or problems identified during plan implementation or control assessments; and
- PL-2eProtect the plans from unauthorized disclosure and modification.
- PL-4(1)Include in the rules of behavior, restrictions on:
- PL-4(1)(a)Use of social media, social networking sites, and external sites/applications;
- PL-4(1)(b)Posting organizational information on public websites; and
- PL-4(1)(c)Use of organization-provided identifiers (e.g., email addresses) and authentication secrets (e.g., passwords) for creating accounts on external sites/applications.
- PL-4aEstablish and provide to individuals requiring access to the system, the rules that describe their responsibilities and expected behavior for information and system usage, security
- PL-4bReceive a documented acknowledgment from such individuals, indicating that they have read, understand, and agree to abide by the rules of behavior, before authorizing access to inf
- PL-4cReview and update the rules of behavior {{ insert: param, pl-04_odp.01 }} ; and
- PL-4dRequire individuals who have acknowledged a previous version of the rules of behavior to read and re-acknowledge {{ insert: param, pl-04_odp.02 }}.
- PL-7aDevelop a Concept of Operations (CONOPS) for the system describing how the organization intends to operate the system from the perspective of information security and privacy; and
- PL-7bReview and update the CONOPS {{ insert: param, pl-07_odp }}.
- PL-8(1)Design the security and privacy architectures for the system using a defense-in-depth approach that:
- PL-8(1)(a)Allocates {{ insert: param, pl-08.01_odp.01 }} to {{ insert: param, pl-08.01_odp.02 }} ; and
- PL-8(1)(b)Ensures that the allocated controls operate in a coordinated and mutually reinforcing manner.
- PL-8(2)Require that {{ insert: param, pl-08.02_odp.01 }} allocated to {{ insert: param, pl-08.02_odp.02 }} are obtained from different suppliers.
- PL-8aDevelop security and privacy architectures for the system that:
- PL-8a1Describe the requirements and approach to be taken for protecting the confidentiality, integrity, and availability of organizational information;
- PL-8a2Describe the requirements and approach to be taken for processing personally identifiable information to minimize privacy risk to individuals;
- PL-8a3Describe how the architectures are integrated into and support the enterprise architecture; and
- PL-8a4Describe any assumptions about, and dependencies on, external systems and services;
- PL-8bReview and update the architectures {{ insert: param, pl-08_odp }} to reflect changes in the enterprise architecture; and
- PL-8cReflect planned architecture changes in security and privacy plans, Concept of Operations (CONOPS), criticality analysis, organizational procedures, and procurements and acquisitio
- PL-9Centrally manage {{ insert: param, pl-09_odp }}.
- PL-10Select a control baseline for the system.
- PL-11Tailor the selected control baseline by applying specified tailoring actions.
- PM-1aDevelop and disseminate an organization-wide information security program plan that:
- PM-1a1Provides an overview of the requirements for the security program and a description of the security program management controls and common controls in place or planned for meeting
- PM-1a2Includes the identification and assignment of roles, responsibilities, management commitment, coordination among organizational entities, and compliance;
- PM-1a3Reflects the coordination among organizational entities responsible for information security; and
- PM-1a4Is approved by a senior official with responsibility and accountability for the risk being incurred to organizational operations (including mission, functions, image, and reputatio
- PM-1bReview and update the organization-wide information security program plan {{ insert: param, pm-01_odp.01 }} and following {{ insert: param, pm-01_odp.02 }} ; and
- PM-1cProtect the information security program plan from unauthorized disclosure and modification.
- PM-2Appoint a senior agency information security officer with the mission and resources to coordinate, develop, implement, and maintain an organization-wide information security progra
- PM-3aInclude the resources needed to implement the information security and privacy programs in capital planning and investment requests and document all exceptions to this requirement;
- PM-3bPrepare documentation required for addressing information security and privacy programs in capital planning and investment requests in accordance with applicable laws, executive or
- PM-3cMake available for expenditure, the planned information security and privacy resources.
- PM-4aImplement a process to ensure that plans of action and milestones for the information security, privacy, and supply chain risk management programs and associated organizational sys
- PM-4a1Are developed and maintained;
- PM-4a2Document the remedial information security, privacy, and supply chain risk management actions to adequately respond to risk to organizational operations and assets, individuals, ot
- PM-4a3Are reported in accordance with established reporting requirements.
- PM-4bReview plans of action and milestones for consistency with the organizational risk management strategy and organization-wide priorities for risk response actions.
- PM-5Develop and update {{ insert: param, pm-05_odp }} an inventory of organizational systems.
- PM-5(1)Establish, maintain, and update {{ insert: param, pm-05.01_odp }} an inventory of all systems, applications, and projects that process personally identifiable information.
- PM-6Develop, monitor, and report on the results of information security and privacy measures of performance.
- PM-7Develop and maintain an enterprise architecture with consideration for information security, privacy, and the resulting risk to organizational operations and assets, individuals, o
- PM-7(1)Offload {{ insert: param, pm-07.01_odp }} to other systems, system components, or an external provider.
- PM-8Address information security and privacy issues in the development, documentation, and updating of a critical infrastructure and key resources protection plan.
- PM-9aDevelops a comprehensive strategy to manage:
- PM-9a1Security risk to organizational operations and assets, individuals, other organizations, and the Nation associated with the operation and use of organizational systems; and
- PM-9a2Privacy risk to individuals resulting from the authorized processing of personally identifiable information;
- PM-9bImplement the risk management strategy consistently across the organization; and
- PM-9cReview and update the risk management strategy {{ insert: param, pm-09_odp }} or as required, to address organizational changes.
- PM-10aManage the security and privacy state of organizational systems and the environments in which those systems operate through authorization processes;
- PM-10bDesignate individuals to fulfill specific roles and responsibilities within the organizational risk management process; and
- PM-10cIntegrate the authorization processes into an organization-wide risk management program.
- PM-11aDefine organizational mission and business processes with consideration for information security and privacy and the resulting risk to organizational operations, organizational ass
- PM-11bDetermine information protection and personally identifiable information processing needs arising from the defined mission and business processes; and
- PM-11cReview and revise the mission and business processes {{ insert: param, pm-11_odp }}.
- PM-12Implement an insider threat program that includes a cross-discipline insider threat incident handling team.
- PM-13Establish a security and privacy workforce development and improvement program.
- PM-14aImplement a process for ensuring that organizational plans for conducting security and privacy testing, training, and monitoring activities associated with organizational systems:
- PM-14a1Are developed and maintained; and
← records 401–800 · All of Security and compliance controls, one provision at a time: NIST SP 800-53 and the HIPAA Security Rule in their own words · records 1,201 on →