Trust Boundaries

Product and cybersecurity architecture understanding package generated from Markdown-derived requirements.

Trust Boundary Diagram

flowchart TB subgraph Product["Inside product boundary"] ECU["ECU software and hardware"] Sec["Security services"] end subgraph Vehicle["Vehicle / network boundary"] Net["Other ECUs and vehicle buses"] end subgraph Backend["Backend / cloud boundary"] Cloud["Update, PKI, logs, portals"] end subgraph Diagnostic["Diagnostic access boundary"] Tool["Service and engineering tools"] end subgraph Tooling["Development / tooling boundary"] ALM["ALM, CI, test, evidence"] end subgraph Customer["Customer / OEM boundary"] OEM["Approval and residual risk"] end Unknown["Unknown deployment zones"] Tool -->|trusted diagnostic session unknown details| ECU Net -->|vehicle data| ECU Cloud -->|update, certificates, events| Sec ALM -->|evidence and artifacts| OEM ECU -->|security evidence| OEM Unknown -. clarification needed .-> ECU
Mermaid source 
flowchart TB
  subgraph Product["Inside product boundary"]
    ECU["ECU software and hardware"]
    Sec["Security services"]
  end
  subgraph Vehicle["Vehicle / network boundary"]
    Net["Other ECUs and vehicle buses"]
  end
  subgraph Backend["Backend / cloud boundary"]
    Cloud["Update, PKI, logs, portals"]
  end
  subgraph Diagnostic["Diagnostic access boundary"]
    Tool["Service and engineering tools"]
  end
  subgraph Tooling["Development / tooling boundary"]
    ALM["ALM, CI, test, evidence"]
  end
  subgraph Customer["Customer / OEM boundary"]
    OEM["Approval and residual risk"]
  end
  Unknown["Unknown deployment zones"]
  Tool -->|trusted diagnostic session unknown details| ECU
  Net -->|vehicle data| ECU
  Cloud -->|update, certificates, events| Sec
  ALM -->|evidence and artifacts| OEM
  ECU -->|security evidence| OEM
  Unknown -. clarification needed .-> ECU

Architecture Trust Boundaries

Trust Boundaries

Classification: Inferred from Requirements

The trust-boundary view separates the Electric Clutch Actuator ECU, vehicle network, diagnostic, backend/cloud, tooling, customer/OEM, and unknown deployment zones.

Evidence Basis:

Security Trust Boundary Model

Trust Boundary Model

Trust Boundary: Electric Clutch Actuator ECU boundary

Classification: Inferred from Requirements

Separates the in-scope clutch-actuator ECU hardware and software from vehicle, service, backend, customer, and supplier environments.

Evidence Basis:

Trust Boundary: Vehicle/network boundary

Classification: Inferred from Requirements

Separates the ECU/application from other ECUs and vehicle networks carrying SecOC/SDT or function data.

Evidence Basis:

Trust Boundary: Diagnostic access boundary

Classification: Explicit Requirement

Separates service tools and engineering testers from privileged ECU diagnostic functions.

Evidence Basis:

Trust Boundary: Backend/cloud boundary

Classification: Inferred from Requirements

Separates offboard update, IT, evidence, monitoring, and supplier/OEM systems from product runtime.

Evidence Basis:

Trust Boundary: Development/tooling boundary

Classification: Explicit Requirement

Separates engineering tooling and evidence repositories from product artifacts and customer-facing evidence.

Evidence Basis:

Trust Boundary: Customer/OEM approval boundary

Classification: Explicit Requirement

Separates supplier-owned security engineering work products from OEM/customer approval and residual-risk acceptance.

Evidence Basis:

Trust Boundary: Unknown assumed deployment boundary

Classification: Needs Customer Clarification

Marks deployment zones, ownership, and connectivity that cannot be confirmed from the extracted requirements alone.

Evidence Basis: