From the Public Safety edition of October 19, 2026
OpenAI and Meta tell the federal Advisory Committee on Evidence Rules that deepfakes are becoming undetectable, as the panel weighs draft deepfake and AI-evidence rules; only 15 of 931 surveyed judges had seen a deepfake challenge
U.S. Judicial Conference Advisory Committee on Evidence Rules · Courts / evidence authentication and AI-generated evidence · United States (federal courts; influences state evidence rules)
- Publisher
- Investing.com (Yahoo Finance Canada)
- Original publication
- Thu, October 15, 2026 at 11:44 a.m. PDT (Investing.com via Yahoo Finance)
- Source retrieved
- 2026-10-20
- Event date
- 2026-10-15
What happened
At the committee’s Oct. 15 meeting in Boston, OpenAI policy counsel Shira Anderson said she does not believe a scientific method to detect AI images will exist, and that because each company uses its own watermarking system, no universal method can verify all content. Meta’s Devin Norder said recent AI media cannot be distinguished by humans and is cheap and fast to create. The committee has worked since 2023 on deepfake authentication and on holding AI-generated evidence to expert-witness reliability standards. A Federal Judicial Center survey in March found only 15 of 931 responding judges had encountered a deepfake challenge, and chair Judge Jesse Furman noted the issue has not yet appeared often in cases.
Why it matters
Body-camera, surveillance, jail-call and citizen video are core evidence in criminal courts. Vendor testimony that detection and watermark checks will not be reliable shifts the burden to provenance and chain-of-custody controls at the agencies that collect evidence.
Evidence and measured results
Opened the Investing.com report syndicated on Yahoo Finance. Quotes and the FJC survey figure are as reported. Secondary analysis (On The Wire, Oct. 19) reviewed during research describes draft Rule 901(c) and revised Rule 707 as not adopted; those rule details are not drawn from the opened source.
Limitations and uncertainty
Brief wire report; statements are company representatives’ views; survey shows challenges are still rare; no rule adopted.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-20; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Courts may soon scrutinize digital evidence authenticity while vendors say deepfake detection will not be reliable.
- Stakeholders
- District attorney
- Police evidence unit manager
- Public defender
- Court administrator
- Agency CIO
- Discovery questions
- How do you prove a video has not been altered?
- Do you accept citizen-submitted media, and how is it verified?
- Are files hashed on ingest?
- Have any authenticity challenges occurred?
- Value hypothesis
- Stronger provenance records can prepare agencies for authenticity challenges without relying on detectors.
- Potential engagement
- 4-week evidence provenance and chain-of-custody gap assessment for digital media.
- Unsupported claims
- A detector can reliably identify deepfakes
- Deepfake challenges are common today
- A specific federal rule will be adopted
Pre-sales engineering
Role takeaway
- Fit
- Prosecutors and agencies managing large volumes of digital media evidence.
- Architecture and integration
- Hash on capture or ingest, preserve original files and metadata, log access and exports, and generate chain-of-custody reports from the evidence platform.
- Prerequisites
- Evidence platform with hashing and audit logs
- Policy for citizen-submitted media
- Prosecutor requirements
- Constraints
- Rules still under study
- Mixed device fleets lack signed metadata
- Citizen media lacks provenance
- Security
- Restrict edit rights, keep originals immutable and log every transformation such as redaction.
- Proof of value
- Proposed: generate chain-of-custody reports for five closed cases
- Proposed: verify hashes match originals after redaction workflows
Delivery
Role takeaway
- Work
- Inventory evidence sources, close provenance gaps and create a standard authenticity packet.
- Dependencies
- Evidence platform configuration
- Prosecutor guidance
- Device metadata support
- Ownership
- Evidence unit manager with the prosecutor’s office
- Skills and adoption
- Train evidence technicians and attorneys on provenance documentation and authenticity challenges.
- Governance checkpoints
- Prosecutor review of packet format
- Annual evidence audit
- Review after federal rule decisions
- Acceptance criteria
- Proposed: 100% of digital media items hashed on ingest
- Proposed: authenticity packet produced within one business day on request
- Risks
- Citizen media without provenance
- Legacy devices lacking metadata
- Overreliance on detector vendors
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Agencies should rely on capture-time provenance (signed device metadata, hash on ingest, immutable evidence logs) rather than after-the-fact deepfake detectors.
Governance
Who approves, reviews and stays accountable for outcomes?
Federal rule changes remain under study; the committee has not adopted a deepfake rule. State courts often follow federal evidence rules, so the outcome will shape state practice.
Security and privacy
What data, permissions and controls need testing?
Vendor watermarking is fragmented, so authenticity checks cannot depend on one company’s system.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Prosecutors, defenders and evidence technicians will need training on authentication challenges and provenance documentation.
Procurement
What should contracts, pricing and exit terms secure?
Evidence-management and camera contracts should require tamper-evident hashing, signed metadata and exportable chain-of-custody logs.
Operating model
Which teams own the service once it runs?
Evidence units and prosecutors share responsibility for proving authenticity; courts set the threshold.
Publication history
- 2026-10-19Public Safety · Issue 417 resources
Stable resource ID: openai-meta-federal-evidence-committee-deepfake-warning-20261015