Skip to content
On this page 7

PCI DSS 4.0: scope reduction by account

Account isolation is the cheapest PCI scope reduction available, and the most over-claimed. Here is what it removes, what stays in scope, and what proves it.

PCI DSS scope is the set of systems an assessor will test, and it is decided by connectivity rather than intent. Every system that stores, processes or transmits account data is in scope, every system that can reach one of those is in scope, and every system that can affect the security of either is in scope. Segmentation is the only lever that shrinks the list.

The reason this is worth engineering rather than arguing about: scope is the multiplier on every other cost in the assessment. Each additional in-scope system means more evidence, more controls to test, more remediation and more disagreement. Reducing scope is the highest-return compliance work available, and the account boundary is where it starts.

What is actually in scope?

#

Most teams think of scope as one ring. It is three.

CategoryWhat it meansCommon examplesCan isolation remove it?
Cardholder data environmentStores, processes or transmits account dataPayment service, checkout API, any datastore holding primary account numbers, log sinks that captured them by accidentNo. This is the thing being protected
Connected-to systemsCan reach the environment over a network, or is reachable from itInternal admin tools, shared databases, support consoles, anything on a permissive network pathYes, this is exactly what segmentation removes
Security-impacting systemsCan affect the security of the environment without holding card dataIdentity provider, key management, logging and monitoring, the deployment pipeline, the management account and its guardrailsNo. Isolation does not help; hardening and evidence do

The third row is the one that surprises people, and it is the row that quietly determines how long an assessment takes. Your single sign-on system is in scope because whoever controls it controls access. Your CI/CD pipeline is in scope because whatever it deploys into the environment is whatever an attacker could deploy. Your log archive is in scope because its integrity is the basis of every other claim you make.

Why the account boundary is the right unit

#

An account boundary is enforced by the cloud provider, above the workload, and it holds even when something inside it is compromised. Cross-account access has to be granted explicitly, which means there is no inherited permission and no accidental network adjacency to discover during an assessment. It is also the natural unit of everything an assessor asks about: billing, quotas, logging destination, blast radius and evidence scope all follow it.

The AWS Enterprise Baseline deploys one organization with 15 accounts across 2 organizational units, which gives you the vocabulary for a scoping conversation that would otherwise be a survey of tags. If the cardholder data environment is an account, then “list every system in scope” is a query and not a project. The multi-account landing zone post covers why the structure is shaped that way.

But an account boundary alone is not segmentation. Two accounts whose networks are joined by a permissive route are one environment with two bills. The boundary has to exist at both layers.

Figure 1
Scope boundaries across accounts and network domains

A band across the top holds the identity, audit, automation and network accounts, marked as in scope because they are security impacting. Below, two isolation domains sit side by side: the production domain containing the cardholder data environment, and the non-production domain containing sandbox, development and staging. A denied edge between the two domains is labeled blackhole route, showing that neither can reach the other. Both domains reach the internet only through centralized egress in the hub network.

shared accounts — in scope as security-impactingidentityauditautomationnetwork hubprod isolation domainprod — cardholder data environmentown VPC, own route table,no path to the other domainnonprod isolation domainsandboxdevstagingout of scope only whilethe blackhole holdsblackholethe account boundary and the network boundary have to say the same thing
Isolation has to agree at both layers. The production and non-production isolation domains cannot route to each other, while the shared accounts above remain in scope as security-impacting whatever the routing says.

How the network boundary is enforced

#

In the AWS Enterprise Baseline, spoke networks connect through a Transit Gateway with two isolation domains, production and non-production, each holding a route table that blackholes the other’s address ranges. Production and non-production cannot reach each other, and that is a property of the routing table rather than a convention anyone has to remember. Egress is centralized in a hub network with a NAT gateway in each of three Availability Zones, so spokes have no direct internet path of their own. Addresses come from an IP address manager with one address map, and a CI guard script rejects any pull request containing a hardcoded network range — which matters here because the most common segmentation failure is a range typed by hand into a rule that nobody revisits.

For an assessor, that yields three artifacts that are hard to argue with: the route tables showing the blackholes, flow logs from all six networks showing what actually traversed them, and the pull request history showing when the routing last changed and who approved it.

What the PCI switches give you

#

The AWS Enterprise Baseline ships PCI coverage in two shapes, both off by default because both cost money to run and only some organizations are in scope.

SwitchWhat it isSizeDefault
Security Hub PCI DSS v4.0.1 standardControl-level findings per resource, grouped by requirement144 controlsOff
PCI DSS v4.0 conformance pack, including global resource typesConfig rules with a compliance score per account, evaluating global resources such as identity127 rulesOff
PCI DSS v4.0 conformance pack, excluding global resource typesThe same, for additional regions, so global resources are scored once99 rulesOff
AWS Foundational Security Best PracticesBroad control findings that the PCI review leans on for data protectionMore than 300 controlsOff

The region rule is the part people get wrong: run the including-global pack in the home region and the excluding-global pack everywhere else. Run the including-global pack in every region and you will spend the first week of the assessment explaining why the same identity finding appears four times.

