Skip to product information
1 of 3

Svenska Dokumentmallar

CRA 2027 – vulnerability reporting for security researchers, CVD policy and contact log | Word/PDF/Excel

CRA 2027 – vulnerability reporting for security researchers, CVD policy and contact log | Word/PDF/Excel

File format
DOCX, PDF, XLSX
Document language
Five Swedish CVD operating procedures and a Swedish user guide in DOCX/PDF; separate English User Guide in DOCX/PDF. A Swedish XLSX with exactly nine tabs. The English guide is not English operating templates.
Number of files
7

Digital download. No physical product is shipped.

Regular price 449 SEK
Regular price Sale price 449 SEK
Sale Sold out
Taxes included.
View full details

About this template

How should a security researcher report a suspected vulnerability in your software or connected product – without the report ending up with the wrong person or being published before it can be addressed? This specialist package helps manufacturers of products with digital elements create a clear, secure, and traceable workflow for Coordinated Vulnerability Disclosure (CVD): public policy, point of contact, intake form, researcher confirmation, coordinated publication, and documented evidence.

Important legal timeline: The Cyber Resilience Act, Regulation (EU) 2024/2847, will apply primarily from 11 December 2027. However, manufacturers’ Article 14 reporting obligations for actively exploited vulnerabilities and serious product-related security incidents apply already from 11 September 2026. The package therefore separates future CVD product and process controls from a potentially already applicable obligation to report to the competent CSIRT and ENISA. European Commission legal timeline · EU reporting rules.

Product core: Annex I, Part II, points 5–6 require a policy for coordinated public disclosure and measures that facilitate the reporting of discovered vulnerabilities, such as a contact address. Annex II, point 2 refers to a single point of contact in the product’s user information, as well as information on where the CVD policy can be found. The manufacturer’s process and responsibilities must be assessed according to Article 13 and the actual scope of the product. Read the official CRA Regulation.

Delivery: 15 files in a digital ZIP: 7 editable Word (DOCX) files, 7 corresponding searchable and printable PDFs, and 1 Swedish Excel workbook (XLSX) with exactly nine tabs and ten tested status counters. Five Swedish operational templates, a Swedish user guide, and a separate English User Guide. The PDF files do not have interactive form fields; changes are made in Word. Compatible DOCX/PDF/XLSX software is required.

01. Package contents

Five independent Swedish CVD working documents, a Swedish user guide, and a separate English User Guide, all seven in editable DOCX and corresponding searchable PDF – 14 document files in total. In addition, a Swedish Excel register with nine tabs and ten administrative counters. 15 customer files in total in the ZIP. The English guide does not translate the five main templates.

02. What the files contain

Customizable publishable reporting policy; which products and versions are covered; limitation of permitted security testing; actual secure reporting address; arrival time and report ID; the researcher’s limited technical findings; confirmation letter and request for additional information; handling of vulnerabilities in third-party components; CVE and publication coordination; separate Article 14 escalation decisions; actual contact, release, and publication evidence.

Who needs the package?

For manufacturers, product owners, PSIRTs, security officers, development managers, and legal/compliance functions at companies that provide software, IoT equipment, and other products with digital elements on the EU market. The package also helps organizations that want to introduce a voluntary, professional intake channel before all CRA process requirements have come into effect.

Not automatically applicable to all digital services: The applicability of the CRA depends on the nature of the product, the role of the operator, and the market flow. A website or cloud service alone does not make a company a CRA manufacturer. Perform the applicability assessment before claiming an obligation.

How does this product differ from CRA PSIRT?

The CRA PSIRT – vulnerability intake, 24/72h reporting, and chain of custody in the template store focuses on concrete incident and vulnerability triage, as well as reporting to authorities. CRA component supplier – SBOM, supplier notification addresses the product’s underlying component chain.

This package is the external, public entry point for researchers: policy on the website, acceptable testing boundaries, secure point of contact, standardized report responses, coordinated publication, and actual channel testing. If a report shows active exploitation or a serious security incident, it must be immediately referred for separate CRA Article 14 assessment; the public CVD process does not replace the report.

File list – document by document

File Practical purpose Language Format
01. Public CVD policy and point of contact Editable text for a security reporting page, with actual product scope, contact, testing boundaries, and cautious researcher terms. Swedish DOCX + PDF
02. Researcher vulnerability report Report form for product version, reproduction steps, limited technical evidence, and secure transmission. Swedish DOCX + PDF
03. Intake response and request for additional information Intake confirmation, clarification, status message, duplicate reports, and factual rejection notices. Swedish DOCX + PDF
04. Coordinated publication Risk and version assessment, third-party supplier, CVE/CNA, publication time, and actual patch/customer information. Swedish DOCX + PDF
05. Channel testing and CRA escalation Verification of an actually functioning point of contact and a separate decision on Article 14 reporting. Swedish DOCX + PDF
06. Swedish user guide Seven steps, three researcher scenarios, legal timeline, and clear policy boundaries. Swedish DOCX + PDF
07. English User Guide English instructions for the five main Swedish documents. Not operational templates in English. English DOCX + PDF
08. Excel – CVD and report register Nine tabs for products, researcher reports, points of contact, triage, coordination, publication, evidence, and Read Me. Ten administrative counters. Swedish XLSX

