Ben christensen senior cip enforcement analyst
This presentation is the property of its rightful owner.
Sponsored Links
1 / 116

Ben Christensen Senior CIP Enforcement Analyst PowerPoint PPT Presentation


  • 168 Views
  • Uploaded on
  • Presentation posted in: General

Ben Christensen Senior CIP Enforcement Analyst. CIP-010-1 May 15, 2014 SLC, UT. Pop Quiz!!. Who invented the electric motor? William Sturgeon Thomas Davenport Michael Faraday. Pop Quiz!!. Who invented the electric motor?. Michael Faraday. Agenda.

Download Presentation

Ben Christensen Senior CIP Enforcement Analyst

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Ben christensen senior cip enforcement analyst

Ben ChristensenSenior CIP Enforcement Analyst

CIP-010-1

May 15, 2014

SLC, UT


Pop quiz

Pop Quiz!!

  • Who invented the electric motor?

    • William Sturgeon

    • Thomas Davenport

    • Michael Faraday


Pop quiz1

Pop Quiz!!

  • Who invented the electric motor?

Michael Faraday


Agenda

Agenda

  • Help entities understand and prepare for the upcoming CIP 010-1

    • Differences and relations to current requirements

    • Possible pitfalls to look for while implementing CIP 010-1

    • WECC’s audit approach

    • Best practices


Cip 010 1

CIP 010-1


Purpose of cip 010 1

Purpose of CIP 010-1

  • Prevent and detect unauthorized changes to BES Cyber Systems.

  • Specify vulnerability assessment requirements in support of protecting BES Cyber Systems from compromise.

  • Document and maintain device baselines and periodically verify they are accurate.


Applicable systems

Applicable Systems


Cip 010 1 similarities with v 3

CIP 010-1 Similarities with V.3

  • CIP 003-3 R6: Change Control and Configuration Management

  • CIP 007-3 R1: Test procedures

  • CIP 005-3 R4 and CIP 007-3 R8: Cyber Vulnerability Assessment(s)

  • CIP 007-3 R9 andCIP 005-3 R5: Documentation review and maintenance


Pop quiz2

POP Quiz!!

  • Who invented the modern automobile?

    • Henry Ford

    • Karl Benz

    • Ransom Olds


Pop quiz3

Pop Quiz!!

  • Who invented the modern automobile?

Karl Benz


Cip 010 1 r1

CIP 010-1 R1


Cip 010 1 r1 1

CIP 010-1 R1.1

  • Applicable to Protected Cyber Assets (PCA) and specifies information required in device baselines

CIP 003-3 R6

CIP 010-1 R1.1


Cip 010 1 r1 1 possible pitfall 1

CIP-010-1 R1.1 - Possible Pitfall #1

  • CIP 003-3 R6 was previously not applicable to Non-CCAs that resided within an ESP. Thus entity did not create baselines or update procedures to ensure baselines were maintained for these devices.


Cip 010 1 r1 1 possible pitfall 2

CIP-010-1 R1.1 - Possible Pitfall #2

  • Entity does not ensure documented baselines for all devices contain operating system, commercial/open source software, custom software, logical ports, and security patches applied.


Cip 010 1 r1 1 approach

CIP-010-1 R1.1 Approach

  • Ensure entity has documented baselines for all devices (or group of devices) in applicable BES Cyber Systems

    • Verify Baselines include operating system/firmware, commercial software, custom software, logical network accessible ports, and security patches applied


Cip 010 1 r1 1 best practice

CIP 010-1 R1.1 Best Practice

  • Use combination of automated tools and manual walkthroughs/verifications to ensure lists and baselines are accurate

  • Minimize applications on devices to only what is necessary

  • Include step to periodically verify accuracy of applicable device lists and baselines


Cip 010 1 r1 1 best practice1

CIP 010-1 R1.1 Best Practice

  • Discussions and careful planning should be conducted on the method for maintaining device baselines

    • Review CIP 007 R3 presentation from Oct 2013 CIPUG for common methods to maintain information

    • What method is best for your organization:

      • Commercial Software

      • Custom Software

      • Spreadsheet


