Resources

Insights for product security and compliance

News from ARIANNA, practical articles on vulnerability management and the CRA, and straight answers to the questions device manufacturers ask us most.

News & articles

Latest from ARIANNA and our partners

Article · Vulnerability management · 5 Nov 2026

The refrigeration systems behind the attacks: known vulnerabilities, ignored security advisories?

Which Copeland/Dixell and Danfoss controllers had known vulnerabilities, and which security advisories had been published before the October 2026 attacks.

Read the article →
Article · Product security · 3 Nov 2026

When cyberattacks become physical: lessons from the supermarket refrigeration attacks

Attacks on refrigeration controllers in France and across Europe show how a compromised connected product becomes a physical and economic problem, and what the CRA asks of manufacturers.

Read the article →
Logic Technology
News · Partnership · 19 Sep 2026

ARIANNA announces new partnership with Logic Technology

Logic Technology adds ARIANNA to its portfolio, giving Benelux engineering teams a single workspace for SBOM/HBOM management, continuous vulnerability monitoring and CRA compliance reporting.

Read the news →
Security Pattern
News · Press release · 1 Aug 2026

Security Pattern spins out ARIANNA as an independent company

From 1 August 2026, ARIANNA operates as an independent company focused on vulnerability management for connected products. Security Pattern remains a shareholder and partner.

Read the news →
COMPLYD
News · Partnership · 29 May 2026

ARIANNA announces new partnership with COMPLYD

COMPLYD joins the ARIANNA partner ecosystem to connect Cyber Resilience Act governance with technical SBOM, HBOM and vulnerability management capabilities.

Read the news →
Estigiti
News · Partnership · 27 May 2026

ARIANNA announces new partnership with Estigiti

Estigiti joins the ARIANNA ecosystem as an implementation and advisory partner, supporting vulnerability management, SBOM and HBOM practices, and CRA readiness.

Read the news →
REEKON
News · Partnership · 11 May 2026

ARIANNA expands into Asia through new partnership with REEKON

REEKON joins the ARIANNA ecosystem as an official implementation partner for the Asian market, supporting connected device manufacturers across Singapore, Taiwan, India and Hong Kong.

Read the news →
Article · CRA & regulation · 6 May 2026

CRA's 24-hour exploit reporting rule is going to expose a major industry problem

Why the CRA's 24-hour reporting rule will test manufacturers' ability to determine vulnerability relevance, exploitability and reportability fast enough.

Read the article →
Article · SBOM · 16 Mar 2026

Why SBOM alone is not enough for IoT security

SBOM is essential, but real vulnerability management for devices requires hardware context, exploitability insight and lifecycle tracking.

Read the article →
Questions & answers

What device manufacturers ask us

Can't find your question? Ask in the chat, or book a free demo and we'll discuss it with you.

Book a free demo

The platform

What is ARIANNA?

A SaaS platform that enables device manufacturers to implement an efficient & effective vulnerability management process. ARIANNA builds a comprehensive model of each device combining its SBOM, HBOM and security context. It continuously monitor new vulnerabilities, enriches vulnerability data with proprietary intelligence, prioritises relevant risks, guides your triage and remediation activities, and provides the evidence needed to demonstrate compliance with the CRA, RED and your customers requirements.

Where is our data hosted?

In the European Union. With the Enterprise plan you also get a dedicated instance of the platform.

SBOM & HBOM

What is a Device Model?

A model of your device that contains the list of hardware & software components, and the information relevant to its security context. It is organised by Processing Unit: for each one, the hardware (HBOM) and then the operating system and software layers on top of it (SBOM).

Do I need a Device Model for every unit we ship?

No. You create one Device Model per device design, whether you ship one unit or a thousand. Each new firmware release becomes a new version of the same model.

Which software stacks are supported?

Microcontroller firmware (bare-metal and RTOS, including Zephyr and the main silicon vendor SDKs), Embedded Linux (Yocto, Buildroot, OpenWRT, Debian, RedHat and more), Windows, Android, applications in common languages, and cloud and container environments. See the full list of supported environments on the Platform page →

Do we need to provide a ready-made SBOM?

No. ARIANNA provides a wide set of its own SCA tools, one for each software stack, that create the SBOM straight from your build.

Do we have to share source code or binaries?

