Skip to content
ControlVerdict
PE.L2-3.10.1addresses
PE.L2-3.10.1Limit Physical Access [CUI Data]
Limit physical access to organizational systems, equipment, and the respective operating environments to authorized individuals.
  • [a]

    authorized individuals allowed physical access are identified;
  • [b]

    physical access to organizational systems is limited to authorized individuals;
  • [c]

    physical access to equipment is limited to authorized individuals; and
  • [d]

    physical access to operating environments is limited to authorized individuals.

View full control

Three badge zones: office, engineering, and the server room are separate grants

ControlVerdict Corpus@cv-corpusOSCJul 31, 2026
Community is just starting — add yours. Only 1 verdict so far.Last verdict Aug 2, 2026

Implementation

AO coverage. Addresses all Limit Physical Access objectives: identifying who is authorized, and limiting physical access to systems, to equipment, and to the operating environments that house them.

Identifying authorized individuals. A badge zone matrix maps each job role to the zones it may enter, and the authorization record for each person is the badge system's group membership, exported and reviewed as a list of names. Anyone not on the list for a zone is a visitor there and is escorted, including employees — an engineer is not authorized in the server room simply by being an engineer.

Zone 1, the suite. Badge required at the suite door during business hours and at all times outside them. All employees and badged long-term contractors are in this zone. The landlord's lobby access is a separate credential we do not control, which is why the suite door rather than the building door is our first boundary.

Zone 2, engineering and the CUI work area. A separate badge group covering the engineering floor where drawings are worked and printed. Membership matches the enclave roster plus a small facilities set. Reception, sales, and finance are not in this group.

Zone 3, the server room. Badge plus a keyed lock on the room itself, six people in the group, no exceptions granted at the door. Systems and network equipment that store or transmit CUI are all inside this room; there is no equipment in an open closet or under a desk, which took a cleanup project to achieve.

Equipment outside the zones. Endpoints in open areas are cable-locked and configured to lock the screen quickly; printers capable of producing CUI are inside zone 2. Network jacks in common areas and conference rooms are on a guest segment with no route to the enclave, so a physical port does not become a logical bypass of the zone model.

Provisioning and removal. Badge grants come from the same HR-driven workflow as logical access: the same request, the same approver, the same termination trigger. Badges are deactivated on the termination date, and the badge system is included in the offboarding checklist rather than remembered separately.

Maintenance. Quarterly review of each zone's membership against the roster, with the zone 3 list reviewed by the IT director personally. Annual walk to confirm no in-scope equipment has migrated outside its zone.

Accepted gap. The landlord's after-hours building access and the shared HVAC and electrical rooms are outside our control. The lease requires notification of contractor access, our suite door remains a controlled boundary regardless of building access, and the server room's separate key means building-level access alone reaches nothing in scope.

What the evidence looks like

  • Badge zone matrix mapping roles to zones
  • Badge group membership export for all three zones with the quarterly review sign-off
  • Offboarding checklist showing badge deactivation, and a completed example
  • Network configuration showing common-area jacks on the guest segment
  • Lease provisions covering landlord-controlled areas and contractor notification

Environment

Single leased suite in a multi-tenant building. The landlord controls the lobby and after-hours building access; we control everything past our suite door. ~180 staff, ~40 with engineering access.

Tools

1 rating on this revision

  • AlignedControlVerdict Implementer@cv-implementerOSCAug 2, 2026

    Across the finish line

    Physical access control to the enclave room is described with visitor escort.

Was this example useful?

Quick reaction — no account needed. For reasoning that moves the community meter, cast a full verdict below.

Discussion(0)

No discussion on this example yet

Verdicts capture a conclusion. Use a thread when the interesting part is the argument.

Sign in to start a thread.