Data Center Security: Physical and Cyber Controls in One Program
Physical access and network access belong in one data center security program. Here is how to set access zones, control contractors and keep the audit evidence.
Data center security controls who can reach your equipment and what they can do once inside. Physical access and network access belong in one security program. A valid badge does not authorize someone to use an open console, and a clean firewall report does not prove your server hall is secure.
Why does a firewall stay green when a badged visitor is in the hall?
A firewall cannot tell you whether a contractor entered the wrong cage. Someone at an unlocked console may use an already authenticated session without triggering a network alert. Physical access creates a path to systems that network controls alone cannot close.
Connect door events to incident response. If someone enters an unauthorized zone, security staff need to establish what equipment was accessible and whether any accounts or devices were used. Facilities and IT can keep separate systems, but someone must reconcile their records and own the investigation.
What are the five security zones in a mission-critical data center?
Use five concentric zones as a design model, not a universal building specification. Each step inward should require stronger verification and admit fewer people. Entrance layouts must also meet the facility’s fire and life-safety requirements.
| Zone | What it covers | Who gets in | What to check |
|---|---|---|---|
| 1. Perimeter | Fences, controlled gates and vehicle barriers | People with an authorized reason to enter the grounds | Intrusion alarms reach a monitored station |
| 2. Building | Controlled staff entrance and loading dock; code-compliant emergency exits | Authorized badge holders and verified deliveries | Propped doors and unmonitored entrances |
| 3. Secure corridor | Staffed checkpoint with a turnstile or mantrap where appropriate | Verified staff and approved, escorted visitors | One credentialed entry admits one person |
| 4. Data hall | Server rows and supporting infrastructure | Authorized staff and named vendors with current work orders | Contractor badges expire when work ends |
| 5. Cage or cabinet | Tenant cages and restricted equipment enclosures | The smallest authorized group; dual custody where justified | Tenant isolation and enforcement of cage permissions |
Colocation access must stop at the customer’s authorized space. Permission to enter a shared hall is not permission to open every cage. Protect power and cooling equipment separately, with locked enclosures and monitored alarms suited to the equipment.
How should biometric access connect to your identity system?
Use biometrics where the sensitivity justifies the friction, usually at the hall or cage. Pair them with a badge or PIN so one compromised credential is insufficient. Configure anti-passback to detect or prevent credential reuse that violates the expected entry-and-exit sequence. Anti-passback does not stop someone from holding a door open, which requires checkpoint design and enforcement.
Why one badge must equal one body
A badge log records credential use, not necessarily everyone who passed through the door. Test tailgating controls during an authorized exercise: can a second person follow without separate verification? Match the door event to camera footage and check whether staff challenge the extra person.
Turnstiles and mantraps can restrict passage, but procedures still matter. Define how escorts admit visitors without making shared entry an accepted shortcut.
Tying enrollment to offboarding
A biometric enrollment is an identity record. Manage it throughout the person’s access lifecycle, then remove it when authorization ends. Disabling a network account does not necessarily disable the fingerprint enrolled at a cage.
One offboarding workflow should cover both systems, with confirmation that each revocation succeeded. Periodic reviews should catch door credentials that survived an account closure.
How do you control HVAC and electrical contractors in a server hall?
A vendor contract does not authorize every employee the vendor sends. Control access by named individual and approved work order. Facilities may schedule the work, but security needs enough detail to enforce its boundaries:
- Record each person’s name and the zones required for the job.
- Apply appropriate background screening to vendor employees with sensitive access.
- Assign an escort for live-floor work and record who is responsible.
- Set badge expiration to match the approved work period; revoke access when the job closes.
- Verify deliveries at the loading dock against the expected shipment or work order.
- Use site instructions that define permitted routes and the exit procedure.
An unlisted contractor should not enter while someone sorts out the paperwork. Verify authorization first. A tailgating event or a badge used outside its approved zone should trigger an incident review, including what equipment the person could have reached.
Contractor control continues after onboarding. Close the work order only after confirming that temporary access has ended and any issued keys have been returned.
Where does the building management system belong on the network?
Separate the building management system, or BMS, from production networks. Controllers that manage cooling or power should not provide an unrestricted route to customer workloads. A compromised facilities controller can create both a network intrusion and an operational disruption.
Document every permitted connection between building systems and production. Identify its purpose and owner, then review whether it is still needed. Micro-segmentation limits lateral movement only when its rules are maintained; an old network diagram does not prove the current configuration enforces those boundaries.
What does a SOC 2 auditor look for in visitor logs and cage access?
SOC 2 testing depends on your system boundaries and stated controls. Confirm the applicable criteria and evidence requirements with your auditor before building the process. Legal counsel should review contractual or legal obligations that affect access records and retention.
Prepare records that show who was authorized and whether the control operated throughout the review period. These are practical evidence examples, not a universal auditor checklist.
| Evidence item | What to keep | What to check |
|---|---|---|
| Visitor log | Identity, host, purpose, entry and exit times, badge issued | Missing exit times or unidentified hosts |
| Escort record | Named escort linked to the visitor’s live-floor work | Whether the escort remained responsible throughout access |
| Access list per zone | Dated export with documented reviewer approval | Former staff and vendors whose work has ended |
| Dual-custody record | Two named people present where the control requires them | Bypasses during maintenance |
| Door event and camera footage | Retrievable footage matched to relevant access events | Timestamp alignment and agreed retention requirements |
| Offboarding record | Dated confirmation of credential revocation and key return | Building access left active after network access ends |
A firewall report cannot establish that a cage stayed locked. Test dual custody during a maintenance window, when operational pressure might expose a bypass. Confirm that camera footage can be retrieved against a specific door event and retained for the period your requirements specify.
How often should access lists and badges be reviewed?
Use quarterly zone-by-zone reviews as a starting cadence, then adjust for risk and contractual requirements. Do not wait for the next review to revoke access after offboarding or completed contractor work. An access incident should prompt an immediate review of the affected permissions.
- Export and date the access list for each zone.
- Compare permissions with current staff responsibilities and active vendor work orders.
- Remove unnecessary access and revoke badges tied to completed jobs.
- Record the reviewer’s approval and retain the evidence of changes.
For departing privileged staff, address shared codes as well as individual credentials. Collect keys and remove biometric enrollments. Confirm the changes in the access system itself; a completed HR ticket is not proof that a door credential stopped working.
Who should own the converged program, and how is it reported?
Name the accountable executive before buying more equipment. Facilities can operate badges while IT maintains firewalls, but one program owner must resolve risks that cross both departments. Otherwise, each team can complete its assigned work while an access gap remains open.
Board reporting should identify unresolved access risks and exceptions that leadership must accept or fund. The program owner does not need to administer every device. The owner must ensure the controls operate and that failures get corrected.
At Total 360 Security, we run security programs across 13 risk domains, including physical security and cybersecurity. We report directly to the board through our Enterprise Security Risk Management and Virtual CSO programs. The operating model establishes accountability across those domains without requiring every control to sit in one department.
What credentials should a security program operator hold?
Verify credentials against the proposed scope. For work in Texas, ask which services require licensing and confirm the firm’s authorization for that work. A certification demonstrates a qualification; it does not establish who will run your program.
- Request the Texas Department of Public Safety license number and confirmation of its scope.
- Verify the certifications held by the people responsible for the engagement.
- Name the person accountable for running the program day to day.
Total 360 Security is based in Fort Worth and is Texas DPS-licensed. Founded in 2013, we provide virtual executive security leadership for mid-market organizations. Read more about the firm and its leadership.
If your facility has separate owners for physical and network security but no accountable program leader, book a 30-minute risk discussion through the consultation booking page, or call 817-677-0515.
Frequently asked questions
Can a firewall report count as evidence for physical controls in a SOC 2 audit?
A firewall report does not prove that physical access controls operated. Evidence for a server hall may include access logs, visitor records and documented permission reviews. Confirm the evidence required for your specific controls with your auditor.
How often should badge access and vendor permissions be reviewed?
Quarterly reviews are a practical starting point, subject to your risk and contractual requirements. Revoke permissions when employment or approved vendor work ends rather than waiting for the next scheduled review. Review affected permissions immediately after an access incident.
What is the difference between a data center guard and a converged security program owner?
A guard performs assigned post duties, which may include verifying visitors and responding to alarms. A converged program owner is accountable for how physical and digital controls work together. That includes resolving cross-department failures and reporting the combined risk to leadership.
How do you prepare a colocation facility for a customer security assessment?
Confirm the customer’s assessment scope, then export current zone permissions and gather the corresponding access records. Verify tenant isolation and test any required dual-custody controls during maintenance. Check camera retrieval and document permitted connections between building systems and production networks.
What should you verify before hiring a firm to run data center security?
Verify licensing applicable to the work and the credentials of the people responsible. Ask who runs the program day to day and who handles an incident spanning facilities and IT. Require the proposal to define operational ownership, evidence maintenance and reporting responsibilities.
Total 360 Security provides virtual Chief Security Officer, vCISO, and Enterprise Security Risk Management programs for mid-market organizations. They design, run, and report security programs covering all 13 risk domains rather than just offering advisory decks or point solutions. The firm is Texas DPS-licensed with CPP, CISSP, and CISM credentials.
Serving Texas, California, Nevada, New Mexico.
More from the blog
10 min read
Identity Access Management Software: What to Govern First
A practical order for identity access management software: define privileged access, name an owner, inventory raw exports and review each quarter before buying a tool.
Read article7 min read
SOC 2 Audit: What Type II Requires and Who Owns Each Control
A SOC 2 audit is an independent CPA examination of your controls against the AICPA criteria. Here is what a Type II report requires, who owns each control and what evidence to keep.
Read article7 min read
Compliance Monitoring: What to Check Monthly and Quarterly
Compliance monitoring is the ongoing check that your operations follow the rules that apply to you. This guide sets a monthly evidence set, a quarterly sampling routine and clear ownership for every exception.
Read article