No. ARIANNA's SCA tools run in your own build environment and only send the component list (vendor, name, version and, where available, licences, patches and dependencies). There is no reverse engineering of binaries.

Do we need to install agents on our devices?

Nothing is installed on your devices. No agents, no additional software to maintain in the field, and no risk of disrupting, interfering with or limiting their normal operation. No false alarms caused by intrusive monitoring. No device-side updates to manage.

Do our devices need to be connected to ARIANNA?

No. The vulnerability assessment report is produced from the Device Model (your HBOM and SBOM), not from the devices themselves. Nothing in the field connects to ARIANNA.

Can we automate SBOM updates in our CI/CD pipeline?

Yes. The SCA tools are lightweight Python, Bash or PowerShell scripts that can be easily integrated as final stage of your CI/CD pipeline. Run them after each release, update an existing Device Model by uploading the SCA Tools output through the REST API provided by ARIANNA, and a new assessment starts automatically.

How is the HBOM created?

You can build a list of relevant hardware components through a guided process in the ARIANNA web interface. Simply select the hardware vendor and part number from ARIANNA's hardware catalogue, and the platform automatically enriches each component with additional technical details, such as internal cores, GPUs and other hardware characteristics.

Vulnerability management

Which vulnerability sources do you monitor, and how often?

ARIANNA maintains an internal vulnerability intelligence database, updated daily with new findings from authoritative sources (including NIST NVD, CVE.org, GitHub Security Advisories and ENISA's European Vulnerability Database (EUVD))and security advisories published by major silicon vendors. Each finding is enriched with proprietary intelligence, including information on known exploitation in the wild, evidence from authoritative exploitation-tracking sources (such as the CISA KEV and ENISA KEV catalogues) and internet-deployed honeypots, exploit availability and maturity levels, and EPSS scores. This additional context enables more accurate vulnerability prioritisation and better-informed remediation decisions.

How do you keep false positives down?

Accurate SBOMs from the build are the first step. ARIANNA then discards findings automatically when the affected version is no longer present, the component was updated or patched, the functionality is not in use, or the source re-evaluated the vulnerability.

How are vulnerabilities prioritised?

The ARIANNA pre-triage engine automatically marks each open vulnerability High or Low priority using rules you configure, by risk, by exploitability (KEV, exploits, EPSS, attack vector exposure) or both. 

What happens when we release a new firmware version?

You create a new version of the Device Model. Your triage work carries over, vulnerabilities in updated, patched or removed components close automatically, and new components are checked straight away.

Can we manage vulnerabilities found in our own pentests?

Yes. Add vulnerabilities from penetration tests, code reviews or responsible disclosure by hand, and manage them in the same workflow as everything else.

Compliance

How does ARIANNA help with the Cyber Resilience Act?

It covers the vulnerability-handling side of the CRA: an SBOM for every version, monitoring for the whole support period, prioritised remediation with deadlines, and an auditable record of every decision, exportable as CycloneDX, SPDX, VEX or PDF. Learn more about the CRA and ARIANNA →

Does ARIANNA help with the 24-hour reporting obligation?

ARIANNA flags vulnerabilities that others, such as other manufacturers reporting to ENISA, have found to be actively exploited, so you can check and prioritise them in your own products straight away. Detecting that your own product is being exploited needs your own sources, such as customer reports, incident response or field monitoring. 

Is ARIANNA relevant for the RED Delegated Act?

Yes. It provides the vulnerability assessment and risk-management evidence for radio equipment, and the same process carries over to the CRA.

Can we get help with compliance beyond the platform?

Yes. Partners in the ARIANNA ecosystem offer consultancy for product security and compliance. Meet our partners →

Plans & getting started

Which plan is right for us?

We offer three flexible licensing models to match your business needs, ranging from on-demand assessments to continuous monitoring of your entire product portfolio. Compare the plans → For more information, contact us.

Does ARIANNA integrate with our tools?

Yes. ARIANNA provides a REST API to integrate  your AI agents, your ticketing system ( Jira, Redmine and GitHub), as well as to automate SBOM generation and updates through your CI/CD pipelines.

How do we get started?

Book a free demo or contact us. In the demo we show you the platform and its features, and discuss your devices, your technology stack and the regulations that apply to them.

Documentation & contact

User manualConcepts, workflows and every feature of the platform.Open the manual → ContactQuestions about ARIANNA, partnerships or press.hello@ariannateam.ai →