1.3 High Impact BES Cyber Systems For a change that deviates from An example of evidence may include, and their associated: the existing baseline but is not limited to, updated baseline EACMS; configuration, update the baseline documentation with a date that is within configuration as necessary within 30 calendar days of the date of the PACS; and 30 calendar days of completing completion of the change. PCA the change. Medium Impact BES Cyber Systems and their associated: EACMS; PACS; and PCA Registered Entity Response (Required): Compliance Narrative: Provide a brief explanation, in your own words, of how you comply with this Requirement. References to supplied evidence, including links to the appropriate page, are recommended. Registered Entity Evidence (Required): The following information is requested for each document submitted as evidence. Also, evidence submitted should be highlighted and bookmarked, as appropriate, to identify the exact location where evidence of compliance may be found. Relevant Revision Page(s) Description of or Document or Applicability of File Name Document Title Version Date Section(s) Document Audit Team Evidence Reviewed (This section to be completed by the Compliance Enforcement Authority): Compliance Assessment Approach Specific to CIP-010-2, R1, Part 1.3 This section to be completed by the Compliance Enforcement Authority For a change that deviates from the existing baseline configuration, verify the Responsible Entity documented one or more processes for updating the baseline configuration as necessary within 30 calendar days of completing the change. For each Applicable System, for a change that deviates from the existing baseline configuration, verify the Responsible Entity updated the baseline configuration as necessary within 30 calendar days of completing the change.
1.3 High Impact BES Cyber Systems and their associated: EACMS; PACS; and PCA Medium Impact BES Cyber Systems and their associated: EACMS; PACS; and PCA For a change that deviates from the existing baseline configuration, update the baseline configuration as necessary within 30 calendar days of completing the change. An example of evidence may include, but is not limited to, updated baseline documentation with a date that is within 30 calendar days of the date of the completion of the change. Registered Entity Response (Required): Compliance Narrative: Provide a brief explanation, in your own words, of how you comply with this Requirement. References to supplied evidence, including links to the appropriate page, are recommended. Registered Entity Evidence (Required): The following information is requested for each document submitted as evidence. Also, evidence submitted should be highlighted and bookmarked, as appropriate, to identify the exact location where evidence of compliance may be found. File Name Document Title Revision or Version Document Date Relevant Page(s) or Section(s) Description of Applicability of Document Audit Team Evidence Reviewed (This section to be completed by the Compliance Enforcement Authority): Compliance Assessment Approach Specific to CIP-010-2, R1, Part 1.3 This section to be completed by the Compliance Enforcement Authority For a change that deviates from the existing baseline configuration, verify the Responsible Entity documented one or more processes for updating the baseline configuration as necessary within 30 calendar days of completing the change. For each Applicable System, for a change that deviates from the existing baseline configuration, verify the Responsible Entity updated the baseline configuration as necessary within 30 calendar days of completing the change.
RSAW%20CIP-010-2_2015_v1.docx