Skip to content

AOC, CDE scope, Requirement 9

PCI-DSS Colocation Providers: What Your QSA Will Ask, and How to Find a Facility That Can Answer

For PCI DSS, a colocation facility in your cardholder data environment should show a current Attestation of Compliance (AOC) as a service provider, assessed by a QSA against PCI DSS v4.0.1, with the physical controls of Requirement 9 in scope. “PCI compliant” on a website isn’t evidence. PCI DSS doesn’t change the rack price: a 5 kW full rack is $1,500–1,800 a month across our 26 markets (November 2026).

Updated November 2026 · Bob Spiegel, Founder, QuoteColo

A locked private colocation cage with a card reader and PIN keypad on the gate, racks inside
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

v4.0.1
the current PCI DSS version; v3.2.1 retired in March 2024 and v4.0 at the end of 2024
AOC
the document to ask for: a service provider Attestation of Compliance, signed by a QSA
3 months
minimum retention for visitor logs (9.3.4) and for camera or access-control data on sensitive areas (9.2.1.1)
$1,500–1,800
full 48U rack, 5 kW, across 26 markets: PCI DSS doesn’t add a price tier

From the PCI Security Standards Council’s PCI DSS v4.0.1; prices from Bob’s November 2026 City Price Sheet, per month. Not a compliance opinion.

What PCI-DSS actually requires from a colocation facility

PCI DSS doesn’t make the facility responsible for your whole compliance posture. It requires the facility to meet the controls that touch the physical and network layer of your cardholder data environment (CDE).

RequirementWhat it means for colocationWhat to ask the facility
1 and 2: network security controls and secure configurationsAny network equipment the facility runs inside your CDE must be segmented and configured securelyDoes the facility manage any network component that carries your card-data traffic? How is it isolated and documented?
6: secure systemsFacility-managed components in scope are patched and changes are controlledWhich components in your scope does the facility manage, and how often are they patched?
7 and 8: access by need, and authenticationWho can reach your cage or cabinet, how access is granted, reviewed and removed; MFA for any facility admin access into the CDE (8.4.2)Who at the facility has access to your space, and how is it logged and revoked?
9: physical accessEntry controls, monitoring of sensitive areas, visitors, media: the part your assessor checks on siteIs Requirement 9 in the scope of the facility’s AOC? How long are visitor logs and camera data kept?
12: managing service providersYou keep a list of providers and a written split of responsibilities; the provider acknowledges its partWill you provide a responsibility matrix (12.8.5) and a written acknowledgement (12.9)?

Most time with your assessor goes on Requirement 9: it covers every physical control at the facility.

CDE scoping: how your colocation choices affect your PCI-DSS scope

The most consequential decision isn’t the provider. It’s where you draw the boundary of your CDE, and your cage and network choices move that boundary.

ConfigurationScope effectAssessor’s view
Shared cabinet, no segmentationIn-scope systems share space and possibly network with others; scope can spreadThe most conservative: shared components get examined
Shared cabinet with network isolationTraffic separated logically; physical access sharedAcceptable if the segmentation is configured, documented and tested
Private cage with network isolationPhysical and logical boundaries both definedThe usual preference: you control the access list; segmentation can be checked
Private cage with dedicated circuitsNo shared network components in scopeThe cleanest to document and defend; the highest cost

Most payments and fintech teams with 2–8 racks land on a cage with network isolation; quarter and half cages give a locked perimeter at a smaller footprint. See private cage pricing.

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

AOC, SAQ, and QSA: what to ask facilities and why it matters

Three acronyms decide whether a facility’s compliance claim is evidence.

The AOC is the evidence.

There’s no PCI “certificate”. A service provider validates compliance each year, and its Attestation of Compliance states the version, the date and the services in scope.

Who assessed matters.

A Qualified Security Assessor (QSA) can assess other companies. An Internal Security Assessor can only assess their own employer, so an ISA can’t produce a service provider AOC you can rely on.

