KMC · KEY MANAGEMENT CENTER
Manage cryptographic keys for train-control communications,
from generation through renewal, destruction and operational history.
SYSTEM ARCHITECTURE
KMC / KEY MANAGEMENT CENTER
Policy settings · Task requests · Processing results
PKCS#11 integration
Online & offline key delivery
The key management application manages operating policies and delivery procedures, integrating the HSM's key protection and cryptographic functions.
Policy, user, target-device and audit modules, together with administration screens, are built around the Key Management Core. Key distribution methods for train-control communication devices, operator workflows and HSM interfaces are designed and developed together.
Source: 2026 Company Profile, pages 18 & 19 · Design & development scope
Detailed models, installation conditions, integration scope and acceptance criteria are finalized through project review and approved specifications.
COMMUNICATION TRUST
Authentication keys (KMAC) in ETCS communications are used for message authentication and integrity verification. KMC is designed as a framework for managing key targets, validity periods and distribution status.
Identity verification and protected channels for management and server communications are integrated with PKI and TLS security frameworks. Roles are defined to manage certificates and trust settings separately from the lifecycle of operational cryptographic keys.
KEY LIFECYCLE
This is the design and development scope of the key management software. Transition, approval and recovery procedures are configured to suit target-device specifications and operating policies.
Define devices and communication relationships using the keys, along with key identifiers, validity periods and renewal intervals.
Configure generation and storage methods for each key type and purpose, distinguishing the HSM's protected domain from the application's management scope.
Deliver keys to target devices through online communications or offline delivery procedures, and track task results.
Manage the status and validity periods of keys applied to devices, connecting change and operational histories.
Define renewal timing and transition procedures, and design handling for exceptions such as distribution failures and communication interruptions.
Handle deactivation and destruction separately, reflecting the changes in related device, policy and audit records.
INTERFACES & DELIVERY
Distinguish online/offline paths and HSM/management interfaces, specifying data and processing conditions in each project's interface definition document.
Integrate connections, authentication, key delivery and processing results between KMC and target devices. Include delayed responses, duplicate requests, disconnections and reconnection scenarios in the interface definition.
Integration itemsTarget identification · Requests/responses · Processing status · Exception handling
Configure key delivery and application procedures for environments with limited network connectivity. Link protection of delivery materials, transfer and receipt records, and target-device application results with operating procedures.
Integration itemsDelivery-material protection · Transfer/receipt · Application confirmation · History
Use the PKCS#11 interface to connect the key management application to the A700's key protection and cryptographic functions. Reflect permissions, connection status and returned errors in the application's processing flow.
Integration itemsPKCS#11 · Protected key references · Permissions · Error handling
Configure identity authentication and protected channels for management and server communications according to the target system's security policies. Separate operational key distribution and renewal management from certificate and trust-framework management.
Integration itemsAccess authentication · Protected channels · Certificate expiry · Trust settings
OPERATIONS & AUDIT
Define the scope of Web UI and CLI tasks, and enable checks of key, device and distribution-task status. Connect the status and error information operators need with administration screens.
Managed assetsKey & device lists · Task status · Connection status · Errors
Define user and role permissions, and design execution permissions and approval procedures for critical tasks such as key generation, distribution and destruction. Configure HSM access and KMC operating permissions for their respective protected assets.
Control itemsRole separation · Access authentication · Task permissions · Approval procedures
Design records to capture who performed each task, when, on which target and with what result. Separate logging fields to prevent raw cryptographic keys and authentication secrets from appearing in operational logs.
Record fieldsActor · Time · Task · Target · Result
Design backup and recovery procedures for the key protection method and data management scope. Review consistency of key, policy and device states and reconnection behavior after failures, defining redundancy according to each project's availability requirements.
Review itemsBackup scope · Recovery permissions · State consistency · Failure recovery
VERIFICATION & DELIVERABLES
Design test scope and acceptance criteria to verify key management functions, device integration and operational controls together.
State transitions for generation, distribution, renewal and destruction; validity periods and deactivation handling
Valid requests, returned errors, disconnection and reconnection, and device application results
Authorized and unauthorized users, role-based permissions and critical-task approval conditions
Duplicate requests, target mismatches, expired delivery materials, and delay/failure handling
Actor, target and result tracking; log access permissions; prevention of secret exposure
Recovery procedures and permissions, consistency of data and key references, and conditions for resuming operations
Analyze relevant IEC 62443 security requirements for the applicable scope and connect them with design and testing. Security levels, certification scope, and performance and availability criteria are defined according to the target system configuration and project requirements.
PROJECT INTEGRATION
DEFINE YOUR SECURITY SCOPE
LET’S MOVE FORWARD
From site conditions and product needs to implementation, operations and technical collaboration.