Special Access Programs (SAPs)
Special Access Programs (SAPs) are a category of U.S. government classified programs that impose security controls and access restrictions beyond those of standard classified programs. Access to a SAP requires a specific "need-to-know" determination in addition to an appropriate security clearance, and is typically controlled through a formal indoctrination process and maintained on strict access rosters. SAPs are further subdivided into Acknowledged SAPs (ASAPs), Unacknowledged SAPs (USAPs), and Waived Unacknowledged SAPs — the latter being the most compartmentalized tier, in which even the program's existence may be withheld from congressional oversight committees beyond select gang-of-eight notifications. The Air Force Special Access Program Central Office (SAPCO) manages the formal registry of Air Force SAPs, including those under the authority of the Office of the Administrative Assistant to the Secretary of the Air Force (SAF/AA).
UAP research alleges that non-human intelligence exploitation programs have been structured as Waived Unacknowledged SAPs, or even moved entirely outside acknowledged SAP frameworks as "outside activities," placing them beyond the reach of standard congressional and inspector general oversight. Edward C. Aldridge is alleged to have architected a "SAP morphing" strategy during his tenure as Under Secretary and Secretary of the Air Force that reconstituted UFO Legacy Programs as outside activities under SAF/AA, insulating them from the standard SAP oversight structure under SAF/AAZ. David Grusch testified that these programs represent an illegal use of SAP-derived security structures to perpetuate activities that have never been formally authorized or disclosed to Congress.
Historical Development
The formal SAP framework as recognized today did not emerge fully formed. During the 1950s, 1960s, and 1970s, highly classified programs relied on informal ad hoc security protocols — primarily top-secret codeword read-on access — that existed as SAPs in all but name. The Defense Counterintelligence and Security Agency's SAP training course directly states SAPs were publicly acknowledged for the first time in the early 1980s.
Key legislative and executive milestones in SAP development include:
- Eisenhower's EO 10501 (1953): Standardized the modern three-tier classification system (confidential/secret/top secret), eliminating a fourth "restricted" tier. This prompted program managers to introduce informal ad hoc codeword access controls.
- Nixon's EO 11652 (1972): Formally legitimized enhanced access controls for programs involving severe national security concerns, shifting from informal practices to structured policy. However, a 1973 House Committee on Government Operations report documented widespread uncontrolled growth of special access labels across DOD, expressing concern about dozens of agencies applying access controls without proper authority.
- Reagan's EO 12356 (1982): Standardized and expanded the SAP framework, tightened oversight, and effectively ended the "wild wild west" era during which legacy programs freely exploited top-secret codeword access with minimal accountability. The DCSA's SAP training course cites EO 12356 as the formal acknowledgment of SAPs.
- Yellow Fruit (1983): An internal DoD audit exposed an unacknowledged SAP out of the Army's Special Operations Division, triggering significant SAP oversight reforms and nearly exposing connected activities.
- Clinton/Perry SAPOC Reorganization (1994): Deputy Secretary of Defense William Perry greatly expanded SAPCO (Special Access Program Central Office) and SAPOC (Special Access Program Oversight Committee) and established the Senior Review Group (SRG), transitioning the most sensitive legacy activities into a quasi-government and industry oversight panel of approximately two dozen individuals. The Wilson-Davis notes reference this structure as the gatekeeping body that denied Admiral Thomas Wilson access to the crash retrieval portfolio.
Types of SAPs
Per UAP Gerb's Special Access Required Vol.2, SAPs governed under Executive Order 13526 and DoD Instructions 5205.11/5205.07 fall into three functional categories:
- Acquisition SAPs comprise roughly 75–80% of all DoD Special Access Programs, protecting sensitive research, development, test, and evaluation (RDT&E), modification, and procurement efforts. Oversight falls under the Under Secretary of Defense for Acquisition and Sustainment (USD A&S).
- Intelligence SAPs safeguard the planning and execution of sensitive intelligence and counterintelligence operations, overseen by the Under Secretary of Defense for Intelligence and Security (USD I&S).
- Operations and Support SAPs (OSAPs) protect the planning, execution, and logistical support of sensitive military operations where operational details must remain obscured.
The video illustrates the distinction using a hypothetical triangular airframe incorporating reverse-engineered, non-human-derived technology: an acquisition SAP would protect how the craft is built, an intelligence SAP would protect how the underlying recovery and its exploitability were determined, and an operations and support SAP would protect how and where the craft is operationally used.
Governance Hierarchy
SAP governance is structured top-down. At the base, component-level SAP Central Offices (SAPCOs) exist for each of the armed services, the Joint Chiefs of Staff, DARPA, and the Missile Defense Agency, each holding purview over SAPs within their own department. Above these sit OSD-level SAPCOs under USD(I&S), USD(A&S), and USD(R&E). Above those sits the DoD-wide SAPCO, which serves as the primary interface and access-approval authority for members of Congress and governs SAP policy DoD-wide. At the apex sits the Special Access Program Oversight Committee (SAPOC), established in 1994, and its Senior Review Group (SRG) — a body of senior executive service-level officials, "both in and out of government" per David Grusch, tasked with preventing duplication of SAPs across the DoD and serving as the primary gatekeeping structure for access into the most sensitive programs. UAP Gerb explicitly distinguishes the SAPOC/SRG governance structure from the alleged quasi-government-and-industry "control group" descended from the Majestic 12/NSC 5412 Committee lineage described in Manhattan Project 2.0 — arguing the former is the operational access-approval gatekeeper, while the latter is a separate, higher-level body focused on overall program direction.
Content-Only SAPs and the Non-Covert Action Loophole
Special Access Required Vol.2 argues the single most important loophole legacy programs exploit is the combination of the non-covert action designation (converting a covert-action program under 50 U.S. Code § 3093 into a White House SAP with no Title 50 reporting requirement) with the content-only budgetary/administrative designation, under which a SAP holds only critical program information (CPI) with no dedicated funding line — its costs absorbed into ordinary DoD or armed-service budgets — thereby waiving Title 10 reporting requirements as well. See Content-Only Special Access Program for full detail.
Department of Energy SAPs
DOE SAPs derive authority both from Executive Order 13526 (as with DoD SAPs) and, independently, from the Atomic Energy Act of 1954 — a statutory basis not subject to unilateral presidential declassification. UAP Gerb argues this makes DOE SAPs an especially airtight secrecy mechanism, citing the DOE's Office of Intelligence and Counterintelligence (OICI) as the agency's internal program-protection and counterintelligence apparatus for such programs.