A
Know your products
Product identity, availability, and reporting inputs, ready for review.
ActLume workflow
The product design brings facts, decisions, drafts, and submission evidence into one workspace while people retain the legal decisions and external submission.
The reporting path
The workflow model supports each step while authorised people make the legal decisions and use the external portal.
Company, products, reporters, and routing details, captured while things are calm rather than mid-incident.
Pull the known facts together and give the case an owner. Logging it is not yet a legal conclusion.
Decide whether it is reportable, and record when you became aware, who decided, and on what basis.
Build the early warning, notification, and final report as versions, and get sign-off before handoff.
Your filer opens ENISA SRP in its own tab, signs in with EU Login, copies each value across, reviews, and submits.
Record what the portal said, when it was submitted, who submitted it, and which version of the report was used.
Before an occurrence
Sort out the basics and the named responsibilities now. An unclear incident is much easier to handle when the reporting details are already settled.
A
Product identity, availability, and reporting inputs, ready for review.
B
Who can use the workspace, who owns the reporting duties, and who is named externally.
C
Rehearse who reviews, who uses EU Login, and who confirms the portal result.
Who does what
Your filer holds the EU Login credentials, reviews the portal, and submits. The product scope covers drafting, internal review, a value-by-value handoff, and submission evidence.
What the portal says is what counts. Your filer records that result against the case.
See the SRP handoff boundaryGo deeper