Cip 010 1 r1 1 best practice2

CIP 010-1 R1.1 Best Practice

  • Consider Moving away from spreadsheets and other manual methods, look into more advanced methods for retaining information.

    • See Joe B presentation from October 2011 CIPUG on advantages of moving from spreadsheet to relational database

      • Includes some labeling schema tips as well for when implementing a database for device management


Cip 010 1 r1 2

CIP 010-1 R1.2

  • Applicable to PCA and requires changes to be authorized

CIP 003-3 R6

CIP 010-1 R1.2


Cip 010 1 r1 2 possible pitfall

CIP-010-1 R1.2 - Possible Pitfall

  • Entity cannot demonstrate all changes made to baseline(s) were authorized


Cip 010 1 r1 2 approach

CIP 010-1 R1.2 - Approach

  • Ensure all changes made to baselines have been authorized.


Cip 010 1 r1 2 best practice

CIP 010-1 R1.2 – Best Practice

  • Update procedural documentation to include at minimum:

    • Who can authorize changes, and to what

    • When authorization needs to occur

    • How the authorization will be documented, stored, and tracked

  • Segregation of duties

    • The implementer should be different from the authorizer


Cip 010 1 r1 3

CIP 010-1 R1.3

  • Baselines must be updated within 30 days of change

CIP 005-3 R5

CIP 010-1 R1.3

CIP 007-3 R9


Cip 010 1 r1 3 possible pitfall

CIP 010-1 R1.3 – Possible Pitfall

  • Entity cannot demonstrate baselines are updated within 30 days of changes made


Cip 010 1 r1 3 approach

CIP 010-1 R1.3 - Approach

  • Ensure entity is updating baselines within 30 days of when change was made.

    • Start date will be determined by reviewing work orders, tracking sheet, or other documentation that details when the change actually occurred.


Cip 010 1 r1 3 best practices

CIP 010-1 R1.3 – Best Practices

  • Procedures for updating baselines should address:

    • Who will communicate the changes made to the baselines

    • How changes will be communicated

    • Who the changes are communicated to

    • When the changes will be made


Cip 010 1 r1 3 best practices1

CIP 010-1 R1.3 – Best Practices

  • Maintain a version history when updating documentation.

    • Version number

    • Who performed the update to the documentation

    • Who made the change to the device

    • Who authorized the change

    • What was changed


Pop quiz4

POP Quiz!!

  • Who invented the printing press?


Pop quiz5

POP Quiz!!

  • Who invented the printing press?

Johannes Gutenberg


Cip 010 1 r1 4

CIP 010-1 R1.4

  • Impact due to a change must consider security controls in CIP 005 and CIP 007

CIP 010-1 R1.4

CIP 007-3 R1


Cip 010 1 r1 4 possible pitfall

CIP 010-1 R1.4 – Possible Pitfall

  • Entity verifies same controls for all changes made to any baseline.

    • Thus entity does not account for different environments, devices, or changes when determining what controls could be impacted

      • May be ok if all controls are verified every time


Cip 010 1 r1 4 approach

CIP 010-1 R1.4 - Approach

  • Verify all changes made to device baselines are documented

  • Ensure controls that may be impacted were identified and documented prior to the change

    • Why were some controls not included?

  • Review evidence supporting identified controls were not adversely impacted


Cip 010 1 r1 4 best practices

CIP 010-1 R1.4 – Best Practices

  • Procedures should include:

    • Documenting date all steps taken to support cyber security controls were identified prior to change taking place

    • How are potential impacted cyber security controls identified?

      • Who does this?

    • How will adverse impacts will be detected

      • Who does this and when?


Cip 010 1 r1 4 best practices1

CIP 010-1 R1.4 – Best Practices

  • Include a peer review step for reviewing what controls may be impacted and when verifying controls weren’t adversely impacted

  • Coordinate testing processes between departments, business units, etc. to ensure consistency


Cip 010 1 r1 5

CIP 010-1 R1.5

CIP 010-1 R1.5

CIP 007-3 R1


Cip 010 1 r1 5 cont

