NISTIR 7628, Smart Grid Cyber Security Strategy and Requirements Draft 2 February 2, 2010 - Comment Resolution Comment

t Number: a Reference: Chapter 2 page 19, Figure 2.1 , Table 2.1 Comment The referenced text, figure and table usage of domains, sub-domains, actors, does not synch exactly with "NIST Smart Grid Framework 1.0 September 2009", "Figure 3. Conceptual Reference Diagram" E.G.: 44 Third Party is indicated as an actor within the Service Providers domain, but is really a sub-domain to Service Provider domain 41 Aggregator / Retail Energy Provider are combined versus being 2 separate actors Third Party Provider CIS actor is missing Human actors are included 23 Customer Information System is denoted being in the Operations domain versus the Service Providers domain 31- ISO/RTO/Wholesale Market is indicated as a new actor Note Even OpenSG SG Communications SG Network Task Force has prepared a conceptual reference diagram of Smart Grid Domains, Sub-Domains, Actors, and interfaces that differs from the both "NIST Smart Grid Framework 1.0 September 2009", "Figure 3. Conceptual Reference Diagram and NISTIR 7628 2nd draft Figure 2.1 which adds in new actors and interfaces to address its deliverables to the OpenSG members and PAPs 1 & 2 work efforts Rationale/Recommendation Recommendation is to harmonize the conceptual reference set of: domains, sub-domains and usage, actors, and interfaces between at least the following work efforts: NIST Smart Grid Framework, NISTIR 7628, OpenSG SG Communications SG Network Task Force. Each effort can use subsets of the harmonized conceptual framework domains, sub-domains, actors and interfaces, with the same definitions, context, naming being consistent across each organizations usages. Rationale This would remove confusion when one attempts to reconcile what one organizations deliverables are referring to and attempting to describe as may relate to another organizations use of the reference material. This would require changes in each of the work efforts deliverables released to-date and some near term maintenance until the vast major of the standards and architecting work around Smart Grid is accomplished. Submitted by: OpenSG SG Communications SG Network Task Force, Matt Gillmore Comment Type: _X_ Tech. __ Editorial _X_ Gen.

Comment Number: a

Submitted by: OpenSG SG Communications SG Network Task Force, Matt Gillmore

Comment Type: _X_ Tech. __ Editorial _X_ Gen.

Disposition (for SGIP-CSWG use)

Comment Number: b Reference: Chapter 2 page 28 Comment

Submitted by: OpenSG SG Communications SG Network Task Force, Matt Gillmore

Comment Type: __ Tech. _X_ Editorial __ Gen.

The last 2sentences prior to section 2.2 states Following each diagram is a table that allocates the logical interfaces to one of the logical interface categories. These logical interface categories are discussed fully in Chapter Three Rationale/Recommendation Recommendation Replace the last sentence with a paragraph that introduces the reader to the purpose and role of logical interface category and still direct the reader to section 3.2 for more details. Rationale There are too many pages to scan through before getting to what the intend and proposed use of the logical interface category and its relationship to the diagram logical interfaces. Disposition (for SGIP-CSWG use)

Comment Number: c Reference: Table 2.2 2.7 Comment

Submitted by: OpenSG SG Communications SG Network Task Force, Matt Gillmore

Comment Type: _X_ Tech. _X_ Editorial __ Gen.

How is the reader of this table to identify which single or combination of "logical interface categories" (LIC) apply to a specific end-to-end actor pair e.g. Customer Information System and Meter e.g. is it (10a, or 10b) and 3a or just (10a or 10b)? Is there to be only 1 LIC that applies to a specific end-to-end actor pair There also appears to be some missing logical interfaces listed for a specific LIC e.g. U24 needs to be added to the 10a and 10b LICs Rationale/Recommendation Recommendation add clarifying language in the recommended paragraph to be added prior to section 2.1 (see comment above). Also validate that all the appropriate pre table 2.2-2.7 have the complete set of logical interfaces listed appropriate to the stated "logical interface category". Rationale Clarifies to the reader how to interpret and use "logical interface categories" and the associated logical interfaces

Comment Number: c

Submitted by: OpenSG SG Communications SG Network Task Force, Matt Gillmore

Comment Type: _X_ Tech. _X_ Editorial __ Gen.

Disposition (for SGIP-CSWG use)

Comment Number: d Reference: Table 3.3 page 78 Comment

Submitted by: OpenSG SG Communications SG Network Task Force, Matt Gillmore

Comment Type: _X_ Tech. __ Editorial __ Gen.

The "Confidentiality", "Integrity", "Availability" (C/I/A) values included in this table appear to indicate that all messages (payloads) that originate and are consumed by the two end point actors for a given logical interface category regardless of the type and content of those message / payloads. OpenSG SG Communications SG Network Task Force current work to provide Smart Grid use case business functional and volumetric requirements to NIST PAP 1 and PAP 2 work efforts, is documenting those requirements to the per payload per actor to actor pairings. That effort also is assigning C/I/A values specific to the payload content and source and consuming actors, much like the LIC rows in Tables 2.2 2.7. The documented requirements to-date is contained in the requirements table (URL http://osgug.ucaiug.org/UtiliComm/Shared %20Documents/Interium_Release_3/SG-Net_TF_%20funct-volumteric-reqs_v3.xls). Using the Customer Information System to/from Meter pair example, 11 different payloads have been documented to-date. The list below identifies those payloads and their associated C/I/A values as extracted (using parent row from and to actor filters ), from the release 3.0 requirements table, which are still under review and change. on-demand_Mtr-read_cmd L M L SW_opr_cancel_cmd M H M SW_opr_cmd M H M SW_state_cmd L L L prepay_meter_config_cmd L H L on-demand_Mtr-read_cmd_err L L L on-demand_Mtr-read_resp-data L M L SW_state_cmd_resp-data L L L SW_opr_cmd_ack L L L SW_opr_fail_cmd-err L M L SW_post-oper-info_resp-data L L L

Rationale/Recommendation Recommendation Change the Table 3.3 and associated text to recognize that by decomposing the high level logical interface categories into the specific messages and payloads, that a different view of the C/I/A values emerges

Comment Number: d

Submitted by: OpenSG SG Communications SG Network Task Force, Matt Gillmore

Comment Type: _X_ Tech. __ Editorial __ Gen.

and needs to be considered in designing and architecting Smart Grid deployments. Rationale Clarifies that when looking at the payload level of detail, a 1 size fits all of "Confidentiality", "Integrity", "Availability" (C/I/A) values for a logical interface category, does not apply at least from a business requirements perspective. Disposition (for SGIP-CSWG use)

Comment Number: e Reference: Comment

Submitted by:

Comment Type: __ Tech. __ Editorial __ Gen.

Rationale/Recommendation Disposition (for SGIP-CSWG use)

Comment Number: f Reference: Comment

Submitted by:

Comment Type: __ Tech. __ Editorial __ Gen.

Rationale/Recommendation Disposition (for SGIP-CSWG use)