Part 1.3 in AR1 Part 1.3 Please Verify the Responsible Entity has documented Table R1 Physical Security Plan provide: one or more physical security that utilize two – or more different physical access controls (this (i) One or more does not require two completely independent Applicable systems documented physical physical access control systems) to High Impact BES cyber systems and their security pertaining to collectively allow unescorted physical access into associated: requirement R1 Part 1.3. physical security perimeters to only those 1. electronic access control or monitoring individuals who have authorized unescorted systems; and physical access, where technically feasible. 2. protected cyber assets Requirements Where technically feasible, utilize two or more different physical access controls (this does not require two completely independent physical access control systems) to collectively allow unescorted physical access into to only physical security perimeters those individuals who have authorized unescorted physical access. Measures An example of evidence may include, but is not limited to, language in the physical security plan that describes the physical security perimeters and how (ii) Evidence that the Verify that each physical security perimeter unescorted physical access is controlled by two or physical security has at least two physical access controls, or that more different methods and that unescorted pertaining to requirement an approved Technical Feasibility Exception physical access is restricted to only authorized R1 Part 1.3 have been covers this circumstance. individuals, such as a list of authorized individuals implemented. accompanied by access logs. Verify that only those individuals with authorized unescorted physical access are allowed authorized unescorted physical access into each applicable physical security perimeter. If an approved Technical Feasibility Exception is applicable to this Part, verify the compensating measures identified by the approved Technical Feasibility Exception are implemented.
Part 1.3 in Table R1 – Physical Security Plan Applicable systems High Impact BES cyber systems and their associated: 1. electronic access control or monitoring systems; and 2. protected cyber assets Requirements Where technically feasible, utilize two or more different physical access controls (this does not require two completely independent physical access control systems) to collectively allow unescorted physical access into physical security perimeters to only those individuals who have authorized unescorted physical access. Measures An example of evidence may include, but is not limited to, language in the physical security plan that describes the physical security perimeters and how unescorted physical access is controlled by two or more different methods and that unescorted physical access is restricted to only authorized individuals, such as a list of authorized individuals accompanied by access logs. AR1 Part 1.3 Please provide: (i) One or more documented physical security pertaining to requirement R1 Part 1.3. Verify the Responsible Entity has documented one or more physical security that utilize two or more different physical access controls (this does not require two completely independent physical access control systems) to collectively allow unescorted physical access into physical security perimeters to only those individuals who have authorized unescorted physical access, where technically feasible. (ii) Evidence that the physical security pertaining to requirement R1 Part 1.3 have been implemented. Verify that each physical security perimeter has at least two physical access controls, or that an approved Technical Feasibility Exception covers this circumstance. Verify that only those individuals with authorized unescorted physical access are allowed authorized unescorted physical access into each applicable physical security perimeter. If an approved Technical Feasibility Exception is applicable to this Part, verify the compensating measures identified by the approved Technical Feasibility Exception are implemented.
CIP-006-AB-5-RSAW.docx