Interface Catalog
Interface: OEM/customer cybersecurity approval and evidence interface
Interface Type
Customer
Connected Elements
Supplier security engineering -> vehicle manufacturer/OEM/customer
Purpose
Exchange cybersecurity concept, method, results, residual-risk position, verification evidence, and approval decisions.
Data Exchanged
Requirements, risk assessment method/results, cybersecurity concept, control traceability, V&V evidence, residual-risk records.
Security Relevance
This interface governs acceptance of risk and evidence integrity; poor control here weakens the whole security case.
Required Protection
Access control, evidence integrity, versioning, audit trail, customer approval workflow, confidentiality for security-sensitive reports.
Requirement Basis
Trust Boundary Crossing
Yes
Confidence Level
Medium
Open Questions
- Confirm implementation-specific parameters and ownership.
Evidence Basis:
- Requirement IDs: REQ-AUTO-00001; REQ_SEC_0001; REQ_SEC_0002; REQ-AUTO-00004; REQ-AUTO-00005; REQ-AUTO-00006; REQ_SEC_0003; REQ_SEC_0024; REQ_SEC_0004; REQ_SEC_0005 (showing 10 of 157)
- Source Markdown sections/pages: converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 3; converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 5; converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 6; converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 7; converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 8; converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 9; converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 10; converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 11 (showing 8 of 74)
- Confidence level: Medium
- Classification: Explicit Requirement
Interface Type
Diagnostic
Connected Elements
Diagnostic/service tool -> ECU diagnostic server/security services
Purpose
Provide service, maintenance, programming, and authenticated diagnostic access.
Data Exchanged
UDS requests/responses, authentication data, certificates, session state, diagnostic security decisions, negative responses.
Security Relevance
Diagnostics can unlock privileged functions and therefore is a critical attack surface.
Required Protection
Authentication, authorization, secure session, certificate validation, rate limiting, replay protection, logging.
Requirement Basis
Trust Boundary Crossing
Yes
Confidence Level
Medium
Open Questions
- Confirm implementation-specific parameters and ownership.
Evidence Basis:
- Requirement IDs: REQ_SEC_0010; REQ_SEC_0011; req-6.20; REQ-AUTO-00282; REQ-AUTO-00284; REQ-AUTO-00290; REQ_UDS-0051; REQ_UDS-0051; REQ-AUTO-00297; REQ-AUTO-00298 (showing 10 of 385)
- Source Markdown sections/pages: converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 8; converted/markdown-cleaned/3299216_1.md page 23; converted/markdown-cleaned/CVS123-2.md page 4; converted/markdown-cleaned/CVS123-2.md page 6; converted/markdown-cleaned/CVS123-2.md page 7; converted/markdown-cleaned/CVS123-2.md page 9; converted/markdown-cleaned/CVS123-2.md page 10; converted/markdown-cleaned/CVS123-2.md page 11 (showing 8 of 133)
- Confidence level: Medium
- Classification: Explicit Requirement
Interface: Vehicle network secure data communication interface
Interface Type
Vehicle Network
Connected Elements
Other ECUs / vehicle network <-> product ECU/application
Purpose
Exchange vehicle-function data, protected messages, counters, and stateful request/response traffic.
Data Exchanged
Signals, messages, SDT requests/responses, SecOC-protected data, freshness counters, authentication tags.
Security Relevance
Vehicle data authenticity, freshness, and optional confidentiality are central to safe function realization.
Required Protection
Message authentication, integrity, freshness, anti-replay, optional encryption, discard rules for malformed or unauthenticated data.
Requirement Basis
Trust Boundary Crossing
Yes
Confidence Level
Medium
Open Questions
- Confirm exact protocol, owner, endpoint, trust anchors, and operational responsibility.
Evidence Basis:
- Requirement IDs: REQ-AUTO-00066; REQ-AUTO-00141; req-6.3; REQ-AUTO-00146; REQ-AUTO-00173; REQ-AUTO-00193; REQ-AUTO-00196; REQ-AUTO-00199; REQ-AUTO-00310; REQ-AUTO-00334 (showing 10 of 127)
- Source Markdown sections/pages: converted/markdown-cleaned/3299216_1.md page 4; converted/markdown-cleaned/3299216_1.md page 22; converted/markdown-cleaned/3299216_1.md page 23; converted/markdown-cleaned/3299216_1.md page 27; converted/markdown-cleaned/3299216_1.md page 31; converted/markdown-cleaned/3299216_1.md page 33; converted/markdown-cleaned/CVS123-2.md page 9; converted/markdown-cleaned/CVS123-2.md page 12 (showing 8 of 49)
- Confidence level: Medium
- Classification: Inferred from Requirements
Interface: Secure update, flash, and IVD interface
Interface Type
Backend
Connected Elements
Update/flash backend or programming tool -> ECU update/boot/security services
Purpose
Deliver and verify software updates, flash programming content, and integrity validation data.
Data Exchanged
Software packages, signatures, IVD data, certificates, programming requests, update result logs.
Security Relevance
Update compromise can replace valid ECU behavior with attacker-controlled software.
Required Protection
Package authenticity, integrity validation, secure boot linkage, certificate validation, rollback policy, logging.
Requirement Basis
Trust Boundary Crossing
Yes
Confidence Level
Medium
Open Questions
- Confirm exact protocol, owner, endpoint, trust anchors, and operational responsibility.
Evidence Basis:
Interface: Certificate and key provisioning interface
Interface Type
Backend
Connected Elements
PKI/provisioning authority -> ECU security services / HSM
Purpose
Provision, validate, and manage certificates, trust anchors, and cryptographic key material.
Data Exchanged
Keys, certificates, trust anchors, certificate chains, key identifiers, validity metadata.
Security Relevance
Trust anchors and keys are high-value assets; compromise undermines authentication and secure communication.
Required Protection
Key protection, certificate validation, secure provisioning, authorization, audit, lifecycle controls.
Requirement Basis
Trust Boundary Crossing
Yes
Confidence Level
Medium
Open Questions
- Confirm implementation-specific parameters and ownership.
Evidence Basis:
- Requirement IDs: REQ_SEC_0016; REQ_SEC_0019; REQ-AUTO-00335; REQ-AUTO-00340; REQ-AUTO-00445; REQ_UDS-0038; REQ_UDS-0068; REQ_UDS-0070; REQ_UDS-0071; REQ_UDS-0072 (showing 10 of 69)
- Source Markdown sections/pages: converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 9; converted/markdown-cleaned/CVS123-2.md page 14; converted/markdown-cleaned/CVS123-2.md page 16; converted/markdown-cleaned/CVS123-2.md page 37; converted/markdown-cleaned/CVS124.md page 22; converted/markdown-cleaned/CVS124.md page 34; converted/markdown-cleaned/CVS124.md page 40; converted/markdown-cleaned/CVS151.md page 11 (showing 8 of 29)
- Confidence level: Medium
- Classification: Explicit Requirement
Interface: Backend/cloud/IT operational interface
Interface Type
Cloud
Connected Elements
Backend/cloud/IT systems <-> supplier/OEM/product lifecycle processes
Purpose
Support offboard functions such as update coordination, evidence storage, monitoring, vulnerability handling, or supplier portals.
Data Exchanged
Configuration, release data, software packages, logs, evidence, vulnerability records, security events.
Security Relevance
Backend compromise can affect update integrity, data confidentiality, and operational response.
Required Protection
Mutual authentication, transport encryption, authorization, audit logging, least privilege, vulnerability management.
Requirement Basis
Trust Boundary Crossing
Yes
Confidence Level
Medium
Open Questions
- Confirm exact protocol, owner, endpoint, trust anchors, and operational responsibility.
Evidence Basis:
- Requirement IDs: REQ-AUTO-00001; REQ_SEC_0001; REQ_SEC_0002; REQ_SEC_0003; REQ_SEC_0022; REQ-AUTO-00009; REQ_SEC_0023; REQ-AUTO-00011; REQ_SEC_0024; REQ_SEC_0004 (showing 10 of 748)
- Source Markdown sections/pages: converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 3; converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 5; converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 6; converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 7; converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 8; converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 9; converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 10; converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 11 (showing 8 of 218)
- Confidence level: Medium
- Classification: Inferred from Requirements
Interface Type
Tooling
Connected Elements
Engineering tools / ALM / CI / test systems -> evidence and release artifacts
Purpose
Create, verify, trace, review, and archive security engineering evidence and released artifacts.
Data Exchanged
Requirements, source references, architecture decisions, test reports, traceability matrices, release evidence.
Security Relevance
Toolchain integrity determines whether software and evidence can be trusted.
Required Protection
Role-based access, artifact integrity, audit trail, change control, branch/release governance, credential protection.
Requirement Basis
Trust Boundary Crossing
Yes
Confidence Level
Medium
Open Questions
- Confirm implementation-specific parameters and ownership.
Evidence Basis:
- Requirement IDs: REQ-AUTO-00001; REQ_SEC_0002; REQ-AUTO-00009; REQ_SEC_0023; REQ_SEC_0004; REQ_SEC_0005; REQ_SEC_0041; REQ_SEC_0008; REQ_SEC_0026; REQ_SEC_0027 (showing 10 of 192)
- Source Markdown sections/pages: converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 3; converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 5; converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 6; converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 7; converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 8; converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 9; converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 10; converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 12 (showing 8 of 110)
- Confidence level: Medium
- Classification: Explicit Requirement
Interface: Security operations and vulnerability reporting interface
Interface Type
Operational
Connected Elements
Product/backend/security monitoring -> supplier and OEM security operations
Purpose
Move security events, vulnerabilities, penetration-test findings, and incident information into lifecycle handling.
Data Exchanged
Security events, logs, vulnerabilities, incident records, penetration-test findings, mitigations, risk treatment decisions.
Security Relevance
This is the feedback path for residual risk and field security issues.
Required Protection
Confidentiality, integrity, authenticated reporting, audit, incident workflow, retention controls.
Requirement Basis
Trust Boundary Crossing
Yes
Confidence Level
Medium
Open Questions
- Confirm implementation-specific parameters and ownership.
Evidence Basis:
- Requirement IDs: REQ_SEC_0002; REQ-AUTO-00009; REQ_SEC_0040; REQ_SEC_0041; REQ_SEC_0044; REQ_SEC_0045; REQ_SEC_0046; REQ_SEC_0032; REQ_SEC_0033; REQ_SEC_0034 (showing 10 of 25)
- Source Markdown sections/pages: converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 5; converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 6; converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 7; converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 10; converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 11; converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 12; converted/markdown-cleaned/3299216_1.md page 27; converted/markdown-cleaned/3299216_1.md page 36 (showing 8 of 16)
- Confidence level: Medium
- Classification: Explicit Requirement
Interface: Application software to security services interface
Interface Type
Internal
Connected Elements
Application software -> security services / crypto / diagnostic access control
Purpose
Allow application behavior to request authentication, verification, secure communication, logging, and access-control decisions.
Data Exchanged
Requests, messages, state variables, verification results, authorization decisions, security events.
Security Relevance
This internal boundary determines whether application features consistently use security controls.
Required Protection
API authorization, fail-closed error handling, input validation, logging, secure key isolation.
Requirement Basis
Trust Boundary Crossing
No
Confidence Level
Medium
Open Questions
- Confirm exact protocol, owner, endpoint, trust anchors, and operational responsibility.
Evidence Basis:
- Requirement IDs: REQ-AUTO-00004; REQ-AUTO-00005; REQ-AUTO-00006; REQ_SEC_0003; REQ-AUTO-00011; REQ_SEC_0007; REQ_SEC_0008; REQ-AUTO-00021; REQ_SEC_0009; REQ_SEC_0020 (showing 10 of 909)
- Source Markdown sections/pages: converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 5; converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 6; converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 7; converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 8; converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 9; converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 10; converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 11; converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 12 (showing 8 of 229)
- Confidence level: Medium
- Classification: Inferred from Requirements
Interface Type
Internal
Connected Elements
Security services -> hardware platform / protected storage / HSM where available
Purpose
Bind cryptographic operations, secure boot assumptions, and key storage to the ECU hardware platform.
Data Exchanged
Keys, certificates, boot measurements, software authenticity status, platform security state.
Security Relevance
Hardware-backed protection is expected where keys and platform integrity must survive software compromise.
Required Protection
Key isolation, access control, secure boot, debug restrictions, tamper-aware handling, audit.
Requirement Basis
Trust Boundary Crossing
No
Confidence Level
Medium
Open Questions
- Confirm exact protocol, owner, endpoint, trust anchors, and operational responsibility.
Evidence Basis:
- Requirement IDs: REQ_SEC_0003; REQ_SEC_0040; REQ_SEC_0025; REQ_SEC_0009; REQ_SEC_0010; REQ_SEC_0011; REQ_SEC_0026; REQ_SEC_0016; REQ_SEC_0019; REQ-AUTO-00051 (showing 10 of 139)
- Source Markdown sections/pages: converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 5; converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 6; converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 7; converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 8; converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 9; converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 11; converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 12; converted/markdown-cleaned/3299216_1.md page 4 (showing 8 of 81)
- Confidence level: Medium
- Classification: Inferred from Requirements