Trustpoint Architecture¶
Trustpoint is an open-source platform for managing digital machine identities and certificate lifecycles in industrial IT and OT environments. It provides device onboarding, certificate issuance and renewal, policy enforcement, revocation management, and integration with industrial workflows through standardized enrollment protocols and APIs.
Project status: Trustpoint is currently a technology preview (beta). The architecture described here reflects the current implementation in the repository. Features, APIs, and deployment patterns may evolve between releases.
Purpose and Scope¶
Trustpoint addresses the challenge of deploying and managing digital identities for machines, devices, and services in industrial environments where:
Networks are segmented, air-gapped, or intermittently connected
Devices have limited resources and diverse capabilities
Certificate lifecycles span years or decades
Manual certificate handling creates operational risk
Enterprise PKI systems are designed for IT, not OT
Trustpoint acts as a trust anchor, issuing CA, or registration authority depending on deployment requirements. It manages the complete identity lifecycle from device onboarding through certificate renewal, revocation, and decommissioning.
Architecture Principles¶
The Trustpoint design follows these core principles:
OT suitability: Support segmented networks, offline operation, and constrained devices.
Standards-based protocols: Use EST (RFC 7030), CMP (RFC 9483), and OPC UA GDS Push for interoperability.
Lifecycle management: Treat certificates as managed identities with state, not isolated artifacts.
Deployment flexibility: Operate as a local CA, external RA, or hybrid depending on trust-domain ownership.
Crypto separation: Abstract key storage and signing operations from certificate-management logic.
Workflow integration: Support zero-touch automation, manual approval, webhooks, and notifications.
Modular extensibility: Isolate protocol handlers, PKI services, workflows, cryptography, and UI concerns.
System Context¶
Trustpoint integrates industrial devices, human operators, business systems, and PKI or HSM infrastructure into a unified certificate-management platform.
flowchart LR
subgraph INDUSTRIAL[Industrial environment]
DEV[Devices / machines / sensors / controllers]
OPC[OPC UA servers]
ENG[Engineering tools]
end
subgraph USERS[Human operators]
ADMIN[System administrators]
OPS[Operators and integrators]
AUDIT[Security and compliance]
end
subgraph ENTERPRISE[Enterprise integration]
ERP[ERP / MES systems]
IAM[Identity providers]
MON[Monitoring / SIEM]
MAIL[Mail notification]
end
TP[Trustpoint Platform]
EPKI[External PKI / Enterprise CA]
HSM[HSM or PKCS#11 / key storage]
DEV -->|EST, CMP, AOKI / certificate requests| TP
OPC -->|OPC UA GDS Push| TP
ENG -->|REST API / remote downloads| TP
ADMIN -->|Web UI / configuration| TP
OPS -->|Web UI / approvals| TP
AUDIT -->|Dashboard / logs, metrics| TP
TP -->|RA certificate requests| EPKI
TP -->|Key operations / signing| HSM
TP -->|Webhooks / events| ERP
TP -.->|Future: identity sync| IAM
TP -->|Metrics / logs| MON
TP -->|Notifications| MAIL
Key relationships:
Devices enroll, renew, and retrieve certificates via protocol endpoints.
Operators configure domains, approve onboarding requests, and monitor system state.
External PKI issues certificates when Trustpoint operates in RA mode.
HSM performs private-key operations for Trustpoint-managed issuing CAs.
Business systems receive lifecycle events via webhooks and notifications.
Documentation Structure¶
This architecture documentation is organized into the following topics:
Core Architecture¶
Runtime Architecture - Container structure, processes, lifecycle phases
Component Structure - Django applications, logical layers, URL routing
Security and Trust¶
Security Model - Trust boundaries, authentication, authorization
PKI Modes - CA vs RA operating modes, hybrid deployments
Device and Certificate Management¶
Device Lifecycle - Onboarding flow, certificate lifecycle, state machines
Infrastructure¶
Cryptography - Key management, PKCS#11, HSM integration
Data Management - Data storage, backup procedures, retention policies
Deployment and Operations¶
Deployment Scenarios - Common deployment patterns and configurations
Operations and Maintenance - Monitoring, logging, troubleshooting, performance tuning
Extensibility¶
Extensions and Future Development - Extension points, planned features, roadmap
- Runtime and Container Architecture
- Component Structure
- Security Model
- PKI Operating Modes: CA vs RA
- Device Lifecycle and Certificate Management
- Workflow Architecture
- Cryptography and Key Management
- Data Management
- Deployment Scenarios
- Operations and Maintenance
- Extensibility and Future Development
- Application Overview
- Application Dependencies
- Model Relationships
- URL Routing Map
- Credentials - Architecture
- Backup And Restore Concept
- Crypto Redesign Implementation Plan
- Overview
- Implementation Principles
- Scope Decisions for This Plan
- Milestone Summary
- Phase 0: Freeze the Target
- Phase 1: Create the New Package Skeleton
- Phase 2: Build the PKCS#11 Core
- Phase 3: First Vertical Slice
- Phase 4: Migrate Persistent Server-Held Flows
- Phase 5: Migrate Export / Download Flows
- Phase 6: Replace Secret Protection
- Phase 7: Remove Legacy Crypto Implementation
- Phase 8: Hardening, Restore, and Rollout
- Testing Strategy
- Recommended Order of File-Level Migration
- De-Risking Guidelines
- Definition of Done
- Crypto Backend Redesign
- Overview
- Status
- Goals
- Non-Goals
- Repository Findings That Drive This Design
- Core Design Decision
- Use-Case Model
- Top-Level Architecture
- Layer Responsibilities
- Target Package Structure
- Backend Contract
- Key Referencing Strategy
- Provider Profiles
- Capability Probing
- Managed Key Flow
- Export Bundle Flow
- Sessions, Login, and Concurrency
- Certificates and Credential Records
- Secrets Protection
- Bootstrap and Restore
- Error Handling
- Observability
- What Should Be Removed
- Out-of-Scope but Related
- Summary