25.12.2012 Views

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

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

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

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

surrounding current AMI components and technology were taken in consideration such as key<br />

management, firmware assurance and protection, and trust between intra- and interorganizational<br />

users and objects.<br />

<strong>Security</strong> controls were selected based on applicability to components and messages of AMI<br />

scenarios that were studied. <strong>Security</strong> service domains were used as a tool to further characterize<br />

these components with respect to additional security considerations. The assigning of<br />

components to AMI security service domains, examination of processes, communication and<br />

security considerations were used in the selection of requirements <strong>for</strong> each component.<br />

3.4 Audience<br />

The primary audience of this document is <strong>for</strong> organizations that are developing or implementing<br />

AMI solutions. This document is written at the normal level of utility security experience <strong>for</strong><br />

system owners, system implementers and security engineers. The user is assumed to be<br />

experienced at in<strong>for</strong>mation asset risk estimation. The user is further assumed to be<br />

knowledgeable in developing security requirements and guidance.<br />

3.5 Disclaimer/Status<br />

Please note that the recommended controls listed in this document are adaptations of the DHS<br />

controls as appropriate <strong>for</strong> AMI security. The DHS control section numbers are only provided<br />

<strong>for</strong> traceability, and not intended to indicate that the controls in this document are the DHS<br />

controls themselves. When the ASAP-SG team created controls <strong>for</strong> which there was no DHS<br />

counterpart, the "ASAP-" prefix is used instead of "DHS-".<br />

<strong>Security</strong> <strong>Profile</strong> <strong>for</strong> <strong>Advanced</strong> <strong>Metering</strong> <strong>Infrastructure</strong> Version 1.0<br />

UtiliSec Working Group (UCAIug) December 10, 2009<br />

5

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!