Skip to main content
CMDashCyber Maturity Dashboard
← IACS UR E27: Cyber resilience of on-board systems and equipment

IACS UR E27: Cyber resilience of on-board systems and equipment control library

Every control CMDash tracks for IACS UR E27: Cyber resilience of on-board systems and equipment, in the order the standard itself uses. Each one is a row in the product with an owner, a status, evidence and its own history.

59 controls4 families33 mapped to other frameworksNo published text extract yet
T1-01Identify and authenticate every human user
Maps to ISO/IEC 27001:2022, NIST Cybersecurity Framework 2.0
T1-02Support full lifecycle management of accounts
Maps to ISO/IEC 27001:2022
T1-03Manage identifiers by user, group and role
T1-04Manage authenticators securely, including default changes
Maps to ISO/IEC 27001:2022
T1-05Identify and authenticate all parties on wireless links
T1-06Enforce configurable password strength
Maps to ISO/IEC 27001:2022
T1-07Hide credential feedback during login
T1-08Authorize users by separation of duties and least privilege
Maps to ISO/IEC 27001:2022, NIST Cybersecurity Framework 2.0
T1-09Authorize, monitor and restrict wireless use
T1-10Limit portable and mobile devices to those permitted and restrict code and data transfer
Maps to ISO/IEC 27001:2022
T1-11Control mobile code
T1-12Lock sessions after inactivity or on request
Maps to ISO/IEC 27001:2022
T1-13Generate security audit records for key event types
Maps to ISO/IEC 27001:2022, NIST Cybersecurity Framework 2.0
T1-14Size audit storage and prevent overrun
Maps to ISO/IEC 27001:2022
T1-15Keep essential services running if audit processing fails
T1-16Timestamp audit records
Maps to ISO/IEC 27001:2022
T1-17Protect integrity of information in transit
Maps to ISO/IEC 27001:2022
T1-18Protect against malicious code and unauthorized software, with updatable protection
Maps to ISO/IEC 27001:2022, NIST Cybersecurity Framework 2.0
T1-19Support verification of security functions and report anomalies in maintenance
T1-20Set outputs to a predetermined state when normal operation fails under attack
T1-21Protect confidentiality of information needing read authorization
Maps to ISO/IEC 27001:2022
T1-22Use accepted cryptographic algorithms, key sizes and mechanisms
Maps to ISO/IEC 27001:2022, NIS2
T1-23Give authorized users and tools read-only access to audit logs
Maps to ISO/IEC 27001:2022
T1-24Maintain essential functions during denial-of-service events
Maps to ISO/IEC 27001:2022, NIST Cybersecurity Framework 2.0
T1-25Limit resource use by security functions to prevent exhaustion
T1-26Identify critical files and support backups without disturbing operation
Maps to ISO/IEC 27001:2022, NIST Cybersecurity Framework 2.0
T1-27Recover and reconstitute to a known secure state
Maps to ISO/IEC 27001:2022, NIST Cybersecurity Framework 2.0
T1-28Switch to and from alternative power without losing security state
T1-29Configure to recommended network and security settings and expose the deployed settings
Maps to ISO/IEC 27001:2022, NIST Cybersecurity Framework 2.0
T1-30Restrict software, services, ports, protocols and access to what the CBS needs
Maps to ISO/IEC 27001:2022, NIST Cybersecurity Framework 2.0

Control identifiers, families and titles are the rows CMDash’s own seed data writes for IACS UR E27: Cyber resilience of on-board systems and equipment Rev.1 (Sep 2023), published from a build-time export rather than read from any customer’s workspace. Cross-framework mappings are CMDash’s own, and each one is shown on both frameworks it connects.

Track these controls in CMDash

Every control on this page becomes a row with an owner, a status, evidence and an audit trail — with the crosswalks already wired, so evidence mapped once counts in more than one framework.

IACS UR E27: Cyber resilience of on-board systems and equipment controls — CMDash