First test authorization · AO decision
Buying cloud is not permission to test. The AO still has to sign a bounded test.
IATT is the controlled way to try a landing zone without treating it as full operations. Time-boxed, named testers, clear exit. It protects the Authorizing Official while the estate is still being stabilized and cleaned up for cloud speed.
Four floors
CLIN. PA. Landing zone. Then the AO signs test.
- vehicleJWCC CLIN
- paDISA PA on the CSO
- lzaLanding zone
- iattIATT
- Gate 1 · CFTVehicle + PA
- Gate 2 · CFTLZA in gov
- Gate 3 · CFTSCCA placed
- Gate 4 · AOIATT signed
Purchase to occupancy
Order. Vend. Bound. Select. Ask. Occupy.
- 01Order
- 02Vend
- 03Bound
- 04Select
- 05Ask
- 06Occupy
AWS GovCloud · LZA
The IATT lives in the test OU. Not in management.
- 01 · CommercialCreateGovCloudAccount
- 02 · GovCloudIndependent org
- 03 · GovCloudBYO Audit + Log Archive
- 04 · GovCloudEnroll the test account
- Not Account Factory createRemoved in GovCloud. Commercial CreateGovCloudAccount, then invite.
- Not Resource Control PoliciesRCPs are not available. SCPs carry the deny-public / gov-region floor.
- Not AFT for new customersCodeStar Connections is not in GovCloud. Do not plan AFT as the IATT path.
- Not Consolidated billing featureNot available in GovCloud Control Tower the commercial way.
- Not Export-controlled in CT metadataAccount names, emails, OU names are Control Tower metadata. They cannot hold export-controlled data.
- Not One org, both partitionsA commercial org cannot contain GovCloud accounts. Two partitions, two orgs.
- Rung 1Tenancy
- Rung 2Identity
- Rung 3Org trail
- Rung 4Network
- Rung 5Keys + policy
- Rung 6Privileged
Pattern · IL5 storage as a service
Assured folder. GCS lifecycle. Twelve bases. Shares, not apps.
Assured Workloads Data Boundary for IL5 — the folder, org policies, US-person support. Not Azure. Not a share. Google Cloud Storage lifecycle in that folder. Standard for rapid access. Nearline / Coldline / Archive for the rest.
- 01Base LAN
- 02On-ramp
- 03SCCA
- 04Assured VPC
- 05Share
- 06Lifecycle
Twelve bases. One service. Twelve on-ramps. Not twelve ZTNA applications.
One base. One share family. One lifecycle hop. Synthetic data unless the AO says live. Not twelve bases on day one.
Not a ZTNA app catalog. Not Azure. Not a second CSO. Not production departmental home drives.
Microsoft prime
Azure Government. Isolation guidelines on top of the tenant. Test management group.
IL5 isolation guidelines on top of the gov tenant — dedicated hosts where required, CMK, Azure Policy, Private Link. The region name is not the isolation.
Management groups: platform (identity, connectivity, management, security) then a test management group. IATT occupies the test group. Prod stays SCP/Policy-locked empty.
Oracle prime
Defense Cloud realm. Compartments are the LZ. FastConnect, not the internet.
Dedicated government realms. Compartments are the LZ analogue. The tenancy is not the IATT.
Tenancy in the DoD realm. Root compartment holds IAM and logging. IATT occupies a child compartment. Prod compartment stays empty and policy-locked.
SCCA in the zone
Four functions. TCCM is a person.
Outside DISA
Thunderdome is how testers arrive. The LZ still has to exist.
- Named AO, ISSM, SCA.
- Categorize: CUI vs NSS, IL from the data.
- Select: 800-53B High + Cloud SRG + CNSSI 1253 if NSS.
- Inheritance written: CSP PA / SCCA / platform / residual.
- LZA DoD sample in us-gov-east-1 / us-gov-west-1.
- SCPs: government regions, federation-only, deny public user.
- Org CloudTrail + Config + GuardDuty on.
- CMK in gov. S3 Block Public Access org-wide.
- DCCS IATT Authorization Request.
- Test plan: objectives that need the live environment.
- Named testers. Data handling. Duration. Exit to ATO or DATO.
- eMASS current. POA&M started. Not a reconstructed binder.
Testers reach the IATT tenancy the way production will: SASE → connector → test VPC. No second on-ramp at ATO.
The LZ still federates ICAM, places the connector, encodes SCPs, and runs VDSS/VDMS/TCCM. Thunderdome does not occupy the test OU.
What the AO signs
Time. Testers. Data. Environment. Exit.
IATO (Interim Authorization to Operate) is not a DoD RMF outcome. DoDI 8510.01 and the DISN Connection Process Guide: operate with ATO or IATT. IATT is test. It is not a mini-ATO.
Not IATT
Eight things that get confused with an authorization to test.
- Not JWCC purchaseA CLIN is the vehicle. It does not authorize a system.
- Not Account vendingGovCloud accounts exist. Occupancy has not started.
- Not LZA deployThe platform is ready. The AO has not signed.
- Not DISA PAThe CSO may host. This mission may not, yet.
- Not ThunderdomeHow testers arrive. Not what they occupy.
- Not ProductionIATT is test. Standing users and live CUI need an ATO.
- Not Software factorySBOM and OSCAL wait. IATT does not emit a build.
- Not cATOAfter an ATO, in Monitor. McKeown memo. IATT is Authorize for test.
DoDI 8510.01: IATT is granted only when an operational environment or live data is required to complete specific test objectives, and expires at the completion of testing.