Security Guidelines Working Group Update CIPC Meeting Phoenix, AZ Mar 16, 2006 Seiki Harada SGWG Chair CIPC Confidentiality: Public Release.

Slides:



Advertisements
Similar presentations
Reliability Center Data Request Task Force Report WECC Board Meeting April 2009.
Advertisements

NERC Critical Infrastructure Protection Advisory Group (CIP AG) Electric Industry Initiatives Reducing Vulnerability To Terrorism.
SERVICE MANAGER 9.2 PROBLEM MANAGEMENT TRAINING JUNE 2011.
0 Chicago, IL March 6 th, 2007 Use Case Requirements, Design and Standards Selection HITSP Use Case Requirements, Design and Standards Selection Date:
Cyber Security Plan Implementation Presentation to CMBG Glen Frix, Duke Energy June 20,
Runway Safety Teams (RSTs) Description and Processes Session 5 Presentation 1.
Audit Committees in Local Government FinPro Professional Development Seminar Linda MacRae Local Solutions Pty Ltd 25 October
The R&M Task Group mandate is to: Develop specific recommendations on how social housing project reporting and monitoring could be improved and made more.
XBRL Voluntary Program on the EDGAR System April 2005 Brigitte Lippmann Attorney Division of Corporation Finance Jeffrey Naumann Enabling Technologies.
NESCC Meeting March 28, Topics Accomplishments Since Last Meeting Program Management for NESCC Support to the NESCC Sponsor Committee Review and.
K E M A, I N C. NERC Cyber Security Standards and August 14 th Blackout Implications OSI PI User Group April 20, 2004 Joe Weiss
CIPC Executive Comittee Update CIPC Conference Call September 16, 2004 Stuart Brindley CIPC Chair CIPC Confidentiality - Public.
Lisa Wood, CISA, CBRM, CBRA Compliance Auditor, Cyber Security
Nuclear Power Plant/Electric Grid Regulatory Coordination and Cooperation - ERO Perspective David R. Nevius and Michael J. Assante 2009 NRC Regulatory.
CRITICAL INFRASTRUCTURE PROTECTION COMMITTEE. 2 Group carried over from ECAR, MAAC, & MAIN workgroups that were assembled to address 1200 Urgent Action.
INFORMATION ASSURANCE USING C OBI T MEYCOR C OBI T CSA & MEYCOR C OBI T AG TOOLS.
CIPC Executive Committee Update CIPC Meeting Denver CO September 29, 2005 Stuart Brindley CIPC Chair Public Release.
Important acronyms AO = authorizing official ISO = information system owner CA = certification agent.
1 Crisis Response Task Force (CRTF) Proposal Tom Bowe (Chairman) CSO, PJM Interconnection Scott Heffentrager (Temp. Chairman) Physical Security.
IEEE COMMITTEE TO RESOLVE MEMBERS' CONCERNS FINAL REPORT IEEE Central Texas Section Spring Section Meeting January 25, 2014 San Marcos, TX.
Web Security for Network and System Administrators1 Chapter 2 Security Processes.
ISA–The Instrumentation, Systems, and Automation Society ISA SP-99 Introduction: Manufacturing and Control Systems Security -- Kickoff Meeting Call to.
Role for Electric Sector in Critical Infrastructure Protection R&D Presented to NERC CIPC Washington D.C. June 9, 2005 Bill Muston Public Release.
SPS policy – Information Presentation Presentation to ROS June 16, 2004.
Motorola GSD Self-Audits How does it work / what do we do? –1.) What is an audit? –2.) What is the procedure? –3.) What are the “judgement parameters”
Board of Directors Meeting September 2010 Enforcement Process Update Robert K. Wargo Manager of Enforcement.
CIPC Executive Committee Update CIPC Meeting Mesa AZ March 16, 2006 Barry Lawson CIPC Vice-Chair CIPC Confidentiality: Public Release.
Performance Measure Recommendations Greg Pierce – Chair, Performance Measures Task Force Compliance and Certification Committee Meeting September 8-9,
Paragraph 81 Project. 2RELIABILITY | ACCOUNTABILITY Background FERC March 15, 2012 Order regarding the Find, Fix, Track and Report (FFT) process  Paragraph.
UPDATING RIGHT OF WAY MANUALS FLORIDA’S PROCEDURES.
IEEE P1603 reviewer’s guideline Wolfgang Roethig, WG chair.
Page 1 of 13 Texas Regional Entity ROS Presentation April 16, 2009 T EXAS RE ROS P RESENTATION A PRIL 2009.
Standards and Guidelines Working Group Status Updates 2005 Jun 09 Washington DC Critical Infrastructure Protection Committee Public Release.
CIPC Executive Committee Update-1 CIPC Meeting Long Beach CA March 17, 2005 Pat Laird Vice Chair Public Release.
Report of the Technical Subcommittee Mario Bergeron, Technical Subcommittee Chair/NGEC Vice Chair.
Security Guidelines Working Group Update CIPC Meeting Denver CO September 29, 2005 Seiki Harada SGWG Chair Public Release.
Doc.: IEEE /0010r0 Submission March 2006 Steve Shellhammer, QualcommSlide 1 Overview of the TAG Notice: This document has been prepared.
Important acronyms AO = authorizing official ISO = information system owner CA = certification agent.
1 Presented by David Thompson, TIA December 14, 2005 NFPA 1600 and Emergency Communications.
Department of Higher Education and Training
Law Firm Data Security: What In-house Counsel Need to Know
COMPREHENSIVE PLAN 2017 AMENDMENT PROCESS and DOCKET
Parliament and the National Budget Process
COMPREHENSIVE PLAN 2017 AMENDMENT PROCESS and DOCKET
CIPC Outreach WG Update March 2006
CIPC Relationships & Roles
Role for Electric Sector in Critical Infrastructure Protection R&D
NERC Critical Infrastructure Protection Advisory Group (CIP AG)
CIPC Executive Committee Update-1
Security Guidelines Working Group Update
CIPC Executive Committee Update
NERC Critical Infrastructure Protection Committee (CIPC) Executive Committee Public Release 29 September 2005.
TGu Requirements Change Motion
Critical Infrastructure Protection Committee
MODULE B - PROCESS SUBMODULES B1. Organizational Structure
Group Meeting Ming Hong Tsai Date :
CIPC Executive Committee Update
UPDATE: Physical Security Guideline
Crisis Response Task Force (CRTF) Proposal
Performance Measure Recommendations
<month year> doc.: IEEE <030158r0> January 2004
Security Guidelines Working Group Update
CIPC Executive Committee Report-2
Report of the Technical Subcommittee
MAC Input on Section 4.9 Review
WG Technical Editor’s Report
Proposed Changes for LB81 Comments
Selection Procedure Recommendation
Standards Review Subcommittee Update
Presentation transcript:

