Clause 6.2 — Product context
Subclause 6.2 specifies requirements to establish and document product context under FprEN 40000-1-2:2026 and BSI TR-03183-1 Section 5.7. Product context forms the foundation for risk assessment and risk treatment.
Portal UI Path: CRA Portal → Products → [Select Product] → Assess → Product context (Clause 6.2)
Related Procedure: SOP-02: Taking a Product Through CRA Compliance
What Clause 6.2 requires
Requirements
[RMA-01-RQ-01]: Identify and document the product context:- Intended purpose and reasonably foreseeable use.
- Reasonably foreseeable misuse (Annex II: record where this creates a significant security risk).
- Product boundaries (what belongs to the product and what is external).
- Operational environment of use (networks, physical surroundings, deployment context).
- User capabilities (layman, instructed, skilled, mixed).
- Product interfaces and communication restrictions (physical, local, dedicated known network, known network, external network).
[RMA-01-RQ-02]: If the product uses a Remote Data Processing Solution (RDPS), include the RDPS in the product context.
Outputs and Assessment
- Output: Documented product context containing all required context elements (
C6.2-OUT-01). - Assessment Criteria: PASS assigned when product context exists, contains all required elements, and matches the product scope.
How CVD Portal supports compliance
CVD Portal provides structured data inputs and an artifact repository in the product Assess tab:
- Structured context data: Capture intended purpose, foreseeable use, foreseeable misuse, product boundaries, and operational environment as discrete fields.
- User capability selection: Select from standard skill levels (Layman, Instructed, Skilled, Mixed) aligned with BSI TR-03183-1 Table 7.
- Interface inventory: Add physical, local, and network interfaces with specific access restrictions (Physical, Local, Dedicated known network, Known network, External network) aligned with BSI TR-03183-1 Table 5.
- Read-only parameter links: View established support periods (Article 13(8)) and RDPS determinations (Article 3(2)) directly in context.
- Automated drafting and export: Structured fields flow directly into the
C6.2-OUT-01drafting prompt and the Annex VII technical documentation export.