4.3 High Impact BES Cyber Systems and For electronic access, verify at least once An example of evidence may their associated: every 15 calendar months that all user include, but is not limited to, accounts, user account groups, or user documentation of the review that EACMS; and role categories, and their specific, includes all of the following: PACS associated privileges are correct and are A dated listing of all those that the Responsible Entity Medium Impact BES Cyber Systems accounts/account groups determines are necessary. with External Routable Connectivity or roles within the and their associated: system; EACMS; and A summary description of PACS privileges associated with each group or role; Accounts assigned to the group or role; and Dated evidence showing verification of the privileges for the group are authorized and appropriate to the work function performed by people assigned to each account. Registered Entity Response (Required): Compliance Narrative: Provide a 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 Version Date Section(s) Document Audit Team Evidence Reviewed (This section to be completed by the Compliance Enforcement Authority):
4.3 High Impact BES Cyber Systems and their associated: EACMS; and PACS Medium Impact BES Cyber Systems with External Routable Connectivity and their associated: EACMS; and PACS For electronic access, verify at least once every 15 calendar months that all user accounts, user account groups, or user role categories, and their specific, associated privileges are correct and are those that the Responsible Entity determines are necessary. An example of evidence may include, but is not limited to, documentation of the review that includes all of the following: A dated listing of all accounts/account groups or roles within the system; A summary description of privileges associated with each group or role; Accounts assigned to the group or role; and Dated evidence showing verification of the privileges for the group are authorized and appropriate to the work function performed by people assigned to each account. Registered Entity Response (Required): Compliance Narrative: Provide a 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 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):
RSAW%20CIP-004-6_2015_v1.docx