Security Guidelines Working Group Update CIPC Meeting Phoenix, AZ Mar 16, 2006 Seiki Harada SGWG Chair CIPC Confidentiality: Public Release

SGWG Foil 2 Discussion Items 1.SGWG Roster 2.Change to the Guideline Preamble Prioritization of the Guideline Updates 4.Regular Review Cycle for All Security Guidelines 5.Content Review of Guidelines by SGWG 6.Guideline Directions

SGWG Foil 3

SGWG Foil 4 SGWG Roster: As of March 10, 2006, the SGWG comprises: 1.Scott McCoy (Physical) 2.Scott Webber (Physical) 3.Bruce Metruck (Physical) 4.Mike Paszynsky (Physical) 5.Larry Bugh (Cyber) 6.Joe Doetzl (Cyber) 7.David Baumken (Cyber) 8.Roger Lampila (Operations) 9.Tom Kropp (Research Institutions) 10.Ken Hall (Research Institutions)

SGWG Foil 5 Changes to the Preamble A suggestion was made by a NERC legal staff to adopt the following: “ This document addresses potential risks that can apply to some electricity sector organizations and provides practices that can help mitigate the risks. Each organization decides for itself the risks it can accept and the practices it deems appropriate to manage its risks. “

SGWG Foil 6 Prioritization of Guideline Updates: 1.Of the 18 Security Guidelines, 14 were assessed as needing updates. 2.The remainder, 4, are recent ones and deemed acceptable. 3.It is not reasonable to expect various working groups to re-draft all 14 of them and put through CIPC approvals in one year (9 months now!). 4.SGWG recommends 7 updates this year and 7 next year (refer to the SGWG Reference Document No.1)

