Moving your servers out of an in-house closet and into a professional colocation facility feels like a smart compliance upgrade. You hand the facility keys to a provider that already has biometric scanners, 24/7 guards, and a stack of certifications. What could go wrong?
Quite a bit, as it turns out. Security gaps most often arise not from colocation itself, but from assumptions that the provider manages controls that actually fall under the customer’s domain. The colocation model is built on a shared responsibility framework, and that word “shared” does real work. If you do not understand exactly where the provider’s obligations end and yours begin, you can walk into an audit with a certified facility and a noncompliant organization.
The global average cost of a data breach is $4.44 million, and organizations with high levels of compliance failures pay approximately $500,000 more per breach than those in compliance. That is not a rounding error. It is the direct financial cost of leaving gaps unaddressed. This article maps five of the most common compliance gaps organizations discover after a colocation move, and what you can do to close each one.
Key Takeaways
- The shared responsibility split is not automatic: While colocation provides a secure physical environment, it does not offload security and compliance responsibilities from the enterprise. Compliance remains a shared duty between the data center and each enterprise customer. Assuming otherwise is the root cause of most colocation compliance failures.
- Certifications do not cover your workloads by default: Security gaps most often arise because they do not guarantee compliance for customer workloads. A facility’s SOC 2 Type II report attests to the facility’s controls, not yours. Your applications, data, and network configurations require separate validation.
- Missing documentation costs more than the fine: Even a single undocumented cable swap or equipment reboot can create a gap that auditors flag as a control failure. Audit readiness is an ongoing operational discipline, not a one-time checklist.
- Encryption is your responsibility, not the facility’s: Regulations like PCI DSS require data encryption in transit and at rest, and those obligations stay with you regardless of how strong the facility’s physical controls are.
- A signed contract is not a compliance program: Network segmentation, encryption logging, vulnerability management, and testing remain your responsibility under PCI DSS 4.0.1. The same principle applies across HIPAA, SOC 2, and ISO 27001.
Quick-Start Prioritization Framework
| Gap | Most Urgent For | Effort to Close | Time to Results |
|---|---|---|---|
| Shared responsibility misunderstanding | All organizations | Low | Days |
| Physical access and audit trails | HIPAA, PCI DSS, SOC 2 | Medium | Weeks |
| Data encryption | PCI DSS, HIPAA, GDPR | Medium, High | Weeks |
| Network segmentation | PCI DSS, ISO 27001, DORA | High | Months |
| Missing contractual agreements | Healthcare, Financial Services | Low | Days |
Start here if you are:
- A healthcare organization: Address the BAA and physical access audit trail gaps first. If there is no BAA, that is a major HIPAA compliance gap.
- In financial services or retail: Prioritize PCI DSS network segmentation and encryption, then confirm your responsibility matrix with the provider.
- A general enterprise: Begin with the shared responsibility review. Map every compliance control to either the provider or your own team before anything else.
Gap 1: Misreading the Shared Responsibility Model
What the Provider Actually Owns
Colocation follows a shared-responsibility model: providers run the facility, while customers own and operate their hardware, operating systems, and applications. The facility provides power, cooling, physical security, and connectivity. Everything running on your servers belongs to you.
This split seems obvious until you are in front of an auditor. In my experience, the most common mistake is treating a facility’s SOC 2 Type II report as a proxy for organizational compliance. It covers the building. It says nothing about how you configure your servers, classify your data, or whether your team follows access-provisioning policies.
What You Actually Own
While an enterprise can leverage a compliance-ready colocation environment to build its digital infrastructure, each enterprise is fully accountable for meeting its own regulatory requirements. That includes logical access controls, operating system hardening, application-layer security, data classification, and your internal risk management program.
Pro Tip: Before signing a colocation contract, build a written responsibility matrix. List every control required by your applicable frameworks (SOC 2, HIPAA, PCI DSS, ISO 27001) and assign each one to either the provider or your team. Any control in a gray zone is a future audit finding.
For the fourth year in a row, CoreSite’s 2025 State of the Data Center Report found that respondents cited physical security as the most important attribute when choosing a colocation provider. Physical security matters enormously. The gap opens when organizations stop there and assume the rest of compliance is handled.
Gap 2: Incomplete Physical Access Documentation and Audit Trails
Why Access Logs Are a Compliance Asset
Physical access logs are not just an operational record. Under HIPAA, PCI DSS, and SOC 2, they are primary compliance evidence. Compliance frameworks including SOC 2, ISO 27001, HIPAA, and PCI DSS often require evidence of documented, exportable access logs, depending on audit scope, not just locked doors.
The challenge with colocation is that the facility generates a site-wide access record, while each tenant needs their own exportable, tenant-specific audit trail. Each tenant typically needs an exportable access record for their compliance obligations, separate from the operator’s site-wide record. Producing two versions of the truth from two different systems creates reconciliation work and audit risk.
Remote Hands: The Overlooked Gap
Remote hands services, where facility technicians perform physical tasks on your servers, sit at the intersection of two compliance obligations: physical access and change management. Because remote hands tasks sit at the intersection of physical access and operational change, they’re among the most scrutinized categories in any compliance review. Without structured documentation practices, even a single undocumented cable swap or equipment reboot can create a gap that auditors flag as a control failure.
According to Datacate’s compliance guidance, many regulations require businesses to provide detailed audit logs and reports, and not all colocation providers offer integrated audit-readiness solutions, leaving businesses to piece together compliance documentation themselves. The fix is to verify, before signing the contract, that your provider can deliver tenant-specific, timestamped access logs on demand, with enough retention to satisfy your longest applicable framework. Industry standard CCTV retention is at least 90 days, and HIPAA often requires six years of relevant records.

