Trust Boundaries

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

Last updated: 2026-06-29 11:49
RTRFQX Review TeamWorkspace

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:

  • Related requirements: RFQX-1001379436-P10-000-01-0001; RFQX-1001379436-P10-000-01-0002; RFQX-1001379436-P10-000-01-0003; RFQX-1001379436-P10-000-01-0004; RFQX-1001379436-P10-000-01-0005; RFQX-1001379436-P10-000-01-0006; RFQX-1001379436-P10-000-01-0007; RFQX-1001379436-P10-000-01-0008; RFQX-1001379436-P10-000-01-0009; RFQX-1001379436-P10-000-01-0010 (sample: 10 of 641)
  • Source document: source document page 3; source document page 5; source document page 6; source document page 7; source document page 8; source document page 9; source document page 10; source document page 11(sample: 8 of 163)
  • Confidence level: Low
  • Classification: Inferred from Requirements

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:

  • Related requirements: RFQX-1001379436-P10-000-01-0001; RFQX-1001379436-P10-000-01-0002; RFQX-1001379436-P10-000-01-0003; RFQX-1001379436-P10-000-01-0004; RFQX-1001379436-P10-000-01-0005; RFQX-1001379436-P10-000-01-0006; RFQX-1001379436-P10-000-01-0007; RFQX-1001379436-P10-000-01-0008; RFQX-1001379436-P10-000-01-0011; RFQX-1001379436-P10-000-01-0012 (sample: 10 of 628)
  • Source document: source document page 3; source document page 5; source document page 6; source document page 7; source document page 8; source document page 9; source document page 10; source document page 11(sample: 8 of 186)
  • Confidence level: Low
  • Classification: Inferred from Requirements

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:

  • Related requirements: RFQX-1001379436-P10-000-01-0002; RFQX-1001379436-P10-000-01-0008; RFQX-1001379436-P10-000-01-0009; RFQX-1001379436-P10-000-01-0010; RFQX-1001379436-P10-000-01-0011; RFQX-1001379436-P10-000-01-0017; RFQX-1001379436-P10-000-01-0020; RFQX-1001379436-P10-000-01-0023; RFQX-1001379436-P10-000-01-0024; RFQX-1001379436-P10-000-01-0025 (sample: 10 of 367)
  • Source document: source document page 3; source document page 5; source document page 6; source document page 7; source document page 8; source document page 9; source document page 10; source document page 11(sample: 8 of 103)
  • Confidence level: Low
  • Classification: Inferred from Requirements

Trust Boundary: Diagnostic access boundary

Classification: Explicit Requirement

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

Evidence Basis:

  • Related requirements: RFQX-1001379436-P10-000-01-0029; RFQX-1001379436-P10-000-01-0030; RFQX-3299216-1-0107; RFQX-3299216-1-0126; RFQX-3299216-1-0127; RFQX-CVS123-2-0005; RFQX-CVS123-2-0009; RFQX-CVS123-2-0010; RFQX-CVS123-2-0013; RFQX-CVS123-2-0017 (sample: 10 of 565)
  • Source document: source document page 8; source document page 23; source document page 25; source document page 4; source document page 5; source document page 6; source document page 7; source document page 9(sample: 8 of 137)
  • Confidence level: Low
  • Classification: Explicit Requirement

Trust Boundary: Backend/cloud boundary

Classification: Inferred from Requirements

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

Evidence Basis:

  • Related requirements: RFQX-1001379436-P10-000-01-0001; RFQX-1001379436-P10-000-01-0002; RFQX-1001379436-P10-000-01-0003; RFQX-1001379436-P10-000-01-0004; RFQX-1001379436-P10-000-01-0005; RFQX-1001379436-P10-000-01-0006; RFQX-1001379436-P10-000-01-0007; RFQX-1001379436-P10-000-01-0008; RFQX-1001379436-P10-000-01-0012; RFQX-1001379436-P10-000-01-0013 (sample: 10 of 1095)
  • Source document: source document page 3; source document page 5; source document page 6; source document page 7; source document page 8; source document page 9; source document page 10; source document page 11(sample: 8 of 231)
  • Confidence level: Low
  • Classification: Inferred from Requirements

Trust Boundary: Development/tooling boundary

Classification: Explicit Requirement

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

Evidence Basis:

  • Related requirements: RFQX-1001379436-P10-000-01-0003; RFQX-1001379436-P10-000-01-0005; RFQX-1001379436-P10-000-01-0006; RFQX-1001379436-P10-000-01-0018; RFQX-1001379436-P10-000-01-0019; RFQX-1001379436-P10-000-01-0023; RFQX-1001379436-P10-000-01-0034; RFQX-1001379436-P10-000-01-0059; RFQX-3299216-1-0034; RFQX-3299216-1-0035 (sample: 10 of 68)
  • Source document: source document page 3; source document page 5; source document page 6; source document page 7; source document page 8; source document page 11; source document page 10; source document page 11(sample: 8 of 39)
  • Confidence level: Low
  • Classification: Explicit Requirement

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:

  • Related requirements: RFQX-1001379436-P10-000-01-0001; RFQX-1001379436-P10-000-01-0002; RFQX-1001379436-P10-000-01-0007; RFQX-1001379436-P10-000-01-0008; RFQX-1001379436-P10-000-01-0009; RFQX-1001379436-P10-000-01-0010; RFQX-1001379436-P10-000-01-0011; RFQX-1001379436-P10-000-01-0012; RFQX-1001379436-P10-000-01-0017; RFQX-1001379436-P10-000-01-0018 (sample: 10 of 140)
  • Source document: source document page 3; source document page 5; source document page 6; source document page 7; source document page 8; source document page 9; source document page 10; source document page 11(sample: 8 of 60)
  • Confidence level: Medium
  • Classification: Explicit Requirement

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:

  • Related requirements: RFQX-1001379436-P10-000-01-0004; RFQX-3299216-1-0019; RFQX-3299216-1-0069; RFQX-3299216-1-0098; RFQX-3299216-1-0099; RFQX-3299216-1-0100; RFQX-3299216-1-0128; RFQX-3299216-1-0129; RFQX-3299216-1-0133; RFQX-3299216-1-0141 (sample: 10 of 75)
  • Source document: source document page 3; source document page 7; source document page 16; source document page 23; source document page 25; source document page 26; source document page 27; source document page 29(sample: 8 of 39)
  • Confidence level: Low
  • Classification: Needs Customer Clarification