Cross-Framework Mapping

IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board SystemsvsHL7 FHIR Security Framework

See exactly how IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems controls map to HL7 FHIR Security Framework. Pre-computed mappings, identified gaps, and coverage analysis.

5
Controls Mapped
14
Gaps Found
16%
Coverage

Need this as a report you can hand to an assessor? A coverage crosswalk for this pair can be built to order.

According to the TheArtOfService Compliance Knowledge Graph:

IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems maps to HL7 FHIR Security Framework with 16% coverage across 3 directly mapped controls. Analysis of 19 IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems controls identifies 16 compliance gaps, primarily concentrated in IACS UR E26 Survey + Approval.

Source: TheArtOfService Knowledge Graph | 19 controls analysed | 704 frameworks | 306K+ cross-framework mappings

Control Mappings

Showing 5 of 5 mapped controls across 3 domains. Sign up to explore all 306K+ mappings across 704 frameworks.

IACS UR E26 Detect(2 mappings)

IACS-UR-E26-Detect-Logging-Monitoring-Audit-AlertingIACS UR E26 Detect Goal - Logging + Network Monitoring + Audit Trail + Alerting + SIEM2 targets
HL7-FHIR-Audit-Provenance-DigitalSignatures-IntegrityHL7 FHIR Audit + Provenance + Digital Signatures + AuditEvent Resource + Audit Log Integrity + Retention
HL7-FHIR-Transport-TLS-CommunicationHL7 FHIR Transport Security - TLS 1.2+, Communication Security, Time Keeping, Server CapabilityStatement

IACS UR E27 User Auth(1 mappings)

IACS-UR-E27-Equipment-UserAuth-Authentication-AuthorizationIACS UR E27 - Equipment User Authentication + Authorization + Session Management + Privileged Access
HL7-FHIR-Auth-SMART-OAuth-OIDC-BackendHL7 FHIR Authentication - SMART App Launch + OAuth 2.0 + OpenID Connect + Backend Services + Token Lifetime

IACS UR E27 Logging + Forensics(2 mappings)

IACS-UR-E27-Logging-Forensics-EventCaptureIACS UR E27 - Equipment Logging + Forensic Readiness + Event Capture + Tamper Detection2 targets
HL7-FHIR-Audit-Provenance-DigitalSignatures-IntegrityHL7 FHIR Audit + Provenance + Digital Signatures + AuditEvent Resource + Audit Log Integrity + Retention
HL7-FHIR-Transport-TLS-CommunicationHL7 FHIR Transport Security - TLS 1.2+, Communication Security, Time Keeping, Server CapabilityStatement
Coverage crosswalk

A IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems to HL7 FHIR Security Framework crosswalk, built to order

The table above lists candidate mappings. A crosswalk answers the narrower question you are probably here for: which HL7 FHIR Security Framework controls your existing IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems work already satisfies, which are real gaps, and the reasoning behind every claim so you can check it. One pair, $299, one time.

IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems into HL7 FHIR Security Framework
Not published yet

This direction has not been through crosswalk review and sign off, so no coverage figure is published for it. Reporting an unreviewed number would be worse than reporting none. It can be built to order at the same price as a pair that is already on the shelf.

If the two frameworks turn out to have too little in common for a crosswalk to help you, we say so and refund it rather than send a number worth nothing.

HL7 FHIR Security Framework into IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems
Not published yet

This direction has not been through crosswalk review and sign off, so no coverage figure is published for it. Reporting an unreviewed number would be worse than reporting none. It can be built to order at the same price as a pair that is already on the shelf.

If the two frameworks turn out to have too little in common for a crosswalk to help you, we say so and refund it rather than send a number worth nothing.

IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems to HL7 FHIR Security Framework (built to order)
$299
per framework pair, one time
  • Every evidenced control, with the reasoning behind it
  • Every gap, with what it requires
  • Its level of review stated plainly, not a bare number

Why this page shows two different percentages. The 16% in the header counts how many IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems controls carry at least one candidate mapping in the graph, before any review. The crosswalk percentage counts something stricter: how many HL7 FHIR Security Framework controls are actually evidenced, after a pass that argued against each mapping and kept only what survived. They answer different questions and they are not meant to agree.

A crosswalk narrows the work. It does not replace an audit, and your assessor may take a different view on individual controls. Mappings between frameworks are judgements, not text printed in either standard, which is why every claim in the report shows its reasoning. Questions go to support@theartofservice.com.

Related Comparisons

Other IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems comparisons

Other HL7 FHIR Security Framework comparisons

Stop Paying Consultants to Read Spreadsheets

AI-powered compliance intelligence across 704 frameworks, at a fraction of consulting costs.

$0/forever

Free

  • 704 framework browser
  • Cross-framework mappings (306K+)
  • 824 compliance assessments
  • 3 AI queries & searches per day
Get Started Free
Recommended
$149/month

Professional

  • Unlimited AI Compliance Advisory
  • Unlimited full-text search
  • Framework self-assessment
  • PDF, Excel & CSV exports
Start 7-Day Free Trial →

What are the key differences between IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems and HL7 FHIR Security Framework?

IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems has 19 controls across its framework, while HL7 FHIR Security Framework covers 7 controls. Direct mapping analysis identifies 3 overlapping controls (16% coverage). The frameworks diverge most significantly in IACS UR E26 Survey + Approval, where 1 IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems controls have no direct HL7 FHIR Security Framework equivalent.

How many controls map between IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems and HL7 FHIR Security Framework?

Of 19 total IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems controls, 3 map directly to HL7 FHIR Security Framework controls, representing 16% coverage. The remaining 16 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems to HL7 FHIR Security Framework?

16 IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems controls have no direct equivalent in HL7 FHIR Security Framework. The highest concentration of gaps is in IACS UR E26 Survey + Approval with 1 unmapped controls. These gaps represent areas where additional controls, policies, or documentation must be created to achieve compliance with both frameworks.

Which control domains have the most gaps between IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems and HL7 FHIR Security Framework?

The domain with the highest gap count is IACS UR E26 Survey + Approval (1 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.

This platform provides educational compliance tools, not legal, regulatory, or professional compliance advice. Cross-framework mappings are AI-assisted interpretations and do not reproduce or replace official standards. Framework names and trademarks belong to their respective owners. Consult qualified professionals for your specific compliance requirements. See our Terms of Service.