Open Decisions
Product and cybersecurity architecture understanding package generated from Markdown-derived requirements.
Open Decisions
Classification: Needs Customer Clarification
These decisions block customer-ready architecture approval because the extracted requirements do not confirm enough implementation detail.
Customer Clarification Points
- Confirm exact ECU item definition, product designation, variants, and vehicle-function allocation.
- Confirm in-scope interfaces: diagnostic, vehicle network, backend/update, PKI, tooling, and security operations.
- Confirm assets, trust boundaries, TARA scope, risk treatment, and residual-risk approval workflow.
- Confirm mechanism details for authentication, certificates, key storage, secure update, secure boot, logging, and monitoring.
Requirement-Level Human Review Items
REQ-AUTO-00006(Medium): Review possible noise/boilerplate contamination.REQ_SEC_0040(Low): Confirm whether this statement is a binding requirement.REQ_SEC_0041(Low): Confirm whether this statement is a binding requirement.req-6.3(Low): Confirm whether this statement is a binding requirement.REQ-AUTO-00146(Medium): Review possible noise/boilerplate contamination.Req.ID-Description-6.22.1(Low): Confirm whether this statement is a binding requirement.REQ-AUTO-00171(Low): Confirm whether this statement is a binding requirement.REQ-AUTO-00175(Low): Confirm whether this statement is a binding requirement.REQ-AUTO-00190(Low): Confirm whether this statement is a binding requirement. | Clarify ambiguous or incomplete source wording.REQ-AUTO-00246(Low): Confirm whether this statement is a binding requirement.REQ-AUTO-00249(Low): Confirm whether this statement is a binding requirement.REQ-AUTO-00250(Low): Confirm whether this statement is a binding requirement.REQ-AUTO-00272(Low): Confirm whether this statement is a binding requirement.REQ-AUTO-00278(Low): Confirm whether this statement is a binding requirement.REQ-AUTO-00279(Low): Confirm whether this statement is a binding requirement.REQ-AUTO-00284(Low): Confirm whether this statement is a binding requirement.REQ-AUTO-00292(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0051(Low): Confirm whether this statement is a binding requirement.REQ-AUTO-00294(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0051(Low): Confirm whether this statement is a binding requirement.REQ-AUTO-00298(Low): Confirm whether this statement is a binding requirement.REQ-AUTO-00317(Medium): Clarify ambiguous or incomplete source wording.REQ-AUTO-00335(Low): Confirm whether this statement is a binding requirement.REQ-AUTO-00337(Low): Confirm whether this statement is a binding requirement.REQ-AUTO-00338(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0051(Low): Confirm whether this statement is a binding requirement.REQ-AUTO-00343(Low): Confirm whether this statement is a binding requirement.REQ-AUTO-00378(Low): Confirm whether this statement is a binding requirement.REQ-AUTO-00420(Low): Confirm whether this statement is a binding requirement.REQ-AUTO-00480(Low): Confirm whether this statement is a binding requirement.REQ-AUTO-00485(Low): Confirm whether this statement is a binding requirement.REQ-AUTO-00488(Medium): Review possible noise/boilerplate contamination.REQ-AUTO-00492(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0003(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0004(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0006(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0007(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0008(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0010(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0014(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0015(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0016(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0017(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0020(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0339(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0340(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0341(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0023(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0025(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0030(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0032(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0033(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0036(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0037(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0038(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0041(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0045(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0049(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0051(High): Clarify ambiguous or incomplete source wording.REQ_UDS-0305(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0306(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0316(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0328(Low): Confirm whether this statement is a binding requirement.REQ-AUTO-00563(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0073(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0074(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0078(Low): Confirm whether this statement is a binding requirement.REQ-AUTO-00588(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0345(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0346(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0347(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0348(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0349(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0093(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0259(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0094(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0095(Low): Confirm whether this statement is a binding requirement.REQ-AUTO-00629(Low): Confirm whether this statement is a binding requirement.REQ-AUTO-00634(Medium): Clarify ambiguous or incomplete source wording.REQ_UDS-0103(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0104(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0105(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0107(Low): Confirm whether this statement is a binding requirement.REQ-AUTO-00652(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0113(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0114(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0116(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0117(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0118(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0120(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0295(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0123(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0134(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0135(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0136(Low): Confirm whether this statement is a binding requirement.REQ-AUTO-00704(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0163(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0167(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0169(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0208(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0209(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0215(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0217(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0218(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0220(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0221(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0222(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0339(Low): Confirm whether this statement is a binding requirement.REQ_UDS-0003(Low): Confirm whether this statement is a binding requirement.REQ-AUTO-00785(Low): Confirm whether this statement is a binding requirement.REQ-AUTO-00843(Low): Confirm whether this statement is a binding requirement.REQ-AUTO-00859(Low): Confirm whether this statement is a binding requirement.REQ-AUTO-00866(Medium): Review possible noise/boilerplate contamination.REQ-AUTO-00880(Low): Confirm whether this statement is a binding requirement.REQ-AUTO-00932(Low): Confirm whether this statement is a binding requirement.REQ-AUTO-00947(Low): Confirm whether this statement is a binding requirement.REQ-AUTO-00988(Low): Confirm whether this statement is a binding requirement.REQ-AUTO-00996(Low): Confirm whether this statement is a binding requirement.REQ-AUTO-01013(Low): Confirm whether this statement is a binding requirement.REQ-AUTO-01056(Low): Confirm whether this statement is a binding requirement.
Architecture Open Decisions
- Needs Customer Clarification: Confirm exact ECU item definition, product designation, and variants.
- Needs Customer Clarification: Confirm vehicle network topology, SecOC/SDT applicability, signals, and protection profiles.
- Needs Customer Clarification: Confirm diagnostic service list, UDS Authentication 0x29 role model, certificate use, lockout, and audit expectations.
- Needs Customer Clarification: Confirm secure update/flash/IVD mechanism, signing chain, backend ownership, and rollback behavior.
- Needs Customer Clarification: Confirm key hierarchy, HSM/protected storage capability, PKI ownership, revocation, renewal, and provisioning process.
- Needs Customer Clarification: Confirm security monitoring, incident response handoff, and vulnerability reporting channels.
- Needs Customer Clarification: Confirm final TARA results and customer residual-risk acceptance workflow.
Security Open Decisions
- Needs Customer Clarification: Confirm ownership and control allocation for Electric Clutch Actuator ECU boundary.
- Needs Customer Clarification: Confirm ownership and control allocation for Vehicle/network boundary.
- Needs Customer Clarification: Confirm ownership and control allocation for Diagnostic access boundary.
- Needs Customer Clarification: Confirm ownership and control allocation for Backend/cloud boundary.
- Needs Customer Clarification: Confirm ownership and control allocation for Development/tooling boundary.
- Needs Customer Clarification: Confirm ownership and control allocation for Customer/OEM approval boundary.
- Needs Customer Clarification: Confirm ownership and control allocation for Unknown assumed deployment boundary.
- Inferred from Requirements: Confirm concrete mechanism and verification evidence for Cryptographic Protection.
- Inferred from Requirements: Confirm concrete mechanism and verification evidence for Secure Communication.
- Inferred from Requirements: Confirm concrete mechanism and verification evidence for Secure Boot and Platform Integrity.
- Inferred from Requirements: Confirm concrete mechanism and verification evidence for Secure Software Update.
- Inferred from Requirements: Confirm concrete mechanism and verification evidence for Security Monitoring and Detection.
- Inferred from Requirements: Confirm concrete mechanism and verification evidence for Development and Toolchain Security.
- Inferred from Requirements: Confirm concrete mechanism and verification evidence for Backend/Cloud Security.
Interface Open Questions
- Inferred from Requirements: Vehicle network secure data communication interface needs customer confirmation for exact topology, ownership, and mechanism details.
- Inferred from Requirements: Secure update, flash, and IVD interface needs customer confirmation for exact topology, ownership, and mechanism details.
- Inferred from Requirements: Backend/cloud/IT operational interface needs customer confirmation for exact topology, ownership, and mechanism details.
- Inferred from Requirements: Application software to security services interface needs customer confirmation for exact topology, ownership, and mechanism details.
- Inferred from Requirements: Hardware platform and key storage interface needs customer confirmation for exact topology, ownership, and mechanism details.
Product Unknowns and Assumptions
Unknowns and Assumptions
- Needs Customer Clarification: Exact product name, ECU variant, and vehicle function allocation.
- Needs Customer Clarification: Exact vehicle network topology, messages, signals, and data classification.
- Needs Customer Clarification: Exact diagnostic role model, UDS service scope, certificates, and lockout/rate-limit behavior.
- Needs Customer Clarification: Exact update mechanism, signing chain, IVD ownership, rollback policy, and backend responsibilities.
- Needs Customer Clarification: Exact key hierarchy, HSM/protected-storage capability, certificate lifecycle, and PKI ownership.
- Needs Customer Clarification: Final TARA results, risk treatment decisions, and customer residual-risk acceptance.
- Expert Assumption: Until clarified, diagrams mark these elements as inferred or assumption-based rather than confirmed implementation.