Do you give us the IEC 62443 or ISO 10218 text?

Not by default — we surface 62443 and 10218 as requirement and clause mappings with Ansvar-authored cross-references, and map the requirements to your system against your licensed copy. But the standard text itself can be added: through the SIS-licensed standards module, any ISO, EN or SS standard SIS publishes can be licensed in and served cited verbatim inside your workflows; see /standards.

Is this a vulnerability scanner for OT?

No. It re-scores vulnerabilities your scanners already found, adding CISA ICS-advisory, KEV and EPSS context so OT risk decisions are reproducible and cited. It never surfaces or runs exploit code.

Sector · Industrial / OT

Industrial / OT / ICS

OT and ICS security, mapped to 62443 and enriched with live advisories.

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.

See full coverage

62443clause map, 1-1…4-2

ENISA · ANSSI · NCSCOT guidance, served verbatim

LiveCISA ICS advisories + KEV

IEC 62443 and ISO 10218 are surfaced as requirement and clause mappings with Ansvar cross-references — never the reproduced standard — alongside the EU Machinery Regulation at article level. What the agencies publish, we serve as text: the ENISA ICS-SCADA good practices, the ANSSI industrial-system guides, the UK NCSC operational-technology guidance, the NIST SP 800-82r3 OT overlay and the DOE C2M2 maturity model. Live CISA ICS advisories enrich your CVEs with exploitation context so an OT TARA runs on what is actually being attacked.

what we cover

The law and standards we ground on

Standard

Control mapping: IEC 62443 (1-1…4-2)

IACS-security requirement/clause mapping + cross-refs into NIST 800-82r3, ATT&CK for ICS — not the standard text

Standard

Control mapping: ISO 10218-1/-2:2025 + the safety-security bridge

robot & robot-cell clause mapping, not the standard text

Standard

OT protocol security models: Modbus/TCP, DNP3, OPC UA, PROFINET, EtherNet/IP (CIP), IEC 61850/62351, BACnet/SC

77 protocol-hardening requirements as clause-map metadata + Ansvar guidance, cross-referenced to NIST SP 800-82r3 — not the reproduced standard text

Standard

NIST SP 800-82r3 — the OT overlay

the Appendix F control-tailoring layer served verbatim: per-control OT applicability, compensating controls and parameter tailoring; the prose guide chapters are not in the corpus

Standard

DOE C2M2 v2.1

356 maturity practices across ten domains, each tagged MIL1-MIL3, served verbatim

Regulation

EU Machinery Regulation (EU) 2023/1230

article-level (applies 2027-01-20)

Regulation

Cyber Resilience Act · NIS2

Guidance

ENISA OT / ICS-SCADA good practices

served verbatim under the ENISA reuse notice — smart-manufacturing IoT security, ICS/SCADA communication dependencies, maturity levels in critical sectors and the secure IoT supply chain

Guidance

ANSSI industrial-system security guides

served verbatim under Etalab v2.0 — the classification method (PA-107), the detailed measures (PA-108), the detection doctrine (PA-084) and the industrial-IoT approach (PG-109)

Guidance

UK NCSC operational-technology guidance

served verbatim under OGL v3.0 — secure connectivity principles, the definitive OT architecture view, cloud-hosted SCADA, secure RF communications and privileged access workstations

Guidance

CISA ICS/OT advisories

mapped to CVEs + affected products, enriched with CISA KEV / EPSS / NVD

what you can do

Workflows that turn it into evidence

Premium

OT / ICS threat model

STRIDE over a zones-and-conduits model, grounded in the IEC 62443 clause map

assembledPremium

Robot-cell TARA

scoped to a robot or cobot cell off the ISO 10218 / safety-security-bridge clause map — an available analysis, not a legally-assured verdict

Team

IEC 62443 zone & conduit gap analysis

configured to the 62443 clause map

assembledTeam

C2M2 maturity-scored OT gap analysis

the DOE C2M2 practices at MIL1-MIL3 over your OT programme — assembled from the served practice text and the gap-analysis workflow

Premium

EU Machinery Regulation gap analysis

Annex III essential-H&S coverage incl. the conformity route — a gap analysis, never a conformity verdict

Team

NIS2 gap analysis for OT/ICS operators

Directive (EU) 2022/2555 Art. 21

Team

ICS-advisory-enriched CVE rescoring

re-rank OT vulnerabilities by CISA KEV, EPSS and ICS-advisory context instead of raw CVSS

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

Do you give us the IEC 62443 or ISO 10218 text?: Not by default — we surface 62443 and 10218 as requirement and clause mappings with Ansvar-authored cross-references, and map the requirements to your system against your licensed copy. But the standard text itself can be added: through the SIS-licensed standards module, any ISO, EN or SS standard SIS publishes can be licensed in and served cited verbatim inside your workflows; see /standards.
Is this a vulnerability scanner for OT?: No. It re-scores vulnerabilities your scanners already found, adding CISA ICS-advisory, KEV and EPSS context so OT risk decisions are reproducible and cited. It never surfaces or runs exploit code.

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.

Setup guide

Building industrial / ot compliance? It works today — we take on a few design partners per sector to tune it to your team.