Source: http://docplayer.net/12094132-North-american-electric-reliability-corporation-critical-infrastructure-protection-version-5-nerc-cip-v5.html
Timestamp: 2018-04-24 07:51:44
Document Index: 271133891

Matched Legal Cases: ['arts 1', 'arts 5', 'art 2', 'art 2', 'art 2', 'art 3', 'art 4', 'art 4', 'art 4', 'art 1', 'art 1']

North American Electric Reliability Corporation: Critical Infrastructure Protection, Version 5 (NERC-CIP V5) - PDF
Download "North American Electric Reliability Corporation: Critical Infrastructure Protection, Version 5 (NERC-CIP V5)"
Maximilian Edmund Green
1 Whitepaper North American Electric Reliability Corporation: Critical Infrastructure Protection, Version 5 (NERC-CIP V5)
2 NERC-CIP Overview The North American Electric Reliability Corporation (NERC) is a nonprofit corporation dedicated to ensuring that the bulk electric system in North America is reliable, adequate and secure. As a federally designated Electric Reliability Organization (ERO), NERC maintains comprehensive reliability standards that define requirements for planning and operating the collective bulk power system. Among these are the Critical Infrastructure Protection (CIP) Cyber Security Standards, which are engineered to ensure the protection of cyber assets that are critical to the reliability of North America s bulk electric systems. In 2006, the Federal Energy Regulatory Commission (FERC) approved the Security and Reliability Standards proposed by NERC, making the CIP Cyber Security Standards mandatory and enforceable across all users, owners and operators of bulk-power systems. After going into effect in June 2006, initial compliance auditing began in June NERC-CIP Version 5 was released on November 22, It categorizes systems based on their impact to BES cyber assets, helping organizations identify risks to their infrastructure and prioritize mitigating efforts. Highand medium-impact BES cyber systems must adhere to NERC-CIP V5 by April 1, 2016, while low-impact BES cyber systems can wait until April 1, LogRhythm Supports NERC-CIP & NERC-CIP V5 NERC-CIP guides organizations to implement and perform procedures to effectively capture, monitor, retain and review log data. This can be challenging because IT environments consist of heterogeneous devices, systems, and applications reporting log data, and because millions of log entries can be generated daily, if not hourly. The task of assembling this information can be overwhelming, and the additional requirements to analyze and report on log data render manual processes or homegrown remedies inadequate and costly. LogRhythm s NERC-CIP compliance automation modules help companies meet these challenges. Further, to support companies transitioning from NERC-CIP V3 to NERC-CIP V5, we offer compliance automation modules for both regimes. The new V5 module leverages an entity-based structure to integrate impact categorization scoring into the logging, reporting, and real-time analytics and alarming capabilities of LogRhythm. LogRhythm uses this information to identify when activities of interest occur to high-, medium- and lowimpact BES cyber systems. NERC-CIP V5 Control Families & LogRhythm Support The remainder of this paper lists the NERC-CIP V5 control guidelines that LogRhythm helps address. For each control guideline, a description explains how LogRhythm supports the objective. PAGE 2
3 CIP-002-5: BES Cyber System Categorization R1. Each Responsible Entity shall implement a process that considers each of the following assets for purposes of parts 1.1 through 1.3: i. Control Centers and backup Control Centers; ii. Transmission stations and substations; iii. Generation resources; iv. Systems and facilities critical to system restoration, including Blackstart Resources and Cranking Paths and initial switching requirements; v. Special Protection Systems that support the reliable operation of the Bulk Electric System; and vi. For Distribution Providers, Protection Systems specified in Applicability section above. 1.1 Identify each of the high-impact BES Cyber Systems according to Attachment 1, Section 1, if any, at each asset; 1.2 Identify each of the medium-impact BES Cyber Systems according to Attachment 1, Section 2, if any, at each asset; and 1.3 Identify each asset that contains a low-impact BES Cyber System according to Attachment 1, Section 3, if any (a discrete list of low impact BES Cyber Systems is not required). LogRhythm augments the control objectives by allowing the organization to leverage an entity-based structure to apply the categorization of BES Cyber Systems into High, Medium and Low impacts. All components of the NERC-CIP Compliance Automation Module then apply the entity structure for easy identification of logging activities by impact. PAGE 3
4 CIP : Personnel & Training R4. Each Responsible Entity shall implement, in a deficiencies, one or more documented access management programs that collectively include each of the applicable requirement parts in CIP Table R4 Access Management Program. 4.1 Process to Authorize based on need, as determined by the Responsible Entity, except for CIP Exceptional Circumstances: Electronic access; Unescorted physical access into a Physical Perimeter; and Access to designated storage locations, whether physical or electronic, for BES Cyber System Information. 4.2 Verify at least once each calendar quarter that individuals with active electronic access or unescorted physical access have Authorization records. 4.3 For electronic access, verify at least once every 15 calendar months that all user accounts, user account groups, or user role categories, and their specific, associated privileges are correct and are those that the Responsible Entity determines are necessary. 4.4 Verify at least once every 15 calendar months that access to the designated storage locations for BES Cyber System Information, whether physical or electronic, are correct and are those that the Responsible Entity determines are necessary for performing assigned work functions. LogRhythm augments control R4 by monitoring any access provisioning activities within the environment. Further, authentication or access activities to both physical and electronic access point are monitored. Privileged accounts or groups, both by default or defined by the organization, are also monitored for access provisioning, authentication and access activities due to their impact within the environment. LogRhythm module content provides reports, alerts and investigations, enabling the organization s periodic access review process. LogRhythm both augments and directly addresses control objectives within R5 by alerting and reporting on access deprovisioning due to reassignment, transfer or termination. This enables the organization to measure policy adherence for timely modification or removal of access. PAGE 4
5 CIP : Personnel & Training (cont.) R5. Each Responsible Entity shall implement, in a deficiencies, one or more documented access revocation programs that collectively include each of the applicable requirement parts in CIP Table R5 Access Revocation. 5.1 A process to initiate removal of an individual s ability for unescorted physical access and Interactive Remote Access upon a termination action, and complete the removals within 24 hours of the termination action (Removal of the ability for access may be different than deletion, disabling, revocation, or removal of all access rights.) 5.2 For reassignments or transfers, revoke the individual s Authorized electronic access to individual accounts and Authorized unescorted physical access that the Responsible Entity determines are not necessary by the end of the next calendar day following the date that the Responsible Entity determines that the individual no longer requires retention of that access. 5.3 For terminations actions, revoke the individual s access to the designated storage locations for BES Cyber System Information, whether physical or electronic (unless already revoked according to Requirement R5.1), by the end of the next calendar day following the effective date of the termination action. 5.4 For termination actions, revoke the individual s non-shared user accounts (unless already revoked according to Parts 5.1 or 5.3) within 30 calendar days of the effective date of the termination action. 5.5 For termination actions, change passwords for shared account(s) known to the user within 30 calendar days of the termination action. For reassignments or transfers, change passwords for shared account(s) known to the user within 30 calendar days following the date the Responsible Entity determines that the individual no longer requires retention of that access. If the Responsible Entity determines and documents that extenuating operating circumstances require a longer period, change the password(s) within 10 calendar days following the end of the operating circumstances. LogRhythm augments control R4 by monitoring any access provisioning activities within the environment. Further, authentication or access activities to both physical and electronic access point are monitored. Privileged accounts or groups, both by default or defined by the organization, are also monitored for access provisioning, authentication and access activities due to their impact within the environment. LogRhythm module content provides reports, alerts and investigations, enabling the organization s periodic access review process. LogRhythm both augments and directly addresses control objectives within R5 by alerting and reporting on access deprovisioning due to reassignment, transfer or termination. This enables the organization to measure policy adherence for timely modification or removal of access. PAGE 5
6 CIP-005-5: Electronic Security Perimeter(s) R1. Each Responsible Entity shall implement one or more documented processes that collectively include each of the applicable requirement parts in CIP Table R1 Electronic Security Perimeter. 1.1 All applicable Cyber Assets connected to a network via a routable protocol shall reside within a defined ESP. 1.2 All External Routable Connectivity must be through an identified Electronic Access Point (EAP). 1.3 Require inbound and outbound access permissions, including the reason for granting access, and deny all other access by default R2. Each Responsible Entity allowing Interactive Remote Access to BES Cyber Systems shall implement one or more documented processes that collectively include the applicable requirement parts, where technically feasible: 2.1 Utilize an Intermediate System such that the Cyber Asset initiating Interactive Remote Access does not directly access an applicable Cyber Asset. 2.2 For all Interactive Remote Access sessions, utilize encryption that terminates at an Intermediate System. 2.3 Require multi-factor Authentication for all Interactive Remote Access sessions. LogRhythm both directly supports and augments objectives within control R1 through enhanced analytics and reporting at the Electronic Security Perimeter. Advanced correlation and alerting reduce the interval to detect and respond to vulnerabilities and attacks against the network. Further analysis of uncommon or suspicious network activities is facilitated through real-time analytics, compliance reports and forensic investigations. LogRhythm augments objectives within control R2 by alerting on potentially malicious activity through VPN tunnels, wireless access points and use of unencrypted network protocols. Reports and investigations allow for detailed review of activities related to points of network access. PAGE 6
7 CIP-006-5: Physical Security of BES Cyber Systems R1. Each Responsible Entity shall implement, in a deficiencies, one or more documented Physical plans that collectively include all of the applicable requirement parts in CIP Table R1 Physical Plan. 1.1 Define operational or procedural controls to restrict physical access. 1.2 Utilize at least one physical access control to allow unescorted physical access into each applicable Physical Perimeter to only those individuals who have authorized unescorted physical access. 1.3 Where technically feasible, utilize two or more different physical access controls (this does not require two completely independent physical access control systems) to collectively allow unescorted physical access into Physical Perimeters to only those individuals who have Authorized unescorted physical access. 1.4 Monitor for unauthorized access through a physical access point into a Physical Perimeter. 1.5 Issue an alarm or alert in response to detected unauthorized access through a physical access point into a Physical Perimeter to the personnel identified in the BES Cyber Security Incident response plan within 15 minutes of detection. 1.6 Monitor each Physical Access Control System for unauthorized physical access to a Physical Access Control System. 1.7 Issue an alarm or alert in response to detected unauthorized physical access to a Physical Access Control System to the personnel identified in the BES Cyber Security Incident response plan within 15 minutes of the detection. 1.8 Log (through automated means or by personnel who control entry) entry of each individual with Authorized unescorted physical access into each Physical Perimeter, with information to identify the individual and date and time of entry. 1.9 Retain physical access logs of entry of individuals with Authorized unescorted physical access into each Physical Perimeter for at least ninety calendar days. LogRhythm directly supports most objectives within controls R1 and R2 by alerting and reporting on access success and failure activity at the Physical Security Perimeter. Reporting and investigations can also allow operations teams to inspect suspicious physical access activities. Depending on the processes employed by the organization to regulate visitor access, LogRhythm can augment objectives within R2. The above methods of alerting, reporting and investigations can also be used to automate physical access processes. PAGE 7
8 CIP-006-5: Physical Security of BES Cyber Systems (cont.) R2. Each Responsible Entity shall implement, in a deficiencies, one or more documented visitor control programs that include each of the applicable requirement parts in CIP Table R2 Visitor Control Program. 2.1 Require continuous escorted access of visitors (individuals who are provided access but are not Authorized for unescorted physical access) within each Physical Perimeter, except during CIP Exceptional Circumstances. 2.2 Require manual or automated logging of visitor entry into and exit from the Physical Perimeter that includes date and time of the initial entry and last exit, the visitor s name, and the name of an individual point of contact responsible for the visitor, except during CIP Exceptional Circumstances. 2.3 Retain visitor logs for at least ninety calendar days. LogRhythm directly supports most objectives within controls R1 and R2 by alerting and reporting on access success and failure activity at the Physical Security Perimeter. Reporting and investigations can also allow operations teams to inspect suspicious physical access activities. Depending on the processes employed by the organization to regulate visitor access, LogRhythm can augment objectives within R2. The above methods of alerting, reporting and investigations can also be used to automate physical access processes. PAGE 8
9 CIP-007-5: System Security Management 007 R5. Each Responsible Entity shall implement, in a deficiencies, one or more documented processes that collectively include each of the applicable requirement parts in CIP Table R5 System Access Controls. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]. 5.2 Identify and inventory all known enabled default or other generic account types, either by system, by grouped of systems, by location, or by system type(s). 5.3 Identify individuals who have Authorized access to shared accounts. 5.4 Change known default passwords, per Cyber Asset capability. 5.5 For password-only Authentication for interactive user access, either technically or procedurally enforce the following password parameters: Password length that is, at least, the lesser of eight characters or the maximum length supported by the Cyber Asset; and Minimum password complexity that is the lesser of three or more different types of characters (e.g., uppercase alphabetic, lowercase alphabetic, numeric, non-alphanumeric) or the maximum complexity supported by the Cyber Asset. 5.6 Where technically feasible, for password-only Authentication for interactive user access, either technically or procedurally enforce password changes or an obligation to change the password at least once every 15 calendar months. 5.7 Where technically feasible, either: Limit the number of unsuccessful Authentication attempts; or Generate alerts after a threshold of unsuccessful Authentication attempts LogRhythm both directly supports and augments the authentication-based objectives in controls 007 R5 and R5. Lists can be used to monitor group various groups of accounts to monitor and report on activities, enabling processes that can be easily integrated with existing account access reviews. Password maintenance protocols can also be aligned between compliance and operational systems. LogRhythm augments objectives in control R2 and R3 by providing reports and detailed investigations on patches and signature updates applied within the environment. These details support existing change and patch management controls. LogRhythm provides both direct and augmented support of controls R3 and R4, which concern monitoring and reporting of malicious activity at various layers of the environment. Correlation and alerting help reduce the time to detect and mitigate these threats. Further monitoring of failed authentication and suspicious activity could provide early indicators of compromised accounts. PAGE 9
10 CIP-007-5: System Security Management (cont.) R2. Each Responsible Entity shall implement, in a deficiencies, one or more documented processes that collectively include each of the applicable requirement parts in CIP Table R2 Security Patch Management. 2.1 A patch management process for tracking, evaluating, and installing cyber security patches for applicable Cyber Assets. The tracking portion shall include the identification of a source or sources that the Responsible Entity tracks for the release of cyber security patches for applicable Cyber Assets that are updateable and for which a patching source exists. 2.2 At least once every 35 calendar days, evaluate security patches for applicability that have been released since the last evaluation from the source or sources identified in Part For applicable patches identified in Part 2.2, within 35 calendar days of evaluation completion, take one of the following actions: Apply the applicable patches; or Create a dated mitigation plan; or Revise an existing mitigation plan. Mitigation plans shall include the Responsible Entity s planned actions to mitigate the vulnerabilities addressed by each security patch and a timeframe to complete these mitigations. 2.4 For each mitigation plan created or revised in Part 2.3, implement the plan within the timeframe specified in the plan, unless a revision to the plan or an extension to the timeframe specified in Part 2.3 is approved by the CIP Senior Manager or delegate R3. Each Responsible Entity shall implement, in a deficiencies, one or more documented processes that collectively include each of the applicable requirement parts in CIP Table R3 Malicious Code Prevention. 3.1 Deploy method(s) to deter, detect, or prevent malicious code. 3.2 Mitigate the threat of detected malicious code. 3.3 For those methods identified in Part 3.1 that use signatures or patterns, have a process for the updated of the signatures or patterns. The process must address testing and installing the signatures or patterns. LogRhythm both directly supports and augments the authentication-based objectives in controls 007 R5 and R5. Lists can be used to monitor group various groups of accounts to monitor and report on activities, enabling processes that can be easily integrated with existing account access reviews. Password maintenance protocols can also be aligned between compliance and operational systems. LogRhythm augments objectives in control R2 and R3 by providing reports and detailed investigations on patches and signature updates applied within the environment. These details support existing change and patch management controls. LogRhythm provides both direct and augmented support of controls R3 and R4, which concern monitoring and reporting of malicious activity at various layers of the environment. Correlation and alerting help reduce the time to detect and mitigate these threats. Further monitoring of failed authentication and suspicious activity could provide early indicators of compromised accounts. PAGE 10
11 CIP-007-5: System Security Management (cont.) R4. Each Responsible Entity shall implement, in a deficiencies, one or more documented processes that collectively include each of the applicable requirement parts in CIP Table R4 Security Event Monitoring. 4.1 Log events at the BES Cyber System level (per BES Cyber System capability) or at the Cyber Asset level (per Cyber Asset capability) for identification of, and after-thefact investigations of, Cyber Security Incidents that includes, as a minimum, each of the following types of events: Detected successful login attempts; Detected failed access attempts and failed login attempts; Detected malicious code. 4.2 Generate alerts for security events that the Responsible Entity determines necessitates, an alert, that includes, as a minimum, each of the following types of events (per Cyber Asset or BES Cyber System capability): Detected malicious code from Part 4.1; and Detected failure of Part 4.1 event logging. 4.3 Where technically feasible, retain applicable event logs identified in Part 4.1 for at least the last 90 consecutive calendar days except under CIP Exceptional Circumstances. 4.4 Review and summarization of sampling of logged events as determined by the Responsible Entity at intervals no greater than 15 calendar days to identify undetected Cyber Security Incidents R5. Each Responsible Entity shall implement, in a deficiencies, one or more documented processes that collectively include each of the applicable requirement parts in CIP Table R5 System Access Controls. 5.1 Have a method(s) to enforce Authentication of interactive user access, where technically feasible. LogRhythm both directly supports and augments the authentication-based objectives in controls 007 R5 and R5. Lists can be used to monitor group various groups of accounts to monitor and report on activities, enabling processes that can be easily integrated with existing account access reviews. Password maintenance protocols can also be aligned between compliance and operational systems. LogRhythm augments objectives in control R2 and R3 by providing reports and detailed investigations on patches and signature updates applied within the environment. These details support existing change and patch management controls. LogRhythm provides both direct and augmented support of controls R3 and R4, which concern monitoring and reporting of malicious activity at various layers of the environment. Correlation and alerting help reduce the time to detect and mitigate these threats. Further monitoring of failed authentication and suspicious activity could provide early indicators of compromised accounts. PAGE 11
12 CIP-008-5: Incident Reporting & Response Planning R1. Each Responsible Entity shall document one or more Cyber Security Incident response plan(s) that collectively include each of the applicable requirement parts in CIP Table R1 Cyber Security Incident Response Plan Specifications. 1.1 One or more processes to identify, classify, and respond to Cyber Security Incidents. 1.2 One or more processes to determine if an identified Cyber Security Incident is a Reportable Cyber Security Incident and notify the Electricity Sector Information Sharing and Analysis Center (ES-ISAC), unless prohibited by law. Initial notification to the ES-ISAC, which may be only a preliminary notice, shall not exceed one hour from the determination of a Reportable Cyber Security Incident. 1.3 The roles and responsibilities of Cyber Security Incident response groups or individuals. 1.4 Incident handling procedures for Cyber Security Incidents R2. Each Responsible Entity shall implement each of its documented Cyber Security Incident response plans to collectively include each of the applicable requirement parts in CIP Table R2 Cyber Security Incident Response Plan Implementation and Testing. 2.1 Test each Cyber Security Incident response plan(s) at least once every 15 calendar months: By responding to an actual Reportable Cyber Security Incident; With a paper drill or tabletop exercise of a Reportable Cyber Security Incident; or With an operational exercise of a Reportable Cyber Security Incident. 2.2 Use the Cyber Security Incident response plan(s) under Requirement R1 when responding to a Reportable Cyber Security Incident or performing an exercise of a Reportable Cyber Security Incident. Document deviations from the plan(s) taken during the response to the incident or exercise. 2.3 Retain records related to Reportable Cyber Security Incidents. LogRhythm augments objectives within controls R1, R2 and R3 to support Incident Response activates. As previously discussed, alerts and advanced correlation help identify potentially harmful activities within the environment. LogRhythm s reporting and investigations around security events allows IT and Security Operations to gather forensic data to better understand and ultimately mitigate malicious activity. The scope of security events expands from monitoring network and remote connections at the Electronic Security Perimeter to suspicious activity and compromised internal accounts. By gathering forensic data and leveraging powerful correlation across the environment, LogRhythm AI Engine rules, alerts, reports and investigations provide ample details for organizations to learn and adapt to ever changing threat landscape. PAGE 12
13 CIP-008-5: Incident Reporting & Response Planning (cont.) R3. Each Responsible Entity shall maintain each of its Cyber Security Incident response plans according to each of the applicable requirement parts in CIP Table R3 Cyber Security Incident Response Plan Review, Update, and Communication. 3.1 No later than 90 calendar days after completion of a Cyber Security Incident response plan(s) test or actual Reportable Cyber Security Incident response: Document any lessons learned or document the absence of any lessons learned; Update the Cyber Security Incident response plan based on any documented lessons learned associated with the plan; and Notify each person or group with a defined role in the Cyber Security Incident response plan of the updates to the Cyber Security Incident response plan based on any documented lessons learned. 3.2 No later than 60 calendar days after a change to the roles or responsibilities, Cyber Security Incident response groups or individuals, or technology that the Responsible Entity determines would impact the ability to execute the plan: Update the Cyber Security Incident response plan(s); and Notify each person or group with a defined role in the Cyber Security Incident response plan of the updates. LogRhythm augments objectives within controls R1, R2 and R3 to support Incident Response activates. As previously discussed, alerts and advanced correlation help identify potentially harmful activities within the environment. LogRhythm s reporting and investigations around security events allows IT and Security Operations to gather forensic data to better understand and ultimately mitigate malicious activity. The scope of security events expands from monitoring network and remote connections at the Electronic Security Perimeter to suspicious activity and compromised internal accounts. By gathering forensic data and leveraging powerful correlation across the environment, LogRhythm AI Engine rules, alerts, reports and investigations provide ample details for organizations to learn and adapt to ever changing threat landscape. PAGE 13
14 CIP-009-5: Recovery Plans for BES Cyber Systems R1. Each Responsible Entity shall have one or more documented recovery plans that collectively include each of the applicable requirement parts in CIP Table R1 Recovery Plan Specifications. 1.1 Conditions for activation of the recovery plan(s). 1.2 Roles and responsibilities of responders. 1.3 One or more processes for the backup and storage of information required to recover BES Cyber System functionality. 1.4 One or more processes to verify the successful completion of the backup processes in Part 1.3 and to address any backup failures. 1.5 One or more processes to preserve data, per Cyber Asset capability, for determining the cause of a Cyber Security Incident that triggers activation of the recovery plan(s). Data preservation should not impede or restrict recovery. LogRhythm augments objectives within control R1 with alerts that provide advanced notice when critical or error events occur. These backup failures, along with successful backup operations, are also captures in reports and detailed investigations. PAGE 14
15 CIP-010-1: Configuration Change Management & Vulnerability Assessments R1. Each Responsible Entity shall implement, in a deficiencies, one or more documented processes that collectively include each of the applicable requirement parts in CIP Table R1 Configuration Change Management. 1.1 Develop a baseline configuration, individually or by group, which shall include the following items: Operating system(s) (including version) or firmware where no independent operating system exists; Any commercially available or opensource application software (including version) intentionally installed; Any custom software installed; Any logical network accessible ports; and Any security patches applied. 1.2 Authorize and document changes that deviate from the existing baseline configuration. 1.3 For a change that deviates from the existing baseline configuration, update the baseline configuration as necessary within 30 calendar days of completing the change. 1.4 For a change that deviates from the existing baseline configuration: Prior to the change, determine required cyber security controls in CIP-005 and CIP-007 that could be impacted by the change; Following the change, verify that required cyber security controls determined in are not adversely affected; and Document the results of the verification. LogRhythm augments objectives within controls CIP R1 and CIP R2 by working with existing change control procedures to alert and report on various types of changes occurring across the environment. Alerts can be configured across all log sources to identify when configuration/policies are changed, signatures or patched are updated, and when software installation occurs. Reports and investigations, coupled with timely alerts of changes, provide additional details to ensure change control procedures are adhered to and any deviations from standard procedures are identified. Further, in order to augment CIP R3, LogRhythm integrates with Rapid7 vulnerability and other scanners to indicate when a vulnerability is identified by the solution. Organizations may also leverage existing AI Engine rules and reports (outside of the NERC-CIP module) to identify when a vulnerability scan occurs outside of an approved time window. PAGE 15
16 CIP-010-1: Configuration Change Management & Vulnerability Assessments (cont.) 1.5 Where technically feasible, for each change that deviates from the existing baseline configuration: Prior to implementing any change in the production environment, test the changes in a test environment or test the changes in a production environment where the test is performed in a manner that minimizes adverse effects, that models the baseline configuration to ensure that required cyber security controls in CIP-005 and CIP-007 are not adversely affected; and Document the results of the testing and, if a test environment was used, the differences between the test environment and the production environment, including a description of the measures used to account for any differences in operation between the test and production environments R2. Each Responsible Entity shall implement, in a deficiencies, one or more documented processes that collectively include each of the applicable requirement parts in CIP Table R2 Configuration Monitoring. 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.differences in operation between the test and production environments R3. Each Responsible Entity shall implement one or more documented processes that collectively include each of the applicable requirement parts in CIP Table R3 Vulnerability Assessments. 3.1 At least once every 15 calendar months, conduct a paper or active vulnerability assessment. LogRhythm augments objectives within controls CIP R1 and CIP R2 by working with existing change control procedures to alert and report on various types of changes occurring across the environment. Alerts can be configured across all log sources to identify when configuration/policies are changed, signatures or patched are updated, and when software installation occurs. Reports and investigations, coupled with timely alerts of changes, provide additional details to ensure change control procedures are adhered to and any deviations from standard procedures are identified. Further, in order to augment CIP R3, LogRhythm integrates with Rapid7 vulnerability and other scanners to indicate when a vulnerability is identified by the solution. Organizations may also leverage existing AI Engine rules and reports (outside of the NERC-CIP module) to identify when a vulnerability scan occurs outside of an approved time window. In order to begin the transition from version 3 to version 5 of NERC-CIP various resources can be leveraged in preparation. NERC-CIP v.5 Transition Guide NERC-CIP v. 5 Implementation Study, Lessons Learned and FAQs NERC-CIP Overview NERC-CIP Standards/Controls For additional information on how LogRhythm can assist in augmenting your NERC-CIP compliance objectives please visit the LogRhythm Website. PAGE LogRhythm Inc. LogRhythm_NERC_CIP_Whitepaper_10.15