A
Know the products
Keep product identity, availability context, and reporting inputs reviewable.
Application coming soon
ActLume will keep readiness, incident facts, human decisions, report stages, the ENISA SRP handoff, and submission evidence together in one web workspace.
The reporting path
ActLume supports each step. Authorised people make the legal decisions and use the external portal.
Record manufacturer, product, reporter, and routing details before the team is under incident pressure.
Bring the known facts together and assign ownership without treating intake as a legal conclusion.
An accountable person decides reportability and separately records the factual awareness event, actor, and basis.
Build the applicable information in stages, preserve what changed, and make review a visible step before handoff.
Open ENISA SRP and EU Login separately. The filer signs in, copies, pastes, reviews, and submits there.
Record the human-confirmed portal result, submission timing, operator, and the version of information used.
Before an occurrence
Start with the information and named responsibilities the team will need later. An incident will still bring unknowns, but basic reporting details should not be among them.
A
Keep product identity, availability context, and reporting inputs reviewable.
B
Separate application permissions, reporting responsibilities, and external designations.
C
Rehearse who reviews, who uses EU Login, and who confirms the portal result.
Who does what
ActLume will not ask for EU Login credentials, read or control the SRP page, or submit a report on someone’s behalf. It will keep the preparation and evidence workflow inside the ActLume workspace and leave authentication, portal review, and submission in the human’s hands.
An ActLume status cannot replace the portal result. The final state depends on the authorised person confirming what happened in SRP.
See the SRP handoff boundaryGo deeper