Pro Tip: Ask prospective providers specifically how remote hands tasks are documented. Request a sample work order and confirm it captures: who performed the task, what was done, the authorization chain, and the timestamp. If the sample is thin, that is what your audit evidence will look like.
Gap 3: Inadequate Data Encryption for In-Scope Workloads
The Two Layers Both Frameworks Require
Both encryption at rest and encryption in transit are required by virtually every major compliance framework. Moving to colocation does not change this, but it does change who is responsible for implementing it. The facility protects the physical drive. Everything above the hardware layer- encryption algorithms, key management, protocol configurations- belongs to you.
Compliant encryption meets the minimum requirements: AES-256 for data at rest, TLS 1.2+ for data in transit, and documented key management procedures. If your servers were running older protocol configurations in an on-premises environment and you moved them without remediation, those same gaps now live in a colocation cage.
The Key Management Problem
I have found that organizations frequently get the algorithm right and the key management wrong. While cloud providers encrypt data at rest by default, many compliance frameworks require customer-managed keys and documented key lifecycle management. In a colocation context, you own the hardware, which means you own the keys entirely. There is no provider-managed default to fall back on.
Legacy systems still operating TLS 1.1 or below present a compliance gap under NIST guidelines and represent an active vulnerability class. Treat a colocation migration as a forced inventory: audit every server’s protocol configuration before the move, and confirm that no legacy TLS version survives the transition.
According to IBM’s Cost of a Data Breach Report 2025, HIPAA violations in the healthcare sector can result in fines of up to $1.5 million per violation category per year, and PCI DSS violations for payment data result in fines from $5,000 to $100,000 per month until compliance is achieved. Both are preventable with correct encryption implementation. If you are not currently meeting AES-256 at rest and TLS 1.2+ in transit for all in-scope workloads, closing that gap is the highest-ROI compliance action you can take this quarter.
Gap 4: Network Segmentation Failures in a Multi-Tenant Environment
Why Multi-Tenancy Introduces Network Compliance Risk
In colocation arrangements where multiple companies share a facility, expanding access points and vulnerabilities becomes harder. Physical cages isolate hardware. They do not automatically isolate network traffic. In a shared environment, traffic from multiple tenants may traverse common network infrastructure unless explicit segmentation controls are in place.
The practical risk is that a weakness in segmentation or resource governance can turn a cost-saving architecture into a cross-tenant exposure. For regulated workloads, particularly those handling cardholder data or protected health information, cross-tenant exposure is not just a security event. It is a compliance event with its own notification obligations.
PCI DSS and ISO 27001 Requirements
Under PCI DSS 4.0.1, network segmentation is not just a best practice. The facility’s Attestation of Compliance covers physical security for your cardholder data environment. Network segmentation, encryption, logging, vulnerability management, and testing remain your responsibility under PCI DSS 4.0.1.
ISO 27001’s A.8.22 expects you to group systems and users by risk, strictly control flows between them, and make tenant boundaries real, not theoretical. Cross-tenant exposure is the modern version of a flat network because it lets one breach spread across customers and environments. Strong, risk-based segregation reduces this blast radius so that one tenant’s problem stays one tenant’s problem.
The action here is to verify segmentation at the network layer before migration and document it. A network diagram showing your cardholder data environment (or PHI environment) with explicit segment boundaries is evidence auditors request at the start of an assessment. Arrive without it, and you will spend the first day of the audit reconstructing your own topology.

