Ansvar AIRegulation
EU drone law — Reg (EU) 2019/947 (operations) · 2019/945 (product)
provision-level
Sector · Drone / UAS
Drone & UAS
Where drone law, drone-cyber threat modelling, and an agent-ready corpus meet.
Ansvar is a gateway for the AI assistant your team already uses — Claude, Microsoft Copilot, any MCP client. Connect it, and every answer below comes back cited to the provision or marked unresolved.
2019/947EU drone law, provision-level
70+Ansvar UAS threats, ATT&CK-mapped
TARA+ counter-UAS assessment
UAS compliance and security in one lane — EU drone law at provision level, eleven national UAS rulebooks and the US federal aviation code beside it, an Ansvar-authored UAS threat library and SORA determination chain, and a standards clause-map for the drone stack, wired into threat-model, TARA and counter-UAS workflows. No other compliance tool fuses aviation law with drone-cyber threat content.
what we cover
The law and standards we ground on
Guidance
UAS threat library
Ansvar-authored drone threats & attack techniques, cross-referenced to ATT&CK for ICS and CAPEC
Guidance
SORA determination chain — Reg (EU) 2019/947 Art. 11
Ansvar-authored: the intrinsic ground-risk class with its M1/M2 mitigations, the air-risk class and TMPR, the SAIL matrix, the SORA 2.5 operational safety objectives and the tiered containment requirements
Standard
Control mapping: UAS standards stack
clause map across product conformity (EN 4709-x direct Remote ID and geo-awareness), Remote ID & UTM (ASTM F3411/F3548, ED-269/270/318), operations (ISO 21384-3, ISO 23629-x) and airworthiness security (DO-326A/356A/355 and the ED-202A/203A/204A equivalents) + Ansvar cross-refs — not the standard text; standards can be licensed in via the SIS add-on (/standards)
Law
National UAS rulebooks — BE, DE, ES, GB, HU, IS, LT, LU, LV, NL and SE
provision-level, alongside the EU regulations
Regulation
US federal aviation regulation (FAA) + 14 CFR Part 107
the FAA code served verbatim from the eCFR, with the US small-UAS rules addressable beside it
Regulation
Horizontal: Cyber Resilience Act · RED · GPSR
drone product security
what you can do
Workflows that turn it into evidence
Drone operator compliance
operational authorisation and obligations under Reg (EU) 2019/947 (legally reviewed)
Drone product-security conformity
against Reg (EU) 2019/945, the CRA and RED (legally reviewed)
Drone threat model (UAS STRIDE)
over the platform, datalink, ground station and backend
assembledPremium
UAS TARA
threat analysis & risk assessment off the UAS threat library — an available analysis, not a legally-assured verdict
assembledTeam
Counter-UAS assessment
an available analysis of counter-UAS posture — not legal advice on use of force
STRIDE threat-model workflows run on every plan against a system you describe — 1 run a month on Free, 2 on Solo, 5 on Premium, which also adds the LINDDUN and TARA families, the rendered reports, and case law inside the run. Document-grounded workflows run on Team and Company. Every tier runs the same corpora as cited research inside your own AI client.
Questions buyers ask first
- What makes this different from a SORA tool?
- SORA tooling stops at the operational risk assessment. This lane fuses the drone law, an Ansvar-authored UAS threat library mapped to ATT&CK, and a standards clause-map — so a single workflow takes you from 2019/947 obligations to a cited UAS threat model and TARA.
- Are the TARA and counter-UAS outputs legally assured?
- No. The operator-compliance and product-security workflows are legally reviewed; the UAS TARA and counter-UAS assessment are available analyses grounded in cited sources, not legal opinions. Counter-UAS in particular says nothing about lawful use of force.
Run it against your own systems
Connect the AI client you already use and ask your first cited question — Free, Solo, Premium and Team are self-serve.
Building drone / uas compliance? It works today — we take on a few design partners per sector to tune it to your team.