Defense · EU AI Act

EU AI Act for defense AI workflows

EU AI Act in defense AI workflows: what compliance requires, who asks for evidence, and the records to keep.

Legal forceBinding law
Applies fromPhased: 2025-02-02, 2025-08-02, 2026-08-02; high-risk 2027-12-02 (Annex III) and 2028-08-02 (Annex I)
SectorDefense
Checked21 Oct 2026

01 / The rule

What EU AI Act requires

Providers, deployers, importers and distributors of AI systems placed on the EU market or whose output is used in the EU, and providers of general-purpose AI models.

  1. 01Do not place on the market or use prohibited AI practices listed in Article 5.
  2. 02Take measures to support AI literacy among staff who operate or use AI systems (Article 4).
  3. 03High-risk providers: run risk management, data governance, technical documentation, logging, human oversight and accuracy controls, then complete conformity assessment.
  4. 04High-risk providers: register systems, monitor them after deployment and report serious incidents.
  5. 05GPAI model providers: keep technical documentation, publish a training-content summary and adopt a copyright policy; systemic-risk models add evaluations and incident reporting.
  6. 06Meet Article 50 transparency: disclose AI interaction, mark synthetic content machine-readably, disclose deepfakes.

02 / In this sector

In a defense AI workflow

Written for AI systems and models throughout. Duties depend on role (provider or deployer) and risk tier, so the same organisation may carry different duties for different systems.

Usually asked by

Program office leads and ATO-package owners.

Named alongside

NIST AI RMF · DoW RAI · OMB M-25-21.

Sector pagePlanisphere for defense

03 / Records

Records to keep

  1. 01AI system inventory with risk classification and role per system
  2. 02Annex IV technical documentation and conformity assessment records
  3. 03Automatically generated logs and post-market monitoring plan
  4. 04AI literacy training records and Article 50 disclosure/marking specifications

Optional evidence · where Planisphere fits

Keep a record anyone can check

When your team meets a duty, Planisphere can seal the event it reports as a receipt.

01 · Your teamRecord the event

A disclosure shown, a review signed, a model change approved: the event your system reports.

02 · PlanisphereSeal it

The event becomes a sealed receipt, dated and attributed to whoever is signed in.

03 · AnyoneCheck it

Paste the receipt into Verify. No account or key.

A record supports your compliance evidence process. It is not a legal finding or a certification. Systems that call Planisphere's gate API can also hold or refuse an action before it runs.

SOURCES

Go back to the source

PRIMARY
Regulation (EU) 2024/1689 (Artificial Intelligence Act)

EUR-Lex, Publications Office of the EU

PRIMARY
Regulation (EU) 2026/1744 (Digital Omnibus on AI)

EUR-Lex, Publications Office of the EU

GUIDANCE

RELATED

Related: EU AI Act: the full guide · EU AI Act for medicine · EU AI Act for law · EU AI Act for education