CRA assistant
The CRA assistant is a compliance copilot: it is available on every dashboard page and works alongside you as you fill things in — it explains, guides and cites the articles of the Cyber Resilience Act. It runs on AWS Bedrock (Claude) and knows the context of the page you are on. It stays advisory: it orients, but it does not qualify events, compute deadlines or decide whether an obligation exists — those stay with the deterministic engine and with you. Besides answering in the chat window, it helps you write: it rephrases, summarises, translates, drafts a user notice.
The available tasks
| Task | What it produces |
|---|---|
| Rephrase | Rewrites the supplied text clearly, professionally and concisely, without adding facts. |
| Summarise | Condenses a report into a structured case summary (facts, product, potential impact), without qualifying the obligation or stating deadlines. |
| Translate | Translates between Italian and English, keeping technical terms and legal references unchanged. |
| Draft a user notice | Prepares a communication to users from the facts supplied, in a sober, non-alarming tone. |
What it will not do, by construction
- It does not set the triage verdict or the legal basis: those come out of the decision table, not out of a language model.
- It does not set or move deadlines and moments of awareness.
- It does not file, does not send communications, does not change a case state.
- It does not answer outside its perimeter: if the request is not about Cyber Resilience Act compliance and related texts, it declines.
Every answer is a draft to review: it has no legal value until a person adopts it. The legal references the model cites are checked against the corpus of guidance on the Regulation it is grounded on; citations that are not supported are flagged along with the draft.
Using it well
- Start from facts already written: paste the report, the notes, the rough draft. The assistant rewrites; it does not invent the content.
- Ask for one task at a time: the summary first, then the rephrasing of the final text.
- Read it back and correct: product names, versions, dates and legal references must always be checked.
- Move the approved text into the notification draft or the user notice.
Good practice. Use the assistant for form when time is short (translating a notice, cleaning up a text written in a hurry at three in the morning) and never for substance. Qualifying the event is the part that defends you: that one is reasoned.
Data and confidentiality
- The model, served through AWS Bedrock, receives the text you provide plus the context of the page you are working on (the section, the case or the product open). The whole registry or every product record is never sent in bulk.
- Do not paste credentials, keys, unnecessary third-party personal data or working exploits.
- Every generation leaves a row in the activity registry (task and model used), so use of the tool is traceable.
Quotas and availability
The chat window
The chat panel is available on every dashboard page and answers questions about using the product and about compliance, taking into account the context of the page you are on — the section, the case or the product open. The same perimeter and the same quotas apply. It is meant for a specific question while you work, not for extended advice: for an answer that commits somebody, there is support.