AI Data Centers

Data Center Physical Security for GPU Racks in Colocation: Cages, Access Logs, Escorts and Audit Evidence

Data center physical security is a tenant verification task in a colocation facility: the operator runs the controls, and the tenant holds the proof in a defined set of records. NIST SP 800-171 Rev 3 requires physical access audit logs, visitor escorts and controlled visitor activity for CUI systems, and tenants outside CUI scope can use them as a template.

The tenant leaves the walk with named records from the operator, each matched to a clause in its audit framework.

Before the Walk: Who Runs What, and Who Must Prove It

Operators and GPU owners split responsibilities in a colocation data center, so the walk covers the controls an operator runs on the tenant's behalf.

Three prerequisites set up the walk:

  1. The operator's facility or security manager must attend, with authority to open records and doors on demand.
  2. The audit framework the tenant answers to must be named first, because it decides which records to request: SOC 2, ISO/IEC 27001:2013 or a NIST-based audit.
  3. The current authorized-person list for the tenant's own cage must be in hand, so each observed entry can be checked against it.

Step 1: Get the Access Agreement and the Authorized-Person List in Writing

Entry authorization starts on paper, ahead of the first badge swipe. The University of Michigan's policy is one example: it requires individuals to agree to a Data Center Access and Security Agreement, or its equivalent, before access to its data centers.

Four records belong in this set:

  1. A signed access agreement covering each named individual before first entry.
  2. The named-person list for the cage, with each badge tied to one individual.
  3. The change procedure: who at the tenant may add or remove names, and how the operator is notified.
  4. The review cycle: a stated review frequency and a rule that removes departing staff from the list.

Done when: the tenant holds signed agreements and a dated list, and can name the person and process that changes it.

Step 2: Walk the Layers From the Site Edge to the Cage Door

Meesons, a security-hardware vendor, publishes a seven-item data centre physical security checklist. The tenant walks from the site edge inward and records each of its layers:

  1. Site location: an isolated area that does not advertise the data center.
  2. Hostile vehicle mitigation: roadblocks, bollards and tyre killers at multiple layers.
  3. External barriers: full-height turnstiles, tall fence lines and folding gates.
  4. CCTV and surveillance: recorded footage linked with visitor management systems and other access control.
  5. Guards: 24/7 employed guards who work the systems and patrol.
  6. Authentication and access policies: formal ID tokens, access cards, badges or QR codes linked to visitor management, with a separate authentication level for personnel who need the data floor.
  7. Biometrics: fingerprint, infrared and facial recognition, which Meesons says reduce the risk of lost tokens.

Two portal controls need direct observation:

  1. Mantrap: Gallagher, a perimeter-security vendor, calls mantraps essential because they admit one authenticated individual per validation. The tenant watches the portal admit one person per badge.
  2. Anti-passback: Gallagher says anti-passback prevents credential sharing. The tenant confirms that the door refuses a badge handed back to a second person.

Branch: if the facility has no portal or mantrap between the lobby and the data floor, the step continues: record the gap as a finding and check camera coverage and escort rules on that path.

Uptime Institute's Facility Security Review examines four areas. The first two set the scope of the site walk, and the last two set the document requests:

  1. Security and access: controlled access to computer rooms and support spaces, controlled building access, and controlled site access.
  2. Physical facility systems and features: doors and windows, bollards (including code compliance for removal or collapse), physical layering, and cameras with their type, number, location, recording procedures and archiving.
  3. Security policies and procedures: documents reviewed for completeness.
  4. Security staff and training: documents confirming security policies appear in employee training.

The Meesons checklist above also covers bollards and recorded camera footage.

Done when: each layer from the site edge to the data floor has a written observation: present, absent or degraded.

Step 3: Inspect the Cage Itself

We expect this step to fail most often at the enclosure, because a cage is only as strong as the walls and ceiling around it. The walk covers an adjacent tenant's wall and an open overhead grid as closely as the door, because both form part of the tenant's own security boundary.

Five checks cover the cage:

  1. Wall and ceiling closure: mesh or panels reach the slab or roof deck and close the joints at shared walls.
  2. Door lock type and key custody: who holds keys or badge permissions for the cage door, tenant or operator.
  3. Tenancy model: a private cage versus a shared suite, and which other tenants sit on the far side of each wall.
  4. Camera view of the cage door: a camera that records the door itself, with retained footage.
  5. Rack-level locks: the last physical layer inside the cage; the check covers the lock type on each rack, who holds the keys or badge permissions, and whether operator staff can open racks during remote-hands work.

Done when: the tenant can state, in writing, the enclosure's boundaries, who can open the door, and what the camera sees.

