International (IACS, 12 classification societies)

IACS Unified Requirements E26/E27

118 controls. 91 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

118 controls 91 frameworks share controls with it International (IACS, 12 classification societies) verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

Every control

CodeControlAlso in
IACS-UR-E26-Detect-Logging-Monitoring-Audit-AlertingIACS UR E26 Detect Goal - Logging + Network Monitoring + Audit Trail + Alerting + SIEM19
IACS-UR-E26-Identify-AssetInventory-CBS-NetworkArchitecture-RiskIACS UR E26 Identify Goal - Asset Inventory of Computer Based Systems + Network Architecture Documentation + Risk-Assessable Scope6
IACS-UR-E26-Identify-Plan-Risk-Survey-DocumentationIACS UR E26 Identify Goal - Ship Cyber Resilience Plan + CBS Risk Assessment + Survey + Documentation41
IACS-UR-E26-Implementation-Training-Supplier-OEM-OnboardTrainingIACS UR E26 Implementation - Training + Awareness + Supplier + OEM Management + Cyber Hygiene0
IACS-UR-E26-Protect-AccessControl-Authentication-IAM-RolesIACS UR E26 Protect Goal - Access Control + Identity + Authentication + Authorization + User Management34
IACS-UR-E26-Protect-Malware-Patch-VulnMgmt-HardeningIACS UR E26 Protect Goal - Malware Defence + Patch + Vulnerability Management + Hardening + Whitelisting0
IACS-UR-E26-Protect-NetworkSegmentation-Zones-Conduits-BoundaryIACS UR E26 Protect Goal - Network Segmentation + Zones + Conduits + Boundary Defence + Data Diodes14
IACS-UR-E26-Protect-RemoteAccess-Wireless-Physical-BoundaryIACS UR E26 Protect Goal - Remote Access + Wireless + Physical Security + Boundary Protection32
IACS-UR-E26-Respond-Recover-IncidentResponse-Recovery-Backup-LessonsIACS UR E26 Respond + Recover Goals - Incident Response + Communication + Recovery + Backup + Lessons Learned49
IACS-UR-E26-Scope-Applicability-2024-IMO-MSC-428IACS UR E26 - Scope + Applicability + Effective 1 July 2024 + Coordination IMO MSC.428(98) + Member Societies0
IACS-UR-E26-Survey-Approval-Documentation-OwnerPackageIACS UR E26 - Class Society Survey + Approval + Owner Documentation + Periodic Review0
IACS-UR-E27-Documentation-Owner-Package-Coordination-IMO-IEC-NISTIACS UR E27 - Documentation Package for Owner + Coordination IMO + IEC 62443 + NIST CSF + 2024-2025 Pipeline0
IACS-UR-E27-Equipment-Hardening-SecureConfig-CommunicationsIACS UR E27 - Equipment Hardening + Secure Configuration + Secure Communications + Cryptography20
IACS-UR-E27-Equipment-UserAuth-Authentication-AuthorizationIACS UR E27 - Equipment User Authentication + Authorization + Session Management + Privileged Access35
IACS-UR-E27-Logging-Forensics-EventCaptureIACS UR E27 - Equipment Logging + Forensic Readiness + Event Capture + Tamper Detection51
IACS-UR-E27-SBOM-SecureDev-TypeApproval-SoftwareIntegrityIACS UR E27 - Software Bill of Materials + Secure Development Lifecycle + Type Approval + Software Integrity0
IACS-UR-E27-Scope-System-Categorization-CategoryI-II-IIIIACS UR E27 - Scope + System-Level Applicability + Category I/II/III Classification + IEC 62443 Security Levels0
IACS-UR-E27-SecurityCapabilities-IEC62443-CategoryProfileIACS UR E27 - Security Capabilities by Category + IEC 62443-4-2 Foundational Requirements + Component Requirements0
IACS-UR-E27-Updates-Patch-Mechanisms-MaintenanceIACS UR E27 - Equipment Update + Patch Mechanisms + Maintenance + Lifecycle Support0
E26-4.1E26 4.1 Identify0
E26-4.1.1E26 4.1.1 Vessel asset inventory1
E26-4.2E26 4.2 Protect0
E26-4.2.1E26 4.2.1 Security zones and network segmentation1
E26-4.2.2E26 4.2.2 Network protection safeguards1
E26-4.2.3E26 4.2.3 Antivirus, antimalware, antispam and other protections from malicious code1
E26-4.2.4E26 4.2.4 Access control1
E26-4.2.5E26 4.2.5 Wireless communication1
E26-4.2.6E26 4.2.6 Remote access control and communication with untrusted networks1
E26-4.2.7E26 4.2.7 Use of mobile and portable devices1
E26-4.3E26 4.3 Detect0
E26-4.3.1E26 4.3.1 Network operation monitoring1
E26-4.3.2E26 4.3.2 Verification and diagnostic functions of CBS and networks0
E26-4.4E26 4.4 Respond0
E26-4.4.1E26 4.4.1 Incident response plan1
E26-4.4.2E26 4.4.2 Local, independent and/or manual operation0
E26-4.4.3E26 4.4.3 Network isolation1
E26-4.4.4E26 4.4.4 Fallback to a minimal risk condition0
E26-4.5E26 4.5 Recover0
E26-4.5.1E26 4.5.1 Recovery plan1
E26-4.5.2E26 4.5.2 Backup and restore capability1
E26-4.5.3E26 4.5.3 Controlled shutdown, reset, roll-back and restart0
E26-5E26 5 Demonstration of compliance0
E26-5.1E26 5.1 During design and construction phases0
E26-5.2E26 5.2 Upon ship commissioning0
E26-5.3E26 5.3 During the operational life of the ship1
E26-6E26 6 Risk assessment for exclusion of CBS from the application of requirements0
E26-appE26 Appendices I and II0
E26-defsE26 2 and 3 Definitions, goals and organisation0
E26-introE26 1 Introduction and scope0
E27-2.3E27 2.3 Essential systems availability0
E27-2.4E27 2.4 Compensating countermeasures0
E27-3.1E27 3.1 CBS documentation0
E27-3.1.1E27 3.1.1 CBS asset inventory0
E27-3.1.10E27 3.1.10 Test reports0
E27-3.1.2E27 3.1.2 Topology diagrams0
E27-3.1.3E27 3.1.3 Description of security capabilities0
E27-3.1.4E27 3.1.4 Test procedure of security capabilities0
E27-3.1.5E27 3.1.5 Security configuration guidelines0
E27-3.1.6E27 3.1.6 Secure development lifecycle documents0
E27-3.1.7E27 3.1.7 Plans for maintenance and verification of the CBS0
E27-3.1.8E27 3.1.8 Information supporting the owner's incident response and recovery plan0
E27-3.1.9E27 3.1.9 Management of change plan0
E27-4.1E27 4.1 Required security capabilities (Table 1)0
E27-4.1-01E27 item 1: Human user identification and authentication0
E27-4.1-02E27 item 2: Account management0
E27-4.1-03E27 item 3: Identifier management0
E27-4.1-04E27 item 4: Authenticator management0
E27-4.1-05E27 item 5: Wireless access management0
E27-4.1-06E27 item 6: Strength of password-based authentication0
E27-4.1-07E27 item 7: Authenticator feedback0
E27-4.1-08E27 item 8: Authorization enforcement0
E27-4.1-09E27 item 9: Wireless use control0
E27-4.1-10E27 item 10: Use control for portable and mobile devices0
E27-4.1-11E27 item 11: Mobile code0
E27-4.1-12E27 item 12: Session lock0
E27-4.1-13E27 item 13: Auditable events0
E27-4.1-14E27 item 14: Audit storage capacity0
E27-4.1-15E27 item 15: Response to audit processing failures0
E27-4.1-16E27 item 16: Timestamps0
E27-4.1-17E27 item 17: Communication integrity0
E27-4.1-18E27 item 18: Malicious code protection0
E27-4.1-19E27 item 19: Security functionality verification0
E27-4.1-20E27 item 20: Deterministic output0
E27-4.1-21E27 item 21: Information confidentiality0
E27-4.1-22E27 item 22: Use of cryptography0
E27-4.1-23E27 item 23: Audit log accessibility0
E27-4.1-24E27 item 24: Denial of service protection0
E27-4.1-25E27 item 25: Resource management0
E27-4.1-26E27 item 26: System backup0
E27-4.1-27E27 item 27: System recovery and reconstitution0
E27-4.1-28E27 item 28: Alternative power source0
E27-4.1-29E27 item 29: Network and security configuration settings0
E27-4.1-30E27 item 30: Least functionality0
E27-4.2E27 4.2 Additional security capabilities (Table 2)0
E27-4.2-31E27 item 31: Multifactor authentication for human users0
E27-4.2-32E27 item 32: Software process and device identification and authentication0
E27-4.2-33E27 item 33: Unsuccessful login attempts0
E27-4.2-34E27 item 34: System use notification0
E27-4.2-35E27 item 35: Access via untrusted networks0
E27-4.2-36E27 item 36: Explicit access request approval0
E27-4.2-37E27 item 37: Remote session termination0
E27-4.2-38E27 item 38: Cryptographic integrity protection0
E27-4.2-39E27 item 39: Input validation0
E27-4.2-40E27 item 40: Session integrity0
E27-4.2-41E27 item 41: Invalidation of session IDs after session termination0
E27-5E27 5 Secure development lifecycle requirements0
E27-5.1E27 5.1 Controls for private keys (IEC 62443-4-1 SM-8)0
E27-5.2E27 5.2 Security update documentation (IEC 62443-4-1 SUM-2)0
E27-5.3E27 5.3 Dependent component security update documentation (IEC 62443-4-1 SUM-3)0
E27-5.4E27 5.4 Security update delivery (IEC 62443-4-1 SUM-4)0
E27-5.5E27 5.5 Product defence in depth (IEC 62443-4-1 SG-1)0
E27-5.6E27 5.6 Defence in depth measures expected in the environment (IEC 62443-4-1 SG-2)0
E27-5.7E27 5.7 Security hardening guidelines (IEC 62443-4-1 SG-3)0
E27-6E27 6 Demonstration of compliance0
E27-6.2E27 6.2 Plan approval0
E27-6.3E27 6.3 Survey and factory acceptance test0
E27-appE27 Appendix II0
E27-introE27 1 and 2 General, scope, definitions and security philosophy0

Tell me when IACS Unified Requirements E26/E27 files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What this page is

A control-level reference for IACS Unified Requirements E26/E27, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition