This page provides information on the Assigned Representatives (AR) submission and update of notifications in the SRP. It is intended for AR users (Primary and Backup).
The information on this page is provided according to our current best knowledge and may be subject to change. Please ensure you consult the latest available guidance before applying these instructions.
Submit New Notification
Purpose: Follow these steps to submit a new notification for an Activly Exploited Vulnerability (AEV) or Severe Incident (SI). The purpose of the notification is to inform the recipient designated CSIRT users for review, dissemination and further processing.
Pre-conditions: your user status is “Active” and you are logged in into the SRP.
Submit Early Warning
Steps
- Click on “Submit new notification” in the Dashboard page. A new notification will be automatically created and pre-filled with the user's type (AR).
- Fill in the mandatory fields and any optional fields to describe the notification in the Early Warning tab.
- Select an existing Manufacturer (approved or pending verification) or add one
- Ater filling the required and optional fields, submit the notification or save it as a Draft.
Notification successfully submitted:
The notification is listed in the Dashboard. Before CSIRT validation:
After CSIRT validation:
Exceptions: If you omit mandatory data, the SRP will return an error informing you which data are missing and need to be provided.
Submit 72h Notification
Pre-condition: An Early Warning has already been submitted.
Steps
- Click on an existing notification in the Dashboard page.
- Fill in the mandatory fields and any optional fields to describe the notification in the 72h Notification tab.
- Finally, you can submit the notification or save it as a Draft.
The notification is listed in the Dashboard (to be validated by the CSIRT):
Exceptions: If you omit mandatory data, the SRP will return an error informing you which mandatory data are missing and need to be provided.
Submit Final Report
Pre-conditions: An Early Warning and a 72h Notification have already been submitted.
Steps:
- Click on an existing notification in the Dashboard page.
- Fill in the mandatory fields and any optional fields to describe the notification in the Final Report tab.
- Finally, submit the Final Report or save it as a Draft
Exceptions: If you omit mandatory data, the SRP will return an error informing you which mandatory data are missing and need to be provided.
When all the Reports have been submitted, the bar on the top of the notification will display the <Accomplished Icons> next to each step submitted.
Expected results:
Draft: the state of a saved draft notification is updated to "Draft". The draft is stored in the National Endpoint Data Layer and is visible only by you
Early Warning: the notification is stored in the SRP National Endpoint Data Layer (of the designated CSIRT). The notification is sent to the designated CSIRT. An email and alert will be sent to the designated CSIRT. An email and alert will be sent you, confirming the notification submission. An email and alert will be also sent to the ENISA automatically. The state of a successfully submitted notification is updated to "EW Submitted". The state of a successfully submitted notification is updated to “Early Warning”.
72h Notification: the state of a successfully submitted notification is updated to "72h Submitted". The dissemination state of a notification under Particularly Exception Circumstances (PEC) is updated to "72h under PEC ". An email and alert will be sent to the ENISA and Concerned CSIRTs with Particularly Exception Circumstances reasons. Recipients (Concerned CSIRTs and ENISA) will receive them if the Early Warning is disseminated to them. ENISA automatically receives the 72h Notification only if Particularly Exception Circumstances are not raised.
Final Report: the state of a successfully submitted notification is updated to "FR Submitted". Concerned CSIRTs will receive the Final Report only after manual full dissemination by CSIRT Designated as Coordinator. The system automatically determines the report that has been submitted. The substate of a successfully submitted notification is updated to “Final Report” for Final Report notifications. ENISA automatically gets the Final Report only if Particularly Exception Circumstances are not raised.
Update Existing Notification
Purpose: Follow these steps to update an existing notification for an Actively Exploited Vulnerability or a Severe Incident.
Pre-conditions:
- Your user is “Active” and you are logged in into the SRP
- A notification have been previously submitted or saved as a draft
- Notification is not closed - closed notifications cannot be updated
- Final Report is not submitted - the notification becomes non‑editable after the submission of a Final Report
- You have opened the details of the notification
Steps
- Open a notification and update the necessary fields in the Notification
- Click on ‘Update’ to save the updated notification information
Exceptions: If you omit mandatory data and click on “Update”, the SRP will return an error informing you which mandatory data are missing and need to be provided
- The SRP automatically notifies the designated CSIRT via an alert
- The SRP automatically notifies ENISA, and the concerned CSIRTs that received the notification through dissemination, via an alert
Expected result:
- For Several Incidents Notifications (regardless of the Notification state):
- If the Notification has not been yet disseminated by the Designated CSIRT, the updated notification data (all fields) are automatically stored only in the SRP National Endpoint Data Layer and remain only visible to the designated CSIRT
- If the Notification is already disseminated to all the concerned CSIRTs by the designated CSIRT, the updated notification data (all fields) are automatically stored in the SRP ENISA Master Data Layer and is automatically made visible to ENISA and the concerned CSIRTs
- For Actively Exploited Vulnerability Notifications:
- If the Notification has not been yet disseminated by the Designated CSIRT, the updated notification data (all fields) are automatically stored only in the SRP National Endpoint Data Layer and remain only visible to the designated CSIRT
The state of a successfully submitted notification is updated to "Submitted". An email and an alert will be sent to you to inform of the update. An email and an alert will be sent to the recipient of the notification (designated CSIRT, and any additional involved parties, if the notification has been disseminated to them) to inform them for the update.
In case the update was cancelled, or mandatory fields were not provided, the information is not stored in the system.