Pentagon ordered to authenticate its own digital content
S. 3563 — A bill to require the Secretary of Defense assess and, as appropriate, implement open technical standards for digital content provenance, and for other purposes. · Filed by Gary Peters (D-MI) · 1 cosponsor · Introduced Dec 18, 2025 · Referred to committee
Your members of Congress
Enter a ZIP to see where your representative and both senators stood on this bill.
Looked up on this device — your ZIP is never stored on our servers.
What it does
This bill requires the Secretary of Defense to develop a roadmap by June 2026 for adopting open technical standards that verify the authenticity and origin of digital media released by the Department of Defense—essentially a plan to embed and verify credentials in DoD photos, videos, and other public content to combat deepfakes and misinformation. The Secretary must brief Congress by July 2026 on feasibility, stakeholder coordination, and next steps.
Why we flagged it
The bill's core function is to require DoD to assess and implement open technical standards for verifying the authenticity and provenance of its publicly released digital content. This is a straightforward government transparency and anti-misinformation measure.
What the text implies
- Adoption of open standards may create interoperability expectations across federal agencies beyond DoD, potentially driving broader government digital authentication infrastructure.
- Engagement with 'federally funded research and development centers, industry, and academia' may accelerate private-sector development of content provenance tools, creating a market for authentication technologies.
- Roadmap development and pilot efforts could establish DoD as a reference implementation, influencing private-sector and international standards for digital content verification.
Section numbers refer to the bill text the analysis read — linked under Primary records below.
Who it affects
Citizens benefit from a government commitment to authenticate its own public communications, reducing the spread of deepfakes and misinformation about military operations and policy. The bill imposes no new restrictions on citizens' rights or remedies; it is a transparency and accountability measure requiring the government to verify its own digital outputs.
Who stands to gain
- software and technology vendors specializing in digital authentication and content provenance tools
- federally funded research and development centers (FFRDCs) contracted to support standards assessmen
Named in the bill
Secretary of Defense, Department of Defense, Military departments and components, Congressional defense committees, Federally funded research and development centers (FFRDCs), Industry and academia stakeholders
Where it stands
1 cosponsor: 1 Republicans.
- Dec 18, 2025 — Introduced · Congress.gov: “Introduced in Senate”
- Dec 18, 2025 — Referred to Senate Committee on Armed Services · Congress.gov: “Read twice and referred to the Committee on Armed Services”
Dates and quoted wording are Congress.gov's action record; the timeline shows status changes, not every procedural step.
How this was measured
Analysis — Quorum's AI read the bill text published by Congress.gov (3,063 characters) on Jun 3, 2026. Section numbers in the findings refer to that text, linked below; transparency and hidden-provision scores are compared against the median of 16,222 analysed bills.
Status and sponsors — Congress.gov's bill record — actions, committee referrals and cosponsors — loaded nightly. The timeline shows status changes, not every procedural action.
As of — page rendered 2026-10-20.
“Pentagon ordered to authenticate its own digital content” QuorumCivic. https://share.quorumcivic.app/bill/119/s3563 Report an error
The week in bills
One email, Sunday: what Congress passed, what it changed, and who paid.
One link arrives to confirm the address. It is used for this email and nothing else, and every issue carries an unsubscribe link.