Security Capability: Identity and Access Control
Purpose
Ensure only authorized tools, systems, users, and software actors can perform security-relevant actions.
Threat / Risk Addressed
Unauthorized actor gains privileged access.
Requirement Basis
Protected Assets
- Vehicle function data
- ECU software and firmware
- Cryptographic keys and certificates
- Diagnostic access state
- Cybersecurity concept and evidence
- Backend/update and security operations data
- Hardware platform integrity
Interfaces Protected
- OEM/customer cybersecurity approval and evidence interface
- Secure update, flash, and IVD interface
- Certificate and key provisioning interface
- Development, ALM, and evidence tooling interface
- Security operations and vulnerability reporting interface
- Hardware platform and key storage interface
Architecture Elements Involved
- Security Services
- Diagnostic Server
- Backend/PKI
Expected Mechanisms
- Authentication
- Authorization
- Secure sessions
- Role or certificate validation
Explicit vs Inferred Status
Explicit Requirement
Confidence Level
Medium
Open Decisions
- Confirm concrete mechanisms, ownership, parameters, and verification evidence.
Evidence Basis:
- Requirement IDs: REQ_SEC_0008; REQ_SEC_0015; REQ-AUTO-00175; REQ-AUTO-00290; REQ-AUTO-00333; REQ-AUTO-00334; REQ-AUTO-00376; REQ-AUTO-00496; REQ_UDS-0030; REQ_UDS-0045 (showing 10 of 149)
- Source Markdown sections/pages: 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 9; converted/markdown-cleaned/3299216_1.md page 27; converted/markdown-cleaned/CVS123-2.md page 6; converted/markdown-cleaned/CVS123-2.md page 12; converted/markdown-cleaned/CVS123-2.md page 23; converted/markdown-cleaned/CVS124.md page 7; converted/markdown-cleaned/CVS124.md page 20 (showing 8 of 54)
- Confidence level: Medium
- Classification: Explicit Requirement
Security Capability: Cryptographic Protection
Purpose
Provide authenticity, integrity, confidentiality, and non-repudiation where required.
Threat / Risk Addressed
Data, software, or credentials are modified, disclosed, or forged.
Requirement Basis
Protected Assets
- Vehicle function data
- ECU software and firmware
- Cryptographic keys and certificates
- Diagnostic access state
- Cybersecurity concept and evidence
- Backend/update and security operations data
- Hardware platform integrity
Interfaces Protected
- See interface catalog; exact allocation needs confirmation.
Architecture Elements Involved
- Security Services
- Hardware Platform / HSM
- Application Software
Expected Mechanisms
- Encryption
- Signatures/MACs
- Integrity checks
- Key isolation
Explicit vs Inferred Status
Inferred from Requirements
Confidence Level
Medium
Open Decisions
- Confirm concrete mechanisms, ownership, parameters, and verification evidence.
Evidence Basis:
- Requirement IDs: REQ_SEC_0008; REQ_SEC_0020; REQ_SEC_0016; REQ_SEC_0019; REQ-AUTO-00089; REQ-AUTO-00321; REQ-AUTO-00323; REQ-AUTO-00324; REQ-AUTO-00339; REQ-AUTO-00340 (showing 10 of 117)
- Source Markdown sections/pages: 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 9; converted/markdown-cleaned/3299216_1.md page 10; converted/markdown-cleaned/CVS123-2.md page 11; converted/markdown-cleaned/CVS123-2.md page 16; converted/markdown-cleaned/CVS123-2.md page 19; converted/markdown-cleaned/CVS123-2.md page 25; converted/markdown-cleaned/CVS123-2.md page 26 (showing 8 of 56)
- Confidence level: Medium
- Classification: Inferred from Requirements
Security Capability: Secure Communication
Purpose
Protect vehicle, diagnostic, backend, and service data exchanges against tampering, spoofing, and replay.
Threat / Risk Addressed
Attacker injects, replays, modifies, or observes security-relevant traffic.
Requirement Basis
Protected Assets
- Vehicle function data
- ECU software and firmware
- Cryptographic keys and certificates
- Diagnostic access state
- Cybersecurity concept and evidence
- Backend/update and security operations data
- Hardware platform integrity
Interfaces Protected
- Vehicle network secure data communication interface
- Secure update, flash, and IVD interface
Architecture Elements Involved
- External Interfaces
- Application Software
- Security Services
Expected Mechanisms
- SecOC/SDT-style protection
- Freshness counters
- Replay protection
- Fail-closed discard rules
Explicit vs Inferred Status
Inferred from Requirements
Confidence Level
Medium
Open Decisions
- Confirm concrete mechanisms, ownership, parameters, and verification evidence.
Evidence Basis:
- Requirement IDs: REQ_SEC_0011; REQ_SEC_0012; REQ_SEC_0013; REQ-AUTO-00066; REQ-AUTO-00099; REQ-AUTO-00139; REQ-AUTO-00141; req-6.3; REQ-AUTO-00146; REQ-AUTO-00193 (showing 10 of 128)
- Source Markdown sections/pages: converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 8; converted/markdown-cleaned/3299216_1.md page 4; converted/markdown-cleaned/3299216_1.md page 11; converted/markdown-cleaned/3299216_1.md page 22; converted/markdown-cleaned/3299216_1.md page 23; converted/markdown-cleaned/3299216_1.md page 31; converted/markdown-cleaned/3299216_1.md page 33; converted/markdown-cleaned/3299216_1.md page 40 (showing 8 of 50)
- Confidence level: Medium
- Classification: Inferred from Requirements
Purpose
Ensure only valid and authorized software executes on an ECU with an integrity-preserving platform.
Threat / Risk Addressed
Unauthorized software or tampered platform state is trusted.
Requirement Basis
Protected Assets
- ECU software and firmware
- Diagnostic access state
- Backend/update and security operations data
- Hardware platform integrity
Interfaces Protected
- Vehicle network secure data communication interface
- Secure update, flash, and IVD interface
Architecture Elements Involved
- Hardware Platform
- Boot/Update Manager
- Security Services
Expected Mechanisms
- Secure boot
- Platform integrity checks
- Debug restrictions
- Authentic software checks
Explicit vs Inferred Status
Inferred from Requirements
Confidence Level
Medium
Open Decisions
- Confirm concrete mechanisms, ownership, parameters, and verification evidence.
Evidence Basis:
Security Capability: Secure Software Update
Purpose
Ensure update and flash content is authentic, intact, authorized, and traceable.
Threat / Risk Addressed
Malicious or wrong software is installed or update evidence is lost.
Requirement Basis
Protected Assets
- Vehicle function data
- ECU software and firmware
- Diagnostic access state
- Cybersecurity concept and evidence
- Backend/update and security operations data
- Hardware platform integrity
Interfaces Protected
- Vehicle network secure data communication interface
- Secure update, flash, and IVD interface
- Application software to security services interface
Architecture Elements Involved
- Backend and IT Systems
- Boot/Update Manager
- Security Services
Expected Mechanisms
- Signed packages
- IVD checks
- Certificate validation
- Update logging
Explicit vs Inferred Status
Inferred from Requirements
Confidence Level
Medium
Open Decisions
- Confirm concrete mechanisms, ownership, parameters, and verification evidence.
Evidence Basis:
Security Capability: Secure Diagnostics
Purpose
Enable service access while preventing unauthorized diagnostic control.
Threat / Risk Addressed
Diagnostic service becomes a bypass for security controls.
Requirement Basis
Protected Assets
- Vehicle function data
- ECU software and firmware
- Cryptographic keys and certificates
- Diagnostic access state
- Cybersecurity concept and evidence
- Backend/update and security operations data
- Hardware platform integrity
Interfaces Protected
- Vehicle network secure data communication interface
- Secure update, flash, and IVD interface
Architecture Elements Involved
- Diagnostic Interface
- Security Services
- Application Software
Expected Mechanisms
- UDS authentication
- Access control
- Rate limiting
- Diagnostic audit
Explicit vs Inferred Status
Explicit Requirement
Confidence Level
Medium
Open Decisions
- Confirm concrete mechanisms, ownership, parameters, and verification evidence.
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-00298; REQ-AUTO-00299 (showing 10 of 341)
- 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 119)
- Confidence level: Medium
- Classification: Explicit Requirement
Security Capability: Key and Certificate Management
Purpose
Maintain trustworthy cryptographic identities and secrets across lifecycle.
Threat / Risk Addressed
Compromised trust material invalidates multiple controls.
Requirement Basis
Protected Assets
- Vehicle function data
- ECU software and firmware
- Cryptographic keys and certificates
- Diagnostic access state
- Cybersecurity concept and evidence
- Backend/update and security operations data
Interfaces Protected
- OEM/customer cybersecurity approval and evidence interface
- Secure update, flash, and IVD interface
- Certificate and key provisioning interface
- Development, ALM, and evidence tooling interface
- Security operations and vulnerability reporting interface
- Hardware platform and key storage interface
Architecture Elements Involved
- Security Services
- PKI/Provisioning
- Hardware Platform
Expected Mechanisms
- PKI lifecycle
- Trust-anchor management
- Secure provisioning
- Protected key storage
Explicit vs Inferred Status
Explicit Requirement
Confidence Level
Medium
Open Decisions
- Confirm concrete mechanisms, ownership, parameters, and verification evidence.
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
Security Capability: Logging and Audit
Purpose
Record security-relevant activity for accountability, evidence, and investigation.
Threat / Risk Addressed
Security events cannot be investigated or evidenced.
Requirement Basis
Protected Assets
- Vehicle function data
- ECU software and firmware
- Cryptographic keys and certificates
- Diagnostic access state
- Cybersecurity concept and evidence
- Backend/update and security operations data
- Hardware platform integrity
Interfaces Protected
- OEM/customer cybersecurity approval and evidence interface
- Secure update, flash, and IVD interface
- Certificate and key provisioning interface
- Development, ALM, and evidence tooling interface
- Security operations and vulnerability reporting interface
- Hardware platform and key storage interface
Architecture Elements Involved
- Security Services
- Backend/SecOps
- Evidence Repository
Expected Mechanisms
- Security event logging
- Evidence retention
- Audit trail
- Traceability IDs
Explicit vs Inferred Status
Explicit Requirement
Confidence Level
Medium
Open Decisions
- Confirm concrete mechanisms, ownership, parameters, and verification evidence.
Evidence Basis:
- Requirement IDs: REQ-AUTO-00001; REQ_SEC_0004; REQ_SEC_0005; REQ_SEC_0041; REQ_SEC_0051; REQ-AUTO-00172; REQ-AUTO-00176; REQ-AUTO-00218; REQ-AUTO-00253; REQ-AUTO-00256 (showing 10 of 50)
- 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 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 12; converted/markdown-cleaned/3299216_1.md page 27; converted/markdown-cleaned/3299216_1.md page 36; converted/markdown-cleaned/3299216_1.md page 49; converted/markdown-cleaned/3299216_1.md page 50 (showing 8 of 36)
- Confidence level: Medium
- Classification: Explicit Requirement
Security Capability: Security Monitoring and Detection
Purpose
Identify security-relevant anomalies or events that need response.
Threat / Risk Addressed
Attacks or control failures remain invisible.
Requirement Basis
Protected Assets
- ECU software and firmware
- Diagnostic access state
- Backend/update and security operations data
- Hardware platform integrity
Interfaces Protected
- OEM/customer cybersecurity approval and evidence interface
- Security operations and vulnerability reporting interface
- Application software to security services interface
Architecture Elements Involved
- Security Services
- Backend/SecOps
- Logging Path
Expected Mechanisms
- Security event collection
- Alert triage
- Detection rules
- Escalation path
Explicit vs Inferred Status
Inferred from Requirements
Confidence Level
Medium
Open Decisions
- Confirm concrete mechanisms, ownership, parameters, and verification evidence.
Evidence Basis:
- Requirement IDs: REQ_SEC_0036; REQ_SEC_0037; REQ_SEC_0051; REQ-AUTO-00177; REQ-AUTO-00180; REQ-AUTO-00183; REQ-AUTO-00194; REQ-AUTO-00220; REQ-AUTO-00298; REQ-AUTO-00345 (showing 10 of 17)
- Source Markdown sections/pages: 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 28; converted/markdown-cleaned/3299216_1.md page 31; converted/markdown-cleaned/3299216_1.md page 36; converted/markdown-cleaned/CVS123-2.md page 7; converted/markdown-cleaned/CVS123-2.md page 20 (showing 8 of 14)
- Confidence level: Medium
- Classification: Inferred from Requirements
Security Capability: Vulnerability and Incident Handling
Purpose
Assess, treat, communicate, and track vulnerabilities and incidents over releases.
Threat / Risk Addressed
Known vulnerabilities or incidents remain untreated.
Requirement Basis
Protected Assets
- ECU software and firmware
- Backend/update and security operations data
- Hardware platform integrity
Interfaces Protected
- OEM/customer cybersecurity approval and evidence interface
- Secure update, flash, and IVD interface
- Certificate and key provisioning interface
- Development, ALM, and evidence tooling interface
- Security operations and vulnerability reporting interface
- Hardware platform and key storage interface
Architecture Elements Involved
- Compliance Process
- Security Operations
- Engineering Toolchain
Expected Mechanisms
- Vulnerability intake
- Risk treatment
- Incident workflow
- Mitigation verification
Explicit vs Inferred Status
Explicit Requirement
Confidence Level
High
Open Decisions
- Confirm concrete mechanisms, ownership, parameters, and verification evidence.
Evidence Basis:
Purpose
Protect the engineering environment and evidence chain that produce security-relevant artifacts.
Threat / Risk Addressed
Compromised tooling produces compromised products or false evidence.
Requirement Basis
Protected Assets
- ECU software and firmware
- Cryptographic keys and certificates
- Diagnostic access state
- Cybersecurity concept and evidence
- Backend/update and security operations data
Interfaces Protected
- OEM/customer cybersecurity approval and evidence interface
- Secure update, flash, and IVD interface
- Certificate and key provisioning interface
- Development, ALM, and evidence tooling interface
- Security operations and vulnerability reporting interface
- Hardware platform and key storage interface
Architecture Elements Involved
- Engineering Toolchain
- ALM/CI
- Evidence Repository
Expected Mechanisms
- Access control
- Artifact integrity
- Review workflow
- Build/test evidence
Explicit vs Inferred Status
Inferred from Requirements
Confidence Level
Medium
Open Decisions
- Confirm concrete mechanisms, ownership, parameters, and verification evidence.
Evidence Basis:
- Requirement IDs: REQ_SEC_0041; REQ_SEC_0014; REQ_SEC_0044; REQ_SEC_0045; REQ_SEC_0046; REQ_SEC_0032; REQ_SEC_0037; REQ-AUTO-00092; REQ-AUTO-00093; REQ-AUTO-00094 (showing 10 of 80)
- Source Markdown sections/pages: 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 10; converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 11; converted/markdown-cleaned/3299216_1.md page 10; converted/markdown-cleaned/3299216_1.md page 11; converted/markdown-cleaned/3299216_1.md page 16; converted/markdown-cleaned/3299216_1.md page 25 (showing 8 of 49)
- Confidence level: Medium
- Classification: Inferred from Requirements
Security Capability: Backend/Cloud Security
Purpose
Protect offboard systems that influence update, evidence, monitoring, and operational security.
Threat / Risk Addressed
Offboard compromise affects products, updates, evidence, or operational data.
Requirement Basis
Protected Assets
- Vehicle function data
- ECU software and firmware
- Cryptographic keys and certificates
- Diagnostic access state
- Cybersecurity concept and evidence
- Backend/update and security operations data
- Hardware platform integrity
Interfaces Protected
- Backend/cloud/IT operational interface
Architecture Elements Involved
- Backend and IT Systems
- External Interfaces
- Security Operations
Expected Mechanisms
- Mutual authentication
- Network segregation
- API authorization
- Backend audit logging
Explicit vs Inferred Status
Inferred from Requirements
Confidence Level
Medium
Open Decisions
- Confirm concrete mechanisms, ownership, parameters, and verification evidence.
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
Security Capability: Compliance and Evidence Management
Purpose
Demonstrate that requirements, controls, verification, validation, and residual risk remain traceable.
Threat / Risk Addressed
Customer cannot verify that security obligations are met.
Requirement Basis
Protected Assets
- Vehicle function data
- ECU software and firmware
- Cryptographic keys and certificates
- Diagnostic access state
- Cybersecurity concept and evidence
- Backend/update and security operations data
- Hardware platform integrity
Interfaces Protected
- OEM/customer cybersecurity approval and evidence interface
- Secure update, flash, and IVD interface
- Certificate and key provisioning interface
- Development, ALM, and evidence tooling interface
- Security operations and vulnerability reporting interface
- Hardware platform and key storage interface
Architecture Elements Involved
- Compliance Process
- Engineering Toolchain
- OEM/Customer Interface
Expected Mechanisms
- Requirement traceability
- Control mapping
- V&V reports
- Residual-risk approval records
Explicit vs Inferred Status
Explicit Requirement
Confidence Level
High
Open Decisions
- Confirm concrete mechanisms, ownership, parameters, and verification evidence.
Evidence Basis:
- Requirement IDs: REQ-AUTO-00001; REQ_SEC_0001; REQ-AUTO-00005; REQ_SEC_0003; REQ_SEC_0024; REQ_SEC_0004; REQ_SEC_0007; REQ_SEC_0041; REQ_SEC_0009; REQ_SEC_0044 (showing 10 of 113)
- 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 10; converted/markdown-cleaned/3299216_1.md page 5; converted/markdown-cleaned/3299216_1.md page 10; converted/markdown-cleaned/3299216_1.md page 11 (showing 8 of 68)
- Confidence level: High
- Classification: Explicit Requirement
Additional PDF Security Evidence
- Vulnerability and Incident Handling: Resolved; direct evidence IDs: REQ_SEC_0002, REQ_SEC_0030, REQ_SEC_0044, REQ_SEC_0045, REQ_SEC_0046, REQ_SEC_0032, REQ_SEC_0033, REQ_SEC_0034.
- Secure communication: Improved; direct evidence IDs: REQ_SEC_0008, REQ_SEC_0011, REQ_SEC_0012, REQ_SEC_0013, REQ_SEC_0014, REQ_SEC_0026, REQ_SEC_0027, REQ_SEC_0016.
- Inferred items remain labelled as inferred; no requirement basis was invented.