What the EU Cyber Resilience Act (Regulation (EU) 2024/2847) means for Aster as software maintained by a company, with a dated timeline and our current state.
This is our reading of the regulation for planning. It is flagged for counsel: it is not legal advice and has not been reviewed by a lawyer. Primary source: https://eur-lex.europa.eu/eli/reg/2024/2847/oj. Check article numbers and the Commission and ENISA guidance before relying on any statement here.
Which role are we? Open-source steward or manufacturer
The CRA places the main duties on the manufacturer of a "product with digital elements" that is made available on the EU market in the course of a commercial activity. For free and open-source software it distinguishes:
| Role | Rough meaning in the regulation | Duties |
|---|---|---|
| Manufacturer | Develops or has developed a product and places it on the market under its name, in the course of commercial activity (supplying for payment, or monetising it, including charging for technical support in a way that is not only to recover costs, or using it to make a profit in other ways) | Full duties: essential requirements, conformity assessment, CE marking, technical file, vulnerability handling, reporting |
| Open-source software steward | A legal person (not a manufacturer) that systematically supports, on a sustained basis, the development of open-source products intended for commercial activities, and ensures their viability | Light-touch duties: a documented cybersecurity policy that fosters vulnerability handling and voluntary reporting, cooperation with market surveillance authorities, and reporting duties under Art. 14 to the extent the steward is involved in development |
| Open-source developer outside commercial activity | Software supplied non-commercially (for example by individuals or by a non-profit without monetisation) | Not in scope as a product |
| Integrator that embeds Aster in a commercial product | A manufacturer of their own product | Full duties for their product, including due diligence on components such as Aster |
Where Aster lands depends on facts that are not yet decided: whether Barnyard Greens LLC (and the planned spin-off) sell support, services, dual-licensed or hosted offerings around Aster, or otherwise monetise it. Planning position: the runtime is not open-source software (the source is private), so the open-source steward route is not relied on. We plan to the manufacturer duties. This is a planning assumption for counsel to confirm. We build to the stricter level because customers who integrate Aster will ask. This classification is the first question for counsel.
What our customers and integrators need
Anyone who builds a commercial product on Aster is a manufacturer of that product and must exercise due diligence on third-party components, including Aster (the regulation requires this, and requires that vulnerabilities found in a component be reported to the component's maintainer). They will ask for an SBOM, a vulnerability contact, a support period and evidence of secure development. This Trust Center is written to answer that, and the pages below map to those requests.
Obligations and where we stand
| Obligation | Where in the regulation | Our state |
|---|---|---|
| Cybersecurity policy fostering vulnerability handling (steward) | Art. 24 | Security policy and Vulnerability handling policy |
| Design, develop and produce to the essential requirements (secure by default, no known exploitable vulnerabilities at release, data minimisation, limiting attack surface) | Art. 13, Annex I Part I (manufacturer) | Largely supported by design: no data, no network in the default build (No data: what Aster does and does not do); unsafe inventory (Unsafe code policy and inventory). A formal mapping to each Annex I requirement is planned |
| Vulnerability handling: SBOM, fix without delay, regular testing, public disclosure of fixed issues, coordinated disclosure policy, contact address, secure updates | Annex I Part II | Policy in place; SBOM in Supply chain: SBOM, licences, advisories, vetting, reproducibility; mailbox [email protected] |
| Technical documentation and risk assessment kept at least 10 years or the support period | Arts. 13, 31, Annex VII (manufacturer) | Planned; this Trust Center is the seed |
| Support period of at least 5 years unless the product is expected to be used for less | Art. 13(8) (manufacturer) | See below |
| Keep security updates available at least 10 years or the rest of the support period | Art. 13(9) | Releases stay available in the release archive. |
| Report actively exploited vulnerabilities and severe incidents (24h / 72h / 14 days) | Art. 14 | Readiness table in Vulnerability handling policy |
| Conformity assessment, declaration of conformity, CE marking | Arts. 28-30, 32 (manufacturer) | Only if we are a manufacturer; see below |
| Cooperate with market surveillance authorities | Art. 24 and others | Willing; no process documented yet |
Conformity assessment and "important products"
- Products are in the default category unless listed in Annex III (important products, Class I and II) or Annex IV (critical products). Default-category manufacturers can use internal control (self-assessment) and issue the declaration of conformity.
- Annex III lists product types such as identity management systems, standalone and embedded browsers, password managers, VPNs, network management systems, operating systems, boot managers, routers, microcontrollers (Class I) and hypervisors and container runtimes, firewalls, intrusion detection systems, tamper-resistant microprocessors (Class II).
- A rendering and UI library is not, on our reading, any of those. Our working conclusion is default category. Two cautions: products that embed Aster (for example a browser) may themselves be Annex III products, which is their manufacturer's assessment; and if Aster ever ships as part of an OS shell, a browser engine or a security product, we re-check. Not confirmed by counsel or any authority.
Support period and update policy
- For any manufacturer-level product the support period must reflect expected use and be at least five years unless the expected use is shorter (Art. 13(8)). For a library embedded in long-lived products we propose five years from each major version's first release; see Support and versioning policy.
- Security updates are free and published openly during the support period, with release notes naming fixed vulnerabilities.
- Updates are signed and distributed as described in Releases: signing, provenance and verification.
SBOM
An SBOM is generated per release. Format, tooling and verification are in Supply chain: SBOM, licences, advisories, vetting, reproducibility and it is published with the release.
Timeline
| Date | What applies |
|---|---|
| 10 Dec 2024 | The regulation enters into force |
| 11 Jun 2026 | Provisions on notification of conformity assessment bodies apply |
| 11 Sep 2026 | Reporting obligations (Art. 14) apply. Already passed. They cover actively exploited vulnerabilities and severe incidents, for in-scope products including those placed on the market earlier |
| 11 Dec 2027 | Full application: essential requirements, conformity assessment, CE marking, documentation |
Source: Article 71 of Regulation (EU) 2024/2847; re-read the dates for individual provisions in the official text.
Open items
| Item | Needs |
|---|---|
| Manufacturer classification for the private-source runtime; whether free distribution is 'in the course of commercial activity' | Counsel and Barnyard Greens |
| Whether a company established outside the EU needs an authorised representative or other arrangement | Counsel |
| Confirm default-category classification, including how Annex III applies to a library | Counsel |
| Named reporting contacts and ENISA platform registration | Barnyard Greens |
| Technical file (Annex VII), if manufacturer duties apply | Engineering |
| Which entity is the maintainer after the planned spin-off | Barnyard Greens and counsel |