Skip to content
Cloud WaypointWWT Federal Cloud Services

Authorization preparation

Make responsibilities clear before they become handoffs.

A landing zone is a start. Authorization is the milestone.

Book a 3-hour workshop How Foundations helps

The boundary, in one picture

Know what you inherit, what you share and what you own.

Much of the control work can be inherited from the platform. The mission service and its operating posture are yours.

Inherited from the platformSharedYoursOperationsConMon, incident, changeDataClassification, handling, retentionMission applicationCode, configuration, usersPlatform servicesCompute, storage, managed servicesIdentity and accessEnterprise identity, rolesNetwork and transportSCCA, CAP, enclave edgeFacilities and hardwareData centers, hostsYour authorizationboundary. Your AOaccepts the risk forwhat sits inside it.inherited controls rise from the platform
  • Inherited from the platform
  • Shared
  • Yours

Your authorization boundary. Your AO accepts the risk for what sits inside it.

  1. Operations

    ConMon, incident, change

    A quarter shared · three quarters yours

  2. Data

    Classification, handling, retention

    All yours

  3. Mission application

    Code, configuration, users

    All yours

  1. Platform services

    Compute, storage, managed services

    Half inherited · half shared

  2. Identity and access

    Enterprise identity, roles

    A quarter inherited · half shared · a quarter yours

  3. Network and transport

    SCCA, CAP, enclave edge

    Three quarters inherited · a quarter shared

  4. Facilities and hardware

    Data centers, hosts

    All inherited

Inherited controls rise from the platform

Illustrative split. Your platform’s control package and your boundary decision set the real one.

The path

Who produces what, from landing zone to continuous authorization.

Foundations prepares these threeLanding zoneOperating postureIATT readinessATOContinuousMission ownerBoundary decisionSOPs as cloudrunbooksEvidence ready totestChange recordsPlatform providerInherited controlpackagePlatform updatesISSMInheritancereviewConMon plan ·POA&MTest plan · draftSSPAuthorizationpackageConMon reportsAuthorizing officialIATT decisionATO decisionOngoing riskacceptance

  1. Foundations prepares

    Landing zone

    Mission owner
    Boundary decision
    Platform provider
    Inherited control package
    ISSM
    Inheritance review

  2. Foundations prepares

    Operating posture

    Mission owner
    SOPs as cloud runbooks
    ISSM
    ConMon plan · POA&M

  3. Foundations prepares

    IATT readiness

    Mission owner
    Evidence ready to test
    ISSM
    Test plan · draft SSP
    Authorizing official
    IATT decision

  4. Decision by your AO

    ATO

    ISSM
    Authorization package
    Authorizing official
    ATO decision

  5. Continuous

    Mission owner
    Change records
    Platform provider
    Platform updates
    ISSM
    ConMon reports
    Authorizing official
    Ongoing risk acceptance
Foundations prepares the first three steps. The ATO is the milestone: a decision by your AO.

Roles and decisions

Who does the work, and who makes the decision?

Responsibility map

Who builds, runs and evidences each control. A RACI assignment does not grant delegated authority.

Authority

Who accepts the risk. Always your designated AO.

Go deeper

See the decisions in context.

Trust and authority in the Visualizer

Open

GSS planning reference

Open

Enterprise reference

Open

NIST authorization boundary

Open

Start here

Bring the boundary question before it becomes a handoff.

A three-hour working session on the decision in front of you. You leave with a consultant-authored recap.

Book a 3-hour workshop

advisory@cloud-waypoint.com