Cloud boundaries
Where provider responsibility stops, where the mission system begins, and which environment or isolation constraints still need proof.
Public-source field reference · National security cloud
Start with the source. Work with the context.
The National Security Cloud Reference organizes public information about cloud boundaries, service scope, authorization evidence, and strategy change—without turning documentation into approval, orderability, or a recommendation.
Cloud Waypoint maintains this research because we need it to execute our own work responsibly. We are happy to share the public-safe portion with the mission community; the authoritative publishers remain the sources of record.
The Studio is the working reference environment: explore subjects, read source facts and Cloud Waypoint context separately, and verify the original source.
New feature. We are continuing to establish and verify sources of record. Feel free to navigate, and expect additional public-safe detail in the coming weeks.
What it covers
Four reference families, organized consistently.
The same four families organize this library and the Reference Studio. Each topic links back to its authoritative source.
Services & availability
Whether a named capability is documented in the required environment, region, authorization scope, and ordering path.
Authorization & evidence
What evidence can be reviewed or inherited, what remains with the mission, and who retains the risk decision.
Strategies & updates
What changed, what was superseded, and how current Department direction affects—not decides—the work.
Fictional learning laboratory
Follow authorization evidence through one connected model.
Explore how a control, fictional implementation, evidence object, finding, POA&M item, monitoring activity, and AO-visible refusal remain connected without generating an authorization decision.
FICTIONAL TRAINING / REFERENCE ARTIFACT — NOT A U.S. NAVY SYSTEM, PROGRAM, ARCHITECTURE, AUTHORIZATION, OR ENDORSEMENT. No government information was used to construct this specimen.
Sourcing promise
The original publisher remains the authority.
Cloud Waypoint does not own the government or cloud-provider source material. We filter, normalize, correlate, date-stamp, and explain public information so it is easier to use responsibly.
- Source facts stay visually separate from Cloud Waypoint interpretation.
- Authoritative sources remain visible and directly linked in the Studio.
- Users should confirm governing details against the original source before making a decision.
How to read the evidence
Five separate questions, never a progression.
A documented capability does not automatically become available, authorized, orderable, or suitable. Each state needs its own scoped evidence.
- Documented
- An authoritative source describes the fact within its stated scope.
- Available
- The provider reports the capability in the named environment and location.
- Authorized / in scope
- A named authorization source includes the defined boundary and conditions.
- Orderable
- A current acquisition path supports the defined item; JWCC service and SKU detail requires controlled confirmation.
- Mission-suitable
- Not determined publicly. Mission authority, architecture, constraints, and evidence remain decisive.
Freshness promise
Weekly change watch, human acceptance.
Public sources are checked weekly for availability and possible changes. Potential updates enter a review queue; a person must approve them before they appear here.
Age is not staleness. Verification intervals follow the source’s change profile, and unresolved gaps remain visible instead of being silently filled.
Dynamic update artifacts remain incubating. Weekly publications, feeds, and subscriptions are not part of this limited public release.
Ready to work
Move from orientation into the reference.
Use the same four families in a persistent workspace built for subject navigation, progressive detail, and source verification.