NERC CIP-002 through CIP-014 Revision 6
2.1 Monitor at least once every 35 calendar days for changes to the baseline configuration (as described in Requirement R1 Part 1.1). Document and investigate detected unauthorized changes.
M2. Evidence must include each of the applicable documented processes that collectively include each of the applicable requirement parts in CIP-010-2 Table R2– Configuration Monitoring and additional evidence to demonstrate implementation as described in the Measures column of the table.CIP-010-2 Table R2– Configuration Monitoring Part Applicable Systems Requirements Measures 2.1 High Impact BES Cyber Systems and their associated: EACMS; andPCAMonitor at least once every 35 calendar days for changes to the baseline configuration (as described in Requirement R1 Part 1.1). Document and investigate detected unauthorized changes. An example of evidence may include but is not limited to logs from a system that is monitoring the configuration along with records of investigation for any unauthorized changes that were detected.
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