Safety & Security

Safety needs
traceable evidence.

Functional safety and cybersecurity: from development to operation – tailored to your application.

Safe · Modular · Secure by Design

Background imageAI-generated concept visualisation

Safety

Functional safety.

System understanding, engineering and evidence for industry and rail.

Development · Assurance · Standards

Core expertise in safety

Engineering & Functional safety assurance

  • Functional safety support and assurance
  • Verification / Validation / Qualification
  • Test and evidence planning

Standards for rail and mechanical engineering

  • IEC 61508
  • EN 50126 / EN 50129 / EN 50716
  • IEC 62061 / ISO 13849
  • ISO 25119 / ISO 10218

Project & System support

  • Project implementation
  • New / pilot projects
  • Existing projects
  • Test automation / Test rigs / Test languages

Sector & cybersecurity standards

  • ISO 26262 / IEC 61511
  • IEC 62304 / IEC 60601
  • IEC 62443 / ISO 27001
  • IEC 63452 / CLC/TS 50701

Application areas

Functional safety for rail

Command, control and signalling infrastructure

  • Axle counters / Signals
  • Points / point machines
  • Electronic interlockings / Level crossings
  • Object Controllers

Control & communication in rail vehicles

  • Door systems / Door controls
  • Rail / Light rail TCMS / CBTC
  • Drive systems
  • MVB / WTB / TRDP / SDTv2 / FSoE

Train protection & train control systems

  • ETCS / CBTC / ATO / ATP
  • Modernisation of existing train protection systems
  • Safety displays / ATS / ATC
  • EULYNX / RaSTA

Functional safety & Braking in rail vehicles

  • SiFa / Speedometer / Speed limits
  • Brakes / magnetic track brakes
  • Wheel slide protection / Wheel slip protection / Rollback protection
Safe · Modular · Secure by Design

Develop safety.
Across the entire lifecycle.

A safety function extends from detecting a condition to delivering an effective response. We consider this complete chain together with hardware, software and interfaces. System design with ETENAR Safe Config and engineering with ETENAR Safe Kit remain aligned with the same requirements.

  1. Requirements & risk

    Describe hazards, safety functions and operating conditions. The required risk reduction and applicable framework determine the requirements for the function.

  2. Architecture & implementation

    Assign functions to building blocks and define interfaces and fault responses. Clear module boundaries make dependencies visible and support subsequent changes.

  3. Verification & validation

    Check that the implementation meets its requirements and the safety function is suitable for the application. Keep test cases, results and deviations traceably linked.

  4. Operation & change

    Include maintenance, testing and new system versions. Assess changes and their effects on unchanged parts, and determine which existing evidence remains applicable.

One shared system baseline: requirements, configuration, software and test results provide the basis for integration and further development.

Plan modernisation
Security · Secure by Design

Secure by Design.

Protection for deployment, operation, updates and servicing.

Security overview from the display: Security standards & SL 3, Trusted hardware platform, Encryption & access control and Key management.
Security at a glanceIEC 62443-4-1/2 / CRA

Standards-oriented development

IEC 62443: development process (4-1), components (4-2), systems (3-3). Applicable CRA requirements are considered in the product and development process.

Trusted hardware options

Selected configurations may include TPM-backed trust, Secure Boot, secure updates and protected storage.

Encryption & Access Control

Authentication, authorisation and encryption are defined in the security concept. The selected variant determines the mechanisms and interfaces available.

Key management throughout the lifecycle

Key management functions can support provisioning, operation, updates and servicing throughout the system lifecycle.

Security across the lifecycle

Bring technology
and responsibility together.

Protection mechanisms need suitable operating conditions and clear responsibilities. Manufacturers, integrators and operators therefore agree how access, keys, updates and vulnerabilities will be managed throughout the system's working life.

Development

Prepare the product.

Describe available protection mechanisms, product versions and operating conditions. Secure provisioning, software maintenance and information for integration form part of the development task.

Define: the product baseline, security functions and maintenance procedures.

Integration

Protect the complete system.

Align communication paths, system boundaries and access rights with the environment. The security concept also considers interfaces between components and interactions with safety functions.

Define: interfaces, permissions and integration tests.

Operation

Maintain protection.

Assign responsibilities for maintenance, updates and vulnerability handling. Assess and test changes before adoption, then document them in the released system baseline.

Define: contacts, approvals and change procedures.

The IEC 62443 series distinguishes development processes, components and systems. Required measures and evidence depend on the specific role, product variant and application.

SIL & evidence

The application defines the scope.

SIL 1–4 describes the safety integrity of a safety function under IEC 61508. The required level follows from the risk assessment and the applicable framework.

The standard, product version, system boundaries and operating conditions define the scope of evidence. Product evidence does not replace system validation. Security Levels are not equivalent to SIL; earlier editions of standards may apply to existing projects.

Product certificates and their scope are provided for the project where available for the selected configuration.

Which requirements apply to your project?

We start with the application and clarify the scope of evidence required.

Discuss your project