Skip to content

BAAs, physical safeguards, ePHI

HIPAA Colocation Providers: What the Physical Layer Actually Requires

For servers holding ePHI, healthcare compliance teams ask a colocation facility for three things: a signed business associate agreement (BAA), documented physical safeguards under 45 CFR §164.310, and a current risk analysis. There is no HIPAA certification. HIPAA doesn’t change the rack price either: a 5 kW full rack is $1,500–1,800 a month across our 26 markets (November 2026); the difference is in the paperwork.

Updated November 2026 · Bob Spiegel, Founder, QuoteColo

A row of private colocation cages with solid lower panels, mesh upper panels and a biometric reader on each gate
Bob Spiegel

“Tell me what you’re deploying; I’ll come back with real options from a network built over 20 years.”

— Bob Spiegel, Founder, QuoteColo

From our desk, November 2026

§164.310
the HIPAA physical safeguards: facility access, workstation use and security, device and media controls
60 days
the outer limit for a business associate to report a breach to you (§164.410)
None
official HIPAA certifications: HHS doesn’t certify facilities
$1,500–1,800
full 48U rack, 5 kW, across 26 markets: HIPAA doesn’t add a price tier

From 45 CFR Parts 160 and 164 (eCFR) and HHS guidance; prices from Bob’s November 2026 City Price Sheet, per month. Not legal advice.

What HIPAA actually requires from a colocation facility

HIPAA has no certification process, so no facility can be “HIPAA certified.” What matters is whether it meets the Security Rule’s requirements for the part of your environment it controls: the building, the access to it and the hardware that passes through it.

1. A business associate agreement (BAA)

A business associate is anyone who “creates, receives, maintains or transmits” protected health information on your behalf. HHS has no guidance on colocation specifically, but it treats storage providers with ongoing access to ePHI as business associates even if they can’t read it, and providers with only incidental access, like cleaning crews, as not. Remote hands, media handling or managed services push a facility firmly into business-associate territory. In practice, most healthcare compliance teams require a signed BAA from the facility before ePHI arrives.

2. Physical safeguards under §164.310

The Security Rule’s physical safeguards set four standards:

  • Facility access controls (§164.310(a)): limit physical access to ePHI systems to authorized people, with contingency operations, a facility security plan, access control and validation, and maintenance records.
  • Workstation use (§164.310(b)): what may be done at equipment with access to ePHI; for colocation, what facility staff may do at or near your servers.
  • Workstation security (§164.310(c)): physical safeguards for that equipment, such as cabinet locks and who holds the keys.
  • Device and media controls (§164.310(d)): how hardware and media with ePHI are received, moved, re-used and destroyed.

Two of the implementation specifications are required (disposal and media re-use); the other six are addressable, which means the facility must assess them and either implement them or document an equivalent alternative.

3. A current risk analysis

HIPAA requires a documented risk analysis but sets no fixed schedule: HHS calls it ongoing. Many buyers expect one no more than 12 months old, covering the facility you’ll use.

Enforcement is real on both counts: a pediatric practice paid $31,000 in 2017 for having no BAA with its records-storage vendor, and Fresenius Medical Care paid $3.5 million in 2018, partly for weak facility access and device and media controls.

§164.310 physical safeguards: what your auditor will ask the facility

Use this table when you evaluate a facility. Ask for the documents behind each line before you sign.

SafeguardRequired or addressableWhat to ask the facilityRed flag
Contingency operations (§164.310(a)(2)(i))AddressableWho authorizes emergency access, and how it’s loggedNo written emergency procedure
Facility security plan (§164.310(a)(2)(ii))AddressableThe written plan and its last review date“We have guards,” nothing written
Access control and validation (§164.310(a)(2)(iii))AddressableRole-based access lists, visitor escort and vendor access proceduresVisitors unescorted or unlogged
Maintenance records (§164.310(a)(2)(iv))AddressableThe log of repairs to locks, doors and badge readersNo records
Workstation use (§164.310(b))Standard, always appliesWhat staff may do at or near customer equipmentNo policy for staff at customer cabinets
Workstation security (§164.310(c))Standard, always appliesCabinet locking, and who holds keys or codes to yoursKeys not tracked
Disposal (§164.310(d)(2)(i))RequiredThe destruction process and certificates“We can dispose of drives,” no chain of custody
Media re-use (§164.310(d)(2)(ii))RequiredHow media are wiped before re-useNo written procedure
Accountability (§164.310(d)(2)(iii))AddressableRecords of hardware moving in and outNo record of movements

