Practical template
CRA remote data processing boundary record
Use this template with your own product details and evidence. Copy the text into your document to complete the fields and add rows as needed.
- Product/function/revision: [fill in]
- Architecture and contracts inspected: [fill in]
| Service/software | Function lost if absent (any product function, not only the core function) | Designed/developed by or under manufacturer's responsibility? Evidence | Boundary conclusion and reviewer | External dependency risk/action |
|---|---|---|---|---|
| [fill in] | [fill in] | [fill in] | [fill in] | [fill in] |
Apply both tests in Article 3(2) of the Cyber Resilience Act (Regulation (EU) 2024/2847): would the absence of the processing prevent the product from performing one of its functions, and was the software designed and developed by the manufacturer or under its responsibility? Who hosts or operates the service does not decide the result. Identify directly interacting software; do not automatically include an entire cloud infrastructure. Record generic third party dependencies, their integration risks and the due diligence performed, even where they are outside the product boundary.
Relevant guidance: Commission guidance on the application of the Cyber Resilience Act (C/2026/6013), section 8, paragraphs 178 to 208. Actual software inventory/support owner: [fill in]. Open questions: [fill in]. Legal/security approval/date: [fill in].
Read the accompanying guide
CRA Scope for Connected Devices and Their Cloud Backends