Part Applicable Systems Requirements Measures 3.3 High Impact BES Cyber Systems and For those methods identified in Part An example of evidence may include, but is their associated: 3.1 that use signatures or patterns, not limited to, documentation showing the have a process for the update of the process used for the update of signatures or EACMS; signatures or patterns. The process patterns. PACS; and must address testing and installing PCA the signatures or patterns. 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 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-007-6, R3, Part 3.3 This section to be completed by the Compliance Enforcement Authority For those methods identified in Part 3.1 that use signatures or patterns, verify the Responsible Entity has documented one or more processes to update the signatures or patterns. The process must address testing and installing the signatures or patterns. For each method deployed to deter, detect, or prevent malicious code that uses signatures or
Part Applicable Systems Requirements Measures 3.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 those methods identified in Part 3.1 that use signatures or patterns, have a process for the update of the signatures or patterns. The process must address testing and installing the signatures or patterns. An example of evidence may include, but is not limited to, documentation showing the process used for the update of signatures or patterns. 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 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-007-6, R3, Part 3.3 This section to be completed by the Compliance Enforcement Authority For those methods identified in Part 3.1 that use signatures or patterns, verify the Responsible Entity has documented one or more processes to update the signatures or patterns. The process must address testing and installing the signatures or patterns. For each method deployed to deter, detect, or prevent malicious code that uses signatures or