Presentation is loading. Please wait.

Presentation is loading. Please wait.

UCAIug: AMI Security Update – September 2008  AMI-SEC Task Force  AMI Security Acceleration Project (ASAP) AMI-SEC Task Force Chair: Darren Reece Highfill,

Similar presentations


Presentation on theme: "UCAIug: AMI Security Update – September 2008  AMI-SEC Task Force  AMI Security Acceleration Project (ASAP) AMI-SEC Task Force Chair: Darren Reece Highfill,"— Presentation transcript:

1 UCAIug: AMI Security Update – September 2008  AMI-SEC Task Force  AMI Security Acceleration Project (ASAP) AMI-SEC Task Force Chair: Darren Reece Highfill, CISSP

2 AMI-SEC Task Force AMI-SEC is concerned with securing AMI system elements.AMI-SEC is concerned with securing AMI system elements. –Contextual Definition: “…those measures that protect and defend AMI information and systems by assuring their ability to operate and perform in their intended manner in the face of malicious actions.” PurposePurpose –Produce technical specification Used by utilities to assess and procureUsed by utilities to assess and procure Used by OpenAMI – part of AMI/DR Reference DesignUsed by OpenAMI – part of AMI/DR Reference Design –Determine baseline level of detail Prescriptive in naturePrescriptive in nature Compliant products will have known functionality and robustnessCompliant products will have known functionality and robustness

3 AMI-SEC Task Force Formation: August 23, 2007Formation: August 23, 2007 Q4 2007: Initial exploration, definition of scope, consensus on approachQ4 2007: Initial exploration, definition of scope, consensus on approach January 2008: Identification of 4 DeliverablesJanuary 2008: Identification of 4 Deliverables –Risk Assessment –Architectural Description –Component Catalog –Implementation Guide Current Participation:Current Participation: –127 Subscribers to Listserv –More than a dozen major utilities actively engaged

4

5 AMI-SEC 2008 – Original Plan Risk Assessment / System Requirements Architectural Description Component Catalog Implementation Guide

6 System Requirements Problem: Q AMI-SEC work to generate Risk Assessment was significant taskProblem: Q AMI-SEC work to generate Risk Assessment was significant task –Substantially tapped volunteer resources Risk Assessment very thorough, but only implied requirements (not explicit)Risk Assessment very thorough, but only implied requirements (not explicit) –System Requirements document needed to be separated Utilities expressing need for requirements to use in procurement processUtilities expressing need for requirements to use in procurement process

7 Outrunning the Train Initial Concept: Late January 2008 (hat tip to Consumers Energy)Initial Concept: Late January 2008 (hat tip to Consumers Energy) Challenge: AMI-SEC TF is volunteer-basedChallenge: AMI-SEC TF is volunteer-based –Operates somewhat like a standards body –Heavy deliverable schedule, pressing industry need –Utilities strapped for human resources Solution: Utility-initiated collaborative project with DOE and EPRISolution: Utility-initiated collaborative project with DOE and EPRI –Band together to fund SME’s Make the team directed, agile, and accountableMake the team directed, agile, and accountable Do “AMI-SEC homework” for utilities (off-load utility personnel)Do “AMI-SEC homework” for utilities (off-load utility personnel) –Utilize FFRDC resources (INL, ORNL, SEI) –Perform independent 3rd party testing Collaborative R&D at EnerNex, EPRI Living Laboratory, Utility Laboratories, and Pilot LocationsCollaborative R&D at EnerNex, EPRI Living Laboratory, Utility Laboratories, and Pilot Locations

8 Outcomes: Support utilities procuring and deploying AMIOutcomes: Support utilities procuring and deploying AMI Roadmap Challenges: Lack of security standards, guidance, best practicesRoadmap Challenges: Lack of security standards, guidance, best practices Approach:Approach: –Provide "drop-in" RFP security requirements –Develop test plans and methodologies –Perform vulnerability testing of AMI solutions –Produce recommendations for AMI security architecture Progress/accomplishments: Team built, research underway, documentation emergingProgress/accomplishments: Team built, research underway, documentation emerging AMI Security Acceleration Project (ASAP)  Schedule: Jan08 – Dec08  Level of Effort: High  Performers: EnerNex, Intelguardians, SEI, INL, ORNL  Partners: Utilities, DOE, EPRI Roadmap to Secure Control Systems in the Energy Sector

