3.14 SYSTEM AND INFORMATION INTEGRITY
Refresh [Assignment: organization-defined systems and system components] from a known trusted state [Assignment: organization-defined frequency].
This requirement mitigates risk from the APT by reducing the targeting capability of adversaries (i.e. the window of opportunity for the attack). By implementing the concept of non-persistence for selected system components organizations can provide a known state computing resource for a specific time period that does not give adversaries sufficient time to exploit vulnerabilities in organizational systems and the environments in which those systems operate. Since the APT is a high-end sophisticated threat regarding capability intent and targeting organizations assume that over an extended period a percentage of attacks will be successful. Non-persistent system components and system services are activated as required using protected information and are terminated periodically or at the end of sessions. Non-persistence increases the work factor of adversaries attempting to compromise or breach systems.Non-persistence can be achieved by refreshing system components (e.g. periodically reimaging components or using a variety of common virtualization techniques). Non-persistent services can be implemented using “Infrastructure as Code” to automatically build configure test deploy and manage containers virtual machines or new instances of processes on physical machines (both persistent or non-persistent). Periodic refreshes of system components and services do not require organizations to determine whether compromises of components or services have occurred (something that may often be difficult to determine). The refresh of selected system components and services occurs with sufficient frequency to prevent the spread or intended impact of attacks but not with such frequency that it makes the system unstable. Refreshes may be done periodically to hinder the ability of adversaries to exploit optimum windows of vulnerabilities. The reimaging of system components includes the reinstallation of firmware operating systems and applications from a known trusted source. Reimaging also includes the installation of patches reapplication of configuration settings and refresh of system or application data from a known trusted source.
What is a Cybersecurity Compliance Framework?
You don’t need to clutter your security and privacy programs with an ever-increasing number of tools as they become more sophisticated. The Lionfish platform offers a one-stop solution to track progress and monitor any framework, from custom-built ones to highly-specialized and in-demand top security and privacy frameworks and certifications.
With the Lionfish platform, every framework is supported with guided scoping, policies, controls, automated evidence collection, and continuous monitoring, ensuring efficient preparation for audits or attestation in minimal time.
The Lionfish platform is compatible with a wide range of security and privacy frameworks, including:
- CMMC v2
- NERC CIP-002 through CIP-014 Revision 6
- NIST 800-171
- NIST 800-172
- PCI (Payment Card Industry Security Standard)
- SOC 2
- NIST 800-53
- NIST SP800-161 Supply Chain Risk Management
- CIS Framework Controls V8