SAQ D is the only self-assessment for providers.

Smaller service providers can validate with SAQ D. Large ones, about 300,000 card transactions a year or more for Visa and Mastercard, need an on-site QSA assessment; most large operators validate that way.

Registries help, but don’t decide.

Visa’s Global Registry of Service Providers is public and lists providers registered by a client bank and revalidated yearly. Many colocation providers aren’t on it; ask for the AOC either way.

PCI-DSS v4.0: changes that affect colocation deployments

PCI DSS v4.0 was published in March 2022 and replaced by v4.0.1 in 2024; requirements that were future-dated became mandatory on 31 March 2025.

  1. Authentication

    MFA into the CDE

    What changed

    Since 31 March 2025, multi-factor authentication covers all non-console access into the CDE (8.4.2), not only administrators (8.4.1) and remote access (8.4.3).

    For colocation

    Mostly yours, for your systems. Ask whether any facility staff access into your CDE exists, and if so whether it uses MFA.

  2. Risk analysis

    Targeted risk analysis

    What changed

    Where the standard lets an entity set how often something happens, it must justify the frequency with a documented targeted risk analysis (12.3.1).

    For colocation

    Ask whether the facility has documented these for the controls it runs, such as review frequencies.

  3. Customized approach

    Another way to meet a requirement

    What changed

    An entity can meet a requirement’s objective with its own control, validated by a QSA, instead of the defined control. It can’t be used with a self-assessment questionnaire.

    For colocation

    If a facility’s AOC mentions it, ask which requirements and how the assessor tested them.

PCI-DSS shared responsibility: what the facility covers vs what you cover

PCI DSS in colocation is shared. Misalignment at the boundary, especially on network controls and physical access, is the most common source of scope creep.

AreaThe facilityYou
Physical access (Req. 9)Entry controls, monitoring of sensitive areas, visitor logs, badge processes for your cage or cabinetYour access list, prompt removals, reviewing logs on request
Network segmentation (Req. 1)Shared network equipment it runs; isolation it manages for youYour firewalls and devices in the CDE; documenting the segmentation boundary
Hardening and patching (Req. 2, 6)Facility-managed components in scopeEverything you run: operating systems, applications, devices
Media (Req. 9.4)Chain of custody for media it handles; process for hardware leavingTracking and destroying your own media, with certificates
Logs (Req. 10)Physical access records kept for the agreed period, available to your assessorYour system logs: 12 months kept, three immediately available (10.5.1)
Annual validation (Req. 12)Its own annual assessment and AOC; the responsibility matrix (12.8.5) and acknowledgement (12.9)Your own assessment, using the facility’s AOC as evidence for its part

The boundary that causes the most debate: shared network equipment. Get written confirmation of which components the facility manages and which are yours.

PCI-DSS Requirement 9: the colocation-specific controls your QSA will audit

Requirement 9, restricting physical access to cardholder data, is the part your assessor checks at the facility. Ask for documents, not assurances.

  1. STEP 1

    Processes (9.1)

    Written, current policies for physical security, with roles defined. Ask for the policy, its last review date and its owner.

  2. STEP 2

    Entry and monitoring (9.2)

    Entry controls to areas with card-data systems (9.2.1). Individual access to sensitive areas monitored with cameras, access-control systems or both, data kept at least three months (9.2.1.1).

  3. STEP 3

    People and visitors (9.3)

    Staff access tied to role and removed on termination. Visitors authorized, escorted, badged and recorded; the visitor log kept at least three months (9.3.4).

  4. STEP 4

    Media (9.4)

    Media with card data secured, tracked when it moves and destroyed when no longer needed. Ask about chain of custody for hardware leaving the facility and the destruction evidence.

Organizations we match to PCI-DSS colocation providers

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

