NERC CIP-003-9: What Now? Response Requirements (Part 3)
NERC CIP-003-9
Keon McEwen | Ben Stirling | Sean Thompson | Joe Baxter
Webinar Information
Quick Recap NERC CIP-003-9
3
The New Requirements and How to Comply – Part 1
What You Should Do vs What You Must Do – Part 2
NERC CIP-003-9 – What can Make Your Program Successful
4
Ensure Plant Personnel �from Management to I&C �and Operations Understand �the Requirements
Compliance has a �Good Understanding �of Each Site
Drive to Consistency
Securing generation and compliance with NERC CIP is not a simple task (don’t expect this to be a quick or easy journey).
The combination requires an intimate understanding of the specific generation process and the Cyber and Physical unique footprint of each site.
Only with the two objectives in mind can you achieve both
Understand the Difference
5
6.1 Vendor Electronic Remote Access (VERA)�
6
6.1 One or more method(s) for determining vendor electronic remote access;
Evidence
Required:
Document ALL network paths that CAN or could be used by Vendors for remote access
Develop and document methods to authorize Vendor remote access
Develop and document methods to monitor Vendor remote access
Develop and document methods to alert and record Vendor remote access
6.1 Vendor Electronic Remote Access (VERA)�
7
Internet
LIBCS
Your Site
Internet
VERA
6.1 Vendor Electronic Remote Access (VERA)�
8
6.2 Method(s) for Disabling Vendor Remote Access�
6.2 One or more method(s) for disabling vendor electronic remote access;
�Evidence
required:
9
Develop and document methods for disabling vendor remote access
Develop and document methods for disabling inbound and/or outbound communication
Develop and document methods for removing physical layer connectivity (brake glass approach)
6.3 Detecting Known or Suspected Malicious Communications�
6.3 One or more method(s) for detecting known or suspected inbound and outbound malicious communications for vendor electronic remote access
�Evidence
required:
10
Document use of Anti‐malware technologies (where they are installed and how they are updated)
Document use of Intrusion Detection/Prevention Systems IDS/IPS
Document use of automated and/or manual log review
Document use of automated and/or manual alerting
Why Consistency Matters for Security and Audits
11
Inconsistency
Security: �Two Analysts = Two Outcomes
Compliance: �Significance of Contradiction
What Consistency Looks Like (and How We can Help)
12
Compliance and Response to RFI
Reduced Burden for Plant Personnel
Concise Responses to RFIs and �Reduced RFIs Follow Up
Documentation and Preparation
Consistent Recording of Security and Compliance Actions for IR Activities
Technical Documentation: Validation and Packaging
Security and Monitoring
Reliable Logging and Analysis
Effective Threat Detection and �Incident Response (IR)
Questions
Thank You
NERC CIP Services Supervisor
Director - Solutions Engineering
Keon McEwen�ISOC Director, Industrial Cybersecurity �kmcewen@abs-group.com�
Director - Industrial Cybersecurity