TL;DR
- Cyber Resilience Act SRP registration, step by step: create an EU Login account, set up representatives, register your manufacturer entity.
- The platform opens 11 September 2026 and there is no reporting API yet — register before you need it, not during an incident.

By now you should know which products are in scope — our free scope tool settles that in minutes — and how the CRA Single Reporting Platform fits the wider EU Cyber Resilience Act. This article adds the practical layer: it gets your organisation onto the platform before the 24-hour clock ever starts.
Access runs on EU Login
You reach the SRP through EU Login, the European Commission’s standard authentication service (formerly ECAS). In practice, each representative signs in with a personal EU Login account — and anyone on your team who has used an EU portal before may already hold one. That single account is all you need to get in; the manufacturer entity you register separately, inside the SRP itself. So set up EU Login first, and add two-factor authentication straight away.
Before your Cyber Resilience Act SRP registration: what to prepare
Do this once, calmly, and well ahead of any incident:
- Decide who holds the roles — a primary person and at least one backup. The SRP calls them Assigned Representatives (AR). Note that AR differs from an Article 18 authorised representative.
- Identify your coordinating CSIRT — the CSIRT of your main EU establishment. You pick it from a dropdown.
- Gather your manufacturer master data — legal name, registered address, and contact details.
- Read the ENISA AR registration guidance and the material on the official SRP page.
Step by step: Cyber Resilience Act SRP registration
Follow these six steps:
- Create an EU Login account for your primary representative at EU Login. Then create a second one for your backup. Set up two-factor authentication while you are there.
- Open the SRP. On first access, select your role.
- Choose your designated CSIRT from the dropdown.
- Accept the legal agreement. Then confirm the details that EU Login pre-fills.
- Register the manufacturer entity. Enter your name, address, and the remaining details.
- Invite your secondary representative by email. Send it promptly, because the link expires after 7 days.
That is the whole onboarding. Done ahead of time, it turns an incident into a login-and-file task — otherwise, you scramble to create accounts under pressure.
● The platform opens on 11 September 2026. So register before you need it, not during an incident.
First, confirm your in-scope products with our free scope tool. Then keep vulnerability handling and SRP notification prep in one workflow with our CRA compliance software, or compare the CRA compliance packages.
Filing a notification: what each stage needs
Once you register, you submit through the browser. At launch, there is no reporting API. The notification follows the staged chain from our reporting deadlines guide:
- 24-hour early warning — mandatory fields only: type and level, title and summary, manufacturer and product name, product version, the date and time you became aware, and whether you suspect a malicious act.
- 72-hour notification — add the nature of the vulnerability or exploit, plus your corrective measures.
- Final report — full description, severity, impact, and the security-update details.
Two limits also apply: a cap of 20 unvalidated notifications per manufacturer, and voluntary reporting under Article 15, which waits for a later phase. For the full chain, see our vulnerability reporting obligations guide, and for the common mistakes, read 10 reporting misconceptions.
When you may hold something back
On justified cybersecurity grounds, you may delay parts of a notification to avoid exposing users before a fix exists — the CRA Delegated Regulation 2026/881 sets out the conditions. Two things never bend, though: you cannot skip the Cyber Resilience Act SRP registration, and you cannot miss the early warning. Otherwise, you face penalties of up to €15 million or 2.5% of global annual turnover.
Why complete Cyber Resilience Act SRP registration early
ENISA published its step-by-step instructions only weeks before go-live, and as of early September 2026 the public platform URL was still pending; treat the exact screens as subject to change, and rely on the official ENISA SRP page for the live link. Do not wait on it, though — prepare your people, roles, and master data today, and a quick readiness check shows whether you can hit a 24-hour deadline. Because the SRP currently accepts submissions only through its web form and offers no API, no tool can file the report for you yet; what COMPLYD does is keep your vulnerability-handling evidence in one place and assemble a submission-ready draft, so you fill the fields above by copying from records you already hold instead of starting from scratch. Want to see it end to end? Then try our free CRA online check tool, book a demo, or read more about the team behind COMPLYD.
Frequently asked questions
What do I need to access the CRA SRP? An EU Login account, the European Commission’s authentication service. Each representative signs in with their own account, and you register the manufacturer entity separately inside the SRP.
Who should register as the representative? Name a primary and at least one backup Assigned Representative (AR). AR is a platform role, and it differs from an Article 18 authorised representative.
When can I register? The platform opens on 11 September 2026. So prepare EU Login accounts, roles, and master data in advance.
Sources: Regulation (EU) 2024/2847 (CRA) — EUR-Lex, ENISA — Single Reporting Platform, EU Login — European Commission
Related to this article
In the guide · Step 7
Meet the reporting obligations in force since 11 September 2026 →
In the guide · Step 6
Check for free
Does the Cyber Resilience Act apply to you? →
Product Check and Readiness Check, no login.
Where does your product stand on the Cyber Resilience Act?
A first answer in minutes — or see the software that turns the legal text into a workflow.