SGWG Foil 7 Criteria for Prioritization: 1.Synchronization with, or in support of, the permanent cyber security guidelines 2.Importance/relevance of the subject matter today 3.How 'off' or 'dated' the content is 4.Subsumed by any new guidelines ( e.g., elimination candidates)?

SGWG Foil 8 Prioritization of Guideline Updates: Recommended Updates for 2006: SG001Vulnerability and Risk Assessment SG002Emergency Plans SG003Continuity of Business Processes SG005Physical Security SG006Cyber Security – Risk Management SG007Cyber Security – Access Controls SG018Threat Alert System and Cyber Response

SGWG Foil 9 Prioritization of Guideline Updates: Recommended Updates for 2007: SG004Communications SG008Cyber Security – IT Firewalls SG009Cyber Security – Intrusion Detection SG010Employment Background Screening SG011Protecting Potentially Sensitive Information SG012Securing Remote Access to Electronic CPS SG014Threat and Incident Reporting

SGWG Foil 10 Guideline Updates – Further Recommendations: 1.The CIPC Executive Committee assign an ‘owning’ working group for each security guideline. 2.The ‘owning’ working group will accommodate identified updates in their 2006/2007 work schedule. 3.NERC CIPC support staff will follow up with respective working group re the timing of completion and CIPC reviews

SGWG Foil 11 Regular Guideline Reviews: 1.Today, there is no fixed schedule for reviewing existing guidelines. 2.The Cyber Security Standard (CIP 003) asks for an annual review of policies. 3.SGWG Recommendation: Complete the identified updates for 2006 and 2007 After that, schedule reviews of the guidelines every two years or when there is a watershed event in the subject area. These bi-annual reviews may not necessarily result in updates.

SGWG Foil 12 Content Review of Security Guidelines: Background: 1.Comments were made that SGWG should stay away from reviewing guideline contents. 2.The SGWG Terms of Reference states, in part: “review existing CIPC guidelines, and other electric and non-electric industry reference material, for currency and relevance”.

SGWG Foil 13 Content Review of Security Guidelines: What the SGWG guideline reviews entail today: 1.Consistency and compatibility with security standards and other security guidelines 2.Consistency of parts within a specific guideline 3.Currency and relevance to the current threats/industry practices (e.g., against IEEE, ISO, NIST, ANSI, CSA, etc)

SGWG Foil 14 Content Review of Security Guidelines: Recommendation: 1.SGWG will review ‘content’ only in the sense of the above consistency checks – not in value judgement. 2.SGWG will provide timely comments to the ‘Owning’ working group. 3.The ‘owning’ working group will consider the comments provided. They are not obliged to accommodate all comments.

SGWG Foil 15 Guideline Directions: 1.Most new guidelines come from Working Groups or Task forces/Teams. 2.SGWG may from time identify the area where a new security guideline is appropriate. 3.The CIPC will have the final say in the generation of a new (or the elimination of an existing) security guidelines.

SGWG Foil 16 Thank you! 1.Thank you for working with me for the past two years. It has been a challenge and pleasure at the same time. 2.Please support Scott McCoy in the coming years!