You moved onto a Special Access Program, opened the first security plan, and nothing matches the muscle memory. Short answer on JSIG vs RMF: it is still RMF. The process steps are the same, the control catalog is still NIST SP 800-53, and the categorization math is still CNSSI 1253. What changes is the document that interprets all three for SAP systems, the authority that signs, and the repository your package lives in. That document is the Joint Special Access Program Implementation Guide, the JSIG, and it works as a technical supplement rather than a competing framework.
The clearest government statement of the boundary sits in a DCSA manual about something else. The DCSA Assessment and Authorization Process Manual, version 2.1, dated 9 March 2020, covers cleared contractors in the National Industrial Security Program, and it says DCSA assesses SAP systems under the JSIG, Revision 4, when contractual requirements direct it, and applies the DAAPM when they do not. One agency, two manuals, and the contract decides. Read the DD Form 254 first.
What the JSIG Is, and What It Is Not
The JSIG provides standardized cybersecurity policy, procedures and implementation guidance for systems at all classification levels under the purview of the SAP Authorizing Official. It is a technical supplement to NIST SP 800-53 and CNSSI 1253, used in combination with the applicable volume of DoDM 5205.07 in the application of RMF. Nothing there replaces RMF. It narrows it.
The version posted in public is the 11 April 2016 final, and the file name DCSA hosts it under carries the string 53Rev4: it is keyed to NIST SP 800-53 Revision 4. The rest of the stack moved on. NIST published Revision 5 in September 2020 and issued Release 5.2.0 on 27 August 2025, and CNSSI 1253 was reissued 29 July 2022 built on Revision 5. The public JSIG predates the catalog the conventional side of DoD now cites, and the gap gets filled by community supplements that are not published. If your program hands you a baseline that does not match the 2016 document, that is the supplement doing its job, and the supplement is the authority.
What does not change when you walk through the door:
- The seven RMF steps. DoDI 8510.01 of 19 July 2022 runs Prepare, Categorize, Select, Implement, Assess, Authorize and Monitor, and the SAP community works that sequence.
- The control catalog. AC-2 is still account management, AU-6 is still audit review, CM-6 is still configuration settings.
- CNSSI 1253 as the categorization instruction, one impact level per security objective.
- The evidence burden: a procedure, a configuration, and proof the two match.
- POA&M discipline. Findings still get owners, milestones and dates.
- Continuous monitoring. The authorization is a start date, not a finish line.
Who the JSIG Applies To, and the Policy Chain Above It
DoDD 5205.07, Special Access Program Policy, dated 12 September 2024, sits at the top. It puts the Director, DoD SAPCO, reporting directly to the Deputy Secretary of Defense. The load-bearing line is in the DoD CIO responsibilities: the CIO develops and issues supplemental guidance for assessment and authorization of DoD SAP information systems. That is the authority the JSIG hangs from.
DoDM 5205.07, the Special Access Program Security Manual, effective 17 January 2025, is the operative manual. It reissues the June 2015 Volume 1 and cancels Volumes 2 and 3, so check whether a volume-numbered reference still exists. It says the DoD CIO sets the cybersecurity baseline through the JSIG or its successor, and that systems handling SAP information must operate in compliance with the ATO issued by the AO. That phrase “or its successor” is the policy writers saying out loud that the 2016 document is expected to be replaced.
Now the part that surprises people. I searched the text of DoDI 8510.01 for Special Access Program, SAP and JSIG and found none of them. The RMF instruction does not carve SAP out by name and never points at the JSIG; that authority lives entirely in the 5205.07 series. Rereading the policy behind DoD RMF in DoDI 8510.01 with that absence in mind explains why nobody on the conventional side ever mentioned the JSIG to you.
Categorization and Overlays: What Actually Shifts
Categorization does not get separate SAP math. CNSSI 1253 of 29 July 2022 governs, and its central mechanic is that it does not adopt the high-water mark concept from FIPS 200 for national security systems. You carry three values, not one. A SAP system is routinely high confidentiality with moderate integrity and moderate availability, and collapsing that to High because the program is sensitive is how baselines get bloated. The CNSSI 1253 categorization walkthrough covers mechanics that are identical here.
CNSSI 1253 also states that a categorization must not be changed or modified to reflect management decisions. Those belong in tailoring, with a written rationale an assessor can argue with, which is the same discipline described in building and defending a control baseline in RMF Step 2. It is the habit that survives the move best.
Overlays are where the public record thins out. In the 2022 instruction, overlays are published separately as attachments to Appendix E, and organizations are told to check the CNSS site periodically for new or updated ones. The named set includes Cross Domain Solutions, Space Platform, Privacy and Intelligence overlays, plus a footnote directing readers to the Classified NSS Overlay. No public SAP overlay appears in that list, and vendor write-ups that place a JSIG overlay in Appendix F are describing a structure the current instruction does not have. If PII rides on the system, the division of labor in privacy overlay, PTA and PIA work still applies without a SAP exemption.
The Protection Level You Will Hear About
SAP authorizations carry a Protection Level, a construct that predates RMF and lives inside the JSIG rather than in CNSSI 1253. Public evidence it is still in use: Microsoft states that its Azure Government Secret and Top Secret environments maintain JSIG Authorizations to Operate at Protection Level 3. I am not going to publish a Protection Level table I cannot source from a primary document, and you should be suspicious of posts that do. Ask your ISSM which Protection Level your enclave is authorized at and what it does to the AC and AU families.
The AO Structure and Who Signs
On the conventional side the rules are public and tight. DoDI 8510.01 requires that AOs only be government personnel, says the role cannot be re-delegated to personnel who do not meet that requirement, and bars AOs from delegating authorization decisions, though other duties may go to a formally appointed AODR.
In the SAP world the chain runs through the SAPCO structure. DoDM 5205.07 has the DoD CIO appointing an OSD or DoD-level AO for systems that process, store or transmit OSD and DoD-level SAPs, and delegating authorizing responsibility to the Cognizant Authority SAPCO and its corresponding AO. Copies of ATOs go to the Deputy CIO for SAP IT oversight, which tells you where visibility aggregates even when the package does not.
Two role differences show up in your first meeting. The first is the Delegated Authorizing Official, the DAO, which appears throughout SAP cybersecurity material alongside the AO and the Security Control Assessor. The second is the GAM, which DoDM 5205.07 identifies as serving as the information system owner and ensuring JSIG compliance. If a program manager used to sign as your system owner, note the title change before you route anything. The underlying split between the ISSO, the ISSM and the ISSE is the split you already know, with the Program Security Officer added as a gate that has no conventional equivalent.
What the Package Actually Looks Like
There is a public contract deliverable description for it. DI-ADMN-81969, titled Joint Special Access Program Implementation Guide (JSIG) System Authorization Package (SAP), is dated 07-AUG-2014 with a notice dated 02-2020. It describes the package as the vehicle used to identify, control and authorize a contractor’s proposed stand-alone computer systems or networks, and it says the contract ISSO or ISSM submits the documentation to the AO, the DAO or the PSO, who must give written approval before processing begins. Note the collision: in that document, SAP means System Authorization Package.
Confirm these six things in your first week, in this order:
- Which guide your contract invokes, JSIG or DAAPM. DCSA defaults to the DAAPM when the contract is silent.
- Which revision of the JSIG your program runs, and whether a community supplement overrides the 2016 public document. Ask in writing.
- Who your AO is, whether a DAO has been delegated, and which Cognizant Authority SAPCO sits above them.
- Your Protection Level, and which control families it changes relative to the CNSSI 1253 baseline.
- Where the package lives, who holds write access, and the approved path for anything that leaves the room.
- Whether the PSO signs before processing begins, because DI-ADMN-81969 puts written approval ahead of operation.
How an eMASS-Trained ISSO Adapts
Start with a fact that reframes the question: DoDI 8510.01 never names eMASS. It refers generally to automated assessment and authorization tools or designated repositories, and names the RMF Knowledge Service as the authoritative source for RMF implementation guidance. eMASS is the enterprise answer on the conventional networks, not a statutory one, and the trend still runs toward it. MARADMIN 324/25, signed 10 July 2025, moved Marine Corps assessment and authorization work off MCCAST and onto eMASS by 11 December 2025, and the DAAPM states that eMASS replaced OBMS as the system of record for NISP packages.
For SAP I could not verify a single DoD-wide system of record from a public primary source, and I will not name a tool I cannot cite. What policy does establish is that the ATO is issued by the AO and copies go to the Deputy CIO for SAP IT oversight. A report-up model, not a portal model: expect a program-hosted repository, a workflow routed through the ISSM and the PSO, and a system of record that is whatever your cognizant authority says it is.
You will miss eMASS. I did not expect to type that sentence either.
What you lose is scaffolding that was doing more work than you noticed: no control-by-control compliance roll-up to point at in a meeting, no inherited controls button quietly absorbing half your baseline, no automatic POA&M aging report. The security plan has to read well to a human who cannot click through to your evidence, so write each implementation statement to name the setting, where it lives, and the artifact that proves it.
The other two adaptations are physical and temporal. Screenshots, scan output and your own working notes inherit the enclave’s classification until someone with authority says otherwise, so ask what an artifact is classified at before you create it. And SAP schedules run on access: plan milestones against read-on timelines, not yours.
None of that changes the craft. The controls are the same controls, and what gets a package signed is still a clean story about what the system is, what it protects, and what you decided not to do and why. If you want a sequence to work against while you learn whose signature matters on your program, the RMF Checklist walks the same steps the JSIG interprets, which makes it a useful spine for the program-specific answers you collect.


Leave a Reply