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

XMLWordPrintable

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Critical
    • wd19
    • Affects Version/s: csd01 - Public Review Draft
    • Component/s: spec
    • None
    • 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.
    • 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

      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.

        1.
        		 715: Information classification for NERC CIP is in-scope for the IRC Sub-task Closed Edgardo Luzcando (Inactive)

            Assignee:
            William Cox (Inactive)
            Reporter:
            Edgardo Luzcando (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: