R3 Requirement & Measure Evidence Submission Evidence Description Evidence Assessment Approach Auditor Notes R3. Each Responsible Entity shall implement, in a manner that identifies, assesses, and corrects deficiencies, one or more documented processes that collectively include each of the applicable requirement Parts in CIP‐007-AB‐5 Table R3 Malicious Code Prevention. – M3. Evidence must include each of the documented processes that collectively include each of the applicable requirement Parts in CIP‐007-AB‐5 Table R3 Malicious – Code Prevention and additional evidence to demonstrate implementation as described in the Measures column of the table. Part 3.1 in Verify the Responsible Entity has documented Please AR3 Part 3.1 one or more processes to deploy method(s) to provide: R3 Malicious Code Prevention – detect, or prevent malicious code. Applicable Systems One or more documented processes High Impact BES cyber systems and their associated: pertaining to 1. electronic access control or monitoring systems; requirement R3 Part 2. physical access control systems; and 3.1 3. protected cyber assets Medium Impact BES cyber systems and their associated: 1. electronic access control or monitoring systems; 2. physical access control systems; and 3. protected cyber assets Requirements Deploy method(s) to deter, detect, or prevent malicious code. Verify that each Applicable System has one or Evidence that the Measures more documented methods deployed to processes pertaining to detect, or prevent malicious code. requirement R3 Part An example of evidence may include, but is not limited to, 3.1 have been records of the Responsible Entity’s performance of these implemented processes (e.g., through traditional antivirus, system hardening, policies, etc.).
R3 Requirement & Measure Evidence Submission Evidence Description Evidence Assessment Approach Auditor Notes R3. Each Responsible Entity shall implement, in a manner that identifies, assesses, and corrects deficiencies, one or more documented processes that collectively include each of the applicable requirement Parts in CIP‐007-AB‐5 Table R3 – Malicious Code Prevention. M3. Evidence must include each of the documented processes that collectively include each of the applicable requirement Parts in CIP‐007-AB‐5 Table R3 – Malicious Code Prevention and additional evidence to demonstrate implementation as described in the Measures column of the table. Part 3.1 in R3 – Malicious Code Prevention Applicable Systems High Impact BES cyber systems and their associated: 1. electronic access control or monitoring systems; 2. physical access control systems; and 3. protected cyber assets Medium Impact BES cyber systems and their associated: 1. electronic access control or monitoring systems; 2. physical access control systems; and 3. protected cyber assets Requirements Deploy method(s) to deter, detect, or prevent malicious code. Measures An example of evidence may include, but is not limited to, records of the Responsible Entity’s performance of these processes (e.g., through traditional antivirus, system hardening, policies, etc.). AR3 Part 3.1 Please provide: One or more documented processes pertaining to requirement R3 Part 3.1 Verify the Responsible Entity has documented one or more processes to deploy method(s) to detect, or prevent malicious code. Evidence that the processes pertaining to requirement R3 Part 3.1 have been implemented Verify that each Applicable System has one or more documented methods deployed to detect, or prevent malicious code.
CIP-007-AB-5-RSAW.docx