9 AMI-SEC 2008 – Revised Plan (includes ASAP)

10 Risk Assessment What must be addressed by the system and whyWhat must be addressed by the system and why Provide traceability for eventually selected mitigation methods back to organizational valueProvide traceability for eventually selected mitigation methods back to organizational value Features:Features: –Asset Catalog –Threat Profiles –Vulnerability Analysis –Threat-Vulnerability-Asset Mapping –Scenario Prioritization

11 System Security Requirements Catalog of available requirementsCatalog of available requirements Pulled from wide library of many sourcesPulled from wide library of many sources –Common Criteria –DHS Control Systems Catalog –FIPS –NIST , –NERC CIP –… (more coming) FeaturesFeatures –System Constraints –States and Modes –Security Objectives –Assembled and Categorized Requirements

12 Architectural Description Abstract (logical, platform-agnostic) mitigation plan for addressing requirements identified in the Risk Assessment.Abstract (logical, platform-agnostic) mitigation plan for addressing requirements identified in the Risk Assessment. Features:Features: –Architectural Representation of Security Systems –Logical Function Descriptions –System, Subsystem, and Function Boundaries

13 Component Catalog Commonly found patterns of functions and services performed by individual componentsCommonly found patterns of functions and services performed by individual components Include specific technologies, but will not be competitive in nature – patterns will overlapInclude specific technologies, but will not be competitive in nature – patterns will overlap Note: Any single system implementation will use only a subset of the catalog.Note: Any single system implementation will use only a subset of the catalog. Features:Features: –Design Patterns –Functional Primitives –Technological Applications and Considerations

14 Implementation Guide Guidance to utilities and vendors for selection, assembly, and implementation of components from the Component CatalogGuidance to utilities and vendors for selection, assembly, and implementation of components from the Component Catalog –Integration Patterns –Procedures, Considerations, Guarantees, and Risks for Component Assembly –Performance Parameters and Relative Metrics –Recommendations and Guidance for Technology Selection –Best Practices to Ensure Component Interoperability and System Longevity

15 EnerNex Process management and draft contributions / editing ASAP – Participants Red Team Testing procedures / methodologies and first-level evaluation of landscape Software Engineering Institute (Carnegie Mellon) Process review / support and targeted analytical reports Idaho National Lab Detailed analytical report and recommendations for AMI communications architecture Current Signees:Current Signees: –Consumers Energy, SCE, PG&E, Duke, Oncor, AEP, BC Hydro Two more in-process, two more committedTwo more in-process, two more committed

16 ASAP – Objectives 1.Ease utility HR demands of participating in volunteer task force –Dedicated, accountable resources –Utility personnel needed for requirements gathering 2.Provide “drop-in” set of RFP security requirements –Vendor-oriented summary of requirements 3.Develop test plans and methodologies –Evaluate security functionality 4.Perform vulnerability testing of AMI solutions –Establish 3 rd party collaborative testing –First-cut cross-section 5.Produce recommendations for AMI communications security architecture –Underlying protocols and technologies –Survivability and the Systems Development Life Cycle (SDLC)

17 AMI-SEC / ASAP Roadmap

18 Deliverable Usage

19 Goals & Objectives – Status 1.Ease utility HR demands –Done and continuing: utilities have been able to guide the process through AMI-SEC with occasional and phone calls. 2.Provide RFP material –Almost done: System Security Requirements document at 95% mark. 3.Develop test plans –Underway: Red Team and Idaho National Laboratory have been working on these since early summer. 4.Perform vulnerability testing –Ready to start: Red Team currently awaiting vendor equipment. 5.Produce recommendations for security architecture –Underway: Architectural Description document at 95% mark, INL recommendations in progress.

20 Questions? AMI-SEC Collaboration Site


Download ppt "UCAIug: AMI Security Update – September 2008  AMI-SEC Task Force  AMI Security Acceleration Project (ASAP) AMI-SEC Task Force Chair: Darren Reece Highfill,"

Similar presentations


Ads by Google