Gap 5: Missing or Incomplete Contractual Compliance Agreements
The BAA Problem for Healthcare Workloads
If your servers handle protected health information (PHI) and your colocation provider can maintain or access the infrastructure where that PHI lives, you need a Business Associate Agreement (BAA) in place before data moves into that facility. Cloud service providers, colocation facilities, and hosting vendors require BAAs when they maintain infrastructure storing covered entity PHI, even when vendor personnel do not routinely access patient-level data.
A missing BAA is an independent violation. The Office for Civil Rights does not require a breach to have occurred before citing the absence of a required agreement. That means you can be fined for the missing document alone, even if no data was ever exposed.
What actually works is treating the BAA as a pre-condition for migration, not a paperwork step after go-live. If a vendor will not sign a BAA, cross it off for any PHI project right away, because that is a legal fact and not a setting your team can configure around.
The Responsibility Matrix Gap in Contracts
Beyond healthcare, every regulated industry faces a version of this problem. While most colocation facilities maintain strong physical security, contracts should clearly define access controls, monitoring protocols, and audit rights. They should also address compliance with relevant standards and assign responsibility for maintaining them.
Ambiguous contracts breed audit findings. Common compliance risks include contractual liability clauses that cap provider exposure too low, no right to audit the provider’s controls, and a mismatch between the provider’s certified scope and your specific cage.
Before signing any colocation agreement, confirm three things: the certification scope covers your specific cage or suite (not just the facility in general), you have the contractual right to request audit documentation, and all relevant framework-specific agreements (BAA for HIPAA, responsibility matrix for PCI DSS) are executed before hardware ships.
Pro Tip: Request the provider’s most recent SOC 2 Type II report and read the scope section carefully. Some providers hold certifications for one facility that do not extend to others. Verify that the specific location where your servers will live is within the certified scope, and ask for confirmation in writing.
Datacate’s Colocation Security Compliance
For organizations that need a colocation provider with documented, independently audited compliance credentials, especially for HIPAA and SOC 2 workloads, Datacate closes several of the gaps described above at the facility level, reducing the compliance burden on your team.
Datacate adheres to the SOC 2 standards based on the AICPA Trust Services Criteria, and its SOC 2 Type II audit of Colocation and Cloud Services builds on its initial SOC 2 Type I certification. That progression from Type I (point-in-time) to Type II (over-time operational testing) is meaningful: it demonstrates that controls are not just designed but actually functioning.
Datacate’s Rancho Cordova facility aligns with the HIPAA Security Rule, specifically sections 45 CFR 164.308, 164.310, and 164.312. The combined SOC 2 and HIPAA report verifies Datacate’s compliance with both frameworks, providing clients with confidence that their sensitive data is secure.
The facility’s security infrastructure includes multi-factor authentication systems, biometric security scanners, on-site security personnel, a camera surveillance system, and 24/7 access event recording. Auditors expect to see these physical safeguards documented when they review a client’s colocation arrangement.
When you move your equipment into a facility that already holds SOC 2 Type II and HIPAA certifications, such as Datacate’s Sacramento data center, you effectively inherit a significant portion of the compliance work, specifically the physical safeguards layer that would otherwise require your own facility build-out and certification program.
For the gaps that remain on your side of the responsibility boundary (encryption, network segmentation, logical access controls), Datacate’s compliance documentation provides a clean foundation that auditors can rely on for the physical controls portion of their review, while your team focuses on the application and data layers.
Frequently Asked Questions
Does a colocation provider’s SOC 2 certification mean my organization is SOC 2 compliant?
No. The provider’s SOC 2 Type II report attests to the facility’s physical and operational controls. However, this alone does not guarantee compliance for customer workloads. Your organization still needs to validate its own logical security controls, access management, change management, and risk assessment processes against the SOC 2 Trust Services Criteria.
What is the minimum encryption standard I need to meet for PCI DSS compliance in a colocation environment?
Compliant encryption meets the minimum requirements of AES-256 for data at rest, TLS 1.2+ for data in transit, and documented key management procedures. These requirements apply to your servers regardless of where they are physically located. The colocation facility’s physical security does not substitute for encryption controls at the application and storage layer.
Do I need a Business Associate Agreement with my colocation provider for HIPAA workloads?
Yes, in most cases. Colocation facilities require BAAs when they maintain infrastructure storing covered entity PHI, even when vendor personnel do not routinely access patient-level data. Confirm this before migration. A provider willing to execute a BAA signals that they understand their role in your compliance program. A provider that refuses or hedges on this point is a red flag for healthcare workloads.
How do I verify that a colocation facility’s compliance attestations cover my specific cage?
When evaluating compliance, examine the scope carefully: does the certification apply to the specific facility you are considering? A provider might have excellent certifications for its primary location that do not extend to secondary or satellite facilities. Request the actual certification documents, read the scope section, and confirm in writing that the specific space your hardware will occupy falls within that scope.
What network segmentation evidence do PCI DSS auditors typically request?
For colocation, PCI DSS requirements translate into specific physical security controls: badge readers and access logging, CCTV monitoring with 90-day retention, restrictions on who can access customer equipment, and documented procedures for managing access lists. At the network layer, auditors will request evidence of cardholder data environment (CDE) segmentation, including network diagrams, firewall rule sets, and evidence of periodic segmentation testing to confirm that in-scope systems cannot be reached from out-of-scope network segments.
Sources
- Is Data Center Colocation Secure? What CIOs and CISOs Need to Know, Security Boulevard. Analysis of colocation security gaps and shared responsibility. https://securityboulevard.com/2026/02/is-data-center-colocation-secure-what-cios-and-cisos-need-to-know/
- 2025 State of the Data Center Report, CoreSite. Annual survey on enterprise colocation priorities. https://www.coresite.com/news/coresite-releases-2025-state-of-the-data-center-report
- How Colocation Supports Compliance in Hybrid IT, CoreSite. Shared responsibility model in colocation. https://www.coresite.com/blog/how-colocation-supports-compliance-in-hybrid-it-understanding-the-shared-responsibility-model
- Average Cost of a Data Breach 2026, StationX (citing IBM 2025). Breach cost statistics by compliance posture. https://app.stationx.net/articles/cost-of-data-breach-statistics
- Data Center Compliance: Standards, Audits and Certifications, Metro Colo Advisor. SOC 2, HIPAA, PCI DSS shared responsibility. https://metrocoloadvisory.com/compliance-colocation/
- What Colocation Providers Do and Don’t Do for Your Infrastructure, Data Center Knowledge. Responsibility boundaries in colocation. https://www.datacenterknowledge.com/colocation/what-colocation-providers-do-and-don-t-do-for-your-infrastructure
- Compliance in the Data Center: Meeting Regulatory Standards, Datacate, Inc. HIPAA, PCI DSS, and SOC 2 colocation compliance. https://www.datacate.net/compliance-in-the-data-center-meeting-regulatory-standards/
- How to Document Remote Hands Tasks for Audit and Compliance Trails, Digita Data Center. Remote hands documentation requirements. https://datacenter.digita.fi/how-to-document-remote-hands-tasks-for-audit-and-compliance-trails/
- Colocation Compliance Checklist, Datum. Access logs, CCTV retention, and audit requirements. https://www.datum.co.uk/insights/blog/colocation-compliance-checklist/
- Data Center Access Control: Standards and Best Practices, Swiftlane. Compliance framework access log requirements. https://swiftlane.com/blog/access-control-for-data-centers/
- Cloud Encryption for Data at Rest and in Transit, SecureSystems. AES-256, TLS 1.2+, and key management requirements. https://www.securesystems.com/cloud-encryption/
- Colocation for Financial Services: Compliance, Security, and Ultra-Low Latency, Netrality. PCI DSS physical and network controls. https://netrality.com/blog/financial-services-colocation-compliance-security-low-latency/
- How A.8.22 Segregation of Networks Stops Cross-Tenant Security Risks, ISMS.online. ISO 27001 network segmentation in multi-tenant environments. https://www.isms.online/managed-service-providers/a-8-22-segregation-of-networks-preventing-cross-tenant-exposure/
- Activating the Colo Model: What Really Matters in Colocation Agreements, Morgan Lewis. Contract compliance obligations and audit rights. https://www.morganlewis.com/blogs/datacenterbytes/2026/05/activating-the-colo-model-what-really-matters-in-data-center-colocation-agreements
- Business Associate Agreement: Complete HIPAA Compliance Guide, Konfirmity. BAA requirements for colocation and hosting. https://www.konfirmity.com/glossary/business-associate-agreement-definition
- HIPAA Compliant Hosting Requirements Every Buyer Gets Wrong, Pantheon. BAA scope and shared responsibility limits. https://pantheon.io/learning-center/hosting/hipaa-compliant
- Security Compliances, Datacate, Inc. SOC 2 Type II, HIPAA, and CSA STAR certifications. https://www.datacate.net/compliances/
- Private Cage Colocation Explained, Datacate, Inc. Compliance certifications and physical security controls. https://www.datacate.net/private-cage-colocation/
- How Colocation Checks Half Your Compliance Boxes, Datacate, Inc. SOC 2 Type II inheritance and shared responsibility in certified facilities. https://www.datacate.net/how-colocation-checks-half-your-compliance-boxes/
- IBM Cost of a Data Breach Report 2025, IBM Security. Global and US breach cost averages, compliance failure costs. https://www.ibm.com/reports/data-breach