WhoPCI DSS situationWhat the options include
Payments platforms and processorsAnnual assessment by a QSA; the facility is part of the CDEFacilities with a current service provider AOC on v4.0.1, private cages, documented segmentation
Fintech SaaS with payment featuresCustomer contracts require PCI DSSMid-tier providers with current AOCs that accept 2–8 racks
E-commerce platformsCardholder data passes through servers in the facilityCage options, network isolation and a clearly documented CDE boundary
Acquirers and gatewaysLarge service providers with on-site assessmentsFacilities with mature PCI programs and a named compliance contact
Healthcare or insurance with paymentsPCI DSS for payments, HIPAA for patient dataFacilities with both an AOC and a BAA; see HIPAA colocation
MSPs managing payment environmentsThe facility’s AOC is part of your evidenceMulti-tenant cages and per-tenant access records

Why finding a PCI DSS colocation provider is harder than it looks

“We support PCI environments” and “we hold a current AOC” are very different statements.

THE DIY WAY

You search for “PCI DSS compliant colocation”

Every result claims it. Only an AOC shows the facility was assessed as a service provider.

THE DIY WAY

You get an AOC but don’t read the scope

It may cover space and power but not remote hands or the network the facility manages for you.

THE DIY WAY

The AOC is on an old version

An AOC against v3.2.1 is out of date: v4.0.1 is the current standard.

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

PCI-DSS colocation: frequently asked questions

What does a colocation facility need to provide to be considered PCI-DSS compliant?

A current Attestation of Compliance (AOC) as a service provider, after a QSA assessment against PCI DSS v4.0.1, covering the services you use: at least the physical facility and Requirement 9, plus any network equipment or managed service in your CDE. Also a responsibility matrix showing which requirements are the facility’s, yours or shared.

What's the difference between a facility that 'supports PCI-DSS environments' and one that has a current AOC?

“Supports PCI environments” is a statement about the building. A current AOC is evidence that the facility’s own controls were assessed for the services it provides. Your assessor will ask for the AOC, not the web page, so get it before you shortlist.

Do I need a private cage for PCI-DSS, or is a shared cabinet acceptable?

Neither is mandated. PCI DSS requires physical access to your CDE to be restricted, documented and auditable. A shared cabinet with network isolation and access records can work; a private cage makes the boundary and the access list cleaner, which most assessors prefer. Quarter and half cages give that at a smaller footprint.

What is PCI-DSS v4.0 and why does it matter for my colocation choice?

The current version is v4.0.1, published in June 2024; v4.0 was retired at the end of 2024 and v3.2.1 in March 2024. The requirements that were future-dated became mandatory on 31 March 2025. An AOC against an older version is out of date, so check which version the facility’s AOC states.

How does network segmentation at the colocation layer affect my PCI-DSS scope?

Segmentation is how you keep systems out of scope. If in-scope systems connect to others through shared network equipment, scope spreads to them. At the colocation layer, confirm in writing which network components the facility manages, how your traffic is isolated, and who documents and tests the boundary.

What's the difference between a QSA and an ISA?

A Qualified Security Assessor works for a firm certified by the PCI Security Standards Council to assess other companies; a QSA assessment produces an AOC others can rely on. An Internal Security Assessor can only assess their own employer. For a facility’s compliance, ask who performed the assessment.

My facility says they're 'PCI-DSS certified.' Is that meaningful?

Not on its own. There’s no PCI DSS certificate: compliance is validated each year, and the AOC is the proof. Ask for the AOC, check its version and date, read the services in scope, and ask for the responsibility matrix. A Visa registry listing helps, but many colocation providers aren’t listed.

Can I use a facility's AOC as evidence in my own PCI-DSS assessment?

Yes. Your assessor asks for the AOC of every service provider in your CDE, and it covers the facility’s share of the responsibilities. It doesn’t cover yours: system hardening, application security and access management on your systems still need your own assessment.

Does QuoteColo find PCI-DSS colocation for small deployments?

Yes. Large operators often want bigger commitments and long terms; mid-tier and regional providers with current AOCs take 2–8 racks in private cages. You get matched options by email within 48 hours once the requirements are clear, with the AOC status and scope 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.