Data backup and storage (§164.310(d)(2)(iv), addressable) is usually your side of the line. In January 2025 HHS proposed a major Security Rule update, including annual compliance audits and yearly written verification of business associates’ safeguards; in November 2026 it is still a proposal.

Want these numbers for your own deployment? and we’ll reply with the providers that fit, with their prices.

HIPAA shared responsibility: facility vs covered entity

The facility covers the physical layer; your organization covers everything else. Auditors ask both sides about the boundary.

AreaThe facilityYour organization
Physical accessBuilding and data-hall entry, cage and cabinet locks, visitors, access logsThe access list, and telling the facility when to remove someone
Physical safeguard documentsWritten policies for access, staff at equipment and mediaReviewing them and using them in your own risk analysis
Media disposalChain of custody and certificates if it destroys your hardwareWhen and how hardware is decommissioned, and checking destruction
Encryption and system accessPort- and circuit-level network controls; no duty to encrypt your dataEncryption at rest and in transit; OS and application access
Administrative safeguardsIts own risk analysis and staff trainingYour risk analysis, policies and training
Breach notificationTell you without unreasonable delay, within 60 days at most, or sooner if the BAA says soNotify individuals within 60 days, HHS, and the media for breaches over 500 people
The BAASign it; flow equivalent terms to subcontractorsHave a BAA with every business associate handling ePHI

The boundary that causes most trouble: encrypting ePHI at rest is yours, not the facility’s. “HIPAA-compliant storage” from a colocation provider usually means physical controls only.

Cage vs. cabinet: what does HIPAA require?

HIPAA doesn’t require a private cage. It requires documented physical access controls: who can reach your systems, how access is approved and removed, and how entry is logged.

Shared cabinet

Works when the facility logs access at the cabinet, lets you manage the access list and can produce the records for your equipment quickly. Logs that only show who entered the data hall are harder to defend in an audit.

Private cage

A separate perimeter and clearer access records. Often preferred for frequent audits, highly sensitive records such as substance-use treatment data under 42 CFR Part 2, or when your auditor asks for isolation.

Quarter and half cages

Organizations with 1–6 racks rarely need a full cage. Smaller cages from mid-tier operators give a locked perimeter at a fraction of the cost. See private cage pricing.

What the BAA actually needs to say for colocation

A colocation BAA is narrower than one with a cloud or SaaS provider: the facility deals with your hardware, not your data. The agreement should reflect that and still cover what the rule requires.

Under 45 CFR §164.504(e) and §164.314(a), the agreement has to cover a set of minimum terms. For a colocation facility, each one has a practical meaning:

  • Permitted uses: access to your systems only as needed to provide the service (power, physical security, remote hands), and no other use or disclosure.
  • Safeguards: Security Rule safeguards for whatever ePHI the facility can reach.
  • Reporting: security incidents and breaches reported to you; the rule’s outer limit is 60 days, so write a shorter deadline into the BAA.
  • Subcontractors: equivalent terms from anyone who can reach your equipment, such as security or maintenance contractors.
  • HHS access: the facility’s records available to HHS when it checks compliance.
  • Termination: return or destruction of PHI where feasible; for colocation, that means your hardware leaving the building under a documented process.

Ask for audit-support terms too, even though the rule doesn’t require them: who sends you logs and documents, and how fast. Some providers have a standard colocation BAA; some negotiate one; a few decline. We find out which before you see the shortlist.

HIPAA colocation for healthcare AI, EHR, and digital health

The physical safeguards are the same for every workload. The infrastructure behind them isn’t.

