SRP paste pack

CRA reports are filed in ENISA’s Single Reporting Platform (SRP). The SRP has no API and takes English only, so each report is typed or pasted in by hand, inside the deadline. The SRP pack tab prepares each report’s fields from what Pharus knows about the incident, in English, ready to copy, and leaves the few only you can answer for you to write. “Pharus never files for you. Copy each field into the SRP, then record the receipt.”

​

Before your first filing

The SRP only takes filings from named people with EU Login. Under Settings → Company, the card Ready to file in ENISA’s SRP records who can file: a Primary assigned representative, Deputies, whether each has EU Login with two-step verification and access to the SRP, and whether the CSIRT has verified the company in the SRP, “so whoever is on call knows who to call.” Owners and admins edit it. Check the route too: the pack shows the CSIRT your reports go to.

​

The three reports

The tab has one pack per report: Early warning, Notification and Final report. It opens on the first one that isn’t submitted yet. The card title says which you are looking at, for example “SRP pack · Early warning”, with the badge “SRP is English-only”.

​

Field mapping

Each field shows its label, its SRP reference (such as SRP · 1.1) and a Copy button. Which fields a report needs depends on the kind of incident (CRA Art. 14(2) and 14(4)). “Both” means an actively exploited vulnerability and a severe incident.

​

Where the values come from

A required field that is empty shows Missing, and the pack counts them, for example “2 required fields are empty”. Better details on the incident give a better pack: edit them on the Overview tab and the pack follows.

​

Copy the pack into the SRP

​

Edit the pack

Select Edit pack to change any field. “Your text replaces the auto-filled value. Clear a field to use the auto-filled value again.” Use auto-filled value puts Pharus’s text back. Select Save pack. An edited field shows Edited in the pack. Any member can edit a pack until its report is marked as submitted. After that: “A submitted pack can’t be edited. Void the filing to change it.”

​

Mark a report as submitted

Select Mark as submitted. The dialog shows:

• Warnings, if any: a report that comes earlier isn’t marked as submitted yet (“You can still file this report.”), the final report of an exploited vulnerability has no fix recorded, or required fields are empty.
• Recipient: the CSIRT from the route, such as ”→ NCSC-FI via SRP”, or “Route not settled. Check the Routing tab.”
• Submitted at (Oslo time): when you filed in the SRP. It defaults to now and can’t be in the future.
• Note: optional.

When you confirm, Pharus keeps a snapshot of the values in the pack, and the tab then shows “Showing the values as submitted” with the time: exactly what was filed, even if the incident changes later. The report’s clock shows Submitted, and for a severe incident the notification’s time starts the final report clock. See Reporting clocks.

​

Record the receipt

When the SRP confirms the report, select Record receipt. Enter the Receipt reference the SRP gave you (for example SRP-2026-000118) and Received at (Oslo time). The pack then shows, for example, “Receipt SRP-2026-000118 recorded”.

​

Void a filing

If you marked a report as submitted, or recorded a receipt, by mistake, select Void filing and give a Reason of at least 3 characters. “Steps back the last action on this report: the receipt first, then the submission. The voided action stays in the audit trail.” Once the submission is voided, the pack can be edited again and the clock runs against its original deadline.

​

What is logged

Every filing action goes into the incident’s audit trail with who did it and when: Edits to the pack aren’t logged one by one: the snapshot taken when you mark the report as submitted is the record of what was filed. See Audit trail.

​

Related