FIELD / OT
Onboard, Trackside & Field Networks
- Identify Target Devices & Connection Segments
- Separate Network Segments & Define Permitted Communications
- Device Authentication & Secure Key Delivery
Field Connection Boundary

CYBERSECURITY · MOBILITY TRUST
Security engineering for railway control communications and road and AI operational infrastructure.
We design cryptographic keys, networks, operating permissions and verification evidence as one system.
KMC · KEY MANAGEMENT CENTER
CREWAVE designs and develops KMC systems integrating key management applications, HSMs, operations and audit functions. We incorporate key distribution methods for the target control communications and field operating procedures.
KMC / KEY MANAGEMENT CENTER
Policy Configuration · Task Requests · Processing Results
PKCS#11 Integration
Online & Offline Key Delivery
The key management application manages operating policies and delivery procedures and integrates the HSM’s key protection and cryptographic functions.
CREWAVE ENGINEERING
We design device registration, key distribution and renewal policies, management consoles, and audit and recovery procedures for each target system.
HSM INTEGRATION
We integrate the key protection and cryptographic operations provided by Thales HSMs with CREWAVE’s key management application through the PKCS#11 interface.
SECURITY ARCHITECTURE
A security architecture designed and integrated to project requirements.
FIELD / OT
Field Connection Boundary
CREWAVE / KMC
Key Management Application + HSM
OPERATIONS / GOVERNANCE
Management Access Boundary
CYBERSECURITY SCOPE
01 / SECURE COMMUNICATION
We distinguish communication paths from operational access across onboard, trackside and control center systems. We design authentication, encryption and access policies with existing equipment and availability requirements in mind.
02 / IDENTITY & KEY
We connect device registration and key distribution with replacement, renewal and destruction procedures. We review online and offline operating conditions and HSM integration methods.
03 / DATA GOVERNANCE
We define the purposes and authorized users for collecting video, events and operational history. We establish data retention, export and deletion policies and an audit framework.
04 / RESILIENCE
We connect security requirements with design and testing, enabling vulnerability remediation, configuration changes, backup and recovery to be reviewed during operations.
PROJECT INTEGRATION
Distinguish devices, data, communication paths and operational access.
Define authentication, key delivery, permissions, audit and system integration requirements.
Verify normal operation, access denial, communication failure and recovery conditions.
Document configuration information, change history, and backup and recovery procedures for operations.
ENGINEERING EVIDENCE
| Stage | Review Scope | Example Deliverables |
|---|---|---|
| Requirements Definition | Define protection scope, operational boundaries and device requirements | Requirements Specification · Risk Review |
| Design & Integration | Design key delivery paths, operating permissions and approval procedures | SRS / SDD / ICD |
| Testing & Verification | Functional, integration, exception and security testing and assessment | STP / STR · Test Evidence |
| Traceability & Handover | Assess requirement changes and update design and verification items | RTM · Operations & Maintenance Documents |
We analyze requirements for products, systems and development processes with the industrial control system security lifecycle in mind. We define applicability and test criteria based on the target system’s assets and operating environment, and connect them with design and verification.
DEFINE YOUR SECURITY SCOPE
LET’S MOVE FORWARD
From site conditions and product needs to implementation, operations and technical collaboration.