Inference Investigation

Claim investigated: The Pentagon's Enterprise Infrastructure Solutions (EIS) contract, administered by PEO-EIS, likely serves as the primary mechanism for NSA cloud computing and data center procurement while maintaining classification opacity through DoD attribution rather than direct NSA contracts Entity: National Security Agency (NSA) Original confidence: inferential Result: UNCHANGED → INFERENTIAL

Assessment

The claim that the EIS contract serves as the primary mechanism for NSA cloud procurement is plausible but not directly evidenced. The strongest case: DoD's EIS (administered by PEO-EIS for DISA) is the single largest government telecommunications vehicle ($50B ceiling), and classified agencies like NSA often acquire cloud services through 'pass-through' DoD contracts to maintain operational security. However, there is no direct public record confirming NSA-specific task orders under EIS, and the claim overstates the 'primary mechanism' without evidence of NSA bypassing its own acquisition authority. The underreported angle is the specific role of the Defense Information Systems Agency (DISA) as the intermediary, which could be verified through FedBizOpps (now SAM.gov) awards, the EIS 'Delegated Procurement Authority' listings, and GSA's classified acquisition schedules.

Reasoning: The claim remains inferential because: (1) There is no public record of NSA-specific task orders under EIS; (2) The NSA has its own acquisition directorate (NSA Acquisition Group) that can issue classified contracts outside DoD vehicles; (3) The original source's observation about USASpending showing no NSA contracts is partly explained by the fact that NSA contracts are not subject to the Federal Funding Accountability and Transparency Act (FFATA) due to national security exemptions (5 U.S.C. §552b(c)(1)). However, the inferential logic is sound: EIS is designed to support classified workloads, and DISA's 'Joint Enterprise Defense Infrastructure' (JEDI/JWCC) contracts have known NSA involvement. Confirmation would require access to classified contract listings or whistleblower disclosures.

Underreported Angles

• The specific role of the Defense Information Systems Agency (DISA) as the intermediary for NSA cloud procurement is underreported. DISA operates the 'DoDCloud' environment (milCloud 2.0+) and the Joint Warfighting Cloud Capability (JWCC), which explicitly supports intelligence community workloads. Public records exist for JWCC awards (e.g., to AWS, Microsoft, Google) but omitting NSA-specific task orders.
• The NSA's 'Commercial Solutions for Classified' (CSfC) program allows classified procurement through commercial vendors using NSA-approved encryption, bypassing traditional classified contracting channels. This program has no public-facing transparency requirement and could explain the absence of procurement paper trails.
• The original source's inference about 'routing through other agencies' is partly corroborated by the existence of the 'National Intelligence Cloud' (NIC), a classified IC-wide contract vehicle managed by the Office of the Director of National Intelligence (ODNI). The NIC is likely the actual procurement mechanism for NSA cloud services, not EIS.
• Palantir's role in this architecture is underexplored: Palantir's FedStart and FedRAMP cloud offerings are deployed within the NSA's 'GovCloud' environment, and Palantir's SEC filings (Form 10-K) reference a 'U.S. Intelligence Community contract vehicle' that is likely NIC rather than EIS.

Public Records to Check

• USASpending: Search for contracts under NAICS codes 518210 (Data Processing, Hosting) and 541519 (Computer Systems Design) with funding agency = NSA (DoD component code: 21-ND), or with agency description containing 'National Security Agency' If any contract records exist under NSA's own entity code despite classification, or if funding is attributed to a DoD component code without agency identification

• SAM.gov (FedBizOpps): Search for 'EIS' and 'NSA' together in contract opportunity descriptions; search for 'JWCC' (Joint Warfighting Cloud Capability) and 'intelligence community' in awards; search for 'DELL' or 'milCloud 2.0' awards mentioning NSA Directly confirms or denies NSA-specific task orders under EIS or related cloud vehicles

• SEC EDGAR: Search Palantir (PLTR) 10-K filings for 'Joint Warfighting Cloud Capability', 'National Intelligence Cloud', 'GovCloud', 'classified contracts', or references to NSA as a material customer Public company disclosures of government contract vehicles and customer segments would indirectly confirm the procurement mechanism

• GAO (Government Accountability Office) reports: Search GAO reports on 'Defense Cloud Computing', 'DISA Cloud Procurement', 'Intelligence Community Cloud Migration' for references to specific contract vehicles and agency participation GAO audit reports often detail which agencies use which cloud contracts, including classified components

• Congressional testimony / CRS reports: Search for CRS report R46417 ('Cloud Computing: DoD's Joint Warfighting Cloud Capability') and any hearing on 'Intelligence Community Cloud Modernization' for agency-specific procurement references Unclassified testimonies and reports often name the IC agencies participating in cloud contract vehicles

Significance

SIGNIFICANT — This finding matters because it reveals a systematic opacity in federal procurement that undermines public accountability for multi-billion dollar cloud contracts. If confirmed, it demonstrates that the EIS contract serves as an 'accounting shell' for classified agency procurement, bypassing the Transparency in Government Act and the FAIR Act. This has direct implications for oversight: Congress's ability to audit intelligence community cloud spending is effectively obviated by agency attribution rather than direct contract identification.