Security Profile for Advanced Metering Infrastructure - Open Smart ...

More documents

Recommendations

Info

Security Domain Description Criteria Examples (AMI) Utility Enterprise Processing and/or Is the asset centrally Meter Data storage of business application data, and located (vs. field deployed and distributed)? (Y) Management System (MDMS), support of utility enterprise applications Does the asset control business operation (i.e., not communications behavior) of assets or provide business processing of data from assets in the Utility Edge domain? (Y) Does the asset interface with utility enterprise applications (or their assets)? (Y) Customer Information System (CIS) Automated Network Collection, transmission, translation, staging, and associated Is the asset centrally located (vs. field deployed and distributed)? (Y) Does the asset provide an AMI Head End, AMI Network Management System transformation of field communications interface for assets in the Utility Enterprise domain to access assets in the Utility Edge or Premise Edge domains? (Y) Does the asset provide a singular logical point of interface to assets in the Utility Enterprise domain for business data from assets in the Utility Edge or Premise Edge domains? (Y) Managed Network Oversight, administration, and Does the asset provide an interface for monitoring or Management Console control of Automated manipulation of functions Services and performed by assets in the Communication Services Communications Relaying, routing, and aggregation of field communications Automated Network or Communications domains? (Y) Is the asset field deployed? (Y) Is the asset part of the communications mechanism connecting centralized utility applications with distributed, field deployed assets? (Y) Field Area Network (FAN), Backhaul Security Profile for Advanced Metering Infrastructure Version 1.0 UtiliSec Working Group (UCAIug) December 10, 2009 21
Security Domain Description Criteria Examples (AMI) Utility Edge Support of field deployed utility Is the asset field deployed? (Y) Metrology, Disconnect Switch equipment and devices (i.e., Is the asset owned and operated by the utility? (Y) Premise Edge monitoring, measurement, and/or control) Support of customer equipment and Does the asset perform a function critical or essential to the operations or business of the utility? (Y) Is the asset field deployed? (Y) Home Area Network (HAN) Interface devices (i.e., Does the asset provide an provisioning, monitoring, measurement, and/or control) interface for the customer (or their assets)? (Y) Table 3: AMI Security Service Domain Characteristics It is important to note that the AMI Security Service Domains form logical points of demarcation with regards to the system. Many commonly found devices and applications in AMI systems (and sometimes components whose functions they implement) actually span two or more domains. Where this occurred, we decomposed the component further into discrete sub-components until each sub-component could fit into one and only one domain. Recommended controls may be associated with logical components or subcomponents. Further work will drive recommendations in some areas to increased levels of detail and prescription and may refine allocation of controls from components to subcomponents. One particular example of interest is the AMI Meter, which as a whole would span the Communications, Utility Edge, and Premise Edge domains. We therefore decomposed this component into the metrology and disconnect switch (if present) in the Utility Edge domain, the Field Area Network interface in the Communications domain, and the Home Area Network interface in the Premise Edge domain. Each of these sub-components and therefore any product implementing their function shall satisfy all security requirements identified in Section 4.3 that apply to that sub-component. The end result is that an AMI Meter inherits security requirements derived from the characteristics and constraints of the Communications, Utility Edge, and Premise Edge domains. 4.4.3 Domain Analysis – Significance, Relevance, and Influence The AMI Security Service Domain proved to be a strong tool for driving convergence of understanding regarding security constraints and expectations of the logical components identified. By examining these components in light of multiple security characteristics simultaneously (as guided by the AMI Security Service Domains), we were able to better understand their relevant attributes and motivate selection of controls. Controls in this document were selected and/or modified to address mission-level needs identified in the referenced AMI system use cases. The resulting controls found Security Profile for Advanced Metering Infrastructure Version 1.0 UtiliSec Working Group (UCAIug) December 10, 2009 22
Page 1 and 2: S E CUR ITY PR OFILE FOR ADVANCED M
Page 3 and 4: Executive Summary The Advanced Mete
Page 5 and 6: DHS-2.8.15 Public Key Infrastructur
Page 7 and 8: Table of Figures Figure 1: A UML ac
Page 9 and 10: 2 Authors Felix Bachman, Software E
Page 11 and 12: 3.1 Purpose The purpose of this doc
Page 13 and 14: 4 Domain Analysis Security requirem
Page 15 and 16: Figure 1: A UML activity diagram fo
Page 17 and 18: This view was extracted from the us
Page 19 and 20: Line # Direction Summary of communi
Page 21 and 22: Line # Direction Summary of communi
Page 23 and 24: 4.3.1 AMI Communications Network De
Page 25 and 26: 4.4 AMI Security Service Domains We
Page 27: • Who owns it? • Who is respons
Page 31 and 32: 5 Recommended Controls The followin
Page 33 and 34: DHS-2.8.3.2 Supplemental Guidance:
Page 35 and 36: DHS-2.8.5.4 Rationale: A denial of
Page 37 and 38: meters and the use of wireless tech
Page 39 and 40: DHS-2.8.10 Trusted Path DHS-2.8.10.
Page 41 and 42: DHS-2.8.13 Collaborative Computing
Page 43 and 44: DHS-2.8.16.3 Requirement Enhancemen
Page 45 and 46: DHS-2.8.20.4 Rationale: Message aut
Page 49 and 50: DHS-2.9.2 Information and Document
Page 51 and 52: protect the exchange of information
Page 53 and 54: DHS-2.9.8.2 Supplemental Guidance:
Page 55 and 56: DHS-2.10.2 Legacy System Upgrades D
Page 57 and 58: • A list of equipment removed or
Page 59 and 60: ASAP-2.10.7.4 Rationale: Many field
Page 61 and 62: mistakes, embody a certain level of
Page 63 and 64: DHS-2.12.5.3 Rationale: The best la
Page 65 and 66: The organization shall identify AMI
Page 67 and 68: outgoing network traffic, including
Page 69 and 70: 2. Logs generated by AMI system com
Page 71 and 72: DHS-2.14.7 Software and Information
Page 75 and 76: DHS-2.14.12 Information Output Hand
Page 77 and 78: 1. A formal, documented, identifica
Page 79 and 80:
DHS-2.15.4 Identifier Management DH
Page 81 and 82:
DHS-2.15.5.4 Rationale: These guide
Page 83 and 84:
DHS-2.15.7.4 Rationale: Access cont
Page 85 and 86:
DHS-2.15.11 Permitted Actions witho
Page 87 and 88:
safety, and security shall provide
Page 89 and 90:
6. The authority to keep and change
Page 91 and 92:
DHS-2.15.20 Unsuccessful Login Atte
Page 93 and 94:
access based upon source of request
Page 95 and 96:
DHS-2.15.27 Untrusted IT Equipment
Page 97 and 98:
information systems and information
Page 99 and 100:
6. Creation, deletion, or modificat
Page 101 and 102:
DHS-2.16.4.3 Requirement Enhancemen
Page 103 and 104:
clocks need to be regularly synchro
Page 105 and 106:
impacting an AMI system can pose si
Page 107 and 108:
Appendix A Mapping of Controls to C
Page 109 and 110:
2.4 Physical and Environmental Secu
Page 111 and 112:
2.6 Configuration Management 2.5.2
Page 113 and 114:
2.8 System and Communication Protec
Page 115 and 116:
2.9 Information and Document Manage
Page 117 and 118:
2.11 Security Awareness and Trainin
Page 119 and 120:
Applies to all components 2.12.8 In
Page 121 and 122:
2.15 Access Control Applies to all
Page 123 and 124:
Applies to all components 2.15.17 S
Page 125 and 126:
Applies to all components 2.16.10 A
Page 127 and 128:
Each communication is mapped to the
Page 129 and 130:
Information in Transit Link (Destin
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149:
Security Profile for Advanced Meter
show all

Security Profile for Advanced Metering Infrastructure - Open Smart ...

Create successful ePaper yourself

Delete template?

Save as template?