CIP 010-1 R1.5 cont..

  • Only applicable to High Impact systems

  • Specific to security controls that must be tested

    • Security Controls in CIP 005 and CIP 007

  • New test environment requirements

    • Document if test environment was used

    • Document differences between test and production environment

      • Measures taken to account for these differences


Cip 010 1 r1 5 possible pitfall

CIP 010-1 R1.5 Possible Pitfall

  • Entity does not document differences between production and testing environment

  • Entity does not take measures to account for differences in the production and testing environment.


Cip 010 1 r1 5 approach

CIP 010-1 R1.5 - Approach

  • For each change that deviates from existing baseline:

    • List of cyber security controls tested

      • Test results

      • List of differences between the production and test environments

      • Descriptions of how any differences were accounted for

      • When testing occurred.


Cip 010 1 r1 5 best practices

CIP 010-1 R1.5 – Best Practices

  • Use checklist or other task managing tool to reduce likelihood of not testing all controls

  • Document specific test procedures for all cyber assets or group of assets?

    • Describe the test procedures

  • Describe the test environment and how It reflects the production environment


Cip 010 1 r2

CIP 010-1 R2


Pop quiz6

POP Quiz!!

  • When was the atomic bomb first invented?


Pop quiz7

POP Quiz!!

  • When was the atomic bomb first invented?

July 1945


Cip 010 1 r2 1

CIP 010-1 R2.1

  • Must actively search for unauthorized changes to baseline

    • Automated preferred but can be manual

  • Must document and investigate unauthorized changes

CIP 003-3 R6

CIP 010-1 R2.1


Cip 010 1 r2 1 possible pitfall

CIP-010-1 R2.1 – Possible Pitfall

  • Not consistently monitoring for changes every 35 days

    • Entity begins process at end of month

      • Thus entity continuously misses 35 day deadline as it does not have enough time to complete review

    • Documentation is inconsistent and SMEs can’t keep track if specific devices have automated or manual process for tracking configuration changes


Cip 010 1 r2 1 approach

CIP 010-1 R2.1 - Approach

  • logs from a system that is monitoring configurations

  • Work orders, tracking sheets, raw data evidence of manual investigations

  • Records investigating detected unauthorized changes


Cip 010 1 r2 best practice

CIP 010-1 R2 – Best Practice

  • Consider using a commercial or open source File Integrity Monitoring software for continuous monitoring

  • Start monitoring process with enough advance to complete review

    • Consider using an automated task managing tool


Cip 010 1 r2 best practice1

CIP 010-1 R2 – Best Practice

  • What if you find an unauthorized change?

    • What change(s) have been madewithout authorization

    • Who made the change(s)?

    • When were the change(s) made?

    • How can a similar issue be prevented?


Cip 010 1 r1 and r2

CIP 010-1 R1 and R2

QUIZ Time


Cip 010 1 r1 and r21

CIP 010-1 R1 and R2

  • Entities are required to test all changes in a test environment that reflects the production environment.

False


Cip 010 1 r1 and r22

CIP 010-1 R1 and R2

  • Entity baselines are required to include:

    • Operating system/Firmware

    • Commercial/open source software

    • Custom software

    • Logical ports

    • All security patches applied

TRUE

But what about devices where some of these don’t apply?


Cip 010 1 r3

CIP 010-1 R3


Cip 010 1 r3 1

CIP 010-1 R3.1

  • No more annual requirement, and CVA can be active or paper

CIP 005-3 R4

CIP 010-1 R3.1

CIP 007-3 R8


Cip 010 1 r3 1 possible pitfall

CIP-010-1 R3.1 – Possible Pitfall

  • Entity conducts initial Vulnerability Assessment in January then not again until April the next year (16 months)

  • Remember the CIP 003 pitfalls


Cip 010 1 r3 1 approach

CIP-010-1 R3.1 – Approach

  • Verify when last CVA was conducted

  • Verify current CVA was conducted within 15 calendar months of previous CVA

  • Evidence could include:

    • A document listing the date of the assessment and the output of any tools used to perform the assessment.


Cip 010 1 r3 2 best practices