The underlying controls those checks evaluate are not optional extras. Organization-wide CloudTrail with log file validation, AWS Config recording in every account, GuardDuty with malware protection, Firewall Manager attaching a web application firewall to every workload load balancer, TLS-only storage policies, image scanning on push with immutable tags, and identity with no long-lived keys anywhere are on from the start. The switches add framework-shaped scoring on top of controls that already exist, which is the right order: if the pack is the first time a control appears, the pack will mostly tell you bad news.

Mapping requirements to mechanisms

#

A condensed version of the mapping, enough to check your own environment against.

RequirementThe mechanism that answers it
1. Network security controlsTransit Gateway isolation domains with blackhole routes, centralized egress, a web application firewall on every workload load balancer, optional egress inspection behind one switch
2. Secure configurationsConfiguration recording in every account, a hardened account baseline applied identically, instance metadata service version 2 enforced
3. Protect stored account dataEncryption defaults per account with customer-managed keys and annual rotation
4. Protect data in transmissionTLS-only storage policies with a TLS 1.2 minimum, HTTPS-only listeners with managed certificates
5. Protect against malicious softwareThreat detection in every account, including malware scanning of attached volumes
6. Secure systems and softwareImage scanning on push, immutable image tags, infrastructure changes through reviewed pull requests with policy and vulnerability scanning in the pipeline
7 and 8. Access control and authenticationSingle sign-on as the only human path, no identity users and no long-lived keys, MFA enforced by policy above the account, permission sets scoped per environment, unused access flagged at 90 days
10. Log and monitor all accessOrganization trail into a separate archive account, 365-day retention with lifecycle to colder storage, seven CIS alarms, network flow logs
11. Test security regularlyContinuous control findings, plus your own penetration testing, which no product performs for you
12. Organizational policyYours. Infrastructure contributes nothing here and should not pretend to

The honest limits of scope reduction

#

Five things segmentation will not do, and it is better to know them before an assessor says them.

  1. It does not shrink requirement 12. Policies, roles, awareness training, incident response and vendor management stay exactly the same size whether your environment is one account or fourteen.
  2. It does not remove the shared services. Identity, logging, key management and the pipeline are in scope because they are security-impacting. Isolating them from the card environment does not help; the only available move is to control and evidence them well.
  3. It has to be tested, not asserted. Segmentation is validated by penetration testing at an interval set by your merchant or service provider level. A diagram is not evidence, and neither is a route table on its own.
  4. It decays. A peering connection added in a hurry, a security group opened for an incident, a shared database quietly reused: each of these silently re-expands scope. Drift detection against the committed configuration is what keeps the boundary honest, and drift is a fact, not a failure covers how to treat it as a signal rather than an embarrassment.
  5. Your assessor decides scope, not you. You can make the boundary defensible and the evidence easy. The determination is theirs, in exactly the way certification is theirs.

What to do next

#

If card data is in your future rather than your present, the order is straightforward: decide whether you can avoid receiving account data at all, then put whatever remains in its own account, then make the network boundary say the same thing as the account boundary, then switch on the standard and the packs at least two weeks before anyone reads the score.

If card data is already in a shared account, the work is a migration rather than a flag, and it is worth starting before an assessment date exists. Readiness and certification are different jobs, and only the first one is yours to schedule.

The controls described here ship in the AWS Enterprise Baseline and are listed framework by framework on the compliance readiness page. If you want to know what your current environment would cost to bring inside a defensible boundary, that is what the BuiltForProd Assessment exists to tell you.

Questions

What is in scope for PCI DSS?

Three categories. The cardholder data environment, meaning anything that stores, processes or transmits account data. Connected-to systems that can reach it over a network. And security-impacting systems such as identity providers, logging, key management and deployment pipelines, which are in scope because compromising them compromises the environment even though they hold no card data.

Does putting the cardholder data environment in its own cloud account reduce scope?

It reduces scope only if the isolation is real at the network layer as well as the account layer, and only if you can demonstrate it. An account boundary prevents implicit identity and resource access, but two accounts joined by a permissive network path are a single flat environment as far as an assessor is concerned.

How do we prove segmentation to an assessor?

With the routing configuration and the traffic record together: route tables showing that the non-production ranges are blackholed from the production domain, security group and network access control rules, flow logs from every network, and a segmentation penetration test performed at the frequency your merchant or service provider level requires.

Which PCI conformance pack should we run in which region?

Run the pack that includes global resource types in your home region, so identity and other global resources are evaluated once, and the pack that excludes them in every additional region. Running the including-global pack everywhere produces duplicate findings for the same global resources and makes the score harder to read.

Does a cloud foundation make us PCI compliant?

No. It supplies infrastructure controls under most of the twelve requirements and the automated checks that evaluate them. Scoping the cardholder data environment, the assessment itself, and the requirements that are organizational rather than technical remain with you and your assessor.

This is what we build.

BuiltForProd deploys a production foundation into your own cloud accounts, hands over the repositories and the documentation, and, if you want it, keeps running it with your team. Tell us what you are running and what is coming next. The first call is 30 minutes, with an engineer who scopes engagements, not a salesperson.

The calendar invite and the video link go to this address. Prefer to write? Send a message instead.