Artifact 3 · named C-ITP

The SNAP object. Not the task order. Not twelve bases.

Cloud IT Project is the thing CAO registers. Same string as the UII. One CSO at that IL. Twelve bases are on-ramps to one boundary unless data and the AO split it.

Who

Mission owner, CSO, DISN CAO, SCCA PMO.

C-ITP is the SNAP object. Four people. The TO is not one of them.

The mission's cloud project SNAP registers — an application, enclave, data set, or service onboarded into a provisionally authorized CSO. Name it the same as the UII / investment name. Not the JWCC task order. Not the CSO. Not Thunderdome. Not twelve bases.

moMission ownerPM / FSM. Categorizes, assesses, authorizes the C-ITP. Owns the SNAP package.

csoCSOThe CSP product (IaaS / PaaS / SaaS) with a DoD PA at this IL. Listed in DCAS. Registered in SNAP (IL4/5) or SGS (IL6).

caoDISN CAOReviews the SNAP registration. Issues Cloud Permission to Connect.

sccaSCCA PMOEngineers the BCAP/ICAP connection after CPTC. Optional VDSS/VDMS is extra.

Appendix C

Initiate → PA → hygiene → ADD → SNAP → CPTC → CAP → onboard.

Appendix C · register, connect, onboard. Order is the order.

C.1Initiate
C.2PA check
C.3Network hygiene
C.4ADD
C.5SNAP / SGS
C.6CPTC
C.7–C.8CAP
C.9Onboard

C.1InitiateName the C-ITP. Pick IL from the data (CC SRG §3). Pick CSO, deployment model, service model. This is planning — not SNAP yet.

C.2PA checkDoes this CSO hold a DoD PA at this IL? DCAS for IL4/5/6. SNAP already has current CSOs. No PA → sponsor the CSO or ask DoD CIO for exception. Do not invent an IL5 path on an IL4 offering.

C.3Network hygieneNIC IP space (IaaS/PaaS) or government enclave ranges (SaaS). PPSM tracking ID. NIPR DMZ whitelist if traffic hits the internet. CSSP aligned per DoDI 8530.01. Without these, CAO will bounce the package.

C.4ADDAO signs ATO or IATT. IATO is gone. IATT is test only — CPTC on an IATT is typically ≤90 days and is not operations. ATO required before the C-ITP goes operational in the CSO.

C.5SNAP / SGSRegister as Mission Owner (Cloud IT Project). Unclassified IL2/4/5 → SNAP (snap.dod.mil, CAC, DD 2875). IL6 → SGS. Upload ADD, topology (Appendix E), CSSP agreement, consent to monitor.

C.6CPTCDISN CAO reviews PA, CAP path, package sufficiency. Issues Cloud Permission to Connect. For DISA BCAP this notifies SCCA PMO. For IL2 or a Component CAP, CPTC may only acknowledge registration. Typical review: about five business days if the package is complete.

C.7–C.8CAPIL4/IL5 off-premises commercial CSO → BCAP. On-premises CSO with an external management plane → ICAP. IL2 may use NIPR IAP. SCCA onboarding form; DISA engineers the path. Thunderdome does not replace this for cloud→DISN.

C.9OnboardC-ITP lands on the CSO. Then sustain: keep SNAP current, CSSP live, ADD/PA unexpired. Expired ATO or PA is a temporary disconnect, not a paperwork exercise.

Charter

Six fields they fill. We do not register SNAP.

Charter · six fields. They name people. We do not register SNAP.

nameName = UIISame string as DITPR / SNaP-IT / DITIP investment. SNAP will fight a pet name.

ilIL from the dataCC SRG §3. CUI vs NSS. Not from the brochure.

csoOne CSO at that ILThe PA'd offering this C-ITP occupies. Two CSOs is two C-ITPs unless the AO says one system.

boundBoundaryAccounts / folder / VPC / share families. Twelve bases are on-ramps to this boundary.

aoAO / ISSM / PMNamed people. The ADD is theirs.

csspCSSPDoDI 8530.01. Who hunts. DISA CSSP or Component.

If they already hold it on this laptop — we read. We do not file it.

ShareDITPR / UIIWe have the SNAP name. Do not rename it.

ShareExisting ATO / SSP titleThat may already be the C-ITP. Confirm boundary.

ShareBase list, no UIIOne C-ITP unless data and AO split it. We will not register SNAP.

ShareNothing namedThe charter is the artifact. They fill names. We do not.

Not this

Twelve bases are on-ramps. Not twelve projects.

Not The task orderA CLIN is a bill. The C-ITP is the SNAP object.
Not Twelve bases as twelve projectsOn-ramps to one boundary unless data and the AO split it.
Not A pet nameSNAP will fight anything that is not the UII.

Phase Zero

Same string as the UII. The AO is a named person.

Phase Zero artifact

Leave with the sponsor

Charter: UII name, IL from the data, one CSO, boundary, AO / ISSM / PM, CSSP.

Awareness, not performance

They fill names. We do not register SNAP. Twelve bases are on-ramps, not twelve projects.

Make them aware of what is needed. Do not perform it — unless they already hold the artifact.

Open the workbench All vignettes Working with DISA JWCC vehicle