OASIS Energy Interoperation TCIcon indicating the project type

OASIS Energy Interoperation TC

Uploaded image for project: 'OASIS Energy Interoperation TC'
  1. OASIS Energy Interoperation TC
  2. ENERGYINTEROP-287

644: ISO's need to comply with NERC CIP, which should be clear in the example

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: csd01 - Public Review Draft
    • Fix Version/s: wd19
    • Component/s: spec
    • Labels:
      None
    • Proposal:
      Hide

      Define an attribute (cardinality [0..1]). The definition will mirror the IRC proposal, i.e., three topcs, and high medium or low for each.

      The CSWG strongly recommends using this as a deployment descriptor, rather than something included in each message. The class model should address how a deployment descriptor is related to a message type or types.

      Show
      Define an attribute (cardinality [0..1] ). The definition will mirror the IRC proposal, i.e., three topcs, and high medium or low for each. The CSWG strongly recommends using this as a deployment descriptor, rather than something included in each message. The class model should address how a deployment descriptor is related to a message type or types.
    • Resolution:
      Hide

      Security risk to add to messages (rather than transport and interaction)

      Close, no change

      Show
      Security risk to add to messages (rather than transport and interaction) Close, no change

      Description

      While line 640 mentiones security, privacy, and reliability the section speaks of security at the communication layer only. ISO's need comply with NERC CIP Information Protection guidelines that should be described in the Information Model (see IRC Information Model and XML Schemas) to classify information, not only protect it.

        Attachments

          Activity

          Ascending order - Click to sort in descending order
          edgardo.luzcando Edgardo Luzcando (Inactive) created issue -
          david.holmberg David Holmberg (Inactive) made changes -
          Field Original Value New Value
          Assignee William Cox [ william.cox ] Toby Considine [ toby.considine ]
          william.cox William Cox (Inactive) made changes -
          Resolution Include an optional attribute (cardinality [0..1]) in each message. The definition will mirror the IRC proposal, i.e., three topcs, and high medium or low for each.
          Status New [ 10000 ] Open [ 1 ]
          william.cox William Cox (Inactive) made changes -
          Fix Version/s wd19 [ 10125 ]
          Resolution Fixed [ 1 ]
          Status Open [ 1 ] Resolved [ 5 ]
          william.cox William Cox (Inactive) made changes -
          Assignee Toby Considine [ toby.considine ] William Cox [ william.cox ]
          Hide
          Permalink
          william.cox William Cox (Inactive) added a comment -

          The information structure correctly describes the information classification for NERC CIP, but including the "value" of the message in the message seems to increase risk by flagging more valuable messages. (From discussion with CSWG members)

          This would be a useful "deployment descriptor", rather than a message component.

          This seems to be relevant information in deciding what security/reliability to compose for specific types of interactions.

          Show
          william.cox William Cox (Inactive) added a comment - The information structure correctly describes the information classification for NERC CIP, but including the "value" of the message in the message seems to increase risk by flagging more valuable messages. (From discussion with CSWG members) This would be a useful "deployment descriptor", rather than a message component. This seems to be relevant information in deciding what security/reliability to compose for specific types of interactions.
          william.cox William Cox (Inactive) made changes -
          Resolution Include an optional attribute (cardinality [0..1]) in each message. The definition will mirror the IRC proposal, i.e., three topcs, and high medium or low for each. Define an attribute (cardinality [0..1]). The definition will mirror the IRC proposal, i.e., three topcs, and high medium or low for each.

          The CSWG strongly recommends using this as a deployment descriptor, rather than something included in each message. The class model should address how a deployment descriptor is related to a message type or types.
          toby.considine Toby Considine (Inactive) made changes -
          Proposal Define an attribute (cardinality [0..1]). The definition will mirror the IRC proposal, i.e., three topcs, and high medium or low for each.

          The CSWG strongly recommends using this as a deployment descriptor, rather than something included in each message. The class model should address how a deployment descriptor is related to a message type or types.
          Resolution Define an attribute (cardinality [0..1]). The definition will mirror the IRC proposal, i.e., three topcs, and high medium or low for each.

          The CSWG strongly recommends using this as a deployment descriptor, rather than something included in each message. The class model should address how a deployment descriptor is related to a message type or types.           		Security risk to add to messages (rather than transport and interaction)

          Close, no change
          Issue Type Bug [ 1 ] Improvement [ 4 ]
          Status Resolved [ 5 ] Applied [ 10002 ]
          toby.considine Toby Considine (Inactive) made changes -
          Status Applied [ 10002 ] Closed [ 6 ]

            People

            • Assignee:
              william.cox William Cox (Inactive)
              Reporter:
              edgardo.luzcando Edgardo Luzcando (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: