Application coming soon

Keep the CRA report moving when the incident is still unclear.

ActLume will give manufacturer security, incident, compliance, and legal teams one place to organise Article 14 reporting while people retain every legal decision and final submission.

The application is not open yet. You can use the public guides while we build it.

How the work moves

Prepare once, then keep each decision clear.

ActLume follows the reporting path a manufacturer has to coordinate. It does not make the legal decision or control the external portal.

01

Prepare

Keep manufacturer, product, reporter, and routing details ready before an incident.

02

Decide

An accountable person assesses reportability and records the factual awareness event.

03

Review

Prepare each stage, preserve revisions, and require a person to check the handoff.

04

Hand off

Copy one selected value, submit it in ENISA SRP, and record the result.

Where ActLume stops

The software organises the work. People make the call.

ActLume focuses on the work around Article 14. It is not a scanner, broad governance suite, legal adviser, or portal operator.

ActLume is being built to

  • keep case facts and human decisions distinct;
  • show the reporting stage and source status clearly;
  • support review before information leaves the workspace;
  • preserve submission evidence for later audit.

The person still must

  • decide whether the occurrence is reportable;
  • declare the factual awareness time;
  • authenticate directly with EU Login;
  • review and submit inside ENISA SRP.

Read before the app launches

Start with the question in front of you.

Read the legal overview, walk through the planned workflow, or check the security boundary. The blog covers practical reporting questions in more detail.

Next step

See where ActLume fits into your incident process.

Follow the six reporting steps