Step 4: Test Escort and Visitor Rules for Vendors and Remote Hands

Visitors are the access path a tenant does not badge for, so the escort rules carry the control. The tenant's rule requires a signed-in record and an escort for each person entering the cage.

Operator staff and remote administrator access need a separate control set beyond the cage walk.

Four tests apply:

  1. Visitor sign-in and badge issue: a vendor or delivery driver signs in, receives a distinct visitor badge, and the record names the individual.
  2. Escort inside the cage: remote-hands technicians and vendor engineers are accompanied, whether by tenant staff or operator security.
  3. Tenant approval: the operator requires the tenant's approval before admitting a third party to the cage, and the approval is logged.
  4. Delivery handling: parcels and replacement parts cross the cage threshold under the same escort rule as people.

Done when: a past visitor entry can be produced, with a named individual, an escort, and a tenant approval on record.

Step 5: Request the Access Logs and Test Them

Logs are the evidence a tenant can request between visits, and their fields decide their value as proof. Gallagher describes the audit logs and operator notes in its Command Centre platform as a documented chain of custody for incidents. A tenant needs the same record for routine entries to its own cage.

A usable log set shows six things:

  1. Who, which door, and when: each entry names the individual, the door or reader, and the date and time, so the tenant can match it to the authorized-person list from Step 1.
  2. Filtered scope: entries for the tenant's cage, filtered from the building's master log, including the data-floor portal on the path to the cage.
  3. Visitor and escort records: each third-party entry carries the visitor's name, the escort's name and the tenant approval from Step 4.
  4. A stated retention period: the operator quotes the period in writing, and the tenant checks that it covers the audit observation window.
  5. Tamper protection: the operator states where the log is stored, who holds edit rights, and whether an edit leaves its own record.
  6. Linked video: the camera recording for an entry is retrievable from the log by timestamp, and camera retention matches the log retention.

One gap decides the log's worth as proof of identity. Access cards can be lost, stolen or intentionally shared by co-workers, according to Tina D'Agostin, CEO of the facial-biometric vendor Alcatraz AI, in Data Center Knowledge. We read a badge-only log as unable to identify the person in a cage during credential sharing.

The tenant asks the operator how it binds a badge event to an individual: escort records, camera review or biometric authentication at the data floor.

Done when: the tenant has received a log extract for its own cage covering a stated period, and has matched at least one entry to a camera recording.

Step 6: Assemble the Audit Evidence Pack

Each walk record answers a named framework item. SOC 2 audits use badge or keycard records and visitor logs as physical access evidence under criterion CC6, Logical and Physical Access Controls.

The SOC 2 distinction sets the collection calendar. A Type I report assesses controls at a point in time; a Type II tests operating effectiveness over a period, typically 3 to 12 months. Type II records must cover the observation window from its first day, so evidence collection starts before the audit period.

ISO/IEC 27001:2013 Annex A.11 covers secure areas with physical entry controls (A.11.1) and equipment (A.11.2). NIST SP 800-53 Rev 5 supplies the PE controls for NIST-based audits: PE-2 physical access authorizations, PE-3 physical access control, PE-6 monitoring physical access and PE-8 visitor access records. Racks that handle CUI also answer to NIST SP 800-171 Rev 3 requirements 03.10.01 and 03.10.07.

RecordWhat it showsFramework hook
Signed access agreementsNamed individuals authorized before entry• SOC 2 CC6
• PE-2
• 03.10.01 (CUI)
Authorized-person list with review datesCurrent authorizations and removal on departure• SOC 2 CC6
• PE-2
Site walk notes on layers and portalControlled access at site, building and data floor• ISO 27001:2013 A.11.1
• PE-3
Cage photo set and lock inventoryEnclosure boundary and key custodyISO 27001:2013 A.11.1
Visitor sign-in and escort recordsThird-party entries accompanied and approved• PE-8
• 03.10.07 (CUI)
Cage access log extract with retention periodEntry history for the tenant's space• SOC 2 CC6
• PE-6

Done when: the tenant holds each record in the table, labeled with its framework hook.

Final Check: Trace One Visit End to End, Then Set the Recheck Trigger

Pick a real entry to the tenant's cage from the last quarter. Follow the badge record to the camera recording, the escort record, and the tenant's own ticket or approval; each record must name the same individual and timestamp.

Three events trigger a recheck:

  1. Lease renewal: the walk and the record requests repeat ahead of the new contract term.
  2. An operator-reported security incident: the trace runs again on entries around the incident.
  3. Each audit period: the evidence pack is refreshed for the new observation window.

Put log delivery, escort duties and access-list change procedures in the colocation contract terms.