CIP 010-1 R3.2 – Best Practices

  • Vulnerability assessment should include at minimum:

    • Network and access point discovery

    • Port and service Identification

    • Review of default accounts, passwords, and network management community strings

    • Wireless access point review


Cip 010 1 r3 1 best practice

CIP-010-1 R3.1 – Best Practice

  • Consider keeping Vulnerability Assessments for devices or groups of devices on the same cycle

  • Implement a task managing tool to help track needed tasks and deadlines

  • Review NIST SP800‐115 for guidance on conducting a vulnerability assessment


Pop quiz8

POP Quiz!!

  • What was the first home video game console?

    • Atari 2600

    • Magnavox Odyssey

    • VES

    • RCA Studio II


Pop quiz9

POP Quiz!!

  • What was the first home video game console?

  • Developed in 1972

Magnavox Odyssey


Cip 010 1 r3 2

CIP 010-1 R3.2

CIP 005-3 R4

CIP 010-1 R3.2

CIP 007-3 R8


Cip 010 1 r3 2 cont

CIP 010-1 R3.2 cont..

  • Only applicable to High Impact BES systems

  • Required to be performed at least every 36 months

  • CVA must be active and can be performed in production or test environment

    • Test environment must reflect production

    • Document differences between test and production environment

    • Take and document measures to address the differences between test and production environment


Cip 010 1 r3 2 possible pitfall

CIP 010-1 R3.2 – Possible Pitfall

  • Entity does not conduct active Vulnerability Assessments at least every 36 months

  • Entity does manual review on devices that are technically feasible to have active review


Cip 010 1 r3 2 approach

CIP 010-1 R3.2 – Approach

  • Verify active Vulnerability Assessments conducted at least every 36 months

  • Description of test environment and how differences were account for (if test environment used for assessment)

  • Raw data outputs of assessment for applicable devices


Cip 010 1 r3 2 best practices1

CIP 010-1 R3.2 – Best Practices

  • Vulnerability assessment should include at minimum:

    • Network and access point discovery

    • Port and service Identification

    • Review of default accounts, passwords, and network management community strings

    • Wireless access point review


Cip 010 1 r3 2 best practice

CIP 010-1 R3.2 – Best Practice

  • Where possible conduct the Vulnerability Assessment on the production environment

  • Implement a task managing tool to help track needed tasks and deadlines

  • Document SMEs responsible for conducting the Vulnerability Assessment and for what cyber assets


Cip 010 1 r3 3

CIP 010-1 R3.3

  • New devices need an active Vulnerability Assessment prior to deployment

CIP 010-1 R3.3

CIP 007-3 R1


Cip 010 1 r3 3 possible pitfall

CIP-010-1 R3.3 – Possible Pitfall

  • Entity adds new asset to production without first conducting active Vulnerability Assessment


Cip 010 1 r3 3 approach

CIP 010-1 R3.3 – Approach

  • Ensure all newly added assets have had active vulnerability scan conducted prior to device being added to production

  • Verify all necessary controls were verified as part of assessment

  • Verify raw data output of vulnerability assessment can be provided


Cip 010 1 r3 3 best practice

CIP 010-1 R3.3 – Best Practice

  • Document specific procedures that include:

    • Responsible personnel for conducting the test

    • When testing needs to occur

    • Where testing should occur

    • How the testing should be conducted for each cyber asset or group of cyber assets

  • Use a checklist and/or peer reviews to reduce chance of human error


Cip 010 1 r3 4

CIP 010-1 R3.4

  • Document planned completion date for each remediation action

CIP 005-3 R4

CIP 010-1 R3.4

CIP 007-3 R8


Cip 010 1 r3 4 possible pitfall

CIP-010-1 R3.4 – Possible Pitfall

  • Entity is not actively maintaining an action plan to remediate vulnerabilities found in the CVA.

    • Entity is not documenting or updating planned date of completion for remediation actions


Cip 010 1 r3 4 approach

CIP-010-1 R3.4 – Approach

  • Document results or the review or assessment

  • List of action items to remediate issues

  • Status of the action items

    • Documented proposed dates of completion for the action plan


Cip 010 1 r3 4 best practice

