Records 1,201–1,600 — 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 to 1,600 of 2,022. Each links to its own page, which carries the source URL and the quoted line that states the value.
- PM-14a2Continue to be executed; and
- PM-14bReview testing, training, and monitoring plans for consistency with the organizational risk management strategy and organization-wide priorities for risk response actions.
- PM-15Establish and institutionalize contact with selected groups and associations within the security and privacy communities:
- PM-15aTo facilitate ongoing security and privacy education and training for organizational personnel;
- PM-15bTo maintain currency with recommended security and privacy practices, techniques, and technologies; and
- PM-15cTo share current security and privacy information, including threats, vulnerabilities, and incidents.
- PM-16Implement a threat awareness program that includes a cross-organization information-sharing capability for threat intelligence.
- PM-16(1)Employ automated mechanisms to maximize the effectiveness of sharing threat intelligence information.
- PM-17aEstablish policy and procedures to ensure that requirements for the protection of controlled unclassified information that is processed, stored or transmitted on external systems,
- PM-17bReview and update the policy and procedures {{ insert: param, pm-17_prm_1 }}.
- PM-18aDevelop and disseminate an organization-wide privacy program plan that provides an overview of the agency’s privacy program, and:
- PM-18a1Includes a description of the structure of the privacy program and the resources dedicated to the privacy program;
- PM-18a2Provides an overview of the requirements for the privacy program and a description of the privacy program management controls and common controls in place or planned for meeting th
- PM-18a3Includes the role of the senior agency official for privacy and the identification and assignment of roles of other privacy officials and staff and their responsibilities;
- PM-18a4Describes management commitment, compliance, and the strategic goals and objectives of the privacy program;
- PM-18a5Reflects coordination among organizational entities responsible for the different aspects of privacy; and
- PM-18a6Is approved by a senior official with responsibility and accountability for the privacy risk being incurred to organizational operations (including mission, functions, image, and r
- PM-18bUpdate the plan {{ insert: param, pm-18_odp }} and to address changes in federal privacy laws and policy and organizational changes and problems identified during plan implementati
- PM-19Appoint a senior agency official for privacy with the authority, mission, accountability, and resources to coordinate, develop, and implement, applicable privacy requirements and m
- PM-20Maintain a central resource webpage on the organization’s principal public website that serves as a central source of information about the organization’s privacy program and that:
- PM-20(1)Develop and post privacy policies on all external-facing websites, mobile applications, and other digital services, that:
- PM-20(1)(a)Are written in plain language and organized in a way that is easy to understand and navigate;
- PM-20(1)(b)Provide information needed by the public to make an informed decision about whether and how to interact with the organization; and
- PM-20(1)(c)Are updated whenever the organization makes a substantive change to the practices it describes and includes a time/date stamp to inform the public of the date of the most recent ch
- PM-20aEnsures that the public has access to information about organizational privacy activities and can communicate with its senior agency official for privacy;
- PM-20bEnsures that organizational privacy practices and reports are publicly available; and
- PM-20cEmploys publicly facing email addresses and/or phone lines to enable the public to provide feedback and/or direct questions to privacy offices regarding privacy practices.
- PM-21aDevelop and maintain an accurate accounting of disclosures of personally identifiable information, including:
- PM-21a1Date, nature, and purpose of each disclosure; and
- PM-21a2Name and address, or other contact information of the individual or organization to which the disclosure was made;
- PM-21bRetain the accounting of disclosures for the length of the time the personally identifiable information is maintained or five years after the disclosure is made, whichever is longe
- PM-21cMake the accounting of disclosures available to the individual to whom the personally identifiable information relates upon request.
- PM-22Develop and document organization-wide policies and procedures for:
- PM-22aReviewing for the accuracy, relevance, timeliness, and completeness of personally identifiable information across the information life cycle;
- PM-22bCorrecting or deleting inaccurate or outdated personally identifiable information;
- PM-22cDisseminating notice of corrected or deleted personally identifiable information to individuals or other appropriate entities; and
- PM-22dAppeals of adverse decisions on correction or deletion requests.
- PM-23Establish a Data Governance Body consisting of {{ insert: param, pm-23_odp.01 }} with {{ insert: param, pm-23_odp.02 }}.
- PM-24Establish a Data Integrity Board to:
- PM-24aReview proposals to conduct or participate in a matching program; and
- PM-24bConduct an annual review of all matching programs in which the agency has participated.
- PM-25aDevelop, document, and implement policies and procedures that address the use of personally identifiable information for internal testing, training, and research;
- PM-25bLimit or minimize the amount of personally identifiable information used for internal testing, training, and research purposes;
- PM-25cAuthorize the use of personally identifiable information when such information is required for internal testing, training, and research; and
- PM-25dReview and update policies and procedures {{ insert: param, pm-25_prm_1 }}.
- PM-26Implement a process for receiving and responding to complaints, concerns, or questions from individuals about the organizational security and privacy practices that includes:
- PM-26aMechanisms that are easy to use and readily accessible by the public;
- PM-26bAll information necessary for successfully filing complaints;
- PM-26cTracking mechanisms to ensure all complaints received are reviewed and addressed within {{ insert: param, pm-26_prm_1 }};
- PM-26dAcknowledgement of receipt of complaints, concerns, or questions from individuals within {{ insert: param, pm-26_odp.03 }} ; and
- PM-26eResponse to complaints, concerns, or questions from individuals within {{ insert: param, pm-26_odp.04 }}.
- PM-27aDevelop {{ insert: param, pm-27_odp.01 }} and disseminate to:
- PM-27a1{{ insert: param, pm-27_odp.02 }} to demonstrate accountability with statutory, regulatory, and policy privacy mandates; and
- PM-27a2{{ insert: param, pm-27_odp.03 }} and other personnel with responsibility for monitoring privacy program compliance; and
- PM-27bReview and update privacy reports {{ insert: param, pm-27_odp.04 }}.
- PM-28aIdentify and document:
- PM-28a1Assumptions affecting risk assessments, risk responses, and risk monitoring;
- PM-28a2Constraints affecting risk assessments, risk responses, and risk monitoring;
- PM-28a3Priorities and trade-offs considered by the organization for managing risk; and
- PM-28a4Organizational risk tolerance;
- PM-28bDistribute the results of risk framing activities to {{ insert: param, pm-28_odp.01 }} ; and
- PM-28cReview and update risk framing considerations {{ insert: param, pm-28_odp.02 }}.
- PM-29aAppoint a Senior Accountable Official for Risk Management to align organizational information security and privacy management processes with strategic, operational, and budgetary p
- PM-29bEstablish a Risk Executive (function) to view and analyze risk from an organization-wide perspective and ensure management of risk is consistent across the organization.
- PM-30(1)Identify, prioritize, and assess suppliers of critical or mission-essential technologies, products, and services.
- PM-30aDevelop an organization-wide strategy for managing supply chain risks associated with the development, acquisition, maintenance, and disposal of systems, system components, and sys
- PM-30bImplement the supply chain risk management strategy consistently across the organization; and
- PM-30cReview and update the supply chain risk management strategy on {{ insert: param, pm-30_odp }} or as required, to address organizational changes.
- PM-31Develop an organization-wide continuous monitoring strategy and implement continuous monitoring programs that include:
- PM-31aEstablishing the following organization-wide metrics to be monitored: {{ insert: param, pm-31_odp.01 }};
- PM-31bEstablishing {{ insert: param, pm-31_odp.02 }} and {{ insert: param, pm-31_odp.03 }} for control effectiveness;
- PM-31cOngoing monitoring of organizationally-defined metrics in accordance with the continuous monitoring strategy;
- PM-31dCorrelation and analysis of information generated by control assessments and monitoring;
- PM-31eResponse actions to address results of the analysis of control assessment and monitoring information; and
- PM-31fReporting the security and privacy status of organizational systems to {{ insert: param, pm-31_prm_4 }} {{ insert: param, pm-31_prm_5 }}.
- PM-32Analyze {{ insert: param, pm-32_odp }} supporting mission essential services or functions to ensure that the information resources are being used consistent with their intended pur
- PS-1aDevelop, document, and disseminate to {{ insert: param, ps-1_prm_1 }}:
- PS-1a1{{ insert: param, ps-01_odp.03 }} personnel security policy that:
- PS-1a1(a)Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
- PS-1a1(b)Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
- PS-1a2Procedures to facilitate the implementation of the personnel security policy and the associated personnel security controls;
- PS-1bDesignate an {{ insert: param, ps-01_odp.04 }} to manage the development, documentation, and dissemination of the personnel security policy and procedures; and
- PS-1cReview and update the current personnel security:
- PS-1c1Policy {{ insert: param, ps-01_odp.05 }} and following {{ insert: param, ps-01_odp.06 }} ; and
- PS-1c2Procedures {{ insert: param, ps-01_odp.07 }} and following {{ insert: param, ps-01_odp.08 }}.
- PS-2aAssign a risk designation to all organizational positions;
- PS-2bEstablish screening criteria for individuals filling those positions; and
- PS-2cReview and update position risk designations {{ insert: param, ps-02_odp }}.
- PS-3(1)Verify that individuals accessing a system processing, storing, or transmitting classified information are cleared and indoctrinated to the highest classification level of the info
- PS-3(2)Verify that individuals accessing a system processing, storing, or transmitting types of classified information that require formal indoctrination, are formally indoctrinated for a
- PS-3(3)Verify that individuals accessing a system processing, storing, or transmitting information requiring special protection:
- PS-3(3)(a)Have valid access authorizations that are demonstrated by assigned official government duties; and
- PS-3(3)(b)Satisfy {{ insert: param, ps-03.03_odp }}.
- PS-3(4)Verify that individuals accessing a system processing, storing, or transmitting {{ insert: param, ps-03.04_odp.01 }} meet {{ insert: param, ps-03.04_odp.02 }}.
- PS-3aScreen individuals prior to authorizing access to the system; and
- PS-3bRescreen individuals in accordance with {{ insert: param, ps-3_prm_1 }}.
- PS-4Upon termination of individual employment:
- PS-4(1)(a)Notify terminated individuals of applicable, legally binding post-employment requirements for the protection of organizational information; and
- PS-4(1)(b)Require terminated individuals to sign an acknowledgment of post-employment requirements as part of the organizational termination process.
- PS-4(2)Use {{ insert: param, ps-04.02_odp.01 }} to {{ insert: param, ps-04.02_odp.02 }}.
- PS-4aDisable system access within {{ insert: param, ps-04_odp.01 }};
- PS-4bTerminate or revoke any authenticators and credentials associated with the individual;
- PS-4cConduct exit interviews that include a discussion of {{ insert: param, ps-04_odp.02 }};
- PS-4dRetrieve all security-related organizational system-related property; and
- PS-4eRetain access to organizational information and systems formerly controlled by terminated individual.
- PS-5aReview and confirm ongoing operational need for current logical and physical access authorizations to systems and facilities when individuals are reassigned or transferred to other
- PS-5bInitiate {{ insert: param, ps-05_odp.01 }} within {{ insert: param, ps-05_odp.02 }};
- PS-5cModify access authorization as needed to correspond with any changes in operational need due to reassignment or transfer; and
- PS-5dNotify {{ insert: param, ps-05_odp.03 }} within {{ insert: param, ps-05_odp.04 }}.
- PS-6(2)Verify that access to classified information requiring special protection is granted only to individuals who:
- PS-6(2)(a)Have a valid access authorization that is demonstrated by assigned official government duties;
- PS-6(2)(b)Satisfy associated personnel security criteria; and
- PS-6(2)(c)Have read, understood, and signed a nondisclosure agreement.
- PS-6(3)(a)Notify individuals of applicable, legally binding post-employment requirements for protection of organizational information; and
- PS-6(3)(b)Require individuals to sign an acknowledgment of these requirements, if applicable, as part of granting initial access to covered information.
- PS-6aDevelop and document access agreements for organizational systems;
- PS-6bReview and update the access agreements {{ insert: param, ps-06_odp.01 }} ; and
- PS-6cVerify that individuals requiring access to organizational information and systems:
- PS-6c1Sign appropriate access agreements prior to being granted access; and
- PS-6c2Re-sign access agreements to maintain access to organizational systems when access agreements have been updated or {{ insert: param, ps-06_odp.02 }}.
- PS-7aEstablish personnel security requirements, including security roles and responsibilities for external providers;
- PS-7bRequire external providers to comply with personnel security policies and procedures established by the organization;
- PS-7cDocument personnel security requirements;
- PS-7dRequire external providers to notify {{ insert: param, ps-07_odp.01 }} of any personnel transfers or terminations of external personnel who possess organizational credentials and/o
- PS-7eMonitor provider compliance with personnel security requirements.
- PS-8aEmploy a formal sanctions process for individuals failing to comply with established information security and privacy policies and procedures; and
- PS-8bNotify {{ insert: param, ps-08_odp.01 }} within {{ insert: param, ps-08_odp.02 }} when a formal employee sanctions process is initiated, identifying the individual sanctioned and t
- PS-9Incorporate security and privacy roles and responsibilities into organizational position descriptions.
- PT-1aDevelop, document, and disseminate to {{ insert: param, pt-1_prm_1 }}:
- PT-1a1{{ insert: param, pt-01_odp.03 }} personally identifiable information processing and transparency policy that:
- PT-1a1(a)Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
- PT-1a1(b)Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
- PT-1a2Procedures to facilitate the implementation of the personally identifiable information processing and transparency policy and the associated personally identifiable information pro
- PT-1bDesignate an {{ insert: param, pt-01_odp.04 }} to manage the development, documentation, and dissemination of the personally identifiable information processing and transparency po
- PT-1cReview and update the current personally identifiable information processing and transparency:
- PT-1c1Policy {{ insert: param, pt-01_odp.05 }} and following {{ insert: param, pt-01_odp.06 }} ; and
- PT-1c2Procedures {{ insert: param, pt-01_odp.07 }} and following {{ insert: param, pt-01_odp.08 }}.
- PT-2(1)Attach data tags containing {{ insert: param, pt-02.01_odp.01 }} to {{ insert: param, pt-02.01_odp.02 }}.
- PT-2(2)Manage enforcement of the authorized processing of personally identifiable information using {{ insert: param, pt-02.02_odp }}.
- PT-2aDetermine and document the {{ insert: param, pt-02_odp.01 }} that permits the {{ insert: param, pt-02_odp.02 }} of personally identifiable information; and
- PT-2bRestrict the {{ insert: param, pt-02_odp.03 }} of personally identifiable information to only that which is authorized.
- PT-3(1)Attach data tags containing the following purposes to {{ insert: param, pt-03.01_odp.02 }}: {{ insert: param, pt-03.01_odp.01 }}.
- PT-3(2)Track processing purposes of personally identifiable information using {{ insert: param, pt-03.02_odp }}.
- PT-3aIdentify and document the {{ insert: param, pt-03_odp.01 }} for processing personally identifiable information;
- PT-3bDescribe the purpose(s) in the public privacy notices and policies of the organization;
- PT-3cRestrict the {{ insert: param, pt-03_odp.02 }} of personally identifiable information to only that which is compatible with the identified purpose(s); and
- PT-3dMonitor changes in processing personally identifiable information and implement {{ insert: param, pt-03_odp.03 }} to ensure that any changes are made in accordance with {{ insert:
- PT-4Implement {{ insert: param, pt-04_odp }} for individuals to consent to the processing of their personally identifiable information prior to its collection that facilitate individua
- PT-4(1)Provide {{ insert: param, pt-04.01_odp }} to allow individuals to tailor processing permissions to selected elements of personally identifiable information.
- PT-4(2)Present {{ insert: param, pt-04.02_odp.01 }} to individuals at {{ insert: param, pt-04.02_odp.02 }} and in conjunction with {{ insert: param, pt-04.02_odp.03 }}.
- PT-4(3)Implement {{ insert: param, pt-04.03_odp }} for individuals to revoke consent to the processing of their personally identifiable information.
- PT-5Provide notice to individuals about the processing of personally identifiable information that:
- PT-5(1)Present notice of personally identifiable information processing to individuals at a time and location where the individual provides personally identifiable information or in conju
- PT-5(2)Include Privacy Act statements on forms that collect information that will be maintained in a Privacy Act system of records, or provide Privacy Act statements on separate forms tha
- PT-5aIs available to individuals upon first interacting with an organization, and subsequently at {{ insert: param, pt-05_odp.01 }};
- PT-5bIs clear and easy-to-understand, expressing information about personally identifiable information processing in plain language;
- PT-5cIdentifies the authority that authorizes the processing of personally identifiable information;
- PT-5dIdentifies the purposes for which personally identifiable information is to be processed; and
- PT-5eIncludes {{ insert: param, pt-05_odp.02 }}.
- PT-6For systems that process information that will be maintained in a Privacy Act system of records:
- PT-6(1)Review all routine uses published in the system of records notice at {{ insert: param, pt-06.01_odp }} to ensure continued accuracy, and to ensure that routine uses continue to be
- PT-6(2)Review all Privacy Act exemptions claimed for the system of records at {{ insert: param, pt-06.02_odp }} to ensure they remain appropriate and necessary in accordance with law, tha
- PT-6aDraft system of records notices in accordance with OMB guidance and submit new and significantly modified system of records notices to the OMB and appropriate congressional committ
- PT-6bPublish system of records notices in the Federal Register; and
- PT-6cKeep system of records notices accurate, up-to-date, and scoped in accordance with policy.
- PT-7Apply {{ insert: param, pt-07_odp }} for specific categories of personally identifiable information.
- PT-7(1)When a system processes Social Security numbers:
- PT-7(1)(a)Eliminate unnecessary collection, maintenance, and use of Social Security numbers, and explore alternatives to their use as a personal identifier;
- PT-7(1)(b)Do not deny any individual any right, benefit, or privilege provided by law because of such individual’s refusal to disclose his or her Social Security number; and
- PT-7(1)(c)Inform any individual who is asked to disclose his or her Social Security number whether that disclosure is mandatory or voluntary, by what statutory or other authority such number
- PT-7(2)Prohibit the processing of information describing how any individual exercises rights guaranteed by the First Amendment unless expressly authorized by statute or by the individual
- PT-8When a system or organization processes information for the purpose of conducting a matching program:
- PT-8aObtain approval from the Data Integrity Board to conduct the matching program;
- PT-8bDevelop and enter into a computer matching agreement;
- PT-8cPublish a matching notice in the Federal Register;
- PT-8dIndependently verify the information produced by the matching program before taking adverse action against an individual, if required; and
- PT-8eProvide individuals with notice and an opportunity to contest the findings before taking adverse action against an individual.
- RA-1aDevelop, document, and disseminate to {{ insert: param, ra-1_prm_1 }}:
- RA-1a1{{ insert: param, ra-01_odp.03 }} risk assessment policy that:
- RA-1a1(a)Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
- RA-1a1(b)Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
- RA-1a2Procedures to facilitate the implementation of the risk assessment policy and the associated risk assessment controls;
- RA-1bDesignate an {{ insert: param, ra-01_odp.04 }} to manage the development, documentation, and dissemination of the risk assessment policy and procedures; and
- RA-1cReview and update the current risk assessment:
- RA-1c1Policy {{ insert: param, ra-01_odp.05 }} and following {{ insert: param, ra-01_odp.06 }} ; and
- RA-1c2Procedures {{ insert: param, ra-01_odp.07 }} and following {{ insert: param, ra-01_odp.08 }}.
- RA-2(1)Conduct an impact-level prioritization of organizational systems to obtain additional granularity on system impact levels.
- RA-2aCategorize the system and information it processes, stores, and transmits;
- RA-2bDocument the security categorization results, including supporting rationale, in the security plan for the system; and
- RA-2cVerify that the authorizing official or authorizing official designated representative reviews and approves the security categorization decision.
- RA-3(1)(a)Assess supply chain risks associated with {{ insert: param, ra-03.01_odp.01 }} ; and
- RA-3(1)(b)Update the supply chain risk assessment {{ insert: param, ra-03.01_odp.02 }} , when there are significant changes to the relevant supply chain, or when changes to the system, envir
- RA-3(2)Use all-source intelligence to assist in the analysis of risk.
- RA-3(3)Determine the current cyber threat environment on an ongoing basis using {{ insert: param, ra-03.03_odp }}.
- RA-3(4)Employ the following advanced automation and analytics capabilities to predict and identify risks to {{ insert: param, ra-03.04_odp.02 }}: {{ insert: param, ra-3.4_prm_2 }}.
- RA-3aConduct a risk assessment, including:
- RA-3a1Identifying threats to and vulnerabilities in the system;
- RA-3a2Determining the likelihood and magnitude of harm from unauthorized access, use, disclosure, disruption, modification, or destruction of the system, the information it processes, st
- RA-3a3Determining the likelihood and impact of adverse effects on individuals arising from the processing of personally identifiable information;
- RA-3bIntegrate risk assessment results and risk management decisions from the organization and mission or business process perspectives with system-level risk assessments;
- RA-3cDocument risk assessment results in {{ insert: param, ra-03_odp.01 }};
- RA-3dReview risk assessment results {{ insert: param, ra-03_odp.03 }};
- RA-3eDisseminate risk assessment results to {{ insert: param, ra-03_odp.04 }} ; and
- RA-3fUpdate the risk assessment {{ insert: param, ra-03_odp.05 }} or when there are significant changes to the system, its environment of operation, or other conditions that may impact
- RA-5(2)Update the system vulnerabilities to be scanned {{ insert: param, ra-05.02_odp.01 }}.
- RA-5(3)Define the breadth and depth of vulnerability scanning coverage.
- RA-5(4)Determine information about the system that is discoverable and take {{ insert: param, ra-05.04_odp }}.
- RA-5(5)Implement privileged access authorization to {{ insert: param, ra-05.05_odp.01 }} for {{ insert: param, ra-05.05_odp.02 }}.
- RA-5(6)Compare the results of multiple vulnerability scans using {{ insert: param, ra-05.06_odp }}.
- RA-5(8)Review historic audit logs to determine if a vulnerability identified in a {{ insert: param, ra-05.08_odp.01 }} has been previously exploited within an {{ insert: param, ra-05.08_o
- RA-5(10)Correlate the output from vulnerability scanning tools to determine the presence of multi-vulnerability and multi-hop attack vectors.
- RA-5(11)Establish a public reporting channel for receiving reports of vulnerabilities in organizational systems and system components.
- RA-5aMonitor and scan for vulnerabilities in the system and hosted applications {{ insert: param, ra-5_prm_1 }} and when new vulnerabilities potentially affecting the system are identif
- RA-5bEmploy vulnerability monitoring tools and techniques that facilitate interoperability among tools and automate parts of the vulnerability management process by using standards for:
- RA-5b1Enumerating platforms, software flaws, and improper configurations;
- RA-5b2Formatting checklists and test procedures; and
- RA-5b3Measuring vulnerability impact;
- RA-5cAnalyze vulnerability scan reports and results from vulnerability monitoring;
- RA-5dRemediate legitimate vulnerabilities {{ insert: param, ra-05_odp.03 }} in accordance with an organizational assessment of risk;
- RA-5eShare information obtained from the vulnerability monitoring process and control assessments with {{ insert: param, ra-05_odp.04 }} to help eliminate similar vulnerabilities in oth
- RA-5fEmploy vulnerability monitoring tools that include the capability to readily update the vulnerabilities to be scanned.
- RA-6Employ a technical surveillance countermeasures survey at {{ insert: param, ra-06_odp.01 }} {{ insert: param, ra-06_odp.02 }}.
- RA-7Respond to findings from security and privacy assessments, monitoring, and audits in accordance with organizational risk tolerance.
- RA-8Conduct privacy impact assessments for systems, programs, or other activities before:
- RA-8aDeveloping or procuring information technology that processes personally identifiable information; and
- RA-8bInitiating a new collection of personally identifiable information that:
- RA-8b1Will be processed using information technology; and
- RA-8b2Includes personally identifiable information permitting the physical or virtual (online) contacting of a specific individual, if identical questions have been posed to, or identica
- RA-9Identify critical system components and functions by performing a criticality analysis for {{ insert: param, ra-09_odp.01 }} at {{ insert: param, ra-09_odp.02 }}.
- RA-10aEstablish and maintain a cyber threat hunting capability to:
- RA-10a1Search for indicators of compromise in organizational systems; and
- RA-10a2Detect, track, and disrupt threats that evade existing controls; and
- RA-10bEmploy the threat hunting capability {{ insert: param, ra-10_odp }}.
- SA-1aDevelop, document, and disseminate to {{ insert: param, sa-1_prm_1 }}:
- SA-1a1{{ insert: param, sa-01_odp.03 }} system and services acquisition policy that:
- SA-1a1(a)Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
- SA-1a1(b)Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
- SA-1a2Procedures to facilitate the implementation of the system and services acquisition policy and the associated system and services acquisition controls;
- SA-1bDesignate an {{ insert: param, sa-01_odp.04 }} to manage the development, documentation, and dissemination of the system and services acquisition policy and procedures; and
- SA-1cReview and update the current system and services acquisition:
- SA-1c1Policy {{ insert: param, sa-01_odp.05 }} and following {{ insert: param, sa-01_odp.06 }} ; and
- SA-1c2Procedures {{ insert: param, sa-01_odp.07 }} and following {{ insert: param, sa-01_odp.08 }}.
- SA-2aDetermine the high-level information security and privacy requirements for the system or system service in mission and business process planning;
- SA-2bDetermine, document, and allocate the resources required to protect the system or system service as part of the organizational capital planning and investment control process; and
- SA-2cEstablish a discrete line item for information security and privacy in organizational programming and budgeting documentation.
- SA-3(1)Protect system preproduction environments commensurate with risk throughout the system development life cycle for the system, system component, or system service.
- SA-3(2)(a)Approve, document, and control the use of live data in preproduction environments for the system, system component, or system service; and
- SA-3(2)(b)Protect preproduction environments for the system, system component, or system service at the same impact or classification level as any live data in use within the preproduction e
- SA-3(3)Plan for and implement a technology refresh schedule for the system throughout the system development life cycle.
- SA-3aAcquire, develop, and manage the system using {{ insert: param, sa-03_odp }} that incorporates information security and privacy considerations;
- SA-3bDefine and document information security and privacy roles and responsibilities throughout the system development life cycle;
- SA-3cIdentify individuals having information security and privacy roles and responsibilities; and
- SA-3dIntegrate the organizational information security and privacy risk management process into system development life cycle activities.
- SA-4Include the following requirements, descriptions, and criteria, explicitly or by reference, using {{ insert: param, sa-04_odp.01 }} in the acquisition contract for the system, syst
- SA-4(1)Require the developer of the system, system component, or system service to provide a description of the functional properties of the controls to be implemented.
- SA-4(2)Require the developer of the system, system component, or system service to provide design and implementation information for the controls that includes: {{ insert: param, sa-04.02
- SA-4(3)Require the developer of the system, system component, or system service to demonstrate the use of a system development life cycle process that includes:
- SA-4(3)(a){{ insert: param, sa-04.03_odp.01 }};
- SA-4(3)(b){{ insert: param, sa-04.03_odp.02 }} ; and
- SA-4(3)(c){{ insert: param, sa-04.03_odp.05 }}.
- SA-4(5)Require the developer of the system, system component, or system service to:
- SA-4(5)(a)Deliver the system, component, or service with {{ insert: param, sa-04.05_odp }} implemented; and
- SA-4(5)(b)Use the configurations as the default for any subsequent system, component, or service reinstallation or upgrade.
- SA-4(6)(a)Employ only government off-the-shelf or commercial off-the-shelf information assurance and information assurance-enabled information technology products that compose an NSA-approve
- SA-4(6)(b)Ensure that these products have been evaluated and/or validated by NSA or in accordance with NSA-approved procedures.
- SA-4(7)(a)Limit the use of commercially provided information assurance and information assurance-enabled information technology products to those products that have been successfully evaluat
- SA-4(7)(b)Require, if no NIAP-approved Protection Profile exists for a specific technology type but a commercially provided information technology product relies on cryptographic functionali
- SA-4(8)Require the developer of the system, system component, or system service to produce a plan for continuous monitoring of control effectiveness that is consistent with the continuous
- SA-4(9)Require the developer of the system, system component, or system service to identify the functions, ports, protocols, and services intended for organizational use.
- SA-4(10)Employ only information technology products on the FIPS 201-approved products list for Personal Identity Verification (PIV) capability implemented within organizational systems.
- SA-4(11)Include {{ insert: param, sa-04.11_odp }} in the acquisition contract for the operation of a system of records on behalf of an organization to accomplish an organizational mission
- SA-4(12)(a)Include organizational data ownership requirements in the acquisition contract; and
- SA-4(12)(b)Require all data to be removed from the contractor’s system and returned to the organization within {{ insert: param, sa-04.12_odp }}.
- SA-4aSecurity and privacy functional requirements;
- SA-4bStrength of mechanism requirements;
- SA-4cSecurity and privacy assurance requirements;
- SA-4dControls needed to satisfy the security and privacy requirements.
- SA-4eSecurity and privacy documentation requirements;
- SA-4fRequirements for protecting security and privacy documentation;
- SA-4gDescription of the system development environment and environment in which the system is intended to operate;
- SA-4hAllocation of responsibility or identification of parties responsible for information security, privacy, and supply chain risk management; and
- SA-4iAcceptance criteria.
- SA-5aObtain or develop administrator documentation for the system, system component, or system service that describes:
- SA-5a1Secure configuration, installation, and operation of the system, component, or service;
- SA-5a2Effective use and maintenance of security and privacy functions and mechanisms; and
- SA-5a3Known vulnerabilities regarding configuration and use of administrative or privileged functions;
- SA-5bObtain or develop user documentation for the system, system component, or system service that describes:
- SA-5b1User-accessible security and privacy functions and mechanisms and how to effectively use those functions and mechanisms;
- SA-5b2Methods for user interaction, which enables individuals to use the system, component, or service in a more secure manner and protect individual privacy; and
- SA-5b3User responsibilities in maintaining the security of the system, component, or service and privacy of individuals;
- SA-5cDocument attempts to obtain system, system component, or system service documentation when such documentation is either unavailable or nonexistent and take {{ insert: param, sa-05_
- SA-5dDistribute documentation to {{ insert: param, sa-05_odp.02 }}.
- SA-8Apply the following systems security and privacy engineering principles in the specification, design, development, implementation, and modification of the system and system compone
- SA-8(1)Implement the security design principle of clear abstractions.
- SA-8(2)Implement the security design principle of least common mechanism in {{ insert: param, sa-08.02_odp }}.
- SA-8(3)Implement the security design principles of modularity and layering in {{ insert: param, sa-8.3_prm_1 }}.
- SA-8(4)Implement the security design principle of partially ordered dependencies in {{ insert: param, sa-08.04_odp }}.
- SA-8(5)Implement the security design principle of efficiently mediated access in {{ insert: param, sa-08.05_odp }}.
- SA-8(6)Implement the security design principle of minimized sharing in {{ insert: param, sa-08.06_odp }}.
- SA-8(7)Implement the security design principle of reduced complexity in {{ insert: param, sa-08.07_odp }}.
- SA-8(8)Implement the security design principle of secure evolvability in {{ insert: param, sa-08.08_odp }}.
- SA-8(9)Implement the security design principle of trusted components in {{ insert: param, sa-08.09_odp }}.
- SA-8(10)Implement the security design principle of hierarchical trust in {{ insert: param, sa-08.10_odp }}.
- SA-8(11)Implement the security design principle of inverse modification threshold in {{ insert: param, sa-08.11_odp }}.
- SA-8(12)Implement the security design principle of hierarchical protection in {{ insert: param, sa-08.12_odp }}.
- SA-8(13)Implement the security design principle of minimized security elements in {{ insert: param, sa-08.13_odp }}.
- SA-8(14)Implement the security design principle of least privilege in {{ insert: param, sa-08.14_odp }}.
- SA-8(15)Implement the security design principle of predicate permission in {{ insert: param, sa-08.15_odp }}.
- SA-8(16)Implement the security design principle of self-reliant trustworthiness in {{ insert: param, sa-08.16_odp }}.
- SA-8(17)Implement the security design principle of secure distributed composition in {{ insert: param, sa-08.17_odp }}.
- SA-8(18)Implement the security design principle of trusted communications channels in {{ insert: param, sa-08.18_odp }}.
- SA-8(19)Implement the security design principle of continuous protection in {{ insert: param, sa-08.19_odp }}.
- SA-8(20)Implement the security design principle of secure metadata management in {{ insert: param, sa-08.20_odp }}.
- SA-8(21)Implement the security design principle of self-analysis in {{ insert: param, sa-08.21_odp }}.
- SA-8(22)Implement the security design principle of accountability and traceability in {{ insert: param, sa-8.22_prm_1 }}.
- SA-8(23)Implement the security design principle of secure defaults in {{ insert: param, sa-08.23_odp }}.
- SA-8(24)Implement the security design principle of secure failure and recovery in {{ insert: param, sa-8.24_prm_1 }}.
- SA-8(25)Implement the security design principle of economic security in {{ insert: param, sa-08.25_odp }}.
- SA-8(26)Implement the security design principle of performance security in {{ insert: param, sa-08.26_odp }}.
- SA-8(27)Implement the security design principle of human factored security in {{ insert: param, sa-08.27_odp }}.
- SA-8(28)Implement the security design principle of acceptable security in {{ insert: param, sa-08.28_odp }}.
- SA-8(29)Implement the security design principle of repeatable and documented procedures in {{ insert: param, sa-08.29_odp }}.
- SA-8(30)Implement the security design principle of procedural rigor in {{ insert: param, sa-08.30_odp }}.
- SA-8(31)Implement the security design principle of secure system modification in {{ insert: param, sa-08.31_odp }}.
- SA-8(32)Implement the security design principle of sufficient documentation in {{ insert: param, sa-08.32_odp }}.
- SA-8(33)Implement the privacy principle of minimization using {{ insert: param, sa-08.33_odp }}.
- SA-9(1)(a)Conduct an organizational assessment of risk prior to the acquisition or outsourcing of information security services; and
- SA-9(1)(b)Verify that the acquisition or outsourcing of dedicated information security services is approved by {{ insert: param, sa-09.01_odp }}.
- SA-9(2)Require providers of the following external system services to identify the functions, ports, protocols, and other services required for the use of such services: {{ insert: param,
- SA-9(3)Establish, document, and maintain trust relationships with external service providers based on the following requirements, properties, factors, or conditions: {{ insert: param, sa-
- SA-9(4)Take the following actions to verify that the interests of {{ insert: param, sa-09.04_odp.01 }} are consistent with and reflect organizational interests: {{ insert: param, sa-09.04
- SA-9(5)Restrict the location of {{ insert: param, sa-09.05_odp.01 }} to {{ insert: param, sa-09.05_odp.02 }} based on {{ insert: param, sa-09.05_odp.03 }}.
- SA-9(6)Maintain exclusive control of cryptographic keys for encrypted material stored or transmitted through an external system.
- SA-9(7)Provide the capability to check the integrity of information while it resides in the external system.
- SA-9(8)Restrict the geographic location of information processing and data storage to facilities located within in the legal jurisdictional boundary of the United States.
- SA-9aRequire that providers of external system services comply with organizational security and privacy requirements and employ the following controls: {{ insert: param, sa-09_odp.01 }}
- SA-9bDefine and document organizational oversight and user roles and responsibilities with regard to external system services; and
- SA-9cEmploy the following processes, methods, and techniques to monitor control compliance by external service providers on an ongoing basis: {{ insert: param, sa-09_odp.02 }}.
- SA-10Require the developer of the system, system component, or system service to:
- SA-10(1)Require the developer of the system, system component, or system service to enable integrity verification of software and firmware components.
- SA-10(2)Provide an alternate configuration management process using organizational personnel in the absence of a dedicated developer configuration management team.
- SA-10(3)Require the developer of the system, system component, or system service to enable integrity verification of hardware components.
- SA-10(4)Require the developer of the system, system component, or system service to employ tools for comparing newly generated versions of security-relevant hardware descriptions, source c
- SA-10(5)Require the developer of the system, system component, or system service to maintain the integrity of the mapping between the master build data describing the current version of se
- SA-10(6)Require the developer of the system, system component, or system service to execute procedures for ensuring that security-relevant hardware, software, and firmware updates distribu
- SA-10(7)Require {{ insert: param, sa-10.7_prm_1 }} to be included in the {{ insert: param, sa-10.7_prm_2 }}.
- SA-10aPerform configuration management during system, component, or service {{ insert: param, sa-10_odp.01 }};
- SA-10bDocument, manage, and control the integrity of changes to {{ insert: param, sa-10_odp.02 }};
- SA-10cImplement only organization-approved changes to the system, component, or service;
- SA-10dDocument approved changes to the system, component, or service and the potential security and privacy impacts of such changes; and
- SA-10eTrack security flaws and flaw resolution within the system, component, or service and report findings to {{ insert: param, sa-10_odp.03 }}.
- SA-11Require the developer of the system, system component, or system service, at all post-design stages of the system development life cycle, to:
- SA-11(1)Require the developer of the system, system component, or system service to employ static code analysis tools to identify common flaws and document the results of the analysis.
- SA-11(2)Require the developer of the system, system component, or system service to perform threat modeling and vulnerability analyses during development and the subsequent testing and eva
- SA-11(2)(a)Uses the following contextual information: {{ insert: param, sa-11.02_odp.01 }};
- SA-11(2)(b)Employs the following tools and methods: {{ insert: param, sa-11.02_odp.02 }};
- SA-11(2)(c)Conducts the modeling and analyses at the following level of rigor: {{ insert: param, sa-11.2_prm_3 }} ; and
- SA-11(2)(d)Produces evidence that meets the following acceptance criteria: {{ insert: param, sa-11.2_prm_4 }}.
- SA-11(3)(a)Require an independent agent satisfying {{ insert: param, sa-11.03_odp }} to verify the correct implementation of the developer security and privacy assessment plans and the eviden
- SA-11(3)(b)Verify that the independent agent is provided with sufficient information to complete the verification process or granted the authority to obtain such information.
- SA-11(4)Require the developer of the system, system component, or system service to perform a manual code review of {{ insert: param, sa-11.04_odp.01 }} using the following processes, proc
- SA-11(5)Require the developer of the system, system component, or system service to perform penetration testing:
- SA-11(5)(a)At the following level of rigor: {{ insert: param, sa-11.5_prm_1 }} ; and
- SA-11(5)(b)Under the following constraints: {{ insert: param, sa-11.05_odp.03 }}.
- SA-11(6)Require the developer of the system, system component, or system service to perform attack surface reviews.
- SA-11(7)Require the developer of the system, system component, or system service to verify that the scope of testing and evaluation provides complete coverage of the required controls at t
- SA-11(8)Require the developer of the system, system component, or system service to employ dynamic code analysis tools to identify common flaws and document the results of the analysis.
- SA-11(9)Require the developer of the system, system component, or system service to employ interactive application security testing tools to identify flaws and document the results.
- SA-11aDevelop and implement a plan for ongoing security and privacy control assessments;
- SA-11bPerform {{ insert: param, sa-11_odp.01 }} testing/evaluation {{ insert: param, sa-11_odp.02 }} at {{ insert: param, sa-11_odp.03 }};
- SA-11cProduce evidence of the execution of the assessment plan and the results of the testing and evaluation;
- SA-11dImplement a verifiable flaw remediation process; and
- SA-11eCorrect flaws identified during testing and evaluation.
- SA-15(1)Require the developer of the system, system component, or system service to:
- SA-15(1)(a)Define quality metrics at the beginning of the development process; and
- SA-15(1)(b)Provide evidence of meeting the quality metrics {{ insert: param, sa-15.01_odp.01 }}.
- SA-15(2)Require the developer of the system, system component, or system service to select and employ security and privacy tracking tools for use during the development process.
- SA-15(3)Require the developer of the system, system component, or system service to perform a criticality analysis:
- SA-15(3)(a)At the following decision points in the system development life cycle: {{ insert: param, sa-15.03_odp.01 }} ; and
- SA-15(3)(b)At the following level of rigor: {{ insert: param, sa-15.3_prm_2 }}.
- SA-15(5)Require the developer of the system, system component, or system service to reduce attack surfaces to {{ insert: param, sa-15.05_odp }}.
- SA-15(6)Require the developer of the system, system component, or system service to implement an explicit process to continuously improve the development process.
- SA-15(7)Require the developer of the system, system component, or system service {{ insert: param, sa-15.07_odp.01 }} to:
- SA-15(7)(a)Perform an automated vulnerability analysis using {{ insert: param, sa-15.07_odp.02 }};
- SA-15(7)(b)Determine the exploitation potential for discovered vulnerabilities;
- SA-15(7)(c)Determine potential risk mitigations for delivered vulnerabilities; and
- SA-15(7)(d)Deliver the outputs of the tools and results of the analysis to {{ insert: param, sa-15.07_odp.03 }}.
- SA-15(8)Require the developer of the system, system component, or system service to use threat modeling and vulnerability analyses from similar systems, components, or services to inform t
- SA-15(10)Require the developer of the system, system component, or system service to provide, implement, and test an incident response plan.
- SA-15(11)Require the developer of the system or system component to archive the system or component to be released or delivered together with the corresponding evidence supporting the final
- SA-15(12)Require the developer of the system or system component to minimize the use of personally identifiable information in development and test environments.
- SA-15(13)Require the developer of the system, system component, or system service to use {{ insert: param, sa-15.13_odp.01 }} to log {{ insert: param, sa-15.13_odp.02 }} at {{ insert: param
- SA-15aRequire the developer of the system, system component, or system service to follow a documented development process that:
- SA-15a1Explicitly addresses security and privacy requirements;
- SA-15a2Identifies the standards and tools used in the development process;
- SA-15a3Documents the specific tool options and tool configurations used in the development process; and
- SA-15a4Documents, manages, and ensures the integrity of changes to the process and/or tools used in development; and
- SA-15bReview the development process, standards, tools, tool options, and tool configurations {{ insert: param, sa-15_odp.01 }} to determine if the process, standards, tools, tool option
- SA-16Require the developer of the system, system component, or system service to provide the following training on the correct use and operation of the implemented security and privacy
- SA-17Require the developer of the system, system component, or system service to produce a design specification and security and privacy architecture that:
← records 801–1,200 · 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,601 on →