Records 1,601–2,000 — 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 to 2,000 of 2,022. Each links to its own page, which carries the source URL and the quoted line that states the value.
- SA-17(1)Require the developer of the system, system component, or system service to:
- SA-17(1)(a)Produce, as an integral part of the development process, a formal policy model describing the {{ insert: param, sa-17.1_prm_1 }} to be enforced; and
- SA-17(1)(b)Prove that the formal policy model is internally consistent and sufficient to enforce the defined elements of the organizational security and privacy policy when implemented.
- SA-17(2)Require the developer of the system, system component, or system service to:
- SA-17(2)(a)Define security-relevant hardware, software, and firmware; and
- SA-17(2)(b)Provide a rationale that the definition for security-relevant hardware, software, and firmware is complete.
- SA-17(3)Require the developer of the system, system component, or system service to:
- SA-17(3)(a)Produce, as an integral part of the development process, a formal top-level specification that specifies the interfaces to security-relevant hardware, software, and firmware in ter
- SA-17(3)(b)Show via proof to the extent feasible with additional informal demonstration as necessary, that the formal top-level specification is consistent with the formal policy model;
- SA-17(3)(c)Show via informal demonstration, that the formal top-level specification completely covers the interfaces to security-relevant hardware, software, and firmware;
- SA-17(3)(d)Show that the formal top-level specification is an accurate description of the implemented security-relevant hardware, software, and firmware; and
- SA-17(3)(e)Describe the security-relevant hardware, software, and firmware mechanisms not addressed in the formal top-level specification but strictly internal to the security-relevant hardwa
- SA-17(4)Require the developer of the system, system component, or system service to:
- SA-17(4)(a)Produce, as an integral part of the development process, an informal descriptive top-level specification that specifies the interfaces to security-relevant hardware, software, and
- SA-17(4)(b)Show via {{ insert: param, sa-17.04_odp }} that the descriptive top-level specification is consistent with the formal policy model;
- SA-17(4)(c)Show via informal demonstration, that the descriptive top-level specification completely covers the interfaces to security-relevant hardware, software, and firmware;
- SA-17(4)(d)Show that the descriptive top-level specification is an accurate description of the interfaces to security-relevant hardware, software, and firmware; and
- SA-17(4)(e)Describe the security-relevant hardware, software, and firmware mechanisms not addressed in the descriptive top-level specification but strictly internal to the security-relevant h
- SA-17(5)Require the developer of the system, system component, or system service to:
- SA-17(5)(a)Design and structure the security-relevant hardware, software, and firmware to use a complete, conceptually simple protection mechanism with precisely defined semantics; and
- SA-17(5)(b)Internally structure the security-relevant hardware, software, and firmware with specific regard for this mechanism.
- SA-17(6)Require the developer of the system, system component, or system service to structure security-relevant hardware, software, and firmware to facilitate testing.
- SA-17(7)Require the developer of the system, system component, or system service to structure security-relevant hardware, software, and firmware to facilitate controlling access with least
- SA-17(8)Design {{ insert: param, sa-17.08_odp.01 }} with coordinated behavior to implement the following capabilities: {{ insert: param, sa-17.08_odp.02 }}.
- SA-17(9)Use different designs for {{ insert: param, sa-17.09_odp }} to satisfy a common set of requirements or to provide equivalent functionality.
- SA-17aIs consistent with the organization’s security and privacy architecture that is an integral part the organization’s enterprise architecture;
- SA-17bAccurately and completely describes the required security and privacy functionality, and the allocation of controls among physical and logical components; and
- SA-17cExpresses how individual security and privacy functions, mechanisms, and services work together to provide required security and privacy capabilities and a unified approach to prot
- SA-20Reimplement or custom develop the following critical system components: {{ insert: param, sa-20_odp }}.
- SA-21Require that the developer of {{ insert: param, sa-21_odp.01 }}:
- SA-21aHas appropriate access authorizations as determined by assigned {{ insert: param, sa-21_odp.02 }} ; and
- SA-21bSatisfies the following additional personnel screening criteria: {{ insert: param, sa-21_odp.03 }}.
- SA-22aReplace system components when support for the components is no longer available from the developer, vendor, or manufacturer; or
- SA-22bProvide the following options for alternative sources for continued support for unsupported components {{ insert: param, sa-22_odp.01 }}.
- SA-23Employ {{ insert: param, sa-23_odp.01 }} on {{ insert: param, sa-23_odp.02 }} supporting mission essential services or functions to increase the trustworthiness in those systems or
- SA-24aDesign organizational systems, system components, or system services to achieve cyber resiliency by:
- SA-24a1Defining the following cyber resiliency goals: {{ insert: param, sa-24_odp.01 }}.
- SA-24a2Defining the following cyber resiliency objectives: {{ insert: param, sa-24_odp.02 }}.
- SA-24a3Defining the following cyber resiliency techniques: {{ insert: param, sa-24_odp.03 }}.
- SA-24a4Defining the following cyber resiliency implementation approaches: {{ insert: param, sa-24_odp.04 }}.
- SA-24a5Defining the following cyber resiliency design principles: {{ insert: param, sa-24_odp.05 }}.
- SA-24bImplement the selected cyber resiliency goals, objectives, techniques, implementation approaches, and design principles as part of an organizational risk management process or syst
- SC-1aDevelop, document, and disseminate to {{ insert: param, sc-1_prm_1 }}:
- SC-1a1{{ insert: param, sc-01_odp.03 }} system and communications protection policy that:
- SC-1a1(a)Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
- SC-1a1(b)Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
- SC-1a2Procedures to facilitate the implementation of the system and communications protection policy and the associated system and communications protection controls;
- SC-1bDesignate an {{ insert: param, sc-01_odp.04 }} to manage the development, documentation, and dissemination of the system and communications protection policy and procedures; and
- SC-1cReview and update the current system and communications protection:
- SC-1c1Policy {{ insert: param, sc-01_odp.05 }} and following {{ insert: param, sc-01_odp.06 }} ; and
- SC-1c2Procedures {{ insert: param, sc-01_odp.07 }} and following {{ insert: param, sc-01_odp.08 }}.
- SC-2Separate user functionality, including user interface services, from system management functionality.
- SC-2(1)Prevent the presentation of system management functionality at interfaces to non-privileged users.
- SC-2(2)Store state information from applications and software separately.
- SC-3Isolate security functions from nonsecurity functions.
- SC-3(1)Employ hardware separation mechanisms to implement security function isolation.
- SC-3(2)Isolate security functions enforcing access and information flow control from nonsecurity functions and from other security functions.
- SC-3(3)Minimize the number of nonsecurity functions included within the isolation boundary containing security functions.
- SC-3(4)Implement security functions as largely independent modules that maximize internal cohesiveness within modules and minimize coupling between modules.
- SC-3(5)Implement security functions as a layered structure minimizing interactions between layers of the design and avoiding any dependence by lower layers on the functionality or correct
- SC-4Prevent unauthorized and unintended information transfer via shared system resources.
- SC-4(2)Prevent unauthorized information transfer via shared resources in accordance with {{ insert: param, sc-04.02_odp }} when system processing explicitly switches between different inf
- SC-5(1)Restrict the ability of individuals to launch the following denial-of-service attacks against other systems: {{ insert: param, sc-05.01_odp }}.
- SC-5(2)Manage capacity, bandwidth, or other redundancy to limit the effects of information flooding denial-of-service attacks.
- SC-5(3)(a)Employ the following monitoring tools to detect indicators of denial-of-service attacks against, or launched from, the system: {{ insert: param, sc-05.03_odp.01 }} ; and
- SC-5(3)(b)Monitor the following system resources to determine if sufficient resources exist to prevent effective denial-of-service attacks: {{ insert: param, sc-05.03_odp.02 }}.
- SC-5a{{ insert: param, sc-05_odp.02 }} the effects of the following types of denial-of-service events: {{ insert: param, sc-05_odp.01 }} ; and
- SC-5bEmploy the following controls to achieve the denial-of-service objective: {{ insert: param, sc-05_odp.03 }}.
- SC-6Protect the availability of resources by allocating {{ insert: param, sc-06_odp.01 }} by {{ insert: param, sc-06_odp.02 }}.
- SC-7(3)Limit the number of external network connections to the system.
- SC-7(4)(a)Implement a managed interface for each external telecommunication service;
- SC-7(4)(b)Establish a traffic flow policy for each managed interface;
- SC-7(4)(c)Protect the confidentiality and integrity of the information being transmitted across each interface;
- SC-7(4)(d)Document each exception to the traffic flow policy with a supporting mission or business need and duration of that need;
- SC-7(4)(e)Review exceptions to the traffic flow policy {{ insert: param, sc-07.04_odp }} and remove exceptions that are no longer supported by an explicit mission or business need;
- SC-7(4)(f)Prevent unauthorized exchange of control plane traffic with external networks;
- SC-7(4)(g)Publish information to enable remote networks to detect unauthorized control plane traffic from internal networks; and
- SC-7(4)(h)Filter unauthorized control plane traffic from external networks.
- SC-7(5)Deny network communications traffic by default and allow network communications traffic by exception {{ insert: param, sc-07.05_odp.01 }}.
- SC-7(7)Prevent split tunneling for remote devices connecting to organizational systems unless the split tunnel is securely provisioned using {{ insert: param, sc-07.07_odp }}.
- SC-7(8)Route {{ insert: param, sc-07.08_odp.01 }} to {{ insert: param, sc-07.08_odp.02 }} through authenticated proxy servers at managed interfaces.
- SC-7(9)(a)Detect and deny outgoing communications traffic posing a threat to external systems; and
- SC-7(9)(b)Audit the identity of internal users associated with denied communications.
- SC-7(10)(a)Prevent the exfiltration of information; and
- SC-7(10)(b)Conduct exfiltration tests {{ insert: param, sc-07.10_odp }}.
- SC-7(11)Only allow incoming communications from {{ insert: param, sc-07.11_odp.01 }} to be routed to {{ insert: param, sc-07.11_odp.02 }}.
- SC-7(12)Implement {{ insert: param, sc-07.12_odp.01 }} at {{ insert: param, sc-07.12_odp.02 }}.
- SC-7(13)Isolate {{ insert: param, sc-07.13_odp }} from other internal system components by implementing physically separate subnetworks with managed interfaces to other components of the s
- SC-7(14)Protect against unauthorized physical connections at {{ insert: param, sc-07.14_odp }}.
- SC-7(15)Route networked, privileged accesses through a dedicated, managed interface for purposes of access control and auditing.
- SC-7(16)Prevent the discovery of specific system components that represent a managed interface.
- SC-7(17)Enforce adherence to protocol formats.
- SC-7(18)Prevent systems from entering unsecure states in the event of an operational failure of a boundary protection device.
- SC-7(19)Block inbound and outbound communications traffic between {{ insert: param, sc-07.19_odp }} that are independently configured by end users and external service providers.
- SC-7(20)Provide the capability to dynamically isolate {{ insert: param, sc-07.20_odp }} from other system components.
- SC-7(21)Employ boundary protection mechanisms to isolate {{ insert: param, sc-07.21_odp.01 }} supporting {{ insert: param, sc-07.21_odp.02 }}.
- SC-7(22)Implement separate network addresses to connect to systems in different security domains.
- SC-7(23)Disable feedback to senders on protocol format validation failure.
- SC-7(24)For systems that process personally identifiable information:
- SC-7(24)(a)Apply the following processing rules to data elements of personally identifiable information: {{ insert: param, sc-07.24_odp }};
- SC-7(24)(b)Monitor for permitted processing at the external interfaces to the system and at key internal boundaries within the system;
- SC-7(24)(c)Document each processing exception; and
- SC-7(24)(d)Review and remove exceptions that are no longer supported.
- SC-7(25)Prohibit the direct connection of {{ insert: param, sc-07.25_odp.01 }} to an external network without the use of {{ insert: param, sc-07.25_odp.02 }}.
- SC-7(26)Prohibit the direct connection of a classified national security system to an external network without the use of {{ insert: param, sc-07.26_odp }}.
- SC-7(27)Prohibit the direct connection of {{ insert: param, sc-07.27_odp.01 }} to an external network without the use of {{ insert: param, sc-07.27_odp.02 }}.
- SC-7(28)Prohibit the direct connection of {{ insert: param, sc-07.28_odp }} to a public network.
- SC-7(29)Implement {{ insert: param, sc-07.29_odp.01 }} separate subnetworks to isolate the following critical system components and functions: {{ insert: param, sc-07.29_odp.02 }}.
- SC-7aMonitor and control communications at the external managed interfaces to the system and at key internal managed interfaces within the system;
- SC-7bImplement subnetworks for publicly accessible system components that are {{ insert: param, sc-07_odp }} separated from internal organizational networks; and
- SC-7cConnect to external networks or systems only through managed interfaces consisting of boundary protection devices arranged in accordance with an organizational security and privacy
- SC-8Protect the {{ insert: param, sc-08_odp }} of transmitted information.
- SC-8(1)Implement cryptographic mechanisms to {{ insert: param, sc-08.01_odp }} during transmission.
- SC-8(2)Maintain the {{ insert: param, sc-08.02_odp }} of information during preparation for transmission and during reception.
- SC-8(3)Implement cryptographic mechanisms to protect message externals unless otherwise protected by {{ insert: param, sc-08.03_odp }}.
- SC-8(4)Implement cryptographic mechanisms to conceal or randomize communication patterns unless otherwise protected by {{ insert: param, sc-08.04_odp }}.
- SC-8(5)Implement {{ insert: param, sc-08.05_odp.01 }} to {{ insert: param, sc-08.05_odp.02 }} during transmission.
- SC-10Terminate the network connection associated with a communications session at the end of the session or after {{ insert: param, sc-10_odp }} of inactivity.
- SC-11(1)(a)Provide a trusted communications path that is irrefutably distinguishable from other communications paths; and
- SC-11(1)(b)Initiate the trusted communications path for communications between the {{ insert: param, sc-11.01_odp }} of the system and the user.
- SC-11aProvide a {{ insert: param, sc-11_odp.01 }} isolated trusted communications path for communications between the user and the trusted components of the system; and
- SC-11bPermit users to invoke the trusted communications path for communications between the user and the following security functions of the system, including at a minimum, authenticatio
- SC-12Establish and manage cryptographic keys when cryptography is employed within the system in accordance with the following key management requirements: {{ insert: param, sc-12_odp }}
- SC-12(1)Maintain availability of information in the event of the loss of cryptographic keys by users.
- SC-12(2)Produce, control, and distribute symmetric cryptographic keys using {{ insert: param, sc-12.02_odp }} key management technology and processes.
- SC-12(3)Produce, control, and distribute asymmetric cryptographic keys using {{ insert: param, sc-12.03_odp }}.
- SC-12(6)Maintain physical control of cryptographic keys when stored information is encrypted by external service providers.
- SC-13aDetermine the {{ insert: param, sc-13_odp.01 }} ; and
- SC-13bImplement the following types of cryptography required for each specified cryptographic use: {{ insert: param, sc-13_odp.02 }}.
- SC-15(1)Provide {{ insert: param, sc-15.01_odp }} disconnect of collaborative computing devices in a manner that supports ease of use.
- SC-15(3)Disable or remove collaborative computing devices and applications from {{ insert: param, sc-15.03_odp.01 }} in {{ insert: param, sc-15.03_odp.02 }}.
- SC-15(4)Provide an explicit indication of current participants in {{ insert: param, sc-15.04_odp }}.
- SC-15aProhibit remote activation of collaborative computing devices and applications with the following exceptions: {{ insert: param, sc-15_odp }} ; and
- SC-15bProvide an explicit indication of use to users physically present at the devices.
- SC-16Associate {{ insert: param, sc-16_prm_1 }} with information exchanged between systems and between system components.
- SC-16(1)Verify the integrity of transmitted security and privacy attributes.
- SC-16(2)Implement anti-spoofing mechanisms to prevent adversaries from falsifying the security attributes indicating the successful application of the security process.
- SC-16(3)Implement {{ insert: param, sc-16.03_odp }} to bind security and privacy attributes to transmitted information.
- SC-17aIssue public key certificates under an {{ insert: param, sc-17_odp }} or obtain public key certificates from an approved service provider; and
- SC-17bInclude only approved trust anchors in trust stores or certificate stores managed by the organization.
- SC-18(1)Identify {{ insert: param, sc-18.01_odp.01 }} and take {{ insert: param, sc-18.01_odp.02 }}.
- SC-18(2)Verify that the acquisition, development, and use of mobile code to be deployed in the system meets {{ insert: param, sc-18.02_odp }}.
- SC-18(3)Prevent the download and execution of {{ insert: param, sc-18.03_odp }}.
- SC-18(4)Prevent the automatic execution of mobile code in {{ insert: param, sc-18.04_odp.01 }} and enforce {{ insert: param, sc-18.04_odp.02 }} prior to executing the code.
- SC-18(5)Allow execution of permitted mobile code only in confined virtual machine environments.
- SC-18aDefine acceptable and unacceptable mobile code and mobile code technologies; and
- SC-18bAuthorize, monitor, and control the use of mobile code within the system.
- SC-19Technology-specific; addressed as any other technology or protocol.
- SC-20(2)Provide data origin and integrity protection artifacts for internal name/address resolution queries.
- SC-20aProvide additional data origin authentication and integrity verification artifacts along with the authoritative name resolution data the system returns in response to external name
- SC-20bProvide the means to indicate the security status of child zones and (if the child supports secure resolution services) to enable verification of a chain of trust among parent and
- SC-21Request and perform data origin authentication and data integrity verification on the name/address resolution responses the system receives from authoritative sources.
- SC-22Ensure the systems that collectively provide name/address resolution service for an organization are fault-tolerant and implement internal and external role separation.
- SC-23Protect the authenticity of communications sessions.
- SC-23(1)Invalidate session identifiers upon user logout or other session termination.
- SC-23(3)Generate a unique session identifier for each session with {{ insert: param, sc-23.03_odp }} and recognize only session identifiers that are system-generated.
- SC-23(5)Only allow the use of {{ insert: param, sc-23.05_odp }} for verification of the establishment of protected sessions.
- SC-24Fail to a {{ insert: param, sc-24_odp.02 }} for the following failures on the indicated components while preserving {{ insert: param, sc-24_odp.03 }} in failure: {{ insert: param,
- SC-25Employ minimal functionality and information storage on the following system components: {{ insert: param, sc-25_odp }}.
- SC-26Include components within organizational systems specifically designed to be the target of malicious attacks for detecting, deflecting, and analyzing such attacks.
- SC-27Include within organizational systems the following platform independent applications: {{ insert: param, sc-27_odp }}.
- SC-28Protect the {{ insert: param, sc-28_odp.01 }} of the following information at rest: {{ insert: param, sc-28_odp.02 }}.
- SC-28(1)Implement cryptographic mechanisms to prevent unauthorized disclosure and modification of the following information at rest on {{ insert: param, sc-28.01_odp.02 }}: {{ insert: para
- SC-28(2)Remove the following information from online storage and store offline in a secure location: {{ insert: param, sc-28.02_odp }}.
- SC-28(3)Provide protected storage for cryptographic keys {{ insert: param, sc-28.03_odp.01 }}.
- SC-29Employ a diverse set of information technologies for the following system components in the implementation of the system: {{ insert: param, sc-29_odp }}.
- SC-29(1)Employ virtualization techniques to support the deployment of a diversity of operating systems and applications that are changed {{ insert: param, sc-29.01_odp }}.
- SC-30Employ the following concealment and misdirection techniques for {{ insert: param, sc-30_odp.02 }} at {{ insert: param, sc-30_odp.03 }} to confuse and mislead adversaries: {{ inser
- SC-30(2)Employ {{ insert: param, sc-30.02_odp }} to introduce randomness into organizational operations and assets.
- SC-30(3)Change the location of {{ insert: param, sc-30.03_odp.01 }} {{ insert: param, sc-30.03_odp.02 }}].
- SC-30(4)Employ realistic, but misleading information in {{ insert: param, sc-30.04_odp }} about its security state or posture.
- SC-30(5)Employ the following techniques to hide or conceal {{ insert: param, sc-30.05_odp.02 }}: {{ insert: param, sc-30.05_odp.01 }}.
- SC-31(1)Test a subset of the identified covert channels to determine the channels that are exploitable.
- SC-31(2)Reduce the maximum bandwidth for identified covert {{ insert: param, sc-31.02_odp.01 }} channels to {{ insert: param, sc-31.02_odp.02 }}.
- SC-31(3)Measure the bandwidth of {{ insert: param, sc-31.03_odp }} in the operational environment of the system.
- SC-31aPerform a covert channel analysis to identify those aspects of communications within the system that are potential avenues for covert {{ insert: param, sc-31_odp }} channels; and
- SC-31bEstimate the maximum bandwidth of those channels.
- SC-32Partition the system into {{ insert: param, sc-32_odp.01 }} residing in separate {{ insert: param, sc-32_odp.02 }} domains or environments based on {{ insert: param, sc-32_odp.03 }
- SC-32(1)Partition privileged functions into separate physical domains.
- SC-34For {{ insert: param, sc-34_odp.01 }} , load and execute:
- SC-34(1)Employ {{ insert: param, sc-34.01_odp }} with no writeable storage that is persistent across component restart or power on/off.
- SC-34(2)Protect the integrity of information prior to storage on read-only media and control the media after such information has been recorded onto the media.
- SC-34aThe operating environment from hardware-enforced, read-only media; and
- SC-34bThe following applications from hardware-enforced, read-only media: {{ insert: param, sc-34_odp.02 }}.
- SC-35Include system components that proactively seek to identify network-based malicious code or malicious websites.
- SC-36Distribute the following processing and storage components across multiple {{ insert: param, sc-36_prm_1 }}: {{ insert: param, sc-36_prm_2 }}.
- SC-36(1)(a)Employ polling techniques to identify potential faults, errors, or compromises to the following processing and storage components: {{ insert: param, sc-36.01_odp.01 }} ; and
- SC-36(1)(b)Take the following actions in response to identified faults, errors, or compromises: {{ insert: param, sc-36.01_odp.02 }}.
- SC-36(2)Synchronize the following duplicate systems or system components: {{ insert: param, sc-36.02_odp }}.
- SC-37Employ the following out-of-band channels for the physical delivery or electronic transmission of {{ insert: param, sc-37_odp.02 }} to {{ insert: param, sc-37_odp.03 }}: {{ insert:
- SC-37(1)Employ {{ insert: param, sc-37.01_odp.01 }} to ensure that only {{ insert: param, sc-37.01_odp.02 }} receive the following information, system components, or devices: {{ insert: pa
- SC-38Employ the following operations security controls to protect key organizational information throughout the system development life cycle: {{ insert: param, sc-38_odp }}.
- SC-39Maintain a separate execution domain for each executing system process.
- SC-39(1)Implement hardware separation mechanisms to facilitate process isolation.
- SC-39(2)Maintain a separate execution domain for each thread in {{ insert: param, sc-39.02_odp }}.
- SC-40Protect external and internal {{ insert: param, sc-40_prm_1 }} from the following signal parameter attacks: {{ insert: param, sc-40_prm_2 }}.
- SC-40(1)Implement cryptographic mechanisms that achieve {{ insert: param, sc-40.01_odp }} against the effects of intentional electromagnetic interference.
- SC-40(2)Implement cryptographic mechanisms to reduce the detection potential of wireless links to {{ insert: param, sc-40.02_odp }}.
- SC-40(3)Implement cryptographic mechanisms to identify and reject wireless transmissions that are deliberate attempts to achieve imitative or manipulative communications deception based on
- SC-40(4)Implement cryptographic mechanisms to prevent the identification of {{ insert: param, sc-40.04_odp }} by using the transmitter signal parameters.
- SC-41{{ insert: param, sc-41_odp.02 }} disable or remove {{ insert: param, sc-41_odp.01 }} on the following systems or system components: {{ insert: param, sc-41_odp.03 }}.
- SC-42(1)Verify that the system is configured so that data or information collected by the {{ insert: param, sc-42.01_odp }} is only reported to authorized individuals or roles.
- SC-42(2)Employ the following measures so that data or information collected by {{ insert: param, sc-42.01_odp }} is only used for authorized purposes: {{ insert: param, sc-42.02_odp }}.
- SC-42(4)Employ the following measures to facilitate an individual’s awareness that personally identifiable information is being collected by {{ insert: param, sc-42.04_odp.02 }}: {{ insert
- SC-42(5)Employ {{ insert: param, sc-42.05_odp }} that are configured to minimize the collection of information about individuals that is not needed.
- SC-42aProhibit {{ insert: param, sc-42_odp.01 }} ; and
- SC-42bProvide an explicit indication of sensor use to {{ insert: param, sc-42_odp.05 }}.
- SC-43aEstablish usage restrictions and implementation guidelines for the following system components: {{ insert: param, sc-43_odp }} ; and
- SC-43bAuthorize, monitor, and control the use of such components within the system.
- SC-44Employ a detonation chamber capability within {{ insert: param, sc-44_odp }}.
- SC-45Synchronize system clocks within and between systems and system components.
- SC-45(1)(a)Compare the internal system clocks {{ insert: param, sc-45.01_odp.01 }} with {{ insert: param, sc-45.01_odp.02 }} ; and
- SC-45(1)(b)Synchronize the internal system clocks to the authoritative time source when the time difference is greater than {{ insert: param, sc-45.01_odp.03 }}.
- SC-45(2)(a)Identify a secondary authoritative time source that is in a different geographic region than the primary authoritative time source; and
- SC-45(2)(b)Synchronize the internal system clocks to the secondary authoritative time source if the primary authoritative time source is unavailable.
- SC-46Implement a policy enforcement mechanism {{ insert: param, sc-46_odp }} between the physical and/or network interfaces for the connecting security domains.
- SC-47Establish {{ insert: param, sc-47_odp }} for system operations organizational command and control.
- SC-48Relocate {{ insert: param, sc-48_odp.01 }} to {{ insert: param, sc-48_odp.02 }} under the following conditions or circumstances: {{ insert: param, sc-48_odp.03 }}.
- SC-48(1)Dynamically relocate {{ insert: param, sc-48.01_odp.01 }} to {{ insert: param, sc-48.01_odp.02 }} under the following conditions or circumstances: {{ insert: param, sc-48.01_odp.03
- SC-49Implement hardware-enforced separation and policy enforcement mechanisms between {{ insert: param, sc-49_odp }}.
- SC-50Implement software-enforced separation and policy enforcement mechanisms between {{ insert: param, sc-50_odp }}.
- SC-51aEmploy hardware-based, write-protect for {{ insert: param, sc-51_odp.01 }} ; and
- SC-51bImplement specific procedures for {{ insert: param, sc-51_odp.02 }} to manually disable hardware write-protect for firmware modifications and re-enable the write-protect prior to r
- SI-1aDevelop, document, and disseminate to {{ insert: param, si-1_prm_1 }}:
- SI-1a1{{ insert: param, si-01_odp.03 }} system and information integrity policy that:
- SI-1a1(a)Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
- SI-1a1(b)Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
- SI-1a2Procedures to facilitate the implementation of the system and information integrity policy and the associated system and information integrity controls;
- SI-1bDesignate an {{ insert: param, si-01_odp.04 }} to manage the development, documentation, and dissemination of the system and information integrity policy and procedures; and
- SI-1cReview and update the current system and information integrity:
- SI-1c1Policy {{ insert: param, si-01_odp.05 }} and following {{ insert: param, si-01_odp.06 }} ; and
- SI-1c2Procedures {{ insert: param, si-01_odp.07 }} and following {{ insert: param, si-01_odp.08 }}.
- SI-2(2)Determine if system components have applicable security-relevant software and firmware updates installed using {{ insert: param, si-02.02_odp.01 }} {{ insert: param, si-02.02_odp.0
- SI-2(3)(a)Measure the time between flaw identification and flaw remediation; and
- SI-2(3)(b)Establish the following benchmarks for taking corrective actions: {{ insert: param, si-02.03_odp }}.
- SI-2(4)Employ automated patch management tools to facilitate flaw remediation to the following system components: {{ insert: param, si-02.04_odp }}.
- SI-2(5)Install {{ insert: param, si-02.05_odp.01 }} automatically to {{ insert: param, si-02.05_odp.02 }}.
- SI-2(6)Remove previous versions of {{ insert: param, si-02.06_odp }} after updated versions have been installed.
- SI-2(7)aConduct root cause analysis to identify underlying causes of issues or failures.
- SI-2(7)bDevelop actions to address the root cause of the issue or failure.
- SI-2(7)cImplement the actions and monitor the implementation for effectiveness.
- SI-2aIdentify, report, and correct system flaws;
- SI-2bTest software and firmware updates related to flaw remediation for effectiveness and potential side effects before installation;
- SI-2cInstall security-relevant software and firmware updates within {{ insert: param, si-02_odp }} of the release of the updates; and
- SI-2dIncorporate flaw remediation into the organizational configuration management process.
- SI-3(4)Update malicious code protection mechanisms only when directed by a privileged user.
- SI-3(6)(a)Test malicious code protection mechanisms {{ insert: param, si-03.06_odp }} by introducing known benign code into the system; and
- SI-3(6)(b)Verify that the detection of the code and the associated incident reporting occur.
- SI-3(8)(a)Detect the following unauthorized operating system commands through the kernel application programming interface on {{ insert: param, si-03.08_odp.02 }}: {{ insert: param, si-03.08
- SI-3(8)(b){{ insert: param, si-03.08_odp.03 }}.
- SI-3(10)(a)Employ the following tools and techniques to analyze the characteristics and behavior of malicious code: {{ insert: param, si-03.10_odp }} ; and
- SI-3(10)(b)Incorporate the results from malicious code analysis into organizational incident response and flaw remediation processes.
- SI-3aImplement {{ insert: param, si-03_odp.01 }} malicious code protection mechanisms at system entry and exit points to detect and eradicate malicious code;
- SI-3bAutomatically update malicious code protection mechanisms as new releases are available in accordance with organizational configuration management policy and procedures;
- SI-3cConfigure malicious code protection mechanisms to:
- SI-3c1Perform periodic scans of the system {{ insert: param, si-03_odp.02 }} and real-time scans of files from external sources at {{ insert: param, si-03_odp.03 }} as the files are down
- SI-3c2{{ insert: param, si-03_odp.04 }} ; and send alert to {{ insert: param, si-03_odp.06 }} in response to malicious code detection; and
- SI-3dAddress the receipt of false positives during malicious code detection and eradication and the resulting potential impact on the availability of the system.
- SI-4(1)Connect and configure individual intrusion detection tools into a system-wide intrusion detection system.
- SI-4(2)Employ automated tools and mechanisms to support near real-time analysis of events.
- SI-4(3)Employ automated tools and mechanisms to integrate intrusion detection tools and mechanisms into access control and flow control mechanisms.
- SI-4(4)(a)Determine criteria for unusual or unauthorized activities or conditions for inbound and outbound communications traffic;
- SI-4(4)(b)Monitor inbound and outbound communications traffic {{ insert: param, si-4.4_prm_1 }} for {{ insert: param, si-4.4_prm_2 }}.
- SI-4(5)Alert {{ insert: param, si-04.05_odp.01 }} when the following system-generated indications of compromise or potential compromise occur: {{ insert: param, si-04.05_odp.02 }}.
- SI-4(7)(a)Notify {{ insert: param, si-04.07_odp.01 }} of detected suspicious events; and
- SI-4(7)(b)Take the following actions upon detection: {{ insert: param, si-04.07_odp.02 }}.
- SI-4(9)Test intrusion-monitoring tools and mechanisms {{ insert: param, si-04.09_odp }}.
- SI-4(10)Make provisions so that {{ insert: param, si-04.10_odp.01 }} is visible to {{ insert: param, si-04.10_odp.02 }}.
- SI-4(11)Analyze outbound communications traffic at the external interfaces to the system and selected {{ insert: param, si-04.11_odp }} to discover anomalies.
- SI-4(12)Alert {{ insert: param, si-04.12_odp.01 }} using {{ insert: param, si-04.12_odp.02 }} when the following indications of inappropriate or unusual activities with security or privacy
- SI-4(13)(a)Analyze communications traffic and event patterns for the system;
- SI-4(13)(b)Develop profiles representing common traffic and event patterns; and
- SI-4(13)(c)Use the traffic and event profiles in tuning system-monitoring devices.
- SI-4(14)Employ a wireless intrusion detection system to identify rogue wireless devices and to detect attack attempts and potential compromises or breaches to the system.
- SI-4(15)Employ an intrusion detection system to monitor wireless communications traffic as the traffic passes from wireless to wireline networks.
- SI-4(16)Correlate information from monitoring tools and mechanisms employed throughout the system.
- SI-4(17)Correlate information from monitoring physical, cyber, and supply chain activities to achieve integrated, organization-wide situational awareness.
- SI-4(18)Analyze outbound communications traffic at external interfaces to the system and at the following interior points to detect covert exfiltration of information: {{ insert: param, si
- SI-4(19)Implement {{ insert: param, si-04.19_odp.01 }} of individuals who have been identified by {{ insert: param, si-04.19_odp.02 }} as posing an increased level of risk.
- SI-4(20)Implement the following additional monitoring of privileged users: {{ insert: param, si-04.20_odp }}.
- SI-4(21)Implement the following additional monitoring of individuals during {{ insert: param, si-04.21_odp.02 }}: {{ insert: param, si-04.21_odp.01 }}.
- SI-4(22)(a)Detect network services that have not been authorized or approved by {{ insert: param, si-04.22_odp.01 }} ; and
- SI-4(22)(b){{ insert: param, si-04.22_odp.02 }} when detected.
- SI-4(23)Implement the following host-based monitoring mechanisms at {{ insert: param, si-04.23_odp.02 }}: {{ insert: param, si-04.23_odp.01 }}.
- SI-4(24)Discover, collect, and distribute to {{ insert: param, si-04.24_odp.02 }} , indicators of compromise provided by {{ insert: param, si-04.24_odp.01 }}.
- SI-4(25)Provide visibility into network traffic at external and key internal system interfaces to optimize the effectiveness of monitoring devices.
- SI-4aMonitor the system to detect:
- SI-4a1Attacks and indicators of potential attacks in accordance with the following monitoring objectives: {{ insert: param, si-04_odp.01 }} ; and
- SI-4a2Unauthorized local, network, and remote connections;
- SI-4bIdentify unauthorized use of the system through the following techniques and methods: {{ insert: param, si-04_odp.02 }};
- SI-4cInvoke internal monitoring capabilities or deploy monitoring devices:
- SI-4c1Strategically within the system to collect organization-determined essential information; and
- SI-4c2At ad hoc locations within the system to track specific types of transactions of interest to the organization;
- SI-4dAnalyze detected events and anomalies;
- SI-4eAdjust the level of system monitoring activity when there is a change in risk to organizational operations and assets, individuals, other organizations, or the Nation;
- SI-4fObtain legal opinion regarding system monitoring activities; and
- SI-4gProvide {{ insert: param, si-04_odp.03 }} to {{ insert: param, si-04_odp.04 }} {{ insert: param, si-04_odp.05 }}.
- SI-5(1)Broadcast security alert and advisory information throughout the organization using {{ insert: param, si-05.01_odp }}.
- SI-5aReceive system security alerts, advisories, and directives from {{ insert: param, si-05_odp.01 }} on an ongoing basis;
- SI-5bGenerate internal security alerts, advisories, and directives as deemed necessary;
- SI-5cDisseminate security alerts, advisories, and directives to: {{ insert: param, si-05_odp.02 }} ; and
- SI-5dImplement security directives in accordance with established time frames, or notify the issuing organization of the degree of noncompliance.
- SI-6(2)Implement automated mechanisms to support the management of distributed security and privacy function testing.
- SI-6(3)Report the results of security and privacy function verification to {{ insert: param, si-06.03_odp }}.
- SI-6aVerify the correct operation of {{ insert: param, si-6_prm_1 }};
- SI-6bPerform the verification of the functions specified in SI-6a {{ insert: param, si-06_odp.03 }};
- SI-6cAlert {{ insert: param, si-06_odp.06 }} to failed security and privacy verification tests; and
- SI-6d{{ insert: param, si-06_odp.07 }} when anomalies are discovered.
- SI-7(1)Perform an integrity check of {{ insert: param, si-7.1_prm_1 }} {{ insert: param, si-7.1_prm_2 }}.
- SI-7(2)Employ automated tools that provide notification to {{ insert: param, si-07.02_odp }} upon discovering discrepancies during integrity verification.
- SI-7(3)Employ centrally managed integrity verification tools.
- SI-7(5)Automatically {{ insert: param, si-07.05_odp.01 }} when integrity violations are discovered.
- SI-7(6)Implement cryptographic mechanisms to detect unauthorized changes to software, firmware, and information.
- SI-7(7)Incorporate the detection of the following unauthorized changes into the organizational incident response capability: {{ insert: param, si-07.07_odp }}.
- SI-7(8)Upon detection of a potential integrity violation, provide the capability to audit the event and initiate the following actions: {{ insert: param, si-07.08_odp.01 }}.
- SI-7(9)Verify the integrity of the boot process of the following system components: {{ insert: param, si-07.09_odp }}.
- SI-7(10)Implement the following mechanisms to protect the integrity of boot firmware in {{ insert: param, si-07.10_odp.02 }}: {{ insert: param, si-07.10_odp.01 }}.
- SI-7(12)Require that the integrity of the following user-installed software be verified prior to execution: {{ insert: param, si-07.12_odp }}.
- SI-7(15)Implement cryptographic mechanisms to authenticate the following software or firmware components prior to installation: {{ insert: param, si-07.15_odp }}.
- SI-7(16)Prohibit processes from executing without supervision for more than {{ insert: param, si-07.16_odp }}.
- SI-7(17)Implement {{ insert: param, si-07.17_odp }} for application self-protection at runtime.
- SI-7aEmploy integrity verification tools to detect unauthorized changes to the following software, firmware, and information: {{ insert: param, si-7_prm_1 }} ; and
- SI-7bTake the following actions when unauthorized changes to the software, firmware, and information are detected: {{ insert: param, si-7_prm_2 }}.
- SI-8(2)Automatically update spam protection mechanisms {{ insert: param, si-08.02_odp }}.
- SI-8(3)Implement spam protection mechanisms with a learning capability to more effectively identify legitimate communications traffic.
- SI-8aEmploy spam protection mechanisms at system entry and exit points to detect and act on unsolicited messages; and
- SI-8bUpdate spam protection mechanisms when new releases are available in accordance with organizational configuration management policy and procedures.
- SI-10Check the validity of the following information inputs: {{ insert: param, si-10_odp }}.
- SI-10(1)(a)Provide a manual override capability for input validation of the following information inputs: {{ insert: param, si-10_odp }};
- SI-10(1)(b)Restrict the use of the manual override capability to only {{ insert: param, si-10.01_odp }} ; and
- SI-10(1)(c)Audit the use of the manual override capability.
- SI-10(2)Review and resolve input validation errors within {{ insert: param, si-10.2_prm_1 }}.
- SI-10(3)Verify that the system behaves in a predictable and documented manner when invalid inputs are received.
- SI-10(4)Account for timing interactions among system components in determining appropriate responses for invalid inputs.
- SI-10(5)Restrict the use of information inputs to {{ insert: param, si-10.05_odp.01 }} and/or {{ insert: param, si-10.05_odp.02 }}.
- SI-10(6)Prevent untrusted data injections.
- SI-11aGenerate error messages that provide information necessary for corrective actions without revealing information that could be exploited; and
- SI-11bReveal error messages only to {{ insert: param, si-11_odp }}.
- SI-12Manage and retain information within the system and information output from the system in accordance with applicable laws, executive orders, directives, regulations, policies, stan
- SI-12(1)Limit personally identifiable information being processed in the information life cycle to the following elements of personally identifiable information: {{ insert: param, si-12.01
- SI-12(2)Use the following techniques to minimize the use of personally identifiable information for research, testing, or training: {{ insert: param, si-12.2_prm_1 }}.
- SI-12(3)Use the following techniques to dispose of, destroy, or erase information following the retention period: {{ insert: param, si-12.3_prm_1 }}.
- SI-13(1)Take system components out of service by transferring component responsibilities to substitute components no later than {{ insert: param, si-13.01_odp }} of mean time to failure.
- SI-13(3)Manually initiate transfers between active and standby system components when the use of the active component reaches {{ insert: param, si-13.03_odp }} of the mean time to failure.
- SI-13(4)If system component failures are detected:
- SI-13(4)(a)Ensure that the standby components are successfully and transparently installed within {{ insert: param, si-13.04_odp.01 }} ; and
- SI-13(4)(b){{ insert: param, si-13.04_odp.02 }}.
- SI-13(5)Provide {{ insert: param, si-13.05_odp.01 }} {{ insert: param, si-13.05_odp.02 }} for the system.
- SI-13aDetermine mean time to failure (MTTF) for the following system components in specific environments of operation: {{ insert: param, si-13_odp.01 }} ; and
- SI-13bProvide substitute system components and a means to exchange active and standby components in accordance with the following criteria: {{ insert: param, si-13_odp.02 }}.
- SI-14Implement non-persistent {{ insert: param, si-14_odp.01 }} that are initiated in a known state and terminated {{ insert: param, si-14_odp.02 }}.
- SI-14(1)Obtain software and data employed during system component and service refreshes from the following trusted sources: {{ insert: param, si-14.01_odp }}.
- SI-14(2)(a){{ insert: param, si-14.02_odp.01 }} ; and
- SI-14(2)(b)Delete information when no longer needed.
- SI-14(3)Establish connections to the system on demand and terminate connections after {{ insert: param, si-14.03_odp }}.
- SI-15Validate information output from the following software programs and/or applications to ensure that the information is consistent with the expected content: {{ insert: param, si-15
- SI-16Implement the following controls to protect the system memory from unauthorized code execution: {{ insert: param, si-16_odp }}.
- SI-17Implement the indicated fail-safe procedures when the indicated failures occur: {{ insert: param, si-17_prm_1 }}.
- SI-18(1)Correct or delete personally identifiable information that is inaccurate or outdated, incorrectly determined regarding impact, or incorrectly de-identified using {{ insert: param,
- SI-18(2)Employ data tags to automate the correction or deletion of personally identifiable information across the information life cycle within organizational systems.
- SI-18(3)Collect personally identifiable information directly from the individual.
- SI-18(4)Correct or delete personally identifiable information upon request by individuals or their designated representatives.
- SI-18(5)Notify {{ insert: param, si-18.05_odp }} and individuals that the personally identifiable information has been corrected or deleted.
- SI-18aCheck the accuracy, relevance, timeliness, and completeness of personally identifiable information across the information life cycle {{ insert: param, si-18_prm_1 }} ; and
- SI-18bCorrect or delete inaccurate or outdated personally identifiable information.
- SI-19(1)De-identify the dataset upon collection by not collecting personally identifiable information.
- SI-19(2)Prohibit archiving of personally identifiable information elements if those elements in a dataset will not be needed after the dataset is archived.
- SI-19(3)Remove personally identifiable information elements from a dataset prior to its release if those elements in the dataset do not need to be part of the data release.
- SI-19(4)Remove, mask, encrypt, hash, or replace direct identifiers in a dataset.
- SI-19(5)Manipulate numerical data, contingency tables, and statistical findings so that no individual or organization is identifiable in the results of the analysis.
- SI-19(6)Prevent disclosure of personally identifiable information by adding non-deterministic noise to the results of mathematical operations before the results are reported.
- SI-19(7)Perform de-identification using validated algorithms and software that is validated to implement the algorithms.
- SI-19(8)Perform a motivated intruder test on the de-identified dataset to determine if the identified data remains or if the de-identified data can be re-identified.
- SI-19aRemove the following elements of personally identifiable information from datasets: {{ insert: param, si-19_odp.01 }} ; and
- SI-19bEvaluate {{ insert: param, si-19_odp.02 }} for effectiveness of de-identification.
- SI-20Embed data or capabilities in the following systems or system components to determine if organizational data has been exfiltrated or improperly removed from the organization: {{ in
- SI-21Refresh {{ insert: param, si-21_odp.01 }} at {{ insert: param, si-21_odp.02 }} or generate the information on demand and delete the information when no longer needed.
- SI-22aIdentify the following alternative sources of information for {{ insert: param, si-22_odp.02 }}: {{ insert: param, si-22_odp.01 }} ; and
- SI-22bUse an alternative information source for the execution of essential functions or services on {{ insert: param, si-22_odp.03 }} when the primary source of information is corrupted
- SI-23Based on {{ insert: param, si-23_odp.01 }}:
- SI-23aFragment the following information: {{ insert: param, si-23_odp.02 }} ; and
- SI-23bDistribute the fragmented information across the following systems or system components: {{ insert: param, si-23_odp.03 }}.
- SR-1aDevelop, document, and disseminate to {{ insert: param, sr-1_prm_1 }}:
- SR-1a1{{ insert: param, sr-01_odp.03 }} supply chain risk management policy that:
- SR-1a1(a)Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
- SR-1a1(b)Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
- SR-1a2Procedures to facilitate the implementation of the supply chain risk management policy and the associated supply chain risk management controls;
- SR-1bDesignate an {{ insert: param, sr-01_odp.04 }} to manage the development, documentation, and dissemination of the supply chain risk management policy and procedures; and
- SR-1cReview and update the current supply chain risk management:
- SR-1c1Policy {{ insert: param, sr-01_odp.05 }} and following {{ insert: param, sr-01_odp.06 }} ; and
- SR-1c2Procedures {{ insert: param, sr-01_odp.07 }} and following {{ insert: param, sr-01_odp.08 }}.
- SR-2(1)Establish a supply chain risk management team consisting of {{ insert: param, sr-02.01_odp.01 }} to lead and support the following SCRM activities: {{ insert: param, sr-02.01_odp.0
- SR-2aDevelop a plan for managing supply chain risks associated with the research and development, design, manufacturing, acquisition, delivery, integration, operations and maintenance,
- SR-2bReview and update the supply chain risk management plan {{ insert: param, sr-02_odp.02 }} or as required, to address threat, organizational or environmental changes; and
- SR-2cProtect the supply chain risk management plan from unauthorized disclosure and modification.
- SR-3(1)Employ a diverse set of sources for the following system components and services: {{ insert: param, sr-3.1_prm_1 }}.
- SR-3(2)Employ the following controls to limit harm from potential adversaries identifying and targeting the organizational supply chain: {{ insert: param, sr-03.02_odp }}.
- SR-3(3)Ensure that the controls included in the contracts of prime contractors are also included in the contracts of subcontractors.
- SR-3aEstablish a process or processes to identify and address weaknesses or deficiencies in the supply chain elements and processes of {{ insert: param, sr-03_odp.01 }} in coordination
- SR-3bEmploy the following controls to protect against supply chain risks to the system, system component, or system service and to limit the harm or consequences from supply chain-relat
← records 1,201–1,600 · 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 2,001 on →