Product and cybersecurity architecture understanding package generated from Markdown-derived requirements.
Product and cybersecurity architecture understanding package generated from Markdown-derived requirements.
This table is horizontally scrollable. Use the bottom scrollbar to view all columns.
| Capability | Product Role | Architecture Component | Interfaces | Security Relevance | Evidence Status | Open Decision |
|---|---|---|---|---|---|---|
| Clutch Actuation Control | Core actuator control | Application Software / System Core | Vehicle Network Interface (CAN) | Safety-relevant command/status handling | Confirmed | Confirm final variant scope |
| Vehicle Integration and CAN Communication | Vehicle command/status exchange | External Interfaces / Application Software | Vehicle Network Interface (CAN), PWM wake-up | Message authenticity/freshness allocation | Confirmed | Confirm signal catalog and SecOC/SDT scope |
| Secure Diagnostics and Role-Based Access | Controlled service and engineering access | Diagnostic Server / Security Services | Diagnostic Tester Interface | Privileged access control | Inferred | Confirm roles, service list and lockout policy |
| Secure Software Update and Flash | Maintain trusted ECU software | Bootloader / Update Logic | Update / Flash Interface, Diagnostic Tester Interface | Software authenticity and integrity | Inferred | Confirm signing chain, rollback and ownership |
| Key and Certificate Handling | Trust-material lifecycle | Security Services / Hardware Platform | PKI / Provisioning Interface | Root of trust for diagnostics, update and secure communication | Inferred | Confirm HSM capability, key hierarchy and PKI ownership |
| Secure Data Transfer / Communication Boundary | Protected security-relevant data exchange | Security Services / External Interfaces | Vehicle Network Interface, Secure Data Transfer Interface | Authenticity, integrity and freshness | Inferred | Confirm protected signals and freshness model |
| Security Logging and Event Handling | Security evidence and response input | Security Services / Backend and IT Systems | Logging / Event Reporting Interface | Auditability and incident support | Inferred | Confirm event set, storage and reporting path |
| Cybersecurity Lifecycle and Evidence | Approval-ready security case | Compliance Process / Engineering Toolchain | Supplier Evidence, OEM Approval Interface | Traceable residual-risk argument | Confirmed | Confirm DIA split and approval authority |
Purpose: Core actuator control
Component mapping: Application Software / System Core
Interface mapping: Vehicle Network Interface (CAN)
Security mapping: Safety-relevant command/status handling
Evidence strength: Confirmed
Open decision: Confirm final variant scope
Purpose: Vehicle command/status exchange
Component mapping: External Interfaces / Application Software
Interface mapping: Vehicle Network Interface (CAN), PWM wake-up
Security mapping: Message authenticity/freshness allocation
Evidence strength: Confirmed
Open decision: Confirm signal catalog and SecOC/SDT scope
Purpose: Controlled service and engineering access
Component mapping: Diagnostic Server / Security Services
Interface mapping: Diagnostic Tester Interface
Security mapping: Privileged access control
Evidence strength: Inferred
Open decision: Confirm roles, service list and lockout policy
Purpose: Maintain trusted ECU software
Component mapping: Bootloader / Update Logic
Interface mapping: Update / Flash Interface, Diagnostic Tester Interface
Security mapping: Software authenticity and integrity
Evidence strength: Inferred
Open decision: Confirm signing chain, rollback and ownership
Purpose: Trust-material lifecycle
Component mapping: Security Services / Hardware Platform
Interface mapping: PKI / Provisioning Interface
Security mapping: Root of trust for diagnostics, update and secure communication
Evidence strength: Inferred
Open decision: Confirm HSM capability, key hierarchy and PKI ownership
Purpose: Protected security-relevant data exchange
Component mapping: Security Services / External Interfaces
Interface mapping: Vehicle Network Interface, Secure Data Transfer Interface
Security mapping: Authenticity, integrity and freshness
Evidence strength: Inferred
Open decision: Confirm protected signals and freshness model
Purpose: Security evidence and response input
Component mapping: Security Services / Backend and IT Systems
Interface mapping: Logging / Event Reporting Interface
Security mapping: Auditability and incident support
Evidence strength: Inferred
Open decision: Confirm event set, storage and reporting path
Purpose: Approval-ready security case
Component mapping: Compliance Process / Engineering Toolchain
Interface mapping: Supplier Evidence, OEM Approval Interface
Security mapping: Traceable residual-risk argument
Evidence strength: Confirmed
Open decision: Confirm DIA split and approval authority
flowchart LR
subgraph Capabilities["System capabilities"]
Actuation["Clutch actuation"]
Diagnostics["Secure diagnostics"]
UpdateCap["Secure update"]
Keys["Key and certificate handling"]
Evidence["Cybersecurity evidence"]
end
subgraph Components["Architecture components"]
App["Application software"]
DiagSrv["Diagnostic server"]
Boot["Bootloader / update logic"]
Sec["Security services"]
Tooling["Engineering evidence toolchain"]
end
Actuation --> App
Diagnostics --> DiagSrv
Diagnostics --> Sec
UpdateCap --> Boot
UpdateCap --> Sec
Keys --> Sec
Evidence --> Tooling
Evidence --> Sec
This feature model groups Markdown-derived requirement clusters into system-security architecture domains. It is not a flat requirement repeat.
Classification: Needs Customer Clarification
No feature cluster is confirmed in the current requirements. Customer clarification is needed.
Classification: Needs Customer Clarification
No feature cluster is confirmed in the current requirements. Customer clarification is needed.
Feature ID: FEAT-X001
Protect vehicle or client/server data exchanges against unauthorized origin, modification, replay, and stale state.
Turns SecOC/SDT-style requirements into a coherent communication security behavior.
Authentication/encryption, verify/decrypt processing, counters, replay checks, and discard behavior for invalid traffic.
Exact algorithms, key lengths, message IDs, and bus allocation need customer confirmation.
Vehicle network, ECU-to-ECU communication, client/server SDT flows.
Protected signals, counters, request/response payloads, authentication tags.
This feature directly protects integrity, authenticity, freshness, and in some cases confidentiality of vehicle data.
Low
Inferred from Requirements
Evidence Basis:
Classification: Needs Customer Clarification
No feature cluster is confirmed in the current requirements. Customer clarification is needed.
Classification: Needs Customer Clarification
No feature cluster is confirmed in the current requirements. Customer clarification is needed.
Classification: Needs Customer Clarification
No feature cluster is confirmed in the current requirements. Customer clarification is needed.
Feature ID: FEAT-X002
Ensure software update, flash, and IVD-related flows preserve authenticity, integrity, and regulatory evidence.
Supports UNECE-style software update obligations and safe maintenance of E/E components.
Update package handling, flash/programming paths, integrity validation data, and update evidence.
Update transport, campaign management, rollback policy, and production signing chain need confirmation.
Backend/update infrastructure, diagnostic/programming tool, ECU boot/update manager, PKI.
Software packages, signatures, IVD data, certificates, programming requests, update logs.
Unauthorized or corrupted software undermines ECU authenticity and all data security goals.
Low
Inferred from Requirements
Evidence Basis:
Feature ID: FEAT-X003
Provide proof that requirements, controls, architecture decisions, verification, validation, and residual risk remain connected.
Gives reviewers a way to audit security decisions before accepting the architecture.
Traceability matrices, evidence reports, human-review queues, quality gates, and open decisions.
Customer acceptance workflow and evidence repository ownership are not confirmed.
ALM/evidence repository, OEM/customer review, supplier security process.
Requirement IDs, source sections, controls, test reports, decisions, open questions.
Without evidence traceability, control implementation cannot be credibly argued.
Medium
Inferred from Requirements
Evidence Basis:
| Feature | Domain | Interfaces | Evidence basis | Classification |
|---|---|---|---|---|
| Secure communication and freshness protection | Communication and Connectivity Capabilities | Vehicle network, ECU-to-ECU communication, client/server SDT flows. | RFQX-CVS123-2-0241; RFQX-CVS154-0036; RFQX-CVS31-0014; RFQX-CVS31-0015; RFQX-CVS32-0007; RFQX-CVS32-0009; RFQX-CVS32-0012; RFQX-CVS32-0014; RFQX-CVS32-0016; RFQX-CVS32-0019 (sample: 10 of 201) | Inferred from Requirements |
| Secure software update and flash readiness | Operational and Lifecycle Capabilities | Backend/update infrastructure, diagnostic/programming tool, ECU boot/update manager, PKI. | RFQX-3299216-1-0176; RFQX-CVS123-2-0023; RFQX-CVS123-2-0030; RFQX-CVS123-2-0037; RFQX-CVS123-2-0039; RFQX-CVS123-2-0042; RFQX-CVS123-2-0043; RFQX-CVS123-2-0048; RFQX-CVS123-2-0049; RFQX-CVS123-2-0050 (sample: 10 of 131) | Inferred from Requirements |
| Security evidence and traceability | Compliance and Evidence Capabilities | ALM/evidence repository, OEM/customer review, supplier security process. | RFQX-1001379436-P10-000-01-0003; RFQX-1001379436-P10-000-01-0005; RFQX-1001379436-P10-000-01-0007; RFQX-1001379436-P10-000-01-0010; RFQX-1001379436-P10-000-01-0017; RFQX-1001379436-P10-000-01-0018; RFQX-1001379436-P10-000-01-0019; RFQX-1001379436-P10-000-01-0021; RFQX-3299216-1-0018; RFQX-3299216-1-0109 (sample: 10 of 59) | Inferred from Requirements |
| Feature | Security capabilities | Evidence basis | Confidence | Classification |
|---|---|---|---|---|
| Secure communication and freshness protection | Secure communication; Cryptographic protection; Key management | RFQX-CVS123-2-0241; RFQX-CVS154-0036; RFQX-CVS31-0014; RFQX-CVS31-0015; RFQX-CVS32-0007; RFQX-CVS32-0009; RFQX-CVS32-0012; RFQX-CVS32-0014; RFQX-CVS32-0016; RFQX-CVS32-0019 (sample: 10 of 201) | Low | Inferred from Requirements |
| Secure software update and flash readiness | Secure software update; Secure boot and platform integrity; Key and certificate management | RFQX-3299216-1-0176; RFQX-CVS123-2-0023; RFQX-CVS123-2-0030; RFQX-CVS123-2-0037; RFQX-CVS123-2-0039; RFQX-CVS123-2-0042; RFQX-CVS123-2-0043; RFQX-CVS123-2-0048; RFQX-CVS123-2-0049; RFQX-CVS123-2-0050 (sample: 10 of 131) | Low | Inferred from Requirements |
| Security evidence and traceability | Compliance and evidence management; Development and toolchain security | RFQX-1001379436-P10-000-01-0003; RFQX-1001379436-P10-000-01-0005; RFQX-1001379436-P10-000-01-0007; RFQX-1001379436-P10-000-01-0010; RFQX-1001379436-P10-000-01-0017; RFQX-1001379436-P10-000-01-0018; RFQX-1001379436-P10-000-01-0019; RFQX-1001379436-P10-000-01-0021; RFQX-3299216-1-0018; RFQX-3299216-1-0109 (sample: 10 of 59) | Medium | Inferred from Requirements |
REQ-AUTO-00006: Review possible noise/boilerplate contamination.REQ_SEC_0040: Confirm whether this statement is a binding requirement.REQ_SEC_0041: Confirm whether this statement is a binding requirement.req-6.3: Confirm whether this statement is a binding requirement.REQ-AUTO-00146: Review possible noise/boilerplate contamination.Req.ID-Description-6.22.1: Confirm whether this statement is a binding requirement.REQ-AUTO-00171: Confirm whether this statement is a binding requirement.REQ-AUTO-00175: Confirm whether this statement is a binding requirement.REQ-AUTO-00190: Confirm whether this statement is a binding requirement. | Clarify ambiguous or incomplete source wording.REQ-AUTO-00246: Confirm whether this statement is a binding requirement.REQ-AUTO-00249: Confirm whether this statement is a binding requirement.REQ-AUTO-00250: Confirm whether this statement is a binding requirement.REQ-AUTO-00272: Confirm whether this statement is a binding requirement.REQ-AUTO-00278: Confirm whether this statement is a binding requirement.REQ-AUTO-00279: Confirm whether this statement is a binding requirement.REQ-AUTO-00284: Confirm whether this statement is a binding requirement.REQ-AUTO-00292: Confirm whether this statement is a binding requirement.REQ_UDS-0051: Confirm whether this statement is a binding requirement.REQ-AUTO-00294: Confirm whether this statement is a binding requirement.REQ_UDS-0051: Confirm whether this statement is a binding requirement.REQ-AUTO-00298: Confirm whether this statement is a binding requirement.REQ-AUTO-00317: Clarify ambiguous or incomplete source wording.REQ-AUTO-00335: Confirm whether this statement is a binding requirement.REQ-AUTO-00337: Confirm whether this statement is a binding requirement.REQ-AUTO-00338: Confirm whether this statement is a binding requirement.REQ_UDS-0051: Confirm whether this statement is a binding requirement.REQ-AUTO-00343: Confirm whether this statement is a binding requirement.REQ-AUTO-00378: Confirm whether this statement is a binding requirement.REQ-AUTO-00420: Confirm whether this statement is a binding requirement.REQ-AUTO-00480: Confirm whether this statement is a binding requirement.REQ-AUTO-00485: Confirm whether this statement is a binding requirement.REQ-AUTO-00488: Review possible noise/boilerplate contamination.REQ-AUTO-00492: Confirm whether this statement is a binding requirement.REQ_UDS-0003: Confirm whether this statement is a binding requirement.REQ_UDS-0004: Confirm whether this statement is a binding requirement.REQ_UDS-0006: Confirm whether this statement is a binding requirement.REQ_UDS-0007: Confirm whether this statement is a binding requirement.REQ_UDS-0008: Confirm whether this statement is a binding requirement.REQ_UDS-0010: Confirm whether this statement is a binding requirement.REQ_UDS-0014: Confirm whether this statement is a binding requirement.REQ_UDS-0015: Confirm whether this statement is a binding requirement.REQ_UDS-0016: Confirm whether this statement is a binding requirement.REQ_UDS-0017: Confirm whether this statement is a binding requirement.REQ_UDS-0020: Confirm whether this statement is a binding requirement.REQ_UDS-0339: Confirm whether this statement is a binding requirement.REQ_UDS-0340: Confirm whether this statement is a binding requirement.REQ_UDS-0341: Confirm whether this statement is a binding requirement.REQ_UDS-0023: Confirm whether this statement is a binding requirement.REQ_UDS-0025: Confirm whether this statement is a binding requirement.REQ_UDS-0030: Confirm whether this statement is a binding requirement.REQ_UDS-0032: Confirm whether this statement is a binding requirement.REQ_UDS-0033: Confirm whether this statement is a binding requirement.REQ_UDS-0036: Confirm whether this statement is a binding requirement.REQ_UDS-0037: Confirm whether this statement is a binding requirement.REQ_UDS-0038: Confirm whether this statement is a binding requirement.REQ_UDS-0041: Confirm whether this statement is a binding requirement.REQ_UDS-0045: Confirm whether this statement is a binding requirement.REQ_UDS-0049: Confirm whether this statement is a binding requirement.REQ_UDS-0051: Clarify ambiguous or incomplete source wording.REQ_UDS-0305: Confirm whether this statement is a binding requirement.REQ_UDS-0306: Confirm whether this statement is a binding requirement.REQ_UDS-0316: Confirm whether this statement is a binding requirement.REQ_UDS-0328: Confirm whether this statement is a binding requirement.REQ-AUTO-00563: Confirm whether this statement is a binding requirement.REQ_UDS-0073: Confirm whether this statement is a binding requirement.REQ_UDS-0074: Confirm whether this statement is a binding requirement.REQ_UDS-0078: Confirm whether this statement is a binding requirement.REQ-AUTO-00588: Confirm whether this statement is a binding requirement.REQ_UDS-0345: Confirm whether this statement is a binding requirement.REQ_UDS-0346: Confirm whether this statement is a binding requirement.REQ_UDS-0347: Confirm whether this statement is a binding requirement.REQ_UDS-0348: Confirm whether this statement is a binding requirement.REQ_UDS-0349: Confirm whether this statement is a binding requirement.REQ_UDS-0093: Confirm whether this statement is a binding requirement.REQ_UDS-0259: Confirm whether this statement is a binding requirement.REQ_UDS-0094: Confirm whether this statement is a binding requirement.REQ_UDS-0095: Confirm whether this statement is a binding requirement.REQ-AUTO-00629: Confirm whether this statement is a binding requirement.REQ-AUTO-00634: Clarify ambiguous or incomplete source wording.REQ_UDS-0103: Confirm whether this statement is a binding requirement.REQ_UDS-0104: Confirm whether this statement is a binding requirement.REQ_UDS-0105: Confirm whether this statement is a binding requirement.REQ_UDS-0107: Confirm whether this statement is a binding requirement.REQ-AUTO-00652: Confirm whether this statement is a binding requirement.REQ_UDS-0113: Confirm whether this statement is a binding requirement.REQ_UDS-0114: Confirm whether this statement is a binding requirement.REQ_UDS-0116: Confirm whether this statement is a binding requirement.REQ_UDS-0117: Confirm whether this statement is a binding requirement.REQ_UDS-0118: Confirm whether this statement is a binding requirement.REQ_UDS-0120: Confirm whether this statement is a binding requirement.REQ_UDS-0295: Confirm whether this statement is a binding requirement.REQ_UDS-0123: Confirm whether this statement is a binding requirement.REQ_UDS-0134: Confirm whether this statement is a binding requirement.REQ_UDS-0135: Confirm whether this statement is a binding requirement.REQ_UDS-0136: Confirm whether this statement is a binding requirement.REQ-AUTO-00704: Confirm whether this statement is a binding requirement.REQ_UDS-0163: Confirm whether this statement is a binding requirement.REQ_UDS-0167: Confirm whether this statement is a binding requirement.REQ_UDS-0169: Confirm whether this statement is a binding requirement.REQ_UDS-0208: Confirm whether this statement is a binding requirement.REQ_UDS-0209: Confirm whether this statement is a binding requirement.REQ_UDS-0215: Confirm whether this statement is a binding requirement.REQ_UDS-0217: Confirm whether this statement is a binding requirement.REQ_UDS-0218: Confirm whether this statement is a binding requirement.REQ_UDS-0220: Confirm whether this statement is a binding requirement.REQ_UDS-0221: Confirm whether this statement is a binding requirement.REQ_UDS-0222: Confirm whether this statement is a binding requirement.REQ_UDS-0339: Confirm whether this statement is a binding requirement.REQ_UDS-0003: Confirm whether this statement is a binding requirement.REQ-AUTO-00785: Confirm whether this statement is a binding requirement.REQ-AUTO-00843: Confirm whether this statement is a binding requirement.REQ-AUTO-00859: Confirm whether this statement is a binding requirement.REQ-AUTO-00866: Review possible noise/boilerplate contamination.REQ-AUTO-00880: Confirm whether this statement is a binding requirement.REQ-AUTO-00932: Confirm whether this statement is a binding requirement.REQ-AUTO-00947: Confirm whether this statement is a binding requirement.REQ-AUTO-00988: Confirm whether this statement is a binding requirement.REQ-AUTO-00996: Confirm whether this statement is a binding requirement.REQ-AUTO-01013: Confirm whether this statement is a binding requirement.REQ-AUTO-01056: Confirm whether this statement is a binding requirement.