The Excel register – nine tabs, ten verified indicators

Overview, Products, Reports, Contacts, Triage, Coordination, Publication, Evidence, and Read Me. The dashboard compiles registered products, sourced CRA scope, actually received researcher reports, technically validated reports, separate Article 14 escalation with an authority reference, tested reporting channels, sent researcher responses, contact with component owners, proven published fixes, and open critical triage items.

How the controls work: a status of “Received” or “Validated” is only counted as verified when relevant evidence IDs and named responsible parties are present. A publication decision requires an actual URL, patch evidence, and review evidence. All ten formulas have been tested with an empty register, status without evidence, and complete fictitious data. The test data has since been cleared. Excel does not determine whether a vulnerability is exploitable, reportable, or technically remediated.

Practical workflow: from researcher tip to publication

  1. Establish CRA responsibility: identify the correct product, version, manufacturer, support period, and any component suppliers.
  2. Publish a true CVD policy: specify an actual secure point of contact, covered systems, permitted testing boundaries, and expected contact methods. Test the channel before publication.
  3. Receive the report: create a case ID, register the product and time, minimize personal data, and store technical evidence in an authorization-controlled system.
  4. Validate professionally: have a competent team assess reproduction, risk, impact, and any actual active exploitation.
  5. Assess authority reporting separately: assess existing Article 14 requirements without waiting for a contractually agreed CVD publication date.
  6. Coordinate communication: involve affected component owners, manage any CVE/CNA process, remediate, test, and inform users when required.
  7. Conclude with actual evidence: save the researcher’s intake evidence, actual patch version, publication link, dispatch, and documented decision.

“Safe harbour” is not a legal guarantee

A CVD policy may express that the company appreciates security research in good faith and wants to cooperate with reporters. However, it cannot automatically provide statutory immunity, the right to intrude, the right to test third-party systems, or an unlimited right to handle customer data. Adapt the text based on legal and technical assessment. ENISA has published an example of a responsible reporting policy for inspiration. ENISA’s policy.

No fabricated service promises: this product does not imply that a company has 24-hour staffing, an encrypted portal, an active PGP key, a paid bug bounty, or a binding response time. All such information is intentionally editable and should be filled with actual data only after review.

Frequently asked questions

Must a company have a CVD policy in 2026?

The CRA’s general product and vulnerability process requirements apply primarily from 11 December 2027. Article 14’s separate reporting obligation, however, applies from 11 September 2026. Introducing the intake channel before 2027 may be appropriate but should not be sold as a mandatory 2026 policy for everyone.

Is this the same as a PSIRT incident report?

No. The product handles the public researcher contact and coordinated publication. A report to ENISA/CSIRT via the Single Reporting Platform is a separate, actual event.

Do the Word and Excel files create a functioning web portal?

No. The customer receives text, process forms, and registers. A secure website, email address, encryption, and access control must be configured and tested separately.

Can we promise security researchers full immunity from prosecution and damages?

No. Such general guarantees are not provided. The relationship to good faith, permitted testing area, national law, and third-party rights must be investigated, and the policy text reviewed.

Must all received researcher tips be reported to ENISA within 24 hours?

No. Article 14 has specific triggering conditions. An unconfirmed researcher report is not automatically an actively exploited vulnerability or a serious security incident. Actual indications must, however, be assessed promptly.

Can we use a regular unprotected Excel workbook for exploits and personal data?

This is not recommended. The Excel register is intended for minimal case references and evidence IDs. Sensitive material should be handled in an actual access- and privacy-protected system.

Are English templates and fillable PDF files included?

The five operational templates are Swedish, with a separate English User Guide. The PDF files are searchable and printable but lack interactive form fields; DOCX is editable.

Official sources and quality control

EU Regulation (EU) 2024/2847, especially Article 13, Article 14, Annex I Part II, and Annex II · European Commission: CRA implementation date · European Commission: reporting obligations · ENISA: example of a responsible disclosure policy.

Version 1.0 · AI-assisted legal source review 17 November 2026. DOCX, PDF, XLSX, and ZIP have been tested. No external legal review, actual vulnerability testing, portal deployment, verification of contact address, CVE assignment, or authority reporting has been performed. The templates are support for document management, not evidence of actual CRA compliance.