System Requirements
Internal supplier system requirements generated from customer requirements, with coverage, verification, and quality checks.
System Requirements
Internal supplier system requirements generated from customer requirements, with coverage, verification, and quality checks.
System Requirement Decision Impact
Downstream engineering artifacts remain provisional until customer clarification closure evidence is complete.
Decision Control Status Options
| Status | Meaning |
|---|---|
| VALIDATED | Customer decision and evidence basis are sufficient for downstream use. |
| ASSUMPTION BASED | Requirement can be reviewed, but customer confirmation is still pending. |
| BLOCKED BY CUSTOMER DECISION | Requirement must not be treated as baseline-mature until customer decision closes. |
| SECURITY DECISION OPEN | Requirement depends on unresolved cybersecurity weak-area confirmation. |
Search and Filters
System Requirement Register
This table is horizontally scrollable. Use the bottom scrollbar to view all columns.
| System Requirement ID | Statement | Coverage Count | Linked Customer Requirement IDs | Rationale | Verification Method | Acceptance Criteria | Priority | Category / Domain | Implementation Notes | Open Questions | Decision Control Status | Validation |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| SSR-CON-001 | The supplier shall produce and maintain the cybersecurity concept and verification evidence covering Security evidence and traceability (Cybersecurity domain; allocated to Security Services; security capability: Cybersecurity requirement handling; interface: OEM/Customer Review Interface). | 4 | RFQX-1001379436-P10-000-01-0007; RFQX-1001379436-P10-000-01-0017; RFQX-1001379436-P10-000-01-0018; RFQX-1001379436-P10-000-01-0019 | Clustered from 4 customer requirements allocated to 'Cybersecurity Concept and Evidence' / 'Security evidence and traceability' (e.g. RFQX-1001379436-P10-000-01-0007, RFQX-1001379436-P10-000-01-0017, RFQX-1001379436-P10-000-01-0018 …). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Security evidence and traceability satisfies the linked customer requirement set and records any open customer assumption. | Medium | Cybersecurity Concept and Evidence | Security evidence and traceability | None | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-1001379436-P10-000-01-0007; RFQX-1001379436-P10-000-01-0017; RFQX-1001379436-P10-000-01-0018; RFQX-1001379436-P10-000-01-0019 Broad coverage justification: No exception justification recorded. |
| SSR-VIH-001 | The supplier shall support vulnerability monitoring and incident handling for Vulnerability and Incident Handling over the defined lifecycle, including field updates (Cybersecurity domain; allocated to Security Services; security capability: Vulnerability management; interface: OEM/Customer Review Interface). | 2 | RFQX-1001379436-P10-000-01-0008; RFQX-1001379436-P10-000-01-0048 | Clustered from 2 customer requirements allocated to 'Vulnerability and Incident Handling' / 'Vulnerability and Incident Handling' (e.g. RFQX-1001379436-P10-000-01-0008, RFQX-1001379436-P10-000-01-0048). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Vulnerability and Incident Handling satisfies the linked customer requirement set and records any open customer assumption. | Medium | Vulnerability and Incident Handling | Vulnerability and Incident Handling | None | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-1001379436-P10-000-01-0008; RFQX-1001379436-P10-000-01-0048 Broad coverage justification: No exception justification recorded. |
| SSR-CON-002 | The supplier shall produce and maintain the cybersecurity concept and verification evidence covering Cybersecurity Concept and Evidence (Cybersecurity domain; allocated to Security Services; security capability: Cybersecurity requirement handling; interface: OEM/Customer Review Interface). | 12 | RFQX-1001379436-P10-000-01-0012; RFQX-1001379436-P10-000-01-0013; RFQX-1001379436-P10-000-01-0015; RFQX-1001379436-P10-000-01-0024; RFQX-1001379436-P10-000-01-0027; RFQX-1001379436-P10-000-01-0037; RFQX-1001379436-P10-000-01-0044; RFQX-1001379436-P10-000-01-0045; RFQX-1001379436-P10-000-01-0046; RFQX-CVS123-2-0196; RFQX-CVS123-2-0201; RFQX-CVS123-2-0243 | Clustered from 12 customer requirements allocated to 'Cybersecurity Concept and Evidence' / 'Cybersecurity Concept and Evidence' (e.g. RFQX-1001379436-P10-000-01-0012, RFQX-1001379436-P10-000-01-0013, RFQX-1001379436-P10-000-01-0015 …). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Cybersecurity Concept and Evidence satisfies the linked customer requirement set and records any open customer assumption. | High | Cybersecurity Concept and Evidence | Cybersecurity Concept and Evidence | None | BLOCKED BY CUSTOMER DECISION | TOO BROAD SYSTEM REQUIREMENT DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-1001379436-P10-000-01-0012; RFQX-1001379436-P10-000-01-0013; RFQX-1001379436-P10-000-01-0015; RFQX-1001379436-P10-000-01-0024; RFQX-1001379436-P10-000-01-0027; RFQX-1001379436-P10-000-01-0037; RFQX-1001379436-P10-000-01-0044; RFQX-1001379436-P10-000-01-0045; RFQX-1001379436-P10-000-01-0046; RFQX-CVS123-2-0196; RFQX-CVS123-2-0201; RFQX-CVS123-2-0243 Broad coverage justification: No exception justification recorded. |
| SSR-CON-003 | The supplier shall produce and maintain the cybersecurity concept and verification evidence covering Security evidence and traceability (Software domain; allocated to Application Software; interface: OEM/Customer Review Interface). | 1 | RFQX-1001379436-P10-000-01-0021 | Clustered from 1 customer requirements allocated to 'Cybersecurity Concept and Evidence' / 'Security evidence and traceability' (e.g. RFQX-1001379436-P10-000-01-0021). | Review + Test | Review + Test evidence demonstrates that Security evidence and traceability satisfies the linked customer requirement set and records any open customer assumption. | Low | Cybersecurity Concept and Evidence | Security evidence and traceability | None | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-1001379436-P10-000-01-0021 Broad coverage justification: No exception justification recorded. |
| SSR-HW-001 | The ECU hardware shall provide the platform and secure-storage capabilities required for Hardware / HSM / Secure Storage (Hardware domain; allocated to Hardware Platform; interface: OEM/Customer Review Interface). | 14 | RFQX-1001379436-P10-000-01-0022; RFQX-1001379436-P10-000-01-0060; RFQX-1001379436-P10-000-01-0063; RFQX-3299216-1-0004; RFQX-3299216-1-0059; RFQX-3299216-1-0145; RFQX-CVS123-2-0316; RFQX-CVS123-2-0334; RFQX-CVS124-0058; RFQX-CVS124-0130; RFQX-CVS124-0152; RFQX-CVS124-0153; 2 additional linked customer requirements | Clustered from 14 customer requirements allocated to 'Hardware / HSM / Secure Storage' / 'Hardware / HSM / Secure Storage' (e.g. RFQX-1001379436-P10-000-01-0022, RFQX-1001379436-P10-000-01-0060, RFQX-1001379436-P10-000-01-0063 …). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Hardware / HSM / Secure Storage satisfies the linked customer requirement set and records any open customer assumption. | Medium | Hardware / HSM / Secure Storage | Hardware / HSM / Secure Storage | None | BLOCKED BY CUSTOMER DECISION | TOO BROAD SYSTEM REQUIREMENT DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-1001379436-P10-000-01-0022; RFQX-1001379436-P10-000-01-0060; RFQX-1001379436-P10-000-01-0063; RFQX-3299216-1-0004; RFQX-3299216-1-0059; RFQX-3299216-1-0145; RFQX-CVS123-2-0316; RFQX-CVS123-2-0334; RFQX-CVS124-0058; RFQX-CVS124-0130; RFQX-CVS124-0152; RFQX-CVS124-0153; RFQX-CVS124-0209; RFQX-CVS124-0270 Broad coverage justification: No exception justification recorded. |
| SSR-DAI-001 | The ECU shall verify the authenticity and integrity of Data Authenticity and Integrity Verification data and reject manipulated or unauthenticated data (Cybersecurity domain; allocated to Security Services; security capability: Authentication; interface: OEM/Customer Review Interface). | 5 | RFQX-1001379436-P10-000-01-0025; RFQX-CVS31-0017; RFQX-CVS31-0021; RFQX-CVS31-0073; RFQX-CVS31-0081 | Clustered from 5 customer requirements allocated to 'Data Authenticity and Integrity Verification' / 'Data Authenticity and Integrity Verification' (e.g. RFQX-1001379436-P10-000-01-0025, RFQX-CVS31-0017, RFQX-CVS31-0021 …). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Data Authenticity and Integrity Verification satisfies the linked customer requirement set and records any open customer assumption. | High | Data Authenticity and Integrity Verification | Data Authenticity and Integrity Verification | OP-002;OP-003 | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-1001379436-P10-000-01-0025; RFQX-CVS31-0017; RFQX-CVS31-0021; RFQX-CVS31-0073; RFQX-CVS31-0081 Broad coverage justification: No exception justification recorded. |
| SSR-SYS-001 | The ECU shall implement the System Function behaviour required by its allocated customer requirements, including the specified functions, signals, states and timing (System domain; allocated to System Core; interface: OEM/Customer Review Interface). | 122 | RFQX-1001379436-P10-000-01-0028; RFQX-1001379436-P10-000-01-0038; RFQX-1001379436-P10-000-01-0039; RFQX-1001379436-P10-000-01-0040; RFQX-1001379436-P10-000-01-0043; RFQX-1001379436-P10-000-01-0051; RFQX-1001379436-P10-000-01-0059; RFQX-1001379436-P10-000-01-0061; RFQX-3299216-1-0002; RFQX-3299216-1-0007; RFQX-3299216-1-0012; RFQX-3299216-1-0013; 110 additional linked customer requirements | Clustered from 122 customer requirements allocated to 'System Function' / 'System Function' (e.g. RFQX-1001379436-P10-000-01-0028, RFQX-1001379436-P10-000-01-0038, RFQX-1001379436-P10-000-01-0039 …). Linked source table/diagram context was considered. | Test + table/diagram context review | Test + table/diagram context review evidence demonstrates that System Function satisfies the linked customer requirement set and records any open customer assumption. | High | System Function | System Function | None | BLOCKED BY CUSTOMER DECISION | TOO BROAD SYSTEM REQUIREMENT DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-1001379436-P10-000-01-0028; RFQX-1001379436-P10-000-01-0038; RFQX-1001379436-P10-000-01-0039; RFQX-1001379436-P10-000-01-0040; RFQX-1001379436-P10-000-01-0043; RFQX-1001379436-P10-000-01-0051; RFQX-1001379436-P10-000-01-0059; RFQX-1001379436-P10-000-01-0061; RFQX-3299216-1-0002; RFQX-3299216-1-0007; RFQX-3299216-1-0012; RFQX-3299216-1-0013; RFQX-3299216-1-0014; RFQX-3299216-1-0021; RFQX-3299216-1-0022; RFQX-3299216-1-0025; RFQX-3299216-1-0026; RFQX-3299216-1-0027; RFQX-3299216-1-0029; RFQX-3299216-1-0030; RFQX-3299216-1-0032; RFQX-3299216-1-0034; RFQX-3299216-1-0047; RFQX-3299216-1-0057; RFQX-3299216-1-0060; RFQX-3299216-1-0062; RFQX-3299216-1-0071; RFQX-3299216-1-0074; RFQX-3299216-1-0089; RFQX-3299216-1-0101; RFQX-3299216-1-0105; RFQX-3299216-1-0110; RFQX-3299216-1-0111; RFQX-3299216-1-0112; RFQX-3299216-1-0113; RFQX-3299216-1-0114; RFQX-3299216-1-0115; RFQX-3299216-1-0116; RFQX-3299216-1-0119; RFQX-3299216-1-0120; RFQX-3299216-1-0121; RFQX-3299216-1-0122; RFQX-3299216-1-0123; RFQX-3299216-1-0124; RFQX-3299216-1-0125; RFQX-3299216-1-0136; RFQX-3299216-1-0138; RFQX-3299216-1-0143; RFQX-3299216-1-0144; RFQX-3299216-1-0146; RFQX-3299216-1-0154; RFQX-3299216-1-0198; RFQX-3299216-1-0199; RFQX-3299216-1-0207; RFQX-3299216-1-0208; RFQX-3299216-1-0213; RFQX-3299216-1-0228; RFQX-3299216-1-0245; RFQX-CVS123-2-0036; RFQX-CVS123-2-0051; RFQX-CVS123-2-0175; RFQX-CVS123-2-0176; RFQX-CVS123-2-0193; RFQX-CVS123-2-0268; RFQX-CVS123-2-0275; RFQX-CVS123-2-0294; RFQX-CVS123-2-0317; RFQX-CVS123-2-0340; RFQX-CVS123-2-0341; RFQX-CVS123-2-0342; RFQX-CVS124-0019; RFQX-CVS124-0036; RFQX-CVS124-0089; RFQX-CVS124-0132; RFQX-CVS124-0195; RFQX-CVS124-0295; RFQX-CVS124-0297; RFQX-CVS124-0303; RFQX-CVS124-0304; RFQX-CVS124-0333 Broad coverage justification: No exception justification recorded. |
| SSR-PROD-001 | The ECU and production process shall enforce development/production hardening for Supplier Development and Production Hardening, including debug lock and protected access (Hardware domain; allocated to Hardware Platform). | 1 | RFQX-1001379436-P10-000-01-0029 | Clustered from 1 customer requirements allocated to 'Supplier Development and Production Hardening' / 'Supplier Development and Production Hardening' (e.g. RFQX-1001379436-P10-000-01-0029). | Review + Test | Review + Test evidence demonstrates that Supplier Development and Production Hardening satisfies the linked customer requirement set and records any open customer assumption. | Low | Supplier Development and Production Hardening | Supplier Development and Production Hardening | None | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-1001379436-P10-000-01-0029 Broad coverage justification: No exception justification recorded. |
| SSR-COM-001 | The ECU shall restrict and protect communication for OEM/Customer Review Interface, exposing only OEM-agreed services and applying authenticity/integrity/freshness and boundary controls on allocated signals (Hardware domain; allocated to Hardware Platform; interface: OEM/Customer Review Interface). | 2 | RFQX-1001379436-P10-000-01-0030; RFQX-1001379436-P10-000-01-0036 | Clustered from 2 customer requirements allocated to 'Secure Communication and Boundary Control' / 'OEM/Customer Review Interface' (e.g. RFQX-1001379436-P10-000-01-0030, RFQX-1001379436-P10-000-01-0036). | Review + Test | Review + Test evidence demonstrates that OEM/Customer Review Interface satisfies the linked customer requirement set and records any open customer assumption. | Low | Secure Communication and Boundary Control | OEM/Customer Review Interface | OP-008 | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-1001379436-P10-000-01-0030; RFQX-1001379436-P10-000-01-0036 Broad coverage justification: No exception justification recorded. |
| SSR-COM-002 | The ECU shall restrict and protect communication for Secure Communication and Boundary Control, exposing only OEM-agreed services and applying authenticity/integrity/freshness and boundary controls on allocated signals (System domain; allocated to System Core). | 4 | RFQX-1001379436-P10-000-01-0031; RFQX-1001379436-P10-000-01-0034; RFQX-CVS123-2-0173; RFQX-CVS124-0172 | Clustered from 4 customer requirements allocated to 'Secure Communication and Boundary Control' / 'Secure Communication and Boundary Control' (e.g. RFQX-1001379436-P10-000-01-0031, RFQX-1001379436-P10-000-01-0034, RFQX-CVS123-2-0173 …). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Secure Communication and Boundary Control satisfies the linked customer requirement set and records any open customer assumption. | Medium | Secure Communication and Boundary Control | Secure Communication and Boundary Control | None | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-1001379436-P10-000-01-0031; RFQX-1001379436-P10-000-01-0034; RFQX-CVS123-2-0173; RFQX-CVS124-0172 Broad coverage justification: No exception justification recorded. |
| SSR-COM-003 | The ECU shall restrict and protect communication for OEM/Customer Review Interface, exposing only OEM-agreed services and applying authenticity/integrity/freshness and boundary controls on allocated signals (System domain; allocated to System Core; interface: OEM/Customer Review Interface). | 1 | RFQX-1001379436-P10-000-01-0032 | Clustered from 1 customer requirements allocated to 'Secure Communication and Boundary Control' / 'OEM/Customer Review Interface' (e.g. RFQX-1001379436-P10-000-01-0032). | Review + Test | Review + Test evidence demonstrates that OEM/Customer Review Interface satisfies the linked customer requirement set and records any open customer assumption. | Low | Secure Communication and Boundary Control | OEM/Customer Review Interface | None | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-1001379436-P10-000-01-0032 Broad coverage justification: No exception justification recorded. |
| SSR-KEY-001 | The ECU shall manage key and certificate material for Key and Certificate Handling across provisioning, storage, use, renewal and revocation per the agreed key lifecycle (Cybersecurity domain; allocated to Security Services; security capability: Certificate handling; interface: OEM/Customer Review Interface). | 18 | RFQX-1001379436-P10-000-01-0041; RFQX-1001379436-P10-000-01-0042; RFQX-CVS124-0160; RFQX-CVS124-0210; RFQX-CVS151-0060; RFQX-CVS151-0066; RFQX-CVS154-0044; RFQX-CVS31-0037; RFQX-CVS31-0074; RFQX-CVS31-0075; RFQX-CVS31-0078; RFQX-CVS31-0080; 6 additional linked customer requirements | Clustered from 18 customer requirements allocated to 'Key and Certificate Handling' / 'Key and Certificate Handling' (e.g. RFQX-1001379436-P10-000-01-0041, RFQX-1001379436-P10-000-01-0042, RFQX-CVS124-0160 …). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Key and Certificate Handling satisfies the linked customer requirement set and records any open customer assumption. | High | Key and Certificate Handling | Key and Certificate Handling | OP-002;OP-003 | BLOCKED BY CUSTOMER DECISION | TOO BROAD SYSTEM REQUIREMENT DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-1001379436-P10-000-01-0041; RFQX-1001379436-P10-000-01-0042; RFQX-CVS124-0160; RFQX-CVS124-0210; RFQX-CVS151-0060; RFQX-CVS151-0066; RFQX-CVS154-0044; RFQX-CVS31-0037; RFQX-CVS31-0074; RFQX-CVS31-0075; RFQX-CVS31-0078; RFQX-CVS31-0080; RFQX-CVS31-0083; RFQX-CVS31-0088; RFQX-CVS31-0101; RFQX-CVS31-0102; RFQX-CVS31-0103; RFQX-CVS31-0106 Broad coverage justification: No exception justification recorded. |
| SSR-VIH-002 | The supplier shall support vulnerability monitoring and incident handling for Vulnerability and Incident Handling over the defined lifecycle, including field updates (Process / compliance domain; allocated to Compliance Process; interface: OEM/Customer Review Interface). | 3 | RFQX-1001379436-P10-000-01-0047; RFQX-1001379436-P10-000-01-0049; RFQX-1001379436-P10-000-01-0050 | Clustered from 3 customer requirements allocated to 'Vulnerability and Incident Handling' / 'Vulnerability and Incident Handling' (e.g. RFQX-1001379436-P10-000-01-0047, RFQX-1001379436-P10-000-01-0049, RFQX-1001379436-P10-000-01-0050). | Review + Test | Review + Test evidence demonstrates that Vulnerability and Incident Handling satisfies the linked customer requirement set and records any open customer assumption. | Low | Vulnerability and Incident Handling | Vulnerability and Incident Handling | None | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-1001379436-P10-000-01-0047; RFQX-1001379436-P10-000-01-0049; RFQX-1001379436-P10-000-01-0050 Broad coverage justification: No exception justification recorded. |
| SSR-VIH-003 | The supplier shall support vulnerability monitoring and incident handling for Vulnerability and Incident Handling over the defined lifecycle, including field updates (System domain; allocated to System Core; interface: OEM/Customer Review Interface). | 2 | RFQX-1001379436-P10-000-01-0054; RFQX-1001379436-P10-000-01-0055 | Clustered from 2 customer requirements allocated to 'Vulnerability and Incident Handling' / 'Vulnerability and Incident Handling' (e.g. RFQX-1001379436-P10-000-01-0054, RFQX-1001379436-P10-000-01-0055). | Review + Test | Review + Test evidence demonstrates that Vulnerability and Incident Handling satisfies the linked customer requirement set and records any open customer assumption. | Low | Vulnerability and Incident Handling | Vulnerability and Incident Handling | OP-006 | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-1001379436-P10-000-01-0054; RFQX-1001379436-P10-000-01-0055 Broad coverage justification: No exception justification recorded. |
| SSR-VIH-004 | The supplier shall support vulnerability monitoring and incident handling for Vulnerability and Incident Handling over the defined lifecycle, including field updates (Interface domain; allocated to External Interfaces; interface: External Interfaces). | 1 | RFQX-1001379436-P10-000-01-0058 | Clustered from 1 customer requirements allocated to 'Vulnerability and Incident Handling' / 'Vulnerability and Incident Handling' (e.g. RFQX-1001379436-P10-000-01-0058). | Review + Test | Review + Test evidence demonstrates that Vulnerability and Incident Handling satisfies the linked customer requirement set and records any open customer assumption. | Low | Vulnerability and Incident Handling | Vulnerability and Incident Handling | None | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-1001379436-P10-000-01-0058 Broad coverage justification: No exception justification recorded. |
| SSR-LIFE-001 | The ECU and supplier process shall handle lifecycle, field return and decommissioning for Lifecycle / Field Return / Decommissioning, including secure data and key handling (Hardware domain; allocated to Hardware Platform). | 1 | RFQX-1001379436-P10-000-01-0062 | Clustered from 1 customer requirements allocated to 'Lifecycle / Field Return / Decommissioning' / 'Lifecycle / Field Return / Decommissioning' (e.g. RFQX-1001379436-P10-000-01-0062). | Review + Test | Review + Test evidence demonstrates that Lifecycle / Field Return / Decommissioning satisfies the linked customer requirement set and records any open customer assumption. | Low | Lifecycle / Field Return / Decommissioning | Lifecycle / Field Return / Decommissioning | None | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-1001379436-P10-000-01-0062 Broad coverage justification: No exception justification recorded. |
| SSR-LOG-001 | The ECU shall record bounded security-relevant events for Security Logging and Event Handling with sufficient integrity and context for diagnostics and incident evidence (Cybersecurity domain; allocated to Security Services; security capability: Logging and audit trail). | 1 | RFQX-1001379436-P10-000-01-0067 | Clustered from 1 customer requirements allocated to 'Security Logging and Event Handling' / 'Security Logging and Event Handling' (e.g. RFQX-1001379436-P10-000-01-0067). | Review + Test | Review + Test evidence demonstrates that Security Logging and Event Handling satisfies the linked customer requirement set and records any open customer assumption. | Low | Security Logging and Event Handling | Security Logging and Event Handling | None | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-1001379436-P10-000-01-0067 Broad coverage justification: No exception justification recorded. |
| SSR-COM-004 | The ECU shall restrict and protect communication for Secure Communication and Boundary Control, exposing only OEM-agreed services and applying authenticity/integrity/freshness and boundary controls on allocated signals (IT / backend domain; allocated to Backend and IT Systems). | 11 | RFQX-3299216-1-0024; RFQX-3299216-1-0033; RFQX-3299216-1-0088; RFQX-CVS124-0433; RFQX-CVS151-0065; RFQX-CVS31-0047; RFQX-CVS31-0060; RFQX-CVS31-0070; RFQX-CVS31-0071; RFQX-CVS31-0157; RFQX-CVS31-0158 | Clustered from 11 customer requirements allocated to 'Secure Communication and Boundary Control' / 'Secure Communication and Boundary Control' (e.g. RFQX-3299216-1-0024, RFQX-3299216-1-0033, RFQX-3299216-1-0088 …). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Secure Communication and Boundary Control satisfies the linked customer requirement set and records any open customer assumption. | High | Secure Communication and Boundary Control | Secure Communication and Boundary Control | OP-002;OP-004 | BLOCKED BY CUSTOMER DECISION | TOO BROAD SYSTEM REQUIREMENT DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-3299216-1-0024; RFQX-3299216-1-0033; RFQX-3299216-1-0088; RFQX-CVS124-0433; RFQX-CVS151-0065; RFQX-CVS31-0047; RFQX-CVS31-0060; RFQX-CVS31-0070; RFQX-CVS31-0071; RFQX-CVS31-0157; RFQX-CVS31-0158 Broad coverage justification: No exception justification recorded. |
| SSR-DAI-002 | The ECU shall verify the authenticity and integrity of Data Authenticity and Integrity Verification data and reject manipulated or unauthenticated data (Interface domain; allocated to External Interfaces; interface: External Interfaces). | 1 | RFQX-3299216-1-0031 | Clustered from 1 customer requirements allocated to 'Data Authenticity and Integrity Verification' / 'Data Authenticity and Integrity Verification' (e.g. RFQX-3299216-1-0031). | Review + Test | Review + Test evidence demonstrates that Data Authenticity and Integrity Verification satisfies the linked customer requirement set and records any open customer assumption. | Low | Data Authenticity and Integrity Verification | Data Authenticity and Integrity Verification | None | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-3299216-1-0031 Broad coverage justification: No exception justification recorded. |
| SSR-TOOL-001 | The supplier shall provide the tooling, IT infrastructure and evidence storage required for Tooling / IT / Evidence Storage (Tooling domain; allocated to Engineering Toolchain). | 1 | RFQX-3299216-1-0035 | Clustered from 1 customer requirements allocated to 'Tooling / IT / Evidence Storage' / 'Tooling / IT / Evidence Storage' (e.g. RFQX-3299216-1-0035). | Review + Test | Review + Test evidence demonstrates that Tooling / IT / Evidence Storage satisfies the linked customer requirement set and records any open customer assumption. | Low | Tooling / IT / Evidence Storage | Tooling / IT / Evidence Storage | None | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-3299216-1-0035 Broad coverage justification: No exception justification recorded. |
| SSR-DAI-003 | The ECU shall verify the authenticity and integrity of Data Authenticity and Integrity Verification data and reject manipulated or unauthenticated data (IT / backend domain; allocated to Backend and IT Systems). | 8 | RFQX-3299216-1-0036; RFQX-3299216-1-0079; RFQX-CVS123-2-0240; RFQX-CVS123-2-0279; RFQX-CVS123-2-0297; RFQX-CVS124-0387; RFQX-CVS31-0041; RFQX-CVS31-0048 | Clustered from 8 customer requirements allocated to 'Data Authenticity and Integrity Verification' / 'Data Authenticity and Integrity Verification' (e.g. RFQX-3299216-1-0036, RFQX-3299216-1-0079, RFQX-CVS123-2-0240 …). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Data Authenticity and Integrity Verification satisfies the linked customer requirement set and records any open customer assumption. | High | Data Authenticity and Integrity Verification | Data Authenticity and Integrity Verification | None | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-3299216-1-0036; RFQX-3299216-1-0079; RFQX-CVS123-2-0240; RFQX-CVS123-2-0279; RFQX-CVS123-2-0297; RFQX-CVS124-0387; RFQX-CVS31-0041; RFQX-CVS31-0048 Broad coverage justification: No exception justification recorded. |
| SSR-TOOL-002 | The supplier shall provide the tooling, IT infrastructure and evidence storage required for Tooling / IT / Evidence Storage (IT / backend domain; allocated to Backend and IT Systems; interface: OEM/Customer Review Interface). | 99 | RFQX-3299216-1-0039; RFQX-3299216-1-0040; RFQX-3299216-1-0043; RFQX-3299216-1-0049; RFQX-3299216-1-0052; RFQX-3299216-1-0055; RFQX-3299216-1-0058; RFQX-3299216-1-0181; RFQX-3299216-1-0201; RFQX-CVS123-2-0112; RFQX-CVS123-2-0169; RFQX-CVS123-2-0186; 87 additional linked customer requirements | Clustered from 99 customer requirements allocated to 'Tooling / IT / Evidence Storage' / 'Tooling / IT / Evidence Storage' (e.g. RFQX-3299216-1-0039, RFQX-3299216-1-0040, RFQX-3299216-1-0043 …). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Tooling / IT / Evidence Storage satisfies the linked customer requirement set and records any open customer assumption. | High | Tooling / IT / Evidence Storage | Tooling / IT / Evidence Storage | OP-004;OP-009 | BLOCKED BY CUSTOMER DECISION | TOO BROAD SYSTEM REQUIREMENT DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-3299216-1-0039; RFQX-3299216-1-0040; RFQX-3299216-1-0043; RFQX-3299216-1-0049; RFQX-3299216-1-0052; RFQX-3299216-1-0055; RFQX-3299216-1-0058; RFQX-3299216-1-0181; RFQX-3299216-1-0201; RFQX-CVS123-2-0112; RFQX-CVS123-2-0169; RFQX-CVS123-2-0186; RFQX-CVS123-2-0200; RFQX-CVS123-2-0209; RFQX-CVS123-2-0220; RFQX-CVS123-2-0222; RFQX-CVS123-2-0225; RFQX-CVS123-2-0226; RFQX-CVS123-2-0228; RFQX-CVS123-2-0232; RFQX-CVS123-2-0233; RFQX-CVS123-2-0235; RFQX-CVS123-2-0237; RFQX-CVS123-2-0238; RFQX-CVS123-2-0250; RFQX-CVS123-2-0254; RFQX-CVS123-2-0262; RFQX-CVS123-2-0263; RFQX-CVS123-2-0265; RFQX-CVS123-2-0273; RFQX-CVS123-2-0276; RFQX-CVS123-2-0281; RFQX-CVS123-2-0282; RFQX-CVS123-2-0284; RFQX-CVS123-2-0292; RFQX-CVS123-2-0295; RFQX-CVS123-2-0298; RFQX-CVS123-2-0302; RFQX-CVS123-2-0308; RFQX-CVS123-2-0309; RFQX-CVS123-2-0310; RFQX-CVS123-2-0311; RFQX-CVS123-2-0313; RFQX-CVS123-2-0323; RFQX-CVS123-2-0325; RFQX-CVS123-2-0329; RFQX-CVS124-0018; RFQX-CVS124-0088; RFQX-CVS124-0154; RFQX-CVS124-0225; RFQX-CVS124-0381; RFQX-CVS124-0384; RFQX-CVS124-0406; RFQX-CVS124-0436; RFQX-CVS151-0014; RFQX-CVS151-0016; RFQX-CVS151-0018; RFQX-CVS151-0023; RFQX-CVS151-0028; RFQX-CVS151-0032; RFQX-CVS151-0033; RFQX-CVS151-0044; RFQX-CVS151-0048; RFQX-CVS151-0050; RFQX-CVS151-0053; RFQX-CVS151-0055; RFQX-CVS151-0057; RFQX-CVS151-0079; RFQX-CVS151-0080; RFQX-CVS151-0081; RFQX-CVS154-0008; RFQX-CVS154-0009; RFQX-CVS154-0011; RFQX-CVS154-0012; RFQX-CVS154-0014; RFQX-CVS154-0015; RFQX-CVS154-0027; RFQX-CVS154-0029; RFQX-CVS154-0040; RFQX-CVS154-0043 Broad coverage justification: No exception justification recorded. |
| SSR-COM-005 | The ECU shall restrict and protect communication for Secure Communication and Boundary Control, exposing only OEM-agreed services and applying authenticity/integrity/freshness and boundary controls on allocated signals (Hardware domain; allocated to Hardware Platform). | 3 | RFQX-3299216-1-0041; RFQX-3299216-1-0042; RFQX-3299216-1-0083 | Clustered from 3 customer requirements allocated to 'Secure Communication and Boundary Control' / 'Secure Communication and Boundary Control' (e.g. RFQX-3299216-1-0041, RFQX-3299216-1-0042, RFQX-3299216-1-0083). | Review + Test | Review + Test evidence demonstrates that Secure Communication and Boundary Control satisfies the linked customer requirement set and records any open customer assumption. | High | Secure Communication and Boundary Control | Secure Communication and Boundary Control | OP-004 | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-3299216-1-0041; RFQX-3299216-1-0042; RFQX-3299216-1-0083 Broad coverage justification: No exception justification recorded. |
| SSR-COM-006 | The ECU shall restrict and protect communication for Secure Communication and Boundary Control, exposing only OEM-agreed services and applying authenticity/integrity/freshness and boundary controls on allocated signals (Software domain; allocated to Application Software). | 5 | RFQX-3299216-1-0061; RFQX-CVS123-2-0211; RFQX-CVS124-0168; RFQX-CVS124-0198; RFQX-CVS31-0141 | Clustered from 5 customer requirements allocated to 'Secure Communication and Boundary Control' / 'Secure Communication and Boundary Control' (e.g. RFQX-3299216-1-0061, RFQX-CVS123-2-0211, RFQX-CVS124-0168 …). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Secure Communication and Boundary Control satisfies the linked customer requirement set and records any open customer assumption. | High | Secure Communication and Boundary Control | Secure Communication and Boundary Control | None | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-3299216-1-0061; RFQX-CVS123-2-0211; RFQX-CVS124-0168; RFQX-CVS124-0198; RFQX-CVS31-0141 Broad coverage justification: No exception justification recorded. |
| SSR-SYS-002 | The ECU shall implement the System Function behaviour required by its allocated customer requirements, including the specified functions, signals, states and timing (Process / compliance domain; allocated to Compliance Process; interface: OEM/Customer Review Interface). | 28 | RFQX-3299216-1-0070; RFQX-CVS123-2-0320; RFQX-CVS124-0129; RFQX-CVS124-0133; RFQX-CVS124-0134; RFQX-CVS124-0147; RFQX-CVS124-0165; RFQX-CVS124-0182; RFQX-CVS124-0202; RFQX-CVS124-0213; RFQX-CVS124-0216; RFQX-CVS124-0222; 16 additional linked customer requirements | Clustered from 28 customer requirements allocated to 'System Function' / 'System Function' (e.g. RFQX-3299216-1-0070, RFQX-CVS123-2-0320, RFQX-CVS124-0129 …). Linked source table/diagram context was considered. | Test + table/diagram context review | Test + table/diagram context review evidence demonstrates that System Function satisfies the linked customer requirement set and records any open customer assumption. | Medium | System Function | System Function | None | BLOCKED BY CUSTOMER DECISION | TOO BROAD SYSTEM REQUIREMENT DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-3299216-1-0070; RFQX-CVS123-2-0320; RFQX-CVS124-0129; RFQX-CVS124-0133; RFQX-CVS124-0134; RFQX-CVS124-0147; RFQX-CVS124-0165; RFQX-CVS124-0182; RFQX-CVS124-0202; RFQX-CVS124-0213; RFQX-CVS124-0216; RFQX-CVS124-0222; RFQX-CVS124-0228; RFQX-CVS124-0250; RFQX-CVS124-0254; RFQX-CVS124-0259; RFQX-CVS124-0264; RFQX-CVS124-0267; RFQX-CVS124-0284; RFQX-CVS124-0285; RFQX-CVS124-0288; RFQX-CVS124-0289; RFQX-CVS124-0290; RFQX-CVS124-0302; RFQX-CVS124-0312; RFQX-CVS124-0325; RFQX-CVS124-0437; RFQX-CVS31-0025 Broad coverage justification: No exception justification recorded. |
| SSR-SYS-003 | The ECU shall implement the System Function behaviour required by its allocated customer requirements, including the specified functions, signals, states and timing (Software domain; allocated to Application Software; interface: OEM/Customer Review Interface). | 30 | RFQX-3299216-1-0075; RFQX-3299216-1-0139; RFQX-3299216-1-0214; RFQX-3299216-1-0218; RFQX-3299216-1-0285; RFQX-CVS123-2-0058; RFQX-CVS123-2-0059; RFQX-CVS123-2-0066; RFQX-CVS123-2-0068; RFQX-CVS123-2-0168; RFQX-CVS123-2-0177; RFQX-CVS123-2-0181; 18 additional linked customer requirements | Clustered from 30 customer requirements allocated to 'System Function' / 'System Function' (e.g. RFQX-3299216-1-0075, RFQX-3299216-1-0139, RFQX-3299216-1-0214 …). Linked source table/diagram context was considered. | Test + table/diagram context review | Test + table/diagram context review evidence demonstrates that System Function satisfies the linked customer requirement set and records any open customer assumption. | High | System Function | System Function | None | BLOCKED BY CUSTOMER DECISION | TOO BROAD SYSTEM REQUIREMENT DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-3299216-1-0075; RFQX-3299216-1-0139; RFQX-3299216-1-0214; RFQX-3299216-1-0218; RFQX-3299216-1-0285; RFQX-CVS123-2-0058; RFQX-CVS123-2-0059; RFQX-CVS123-2-0066; RFQX-CVS123-2-0068; RFQX-CVS123-2-0168; RFQX-CVS123-2-0177; RFQX-CVS123-2-0181; RFQX-CVS123-2-0266; RFQX-CVS123-2-0319; RFQX-CVS123-2-0331; RFQX-CVS124-0079; RFQX-CVS124-0082; RFQX-CVS124-0150; RFQX-CVS124-0162; RFQX-CVS124-0180; RFQX-CVS124-0244; RFQX-CVS124-0300; RFQX-CVS124-0313; RFQX-CVS124-0315; RFQX-CVS124-0321; RFQX-CVS124-0332; RFQX-CVS124-0352; RFQX-CVS124-0368; RFQX-CVS124-0374; RFQX-CVS124-0398 Broad coverage justification: No exception justification recorded. |
| SSR-COM-007 | The ECU shall restrict and protect communication for External Interfaces, exposing only OEM-agreed services and applying authenticity/integrity/freshness and boundary controls on allocated signals (Interface domain; allocated to External Interfaces; interface: External Interfaces). | 26 | RFQX-3299216-1-0084; RFQX-3299216-1-0102; RFQX-3299216-1-0103; RFQX-3299216-1-0104; RFQX-3299216-1-0153; RFQX-3299216-1-0171; RFQX-3299216-1-0172; RFQX-3299216-1-0177; RFQX-3299216-1-0178; RFQX-CVS124-0149; RFQX-CVS32-0026; RFQX-CVS32-0029; 14 additional linked customer requirements | Clustered from 26 customer requirements allocated to 'Secure Communication and Boundary Control' / 'External Interfaces' (e.g. RFQX-3299216-1-0084, RFQX-3299216-1-0102, RFQX-3299216-1-0103 …). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that External Interfaces satisfies the linked customer requirement set and records any open customer assumption. | High | Secure Communication and Boundary Control | External Interfaces | None | BLOCKED BY CUSTOMER DECISION | TOO BROAD SYSTEM REQUIREMENT DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-3299216-1-0084; RFQX-3299216-1-0102; RFQX-3299216-1-0103; RFQX-3299216-1-0104; RFQX-3299216-1-0153; RFQX-3299216-1-0171; RFQX-3299216-1-0172; RFQX-3299216-1-0177; RFQX-3299216-1-0178; RFQX-CVS124-0149; RFQX-CVS32-0026; RFQX-CVS32-0029; RFQX-CVS32-0030; RFQX-CVS32-0044; RFQX-CVS32-0047; RFQX-CVS32-0071; RFQX-CVS32-0074; RFQX-CVS32-0075; RFQX-CVS32-0076; RFQX-CVS32-0078; RFQX-CVS32-0088; RFQX-CVS32-0100; RFQX-CVS32-0101; RFQX-CVS32-0102; RFQX-CVS32-0104; RFQX-CVS32-0111 Broad coverage justification: No exception justification recorded. |
| SSR-RBAC-001 | The ECU shall enforce authenticated, role-authorised access for Secure Diagnostics / RBAC, restricting security-relevant diagnostic services per the OEM-agreed role model (Cybersecurity domain; allocated to Security Services; security capability: Diagnostic security; interface: OEM/Customer Review Interface). | 20 | RFQX-3299216-1-0107; RFQX-3299216-1-0126; RFQX-CVS123-2-0034; RFQX-CVS123-2-0047; RFQX-CVS123-2-0052; RFQX-CVS123-2-0056; RFQX-CVS123-2-0166; RFQX-CVS123-2-0192; RFQX-CVS123-2-0242; RFQX-CVS123-2-0303; RFQX-CVS124-0075; RFQX-CVS124-0077; 8 additional linked customer requirements | Clustered from 20 customer requirements allocated to 'Secure Diagnostics / RBAC' / 'Secure Diagnostics / RBAC' (e.g. RFQX-3299216-1-0107, RFQX-3299216-1-0126, RFQX-CVS123-2-0034 …). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Secure Diagnostics / RBAC satisfies the linked customer requirement set and records any open customer assumption. | High | Secure Diagnostics / RBAC | Secure Diagnostics / RBAC | OP-002 | BLOCKED BY CUSTOMER DECISION | TOO BROAD SYSTEM REQUIREMENT DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-3299216-1-0107; RFQX-3299216-1-0126; RFQX-CVS123-2-0034; RFQX-CVS123-2-0047; RFQX-CVS123-2-0052; RFQX-CVS123-2-0056; RFQX-CVS123-2-0166; RFQX-CVS123-2-0192; RFQX-CVS123-2-0242; RFQX-CVS123-2-0303; RFQX-CVS124-0075; RFQX-CVS124-0077; RFQX-CVS124-0078; RFQX-CVS124-0171; RFQX-CVS124-0186; RFQX-CVS124-0431; RFQX-CVS124-0432; RFQX-CVS151-0045; RFQX-CVS151-0083; RFQX-CVS31-0006 Broad coverage justification: No exception justification recorded. |
| SSR-VV-001 | The supplier shall verify and validate Security evidence and traceability per the agreed cybersecurity verification and validation plan (System domain; allocated to System Core; interface: OEM/Customer Review Interface). | 2 | RFQX-3299216-1-0134; RFQX-CVS154-0021 | Clustered from 2 customer requirements allocated to 'Verification and Validation' / 'Security evidence and traceability' (e.g. RFQX-3299216-1-0134, RFQX-CVS154-0021). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Security evidence and traceability satisfies the linked customer requirement set and records any open customer assumption. | Medium | Verification and Validation | Security evidence and traceability | None | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-3299216-1-0134; RFQX-CVS154-0021 Broad coverage justification: No exception justification recorded. |
| SSR-DIAG-001 | The ECU shall provide the diagnostic services for Diagnostic Services required by the allocated customer requirements, including the specified services, sessions and data identifiers (Interface domain; allocated to External Interfaces; interface: External Interfaces). | 1 | RFQX-3299216-1-0135 | Clustered from 1 customer requirements allocated to 'Diagnostic Services' / 'Diagnostic Services' (e.g. RFQX-3299216-1-0135). | Test | Test evidence demonstrates that Diagnostic Services satisfies the linked customer requirement set and records any open customer assumption. | Low | Diagnostic Services | Diagnostic Services | None | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-3299216-1-0135 Broad coverage justification: No exception justification recorded. |
| SSR-COM-008 | The ECU shall restrict and protect communication for OEM/Customer Review Interface, exposing only OEM-agreed services and applying authenticity/integrity/freshness and boundary controls on allocated signals (Software domain; allocated to Application Software; interface: OEM/Customer Review Interface). | 1 | RFQX-3299216-1-0137 | Clustered from 1 customer requirements allocated to 'Secure Communication and Boundary Control' / 'OEM/Customer Review Interface' (e.g. RFQX-3299216-1-0137). | Review + Test | Review + Test evidence demonstrates that OEM/Customer Review Interface satisfies the linked customer requirement set and records any open customer assumption. | Low | Secure Communication and Boundary Control | OEM/Customer Review Interface | None | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-3299216-1-0137 Broad coverage justification: No exception justification recorded. |
| SSR-LIFE-002 | The ECU and supplier process shall handle lifecycle, field return and decommissioning for Lifecycle / Field Return / Decommissioning, including secure data and key handling (System domain; allocated to System Core). | 1 | RFQX-3299216-1-0200 | Clustered from 1 customer requirements allocated to 'Lifecycle / Field Return / Decommissioning' / 'Lifecycle / Field Return / Decommissioning' (e.g. RFQX-3299216-1-0200). | Review + Test | Review + Test evidence demonstrates that Lifecycle / Field Return / Decommissioning satisfies the linked customer requirement set and records any open customer assumption. | Low | Lifecycle / Field Return / Decommissioning | Lifecycle / Field Return / Decommissioning | None | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-3299216-1-0200 Broad coverage justification: No exception justification recorded. |
| SSR-BOOT-001 | The ECU shall verify boot and application authenticity/integrity for Secure software update and flash readiness and enforce the defined behaviour on verification failure (Software domain; allocated to Application Software; interface: OEM/Customer Review Interface). | 3 | RFQX-CVS123-2-0037; RFQX-CVS123-2-0072; RFQX-CVS124-0014 | Clustered from 3 customer requirements allocated to 'Bootloader and Application State Handling' / 'Secure software update and flash readiness' (e.g. RFQX-CVS123-2-0037, RFQX-CVS123-2-0072, RFQX-CVS124-0014). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Secure software update and flash readiness satisfies the linked customer requirement set and records any open customer assumption. | High | Bootloader and Application State Handling | Secure software update and flash readiness | OP-002 | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS123-2-0037; RFQX-CVS123-2-0072; RFQX-CVS124-0014 Broad coverage justification: No exception justification recorded. |
| SSR-BOOT-002 | The ECU shall verify boot and application authenticity/integrity for Secure software update and flash readiness and enforce the defined behaviour on verification failure (Hardware domain; allocated to Hardware Platform). | 3 | RFQX-CVS123-2-0039; RFQX-CVS123-2-0258; RFQX-CVS124-0343 | Clustered from 3 customer requirements allocated to 'Bootloader and Application State Handling' / 'Secure software update and flash readiness' (e.g. RFQX-CVS123-2-0039, RFQX-CVS123-2-0258, RFQX-CVS124-0343). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Secure software update and flash readiness satisfies the linked customer requirement set and records any open customer assumption. | High | Bootloader and Application State Handling | Secure software update and flash readiness | None | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS123-2-0039; RFQX-CVS123-2-0258; RFQX-CVS124-0343 Broad coverage justification: No exception justification recorded. |
| SSR-UPD-001 | The ECU shall support secure software update/flashing for Secure software update and flash readiness, accepting only authenticated, integrity-verified software through the agreed programming sequence (Software domain; allocated to Application Software; interface: OEM/Customer Review Interface). | 17 | RFQX-CVS123-2-0042; RFQX-CVS123-2-0048; RFQX-CVS123-2-0049; RFQX-CVS123-2-0050; RFQX-CVS123-2-0178; RFQX-CVS123-2-0184; RFQX-CVS123-2-0188; RFQX-CVS123-2-0197; RFQX-CVS123-2-0199; RFQX-CVS123-2-0299; RFQX-CVS123-2-0333; RFQX-CVS124-0060; 5 additional linked customer requirements | Clustered from 17 customer requirements allocated to 'Software Update / Flashing' / 'Secure software update and flash readiness' (e.g. RFQX-CVS123-2-0042, RFQX-CVS123-2-0048, RFQX-CVS123-2-0049 …). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Secure software update and flash readiness satisfies the linked customer requirement set and records any open customer assumption. | High | Software Update / Flashing | Secure software update and flash readiness | OP-004 | BLOCKED BY CUSTOMER DECISION | TOO BROAD SYSTEM REQUIREMENT DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS123-2-0042; RFQX-CVS123-2-0048; RFQX-CVS123-2-0049; RFQX-CVS123-2-0050; RFQX-CVS123-2-0178; RFQX-CVS123-2-0184; RFQX-CVS123-2-0188; RFQX-CVS123-2-0197; RFQX-CVS123-2-0199; RFQX-CVS123-2-0299; RFQX-CVS123-2-0333; RFQX-CVS124-0060; RFQX-CVS124-0137; RFQX-CVS124-0140; RFQX-CVS124-0185; RFQX-CVS124-0389; RFQX-CVS124-0391 Broad coverage justification: No exception justification recorded. |
| SSR-UPD-002 | The ECU shall support secure software update/flashing for Secure software update and flash readiness, accepting only authenticated, integrity-verified software through the agreed programming sequence (System domain; allocated to System Core; interface: OEM/Customer Review Interface). | 18 | RFQX-CVS123-2-0043; RFQX-CVS123-2-0062; RFQX-CVS123-2-0064; RFQX-CVS123-2-0070; RFQX-CVS123-2-0071; RFQX-CVS123-2-0185; RFQX-CVS123-2-0271; RFQX-CVS124-0145; RFQX-CVS124-0327; RFQX-CVS124-0329; RFQX-CVS124-0330; RFQX-CVS124-0336; 6 additional linked customer requirements | Clustered from 18 customer requirements allocated to 'Software Update / Flashing' / 'Secure software update and flash readiness' (e.g. RFQX-CVS123-2-0043, RFQX-CVS123-2-0062, RFQX-CVS123-2-0064 …). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Secure software update and flash readiness satisfies the linked customer requirement set and records any open customer assumption. | High | Software Update / Flashing | Secure software update and flash readiness | OP-004 | BLOCKED BY CUSTOMER DECISION | TOO BROAD SYSTEM REQUIREMENT DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS123-2-0043; RFQX-CVS123-2-0062; RFQX-CVS123-2-0064; RFQX-CVS123-2-0070; RFQX-CVS123-2-0071; RFQX-CVS123-2-0185; RFQX-CVS123-2-0271; RFQX-CVS124-0145; RFQX-CVS124-0327; RFQX-CVS124-0329; RFQX-CVS124-0330; RFQX-CVS124-0336; RFQX-CVS124-0337; RFQX-CVS124-0339; RFQX-CVS124-0348; RFQX-CVS124-0366; RFQX-CVS124-0388; RFQX-CVS124-0392 Broad coverage justification: No exception justification recorded. |
| SSR-BOOT-003 | The ECU shall verify boot and application authenticity/integrity for Bootloader and Application State Handling and enforce the defined behaviour on verification failure (System domain; allocated to System Core). | 1 | RFQX-CVS123-2-0044 | Clustered from 1 customer requirements allocated to 'Bootloader and Application State Handling' / 'Bootloader and Application State Handling' (e.g. RFQX-CVS123-2-0044). | Review + Test | Review + Test evidence demonstrates that Bootloader and Application State Handling satisfies the linked customer requirement set and records any open customer assumption. | Low | Bootloader and Application State Handling | Bootloader and Application State Handling | None | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS123-2-0044 Broad coverage justification: No exception justification recorded. |
| SSR-DIAG-002 | The ECU shall provide the diagnostic services for Diagnostic Services required by the allocated customer requirements, including the specified services, sessions and data identifiers (IT / backend domain; allocated to Backend and IT Systems; interface: OEM/Customer Review Interface). | 2 | RFQX-CVS123-2-0046; RFQX-CVS123-2-0251 | Clustered from 2 customer requirements allocated to 'Diagnostic Services' / 'Diagnostic Services' (e.g. RFQX-CVS123-2-0046, RFQX-CVS123-2-0251). Linked source table/diagram context was considered. | Test + table/diagram context review | Test + table/diagram context review evidence demonstrates that Diagnostic Services satisfies the linked customer requirement set and records any open customer assumption. | Medium | Diagnostic Services | Diagnostic Services | None | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS123-2-0046; RFQX-CVS123-2-0251 Broad coverage justification: No exception justification recorded. |
| SSR-BOOT-004 | The ECU shall verify boot and application authenticity/integrity for Bootloader and Application State Handling and enforce the defined behaviour on verification failure (IT / backend domain; allocated to Backend and IT Systems). | 1 | RFQX-CVS123-2-0055 | Clustered from 1 customer requirements allocated to 'Bootloader and Application State Handling' / 'Bootloader and Application State Handling' (e.g. RFQX-CVS123-2-0055). | Review + Test | Review + Test evidence demonstrates that Bootloader and Application State Handling satisfies the linked customer requirement set and records any open customer assumption. | High | Bootloader and Application State Handling | Bootloader and Application State Handling | OP-004 | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS123-2-0055 Broad coverage justification: No exception justification recorded. |
| SSR-DAI-004 | The ECU shall verify the authenticity and integrity of Data Authenticity and Integrity Verification data and reject manipulated or unauthenticated data (Software domain; allocated to Application Software). | 8 | RFQX-CVS123-2-0061; RFQX-CVS123-2-0110; RFQX-CVS123-2-0246; RFQX-CVS123-2-0277; RFQX-CVS123-2-0278; RFQX-CVS123-2-0337; RFQX-CVS124-0385; RFQX-CVS124-0386 | Clustered from 8 customer requirements allocated to 'Data Authenticity and Integrity Verification' / 'Data Authenticity and Integrity Verification' (e.g. RFQX-CVS123-2-0061, RFQX-CVS123-2-0110, RFQX-CVS123-2-0246 …). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Data Authenticity and Integrity Verification satisfies the linked customer requirement set and records any open customer assumption. | High | Data Authenticity and Integrity Verification | Data Authenticity and Integrity Verification | OP-008 | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS123-2-0061; RFQX-CVS123-2-0110; RFQX-CVS123-2-0246; RFQX-CVS123-2-0277; RFQX-CVS123-2-0278; RFQX-CVS123-2-0337; RFQX-CVS124-0385; RFQX-CVS124-0386 Broad coverage justification: No exception justification recorded. |
| SSR-RBAC-002 | The ECU shall enforce authenticated, role-authorised access for Secure software update and flash readiness, restricting security-relevant diagnostic services per the OEM-agreed role model (Cybersecurity domain; allocated to Security Services; security capability: Authentication). | 3 | RFQX-CVS123-2-0078; RFQX-CVS123-2-0079; RFQX-CVS123-2-0244 | Clustered from 3 customer requirements allocated to 'Secure Diagnostics / RBAC' / 'Secure software update and flash readiness' (e.g. RFQX-CVS123-2-0078, RFQX-CVS123-2-0079, RFQX-CVS123-2-0244). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Secure software update and flash readiness satisfies the linked customer requirement set and records any open customer assumption. | High | Secure Diagnostics / RBAC | Secure software update and flash readiness | OP-002 | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS123-2-0078; RFQX-CVS123-2-0079; RFQX-CVS123-2-0244 Broad coverage justification: No exception justification recorded. |
| SSR-SDT-001 | The ECU shall protect security-relevant data transfer for Secure Data Transfer / Data Security Container using the agreed secured data transfer / data security container scheme (Software domain; allocated to Application Software). | 6 | RFQX-CVS123-2-0114; RFQX-CVS123-2-0204; RFQX-CVS123-2-0247; RFQX-CVS123-2-0261; RFQX-CVS124-0273; RFQX-CVS124-0346 | Clustered from 6 customer requirements allocated to 'Secure Data Transfer / Data Security Container' / 'Secure Data Transfer / Data Security Container' (e.g. RFQX-CVS123-2-0114, RFQX-CVS123-2-0204, RFQX-CVS123-2-0247 …). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Secure Data Transfer / Data Security Container satisfies the linked customer requirement set and records any open customer assumption. | High | Secure Data Transfer / Data Security Container | Secure Data Transfer / Data Security Container | None | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS123-2-0114; RFQX-CVS123-2-0204; RFQX-CVS123-2-0247; RFQX-CVS123-2-0261; RFQX-CVS124-0273; RFQX-CVS124-0346 Broad coverage justification: No exception justification recorded. |
| SSR-UPD-003 | The ECU shall support secure software update/flashing for Secure software update and flash readiness, accepting only authenticated, integrity-verified software through the agreed programming sequence (IT / backend domain; allocated to Backend and IT Systems; interface: OEM/Customer Review Interface). | 4 | RFQX-CVS123-2-0164; RFQX-CVS123-2-0187; RFQX-CVS124-0142; RFQX-CVS124-0397 | Clustered from 4 customer requirements allocated to 'Software Update / Flashing' / 'Secure software update and flash readiness' (e.g. RFQX-CVS123-2-0164, RFQX-CVS123-2-0187, RFQX-CVS124-0142 …). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Secure software update and flash readiness satisfies the linked customer requirement set and records any open customer assumption. | High | Software Update / Flashing | Secure software update and flash readiness | OP-002;OP-004 | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS123-2-0164; RFQX-CVS123-2-0187; RFQX-CVS124-0142; RFQX-CVS124-0397 Broad coverage justification: No exception justification recorded. |
| SSR-UPD-004 | The ECU shall support secure software update/flashing for Secure software update and flash readiness, accepting only authenticated, integrity-verified software through the agreed programming sequence (Hardware domain; allocated to Hardware Platform; interface: OEM/Customer Review Interface). | 6 | RFQX-CVS123-2-0165; RFQX-CVS124-0024; RFQX-CVS124-0028; RFQX-CVS124-0031; RFQX-CVS124-0043; RFQX-CVS124-0074 | Clustered from 6 customer requirements allocated to 'Software Update / Flashing' / 'Secure software update and flash readiness' (e.g. RFQX-CVS123-2-0165, RFQX-CVS124-0024, RFQX-CVS124-0028 …). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Secure software update and flash readiness satisfies the linked customer requirement set and records any open customer assumption. | High | Software Update / Flashing | Secure software update and flash readiness | None | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS123-2-0165; RFQX-CVS124-0024; RFQX-CVS124-0028; RFQX-CVS124-0031; RFQX-CVS124-0043; RFQX-CVS124-0074 Broad coverage justification: No exception justification recorded. |
| SSR-TOOL-003 | The supplier shall provide the tooling, IT infrastructure and evidence storage required for Tooling / IT / Evidence Storage (Software domain; allocated to Application Software). | 31 | RFQX-CVS123-2-0167; RFQX-CVS123-2-0190; RFQX-CVS123-2-0203; RFQX-CVS123-2-0205; RFQX-CVS123-2-0213; RFQX-CVS123-2-0214; RFQX-CVS123-2-0215; RFQX-CVS123-2-0218; RFQX-CVS123-2-0223; RFQX-CVS123-2-0224; RFQX-CVS123-2-0227; RFQX-CVS123-2-0229; 19 additional linked customer requirements | Clustered from 31 customer requirements allocated to 'Tooling / IT / Evidence Storage' / 'Tooling / IT / Evidence Storage' (e.g. RFQX-CVS123-2-0167, RFQX-CVS123-2-0190, RFQX-CVS123-2-0203 …). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Tooling / IT / Evidence Storage satisfies the linked customer requirement set and records any open customer assumption. | High | Tooling / IT / Evidence Storage | Tooling / IT / Evidence Storage | None | BLOCKED BY CUSTOMER DECISION | TOO BROAD SYSTEM REQUIREMENT DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS123-2-0167; RFQX-CVS123-2-0190; RFQX-CVS123-2-0203; RFQX-CVS123-2-0205; RFQX-CVS123-2-0213; RFQX-CVS123-2-0214; RFQX-CVS123-2-0215; RFQX-CVS123-2-0218; RFQX-CVS123-2-0223; RFQX-CVS123-2-0224; RFQX-CVS123-2-0227; RFQX-CVS123-2-0229; RFQX-CVS123-2-0230; RFQX-CVS123-2-0234; RFQX-CVS123-2-0239; RFQX-CVS123-2-0256; RFQX-CVS123-2-0260; RFQX-CVS123-2-0269; RFQX-CVS123-2-0328; RFQX-CVS123-2-0336; RFQX-CVS123-2-0339; RFQX-CVS124-0157; RFQX-CVS124-0161; RFQX-CVS124-0192; RFQX-CVS124-0272; RFQX-CVS124-0274; RFQX-CVS124-0275; RFQX-CVS124-0341; RFQX-CVS124-0345; RFQX-CVS124-0364; RFQX-CVS154-0038 Broad coverage justification: No exception justification recorded. |
| SSR-BOOT-005 | The ECU shall verify boot and application authenticity/integrity for Bootloader and Application State Handling and enforce the defined behaviour on verification failure (Software domain; allocated to Application Software). | 3 | RFQX-CVS123-2-0179; RFQX-CVS124-0193; RFQX-CVS124-0354 | Clustered from 3 customer requirements allocated to 'Bootloader and Application State Handling' / 'Bootloader and Application State Handling' (e.g. RFQX-CVS123-2-0179, RFQX-CVS124-0193, RFQX-CVS124-0354). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Bootloader and Application State Handling satisfies the linked customer requirement set and records any open customer assumption. | Medium | Bootloader and Application State Handling | Bootloader and Application State Handling | None | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS123-2-0179; RFQX-CVS124-0193; RFQX-CVS124-0354 Broad coverage justification: No exception justification recorded. |
| SSR-VV-002 | The supplier shall verify and validate Security evidence and traceability per the agreed cybersecurity verification and validation plan (IT / backend domain; allocated to Backend and IT Systems; interface: OEM/Customer Review Interface). | 5 | RFQX-CVS123-2-0207; RFQX-CVS123-2-0335; RFQX-CVS154-0010; RFQX-CVS154-0013; RFQX-CVS154-0016 | Clustered from 5 customer requirements allocated to 'Verification and Validation' / 'Security evidence and traceability' (e.g. RFQX-CVS123-2-0207, RFQX-CVS123-2-0335, RFQX-CVS154-0010 …). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Security evidence and traceability satisfies the linked customer requirement set and records any open customer assumption. | Medium | Verification and Validation | Security evidence and traceability | None | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS123-2-0207; RFQX-CVS123-2-0335; RFQX-CVS154-0010; RFQX-CVS154-0013; RFQX-CVS154-0016 Broad coverage justification: No exception justification recorded. |
| SSR-VV-003 | The supplier shall verify and validate Security evidence and traceability per the agreed cybersecurity verification and validation plan (Software domain; allocated to Application Software; interface: OEM/Customer Review Interface). | 3 | RFQX-CVS123-2-0216; RFQX-CVS123-2-0217; RFQX-CVS123-2-0326 | Clustered from 3 customer requirements allocated to 'Verification and Validation' / 'Security evidence and traceability' (e.g. RFQX-CVS123-2-0216, RFQX-CVS123-2-0217, RFQX-CVS123-2-0326). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Security evidence and traceability satisfies the linked customer requirement set and records any open customer assumption. | Medium | Verification and Validation | Security evidence and traceability | None | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS123-2-0216; RFQX-CVS123-2-0217; RFQX-CVS123-2-0326 Broad coverage justification: No exception justification recorded. |
| SSR-COM-009 | The ECU shall restrict and protect communication for Secure communication and freshness protection, exposing only OEM-agreed services and applying authenticity/integrity/freshness and boundary controls on allocated signals (IT / backend domain; allocated to Backend and IT Systems). | 27 | RFQX-CVS123-2-0241; RFQX-CVS154-0036; RFQX-CVS32-0025; RFQX-CVS32-0027; RFQX-CVS32-0028; RFQX-CVS32-0031; RFQX-CVS32-0033; RFQX-CVS32-0048; RFQX-CVS32-0080; RFQX-CVS32-0083; RFQX-CVS32-0084; RFQX-CVS32-0085; 15 additional linked customer requirements | Clustered from 27 customer requirements allocated to 'Secure Communication and Boundary Control' / 'Secure communication and freshness protection' (e.g. RFQX-CVS123-2-0241, RFQX-CVS154-0036, RFQX-CVS32-0025 …). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Secure communication and freshness protection satisfies the linked customer requirement set and records any open customer assumption. | High | Secure Communication and Boundary Control | Secure communication and freshness protection | OP-005 | BLOCKED BY CUSTOMER DECISION | TOO BROAD SYSTEM REQUIREMENT DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS123-2-0241; RFQX-CVS154-0036; RFQX-CVS32-0025; RFQX-CVS32-0027; RFQX-CVS32-0028; RFQX-CVS32-0031; RFQX-CVS32-0033; RFQX-CVS32-0048; RFQX-CVS32-0080; RFQX-CVS32-0083; RFQX-CVS32-0084; RFQX-CVS32-0085; RFQX-CVS32-0108; RFQX-CVS32-0109; RFQX-CVS32-0110; RFQX-CVS32-0119; RFQX-CVS32-0121; RFQX-CVS32-0122; RFQX-CVS32-0123; RFQX-CVS32-0124; RFQX-CVS32-0125; RFQX-CVS32-0126; RFQX-CVS32-0128; RFQX-CVS32-0130; RFQX-CVS32-0131; RFQX-CVS32-0147; RFQX-CVS32-0151 Broad coverage justification: No exception justification recorded. |
| SSR-DAI-005 | The ECU shall verify the authenticity and integrity of Security evidence and traceability data and reject manipulated or unauthenticated data (Software domain; allocated to Application Software; interface: OEM/Customer Review Interface). | 2 | RFQX-CVS123-2-0285; RFQX-CVS124-0370 | Clustered from 2 customer requirements allocated to 'Data Authenticity and Integrity Verification' / 'Security evidence and traceability' (e.g. RFQX-CVS123-2-0285, RFQX-CVS124-0370). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Security evidence and traceability satisfies the linked customer requirement set and records any open customer assumption. | Medium | Data Authenticity and Integrity Verification | Security evidence and traceability | None | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS123-2-0285; RFQX-CVS124-0370 Broad coverage justification: No exception justification recorded. |
| SSR-SDT-002 | The ECU shall protect security-relevant data transfer for Secure Data Transfer / Data Security Container using the agreed secured data transfer / data security container scheme (Hardware domain; allocated to Hardware Platform). | 1 | RFQX-CVS123-2-0350 | Clustered from 1 customer requirements allocated to 'Secure Data Transfer / Data Security Container' / 'Secure Data Transfer / Data Security Container' (e.g. RFQX-CVS123-2-0350). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Secure Data Transfer / Data Security Container satisfies the linked customer requirement set and records any open customer assumption. | Medium | Secure Data Transfer / Data Security Container | Secure Data Transfer / Data Security Container | None | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS123-2-0350 Broad coverage justification: No exception justification recorded. |
| SSR-RBAC-003 | The ECU shall enforce authenticated, role-authorised access for Secure Diagnostics / RBAC, restricting security-relevant diagnostic services per the OEM-agreed role model (IT / backend domain; allocated to Backend and IT Systems). | 15 | RFQX-CVS124-0083; RFQX-CVS151-0019; RFQX-CVS151-0030; RFQX-CVS151-0035; RFQX-CVS151-0037; RFQX-CVS151-0040; RFQX-CVS151-0041; RFQX-CVS151-0062; RFQX-CVS151-0074; RFQX-CVS151-0075; RFQX-CVS151-0086; RFQX-CVS151-0088; 3 additional linked customer requirements | Clustered from 15 customer requirements allocated to 'Secure Diagnostics / RBAC' / 'Secure Diagnostics / RBAC' (e.g. RFQX-CVS124-0083, RFQX-CVS151-0019, RFQX-CVS151-0030 …). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Secure Diagnostics / RBAC satisfies the linked customer requirement set and records any open customer assumption. | High | Secure Diagnostics / RBAC | Secure Diagnostics / RBAC | OP-002 | BLOCKED BY CUSTOMER DECISION | TOO BROAD SYSTEM REQUIREMENT DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS124-0083; RFQX-CVS151-0019; RFQX-CVS151-0030; RFQX-CVS151-0035; RFQX-CVS151-0037; RFQX-CVS151-0040; RFQX-CVS151-0041; RFQX-CVS151-0062; RFQX-CVS151-0074; RFQX-CVS151-0075; RFQX-CVS151-0086; RFQX-CVS151-0088; RFQX-CVS31-0093; RFQX-CVS31-0095; RFQX-CVS31-0098 Broad coverage justification: No exception justification recorded. |
| SSR-RBAC-004 | The ECU shall enforce authenticated, role-authorised access for Secure Diagnostics / RBAC, restricting security-relevant diagnostic services per the OEM-agreed role model (Software domain; allocated to Application Software). | 11 | RFQX-CVS124-0084; RFQX-CVS124-0135; RFQX-CVS124-0305; RFQX-CVS124-0306; RFQX-CVS124-0307; RFQX-CVS151-0068; RFQX-CVS151-0071; RFQX-CVS151-0085; RFQX-CVS31-0042; RFQX-CVS31-0066; RFQX-CVS31-0143 | Clustered from 11 customer requirements allocated to 'Secure Diagnostics / RBAC' / 'Secure Diagnostics / RBAC' (e.g. RFQX-CVS124-0084, RFQX-CVS124-0135, RFQX-CVS124-0305 …). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Secure Diagnostics / RBAC satisfies the linked customer requirement set and records any open customer assumption. | High | Secure Diagnostics / RBAC | Secure Diagnostics / RBAC | OP-002 | BLOCKED BY CUSTOMER DECISION | TOO BROAD SYSTEM REQUIREMENT DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS124-0084; RFQX-CVS124-0135; RFQX-CVS124-0305; RFQX-CVS124-0306; RFQX-CVS124-0307; RFQX-CVS151-0068; RFQX-CVS151-0071; RFQX-CVS151-0085; RFQX-CVS31-0042; RFQX-CVS31-0066; RFQX-CVS31-0143 Broad coverage justification: No exception justification recorded. |
| SSR-DIAG-003 | The ECU shall provide the diagnostic services for Diagnostic Services required by the allocated customer requirements, including the specified services, sessions and data identifiers (System domain; allocated to System Core; interface: OEM/Customer Review Interface). | 10 | RFQX-CVS124-0087; RFQX-CVS124-0203; RFQX-CVS124-0242; RFQX-CVS124-0400; RFQX-CVS124-0407; RFQX-CVS124-0408; RFQX-CVS124-0409; RFQX-CVS124-0415; RFQX-CVS124-0416; RFQX-CVS124-0418 | Clustered from 10 customer requirements allocated to 'Diagnostic Services' / 'Diagnostic Services' (e.g. RFQX-CVS124-0087, RFQX-CVS124-0203, RFQX-CVS124-0242 …). Linked source table/diagram context was considered. | Test + table/diagram context review | Test + table/diagram context review evidence demonstrates that Diagnostic Services satisfies the linked customer requirement set and records any open customer assumption. | High | Diagnostic Services | Diagnostic Services | None | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS124-0087; RFQX-CVS124-0203; RFQX-CVS124-0242; RFQX-CVS124-0400; RFQX-CVS124-0407; RFQX-CVS124-0408; RFQX-CVS124-0409; RFQX-CVS124-0415; RFQX-CVS124-0416; RFQX-CVS124-0418 Broad coverage justification: No exception justification recorded. |
| SSR-DIAG-004 | The ECU shall provide the diagnostic services for Diagnostic Services required by the allocated customer requirements, including the specified services, sessions and data identifiers (Process / compliance domain; allocated to Compliance Process). | 13 | RFQX-CVS124-0146; RFQX-CVS124-0223; RFQX-CVS124-0226; RFQX-CVS124-0229; RFQX-CVS124-0230; RFQX-CVS124-0232; RFQX-CVS124-0233; RFQX-CVS124-0234; RFQX-CVS124-0235; RFQX-CVS124-0236; RFQX-CVS124-0251; RFQX-CVS124-0252; 1 additional linked customer requirements | Clustered from 13 customer requirements allocated to 'Diagnostic Services' / 'Diagnostic Services' (e.g. RFQX-CVS124-0146, RFQX-CVS124-0223, RFQX-CVS124-0226 …). Linked source table/diagram context was considered. | Test + table/diagram context review | Test + table/diagram context review evidence demonstrates that Diagnostic Services satisfies the linked customer requirement set and records any open customer assumption. | High | Diagnostic Services | Diagnostic Services | None | BLOCKED BY CUSTOMER DECISION | TOO BROAD SYSTEM REQUIREMENT DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS124-0146; RFQX-CVS124-0223; RFQX-CVS124-0226; RFQX-CVS124-0229; RFQX-CVS124-0230; RFQX-CVS124-0232; RFQX-CVS124-0233; RFQX-CVS124-0234; RFQX-CVS124-0235; RFQX-CVS124-0236; RFQX-CVS124-0251; RFQX-CVS124-0252; RFQX-CVS124-0256 Broad coverage justification: No exception justification recorded. |
| SSR-DIAG-005 | The ECU shall provide the diagnostic services for Diagnostic Services required by the allocated customer requirements, including the specified services, sessions and data identifiers (Hardware domain; allocated to Hardware Platform). | 1 | RFQX-CVS124-0201 | Clustered from 1 customer requirements allocated to 'Diagnostic Services' / 'Diagnostic Services' (e.g. RFQX-CVS124-0201). Linked source table/diagram context was considered. | Test + table/diagram context review | Test + table/diagram context review evidence demonstrates that Diagnostic Services satisfies the linked customer requirement set and records any open customer assumption. | Medium | Diagnostic Services | Diagnostic Services | None | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS124-0201 Broad coverage justification: No exception justification recorded. |
| SSR-DIAG-006 | The ECU shall provide the diagnostic services for Diagnostic Services required by the allocated customer requirements, including the specified services, sessions and data identifiers (Software domain; allocated to Application Software). | 4 | RFQX-CVS124-0207; RFQX-CVS124-0238; RFQX-CVS31-0111; RFQX-CVS31-0119 | Clustered from 4 customer requirements allocated to 'Diagnostic Services' / 'Diagnostic Services' (e.g. RFQX-CVS124-0207, RFQX-CVS124-0238, RFQX-CVS31-0111 …). Linked source table/diagram context was considered. | Test + table/diagram context review | Test + table/diagram context review evidence demonstrates that Diagnostic Services satisfies the linked customer requirement set and records any open customer assumption. | High | Diagnostic Services | Diagnostic Services | OP-002 | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS124-0207; RFQX-CVS124-0238; RFQX-CVS31-0111; RFQX-CVS31-0119 Broad coverage justification: No exception justification recorded. |
| SSR-DAI-006 | The ECU shall verify the authenticity and integrity of Security evidence and traceability data and reject manipulated or unauthenticated data (IT / backend domain; allocated to Backend and IT Systems; interface: OEM/Customer Review Interface). | 5 | RFQX-CVS124-0362; RFQX-CVS124-0365; RFQX-CVS31-0046; RFQX-CVS31-0061; RFQX-CVS31-0062 | Clustered from 5 customer requirements allocated to 'Data Authenticity and Integrity Verification' / 'Security evidence and traceability' (e.g. RFQX-CVS124-0362, RFQX-CVS124-0365, RFQX-CVS31-0046 …). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Security evidence and traceability satisfies the linked customer requirement set and records any open customer assumption. | High | Data Authenticity and Integrity Verification | Security evidence and traceability | OP-004 | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS124-0362; RFQX-CVS124-0365; RFQX-CVS31-0046; RFQX-CVS31-0061; RFQX-CVS31-0062 Broad coverage justification: No exception justification recorded. |
| SSR-DAI-007 | The ECU shall verify the authenticity and integrity of Security evidence and traceability data and reject manipulated or unauthenticated data (System domain; allocated to System Core; interface: OEM/Customer Review Interface). | 2 | RFQX-CVS124-0369; RFQX-CVS124-0371 | Clustered from 2 customer requirements allocated to 'Data Authenticity and Integrity Verification' / 'Security evidence and traceability' (e.g. RFQX-CVS124-0369, RFQX-CVS124-0371). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Security evidence and traceability satisfies the linked customer requirement set and records any open customer assumption. | Medium | Data Authenticity and Integrity Verification | Security evidence and traceability | None | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS124-0369; RFQX-CVS124-0371 Broad coverage justification: No exception justification recorded. |
| SSR-TOOL-004 | The supplier shall provide the tooling, IT infrastructure and evidence storage required for Tooling / IT / Evidence Storage (System domain; allocated to System Core; interface: OEM/Customer Review Interface). | 4 | RFQX-CVS124-0434; RFQX-CVS124-0438; RFQX-CVS124-0439; RFQX-CVS31-0031 | Clustered from 4 customer requirements allocated to 'Tooling / IT / Evidence Storage' / 'Tooling / IT / Evidence Storage' (e.g. RFQX-CVS124-0434, RFQX-CVS124-0438, RFQX-CVS124-0439 …). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Tooling / IT / Evidence Storage satisfies the linked customer requirement set and records any open customer assumption. | High | Tooling / IT / Evidence Storage | Tooling / IT / Evidence Storage | None | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS124-0434; RFQX-CVS124-0438; RFQX-CVS124-0439; RFQX-CVS31-0031 Broad coverage justification: No exception justification recorded. |
| SSR-RBAC-005 | The ECU shall enforce authenticated, role-authorised access for Secure Diagnostics / RBAC, restricting security-relevant diagnostic services per the OEM-agreed role model (System domain; allocated to System Core). | 2 | RFQX-CVS151-0011; RFQX-CVS151-0078 | Clustered from 2 customer requirements allocated to 'Secure Diagnostics / RBAC' / 'Secure Diagnostics / RBAC' (e.g. RFQX-CVS151-0011, RFQX-CVS151-0078). | Review + Test | Review + Test evidence demonstrates that Secure Diagnostics / RBAC satisfies the linked customer requirement set and records any open customer assumption. | High | Secure Diagnostics / RBAC | Secure Diagnostics / RBAC | None | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS151-0011; RFQX-CVS151-0078 Broad coverage justification: No exception justification recorded. |
| SSR-RBAC-006 | The ECU shall enforce authenticated, role-authorised access for Secure communication and freshness protection, restricting security-relevant diagnostic services per the OEM-agreed role model (Software domain; allocated to Application Software). | 2 | RFQX-CVS31-0014; RFQX-CVS32-0057 | Clustered from 2 customer requirements allocated to 'Secure Diagnostics / RBAC' / 'Secure communication and freshness protection' (e.g. RFQX-CVS31-0014, RFQX-CVS32-0057). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Secure communication and freshness protection satisfies the linked customer requirement set and records any open customer assumption. | High | Secure Diagnostics / RBAC | Secure communication and freshness protection | OP-002 | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS31-0014; RFQX-CVS32-0057 Broad coverage justification: No exception justification recorded. |
| SSR-KEY-002 | The ECU shall manage key and certificate material for Key and Certificate Handling across provisioning, storage, use, renewal and revocation per the agreed key lifecycle (System domain; allocated to System Core). | 5 | RFQX-CVS31-0016; RFQX-CVS31-0026; RFQX-CVS31-0029; RFQX-CVS31-0077; RFQX-CVS31-0137 | Clustered from 5 customer requirements allocated to 'Key and Certificate Handling' / 'Key and Certificate Handling' (e.g. RFQX-CVS31-0016, RFQX-CVS31-0026, RFQX-CVS31-0029 …). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Key and Certificate Handling satisfies the linked customer requirement set and records any open customer assumption. | High | Key and Certificate Handling | Key and Certificate Handling | None | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS31-0016; RFQX-CVS31-0026; RFQX-CVS31-0029; RFQX-CVS31-0077; RFQX-CVS31-0137 Broad coverage justification: No exception justification recorded. |
| SSR-KEY-003 | The ECU shall manage key and certificate material for Key and Certificate Handling across provisioning, storage, use, renewal and revocation per the agreed key lifecycle (IT / backend domain; allocated to Backend and IT Systems). | 6 | RFQX-CVS31-0019; RFQX-CVS31-0027; RFQX-CVS31-0028; RFQX-CVS31-0036; RFQX-CVS31-0038; RFQX-CVS31-0156 | Clustered from 6 customer requirements allocated to 'Key and Certificate Handling' / 'Key and Certificate Handling' (e.g. RFQX-CVS31-0019, RFQX-CVS31-0027, RFQX-CVS31-0028 …). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Key and Certificate Handling satisfies the linked customer requirement set and records any open customer assumption. | High | Key and Certificate Handling | Key and Certificate Handling | OP-003 | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS31-0019; RFQX-CVS31-0027; RFQX-CVS31-0028; RFQX-CVS31-0036; RFQX-CVS31-0038; RFQX-CVS31-0156 Broad coverage justification: No exception justification recorded. |
| SSR-DAI-008 | The ECU shall verify the authenticity and integrity of Data Authenticity and Integrity Verification data and reject manipulated or unauthenticated data (System domain; allocated to System Core). | 3 | RFQX-CVS31-0033; RFQX-CVS31-0056; RFQX-CVS31-0105 | Clustered from 3 customer requirements allocated to 'Data Authenticity and Integrity Verification' / 'Data Authenticity and Integrity Verification' (e.g. RFQX-CVS31-0033, RFQX-CVS31-0056, RFQX-CVS31-0105). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Data Authenticity and Integrity Verification satisfies the linked customer requirement set and records any open customer assumption. | Medium | Data Authenticity and Integrity Verification | Data Authenticity and Integrity Verification | None | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS31-0033; RFQX-CVS31-0056; RFQX-CVS31-0105 Broad coverage justification: No exception justification recorded. |
| SSR-KEY-004 | The ECU shall manage key and certificate material for Secure communication and freshness protection across provisioning, storage, use, renewal and revocation per the agreed key lifecycle (Cybersecurity domain; allocated to Security Services; security capability: Key management). | 7 | RFQX-CVS32-0007; RFQX-CVS32-0051; RFQX-CVS32-0056; RFQX-CVS32-0065; RFQX-CVS32-0066; RFQX-CVS32-0068; RFQX-CVS32-0095 | Clustered from 7 customer requirements allocated to 'Key and Certificate Handling' / 'Secure communication and freshness protection' (e.g. RFQX-CVS32-0007, RFQX-CVS32-0051, RFQX-CVS32-0056 …). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Secure communication and freshness protection satisfies the linked customer requirement set and records any open customer assumption. | High | Key and Certificate Handling | Secure communication and freshness protection | OP-004;OP-005 | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS32-0007; RFQX-CVS32-0051; RFQX-CVS32-0056; RFQX-CVS32-0065; RFQX-CVS32-0066; RFQX-CVS32-0068; RFQX-CVS32-0095 Broad coverage justification: No exception justification recorded. |
| SSR-COM-010 | The ECU shall restrict and protect communication for Secure communication and freshness protection, exposing only OEM-agreed services and applying authenticity/integrity/freshness and boundary controls on allocated signals (System domain; allocated to System Core). | 18 | RFQX-CVS32-0009; RFQX-CVS32-0012; RFQX-CVS32-0040; RFQX-CVS32-0046; RFQX-CVS32-0053; RFQX-CVS32-0069; RFQX-CVS32-0070; RFQX-CVS32-0077; RFQX-CVS32-0096; RFQX-CVS32-0099; RFQX-CVS32-0103; RFQX-CVS32-0140; 6 additional linked customer requirements | Clustered from 18 customer requirements allocated to 'Secure Communication and Boundary Control' / 'Secure communication and freshness protection' (e.g. RFQX-CVS32-0009, RFQX-CVS32-0012, RFQX-CVS32-0040 …). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Secure communication and freshness protection satisfies the linked customer requirement set and records any open customer assumption. | High | Secure Communication and Boundary Control | Secure communication and freshness protection | None | BLOCKED BY CUSTOMER DECISION | TOO BROAD SYSTEM REQUIREMENT DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS32-0009; RFQX-CVS32-0012; RFQX-CVS32-0040; RFQX-CVS32-0046; RFQX-CVS32-0053; RFQX-CVS32-0069; RFQX-CVS32-0070; RFQX-CVS32-0077; RFQX-CVS32-0096; RFQX-CVS32-0099; RFQX-CVS32-0103; RFQX-CVS32-0140; RFQX-CVS32-0141; RFQX-CVS32-0142; RFQX-CVS32-0143; RFQX-CVS32-0144; RFQX-CVS32-0145; RFQX-CVS32-0146 Broad coverage justification: No exception justification recorded. |
| SSR-RBAC-007 | The ECU shall enforce authenticated, role-authorised access for Secure communication and freshness protection, restricting security-relevant diagnostic services per the OEM-agreed role model (Cybersecurity domain; allocated to Security Services; security capability: Authentication). | 1 | RFQX-CVS32-0016 | Clustered from 1 customer requirements allocated to 'Secure Diagnostics / RBAC' / 'Secure communication and freshness protection' (e.g. RFQX-CVS32-0016). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Secure communication and freshness protection satisfies the linked customer requirement set and records any open customer assumption. | High | Secure Diagnostics / RBAC | Secure communication and freshness protection | OP-002 | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS32-0016 Broad coverage justification: No exception justification recorded. |
| SSR-COM-011 | The ECU shall restrict and protect communication for Secure communication and freshness protection, exposing only OEM-agreed services and applying authenticity/integrity/freshness and boundary controls on allocated signals (Software domain; allocated to Application Software). | 5 | RFQX-CVS32-0019; RFQX-CVS32-0058; RFQX-CVS32-0059; RFQX-CVS32-0064; RFQX-CVS32-0091 | Clustered from 5 customer requirements allocated to 'Secure Communication and Boundary Control' / 'Secure communication and freshness protection' (e.g. RFQX-CVS32-0019, RFQX-CVS32-0058, RFQX-CVS32-0059 …). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Secure communication and freshness protection satisfies the linked customer requirement set and records any open customer assumption. | High | Secure Communication and Boundary Control | Secure communication and freshness protection | OP-005 | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS32-0019; RFQX-CVS32-0058; RFQX-CVS32-0059; RFQX-CVS32-0064; RFQX-CVS32-0091 Broad coverage justification: No exception justification recorded. |
| SSR-VV-004 | The supplier shall verify and validate Secure communication and freshness protection per the agreed cybersecurity verification and validation plan (IT / backend domain; allocated to Backend and IT Systems; interface: OEM/Customer Review Interface). | 1 | RFQX-CVS32-0054 | Clustered from 1 customer requirements allocated to 'Verification and Validation' / 'Secure communication and freshness protection' (e.g. RFQX-CVS32-0054). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Secure communication and freshness protection satisfies the linked customer requirement set and records any open customer assumption. | High | Verification and Validation | Secure communication and freshness protection | OP-005 | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS32-0054 Broad coverage justification: No exception justification recorded. |
| SSR-DAI-009 | The ECU shall verify the authenticity and integrity of Secure communication and freshness protection data and reject manipulated or unauthenticated data (Cybersecurity domain; allocated to Security Services; security capability: Authentication). | 6 | RFQX-CVS32-0073; RFQX-CVS32-0082; RFQX-CVS32-0092; RFQX-CVS32-0093; RFQX-CVS32-0133; RFQX-CVS32-0139 | Clustered from 6 customer requirements allocated to 'Data Authenticity and Integrity Verification' / 'Secure communication and freshness protection' (e.g. RFQX-CVS32-0073, RFQX-CVS32-0082, RFQX-CVS32-0092 …). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Secure communication and freshness protection satisfies the linked customer requirement set and records any open customer assumption. | High | Data Authenticity and Integrity Verification | Secure communication and freshness protection | OP-005 | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS32-0073; RFQX-CVS32-0082; RFQX-CVS32-0092; RFQX-CVS32-0093; RFQX-CVS32-0133; RFQX-CVS32-0139 Broad coverage justification: No exception justification recorded. |
| SSR-COM-012 | The ECU shall restrict and protect communication for OEM/Customer Review Interface, exposing only OEM-agreed services and applying authenticity/integrity/freshness and boundary controls on allocated signals (IT / backend domain; allocated to Backend and IT Systems; interface: OEM/Customer Review Interface). | 1 | RFQX-CVS32-0106 | Clustered from 1 customer requirements allocated to 'Secure Communication and Boundary Control' / 'OEM/Customer Review Interface' (e.g. RFQX-CVS32-0106). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that OEM/Customer Review Interface satisfies the linked customer requirement set and records any open customer assumption. | High | Secure Communication and Boundary Control | OEM/Customer Review Interface | OP-005 | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS32-0106 Broad coverage justification: No exception justification recorded. |
| SSR-COM-013 | The ECU shall restrict and protect communication for Secure communication and freshness protection, exposing only OEM-agreed services and applying authenticity/integrity/freshness and boundary controls on allocated signals (Cybersecurity domain; allocated to Security Services; security capability: Secure communication). | 1 | RFQX-CVS32-0120 | Clustered from 1 customer requirements allocated to 'Secure Communication and Boundary Control' / 'Secure communication and freshness protection' (e.g. RFQX-CVS32-0120). Linked source table/diagram context was considered. | Review + Test + table/diagram context review | Review + Test + table/diagram context review evidence demonstrates that Secure communication and freshness protection satisfies the linked customer requirement set and records any open customer assumption. | High | Secure Communication and Boundary Control | Secure communication and freshness protection | OP-005 | BLOCKED BY CUSTOMER DECISION | DERIVED ACCEPTANCE CRITERIALinked customer requirementsRFQX-CVS32-0120 Broad coverage justification: No exception justification recorded. |
Missing Customer Requirement Coverage
This table is horizontally scrollable. Use the bottom scrollbar to view all columns.
| Customer Requirement | Statement | Status |
|---|---|---|
| RFQX-3299216-1-0069 | 100ms after reaching 2 mm from target, the maximum position error should be ±0.1mm. | MISSING SYSTEM REQUIREMENT |
| RFQX-3299216-1-0303 | and 5.2. | MISSING SYSTEM REQUIREMENT |
Engineering Quality Analysis
1 grouped duplicate/near-duplicate SSR issue(s) require consolidation.
Counts by Issue Type
| Issue Type | Count |
|---|---|
| DUPLICATE | 1 |
| INCOMPLETE | 1 |
| NEEDS_ENGINEERING_DECISION | 1 |
| NEEDS_SOURCE_CLARIFICATION | 1 |
| NOT_TESTABLE | 1 |
| WEAK | 1 |
Duplicate / Near-Duplicate SSR Groups
This table is horizontally scrollable. Use the bottom scrollbar to view all columns.
| Finding | Issue | Affected SSR IDs | Recommendation | Confidence | Details |
|---|---|---|---|---|---|
| SSR-DUP-001 | DUPLICATE | Consolidate the repeated SSRs into one requirement with all affected source IDs, or rewrite each retained SSR with a unique engineering obligation and acceptance criterion. | high | Engineering detailReasoning: Duplicate / near-duplicate requirement detected across SSR-CON-001, SSR-CON-002. The SSR text is identical or materially equivalent, so separate rows do not express distinct behavior, interfaces, constraints, failure handling, or acceptance criteria. Impact: Reviewers see repeated analysis blocks and cannot tell whether the scope is one requirement repeated or several distinct engineering obligations. Recommendation: Consolidate the repeated SSRs into one requirement with all affected source IDs, or rewrite each retained SSR with a unique engineering obligation and acceptance criterion. Improved wording: Replace the repeated SSR text with one consolidated Cybersecurity Concept and Evidence requirement for Security evidence and traceability on OEM/Customer Review Interface, or rewrite each retained SSR so it states the distinct behavior, interface, constraint, failure behavior, and acceptance criterion that makes it unique. Canonical statement: The supplier shall produce and maintain the cybersecurity concept and verification evidence covering Security evidence and traceability (Cybersecurity domain; allocated to Security Services; security capability: Cybersecurity requirement handling; interface: OEM/Customer Review Interface). Source customer IDs: RFQX-1001379436-P10-000-01-0007, RFQX-1001379436-P10-000-01-0012, RFQX-1001379436-P10-000-01-0013, RFQX-1001379436-P10-000-01-0015, RFQX-1001379436-P10-000-01-0017, RFQX-1001379436-P10-000-01-0018, RFQX-1001379436-P10-000-01-0019, RFQX-1001379436-P10-000-01-0024, RFQX-1001379436-P10-000-01-0027, RFQX-1001379436-P10-000-01-0037, RFQX-1001379436-P10-000-01-0044, RFQX-1001379436-P10-000-01-0045, RFQX-1001379436-P10-000-01-0046, RFQX-CVS123-2-0196, RFQX-CVS123-2-0201, RFQX-CVS123-2-0243 |
Grouped Engineering Findings
This table is horizontally scrollable. Use the bottom scrollbar to view all columns.
| Finding | Issue | Affected SSR IDs | Recommendation | Confidence | Details |
|---|---|---|---|---|---|
| SSR-IF-001 | INCOMPLETE | Allocate each SSR to the relevant diagnostic, update, communication, backend, or ECU interface, or mark the interface decision as an explicit open point. | high | Engineering detailReasoning: The affected interface-dependent SSRs do not identify a concrete interface allocation. Impact: Design ownership, integration scope, and verification setup remain underspecified. Recommendation: Allocate each SSR to the relevant diagnostic, update, communication, backend, or ECU interface, or mark the interface decision as an explicit open point. Improved wording: The ECU shall perform the Secure Communication and Boundary Control behavior with explicit inputs, outputs, timing or state constraints, failure handling, and pass/fail acceptance criteria traceable to the source IDs. | |
| SSR-TEST-001 | NOT_TESTABLE | Add acceptance criteria with test stimulus, expected ECU response, rejected or failure case, and required evidence. | medium | Engineering detailReasoning: The affected SSRs do not state measurable stimuli, expected responses, limits, or pass/fail conditions. Impact: Verification planning becomes subjective and risks late disputes over whether the requirement is satisfied. Recommendation: Add acceptance criteria with test stimulus, expected ECU response, rejected or failure case, and required evidence. Improved wording: The ECU shall provide Security evidence and traceability on OEM/Customer Review Interface with measurable acceptance criteria, including the stimulus, expected response, rejected/error cases, and required verification evidence. | |
| SSR-DEC-001 | NEEDS_ENGINEERING_DECISION | Keep these SSRs conditional in proposal and planning views until the linked decision is closed. | high | Engineering detailReasoning: The affected SSRs are blocked by customer clarification or an open point dependency. Impact: Treating these SSRs as committed scope would hide unresolved ownership, interface, or verification decisions. Recommendation: Keep these SSRs conditional in proposal and planning views until the linked decision is closed. Improved wording: Keep Data Authenticity and Integrity Verification conditional until the linked customer decision fixes ownership, interface assumptions, and verification responsibility. | |
| SSR-SRC-001 | NEEDS_SOURCE_CLARIFICATION | Add the controlling document, interface decision, lifecycle state, or customer open point to each affected SSR. | medium | Engineering detailReasoning: The affected SSRs rely on words such as agreed, defined, or specified without naming the controlling interface, profile, lifecycle state, or acceptance reference. Impact: The team cannot verify completeness until the controlling source or engineering decision is explicit. Recommendation: Add the controlling document, interface decision, lifecycle state, or customer open point to each affected SSR. Improved wording: Rewrite the Vulnerability and Incident Handling SSR for Vulnerability and Incident Handling on OEM/Customer Review Interface as a single observable SHALL statement with source constraints, responsible owner, and verification evidence. | |
| SSR-WEAK-001 | WEAK | Rewrite the SSR text so the behavior, signal/state scope, constraints, and expected outcome are visible in the SSR itself; keep source IDs as traceability, not as the requirement content. | high | Engineering detailReasoning: The affected SSRs delegate their real engineering content to upstream allocated requirements instead of stating the behavior directly. Impact: The SSR is not self-contained enough for implementation planning, supplier review, or verification scoping. Recommendation: Rewrite the SSR text so the behavior, signal/state scope, constraints, and expected outcome are visible in the SSR itself; keep source IDs as traceability, not as the requirement content. Improved wording: Rewrite the System Function SSR for System Function on OEM/Customer Review Interface as a single observable SHALL statement with source constraints, responsible owner, and verification evidence. |
Open Engineering Questions
This table is horizontally scrollable. Use the bottom scrollbar to view all columns.
| Issue | Affected SSR IDs | Question / Decision Needed |
|---|---|---|
| NEEDS_ENGINEERING_DECISION | Keep these SSRs conditional in proposal and planning views until the linked decision is closed. | |
| NEEDS_SOURCE_CLARIFICATION | Add the controlling document, interface decision, lifecycle state, or customer open point to each affected SSR. |