CIP-010-1 R3.4 – Best Practice

  • Tie actions outlined in the plan to specific SMEs

    • Use an automated task managing tool to track all required tasks and ensure they are being completed

    • Have steps to ensure action plan is updated and reflects actual proposed completion date of actions


Cip 010 1 r31

CIP 010-1 R3

QUIZ Time


Cip 010 1 r32

CIP 010-1 R3

  • Entities are required to test all changes in a test environment that reflects the production environment.

False

Active CVA not required for Medium impact facilities or for like devices with similar baseline configurations


Cip 010 1 r33

CIP 010-1 R3

  • Entity’s will be required to meet expected completion date of action plans to remediate issues found during Vulnerability Assessment

However, entity can update the expected date if more time is needed.

If the update is reasonable, justified, and done prior to the due date

TRUE


Additional resources

Additional Resources

  • CIP-010-1

  • NERC version 4 to version 5 mapping

  • Glossary of Terms Used in NERC Reliability Standards

  • NIST SP800‐115 – Security testing


Summary

Summary

  • Know what is required for each BES cyber system(s)

  • Create and Maintain device baselines

  • Track and manage deadlines

  • Review referenced NIST documents for added guidance


Ben christensen senior cip enforcement analyst1

Ben ChristensenSenior CIP Enforcement Analyst

CIP-011-1

May 15, 2014

SLC, UT


Agenda1

Agenda

  • Help entities understand and prepare for the upcoming CIP 011-1 standard

    • Differences and relations to current requirements

    • Possible pitfalls to look for while implementing CIP 011-1

    • Implementation tips


Cip 011 1 general pitfalls

CIP 011-1 General Pitfalls

  • Identify, Assess, and Correct (IAC)

    • FERC has conditionally approved CIP 011-1 on the basis that NERC’s Standard Drafting Team make clarifications or remove the IAC language

  • BES Cyber System

    • Pay special attention to the applicable BES cyber systems in each requirement


Purpose

Purpose

  • Prevent unauthorized access to BES Cyber System Information


Bes cyber system i nformation

BES Cyber System Information

  • Information about the BES Cyber System that could be used to gain unauthorized access or pose a security threat to the BES Cyber System – NERC glossary


Bes cyber system i nformation1

BES Cyber System Information

  • Includes:

    • Security procedures/information

      • BES Cyber Systems

      • PACS

      • EACMS

    • List of devices with IP addresses

    • Network diagrams


Bes cyber system i nformation2

BES Cyber System Information

  • Does NOT include:

    • Individual pieces of information that by themselves do not pose a threat or could not be used to allow unauthorized access

      • Devices names

      • Individual IP addresses

      • ESP names

      • Policy statements


Cip 011 1 similarities with v 3

CIP 011-1 Similarities with V.3

  • CIP 003-3 R4: Information Protection

  • CIP 007-3 R7: Disposal or Redeployment


Cip 011 1 similarities to v 3

CIP 011-1 similarities to V.3

CIP 011-1 R1.1

CIP 003-3 R4

CIP 011-1 R1.2

CIP 007-3 R7

CIP 011-1 R2.1

CIP 011-1 R2.2


Cip 011 1 r1 intro

CIP 011-1 R1 - Intro


Cip 011 1 r1

CIP 011-1 R1

CIP 011-1 R1.1

CIP 003-3 R4

CIP 011-1 R1.2


Cip 011 1 r1 1 language

CIP-011-1 R1.1 Language

  • No longer a requirement to classify BES cyber system information

CIP 011-1 R1.1

CIP 003-3 R4


Cip 011 1 r1 2

CIP 011-1 R1.2

  • Procedures for protecting information must now address storage, transit, and use

CIP 011-1 R1.1

CIP 003-3 R4


Cip 011 1 r1 1 evidence

CIP 011-1 R1.1 - Evidence

  • Documented BES Cyber System Information method

  • How you identify BES Cyber System Information (labels, classification)?

  • Repository or electronic and physical locations to house BES Cyber System Information


Cip 011 1 r1 2 evidence

CIP 011-1 R1.2 - Evidence

  • Procedure for protecting BES Cyber System

    • Storage

    • Transit

    • Use

  • Records information was handled per your procedures

    • Change control ticket


