Supplier System Requirements
Review supplier-side system requirements derived from customer requirements and design decisions.
Supplier System Requirements
Review supplier-side system requirements derived from customer requirements and design decisions.
Executive Takeaway
Supplier System Requirements are derived many-to-many from accepted, accepted-with-assumption, and partially accepted customer requirements. The derivation is coverage-ready for proposal work, but blocked-by-clarification items must stay conditional until the customer closes the linked decisions.
- Use SSRs as supplier engineering scope candidates, not customer-approved contract text.
- Every customer requirement keeps a derivation disposition in the traceability matrix.
- Open gaps are explicit; do not hide unresolved responsibility allocation.
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. |
Status & Responsibility
| Status | Count |
|---|---|
| Candidate | 30 |
| Blocked by Customer Clarification | 24 |
| Ready for Customer Alignment | 15 |
| Ready for Internal Review | 2 |
| Responsibility | Count |
|---|---|
| Shared | 39 |
| Supplier-Owned | 32 |
Category Coverage Matrix
| Category | Customer Requirements | Derived SSRs | Coverage | Open Issues |
|---|---|---|---|---|
| System Function | 710 | 3 | 25.4% | 0 |
| Diagnostic Services | 99 | 6 | 31.3% | 1 |
| Secure Diagnostics / RBAC | 107 | 7 | 49.5% | 6 |
| Software Update / Flashing | 104 | 4 | 43.3% | 3 |
| Bootloader and Application State Handling | 61 | 4 | 14.8% | 0 |
| Secure Data Transfer / Data Security Container | 14 | 1 | 42.9% | 0 |
| Key and Certificate Handling | 77 | 4 | 46.8% | 3 |
| Secure Communication and Boundary Control | 257 | 13 | 40.9% | 7 |
| Data Authenticity and Integrity Verification | 53 | 9 | 75.5% | 4 |
| Security Logging and Event Handling | 2 | 1 | 50.0% | 0 |
| Vulnerability and Incident Handling | 9 | 4 | 88.9% | 1 |
| Cybersecurity Concept and Evidence | 29 | 3 | 58.6% | 0 |
| Lifecycle / Field Return / Decommissioning | 8 | 2 | 25.0% | 0 |
| Supplier Development and Production Hardening | 1 | 1 | 100.0% | 0 |
| Tooling / IT / Evidence Storage | 189 | 4 | 71.4% | 1 |
| Hardware / HSM / Secure Storage | 41 | 1 | 34.1% | 0 |
| Verification and Validation | 28 | 4 | 39.3% | 1 |
Supplier System Requirement Table
| SSR ID | Statement | Category | Security Capability | Derived From | Responsibility | Status | Details |
|---|---|---|---|---|---|---|---|
| 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). | Cybersecurity Concept and Evidence | Cybersecurity requirement handling | 4 | Supplier-Owned | Candidate | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Security evidence and traceability Security capability: Cybersecurity requirement handling Interface: OEM/Customer Review Interface Architecture: Security Services Verification: Review + Test + table/diagram context review Related document artifacts: TABLE-1001379436P1000001RDDM11-0002 Artifact context: TABLE-1001379436P1000001RDDM11-0002 (Table): Table 2: Abbreviated terms page 3 Derived from: RFQX-1001379436-P10-000-01-0007;RFQX-1001379436-P10-000-01-0017;RFQX-1001379436-P10-000-01-0018;RFQX-1001379436-P10-000-01-0019 |
| 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). | Vulnerability and Incident Handling | Vulnerability management | 2 | Supplier-Owned | Candidate | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Vulnerability and Incident Handling Security capability: Vulnerability management Interface: OEM/Customer Review Interface Architecture: Security Services Verification: Review + Test + table/diagram context review Related document artifacts: TABLE-1001379436P1000001RDDM11-0002 Artifact context: TABLE-1001379436P1000001RDDM11-0002 (Table): Table 2: Abbreviated terms page 3 Derived from: RFQX-1001379436-P10-000-01-0008;RFQX-1001379436-P10-000-01-0048 |
| 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). | Cybersecurity Concept and Evidence | Cybersecurity requirement handling | 12 | Shared | Ready for Customer Alignment | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Cybersecurity Concept and Evidence Security capability: Cybersecurity requirement handling Interface: OEM/Customer Review Interface Architecture: Security Services Verification: Review + Test + table/diagram context review Related document artifacts: TABLE-CVS1232-0003;TABLE-CVS1232-0004;TABLE-CVS1232-0012;TABLE-CVS1232-0013 Artifact context: TABLE-CVS1232-0003 (Table): Table 3: Services support due to SUV2 page 23 | TABLE-CVS1232-0004 (Table): Table 4: Routine identifiers for non-volatile memory access page 24 | TABLE-CVS1232-0012 (Table): Table 12: Routine Support per Diagnostic Session page 29 | TABLE-CVS1232-0013 (Table): Table 13: Routine Support per routineControlType page 30 Derived from: 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 |
| 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). | Cybersecurity Concept and Evidence | None | 1 | Supplier-Owned | Candidate | DetailsStatement: 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). Derivation rationale: Clustered from 1 customer requirements allocated to 'Cybersecurity Concept and Evidence' / 'Security evidence and traceability' (e.g. RFQX-1001379436-P10-000-01-0021). Allocated feature: Security evidence and traceability Security capability: None Interface: OEM/Customer Review Interface Architecture: Application Software Verification: Review + Test Related document artifacts: - Artifact context: - Derived from: RFQX-1001379436-P10-000-01-0021 |
| 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). | Hardware / HSM / Secure Storage | None | 14 | Shared | Ready for Customer Alignment | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Hardware / HSM / Secure Storage Security capability: None Interface: OEM/Customer Review Interface Architecture: Hardware Platform Verification: Review + Test + table/diagram context review Related document artifacts: DIAGRAM-CVS1232-0006;TABLE-CVS124-0029;TABLE-CVS124-0030;TABLE-CVS124-0041;TABLE-CVS124-0042;TABLE-CVS124-0043;TABLE-CVS124-0045;TABLE-CVS124-0063 Artifact context: DIAGRAM-CVS1232-0006 (Diagram): Figure 6: Erased-only bytes of a memory module page 41 | TABLE-CVS124-0029 (Table): Table 29 – Description of DID 0xF1A6 engineNumber page 19 | TABLE-CVS124-0030 (Table): Table 30 – Description of DID 0xF1A9 Lifetime ECU-runtime at software update stamp page 20 | TABLE-CVS124-0041 (Table): Table 41 lists reserved ECU DIDs/DID ranges which are not used for identification and which page 31 | TABLE-CVS124-0042 (Table): Table 41 – Data identifier (DID) ranges page 31 | TABLE-CVS124-0043 (Table): Table 42 – IVD DIDs page 31 Derived from: 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;RFQX-CVS124-0209;RFQX-CVS124-0270 |
| 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). | Data Authenticity and Integrity Verification | Authentication | 5 | Shared | Blocked by Customer Clarification | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Data Authenticity and Integrity Verification Security capability: Authentication Interface: OEM/Customer Review Interface Architecture: Security Services Verification: Review + Test + table/diagram context review Related document artifacts: TABLE-CVS31-0005 Artifact context: TABLE-CVS31-0005 (Table): Table 5 – verifyCertificateBidirectional Request page 8 | TABLE-CVS31-0005 (Table): Table 5 – verifyCertificateBidirectional Request page 8 Derived from: RFQX-1001379436-P10-000-01-0025;RFQX-CVS31-0017;RFQX-CVS31-0021;RFQX-CVS31-0073;RFQX-CVS31-0081 |
| 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). | System Function | None | 122 | Supplier-Owned | Candidate | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: System Function Security capability: None Interface: OEM/Customer Review Interface Architecture: System Core Verification: Test + table/diagram context review Related document artifacts: DIAGRAM-32992161-0003;DIAGRAM-32992161-0004;DIAGRAM-32992161-0005;DIAGRAM-32992161-0011;DIAGRAM-32992161-0012;DIAGRAM-CVS124-0002;DIAGRAM-CVS154-0005;DIAGRAM-CVS154-0007;DIAGRAM-CVS31-0003;DIAGRAM-CVS31-0004;TABLE-CVS1232-0003;TABLE-CVS1232-0020;TABLE-CVS1232-0021;TABLE-CVS1232-0022;TABLE-CVS1232-0023;TABLE-CVS124-0004;TABLE-CVS124-0005;TABLE-CVS124-0013;TABLE-CVS124-0014;TABLE-CVS124-0041 Artifact context: DIAGRAM-32992161-0003 (Diagram): Figure 3 - Pushrod positions page 8 | DIAGRAM-32992161-0004 (Diagram): Figure 4 – ISO view of 3d envelope. (all parts not shown) page 9 | DIAGRAM-32992161-0005 (Diagram): Figure 5 - Gearbox flange page 10 Derived from: 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;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;RFQX-CVS124-0334;RFQX-CVS124-0338;RFQX-CVS124-0350;RFQX-CVS124-0356;RFQX-CVS124-0367;RFQX-CVS124-0372;RFQX-CVS124-0373;RFQX-CVS124-0376;RFQX-CVS124-0383;RFQX-CVS124-0390;RFQX-CVS124-0402;RFQX-CVS124-0403;RFQX-CVS124-0404;RFQX-CVS124-0405;RFQX-CVS124-0410;RFQX-CVS124-0412;RFQX-CVS124-0417;RFQX-CVS124-0420;RFQX-CVS124-0421;RFQX-CVS124-0427;RFQX-CVS124-0435;RFQX-CVS151-0051;RFQX-CVS154-0031;RFQX-CVS154-0034;RFQX-CVS154-0037;RFQX-CVS154-0039;RFQX-CVS154-0041;RFQX-CVS31-0024;RFQX-CVS31-0040;RFQX-CVS31-0051;RFQX-CVS31-0054;RFQX-CVS31-0065;RFQX-CVS31-0084;RFQX-CVS31-0089;RFQX-CVS31-0100;RFQX-CVS31-0104;RFQX-CVS31-0138;RFQX-CVS31-0142;RFQX-CVS31-0146;RFQX-CVS31-0152;RFQX-CVS31-0155;RFQX-CVS31-0160 |
| 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). | Supplier Development and Production Hardening | None | 1 | Supplier-Owned | Candidate | DetailsStatement: 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). Derivation rationale: 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). Allocated feature: Supplier Development and Production Hardening Security capability: None Interface: None Architecture: Hardware Platform Verification: Review + Test Related document artifacts: - Artifact context: - Derived from: RFQX-1001379436-P10-000-01-0029 |
| 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). | Secure Communication and Boundary Control | None | 2 | Shared | Ready for Customer Alignment | DetailsStatement: 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). Derivation rationale: 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). Allocated feature: OEM/Customer Review Interface Security capability: None Interface: OEM/Customer Review Interface Architecture: Hardware Platform Verification: Review + Test Related document artifacts: - Artifact context: - Derived from: RFQX-1001379436-P10-000-01-0030;RFQX-1001379436-P10-000-01-0036 |
| 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). | Secure Communication and Boundary Control | None | 4 | Supplier-Owned | Candidate | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Secure Communication and Boundary Control Security capability: None Interface: None Architecture: System Core Verification: Review + Test + table/diagram context review Related document artifacts: TABLE-CVS1232-0004;TABLE-CVS1232-0020;TABLE-CVS1232-0021;TABLE-CVS124-0047 Artifact context: TABLE-CVS1232-0004 (Table): Table 4: Routine identifiers for non-volatile memory access page 24 | TABLE-CVS1232-0020 (Table): Table 20: Routine 0xFF00 addressAndLengthFormatIdentifier Format page 34 | TABLE-CVS1232-0021 (Table): Table 21: Module to Index Mapping page 34 | TABLE-CVS124-0047 (Table): Table 46 – Service 0x11 negative response codes page 35 Derived from: RFQX-1001379436-P10-000-01-0031;RFQX-1001379436-P10-000-01-0034;RFQX-CVS123-2-0173;RFQX-CVS124-0172 |
| 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). | Secure Communication and Boundary Control | None | 1 | Supplier-Owned | Candidate | DetailsStatement: 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). Derivation rationale: Clustered from 1 customer requirements allocated to 'Secure Communication and Boundary Control' / 'OEM/Customer Review Interface' (e.g. RFQX-1001379436-P10-000-01-0032). Allocated feature: OEM/Customer Review Interface Security capability: None Interface: OEM/Customer Review Interface Architecture: System Core Verification: Review + Test Related document artifacts: - Artifact context: - Derived from: RFQX-1001379436-P10-000-01-0032 |
| 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). | Key and Certificate Handling | Certificate handling | 18 | Shared | Blocked by Customer Clarification | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Key and Certificate Handling Security capability: Certificate handling Interface: OEM/Customer Review Interface Architecture: Security Services Verification: Review + Test + table/diagram context review Related document artifacts: DIAGRAM-CVS151-0004;DIAGRAM-CVS31-0003;TABLE-CVS124-0045;TABLE-CVS124-0046;TABLE-CVS151-0003 Artifact context: TABLE-CVS124-0045 (Table): Table 44 – Service 0x11 request parameter resetType description page 34 | TABLE-CVS124-0046 (Table): Table 45 – Service 0x11 positive response parameter description page 34 | TABLE-CVS151-0003 (Table): Table 3 – RID Rule Setting page 11 | DIAGRAM-CVS151-0004 (Diagram): Figure 3 shows the interaction between the diagnostics server and the RBAC enforcer logic. page 12 Derived from: 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;RFQX-CVS31-0083;RFQX-CVS31-0088;RFQX-CVS31-0101;RFQX-CVS31-0102;RFQX-CVS31-0103;RFQX-CVS31-0106 |
| 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). | Vulnerability and Incident Handling | None | 3 | Supplier-Owned | Candidate | DetailsStatement: 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). Derivation rationale: 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). Allocated feature: Vulnerability and Incident Handling Security capability: None Interface: OEM/Customer Review Interface Architecture: Compliance Process Verification: Review + Test Related document artifacts: - Artifact context: - Derived from: RFQX-1001379436-P10-000-01-0047;RFQX-1001379436-P10-000-01-0049;RFQX-1001379436-P10-000-01-0050 |
| 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). | Vulnerability and Incident Handling | None | 2 | Shared | Ready for Customer Alignment | DetailsStatement: 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). Derivation rationale: 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). Allocated feature: Vulnerability and Incident Handling Security capability: None Interface: OEM/Customer Review Interface Architecture: System Core Verification: Review + Test Related document artifacts: - Artifact context: - Derived from: RFQX-1001379436-P10-000-01-0054;RFQX-1001379436-P10-000-01-0055 |
| 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). | Vulnerability and Incident Handling | None | 1 | Supplier-Owned | Candidate | DetailsStatement: 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). Derivation rationale: Clustered from 1 customer requirements allocated to 'Vulnerability and Incident Handling' / 'Vulnerability and Incident Handling' (e.g. RFQX-1001379436-P10-000-01-0058). Allocated feature: Vulnerability and Incident Handling Security capability: None Interface: External Interfaces Architecture: External Interfaces Verification: Review + Test Related document artifacts: - Artifact context: - Derived from: RFQX-1001379436-P10-000-01-0058 |
| 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). | Lifecycle / Field Return / Decommissioning | None | 1 | Supplier-Owned | Ready for Internal Review | DetailsStatement: 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). Derivation rationale: Clustered from 1 customer requirements allocated to 'Lifecycle / Field Return / Decommissioning' / 'Lifecycle / Field Return / Decommissioning' (e.g. RFQX-1001379436-P10-000-01-0062). Allocated feature: Lifecycle / Field Return / Decommissioning Security capability: None Interface: None Architecture: Hardware Platform Verification: Review + Test Related document artifacts: - Artifact context: - Derived from: RFQX-1001379436-P10-000-01-0062 |
| 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). | Security Logging and Event Handling | Logging and audit trail | 1 | Supplier-Owned | Candidate | DetailsStatement: 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). Derivation rationale: 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). Allocated feature: Security Logging and Event Handling Security capability: Logging and audit trail Interface: None Architecture: Security Services Verification: Review + Test Related document artifacts: - Artifact context: - Derived from: RFQX-1001379436-P10-000-01-0067 |
| 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). | Secure Communication and Boundary Control | None | 11 | Shared | Blocked by Customer Clarification | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Secure Communication and Boundary Control Security capability: None Interface: None Architecture: Backend and IT Systems Verification: Review + Test + table/diagram context review Related document artifacts: TABLE-CVS31-0007;TABLE-CVS31-0010 Artifact context: TABLE-CVS31-0007 (Table): Table 7 – proofOfOwnership Request page 12 | TABLE-CVS31-0010 (Table): Table 10 – deAuthenticate response message layout page 15 Derived from: 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 |
| 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). | Data Authenticity and Integrity Verification | None | 1 | Supplier-Owned | Candidate | DetailsStatement: 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). Derivation rationale: Clustered from 1 customer requirements allocated to 'Data Authenticity and Integrity Verification' / 'Data Authenticity and Integrity Verification' (e.g. RFQX-3299216-1-0031). Allocated feature: Data Authenticity and Integrity Verification Security capability: None Interface: External Interfaces Architecture: External Interfaces Verification: Review + Test Related document artifacts: - Artifact context: - Derived from: RFQX-3299216-1-0031 |
| 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). | Tooling / IT / Evidence Storage | None | 1 | Supplier-Owned | Candidate | DetailsStatement: The supplier shall provide the tooling, IT infrastructure and evidence storage required for Tooling / IT / Evidence Storage (Tooling domain; allocated to Engineering Toolchain). Derivation rationale: Clustered from 1 customer requirements allocated to 'Tooling / IT / Evidence Storage' / 'Tooling / IT / Evidence Storage' (e.g. RFQX-3299216-1-0035). Allocated feature: Tooling / IT / Evidence Storage Security capability: None Interface: None Architecture: Engineering Toolchain Verification: Review + Test Related document artifacts: - Artifact context: - Derived from: RFQX-3299216-1-0035 |
| 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). | Data Authenticity and Integrity Verification | None | 8 | Shared | Ready for Customer Alignment | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Data Authenticity and Integrity Verification Security capability: None Interface: None Architecture: Backend and IT Systems Verification: Review + Test + table/diagram context review Related document artifacts: TABLE-CVS1232-0012;TABLE-CVS1232-0023;TABLE-CVS124-0094;TABLE-CVS31-0007 Artifact context: TABLE-CVS1232-0012 (Table): Table 12: Routine Support per Diagnostic Session page 29 | TABLE-CVS1232-0023 (Table): Table 23: Routine 0xFF01 Request Format page 35 | TABLE-CVS124-0094 (Table): Table 92 – RoutineIdentifier 0xFF01 description page 77 Derived from: 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 |
| 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). | Tooling / IT / Evidence Storage | None | 99 | Shared | Blocked by Customer Clarification | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Tooling / IT / Evidence Storage Security capability: None Interface: OEM/Customer Review Interface Architecture: Backend and IT Systems Verification: Review + Test + table/diagram context review Related document artifacts: DIAGRAM-32992161-0006;DIAGRAM-32992161-0007;DIAGRAM-32992161-0008;DIAGRAM-CVS1232-0003;DIAGRAM-CVS1232-0005;DIAGRAM-CVS1232-0006;DIAGRAM-CVS124-0002;DIAGRAM-CVS151-0010;DIAGRAM-CVS31-0007;TABLE-CVS1232-0004;TABLE-CVS1232-0005;TABLE-CVS1232-0006;TABLE-CVS1232-0007;TABLE-CVS1232-0008;TABLE-CVS1232-0009;TABLE-CVS1232-0010;TABLE-CVS1232-0011;TABLE-CVS1232-0015;TABLE-CVS1232-0016;TABLE-CVS1232-0017 Artifact context: DIAGRAM-32992161-0006 (Diagram): Figure 6 - Snap in tool space page 11 | DIAGRAM-32992161-0007 (Diagram): Figure 7 – Maximum disengage time page 13 | DIAGRAM-32992161-0008 (Diagram): Figure 8 - Maximum engage time page 14 | DIAGRAM-CVS1232-0003 (Diagram): Figure 3: Programming phase #1 – Programming step page 16 Derived from: 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;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;RFQX-CVS154-0046;RFQX-CVS31-0012;RFQX-CVS31-0022;RFQX-CVS31-0030;RFQX-CVS31-0043;RFQX-CVS31-0045;RFQX-CVS31-0058;RFQX-CVS31-0059;RFQX-CVS31-0063;RFQX-CVS31-0067;RFQX-CVS31-0068;RFQX-CVS31-0113;RFQX-CVS31-0120;RFQX-CVS31-0128;RFQX-CVS31-0133;RFQX-CVS31-0134;RFQX-CVS31-0147;RFQX-CVS31-0148;RFQX-CVS31-0151 |
| 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). | Secure Communication and Boundary Control | None | 3 | Shared | Blocked by Customer Clarification | DetailsStatement: 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). Derivation rationale: 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). Allocated feature: Secure Communication and Boundary Control Security capability: None Interface: None Architecture: Hardware Platform Verification: Review + Test Related document artifacts: - Artifact context: - Derived from: RFQX-3299216-1-0041;RFQX-3299216-1-0042;RFQX-3299216-1-0083 |
| 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). | Secure Communication and Boundary Control | None | 5 | Shared | Ready for Customer Alignment | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Secure Communication and Boundary Control Security capability: None Interface: None Architecture: Application Software Verification: Review + Test + table/diagram context review Related document artifacts: DIAGRAM-CVS31-0004;TABLE-CVS1232-0005;TABLE-CVS124-0047;TABLE-CVS124-0051;TABLE-CVS124-0052 Artifact context: TABLE-CVS1232-0005 (Table): Table 5: Service 0x34 Request Format page 25 | TABLE-CVS124-0047 (Table): Table 46 – Service 0x11 negative response codes page 35 | TABLE-CVS124-0051 (Table): Table 50 – Service 0x87 request parameter linkControlType description page 39 | TABLE-CVS124-0052 (Table): Table 51 – Service 0x87 request parameter linkControlModeIdentifier description page 39 Derived from: RFQX-3299216-1-0061;RFQX-CVS123-2-0211;RFQX-CVS124-0168;RFQX-CVS124-0198;RFQX-CVS31-0141 |
| 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). | System Function | None | 28 | Supplier-Owned | Candidate | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: System Function Security capability: None Interface: OEM/Customer Review Interface Architecture: Compliance Process Verification: Test + table/diagram context review Related document artifacts: DIAGRAM-32992161-0009;DIAGRAM-32992161-0010;TABLE-CVS124-0041;TABLE-CVS124-0042;TABLE-CVS124-0043;TABLE-CVS124-0044;TABLE-CVS124-0046;TABLE-CVS124-0047;TABLE-CVS124-0052;TABLE-CVS124-0053;TABLE-CVS124-0054;TABLE-CVS124-0055;TABLE-CVS124-0059;TABLE-CVS124-0060;TABLE-CVS124-0061;TABLE-CVS124-0062;TABLE-CVS124-0063;TABLE-CVS124-0070;TABLE-CVS124-0071;TABLE-CVS124-0072 Artifact context: DIAGRAM-32992161-0009 (Diagram): Figure 9 - Step response. page 16 | DIAGRAM-32992161-0010 (Diagram): Figure 9 - Step response page 16 | TABLE-CVS124-0041 (Table): Table 41 lists reserved ECU DIDs/DID ranges which are not used for identification and which page 31 | TABLE-CVS124-0042 (Table): Table 41 – Data identifier (DID) ranges page 31 | TABLE-CVS124-0043 (Table): Table 42 – IVD DIDs page 31 | TABLE-CVS124-0044 (Table): Table 43 – Service 0x10 request parameter diagnosticSessionType description page 32 Derived from: 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;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 |
| 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). | System Function | None | 30 | Supplier-Owned | Candidate | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: System Function Security capability: None Interface: OEM/Customer Review Interface Architecture: Application Software Verification: Test + table/diagram context review Related document artifacts: DIAGRAM-32992161-0020;DIAGRAM-CVS1232-0006;TABLE-CVS1232-0020;TABLE-CVS1232-0021;TABLE-CVS1232-0022;TABLE-CVS124-0038;TABLE-CVS124-0039;TABLE-CVS124-0045;TABLE-CVS124-0046;TABLE-CVS124-0050;TABLE-CVS124-0057;TABLE-CVS124-0058;TABLE-CVS124-0075;TABLE-CVS124-0076;TABLE-CVS124-0077;TABLE-CVS124-0078;TABLE-CVS124-0081;TABLE-CVS124-0082;TABLE-CVS124-0090;TABLE-CVS124-0091 Artifact context: DIAGRAM-32992161-0020 (Diagram): Figure 17 - Test procedure I page 41 | TABLE-CVS1232-0020 (Table): Table 20: Routine 0xFF00 addressAndLengthFormatIdentifier Format page 34 | TABLE-CVS1232-0021 (Table): Table 21: Module to Index Mapping page 34 | TABLE-CVS1232-0022 (Table): Table 22: Routine 0xFF00 routineStatus routineResult Format page 34 | DIAGRAM-CVS1232-0006 (Diagram): Figure 6: Erased-only bytes of a memory module page 41 Derived from: 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;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 |
| 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). | Secure Communication and Boundary Control | None | 26 | Supplier-Owned | Candidate | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: External Interfaces Security capability: None Interface: External Interfaces Architecture: External Interfaces Verification: Review + Test + table/diagram context review Related document artifacts: DIAGRAM-CVS32-0003;DIAGRAM-CVS32-0004;DIAGRAM-CVS32-0005;TABLE-CVS32-0002 Artifact context: DIAGRAM-CVS32-0003 (Diagram): Figure 2 – Anti-replay protection page 8 | DIAGRAM-CVS32-0004 (Diagram): Figure 3 – Anti-replay protection and transaction coherency page 9 | DIAGRAM-CVS32-0005 (Diagram): Figure 3 illustrates transaction coherency and the use of PREQTAG. To avoid mix-up, the page 9 | TABLE-CVS32-0002 (Table): Table 2 – Supported CipherSchemes page 10 Derived from: 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;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 |
| 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). | Secure Diagnostics / RBAC | Diagnostic security | 19 | Shared | Blocked by Customer Clarification | DetailsStatement: 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). Derivation rationale: Clustered from 19 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. Allocated feature: Secure Diagnostics / RBAC Security capability: Diagnostic security Interface: OEM/Customer Review Interface Architecture: Security Services Verification: Review + Test + table/diagram context review Related document artifacts: DIAGRAM-CVS1232-0005;TABLE-CVS1232-0003;TABLE-CVS1232-0012;TABLE-CVS124-0038;TABLE-CVS124-0039;TABLE-CVS124-0047;TABLE-CVS151-0001 Artifact context: TABLE-CVS1232-0003 (Table): Table 3: Services support due to SUV2 page 23 | TABLE-CVS1232-0012 (Table): Table 12: Routine Support per Diagnostic Session page 29 | DIAGRAM-CVS1232-0005 (Diagram): Figure 5: diagram for signing of software update results page 38 Derived from: 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;RFQX-CVS124-0078;RFQX-CVS124-0171;RFQX-CVS124-0186;RFQX-CVS124-0431;RFQX-CVS124-0432;RFQX-CVS151-0045;RFQX-CVS151-0083 |
| 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). | Verification and Validation | None | 2 | Supplier-Owned | Candidate | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Security evidence and traceability Security capability: None Interface: OEM/Customer Review Interface Architecture: System Core Verification: Review + Test + table/diagram context review Related document artifacts: DIAGRAM-CVS154-0004 Artifact context: DIAGRAM-CVS154-0004 (Diagram): Figure 3 – HashCmp page 6 Derived from: RFQX-3299216-1-0134;RFQX-CVS154-0021 |
| 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). | Diagnostic Services | None | 1 | Supplier-Owned | Candidate | DetailsStatement: 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). Derivation rationale: Clustered from 1 customer requirements allocated to 'Diagnostic Services' / 'Diagnostic Services' (e.g. RFQX-3299216-1-0135). Allocated feature: Diagnostic Services Security capability: None Interface: External Interfaces Architecture: External Interfaces Verification: Test Related document artifacts: - Artifact context: - Derived from: RFQX-3299216-1-0135 |
| 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). | Secure Communication and Boundary Control | None | 1 | Supplier-Owned | Candidate | DetailsStatement: 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). Derivation rationale: Clustered from 1 customer requirements allocated to 'Secure Communication and Boundary Control' / 'OEM/Customer Review Interface' (e.g. RFQX-3299216-1-0137). Allocated feature: OEM/Customer Review Interface Security capability: None Interface: OEM/Customer Review Interface Architecture: Application Software Verification: Review + Test Related document artifacts: - Artifact context: - Derived from: RFQX-3299216-1-0137 |
| 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). | Lifecycle / Field Return / Decommissioning | None | 1 | Supplier-Owned | Ready for Internal Review | DetailsStatement: 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). Derivation rationale: Clustered from 1 customer requirements allocated to 'Lifecycle / Field Return / Decommissioning' / 'Lifecycle / Field Return / Decommissioning' (e.g. RFQX-3299216-1-0200). Allocated feature: Lifecycle / Field Return / Decommissioning Security capability: None Interface: None Architecture: System Core Verification: Review + Test Related document artifacts: - Artifact context: - Derived from: RFQX-3299216-1-0200 |
| 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). | Bootloader and Application State Handling | None | 2 | Supplier-Owned | Candidate | DetailsStatement: 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). Derivation rationale: Clustered from 2 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). Allocated feature: Secure software update and flash readiness Security capability: None Interface: None Architecture: Application Software Verification: Review + Test Related document artifacts: - Artifact context: - Derived from: RFQX-CVS123-2-0037;RFQX-CVS123-2-0072 |
| 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). | Bootloader and Application State Handling | None | 3 | Supplier-Owned | Candidate | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Secure software update and flash readiness Security capability: None Interface: None Architecture: Hardware Platform Verification: Review + Test + table/diagram context review Related document artifacts: TABLE-CVS1232-0017 Artifact context: TABLE-CVS1232-0017 (Table): Table 17: Routine 0x2202 routineStatus routineResult Format page 32 Derived from: RFQX-CVS123-2-0039;RFQX-CVS123-2-0258;RFQX-CVS124-0343 |
| 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). | Software Update / Flashing | None | 17 | Shared | Blocked by Customer Clarification | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Secure software update and flash readiness Security capability: None Interface: OEM/Customer Review Interface Architecture: Application Software Verification: Review + Test + table/diagram context review Related document artifacts: DIAGRAM-CVS1232-0005;DIAGRAM-CVS1232-0006;TABLE-CVS1232-0003;TABLE-CVS1232-0004;TABLE-CVS1232-0021;TABLE-CVS124-0030;TABLE-CVS124-0031;TABLE-CVS124-0043;TABLE-CVS124-0044;TABLE-CVS124-0094;TABLE-CVS124-0095;TABLE-CVS124-0096 Artifact context: TABLE-CVS1232-0003 (Table): Table 3: Services support due to SUV2 page 23 | TABLE-CVS1232-0021 (Table): Table 21: Module to Index Mapping page 34 | TABLE-CVS1232-0003 (Table): Table 3: Services support due to SUV2 page 23 | TABLE-CVS1232-0004 (Table): Table 4: Routine identifiers for non-volatile memory access page 24 | TABLE-CVS1232-0021 (Table): Table 21: Module to Index Mapping page 34 | DIAGRAM-CVS1232-0005 (Diagram): Figure 5: diagram for signing of software update results page 38 Derived from: 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;RFQX-CVS124-0137;RFQX-CVS124-0140;RFQX-CVS124-0185;RFQX-CVS124-0389;RFQX-CVS124-0391 |
| 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). | Software Update / Flashing | None | 18 | Shared | Blocked by Customer Clarification | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Secure software update and flash readiness Security capability: None Interface: OEM/Customer Review Interface Architecture: System Core Verification: Review + Test + table/diagram context review Related document artifacts: TABLE-CVS1232-0022;TABLE-CVS124-0078;TABLE-CVS124-0079;TABLE-CVS124-0080;TABLE-CVS124-0094;TABLE-CVS124-0095;TABLE-CVS124-0096 Artifact context: TABLE-CVS1232-0022 (Table): Table 22: Routine 0xFF00 routineStatus routineResult Format page 34 | TABLE-CVS124-0078 (Table): Table 76 – RoutineControl (CheckProgrammingPreconditions) positive response format page 67 | TABLE-CVS124-0078 (Table): Table 76 – RoutineControl (CheckProgrammingPreconditions) positive response format page 67 Derived from: 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;RFQX-CVS124-0337;RFQX-CVS124-0339;RFQX-CVS124-0348;RFQX-CVS124-0366;RFQX-CVS124-0388;RFQX-CVS124-0392 |
| 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). | Bootloader and Application State Handling | None | 1 | Supplier-Owned | Candidate | DetailsStatement: 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). Derivation rationale: Clustered from 1 customer requirements allocated to 'Bootloader and Application State Handling' / 'Bootloader and Application State Handling' (e.g. RFQX-CVS123-2-0044). Allocated feature: Bootloader and Application State Handling Security capability: None Interface: None Architecture: System Core Verification: Review + Test Related document artifacts: - Artifact context: - Derived from: RFQX-CVS123-2-0044 |
| 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). | Diagnostic Services | None | 2 | Shared | Ready for Customer Alignment | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Diagnostic Services Security capability: None Interface: OEM/Customer Review Interface Architecture: Backend and IT Systems Verification: Test + table/diagram context review Related document artifacts: TABLE-CVS1232-0015;TABLE-CVS1232-0016 Artifact context: TABLE-CVS1232-0015 (Table): Table 15: Routine 0x2202 Request Format page 31 | TABLE-CVS1232-0016 (Table): Table 16: Routine 0x2202 Positive Response Format page 31 Derived from: RFQX-CVS123-2-0046;RFQX-CVS123-2-0251 |
| 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). | Data Authenticity and Integrity Verification | None | 8 | Shared | Ready for Customer Alignment | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Data Authenticity and Integrity Verification Security capability: None Interface: None Architecture: Application Software Verification: Review + Test + table/diagram context review Related document artifacts: DIAGRAM-CVS1232-0003;TABLE-CVS1232-0013;TABLE-CVS1232-0014;TABLE-CVS1232-0023;TABLE-CVS124-0094 Artifact context: DIAGRAM-CVS1232-0003 (Diagram): Figure 3: Programming phase #1 – Programming step page 16 | TABLE-CVS1232-0013 (Table): Table 13: Routine Support per routineControlType page 30 | TABLE-CVS1232-0014 (Table): Table 14: Routine support for Safe State Conditions page 30 | TABLE-CVS1232-0023 (Table): Table 23: Routine 0xFF01 Request Format page 35 Derived from: 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 |
| 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). | Secure Diagnostics / RBAC | Authentication | 3 | Shared | Blocked by Customer Clarification | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Secure software update and flash readiness Security capability: Authentication Interface: None Architecture: Security Services Verification: Review + Test + table/diagram context review Related document artifacts: TABLE-CVS1232-0013;TABLE-CVS1232-0014 Artifact context: TABLE-CVS1232-0013 (Table): Table 13: Routine Support per routineControlType page 30 | TABLE-CVS1232-0014 (Table): Table 14: Routine support for Safe State Conditions page 30 Derived from: RFQX-CVS123-2-0078;RFQX-CVS123-2-0079;RFQX-CVS123-2-0244 |
| 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). | Secure Data Transfer / Data Security Container | None | 6 | Shared | Ready for Customer Alignment | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Secure Data Transfer / Data Security Container Security capability: None Interface: None Architecture: Application Software Verification: Review + Test + table/diagram context review Related document artifacts: DIAGRAM-CVS1232-0003;TABLE-CVS1232-0014;TABLE-CVS1232-0018;TABLE-CVS124-0080 Artifact context: DIAGRAM-CVS1232-0003 (Diagram): Figure 3: Programming phase #1 – Programming step page 16 | TABLE-CVS1232-0014 (Table): Table 14: Routine support for Safe State Conditions page 30 | TABLE-CVS1232-0018 (Table): Table 18: Routine 0xFF00 Request Format page 33 Derived from: RFQX-CVS123-2-0114;RFQX-CVS123-2-0204;RFQX-CVS123-2-0247;RFQX-CVS123-2-0261;RFQX-CVS124-0273;RFQX-CVS124-0346 |
| 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). | Software Update / Flashing | None | 4 | Shared | Blocked by Customer Clarification | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Secure software update and flash readiness Security capability: None Interface: OEM/Customer Review Interface Architecture: Backend and IT Systems Verification: Review + Test + table/diagram context review Related document artifacts: TABLE-CVS124-0044;TABLE-CVS124-0097;TABLE-CVS124-0098 Artifact context: TABLE-CVS124-0044 (Table): Table 43 – Service 0x10 request parameter diagnosticSessionType description page 32 | TABLE-CVS124-0097 (Table): Table 95 – Example: Request: client → server page 79 | TABLE-CVS124-0098 (Table): Table 96 – Positive response: server → client page 79 Derived from: RFQX-CVS123-2-0164;RFQX-CVS123-2-0187;RFQX-CVS124-0142;RFQX-CVS124-0397 |
| 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). | Software Update / Flashing | None | 6 | Supplier-Owned | Candidate | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Secure software update and flash readiness Security capability: None Interface: OEM/Customer Review Interface Architecture: Hardware Platform Verification: Review + Test + table/diagram context review Related document artifacts: TABLE-CVS124-0006;TABLE-CVS124-0007;TABLE-CVS124-0008;TABLE-CVS124-0009;TABLE-CVS124-0010;TABLE-CVS124-0011;TABLE-CVS124-0018;TABLE-CVS124-0019;TABLE-CVS124-0038 Artifact context: TABLE-CVS124-0006 (Table): Table 6 – Description of DID 0xF180 bootSoftwareIdentificationDataIdentifier page 10 | TABLE-CVS124-0007 (Table): Table 7 – Description of DID 0xF181 applicationSoftwareIdentificationDataIdentifier page 10 | TABLE-CVS124-0008 (Table): Table 8 – Description of DID 0xF182 applicationDataIdentificationDataIdentifier page 11 | TABLE-CVS124-0009 (Table): Table 9 – Description of DID 0xF186 ActiveDiagnosticSessionDataIdentifier page 11 | TABLE-CVS124-0010 (Table): Table 10 – Description of DID 0xF187 vehicleManufacturerSparePartNumberDataIdentifier page 12 | TABLE-CVS124-0011 (Table): Table 11 – Description of DID 0xF188 vehicleManufacturerECUSoftwareNumberDataIdentifier page 12 Derived from: RFQX-CVS123-2-0165;RFQX-CVS124-0024;RFQX-CVS124-0028;RFQX-CVS124-0031;RFQX-CVS124-0043;RFQX-CVS124-0074 |
| 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). | Tooling / IT / Evidence Storage | None | 31 | Shared | Ready for Customer Alignment | DetailsStatement: The supplier shall provide the tooling, IT infrastructure and evidence storage required for Tooling / IT / Evidence Storage (Software domain; allocated to Application Software). Derivation rationale: 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. Allocated feature: Tooling / IT / Evidence Storage Security capability: None Interface: None Architecture: Application Software Verification: Review + Test + table/diagram context review Related document artifacts: DIAGRAM-CVS1232-0006;TABLE-CVS1232-0004;TABLE-CVS1232-0005;TABLE-CVS1232-0006;TABLE-CVS1232-0007;TABLE-CVS1232-0008;TABLE-CVS1232-0009;TABLE-CVS1232-0010;TABLE-CVS1232-0011;TABLE-CVS1232-0012;TABLE-CVS1232-0017;TABLE-CVS1232-0020;TABLE-CVS1232-0021;TABLE-CVS1232-0022;TABLE-CVS124-0045;TABLE-CVS124-0046;TABLE-CVS124-0064;TABLE-CVS124-0089 Artifact context: TABLE-CVS1232-0004 (Table): Table 4: Routine identifiers for non-volatile memory access page 24 | TABLE-CVS1232-0005 (Table): Table 5: Service 0x34 Request Format page 25 | TABLE-CVS1232-0005 (Table): Table 5: Service 0x34 Request Format page 25 | TABLE-CVS1232-0006 (Table): Table 6: Service 0x34 Positive Response Format page 26 Derived from: 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;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 |
| 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 (Software domain; allocated to Application Software). | Bootloader and Application State Handling | None | 3 | Shared | Ready for Customer Alignment | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Bootloader and Application State Handling Security capability: None Interface: None Architecture: Application Software Verification: Review + Test + table/diagram context review Related document artifacts: TABLE-CVS124-0081;TABLE-CVS124-0082 Artifact context: TABLE-CVS124-0081 (Table): Table 79 – Request parameter addressAndLengthFormatIdentifier values page 71 | TABLE-CVS124-0082 (Table): Table 80 – RoutineControl (EraseMemory) positive response format page 71 Derived from: RFQX-CVS123-2-0179;RFQX-CVS124-0193;RFQX-CVS124-0354 |
| 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). | Verification and Validation | None | 5 | Shared | Ready for Customer Alignment | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Security evidence and traceability Security capability: None Interface: OEM/Customer Review Interface Architecture: Backend and IT Systems Verification: Review + Test + table/diagram context review Related document artifacts: DIAGRAM-CVS1232-0006 Artifact context: DIAGRAM-CVS1232-0006 (Diagram): Figure 6: Erased-only bytes of a memory module page 41 Derived from: RFQX-CVS123-2-0207;RFQX-CVS123-2-0335;RFQX-CVS154-0010;RFQX-CVS154-0013;RFQX-CVS154-0016 |
| 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). | Verification and Validation | None | 3 | Shared | Ready for Customer Alignment | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Security evidence and traceability Security capability: None Interface: OEM/Customer Review Interface Architecture: Application Software Verification: Review + Test + table/diagram context review Related document artifacts: TABLE-CVS1232-0006;TABLE-CVS1232-0007 Artifact context: TABLE-CVS1232-0006 (Table): Table 6: Service 0x34 Positive Response Format page 26 | TABLE-CVS1232-0007 (Table): Table 7: Service 0x34 dataFormatIdentifier Format page 26 | TABLE-CVS1232-0006 (Table): Table 6: Service 0x34 Positive Response Format page 26 | TABLE-CVS1232-0007 (Table): Table 7: Service 0x34 dataFormatIdentifier Format page 26 Derived from: RFQX-CVS123-2-0216;RFQX-CVS123-2-0217;RFQX-CVS123-2-0326 |
| 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). | Secure Communication and Boundary Control | None | 27 | Shared | Blocked by Customer Clarification | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Secure communication and freshness protection Security capability: None Interface: None Architecture: Backend and IT Systems Verification: Review + Test + table/diagram context review Related document artifacts: DIAGRAM-CVS32-0003;DIAGRAM-CVS32-0009;DIAGRAM-CVS32-0013;DIAGRAM-CVS32-0014;DIAGRAM-CVS32-0015;TABLE-CVS1232-0012;TABLE-CVS32-0002 Artifact context: TABLE-CVS1232-0012 (Table): Table 12: Routine Support per Diagnostic Session page 29 | DIAGRAM-CVS32-0003 (Diagram): Figure 2 – Anti-replay protection page 8 | DIAGRAM-CVS32-0003 (Diagram): Figure 2 – Anti-replay protection page 8 Derived from: 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;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 |
| 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). | Data Authenticity and Integrity Verification | None | 2 | Shared | Ready for Customer Alignment | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Security evidence and traceability Security capability: None Interface: OEM/Customer Review Interface Architecture: Application Software Verification: Review + Test + table/diagram context review Related document artifacts: TABLE-CVS1232-0024;TABLE-CVS1232-0025;TABLE-CVS124-0090;TABLE-CVS124-0091;TABLE-CVS124-0092 Artifact context: TABLE-CVS1232-0024 (Table): Table 24: Routine 0xFF01 Positive Response Format page 36 | TABLE-CVS1232-0025 (Table): Table 25: Routine 0xFF01 routineStatus routineResult Format page 36 | TABLE-CVS124-0090 (Table): Table 88 – RoutineControl (Software Installation) positive StartRoutine response format page 75 | TABLE-CVS124-0091 (Table): Table 89 – RoutineControl (Software Installation) positive requestRoutineResult response format page 75 | TABLE-CVS124-0092 (Table): Table 90 – AuthenticityVerificationStatus page 75 Derived from: RFQX-CVS123-2-0285;RFQX-CVS124-0370 |
| 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). | Secure Diagnostics / RBAC | None | 15 | Shared | Blocked by Customer Clarification | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Secure Diagnostics / RBAC Security capability: None Interface: None Architecture: Backend and IT Systems Verification: Review + Test + table/diagram context review Related document artifacts: DIAGRAM-CVS151-0003;DIAGRAM-CVS151-0007;DIAGRAM-CVS151-0008;TABLE-CVS124-0039 Artifact context: TABLE-CVS124-0039 (Table): Table 39 – Diagnostic service support page 24 | DIAGRAM-CVS151-0003 (Diagram): Figure 2 – Visual representation of the RBACC page 7 | DIAGRAM-CVS151-0007 (Diagram): Figure 5 – Pattern-rules evaluation page 15 Derived from: 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;RFQX-CVS31-0093;RFQX-CVS31-0095;RFQX-CVS31-0098 |
| 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). | Secure Diagnostics / RBAC | None | 11 | Shared | Blocked by Customer Clarification | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Secure Diagnostics / RBAC Security capability: None Interface: None Architecture: Application Software Verification: Review + Test + table/diagram context review Related document artifacts: DIAGRAM-CVS151-0004;DIAGRAM-CVS151-0005;TABLE-CVS124-0039;TABLE-CVS124-0040;TABLE-CVS124-0043;TABLE-CVS124-0044;TABLE-CVS124-0075;TABLE-CVS31-0007;TABLE-CVS31-0009;TABLE-CVS31-0010 Artifact context: TABLE-CVS124-0039 (Table): Table 39 – Diagnostic service support page 24 | TABLE-CVS124-0040 (Table): Table 40 – Diagnostic Safe State check for Services page 25 | TABLE-CVS124-0043 (Table): Table 42 – IVD DIDs page 31 | TABLE-CVS124-0044 (Table): Table 43 – Service 0x10 request parameter diagnosticSessionType description page 32 | TABLE-CVS124-0075 (Table): Table 73 – Service 0x29 supported negative response codes page 64 Derived from: 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 |
| 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). | Diagnostic Services | None | 10 | Supplier-Owned | Candidate | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Diagnostic Services Security capability: None Interface: OEM/Customer Review Interface Architecture: System Core Verification: Test + table/diagram context review Related document artifacts: TABLE-CVS124-0040;TABLE-CVS124-0057;TABLE-CVS124-0099;TABLE-CVS124-0100 Artifact context: TABLE-CVS124-0040 (Table): Table 40 – Diagnostic Safe State check for Services page 25 | TABLE-CVS124-0057 (Table): Table 56 – Service 0x19 response parameter DTCExtDataRecordNumber description page 51 | TABLE-CVS124-0099 (Table): Table 97 – Fault memory DTC status bits description page 80 Derived from: 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 |
| 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). | Diagnostic Services | None | 13 | Supplier-Owned | Candidate | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Diagnostic Services Security capability: None Interface: None Architecture: Compliance Process Verification: Test + table/diagram context review Related document artifacts: TABLE-CVS124-0054;TABLE-CVS124-0055;TABLE-CVS124-0056;TABLE-CVS124-0059 Artifact context: TABLE-CVS124-0054 (Table): Table 53 – Service 0x19 request parameter DTCMaskRecord description page 42 | TABLE-CVS124-0054 (Table): Table 53 – Service 0x19 request parameter DTCMaskRecord description page 42 | TABLE-CVS124-0055 (Table): Table 54 – Service 0x19 request parameter DTCExtDataRecordNumber description page 43 Derived from: 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;RFQX-CVS124-0256 |
| 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). | Diagnostic Services | None | 1 | Supplier-Owned | Candidate | DetailsStatement: 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). Derivation rationale: Clustered from 1 customer requirements allocated to 'Diagnostic Services' / 'Diagnostic Services' (e.g. RFQX-CVS124-0201). Linked source table/diagram context was considered. Allocated feature: Diagnostic Services Security capability: None Interface: None Architecture: Hardware Platform Verification: Test + table/diagram context review Related document artifacts: TABLE-CVS124-0051;TABLE-CVS124-0052 Artifact context: TABLE-CVS124-0051 (Table): Table 50 – Service 0x87 request parameter linkControlType description page 39 | TABLE-CVS124-0052 (Table): Table 51 – Service 0x87 request parameter linkControlModeIdentifier description page 39 Derived from: RFQX-CVS124-0201 |
| 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). | Diagnostic Services | None | 4 | Shared | Blocked by Customer Clarification | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Diagnostic Services Security capability: None Interface: None Architecture: Application Software Verification: Test + table/diagram context review Related document artifacts: TABLE-CVS124-0056 Artifact context: TABLE-CVS124-0056 (Table): Table 55 – Snapshot data sub-function (0x04) positive response message content and format page 44 Derived from: RFQX-CVS124-0207;RFQX-CVS124-0238;RFQX-CVS31-0111;RFQX-CVS31-0119 |
| 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). | Data Authenticity and Integrity Verification | None | 5 | Shared | Blocked by Customer Clarification | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Security evidence and traceability Security capability: None Interface: OEM/Customer Review Interface Architecture: Backend and IT Systems Verification: Review + Test + table/diagram context review Related document artifacts: TABLE-CVS124-0088;TABLE-CVS124-0089;TABLE-CVS31-0007 Artifact context: TABLE-CVS124-0088 (Table): Table 86 – Example #2: Positive response: server → client page 73 | TABLE-CVS124-0089 (Table): Table 87 – Example #2: Negative response: server → client page 74 | TABLE-CVS124-0089 (Table): Table 87 – Example #2: Negative response: server → client page 74 | TABLE-CVS31-0007 (Table): Table 7 – proofOfOwnership Request page 12 Derived from: RFQX-CVS124-0362;RFQX-CVS124-0365;RFQX-CVS31-0046;RFQX-CVS31-0061;RFQX-CVS31-0062 |
| 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). | Data Authenticity and Integrity Verification | None | 2 | Supplier-Owned | Candidate | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Security evidence and traceability Security capability: None Interface: OEM/Customer Review Interface Architecture: System Core Verification: Review + Test + table/diagram context review Related document artifacts: TABLE-CVS124-0090;TABLE-CVS124-0091;TABLE-CVS124-0092 Artifact context: TABLE-CVS124-0090 (Table): Table 88 – RoutineControl (Software Installation) positive StartRoutine response format page 75 | TABLE-CVS124-0091 (Table): Table 89 – RoutineControl (Software Installation) positive requestRoutineResult response format page 75 | TABLE-CVS124-0092 (Table): Table 90 – AuthenticityVerificationStatus page 75 | TABLE-CVS124-0090 (Table): Table 88 – RoutineControl (Software Installation) positive StartRoutine response format page 75 | TABLE-CVS124-0091 (Table): Table 89 – RoutineControl (Software Installation) positive requestRoutineResult response format page 75 | TABLE-CVS124-0092 (Table): Table 90 – AuthenticityVerificationStatus page 75 Derived from: RFQX-CVS124-0369;RFQX-CVS124-0371 |
| 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). | Tooling / IT / Evidence Storage | None | 4 | Shared | Ready for Customer Alignment | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Tooling / IT / Evidence Storage Security capability: None Interface: OEM/Customer Review Interface Architecture: System Core Verification: Review + Test + table/diagram context review Related document artifacts: TABLE-CVS31-0006 Artifact context: TABLE-CVS31-0006 (Table): Table 6 – verifyCertificateBidirectional Response page 10 Derived from: RFQX-CVS124-0434;RFQX-CVS124-0438;RFQX-CVS124-0439;RFQX-CVS31-0031 |
| 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). | Secure Diagnostics / RBAC | None | 2 | Supplier-Owned | Candidate | DetailsStatement: 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). Derivation rationale: Clustered from 2 customer requirements allocated to 'Secure Diagnostics / RBAC' / 'Secure Diagnostics / RBAC' (e.g. RFQX-CVS151-0011, RFQX-CVS151-0078). Allocated feature: Secure Diagnostics / RBAC Security capability: None Interface: None Architecture: System Core Verification: Review + Test Related document artifacts: - Artifact context: - Derived from: RFQX-CVS151-0011;RFQX-CVS151-0078 |
| 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). | Secure Diagnostics / RBAC | None | 2 | Shared | Blocked by Customer Clarification | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Secure communication and freshness protection Security capability: None Interface: None Architecture: Application Software Verification: Review + Test + table/diagram context review Related document artifacts: DIAGRAM-CVS32-0007;TABLE-CVS31-0004 Artifact context: TABLE-CVS31-0004 (Table): Table 4 – Supported subFunctions (ISO 14229-1:2020) page 7 | DIAGRAM-CVS32-0007 (Diagram): Figure 4 – Change of CipherScheme mid sequence page 11 Derived from: RFQX-CVS31-0014;RFQX-CVS32-0057 |
| 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). | Key and Certificate Handling | None | 5 | Supplier-Owned | Candidate | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Key and Certificate Handling Security capability: None Interface: None Architecture: System Core Verification: Review + Test + table/diagram context review Related document artifacts: DIAGRAM-CVS31-0004;DIAGRAM-CVS31-0007;TABLE-CVS31-0004;TABLE-CVS31-0005;TABLE-CVS31-0006 Artifact context: TABLE-CVS31-0004 (Table): Table 4 – Supported subFunctions (ISO 14229-1:2020) page 7 | TABLE-CVS31-0005 (Table): Table 5 – verifyCertificateBidirectional Request page 8 | DIAGRAM-CVS31-0007 (Diagram): Figure 7 – Authentication State Transition page 28 | TABLE-CVS31-0006 (Table): Table 6 – verifyCertificateBidirectional Response page 10 | DIAGRAM-CVS31-0004 (Diagram): Figure 4 – Overview Ephemeral Diffie-Hellman key-exchange page 22 Derived from: RFQX-CVS31-0016;RFQX-CVS31-0026;RFQX-CVS31-0029;RFQX-CVS31-0077;RFQX-CVS31-0137 |
| 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). | Key and Certificate Handling | None | 6 | Shared | Blocked by Customer Clarification | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Key and Certificate Handling Security capability: None Interface: None Architecture: Backend and IT Systems Verification: Review + Test + table/diagram context review Related document artifacts: TABLE-CVS31-0005;TABLE-CVS31-0006 Artifact context: TABLE-CVS31-0005 (Table): Table 5 – verifyCertificateBidirectional Request page 8 | TABLE-CVS31-0006 (Table): Table 6 – verifyCertificateBidirectional Response page 10 Derived from: RFQX-CVS31-0019;RFQX-CVS31-0027;RFQX-CVS31-0028;RFQX-CVS31-0036;RFQX-CVS31-0038;RFQX-CVS31-0156 |
| 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). | Data Authenticity and Integrity Verification | None | 3 | Supplier-Owned | Candidate | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Data Authenticity and Integrity Verification Security capability: None Interface: None Architecture: System Core Verification: Review + Test + table/diagram context review Related document artifacts: TABLE-CVS31-0006;TABLE-CVS31-0008 Artifact context: TABLE-CVS31-0006 (Table): Table 6 – verifyCertificateBidirectional Response page 10 | TABLE-CVS31-0008 (Table): Table 8 – proofOfOwnership Response page 13 Derived from: RFQX-CVS31-0033;RFQX-CVS31-0056;RFQX-CVS31-0105 |
| 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). | Key and Certificate Handling | Key management | 7 | Shared | Blocked by Customer Clarification | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Secure communication and freshness protection Security capability: Key management Interface: None Architecture: Security Services Verification: Review + Test + table/diagram context review Related document artifacts: DIAGRAM-CVS32-0007;DIAGRAM-CVS32-0008;DIAGRAM-CVS32-0010;TABLE-CVS32-0002 Artifact context: TABLE-CVS32-0002 (Table): Table 2 – Supported CipherSchemes page 10 | DIAGRAM-CVS32-0007 (Diagram): Figure 4 – Change of CipherScheme mid sequence page 11 | DIAGRAM-CVS32-0008 (Diagram): Figure 5 – Use of HKDF output key material (okm) with SDT_CHACHA20_POLY1305 page 12 Derived from: RFQX-CVS32-0007;RFQX-CVS32-0051;RFQX-CVS32-0056;RFQX-CVS32-0065;RFQX-CVS32-0066;RFQX-CVS32-0068;RFQX-CVS32-0095 |
| 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). | Secure Communication and Boundary Control | None | 18 | Supplier-Owned | Candidate | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Secure communication and freshness protection Security capability: None Interface: None Architecture: System Core Verification: Review + Test + table/diagram context review Related document artifacts: DIAGRAM-CVS32-0001;DIAGRAM-CVS32-0002;DIAGRAM-CVS32-0004;DIAGRAM-CVS32-0005;DIAGRAM-CVS32-0006;DIAGRAM-CVS32-0008;DIAGRAM-CVS32-0010;DIAGRAM-CVS32-0019;TABLE-CVS32-0002 Artifact context: DIAGRAM-CVS32-0001 (Diagram): Figure 1 – SDT Overview page 6 | DIAGRAM-CVS32-0002 (Diagram): Figure 1 shows the layout of an SDT message with its protocol elements (for details refer to page 6 | DIAGRAM-CVS32-0001 (Diagram): Figure 1 – SDT Overview page 6 | DIAGRAM-CVS32-0002 (Diagram): Figure 1 shows the layout of an SDT message with its protocol elements (for details refer to page 6 | DIAGRAM-CVS32-0004 (Diagram): Figure 3 – Anti-replay protection and transaction coherency page 9 | DIAGRAM-CVS32-0005 (Diagram): Figure 3 illustrates transaction coherency and the use of PREQTAG. To avoid mix-up, the page 9 Derived from: 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;RFQX-CVS32-0141;RFQX-CVS32-0142;RFQX-CVS32-0143;RFQX-CVS32-0144;RFQX-CVS32-0145;RFQX-CVS32-0146 |
| 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). | Secure Diagnostics / RBAC | Authentication | 1 | Shared | Blocked by Customer Clarification | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Secure communication and freshness protection Security capability: Authentication Interface: None Architecture: Security Services Verification: Review + Test + table/diagram context review Related document artifacts: DIAGRAM-CVS32-0002 Artifact context: DIAGRAM-CVS32-0002 (Diagram): Figure 1 shows the layout of an SDT message with its protocol elements (for details refer to page 6 Derived from: RFQX-CVS32-0016 |
| 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). | Secure Communication and Boundary Control | None | 5 | Shared | Blocked by Customer Clarification | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Secure communication and freshness protection Security capability: None Interface: None Architecture: Application Software Verification: Review + Test + table/diagram context review Related document artifacts: DIAGRAM-CVS32-0007;DIAGRAM-CVS32-0008;DIAGRAM-CVS32-0010 Artifact context: DIAGRAM-CVS32-0007 (Diagram): Figure 4 – Change of CipherScheme mid sequence page 11 | DIAGRAM-CVS32-0007 (Diagram): Figure 4 – Change of CipherScheme mid sequence page 11 | DIAGRAM-CVS32-0008 (Diagram): Figure 5 – Use of HKDF output key material (okm) with SDT_CHACHA20_POLY1305 page 12 Derived from: RFQX-CVS32-0019;RFQX-CVS32-0058;RFQX-CVS32-0059;RFQX-CVS32-0064;RFQX-CVS32-0091 |
| 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). | Verification and Validation | None | 1 | Shared | Blocked by Customer Clarification | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Secure communication and freshness protection Security capability: None Interface: OEM/Customer Review Interface Architecture: Backend and IT Systems Verification: Review + Test + table/diagram context review Related document artifacts: DIAGRAM-CVS32-0006;TABLE-CVS32-0002 Artifact context: TABLE-CVS32-0002 (Table): Table 2 – Supported CipherSchemes page 10 | DIAGRAM-CVS32-0006 (Diagram): Figure 4 illustrates the switching of CipherSchemes within an SDT sequence. The client has page 11 Derived from: RFQX-CVS32-0054 |
| 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). | Data Authenticity and Integrity Verification | Authentication | 6 | Shared | Blocked by Customer Clarification | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Secure communication and freshness protection Security capability: Authentication Interface: None Architecture: Security Services Verification: Review + Test + table/diagram context review Related document artifacts: DIAGRAM-CVS32-0010;DIAGRAM-CVS32-0016;DIAGRAM-CVS32-0017;DIAGRAM-CVS32-0018;DIAGRAM-CVS32-0019 Artifact context: DIAGRAM-CVS32-0010 (Diagram): Figure 7 – Use of HKDF output key material (okm) with SDT_POLY1305 page 15 | DIAGRAM-CVS32-0010 (Diagram): Figure 7 – Use of HKDF output key material (okm) with SDT_POLY1305 page 15 | DIAGRAM-CVS32-0016 (Diagram): Figure 11 shows an example where the client sends a RDBI and the server responds with two page 21 | DIAGRAM-CVS32-0017 (Diagram): Figure 11 – Example of a multi-response transaction page 21 | DIAGRAM-CVS32-0018 (Diagram): Figure 12Figure 12 illustrates error- and state handling in the client’s security sub-layer. The page 21 | DIAGRAM-CVS32-0019 (Diagram): Figure 12 – The client's error and state handling page 22 Derived from: RFQX-CVS32-0073;RFQX-CVS32-0082;RFQX-CVS32-0092;RFQX-CVS32-0093;RFQX-CVS32-0133;RFQX-CVS32-0139 |
| 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). | Secure Communication and Boundary Control | None | 1 | Shared | Blocked by Customer Clarification | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: OEM/Customer Review Interface Security capability: None Interface: OEM/Customer Review Interface Architecture: Backend and IT Systems Verification: Review + Test + table/diagram context review Related document artifacts: DIAGRAM-CVS32-0011 Artifact context: DIAGRAM-CVS32-0011 (Diagram): Figure 8 – Example of client and server's behavior using SDT_POLY1305 page 17 Derived from: RFQX-CVS32-0106 |
| 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). | Secure Communication and Boundary Control | Secure communication | 1 | Shared | Blocked by Customer Clarification | DetailsStatement: 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). Derivation rationale: 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. Allocated feature: Secure communication and freshness protection Security capability: Secure communication Interface: None Architecture: Security Services Verification: Review + Test + table/diagram context review Related document artifacts: DIAGRAM-CVS32-0015 Artifact context: DIAGRAM-CVS32-0015 (Diagram): Figure 10 – Server's error and state handling page 19 Derived from: RFQX-CVS32-0120 |
Blocked-by-Clarification List
| SSR ID | Category | Open Point |
|---|---|---|
| SSR-DAI-001 | Data Authenticity and Integrity Verification | OP-002;OP-003 |
| SSR-KEY-001 | Key and Certificate Handling | OP-002;OP-003 |
| SSR-COM-004 | Secure Communication and Boundary Control | OP-002;OP-004 |
| SSR-TOOL-002 | Tooling / IT / Evidence Storage | OP-004;OP-009 |
| SSR-COM-005 | Secure Communication and Boundary Control | OP-004 |
| SSR-RBAC-001 | Secure Diagnostics / RBAC | OP-002 |
| SSR-UPD-001 | Software Update / Flashing | OP-004 |
| SSR-UPD-002 | Software Update / Flashing | OP-004 |
| SSR-RBAC-002 | Secure Diagnostics / RBAC | OP-002 |
| SSR-UPD-003 | Software Update / Flashing | OP-002;OP-004 |
| SSR-COM-009 | Secure Communication and Boundary Control | OP-005 |
| SSR-RBAC-003 | Secure Diagnostics / RBAC | OP-002 |
| SSR-RBAC-004 | Secure Diagnostics / RBAC | OP-002 |
| SSR-DIAG-006 | Diagnostic Services | OP-002 |
| SSR-DAI-006 | Data Authenticity and Integrity Verification | OP-004 |
| SSR-RBAC-006 | Secure Diagnostics / RBAC | OP-002 |
| SSR-KEY-003 | Key and Certificate Handling | OP-003 |
| SSR-KEY-004 | Key and Certificate Handling | OP-004;OP-005 |
| SSR-RBAC-007 | Secure Diagnostics / RBAC | OP-002 |
| SSR-COM-011 | Secure Communication and Boundary Control | OP-005 |
| SSR-VV-004 | Verification and Validation | OP-005 |
| SSR-DAI-009 | Data Authenticity and Integrity Verification | OP-005 |
| SSR-COM-012 | Secure Communication and Boundary Control | OP-005 |
| SSR-COM-013 | Secure Communication and Boundary Control | OP-005 |
Document Traceability
Open Derivation Gaps
| Category | Customer Requirements | Coverage |
|---|---|---|
| System Function | 710 | 25.4% |
| Diagnostic Services | 99 | 31.3% |
| Secure Diagnostics / RBAC | 107 | 49.5% |
| Software Update / Flashing | 104 | 43.3% |
| Bootloader and Application State Handling | 61 | 14.8% |
| Secure Data Transfer / Data Security Container | 14 | 42.9% |
| Key and Certificate Handling | 77 | 46.8% |
| Secure Communication and Boundary Control | 257 | 40.9% |
| Cybersecurity Concept and Evidence | 29 | 58.6% |
| Hardware / HSM / Secure Storage | 41 | 34.1% |
| Verification and Validation | 28 | 39.3% |
Customer-to-Supplier Traceability Table
Show customer-to-supplier matrix (1789 requirements)
| Customer Requirement ID | Disposition | SSR ID | Mapping Confidence | Reason |
|---|---|---|---|---|
| RFQX-1001379436-P10-000-01-0001 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-1001379436-P10-000-01-0002 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-1001379436-P10-000-01-0003 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-1001379436-P10-000-01-0004 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-1001379436-P10-000-01-0005 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-1001379436-P10-000-01-0006 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-1001379436-P10-000-01-0007 | Derive Supplier System Requirement | SSR-CON-001 | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-1001379436-P10-000-01-0008 | Derive Supplier System Requirement | SSR-VIH-001 | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-1001379436-P10-000-01-0009 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-1001379436-P10-000-01-0010 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-1001379436-P10-000-01-0011 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-1001379436-P10-000-01-0012 | Derive Supplier System Requirement | SSR-CON-002 | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-1001379436-P10-000-01-0013 | Covered by Existing Supplier System Requirement | SSR-CON-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-1001379436-P10-000-01-0014 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-1001379436-P10-000-01-0015 | Covered by Existing Supplier System Requirement | SSR-CON-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-1001379436-P10-000-01-0016 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-1001379436-P10-000-01-0017 | Covered by Existing Supplier System Requirement | SSR-CON-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-1001379436-P10-000-01-0018 | Covered by Existing Supplier System Requirement | SSR-CON-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-1001379436-P10-000-01-0019 | Covered by Existing Supplier System Requirement | SSR-CON-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-1001379436-P10-000-01-0020 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-1001379436-P10-000-01-0021 | Derive Supplier System Requirement | SSR-CON-003 | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-1001379436-P10-000-01-0022 | Derive Supplier System Requirement | SSR-HW-001 | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-1001379436-P10-000-01-0023 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-1001379436-P10-000-01-0024 | Covered by Existing Supplier System Requirement | SSR-CON-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-1001379436-P10-000-01-0025 | Derive Supplier System Requirement | SSR-DAI-001 | Low | Accepted requirement; seed of its SSR cluster. |
| RFQX-1001379436-P10-000-01-0026 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-1001379436-P10-000-01-0027 | Covered by Existing Supplier System Requirement | SSR-CON-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-1001379436-P10-000-01-0028 | Derive Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-1001379436-P10-000-01-0029 | Derive Supplier System Requirement | SSR-PROD-001 | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-1001379436-P10-000-01-0030 | Derive Supplier System Requirement | SSR-COM-001 | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-1001379436-P10-000-01-0031 | Derive Supplier System Requirement | SSR-COM-002 | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-1001379436-P10-000-01-0032 | Derive Supplier System Requirement | SSR-COM-003 | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-1001379436-P10-000-01-0033 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-1001379436-P10-000-01-0034 | Covered by Existing Supplier System Requirement | SSR-COM-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-1001379436-P10-000-01-0035 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-1001379436-P10-000-01-0036 | Shared Responsibility / CIA Needed | SSR-COM-001 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-1001379436-P10-000-01-0037 | Covered by Existing Supplier System Requirement | SSR-CON-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-1001379436-P10-000-01-0038 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-1001379436-P10-000-01-0039 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-1001379436-P10-000-01-0040 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-1001379436-P10-000-01-0041 | Shared Responsibility / CIA Needed | SSR-KEY-001 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-1001379436-P10-000-01-0042 | Covered by Existing Supplier System Requirement | SSR-KEY-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-1001379436-P10-000-01-0043 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-1001379436-P10-000-01-0044 | Covered by Existing Supplier System Requirement | SSR-CON-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-1001379436-P10-000-01-0045 | Covered by Existing Supplier System Requirement | SSR-CON-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-1001379436-P10-000-01-0046 | Covered by Existing Supplier System Requirement | SSR-CON-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-1001379436-P10-000-01-0047 | Derive Supplier System Requirement | SSR-VIH-002 | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-1001379436-P10-000-01-0048 | Covered by Existing Supplier System Requirement | SSR-VIH-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-1001379436-P10-000-01-0049 | Covered by Existing Supplier System Requirement | SSR-VIH-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-1001379436-P10-000-01-0050 | Covered by Existing Supplier System Requirement | SSR-VIH-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-1001379436-P10-000-01-0051 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-1001379436-P10-000-01-0052 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-1001379436-P10-000-01-0053 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-1001379436-P10-000-01-0054 | Shared Responsibility / CIA Needed | SSR-VIH-003 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-1001379436-P10-000-01-0055 | Covered by Existing Supplier System Requirement | SSR-VIH-003 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-1001379436-P10-000-01-0056 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-1001379436-P10-000-01-0057 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-1001379436-P10-000-01-0058 | Derive Supplier System Requirement | SSR-VIH-004 | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-1001379436-P10-000-01-0059 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-1001379436-P10-000-01-0060 | Covered by Existing Supplier System Requirement | SSR-HW-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-1001379436-P10-000-01-0061 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-1001379436-P10-000-01-0062 | Derive Supplier System Requirement | SSR-LIFE-001 | High | Accepted requirement; seed of its SSR cluster. |
| RFQX-1001379436-P10-000-01-0063 | Shared Responsibility / CIA Needed | SSR-HW-001 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-1001379436-P10-000-01-0064 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-1001379436-P10-000-01-0065 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-1001379436-P10-000-01-0066 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-1001379436-P10-000-01-0067 | Derive Supplier System Requirement | SSR-LOG-001 | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-3299216-1-0001 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0002 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0003 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0004 | Covered by Existing Supplier System Requirement | SSR-HW-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0005 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0006 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0007 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0008 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0009 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0010 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0011 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0012 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0013 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0014 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0015 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0016 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0017 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0018 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0019 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0020 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0021 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0022 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0023 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0024 | Shared Responsibility / CIA Needed | SSR-COM-004 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-3299216-1-0025 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0026 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0027 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0028 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0029 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0030 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0031 | Derive Supplier System Requirement | SSR-DAI-002 | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-3299216-1-0032 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0033 | Shared Responsibility / CIA Needed | SSR-COM-004 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-3299216-1-0034 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0035 | Derive Supplier System Requirement | SSR-TOOL-001 | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-3299216-1-0036 | Shared Responsibility / CIA Needed | SSR-DAI-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-3299216-1-0037 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0038 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0039 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-3299216-1-0040 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-3299216-1-0041 | Shared Responsibility / CIA Needed | SSR-COM-005 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-3299216-1-0042 | Covered by Existing Supplier System Requirement | SSR-COM-005 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0043 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0044 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0045 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0046 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0047 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0048 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0049 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0050 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0051 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0052 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0053 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0054 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0055 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0056 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0057 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0058 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0059 | Covered by Existing Supplier System Requirement | SSR-HW-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0060 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0061 | Derive Supplier System Requirement | SSR-COM-006 | Low | Accepted requirement; seed of its SSR cluster. |
| RFQX-3299216-1-0062 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0063 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0064 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0065 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0066 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0067 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0068 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0069 | Needs Internal Review | None | n/a | Low confidence / human review before derivation. |
| RFQX-3299216-1-0070 | Derive Supplier System Requirement | SSR-SYS-002 | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-3299216-1-0071 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0072 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0073 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0074 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0075 | Derive Supplier System Requirement | SSR-SYS-003 | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-3299216-1-0076 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0077 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0078 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0079 | Shared Responsibility / CIA Needed | SSR-DAI-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-3299216-1-0080 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0081 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0082 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0083 | Covered by Existing Supplier System Requirement | SSR-COM-005 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0084 | Derive Supplier System Requirement | SSR-COM-007 | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-3299216-1-0085 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0086 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0087 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0088 | Shared Responsibility / CIA Needed | SSR-COM-004 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-3299216-1-0089 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0090 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0091 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0092 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0093 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0094 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0095 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0096 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0097 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0098 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0099 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0100 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0101 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0102 | Covered by Existing Supplier System Requirement | SSR-COM-007 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0103 | Covered by Existing Supplier System Requirement | SSR-COM-007 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0104 | Covered by Existing Supplier System Requirement | SSR-COM-007 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0105 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0106 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0107 | Derive Supplier System Requirement | SSR-RBAC-001 | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-3299216-1-0108 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0109 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0110 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0111 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0112 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0113 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0114 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0115 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0116 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0117 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0118 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0119 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0120 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0121 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0122 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0123 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0124 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0125 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0126 | Covered by Existing Supplier System Requirement | SSR-RBAC-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0127 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0128 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0129 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0130 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0131 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0132 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0134 | Derive Supplier System Requirement | SSR-VV-001 | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-3299216-1-0135 | Derive Supplier System Requirement | SSR-DIAG-001 | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-3299216-1-0136 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0137 | Derive Supplier System Requirement | SSR-COM-008 | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-3299216-1-0138 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0139 | Covered by Existing Supplier System Requirement | SSR-SYS-003 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0140 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0141 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0142 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0143 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0144 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0145 | Covered by Existing Supplier System Requirement | SSR-HW-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0146 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0147 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0148 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0149 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0150 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0151 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0152 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0153 | Covered by Existing Supplier System Requirement | SSR-COM-007 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0154 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0155 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0156 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0157 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0158 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0159 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0160 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0161 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0162 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0163 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0164 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0165 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0166 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0167 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0168 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0169 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0170 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0171 | Covered by Existing Supplier System Requirement | SSR-COM-007 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0172 | Covered by Existing Supplier System Requirement | SSR-COM-007 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0173 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0174 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0175 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0176 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0177 | Covered by Existing Supplier System Requirement | SSR-COM-007 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0178 | Covered by Existing Supplier System Requirement | SSR-COM-007 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0179 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0180 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0181 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-3299216-1-0182 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0183 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0184 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0185 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0186 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0187 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0188 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0189 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0190 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0191 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0192 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0193 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0194 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0195 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0196 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0197 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0198 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0199 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0200 | Derive Supplier System Requirement | SSR-LIFE-002 | High | Accepted requirement; seed of its SSR cluster. |
| RFQX-3299216-1-0201 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0202 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0203 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0204 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0205 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0206 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0207 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0208 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0209 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0210 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0211 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0212 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0213 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0214 | Covered by Existing Supplier System Requirement | SSR-SYS-003 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0215 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0216 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0217 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0218 | Covered by Existing Supplier System Requirement | SSR-SYS-003 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0219 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0220 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0221 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0222 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0223 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0224 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0225 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0226 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0227 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0228 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0229 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0230 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0231 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0232 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0233 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0234 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0235 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0236 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0237 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0238 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0239 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0240 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0241 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0242 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0243 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0244 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0245 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0246 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0247 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0248 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0249 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0250 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0251 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0252 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0253 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0254 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0255 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0256 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0257 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0258 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0259 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0260 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0261 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0262 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0263 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0264 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0265 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0266 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0267 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0268 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0269 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0270 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0271 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0272 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0273 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0274 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0275 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0276 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0277 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0278 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0279 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0280 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0281 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0282 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0283 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0284 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0285 | Covered by Existing Supplier System Requirement | SSR-SYS-003 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0286 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0287 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0288 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0289 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0290 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0291 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0292 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0293 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0294 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0295 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0296 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0297 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0298 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0299 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0300 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0301 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0302 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0303 | Needs Internal Review | None | n/a | Low confidence / human review before derivation. |
| RFQX-3299216-1-0304 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0305 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0306 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0307 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0308 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0309 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0001 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0002 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS123-2-0003 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS123-2-0004 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0005 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0006 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0007 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0008 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0009 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0010 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0011 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0012 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0013 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0014 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS123-2-0015 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0016 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0017 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0018 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0019 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0020 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0021 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0022 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0023 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0024 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0025 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0026 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0027 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0028 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0029 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0030 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0031 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0032 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0033 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0034 | Shared Responsibility / CIA Needed | SSR-RBAC-001 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0035 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS123-2-0036 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0037 | Derive Supplier System Requirement | SSR-BOOT-001 | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-CVS123-2-0038 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0039 | Derive Supplier System Requirement | SSR-BOOT-002 | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-CVS123-2-0040 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS123-2-0041 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS123-2-0042 | Shared Responsibility / CIA Needed | SSR-UPD-001 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0043 | Derive Supplier System Requirement | SSR-UPD-002 | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-CVS123-2-0044 | Derive Supplier System Requirement | SSR-BOOT-003 | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-CVS123-2-0045 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0046 | Shared Responsibility / CIA Needed | SSR-DIAG-002 | High | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0047 | Shared Responsibility / CIA Needed | SSR-RBAC-001 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0048 | Covered by Existing Supplier System Requirement | SSR-UPD-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0049 | Covered by Existing Supplier System Requirement | SSR-UPD-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0050 | Shared Responsibility / CIA Needed | SSR-UPD-001 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0051 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0052 | Covered by Existing Supplier System Requirement | SSR-RBAC-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0053 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS123-2-0054 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0055 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS123-2-0056 | Covered by Existing Supplier System Requirement | SSR-RBAC-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0057 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0058 | Covered by Existing Supplier System Requirement | SSR-SYS-003 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0059 | Covered by Existing Supplier System Requirement | SSR-SYS-003 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0060 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0061 | Shared Responsibility / CIA Needed | SSR-DAI-004 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0062 | Covered by Existing Supplier System Requirement | SSR-UPD-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0063 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0064 | Covered by Existing Supplier System Requirement | SSR-UPD-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0065 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0066 | Covered by Existing Supplier System Requirement | SSR-SYS-003 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0067 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0068 | Covered by Existing Supplier System Requirement | SSR-SYS-003 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0069 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS123-2-0070 | Shared Responsibility / CIA Needed | SSR-UPD-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0071 | Shared Responsibility / CIA Needed | SSR-UPD-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0072 | Covered by Existing Supplier System Requirement | SSR-BOOT-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0073 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0074 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0075 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS123-2-0076 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0077 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0078 | Shared Responsibility / CIA Needed | SSR-RBAC-002 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0079 | Shared Responsibility / CIA Needed | SSR-RBAC-002 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0080 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0081 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0082 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0083 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0084 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0085 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0086 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0087 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0088 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0089 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0090 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0091 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0092 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0093 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0094 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0095 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0096 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0097 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0098 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0099 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0100 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0101 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0102 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0103 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0104 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0105 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0106 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0107 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0108 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0109 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0110 | Shared Responsibility / CIA Needed | SSR-DAI-004 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0111 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0112 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0113 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0114 | Shared Responsibility / CIA Needed | SSR-SDT-001 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0115 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0116 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0117 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0118 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0119 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0120 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0121 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0122 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0123 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0124 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0125 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0126 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0127 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0128 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0129 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0130 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0131 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0132 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0133 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0134 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0135 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0136 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0137 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0138 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0139 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0140 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0141 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0142 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0143 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0144 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0145 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0146 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0147 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0148 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0149 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0150 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0151 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0152 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0153 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS123-2-0154 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0155 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0156 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0157 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0158 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0159 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0160 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0161 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0162 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0163 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0164 | Shared Responsibility / CIA Needed | SSR-UPD-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0165 | Derive Supplier System Requirement | SSR-UPD-004 | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-CVS123-2-0166 | Shared Responsibility / CIA Needed | SSR-RBAC-001 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0167 | Derive Supplier System Requirement | SSR-TOOL-003 | Low | Accepted requirement; seed of its SSR cluster. |
| RFQX-CVS123-2-0168 | Covered by Existing Supplier System Requirement | SSR-SYS-003 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0169 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0170 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0171 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0172 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0173 | Covered by Existing Supplier System Requirement | SSR-COM-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0174 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0175 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0176 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0177 | Covered by Existing Supplier System Requirement | SSR-SYS-003 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0178 | Covered by Existing Supplier System Requirement | SSR-UPD-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0179 | Derive Supplier System Requirement | SSR-BOOT-004 | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-CVS123-2-0180 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0181 | Covered by Existing Supplier System Requirement | SSR-SYS-003 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0182 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS123-2-0183 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS123-2-0184 | Covered by Existing Supplier System Requirement | SSR-UPD-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0185 | Covered by Existing Supplier System Requirement | SSR-UPD-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0186 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0187 | Shared Responsibility / CIA Needed | SSR-UPD-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0188 | Shared Responsibility / CIA Needed | SSR-UPD-001 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0189 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS123-2-0190 | Covered by Existing Supplier System Requirement | SSR-TOOL-003 | Low | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0191 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0192 | Covered by Existing Supplier System Requirement | SSR-RBAC-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0193 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0194 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0195 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0196 | Covered by Existing Supplier System Requirement | SSR-CON-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0197 | Shared Responsibility / CIA Needed | SSR-UPD-001 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0198 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0199 | Shared Responsibility / CIA Needed | SSR-UPD-001 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0200 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0201 | Shared Responsibility / CIA Needed | SSR-CON-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0202 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0203 | Shared Responsibility / CIA Needed | SSR-TOOL-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0204 | Covered by Existing Supplier System Requirement | SSR-SDT-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0205 | Shared Responsibility / CIA Needed | SSR-TOOL-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0206 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS123-2-0207 | Shared Responsibility / CIA Needed | SSR-VV-002 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0208 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0209 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0210 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0211 | Shared Responsibility / CIA Needed | SSR-COM-006 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0212 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0213 | Shared Responsibility / CIA Needed | SSR-TOOL-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0214 | Shared Responsibility / CIA Needed | SSR-TOOL-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0215 | Shared Responsibility / CIA Needed | SSR-TOOL-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0216 | Shared Responsibility / CIA Needed | SSR-VV-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0217 | Shared Responsibility / CIA Needed | SSR-VV-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0218 | Shared Responsibility / CIA Needed | SSR-TOOL-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0219 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0220 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0221 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0222 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0223 | Shared Responsibility / CIA Needed | SSR-TOOL-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0224 | Shared Responsibility / CIA Needed | SSR-TOOL-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0225 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0226 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0227 | Shared Responsibility / CIA Needed | SSR-TOOL-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0228 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0229 | Shared Responsibility / CIA Needed | SSR-TOOL-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0230 | Shared Responsibility / CIA Needed | SSR-TOOL-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0231 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0232 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0233 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0234 | Shared Responsibility / CIA Needed | SSR-TOOL-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0235 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0236 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0237 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0238 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0239 | Shared Responsibility / CIA Needed | SSR-TOOL-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0240 | Shared Responsibility / CIA Needed | SSR-DAI-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0241 | Derive Supplier System Requirement | SSR-COM-009 | Low | Accepted requirement; seed of its SSR cluster. |
| RFQX-CVS123-2-0242 | Shared Responsibility / CIA Needed | SSR-RBAC-001 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0243 | Shared Responsibility / CIA Needed | SSR-CON-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0244 | Shared Responsibility / CIA Needed | SSR-RBAC-002 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0245 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0246 | Shared Responsibility / CIA Needed | SSR-DAI-004 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0247 | Covered by Existing Supplier System Requirement | SSR-SDT-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0248 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0249 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0250 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0251 | Covered by Existing Supplier System Requirement | SSR-DIAG-002 | High | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0252 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0253 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0254 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0255 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0256 | Shared Responsibility / CIA Needed | SSR-TOOL-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0257 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0258 | Covered by Existing Supplier System Requirement | SSR-BOOT-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0259 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0260 | Shared Responsibility / CIA Needed | SSR-TOOL-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0261 | Covered by Existing Supplier System Requirement | SSR-SDT-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0262 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0263 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0264 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0265 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0266 | Covered by Existing Supplier System Requirement | SSR-SYS-003 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0267 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0268 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0269 | Shared Responsibility / CIA Needed | SSR-TOOL-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0270 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0271 | Covered by Existing Supplier System Requirement | SSR-UPD-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0272 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0273 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0274 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS123-2-0275 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0276 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0277 | Shared Responsibility / CIA Needed | SSR-DAI-004 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0278 | Shared Responsibility / CIA Needed | SSR-DAI-004 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0279 | Shared Responsibility / CIA Needed | SSR-DAI-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0280 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0281 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0282 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0283 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0284 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0285 | Shared Responsibility / CIA Needed | SSR-DAI-005 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0286 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS123-2-0287 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0288 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0289 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0290 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0291 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0292 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0293 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0294 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0295 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0296 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0297 | Shared Responsibility / CIA Needed | SSR-DAI-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0298 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0299 | Shared Responsibility / CIA Needed | SSR-UPD-001 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0300 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0301 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0302 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0303 | Shared Responsibility / CIA Needed | SSR-RBAC-001 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0304 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0305 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0306 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0307 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0308 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0309 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0310 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0311 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0312 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0313 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0314 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0315 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0316 | Covered by Existing Supplier System Requirement | SSR-HW-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0317 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0318 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0319 | Covered by Existing Supplier System Requirement | SSR-SYS-003 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0320 | Covered by Existing Supplier System Requirement | SSR-SYS-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0321 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0322 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS123-2-0323 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0324 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0325 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0326 | Shared Responsibility / CIA Needed | SSR-VV-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0327 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0328 | Covered by Existing Supplier System Requirement | SSR-TOOL-003 | Low | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0329 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0330 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0331 | Covered by Existing Supplier System Requirement | SSR-SYS-003 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0332 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0333 | Covered by Existing Supplier System Requirement | SSR-UPD-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0334 | Shared Responsibility / CIA Needed | SSR-HW-001 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0335 | Shared Responsibility / CIA Needed | SSR-VV-002 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0336 | Covered by Existing Supplier System Requirement | SSR-TOOL-003 | Low | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0337 | Shared Responsibility / CIA Needed | SSR-DAI-004 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS123-2-0338 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0339 | Covered by Existing Supplier System Requirement | SSR-TOOL-003 | Low | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0340 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0341 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0342 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0343 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS123-2-0344 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0345 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0346 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS123-2-0347 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0348 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0349 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0350 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS123-2-0351 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0001 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0002 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0003 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0004 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0005 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0006 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0007 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0008 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0009 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0010 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0011 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0012 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0013 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0014 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0015 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0016 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0017 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0018 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0019 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0020 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0021 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0022 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0023 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0024 | Covered by Existing Supplier System Requirement | SSR-UPD-004 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0025 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0026 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0027 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0028 | Covered by Existing Supplier System Requirement | SSR-UPD-004 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0029 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0030 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0031 | Covered by Existing Supplier System Requirement | SSR-UPD-004 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0032 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0033 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0034 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0035 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0036 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0037 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0038 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0039 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0040 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0041 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0042 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0043 | Covered by Existing Supplier System Requirement | SSR-UPD-004 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0044 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0045 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0046 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0047 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0048 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0049 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0050 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0051 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0052 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0053 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0054 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0055 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0056 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0057 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0058 | Covered by Existing Supplier System Requirement | SSR-HW-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0059 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0060 | Covered by Existing Supplier System Requirement | SSR-UPD-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0061 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0062 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0063 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0064 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0065 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0066 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0067 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0068 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0069 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0070 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0071 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0072 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0073 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0074 | Covered by Existing Supplier System Requirement | SSR-UPD-004 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0075 | Covered by Existing Supplier System Requirement | SSR-RBAC-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0076 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0077 | Covered by Existing Supplier System Requirement | SSR-RBAC-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0078 | Covered by Existing Supplier System Requirement | SSR-RBAC-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0079 | Covered by Existing Supplier System Requirement | SSR-SYS-003 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0080 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0081 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0082 | Covered by Existing Supplier System Requirement | SSR-SYS-003 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0083 | Shared Responsibility / CIA Needed | SSR-RBAC-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0084 | Derive Supplier System Requirement | SSR-RBAC-004 | Low | Accepted requirement; seed of its SSR cluster. |
| RFQX-CVS124-0085 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0086 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0087 | Derive Supplier System Requirement | SSR-DIAG-003 | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-CVS124-0088 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0089 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0090 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0091 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0092 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0093 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0094 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0095 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0096 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0097 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0098 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0099 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0100 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0101 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0102 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0103 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0104 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0105 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0106 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0107 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0108 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0109 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0110 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0111 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0112 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0113 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0114 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0115 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0116 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0117 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0118 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0119 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0120 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0121 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0122 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0123 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0124 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0125 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0126 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0127 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0128 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0129 | Covered by Existing Supplier System Requirement | SSR-SYS-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0130 | Covered by Existing Supplier System Requirement | SSR-HW-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0131 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0132 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0133 | Covered by Existing Supplier System Requirement | SSR-SYS-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0134 | Covered by Existing Supplier System Requirement | SSR-SYS-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0135 | Covered by Existing Supplier System Requirement | SSR-RBAC-004 | Low | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0136 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0137 | Covered by Existing Supplier System Requirement | SSR-UPD-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0138 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0139 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0140 | Covered by Existing Supplier System Requirement | SSR-UPD-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0141 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0142 | Shared Responsibility / CIA Needed | SSR-UPD-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0143 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0144 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0145 | Covered by Existing Supplier System Requirement | SSR-UPD-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0146 | Derive Supplier System Requirement | SSR-DIAG-004 | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-CVS124-0147 | Covered by Existing Supplier System Requirement | SSR-SYS-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0148 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0149 | Covered by Existing Supplier System Requirement | SSR-COM-007 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0150 | Covered by Existing Supplier System Requirement | SSR-SYS-003 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0151 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0152 | Shared Responsibility / CIA Needed | SSR-HW-001 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0153 | Covered by Existing Supplier System Requirement | SSR-HW-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0154 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0155 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0156 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0157 | Shared Responsibility / CIA Needed | SSR-TOOL-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0158 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0159 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0160 | Covered by Existing Supplier System Requirement | SSR-KEY-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0161 | Shared Responsibility / CIA Needed | SSR-TOOL-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0162 | Covered by Existing Supplier System Requirement | SSR-SYS-003 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0163 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0164 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0165 | Covered by Existing Supplier System Requirement | SSR-SYS-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0166 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0167 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0168 | Shared Responsibility / CIA Needed | SSR-COM-006 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0169 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0170 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0171 | Shared Responsibility / CIA Needed | SSR-RBAC-001 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0172 | Covered by Existing Supplier System Requirement | SSR-COM-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0173 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0174 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0175 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0176 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0177 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0178 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0179 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0180 | Covered by Existing Supplier System Requirement | SSR-SYS-003 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0181 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0182 | Covered by Existing Supplier System Requirement | SSR-SYS-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0183 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0184 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0185 | Shared Responsibility / CIA Needed | SSR-UPD-001 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0186 | Covered by Existing Supplier System Requirement | SSR-RBAC-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0187 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0188 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0189 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0190 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0191 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0192 | Shared Responsibility / CIA Needed | SSR-TOOL-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0193 | Shared Responsibility / CIA Needed | SSR-BOOT-004 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0194 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0195 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0196 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0197 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0198 | Covered by Existing Supplier System Requirement | SSR-COM-006 | Low | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0199 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0200 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0201 | Derive Supplier System Requirement | SSR-DIAG-005 | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-CVS124-0202 | Covered by Existing Supplier System Requirement | SSR-SYS-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0203 | Covered by Existing Supplier System Requirement | SSR-DIAG-003 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0204 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0205 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0206 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0207 | Derive Supplier System Requirement | SSR-DIAG-006 | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-CVS124-0208 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0209 | Covered by Existing Supplier System Requirement | SSR-HW-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0210 | Covered by Existing Supplier System Requirement | SSR-KEY-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0211 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0212 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0213 | Covered by Existing Supplier System Requirement | SSR-SYS-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0214 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0215 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0216 | Covered by Existing Supplier System Requirement | SSR-SYS-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0217 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0218 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0219 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0220 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0221 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0222 | Covered by Existing Supplier System Requirement | SSR-SYS-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0223 | Covered by Existing Supplier System Requirement | SSR-DIAG-004 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0224 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0225 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0226 | Covered by Existing Supplier System Requirement | SSR-DIAG-004 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0227 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0228 | Covered by Existing Supplier System Requirement | SSR-SYS-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0229 | Covered by Existing Supplier System Requirement | SSR-DIAG-004 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0230 | Covered by Existing Supplier System Requirement | SSR-DIAG-004 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0231 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0232 | Covered by Existing Supplier System Requirement | SSR-DIAG-004 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0233 | Covered by Existing Supplier System Requirement | SSR-DIAG-004 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0234 | Covered by Existing Supplier System Requirement | SSR-DIAG-004 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0235 | Covered by Existing Supplier System Requirement | SSR-DIAG-004 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0236 | Covered by Existing Supplier System Requirement | SSR-DIAG-004 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0237 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0238 | Covered by Existing Supplier System Requirement | SSR-DIAG-006 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0239 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0240 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0241 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0242 | Covered by Existing Supplier System Requirement | SSR-DIAG-003 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0243 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0244 | Covered by Existing Supplier System Requirement | SSR-SYS-003 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0245 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0246 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0247 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0248 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0249 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0250 | Covered by Existing Supplier System Requirement | SSR-SYS-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0251 | Covered by Existing Supplier System Requirement | SSR-DIAG-004 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0252 | Covered by Existing Supplier System Requirement | SSR-DIAG-004 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0253 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0254 | Covered by Existing Supplier System Requirement | SSR-SYS-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0255 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0256 | Covered by Existing Supplier System Requirement | SSR-DIAG-004 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0257 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0258 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0259 | Covered by Existing Supplier System Requirement | SSR-SYS-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0260 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0261 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0262 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0263 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0264 | Covered by Existing Supplier System Requirement | SSR-SYS-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0265 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0266 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0267 | Covered by Existing Supplier System Requirement | SSR-SYS-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0268 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0269 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0270 | Shared Responsibility / CIA Needed | SSR-HW-001 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0271 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0272 | Shared Responsibility / CIA Needed | SSR-TOOL-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0273 | Covered by Existing Supplier System Requirement | SSR-SDT-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0274 | Shared Responsibility / CIA Needed | SSR-TOOL-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0275 | Shared Responsibility / CIA Needed | SSR-TOOL-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0276 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0277 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0278 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0279 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0280 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0281 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0282 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0283 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0284 | Covered by Existing Supplier System Requirement | SSR-SYS-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0285 | Covered by Existing Supplier System Requirement | SSR-SYS-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0286 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0287 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0288 | Covered by Existing Supplier System Requirement | SSR-SYS-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0289 | Covered by Existing Supplier System Requirement | SSR-SYS-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0290 | Covered by Existing Supplier System Requirement | SSR-SYS-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0291 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0292 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0293 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0294 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0295 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0296 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0297 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0298 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0299 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0300 | Covered by Existing Supplier System Requirement | SSR-SYS-003 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0301 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0302 | Covered by Existing Supplier System Requirement | SSR-SYS-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0303 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0304 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0305 | Covered by Existing Supplier System Requirement | SSR-RBAC-004 | Low | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0306 | Shared Responsibility / CIA Needed | SSR-RBAC-004 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0307 | Covered by Existing Supplier System Requirement | SSR-RBAC-004 | Low | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0308 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0309 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0310 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0311 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0312 | Covered by Existing Supplier System Requirement | SSR-SYS-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0313 | Covered by Existing Supplier System Requirement | SSR-SYS-003 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0314 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0315 | Covered by Existing Supplier System Requirement | SSR-SYS-003 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0316 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0317 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0318 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0319 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0320 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0321 | Covered by Existing Supplier System Requirement | SSR-SYS-003 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0322 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0323 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0324 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0325 | Covered by Existing Supplier System Requirement | SSR-SYS-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0326 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0327 | Covered by Existing Supplier System Requirement | SSR-UPD-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0328 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0329 | Covered by Existing Supplier System Requirement | SSR-UPD-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0330 | Covered by Existing Supplier System Requirement | SSR-UPD-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0331 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0332 | Covered by Existing Supplier System Requirement | SSR-SYS-003 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0333 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0334 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0335 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0336 | Covered by Existing Supplier System Requirement | SSR-UPD-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0337 | Covered by Existing Supplier System Requirement | SSR-UPD-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0338 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0339 | Covered by Existing Supplier System Requirement | SSR-UPD-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0340 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0341 | Shared Responsibility / CIA Needed | SSR-TOOL-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0342 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0343 | Covered by Existing Supplier System Requirement | SSR-BOOT-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0344 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0345 | Shared Responsibility / CIA Needed | SSR-TOOL-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0346 | Covered by Existing Supplier System Requirement | SSR-SDT-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0347 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0348 | Covered by Existing Supplier System Requirement | SSR-UPD-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0349 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0350 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0351 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0352 | Covered by Existing Supplier System Requirement | SSR-SYS-003 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0353 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0354 | Covered by Existing Supplier System Requirement | SSR-BOOT-004 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0355 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0356 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0357 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0358 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0359 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0360 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0361 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0362 | Shared Responsibility / CIA Needed | SSR-DAI-006 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0363 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0364 | Shared Responsibility / CIA Needed | SSR-TOOL-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0365 | Shared Responsibility / CIA Needed | SSR-DAI-006 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0366 | Covered by Existing Supplier System Requirement | SSR-UPD-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0367 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0368 | Covered by Existing Supplier System Requirement | SSR-SYS-003 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0369 | Derive Supplier System Requirement | SSR-DAI-007 | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-CVS124-0370 | Covered by Existing Supplier System Requirement | SSR-DAI-005 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0371 | Covered by Existing Supplier System Requirement | SSR-DAI-007 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0372 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0373 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0374 | Covered by Existing Supplier System Requirement | SSR-SYS-003 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0375 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0376 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0377 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0378 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0379 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0380 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0381 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0382 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0383 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0384 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0385 | Shared Responsibility / CIA Needed | SSR-DAI-004 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0386 | Shared Responsibility / CIA Needed | SSR-DAI-004 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0387 | Shared Responsibility / CIA Needed | SSR-DAI-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0388 | Covered by Existing Supplier System Requirement | SSR-UPD-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0389 | Shared Responsibility / CIA Needed | SSR-UPD-001 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0390 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0391 | Covered by Existing Supplier System Requirement | SSR-UPD-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0392 | Covered by Existing Supplier System Requirement | SSR-UPD-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0393 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0394 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0395 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0396 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0397 | Shared Responsibility / CIA Needed | SSR-UPD-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0398 | Covered by Existing Supplier System Requirement | SSR-SYS-003 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0399 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0400 | Covered by Existing Supplier System Requirement | SSR-DIAG-003 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0401 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0402 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0403 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0404 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0405 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0406 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0407 | Covered by Existing Supplier System Requirement | SSR-DIAG-003 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0408 | Covered by Existing Supplier System Requirement | SSR-DIAG-003 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0409 | Covered by Existing Supplier System Requirement | SSR-DIAG-003 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0410 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0411 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0412 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0413 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0414 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0415 | Covered by Existing Supplier System Requirement | SSR-DIAG-003 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0416 | Covered by Existing Supplier System Requirement | SSR-DIAG-003 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0417 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0418 | Covered by Existing Supplier System Requirement | SSR-DIAG-003 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0419 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0420 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0421 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0422 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0423 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0424 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0425 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0426 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0427 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0428 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0429 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0430 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0431 | Shared Responsibility / CIA Needed | SSR-RBAC-001 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0432 | Covered by Existing Supplier System Requirement | SSR-RBAC-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0433 | Shared Responsibility / CIA Needed | SSR-COM-004 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0434 | Shared Responsibility / CIA Needed | SSR-TOOL-004 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0435 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0436 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0437 | Covered by Existing Supplier System Requirement | SSR-SYS-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0438 | Shared Responsibility / CIA Needed | SSR-TOOL-004 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0439 | Shared Responsibility / CIA Needed | SSR-TOOL-004 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0440 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0441 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0442 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0443 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0444 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0445 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0446 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0447 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0448 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0449 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0450 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0451 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0452 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0453 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0454 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0455 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0456 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0457 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0458 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0459 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0460 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0461 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0462 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0463 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0464 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS124-0465 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0001 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS151-0002 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS151-0003 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS151-0004 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS151-0005 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0006 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0007 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0008 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0009 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0010 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0011 | Derive Supplier System Requirement | SSR-RBAC-005 | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-CVS151-0012 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0013 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0014 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS151-0015 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0016 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS151-0017 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0018 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS151-0019 | Shared Responsibility / CIA Needed | SSR-RBAC-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS151-0020 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0021 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0022 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0023 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS151-0024 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0025 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0026 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0027 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0028 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS151-0029 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0030 | Shared Responsibility / CIA Needed | SSR-RBAC-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS151-0031 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0032 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS151-0033 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS151-0034 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0035 | Shared Responsibility / CIA Needed | SSR-RBAC-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS151-0036 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS151-0037 | Shared Responsibility / CIA Needed | SSR-RBAC-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS151-0038 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0039 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0040 | Shared Responsibility / CIA Needed | SSR-RBAC-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS151-0041 | Shared Responsibility / CIA Needed | SSR-RBAC-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS151-0042 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0043 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0044 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS151-0045 | Shared Responsibility / CIA Needed | SSR-RBAC-001 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS151-0046 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0047 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0048 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS151-0049 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS151-0050 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS151-0051 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS151-0052 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0053 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS151-0054 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS151-0055 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS151-0056 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0057 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS151-0058 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS151-0059 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0060 | Shared Responsibility / CIA Needed | SSR-KEY-001 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS151-0061 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0062 | Shared Responsibility / CIA Needed | SSR-RBAC-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS151-0063 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0064 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0065 | Shared Responsibility / CIA Needed | SSR-COM-004 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS151-0066 | Shared Responsibility / CIA Needed | SSR-KEY-001 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS151-0067 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0068 | Shared Responsibility / CIA Needed | SSR-RBAC-004 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS151-0069 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0070 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0071 | Shared Responsibility / CIA Needed | SSR-RBAC-004 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS151-0072 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0073 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS151-0074 | Shared Responsibility / CIA Needed | SSR-RBAC-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS151-0075 | Shared Responsibility / CIA Needed | SSR-RBAC-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS151-0076 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0077 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0078 | Covered by Existing Supplier System Requirement | SSR-RBAC-005 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS151-0079 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS151-0080 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS151-0081 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS151-0082 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0083 | Shared Responsibility / CIA Needed | SSR-RBAC-001 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS151-0084 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0085 | Shared Responsibility / CIA Needed | SSR-RBAC-004 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS151-0086 | Shared Responsibility / CIA Needed | SSR-RBAC-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS151-0087 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0088 | Shared Responsibility / CIA Needed | SSR-RBAC-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS151-0089 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0090 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS151-0091 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS151-0092 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS151-0093 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS151-0094 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS154-0001 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS154-0002 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS154-0003 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS154-0004 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS154-0005 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS154-0006 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS154-0007 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS154-0008 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS154-0009 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS154-0010 | Shared Responsibility / CIA Needed | SSR-VV-002 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS154-0011 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS154-0012 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS154-0013 | Shared Responsibility / CIA Needed | SSR-VV-002 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS154-0014 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS154-0015 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS154-0016 | Shared Responsibility / CIA Needed | SSR-VV-002 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS154-0017 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS154-0018 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS154-0019 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS154-0020 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS154-0021 | Covered by Existing Supplier System Requirement | SSR-VV-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS154-0022 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS154-0023 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS154-0024 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS154-0025 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS154-0026 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS154-0027 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS154-0028 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS154-0029 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS154-0030 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS154-0031 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS154-0032 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS154-0033 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS154-0034 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS154-0035 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS154-0036 | Covered by Existing Supplier System Requirement | SSR-COM-009 | Low | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS154-0037 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS154-0038 | Shared Responsibility / CIA Needed | SSR-TOOL-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS154-0039 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS154-0040 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS154-0041 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS154-0042 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS154-0043 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS154-0044 | Covered by Existing Supplier System Requirement | SSR-KEY-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS154-0045 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS154-0046 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS154-0047 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS31-0001 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS31-0002 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS31-0003 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS31-0004 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS31-0005 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS31-0006 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS31-0007 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS31-0008 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS31-0009 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS31-0010 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS31-0011 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0012 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS31-0013 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0014 | Shared Responsibility / CIA Needed | SSR-RBAC-006 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0015 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS31-0016 | Derive Supplier System Requirement | SSR-KEY-002 | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-CVS31-0017 | Shared Responsibility / CIA Needed | SSR-DAI-001 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0018 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0019 | Shared Responsibility / CIA Needed | SSR-KEY-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0020 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0021 | Shared Responsibility / CIA Needed | SSR-DAI-001 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0022 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0023 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0024 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS31-0025 | Covered by Existing Supplier System Requirement | SSR-SYS-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS31-0026 | Covered by Existing Supplier System Requirement | SSR-KEY-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS31-0027 | Shared Responsibility / CIA Needed | SSR-KEY-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0028 | Shared Responsibility / CIA Needed | SSR-KEY-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0029 | Covered by Existing Supplier System Requirement | SSR-KEY-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS31-0030 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0031 | Shared Responsibility / CIA Needed | SSR-TOOL-004 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0032 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0033 | Derive Supplier System Requirement | SSR-DAI-008 | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-CVS31-0034 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0035 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0036 | Shared Responsibility / CIA Needed | SSR-KEY-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0037 | Shared Responsibility / CIA Needed | SSR-KEY-001 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0038 | Shared Responsibility / CIA Needed | SSR-KEY-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0039 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0040 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS31-0041 | Shared Responsibility / CIA Needed | SSR-DAI-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0042 | Shared Responsibility / CIA Needed | SSR-RBAC-004 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0043 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0044 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0045 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0046 | Shared Responsibility / CIA Needed | SSR-DAI-006 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0047 | Shared Responsibility / CIA Needed | SSR-COM-004 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0048 | Shared Responsibility / CIA Needed | SSR-DAI-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0049 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS31-0050 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0051 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS31-0052 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0053 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0054 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS31-0055 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0056 | Covered by Existing Supplier System Requirement | SSR-DAI-008 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS31-0057 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0058 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0059 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0060 | Shared Responsibility / CIA Needed | SSR-COM-004 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0061 | Shared Responsibility / CIA Needed | SSR-DAI-006 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0062 | Shared Responsibility / CIA Needed | SSR-DAI-006 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0063 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0064 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0065 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS31-0066 | Covered by Existing Supplier System Requirement | SSR-RBAC-004 | Low | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS31-0067 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0068 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS31-0069 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0070 | Shared Responsibility / CIA Needed | SSR-COM-004 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0071 | Shared Responsibility / CIA Needed | SSR-COM-004 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0072 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0073 | Covered by Existing Supplier System Requirement | SSR-DAI-001 | Low | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS31-0074 | Covered by Existing Supplier System Requirement | SSR-KEY-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS31-0075 | Shared Responsibility / CIA Needed | SSR-KEY-001 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0076 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0077 | Covered by Existing Supplier System Requirement | SSR-KEY-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS31-0078 | Shared Responsibility / CIA Needed | SSR-KEY-001 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0079 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0080 | Shared Responsibility / CIA Needed | SSR-KEY-001 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0081 | Shared Responsibility / CIA Needed | SSR-DAI-001 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0082 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0083 | Shared Responsibility / CIA Needed | SSR-KEY-001 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0084 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS31-0085 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0086 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0087 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0088 | Covered by Existing Supplier System Requirement | SSR-KEY-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS31-0089 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS31-0090 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0091 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0092 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0093 | Shared Responsibility / CIA Needed | SSR-RBAC-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0094 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0095 | Shared Responsibility / CIA Needed | SSR-RBAC-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0096 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS31-0097 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0098 | Shared Responsibility / CIA Needed | SSR-RBAC-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0099 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS31-0100 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS31-0101 | Covered by Existing Supplier System Requirement | SSR-KEY-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS31-0102 | Covered by Existing Supplier System Requirement | SSR-KEY-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS31-0103 | Covered by Existing Supplier System Requirement | SSR-KEY-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS31-0104 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS31-0105 | Covered by Existing Supplier System Requirement | SSR-DAI-008 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS31-0106 | Shared Responsibility / CIA Needed | SSR-KEY-001 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0107 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0108 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0109 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0110 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0111 | Shared Responsibility / CIA Needed | SSR-DIAG-006 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0112 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0113 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0114 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0115 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0116 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0117 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0118 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0119 | Shared Responsibility / CIA Needed | SSR-DIAG-006 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0120 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0121 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0122 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0123 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0124 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0125 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0126 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0127 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0128 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0129 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0130 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0131 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0132 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0133 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0134 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0135 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0136 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0137 | Covered by Existing Supplier System Requirement | SSR-KEY-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS31-0138 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS31-0139 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0140 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0141 | Shared Responsibility / CIA Needed | SSR-COM-006 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0142 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS31-0143 | Shared Responsibility / CIA Needed | SSR-RBAC-004 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0144 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0145 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0146 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS31-0147 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0148 | Covered by Existing Supplier System Requirement | SSR-TOOL-002 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS31-0149 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0150 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0151 | Shared Responsibility / CIA Needed | SSR-TOOL-002 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0152 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS31-0153 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0154 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0155 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS31-0156 | Shared Responsibility / CIA Needed | SSR-KEY-003 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0157 | Shared Responsibility / CIA Needed | SSR-COM-004 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0158 | Shared Responsibility / CIA Needed | SSR-COM-004 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS31-0159 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0160 | Covered by Existing Supplier System Requirement | SSR-SYS-001 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS31-0161 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0162 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0163 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0164 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0165 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS31-0166 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0167 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0168 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0169 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0170 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0171 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0172 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0173 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0174 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0175 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0176 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0177 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0178 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0179 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0180 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0181 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0182 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0183 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0184 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0185 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0186 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0187 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0188 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0189 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0190 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0191 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0192 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0193 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0194 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0195 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0196 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0197 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0198 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0199 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0200 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0201 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0202 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0203 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0204 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0205 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0206 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0207 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0208 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0209 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0210 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0211 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0212 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0213 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0214 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0215 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0216 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0217 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0218 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0219 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0220 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0221 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0222 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0223 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0224 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0225 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0226 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0227 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0228 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0229 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0230 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0231 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0232 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0233 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0234 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0235 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0236 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0237 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0238 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0239 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0240 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0241 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0242 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0243 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0244 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0245 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0246 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0247 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0248 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0249 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0250 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0251 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0252 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0253 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS31-0254 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0001 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS32-0002 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0003 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS32-0004 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS32-0005 | Covered by Existing Supplier System Requirement | None | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0006 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0007 | Shared Responsibility / CIA Needed | SSR-KEY-004 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS32-0008 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS32-0009 | Derive Supplier System Requirement | SSR-COM-010 | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-CVS32-0010 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0011 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0012 | Covered by Existing Supplier System Requirement | SSR-COM-010 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0013 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0014 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS32-0015 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0016 | Shared Responsibility / CIA Needed | SSR-RBAC-007 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS32-0017 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0018 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0019 | Shared Responsibility / CIA Needed | SSR-COM-011 | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS32-0020 | Blocked by Customer Clarification | None | n/a | Needs customer clarification before derivation. |
| RFQX-CVS32-0021 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0022 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0023 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0024 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0025 | Shared Responsibility / CIA Needed | SSR-COM-009 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS32-0026 | Covered by Existing Supplier System Requirement | SSR-COM-007 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0027 | Shared Responsibility / CIA Needed | SSR-COM-009 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS32-0028 | Shared Responsibility / CIA Needed | SSR-COM-009 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS32-0029 | Covered by Existing Supplier System Requirement | SSR-COM-007 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0030 | Covered by Existing Supplier System Requirement | SSR-COM-007 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0031 | Shared Responsibility / CIA Needed | SSR-COM-009 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS32-0032 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0033 | Shared Responsibility / CIA Needed | SSR-COM-009 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS32-0034 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0035 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0036 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0037 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0038 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0039 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0040 | Covered by Existing Supplier System Requirement | SSR-COM-010 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0041 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0042 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0043 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0044 | Covered by Existing Supplier System Requirement | SSR-COM-007 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0045 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0046 | Covered by Existing Supplier System Requirement | SSR-COM-010 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0047 | Covered by Existing Supplier System Requirement | SSR-COM-007 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0048 | Shared Responsibility / CIA Needed | SSR-COM-009 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS32-0049 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0050 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0051 | Shared Responsibility / CIA Needed | SSR-KEY-004 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS32-0052 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0053 | Covered by Existing Supplier System Requirement | SSR-COM-010 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0054 | Shared Responsibility / CIA Needed | SSR-VV-004 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS32-0055 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0056 | Shared Responsibility / CIA Needed | SSR-KEY-004 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS32-0057 | Covered by Existing Supplier System Requirement | SSR-RBAC-006 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0058 | Covered by Existing Supplier System Requirement | SSR-COM-011 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0059 | Covered by Existing Supplier System Requirement | SSR-COM-011 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0060 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0061 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0062 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0063 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0064 | Covered by Existing Supplier System Requirement | SSR-COM-011 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0065 | Shared Responsibility / CIA Needed | SSR-KEY-004 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS32-0066 | Shared Responsibility / CIA Needed | SSR-KEY-004 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS32-0067 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0068 | Covered by Existing Supplier System Requirement | SSR-KEY-004 | Low | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0069 | Covered by Existing Supplier System Requirement | SSR-COM-010 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0070 | Covered by Existing Supplier System Requirement | SSR-COM-010 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0071 | Covered by Existing Supplier System Requirement | SSR-COM-007 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0072 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0073 | Derive Supplier System Requirement | SSR-DAI-009 | Low | Accepted requirement; seed of its SSR cluster. |
| RFQX-CVS32-0074 | Covered by Existing Supplier System Requirement | SSR-COM-007 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0075 | Covered by Existing Supplier System Requirement | SSR-COM-007 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0076 | Covered by Existing Supplier System Requirement | SSR-COM-007 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0077 | Covered by Existing Supplier System Requirement | SSR-COM-010 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0078 | Covered by Existing Supplier System Requirement | SSR-COM-007 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0079 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0080 | Shared Responsibility / CIA Needed | SSR-COM-009 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS32-0081 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0082 | Shared Responsibility / CIA Needed | SSR-DAI-009 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS32-0083 | Shared Responsibility / CIA Needed | SSR-COM-009 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS32-0084 | Shared Responsibility / CIA Needed | SSR-COM-009 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS32-0085 | Shared Responsibility / CIA Needed | SSR-COM-009 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS32-0086 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0087 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0088 | Covered by Existing Supplier System Requirement | SSR-COM-007 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0089 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0090 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0091 | Covered by Existing Supplier System Requirement | SSR-COM-011 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0092 | Shared Responsibility / CIA Needed | SSR-DAI-009 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS32-0093 | Shared Responsibility / CIA Needed | SSR-DAI-009 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS32-0094 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0095 | Covered by Existing Supplier System Requirement | SSR-KEY-004 | Low | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0096 | Covered by Existing Supplier System Requirement | SSR-COM-010 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0097 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0098 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0099 | Covered by Existing Supplier System Requirement | SSR-COM-010 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0100 | Covered by Existing Supplier System Requirement | SSR-COM-007 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0101 | Covered by Existing Supplier System Requirement | SSR-COM-007 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0102 | Covered by Existing Supplier System Requirement | SSR-COM-007 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0103 | Covered by Existing Supplier System Requirement | SSR-COM-010 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0104 | Covered by Existing Supplier System Requirement | SSR-COM-007 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0105 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0106 | Shared Responsibility / CIA Needed | SSR-COM-012 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS32-0107 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0108 | Shared Responsibility / CIA Needed | SSR-COM-009 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS32-0109 | Shared Responsibility / CIA Needed | SSR-COM-009 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS32-0110 | Shared Responsibility / CIA Needed | SSR-COM-009 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS32-0111 | Covered by Existing Supplier System Requirement | SSR-COM-007 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0112 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0113 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0114 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0115 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0116 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0117 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0118 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0119 | Shared Responsibility / CIA Needed | SSR-COM-009 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS32-0120 | Shared Responsibility / CIA Needed | SSR-COM-013 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS32-0121 | Shared Responsibility / CIA Needed | SSR-COM-009 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS32-0122 | Shared Responsibility / CIA Needed | SSR-COM-009 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS32-0123 | Shared Responsibility / CIA Needed | SSR-COM-009 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS32-0124 | Shared Responsibility / CIA Needed | SSR-COM-009 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS32-0125 | Shared Responsibility / CIA Needed | SSR-COM-009 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS32-0126 | Shared Responsibility / CIA Needed | SSR-COM-009 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS32-0127 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0128 | Shared Responsibility / CIA Needed | SSR-COM-009 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS32-0129 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0130 | Shared Responsibility / CIA Needed | SSR-COM-009 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS32-0131 | Shared Responsibility / CIA Needed | SSR-COM-009 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS32-0132 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0133 | Shared Responsibility / CIA Needed | SSR-DAI-009 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS32-0134 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0135 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0136 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0137 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0138 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0139 | Covered by Existing Supplier System Requirement | SSR-DAI-009 | Low | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0140 | Covered by Existing Supplier System Requirement | SSR-COM-010 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0141 | Covered by Existing Supplier System Requirement | SSR-COM-010 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0142 | Covered by Existing Supplier System Requirement | SSR-COM-010 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0143 | Covered by Existing Supplier System Requirement | SSR-COM-010 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0144 | Covered by Existing Supplier System Requirement | SSR-COM-010 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0145 | Covered by Existing Supplier System Requirement | SSR-COM-010 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0146 | Covered by Existing Supplier System Requirement | SSR-COM-010 | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS32-0147 | Shared Responsibility / CIA Needed | SSR-COM-009 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS32-0148 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0149 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0150 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0151 | Shared Responsibility / CIA Needed | SSR-COM-009 | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS32-0152 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0153 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0154 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0155 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0156 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0157 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0158 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0159 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0160 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0161 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0162 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0163 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0164 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0165 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0166 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0167 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0168 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0169 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0170 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0171 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0172 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0173 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0174 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0175 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0176 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0177 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0178 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0179 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0180 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0181 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0182 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0183 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0184 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0185 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0186 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0187 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0188 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0189 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0190 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0191 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0192 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0193 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0194 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0195 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0196 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0197 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0198 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0199 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0200 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0201 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0202 | Informational Only | None | n/a | Non-binding; not derived. |
| RFQX-CVS32-0203 | Informational Only | None | n/a | Non-binding; not derived. |
SSR Detail
Show all 71 SSR detail blocks
SSR-CON-001 - Security evidence and traceability — Cybersecurity Concept and Evidence (Candidate)
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).
Derivation rationale: 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.
Allocated: feature Security evidence and traceability | capability Cybersecurity requirement handling | interface OEM/Customer Review Interface
Responsibility: Supplier-Owned | Verification: Review + Test + table/diagram context review | Confidence: Medium
Derived from (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
SSR-VIH-001 - Vulnerability and Incident Handling — Vulnerability and Incident Handling (Candidate)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Vulnerability and Incident Handling | capability Vulnerability management | interface OEM/Customer Review Interface
Responsibility: Supplier-Owned | Verification: Review + Test + table/diagram context review | Confidence: Medium
Derived from (2): RFQX-1001379436-P10-000-01-0008;RFQX-1001379436-P10-000-01-0048
SSR-CON-002 - Cybersecurity Concept and Evidence — Cybersecurity Concept and Evidence (Ready for Customer Alignment)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Cybersecurity Concept and Evidence | capability Cybersecurity requirement handling | interface OEM/Customer Review Interface
Responsibility: Shared | Verification: Review + Test + table/diagram context review | Confidence: Medium
Derived from (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
SSR-CON-003 - Security evidence and traceability — Cybersecurity Concept and Evidence (Candidate)
Statement: 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).
Derivation rationale: Clustered from 1 customer requirements allocated to 'Cybersecurity Concept and Evidence' / 'Security evidence and traceability' (e.g. RFQX-1001379436-P10-000-01-0021).
Allocated: feature Security evidence and traceability | capability None | interface OEM/Customer Review Interface
Responsibility: Supplier-Owned | Verification: Review + Test | Confidence: Medium
Derived from (1): RFQX-1001379436-P10-000-01-0021
SSR-HW-001 - Hardware / HSM / Secure Storage — Hardware / HSM / Secure Storage (Ready for Customer Alignment)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Hardware / HSM / Secure Storage | capability None | interface OEM/Customer Review Interface
Responsibility: Shared | Verification: Review + Test + table/diagram context review | Confidence: Medium
Derived from (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;RFQX-CVS124-0209;RFQX-CVS124-0270
SSR-DAI-001 - Data Authenticity and Integrity Verification — Data Authenticity and Integrity Verification (Blocked by Customer Clarification)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Data Authenticity and Integrity Verification | capability Authentication | interface OEM/Customer Review Interface
Responsibility: Shared | Verification: Review + Test + table/diagram context review | Confidence: Low
Derived from (5): RFQX-1001379436-P10-000-01-0025;RFQX-CVS31-0017;RFQX-CVS31-0021;RFQX-CVS31-0073;RFQX-CVS31-0081
SSR-SYS-001 - System Function — System Function (Candidate)
Statement: 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).
Derivation rationale: 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.
Allocated: feature System Function | capability None | interface OEM/Customer Review Interface
Responsibility: Supplier-Owned | Verification: Test + table/diagram context review | Confidence: Medium
Derived from (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;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;RFQX-CVS124-0334;RFQX-CVS124-0338;RFQX-CVS124-0350;RFQX-CVS124-0356;RFQX-CVS124-0367;RFQX-CVS124-0372;RFQX-CVS124-0373;RFQX-CVS124-0376;RFQX-CVS124-0383;RFQX-CVS124-0390;RFQX-CVS124-0402;RFQX-CVS124-0403;RFQX-CVS124-0404;RFQX-CVS124-0405;RFQX-CVS124-0410;RFQX-CVS124-0412;RFQX-CVS124-0417;RFQX-CVS124-0420;RFQX-CVS124-0421;RFQX-CVS124-0427;RFQX-CVS124-0435;RFQX-CVS151-0051;RFQX-CVS154-0031;RFQX-CVS154-0034;RFQX-CVS154-0037;RFQX-CVS154-0039;RFQX-CVS154-0041;RFQX-CVS31-0024;RFQX-CVS31-0040;RFQX-CVS31-0051;RFQX-CVS31-0054;RFQX-CVS31-0065;RFQX-CVS31-0084;RFQX-CVS31-0089;RFQX-CVS31-0100;RFQX-CVS31-0104;RFQX-CVS31-0138;RFQX-CVS31-0142;RFQX-CVS31-0146;RFQX-CVS31-0152;RFQX-CVS31-0155;RFQX-CVS31-0160
SSR-PROD-001 - Supplier Development and Production Hardening — Supplier Development and Production Hardening (Candidate)
Statement: 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).
Derivation rationale: 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).
Allocated: feature Supplier Development and Production Hardening | capability None | interface None
Responsibility: Supplier-Owned | Verification: Review + Test | Confidence: Medium
Derived from (1): RFQX-1001379436-P10-000-01-0029
SSR-COM-001 - OEM/Customer Review Interface — Secure Communication and Boundary Control (Ready for Customer Alignment)
Statement: 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).
Derivation rationale: 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).
Allocated: feature OEM/Customer Review Interface | capability None | interface OEM/Customer Review Interface
Responsibility: Shared | Verification: Review + Test | Confidence: Medium
Derived from (2): RFQX-1001379436-P10-000-01-0030;RFQX-1001379436-P10-000-01-0036
SSR-COM-002 - Secure Communication and Boundary Control — Secure Communication and Boundary Control (Candidate)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Secure Communication and Boundary Control | capability None | interface None
Responsibility: Supplier-Owned | Verification: Review + Test + table/diagram context review | Confidence: Medium
Derived from (4): RFQX-1001379436-P10-000-01-0031;RFQX-1001379436-P10-000-01-0034;RFQX-CVS123-2-0173;RFQX-CVS124-0172
SSR-COM-003 - OEM/Customer Review Interface — Secure Communication and Boundary Control (Candidate)
Statement: 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).
Derivation rationale: Clustered from 1 customer requirements allocated to 'Secure Communication and Boundary Control' / 'OEM/Customer Review Interface' (e.g. RFQX-1001379436-P10-000-01-0032).
Allocated: feature OEM/Customer Review Interface | capability None | interface OEM/Customer Review Interface
Responsibility: Supplier-Owned | Verification: Review + Test | Confidence: Medium
Derived from (1): RFQX-1001379436-P10-000-01-0032
SSR-KEY-001 - Key and Certificate Handling — Key and Certificate Handling (Blocked by Customer Clarification)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Key and Certificate Handling | capability Certificate handling | interface OEM/Customer Review Interface
Responsibility: Shared | Verification: Review + Test + table/diagram context review | Confidence: Medium
Derived from (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;RFQX-CVS31-0083;RFQX-CVS31-0088;RFQX-CVS31-0101;RFQX-CVS31-0102;RFQX-CVS31-0103;RFQX-CVS31-0106
SSR-VIH-002 - Vulnerability and Incident Handling — Vulnerability and Incident Handling (Candidate)
Statement: 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).
Derivation rationale: 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).
Allocated: feature Vulnerability and Incident Handling | capability None | interface OEM/Customer Review Interface
Responsibility: Supplier-Owned | Verification: Review + Test | Confidence: Medium
Derived from (3): RFQX-1001379436-P10-000-01-0047;RFQX-1001379436-P10-000-01-0049;RFQX-1001379436-P10-000-01-0050
SSR-VIH-003 - Vulnerability and Incident Handling — Vulnerability and Incident Handling (Ready for Customer Alignment)
Statement: 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).
Derivation rationale: 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).
Allocated: feature Vulnerability and Incident Handling | capability None | interface OEM/Customer Review Interface
Responsibility: Shared | Verification: Review + Test | Confidence: Medium
Derived from (2): RFQX-1001379436-P10-000-01-0054;RFQX-1001379436-P10-000-01-0055
SSR-VIH-004 - Vulnerability and Incident Handling — Vulnerability and Incident Handling (Candidate)
Statement: 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).
Derivation rationale: Clustered from 1 customer requirements allocated to 'Vulnerability and Incident Handling' / 'Vulnerability and Incident Handling' (e.g. RFQX-1001379436-P10-000-01-0058).
Allocated: feature Vulnerability and Incident Handling | capability None | interface External Interfaces
Responsibility: Supplier-Owned | Verification: Review + Test | Confidence: Medium
Derived from (1): RFQX-1001379436-P10-000-01-0058
SSR-LIFE-001 - Lifecycle / Field Return / Decommissioning — Lifecycle / Field Return / Decommissioning (Ready for Internal Review)
Statement: 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).
Derivation rationale: Clustered from 1 customer requirements allocated to 'Lifecycle / Field Return / Decommissioning' / 'Lifecycle / Field Return / Decommissioning' (e.g. RFQX-1001379436-P10-000-01-0062).
Allocated: feature Lifecycle / Field Return / Decommissioning | capability None | interface None
Responsibility: Supplier-Owned | Verification: Review + Test | Confidence: High
Derived from (1): RFQX-1001379436-P10-000-01-0062
SSR-LOG-001 - Security Logging and Event Handling — Security Logging and Event Handling (Candidate)
Statement: 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).
Derivation rationale: 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).
Allocated: feature Security Logging and Event Handling | capability Logging and audit trail | interface None
Responsibility: Supplier-Owned | Verification: Review + Test | Confidence: Medium
Derived from (1): RFQX-1001379436-P10-000-01-0067
SSR-COM-004 - Secure Communication and Boundary Control — Secure Communication and Boundary Control (Blocked by Customer Clarification)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Secure Communication and Boundary Control | capability None | interface None
Responsibility: Shared | Verification: Review + Test + table/diagram context review | Confidence: Low
Derived from (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
SSR-DAI-002 - Data Authenticity and Integrity Verification — Data Authenticity and Integrity Verification (Candidate)
Statement: 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).
Derivation rationale: Clustered from 1 customer requirements allocated to 'Data Authenticity and Integrity Verification' / 'Data Authenticity and Integrity Verification' (e.g. RFQX-3299216-1-0031).
Allocated: feature Data Authenticity and Integrity Verification | capability None | interface External Interfaces
Responsibility: Supplier-Owned | Verification: Review + Test | Confidence: Medium
Derived from (1): RFQX-3299216-1-0031
SSR-TOOL-001 - Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage (Candidate)
Statement: The supplier shall provide the tooling, IT infrastructure and evidence storage required for Tooling / IT / Evidence Storage (Tooling domain; allocated to Engineering Toolchain).
Derivation rationale: Clustered from 1 customer requirements allocated to 'Tooling / IT / Evidence Storage' / 'Tooling / IT / Evidence Storage' (e.g. RFQX-3299216-1-0035).
Allocated: feature Tooling / IT / Evidence Storage | capability None | interface None
Responsibility: Supplier-Owned | Verification: Review + Test | Confidence: Medium
Derived from (1): RFQX-3299216-1-0035
SSR-DAI-003 - Data Authenticity and Integrity Verification — Data Authenticity and Integrity Verification (Ready for Customer Alignment)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Data Authenticity and Integrity Verification | capability None | interface None
Responsibility: Shared | Verification: Review + Test + table/diagram context review | Confidence: Low
Derived from (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
SSR-TOOL-002 - Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage (Blocked by Customer Clarification)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Tooling / IT / Evidence Storage | capability None | interface OEM/Customer Review Interface
Responsibility: Shared | Verification: Review + Test + table/diagram context review | Confidence: Medium
Derived from (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;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;RFQX-CVS154-0046;RFQX-CVS31-0012;RFQX-CVS31-0022;RFQX-CVS31-0030;RFQX-CVS31-0043;RFQX-CVS31-0045;RFQX-CVS31-0058;RFQX-CVS31-0059;RFQX-CVS31-0063;RFQX-CVS31-0067;RFQX-CVS31-0068;RFQX-CVS31-0113;RFQX-CVS31-0120;RFQX-CVS31-0128;RFQX-CVS31-0133;RFQX-CVS31-0134;RFQX-CVS31-0147;RFQX-CVS31-0148;RFQX-CVS31-0151
SSR-COM-005 - Secure Communication and Boundary Control — Secure Communication and Boundary Control (Blocked by Customer Clarification)
Statement: 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).
Derivation rationale: 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).
Allocated: feature Secure Communication and Boundary Control | capability None | interface None
Responsibility: Shared | Verification: Review + Test | Confidence: Medium
Derived from (3): RFQX-3299216-1-0041;RFQX-3299216-1-0042;RFQX-3299216-1-0083
SSR-COM-006 - Secure Communication and Boundary Control — Secure Communication and Boundary Control (Ready for Customer Alignment)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Secure Communication and Boundary Control | capability None | interface None
Responsibility: Shared | Verification: Review + Test + table/diagram context review | Confidence: Low
Derived from (5): RFQX-3299216-1-0061;RFQX-CVS123-2-0211;RFQX-CVS124-0168;RFQX-CVS124-0198;RFQX-CVS31-0141
SSR-SYS-002 - System Function — System Function (Candidate)
Statement: 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).
Derivation rationale: 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.
Allocated: feature System Function | capability None | interface OEM/Customer Review Interface
Responsibility: Supplier-Owned | Verification: Test + table/diagram context review | Confidence: Medium
Derived from (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;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
SSR-SYS-003 - System Function — System Function (Candidate)
Statement: 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).
Derivation rationale: 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.
Allocated: feature System Function | capability None | interface OEM/Customer Review Interface
Responsibility: Supplier-Owned | Verification: Test + table/diagram context review | Confidence: Medium
Derived from (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;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
SSR-COM-007 - External Interfaces — Secure Communication and Boundary Control (Candidate)
Statement: 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).
Derivation rationale: 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.
Allocated: feature External Interfaces | capability None | interface External Interfaces
Responsibility: Supplier-Owned | Verification: Review + Test + table/diagram context review | Confidence: Medium
Derived from (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;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
SSR-RBAC-001 - Secure Diagnostics / RBAC — Secure Diagnostics / RBAC (Blocked by Customer Clarification)
Statement: 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).
Derivation rationale: Clustered from 19 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.
Allocated: feature Secure Diagnostics / RBAC | capability Diagnostic security | interface OEM/Customer Review Interface
Responsibility: Shared | Verification: Review + Test + table/diagram context review | Confidence: Medium
Derived from (19): 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;RFQX-CVS124-0078;RFQX-CVS124-0171;RFQX-CVS124-0186;RFQX-CVS124-0431;RFQX-CVS124-0432;RFQX-CVS151-0045;RFQX-CVS151-0083
SSR-VV-001 - Security evidence and traceability — Verification and Validation (Candidate)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Security evidence and traceability | capability None | interface OEM/Customer Review Interface
Responsibility: Supplier-Owned | Verification: Review + Test + table/diagram context review | Confidence: Medium
Derived from (2): RFQX-3299216-1-0134;RFQX-CVS154-0021
SSR-DIAG-001 - Diagnostic Services — Diagnostic Services (Candidate)
Statement: 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).
Derivation rationale: Clustered from 1 customer requirements allocated to 'Diagnostic Services' / 'Diagnostic Services' (e.g. RFQX-3299216-1-0135).
Allocated: feature Diagnostic Services | capability None | interface External Interfaces
Responsibility: Supplier-Owned | Verification: Test | Confidence: Medium
Derived from (1): RFQX-3299216-1-0135
SSR-COM-008 - OEM/Customer Review Interface — Secure Communication and Boundary Control (Candidate)
Statement: 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).
Derivation rationale: Clustered from 1 customer requirements allocated to 'Secure Communication and Boundary Control' / 'OEM/Customer Review Interface' (e.g. RFQX-3299216-1-0137).
Allocated: feature OEM/Customer Review Interface | capability None | interface OEM/Customer Review Interface
Responsibility: Supplier-Owned | Verification: Review + Test | Confidence: Medium
Derived from (1): RFQX-3299216-1-0137
SSR-LIFE-002 - Lifecycle / Field Return / Decommissioning — Lifecycle / Field Return / Decommissioning (Ready for Internal Review)
Statement: 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).
Derivation rationale: Clustered from 1 customer requirements allocated to 'Lifecycle / Field Return / Decommissioning' / 'Lifecycle / Field Return / Decommissioning' (e.g. RFQX-3299216-1-0200).
Allocated: feature Lifecycle / Field Return / Decommissioning | capability None | interface None
Responsibility: Supplier-Owned | Verification: Review + Test | Confidence: High
Derived from (1): RFQX-3299216-1-0200
SSR-BOOT-001 - Secure software update and flash readiness — Bootloader and Application State Handling (Candidate)
Statement: 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).
Derivation rationale: Clustered from 2 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).
Allocated: feature Secure software update and flash readiness | capability None | interface None
Responsibility: Supplier-Owned | Verification: Review + Test | Confidence: Medium
Derived from (2): RFQX-CVS123-2-0037;RFQX-CVS123-2-0072
SSR-BOOT-002 - Secure software update and flash readiness — Bootloader and Application State Handling (Candidate)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Secure software update and flash readiness | capability None | interface None
Responsibility: Supplier-Owned | Verification: Review + Test + table/diagram context review | Confidence: Medium
Derived from (3): RFQX-CVS123-2-0039;RFQX-CVS123-2-0258;RFQX-CVS124-0343
SSR-UPD-001 - Secure software update and flash readiness — Software Update / Flashing (Blocked by Customer Clarification)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Secure software update and flash readiness | capability None | interface OEM/Customer Review Interface
Responsibility: Shared | Verification: Review + Test + table/diagram context review | Confidence: Medium
Derived from (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;RFQX-CVS124-0137;RFQX-CVS124-0140;RFQX-CVS124-0185;RFQX-CVS124-0389;RFQX-CVS124-0391
SSR-UPD-002 - Secure software update and flash readiness — Software Update / Flashing (Blocked by Customer Clarification)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Secure software update and flash readiness | capability None | interface OEM/Customer Review Interface
Responsibility: Shared | Verification: Review + Test + table/diagram context review | Confidence: Medium
Derived from (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;RFQX-CVS124-0337;RFQX-CVS124-0339;RFQX-CVS124-0348;RFQX-CVS124-0366;RFQX-CVS124-0388;RFQX-CVS124-0392
SSR-BOOT-003 - Bootloader and Application State Handling — Bootloader and Application State Handling (Candidate)
Statement: 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).
Derivation rationale: Clustered from 1 customer requirements allocated to 'Bootloader and Application State Handling' / 'Bootloader and Application State Handling' (e.g. RFQX-CVS123-2-0044).
Allocated: feature Bootloader and Application State Handling | capability None | interface None
Responsibility: Supplier-Owned | Verification: Review + Test | Confidence: Medium
Derived from (1): RFQX-CVS123-2-0044
SSR-DIAG-002 - Diagnostic Services — Diagnostic Services (Ready for Customer Alignment)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Diagnostic Services | capability None | interface OEM/Customer Review Interface
Responsibility: Shared | Verification: Test + table/diagram context review | Confidence: High
Derived from (2): RFQX-CVS123-2-0046;RFQX-CVS123-2-0251
SSR-DAI-004 - Data Authenticity and Integrity Verification — Data Authenticity and Integrity Verification (Ready for Customer Alignment)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Data Authenticity and Integrity Verification | capability None | interface None
Responsibility: Shared | Verification: Review + Test + table/diagram context review | Confidence: Low
Derived from (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
SSR-RBAC-002 - Secure software update and flash readiness — Secure Diagnostics / RBAC (Blocked by Customer Clarification)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Secure software update and flash readiness | capability Authentication | interface None
Responsibility: Shared | Verification: Review + Test + table/diagram context review | Confidence: Low
Derived from (3): RFQX-CVS123-2-0078;RFQX-CVS123-2-0079;RFQX-CVS123-2-0244
SSR-SDT-001 - Secure Data Transfer / Data Security Container — Secure Data Transfer / Data Security Container (Ready for Customer Alignment)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Secure Data Transfer / Data Security Container | capability None | interface None
Responsibility: Shared | Verification: Review + Test + table/diagram context review | Confidence: Medium
Derived from (6): RFQX-CVS123-2-0114;RFQX-CVS123-2-0204;RFQX-CVS123-2-0247;RFQX-CVS123-2-0261;RFQX-CVS124-0273;RFQX-CVS124-0346
SSR-UPD-003 - Secure software update and flash readiness — Software Update / Flashing (Blocked by Customer Clarification)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Secure software update and flash readiness | capability None | interface OEM/Customer Review Interface
Responsibility: Shared | Verification: Review + Test + table/diagram context review | Confidence: Low
Derived from (4): RFQX-CVS123-2-0164;RFQX-CVS123-2-0187;RFQX-CVS124-0142;RFQX-CVS124-0397
SSR-UPD-004 - Secure software update and flash readiness — Software Update / Flashing (Candidate)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Secure software update and flash readiness | capability None | interface OEM/Customer Review Interface
Responsibility: Supplier-Owned | Verification: Review + Test + table/diagram context review | Confidence: Medium
Derived from (6): RFQX-CVS123-2-0165;RFQX-CVS124-0024;RFQX-CVS124-0028;RFQX-CVS124-0031;RFQX-CVS124-0043;RFQX-CVS124-0074
SSR-TOOL-003 - Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage (Ready for Customer Alignment)
Statement: The supplier shall provide the tooling, IT infrastructure and evidence storage required for Tooling / IT / Evidence Storage (Software domain; allocated to Application Software).
Derivation rationale: 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.
Allocated: feature Tooling / IT / Evidence Storage | capability None | interface None
Responsibility: Shared | Verification: Review + Test + table/diagram context review | Confidence: Low
Derived from (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;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
SSR-BOOT-004 - Bootloader and Application State Handling — Bootloader and Application State Handling (Ready for Customer Alignment)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Bootloader and Application State Handling | capability None | interface None
Responsibility: Shared | Verification: Review + Test + table/diagram context review | Confidence: Medium
Derived from (3): RFQX-CVS123-2-0179;RFQX-CVS124-0193;RFQX-CVS124-0354
SSR-VV-002 - Security evidence and traceability — Verification and Validation (Ready for Customer Alignment)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Security evidence and traceability | capability None | interface OEM/Customer Review Interface
Responsibility: Shared | Verification: Review + Test + table/diagram context review | Confidence: Low
Derived from (5): RFQX-CVS123-2-0207;RFQX-CVS123-2-0335;RFQX-CVS154-0010;RFQX-CVS154-0013;RFQX-CVS154-0016
SSR-VV-003 - Security evidence and traceability — Verification and Validation (Ready for Customer Alignment)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Security evidence and traceability | capability None | interface OEM/Customer Review Interface
Responsibility: Shared | Verification: Review + Test + table/diagram context review | Confidence: Low
Derived from (3): RFQX-CVS123-2-0216;RFQX-CVS123-2-0217;RFQX-CVS123-2-0326
SSR-COM-009 - Secure communication and freshness protection — Secure Communication and Boundary Control (Blocked by Customer Clarification)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Secure communication and freshness protection | capability None | interface None
Responsibility: Shared | Verification: Review + Test + table/diagram context review | Confidence: Low
Derived from (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;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
SSR-DAI-005 - Security evidence and traceability — Data Authenticity and Integrity Verification (Ready for Customer Alignment)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Security evidence and traceability | capability None | interface OEM/Customer Review Interface
Responsibility: Shared | Verification: Review + Test + table/diagram context review | Confidence: Medium
Derived from (2): RFQX-CVS123-2-0285;RFQX-CVS124-0370
SSR-RBAC-003 - Secure Diagnostics / RBAC — Secure Diagnostics / RBAC (Blocked by Customer Clarification)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Secure Diagnostics / RBAC | capability None | interface None
Responsibility: Shared | Verification: Review + Test + table/diagram context review | Confidence: Low
Derived from (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;RFQX-CVS31-0093;RFQX-CVS31-0095;RFQX-CVS31-0098
SSR-RBAC-004 - Secure Diagnostics / RBAC — Secure Diagnostics / RBAC (Blocked by Customer Clarification)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Secure Diagnostics / RBAC | capability None | interface None
Responsibility: Shared | Verification: Review + Test + table/diagram context review | Confidence: Low
Derived from (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
SSR-DIAG-003 - Diagnostic Services — Diagnostic Services (Candidate)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Diagnostic Services | capability None | interface OEM/Customer Review Interface
Responsibility: Supplier-Owned | Verification: Test + table/diagram context review | Confidence: Medium
Derived from (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
SSR-DIAG-004 - Diagnostic Services — Diagnostic Services (Candidate)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Diagnostic Services | capability None | interface None
Responsibility: Supplier-Owned | Verification: Test + table/diagram context review | Confidence: Medium
Derived from (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;RFQX-CVS124-0256
SSR-DIAG-005 - Diagnostic Services — Diagnostic Services (Candidate)
Statement: 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).
Derivation rationale: Clustered from 1 customer requirements allocated to 'Diagnostic Services' / 'Diagnostic Services' (e.g. RFQX-CVS124-0201). Linked source table/diagram context was considered.
Allocated: feature Diagnostic Services | capability None | interface None
Responsibility: Supplier-Owned | Verification: Test + table/diagram context review | Confidence: Medium
Derived from (1): RFQX-CVS124-0201
SSR-DIAG-006 - Diagnostic Services — Diagnostic Services (Blocked by Customer Clarification)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Diagnostic Services | capability None | interface None
Responsibility: Shared | Verification: Test + table/diagram context review | Confidence: Medium
Derived from (4): RFQX-CVS124-0207;RFQX-CVS124-0238;RFQX-CVS31-0111;RFQX-CVS31-0119
SSR-DAI-006 - Security evidence and traceability — Data Authenticity and Integrity Verification (Blocked by Customer Clarification)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Security evidence and traceability | capability None | interface OEM/Customer Review Interface
Responsibility: Shared | Verification: Review + Test + table/diagram context review | Confidence: Low
Derived from (5): RFQX-CVS124-0362;RFQX-CVS124-0365;RFQX-CVS31-0046;RFQX-CVS31-0061;RFQX-CVS31-0062
SSR-DAI-007 - Security evidence and traceability — Data Authenticity and Integrity Verification (Candidate)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Security evidence and traceability | capability None | interface OEM/Customer Review Interface
Responsibility: Supplier-Owned | Verification: Review + Test + table/diagram context review | Confidence: Medium
Derived from (2): RFQX-CVS124-0369;RFQX-CVS124-0371
SSR-TOOL-004 - Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage (Ready for Customer Alignment)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Tooling / IT / Evidence Storage | capability None | interface OEM/Customer Review Interface
Responsibility: Shared | Verification: Review + Test + table/diagram context review | Confidence: Low
Derived from (4): RFQX-CVS124-0434;RFQX-CVS124-0438;RFQX-CVS124-0439;RFQX-CVS31-0031
SSR-RBAC-005 - Secure Diagnostics / RBAC — Secure Diagnostics / RBAC (Candidate)
Statement: 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).
Derivation rationale: Clustered from 2 customer requirements allocated to 'Secure Diagnostics / RBAC' / 'Secure Diagnostics / RBAC' (e.g. RFQX-CVS151-0011, RFQX-CVS151-0078).
Allocated: feature Secure Diagnostics / RBAC | capability None | interface None
Responsibility: Supplier-Owned | Verification: Review + Test | Confidence: Medium
Derived from (2): RFQX-CVS151-0011;RFQX-CVS151-0078
SSR-RBAC-006 - Secure communication and freshness protection — Secure Diagnostics / RBAC (Blocked by Customer Clarification)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Secure communication and freshness protection | capability None | interface None
Responsibility: Shared | Verification: Review + Test + table/diagram context review | Confidence: Medium
Derived from (2): RFQX-CVS31-0014;RFQX-CVS32-0057
SSR-KEY-002 - Key and Certificate Handling — Key and Certificate Handling (Candidate)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Key and Certificate Handling | capability None | interface None
Responsibility: Supplier-Owned | Verification: Review + Test + table/diagram context review | Confidence: Medium
Derived from (5): RFQX-CVS31-0016;RFQX-CVS31-0026;RFQX-CVS31-0029;RFQX-CVS31-0077;RFQX-CVS31-0137
SSR-KEY-003 - Key and Certificate Handling — Key and Certificate Handling (Blocked by Customer Clarification)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Key and Certificate Handling | capability None | interface None
Responsibility: Shared | Verification: Review + Test + table/diagram context review | Confidence: Low
Derived from (6): RFQX-CVS31-0019;RFQX-CVS31-0027;RFQX-CVS31-0028;RFQX-CVS31-0036;RFQX-CVS31-0038;RFQX-CVS31-0156
SSR-DAI-008 - Data Authenticity and Integrity Verification — Data Authenticity and Integrity Verification (Candidate)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Data Authenticity and Integrity Verification | capability None | interface None
Responsibility: Supplier-Owned | Verification: Review + Test + table/diagram context review | Confidence: Medium
Derived from (3): RFQX-CVS31-0033;RFQX-CVS31-0056;RFQX-CVS31-0105
SSR-KEY-004 - Secure communication and freshness protection — Key and Certificate Handling (Blocked by Customer Clarification)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Secure communication and freshness protection | capability Key management | interface None
Responsibility: Shared | Verification: Review + Test + table/diagram context review | Confidence: Low
Derived from (7): RFQX-CVS32-0007;RFQX-CVS32-0051;RFQX-CVS32-0056;RFQX-CVS32-0065;RFQX-CVS32-0066;RFQX-CVS32-0068;RFQX-CVS32-0095
SSR-COM-010 - Secure communication and freshness protection — Secure Communication and Boundary Control (Candidate)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Secure communication and freshness protection | capability None | interface None
Responsibility: Supplier-Owned | Verification: Review + Test + table/diagram context review | Confidence: Medium
Derived from (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;RFQX-CVS32-0141;RFQX-CVS32-0142;RFQX-CVS32-0143;RFQX-CVS32-0144;RFQX-CVS32-0145;RFQX-CVS32-0146
SSR-RBAC-007 - Secure communication and freshness protection — Secure Diagnostics / RBAC (Blocked by Customer Clarification)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Secure communication and freshness protection | capability Authentication | interface None
Responsibility: Shared | Verification: Review + Test + table/diagram context review | Confidence: Low
Derived from (1): RFQX-CVS32-0016
SSR-COM-011 - Secure communication and freshness protection — Secure Communication and Boundary Control (Blocked by Customer Clarification)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Secure communication and freshness protection | capability None | interface None
Responsibility: Shared | Verification: Review + Test + table/diagram context review | Confidence: Medium
Derived from (5): RFQX-CVS32-0019;RFQX-CVS32-0058;RFQX-CVS32-0059;RFQX-CVS32-0064;RFQX-CVS32-0091
SSR-VV-004 - Secure communication and freshness protection — Verification and Validation (Blocked by Customer Clarification)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Secure communication and freshness protection | capability None | interface OEM/Customer Review Interface
Responsibility: Shared | Verification: Review + Test + table/diagram context review | Confidence: Low
Derived from (1): RFQX-CVS32-0054
SSR-DAI-009 - Secure communication and freshness protection — Data Authenticity and Integrity Verification (Blocked by Customer Clarification)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Secure communication and freshness protection | capability Authentication | interface None
Responsibility: Shared | Verification: Review + Test + table/diagram context review | Confidence: Low
Derived from (6): RFQX-CVS32-0073;RFQX-CVS32-0082;RFQX-CVS32-0092;RFQX-CVS32-0093;RFQX-CVS32-0133;RFQX-CVS32-0139
SSR-COM-012 - OEM/Customer Review Interface — Secure Communication and Boundary Control (Blocked by Customer Clarification)
Statement: 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).
Derivation rationale: 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.
Allocated: feature OEM/Customer Review Interface | capability None | interface OEM/Customer Review Interface
Responsibility: Shared | Verification: Review + Test + table/diagram context review | Confidence: Low
Derived from (1): RFQX-CVS32-0106
SSR-COM-013 - Secure communication and freshness protection — Secure Communication and Boundary Control (Blocked by Customer Clarification)
Statement: 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).
Derivation rationale: 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.
Allocated: feature Secure communication and freshness protection | capability Secure communication | interface None
Responsibility: Shared | Verification: Review + Test + table/diagram context review | Confidence: Low
Derived from (1): RFQX-CVS32-0120