Healthcare AI

Models trained on properly de-identified data can fall outside HIPAA; training pipelines, patient-facing inference and EHR integrations that touch identifiable data don’t. They need a BAA and documented safeguards, often with GPU density. See high-density colocation.

EHR platforms

Hosting for EHR systems usually comes with a BAA, a SOC 2 Type II report, documented access controls and redundant power to the cabinet. See A+B power and SOC 2 colocation.

Imaging and genomics

PACS archives, DICOM storage and genomics combine large storage with GPU compute. Size the footprint and power, then check the safeguards.

Behavioral health records

Substance-use disorder records under 42 CFR Part 2 carry extra disclosure rules. Tell us if they’re involved so the shortlist reflects it.

What does HIPAA colocation cost?

HIPAA isn’t a price tier. Facilities that can meet the physical safeguards charge market rates; the documentation is their overhead, not a line on your invoice.

Cost lineWhat to expectHIPAA note
Rack$750–1,500 for a half rack and $1,500–1,800 for a 5 kW full rack (our November 2026 sheet)Market, power and term set the price, not HIPAA.
Private cage, if neededQuoted per cage size; see private cage pricingA quarter or half cage usually fits 1–6 racks.
A+B powerIncluded in the cabinet price or billed per circuitUsually expected for ePHI systems; confirm it at the cabinet. See A+B power.
The BAARarely a separate line itemAsk how long legal review takes.
Audit supportIncluded hours or professional-services ratesAgree it before signing.
TermShorter terms usually cost more per monthHIPAA doesn’t change term structure.

Organizations we match to HIPAA colocation providers

Who asks us for HIPAA colocation, and what their options include.

WhoTypical situationWhat the options include
Health systems and providersHosting EHR, PACS or clinical applicationsA signed BAA, written §164.310 policies, cabinet-level access logs, cage options, SOC 2 Type II
Digital health startupsSteady workloads moving out of the cloud, small footprintMid-tier providers that sign BAAs, 2–6 rack minimums, 12-month terms
Healthcare AI platformsGPU training or inference on clinical data at 10–40 kW a rackFacilities with BAAs and documented safeguards that also support the density
Health insurers and payersClaims and member data, an in-house compliance teamProviders with BAA history, audit support and SOC 2 Type II
MSPs serving healthcareHosting client environments with ePHIBAAs, multi-tenant cages and per-tenant access records
Life sciencesTrial and patient-linked research dataHIPAA documentation, often HITRUST certification and GxP experience

Why “HIPAA compliant colocation” is hard to verify

There’s no certificate to check, so every provider can use the phrase.

THE DIY WAY

You search for “HIPAA compliant colocation”

Every result claims it. Website copy and security PDFs don’t replace a signed BAA and written §164.310 safeguards.

THE DIY WAY

You go to a large operator

Mature programs, but minimums, pricing and sales cycles that may not fit 2–6 racks.

THE DIY WAY

You find a regional provider

Better pricing and flexibility, but the BAA, risk analysis or written policies may be out of date. Your legal team finds out late.

How it works

You send the specs. We find the options. You decide.

STEP 1

Send your requirements.

Tell us what you're deploying, where you want it, and when you need it. Send the specs you have; we'll help with the rest.

HardwareRacks & kWLocationStart date

Estimates are fine. No perfect RFP needed.

STEP 3

Take the next step. On your terms.

Like the options? Contact the providers directly. Need more detail? Call or email us. We're here to help, not push you.

  • Go directly to the providers you like
  • Ask us questions whenever you need

Get 2–4 qualified options in 48 hours

Free for buyers

Your price is the same as going direct.

Comparable prices by email

Review the options before deciding on a call.

Trusted service since 2004

5,000+ clients helped.

By clicking here, I state that I have read and understood the Terms and Conditions

Case studies

See how we helped teams secure colocation with the right power, pricing, and providers.

Leonard Roszkowski

CEO Elemental Energy Solutions

Problem: Needed to source ASIC servers domestically. Skeptical about working with a new organization.