Cip 011 1 r1 possible pitfall

CIP 011-1 R1 Possible Pitfall

  • Information Protection plan does not address storage, transit, and use of BES Cyber System Information


Cip 011 1 r1 implementation tips

CIP 011-1 R1 - Implementation tips

  • Consider different variables when determining how to properly protect information during transit, storage, and use

    • Digital information stored locally

    • Physical information stored in a PSP or not

    • Information being held by vendors or accessed by vendors


Cip 011 1 r11

CIP 011-1 R1

QUIZ


Cip 011 1 r12

CIP 011-1 R1

Which of the following would be considered BES Cyber System Information?

  • Device host name

  • ESP diagram

  • PSP name

  • Inventory list with network addresses


Cip 011 1 r13

CIP 011-1 R1

Which of the following would be considered BES Cyber System Information?

  • Device host name

  • ESP diagram

  • PSP name

  • Inventory list with network addresses


Cip 011 1 r2

CIP 011-1 R2


Cip 011 1 r2 1

CIP 011-1 R2.1

  • Focus is now on preventing unauthorized retrieval instead of data destruction

CIP 011-1 R2.1

CIP 007-3 R7


Cip 011 1 r2 2

CIP 011-1 R2.2

  • Focus is now on preventing unauthorized retrieval instead of data destruction

CIP 011-1 R2.2

CIP 007-3 R7


Cip 011 1 r2 1 evidence

CIP 011-1 R2.1 – Evidence

  • Records of sanitization actions

    • Clearing

    • Purging

    • Destroying

  • Records tracking

    • Encryption

    • Held in PSP


Cip 011 1 r2 2 evidence

CIP 011-1 R2.2 – Evidence

  • Records showing media was destroyed prior to disposal

  • Other records of actions taken to prevent unauthorized retrieval of BES Cyber System Information


Cip 011 1 r2 possible pitfall

CIP 011-1 R2 – Possible Pitfall

  • Entity secures cyber assets no longer used that contain BES cyber system information in a location that is not restricted to only those individuals with access to the BES cyber system information


Cip 011 1 r2 implementation tips

CIP 011-1 R2 – Implementation tips

  • Review NIST SP800-88 for guidance on developing media sanitation processes

  • Where possible erase, destroy, degauss, or encrypt data as soon as possible after a device is no longer needed to reduce mishandling of devices or BES cyber system information


Cip 011 1 scenario 1

CIP 011-1 – Scenario 1

  • What if I have a 3rd party host my email?

  • Do I need to protect this information under CIP-011-1?


Cip 011 1 scenario 2

CIP 011-1 – Scenario 2

  • I have hard copies of my network diagrams located in a secure facility. Do I need to include these in my CIP-011-1 program?


Purpose1

Purpose

  • Prevent unauthorized access to BES Cyber System information


Cip 011 1 scenario 11

CIP 011-1 – Scenario 1

  • What if I have a 3rd party host my email?

  • Do I need to protect this information under CIP-011-1?

    It Depends


Cip 011 1 scenario 12

CIP 011-1 – Scenario 1

  • What type of information is stored on the exchange server?

    • BES Cyber System Information

  • How do your procedures account for emails containing this information?


Cip 011 1 scenario 21

CIP 011-1 – Scenario 2

  • I have hard copies of my network diagrams located in a secure facility. Do I need to include these in my CIP-011-1 program?

    YES


Cip 011 1 scenario 22

CIP 011-1 – Scenario 2

  • What type of information is on the diagrams?

    • BES Cyber System Information

    • List of all IP addresses

    • List of all network access points

  • What do your procedures state about securing hard copies?

  • What facilities might contain this information?


Additional resources1

Additional Resources

  • CIP-011-1

  • NERC version 4 to version 5 mapping

  • Glossary of Terms Used in NERC Reliability Standards

  • NIST SP800-88 – Disposal guidance


Summary1

Summary

  • Purpose

  • Differences

  • Pitfalls

  • Implementation tips


Ben christensen senior cip enforcement analyst

Questions?

Ben Christensen

801.819.7666

[email protected]


  • Login