1 / 12

Security Guidelines Working Group Update

Public Release. Security Guidelines Working Group Update. CIPC Meeting Denver CO September 29, 2005 Seiki Harada SGWG Chair. Working Group Name Change. The CIPC meeting of 2005 June precluded ‘standard’ documents from the review responsibility of SGWG.

keene
Download Presentation

Security Guidelines Working Group Update

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Public Release Security Guidelines Working GroupUpdate CIPC Meeting Denver CO September 29, 2005 Seiki Harada SGWG Chair

  2. Working Group Name Change • The CIPC meeting of 2005 June precluded ‘standard’ documents from the review responsibility of SGWG. • Based on this, in May 17, CIPC endorsed dropping ‘S’ from SGWG, and make it GWG. • The working group had a second thought about the abbreviation. We now seek approval to keep the SGWG abbreviation and interpret the first character as “Security”.

  3. SGWG Membership Renewal: • The Issue: • There are 23 names on the current SGWG roster • NERC meeting procedure requires: • a quorum of 2/3 of the registered member • 2/3 majority for a decision making • In any of the SGWG meetings in the past, we were not able to attain the quorum

  4. SGWG Membership Renewal: • The Proposal: • Voting Members: • 6 – 8 members representing Operations, Cyber Security, Physical Security. • Non-voting contributors

  5. CIPC Document Review Process • Discussion Points: • In the June 2005 CIPC meeting, a process flow diagram for SGWG document review was endorsed (see next foil). • CIPC still needed a higher level process of which the SGWG process is a part. We propose such a process for approval.

  6. CIPC Document Review Process

  7. Security Guideline Process Flow Origin- ator CIPC EXEC WG or TF SGWG CIPC EXEC CIPC NERC Board CIPC • Need • Approve • Review • Prioritize • Owner • Sponsor • Resources • Scope • Draft • Content • Expertise • Iterate w/Industry • Format • Consistency • Terminology • Distribute • Train • Cycle • Review • Adopt • Track Guideline Status and Progress • Post for Final Review • Facilitate Vote • Initiate Review on 2 Year Cycle NERC Staff

  8. Updated Guideline DRAFT: Agenda • Discussion and approval of the combined guidelines, “Threat Alert System and Physical Response” Version 2.1 • This guideline is a combination of: • Threat Alert System and Physical Response Guidelines for the Electric Sector Version 2.0 • Threat Response Version 2.0

  9. SGWG Objectives for 2005

  10. Status of Document Reviews • Refer to the Word document: • “Guideline Review Status” • Discussion Points: • Reviewed 10 guidelines in March 2005 • 5 more reviewed by Sep 2005 • All of guidelines over ~ 12 months are reviewed now. • Assignments for drafting new versions and reviews of the new versions to follow.

  11. Succession Plan – SGWG Chair: • Discussion Points: • The incumbent is packing it in, in six months • Preferred transition target: 2006 January • Any volunteers?

More Related