What we did: Connected them to buyers, sellers, and infrastructure partners across deployments. Removed procurement and logistics overhead entirely.

Result: Rapid organizational growth in a short period. Now uses QuoteColo as an ongoing procurement interface across hardware and infrastructure.

Noel Frutasio

CEO FSN Services and Communications

Problem: Regularly needed colocation space across multiple US states and time zones. Difficult to navigate the market without deep industry knowledge.

What we did: Defined requirements in one meeting, then delivered proposals with multiple carrier and data center options across every target market.

Result: Placed in 4 cities. Contracts signed quickly. Multi-state colocation needs resolved through a single point of contact.

Tim Mandell

DC Mining / MDI Access

Problem: Needed reliable options for crypto mining containers and equipment, along with industry partners who could support real deployment requirements.

What we did: Connected the project with relevant mining infrastructure and equipment resources through the QuoteColo network, simplifying the search and evaluation process.

Result: Gained a clearer path to suitable mining infrastructure, equipment and industry contacts without having to source every option independently.

5,000+

Clients helped since 2004

No Cost

to Buyers

500+

Worldwide providers

Quotes

in 48 h

HIPAA colocation: frequently asked questions

Can a colocation facility be 'HIPAA certified'?

No. HHS doesn’t certify facilities and doesn’t recognize private “HIPAA certified” labels. What you can check is evidence: a signed business associate agreement, written §164.310 physical safeguards, a current risk analysis, and reports such as SOC 2 Type II or a HITRUST certification. A facility that says it is “HIPAA certified” is using marketing language.

Does my colocation provider need to sign a BAA?

Usually, yes. HHS treats a provider that maintains ePHI as a business associate even if it can’t read it, and remote hands or media handling make that clearer. HHS hasn’t ruled on pure space-and-power colocation, so most healthcare compliance teams simply require a signed BAA before ePHI reaches the facility. Some providers sign readily; some don’t.

What does §164.310 actually require from a colocation facility?

Four standards: facility access controls, workstation use, workstation security, and device and media controls. In practice that means written access policies, cabinet-level access logs, rules for what staff may do near your equipment, and a documented chain of custody for hardware with ePHI. Disposal and media re-use are required specifications; the other six are addressable.

Do I need a private cage for HIPAA, or is a shared cabinet acceptable?

HIPAA requires documented physical access controls, not a cage. A shared cabinet can work if the facility logs access at the cabinet and you control the access list. A private cage makes the records unambiguous and suits frequent audits or highly sensitive records; quarter and half cages fit 1–6 racks at a fraction of a full cage’s cost.

What's the difference between HIPAA and HITECH for colocation purposes?

The HITECH Act (2009) and HHS’s 2013 Omnibus Rule made business associates, and their subcontractors, directly liable for Security Rule compliance. So a facility that is your business associate can face OCR enforcement itself for weak physical safeguards, not only through its contract with you. A provider that treats HIPAA as only your problem hasn’t caught up.

How does HIPAA colocation interact with SOC 2 Type II?

They complement each other. A SOC 2 Type II report shows the facility’s controls worked over a period and helps your risk analysis; it doesn’t replace a BAA or address §164.310 point by point. Most healthcare buyers ask for both, and enterprise customers often require both from your providers.

What should I request from a HIPAA colocation provider before signing?

Six things: its BAA template, written §164.310 policies, the date and scope of its latest risk analysis and who did it, its access-log retention and turnaround for log requests, its device and media disposal process, and its breach-notification procedure with the deadline it will commit to. Facilities that produce all six quickly are worth shortlisting.

Can QuoteColo find HIPAA colocation for small deployments (1-6 racks)?

Yes. This is the part of the market that’s hardest to find on your own: large operators prefer bigger footprints, while mid-tier and regional providers with current HIPAA documents take quarter and half cages and 1–6 racks. You get matched options by email within 48 hours once the requirements are clear, with the BAA status for each.

Does QuoteColo charge for this service?

No. You don’t pay us. Providers share their existing standard sales commission with QuoteColo, so there’s no added fee or markup on your provider quote.