Cross-Framework Mapping

IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board SystemsvsFISMA

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

8
Controls Mapped
94
Gaps Found
8%
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 FISMA with 8% coverage across 8 directly mapped controls. Analysis of 102 IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems controls identifies 94 compliance gaps, primarily concentrated in UR E27 section 4: security capabilities – IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems.

Source: TheArtOfService Knowledge Graph | 102 controls analysed | 1,016 frameworks | 316K+ cross-framework mappings

Control Mappings

Showing 13 of 13 control mappings across 1 domains. Sign up to explore all 316K+ mappings across 1,016 frameworks.

Superseded batch representation – IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems(13 mappings)

IACS-UR-E26-Detect-Logging-Monitoring-Audit-AlertingIACS UR E26 Detect Goal - Logging + Network Monitoring + Audit Trail + Alerting + SIEM
→FISMA-NIST-800-53-RMF-800-171-FIPSOperationalisation via NIST 800-53 + 800-37 RMF + 800-171 + FIPS 199 + FIPS 200
IACS-UR-E26-Identify-Plan-Risk-Survey-DocumentationIACS UR E26 Identify Goal - Ship Cyber Resilience Plan + CBS Risk Assessment + Survey + Documentation3 targets
→FISMA-3554-Agency-ResponsibilitiesFederal Agency Responsibilities (44 USC 3554) - CIO + CISO + Program + Reporting
→FISMA-CIRCIA-ZTA-EO14028CIRCIA, Zero Trust Architecture, EO 14028 + 14110 + OMB Memoranda
→FISMA-NIST-800-53-RMF-800-171-FIPSOperationalisation via NIST 800-53 + 800-37 RMF + 800-171 + FIPS 199 + FIPS 200
IACS-UR-E26-Protect-AccessControl-Authentication-IAM-RolesIACS UR E26 Protect Goal - Access Control + Identity + Authentication + Authorization + User Management
→FISMA-CIRCIA-ZTA-EO14028CIRCIA, Zero Trust Architecture, EO 14028 + 14110 + OMB Memoranda
IACS-UR-E26-Protect-RemoteAccess-Wireless-Physical-BoundaryIACS UR E26 Protect Goal - Remote Access + Wireless + Physical Security + Boundary Protection
→FISMA-NIST-800-53-RMF-800-171-FIPSOperationalisation via NIST 800-53 + 800-37 RMF + 800-171 + FIPS 199 + FIPS 200
IACS-UR-E26-Respond-Recover-IncidentResponse-Recovery-Backup-LessonsIACS UR E26 Respond + Recover Goals - Incident Response + Communication + Recovery + Backup + Lessons Learned2 targets
→FISMA-3554-Agency-ResponsibilitiesFederal Agency Responsibilities (44 USC 3554) - CIO + CISO + Program + Reporting
→FISMA-NIST-800-53-RMF-800-171-FIPSOperationalisation via NIST 800-53 + 800-37 RMF + 800-171 + FIPS 199 + FIPS 200
IACS-UR-E27-Equipment-Hardening-SecureConfig-CommunicationsIACS UR E27 - Equipment Hardening + Secure Configuration + Secure Communications + Cryptography2 targets
→FISMA-3554-Agency-ResponsibilitiesFederal Agency Responsibilities (44 USC 3554) - CIO + CISO + Program + Reporting
→FISMA-NIST-800-53-RMF-800-171-FIPSOperationalisation via NIST 800-53 + 800-37 RMF + 800-171 + FIPS 199 + FIPS 200
IACS-UR-E27-Equipment-UserAuth-Authentication-AuthorizationIACS UR E27 - Equipment User Authentication + Authorization + Session Management + Privileged Access
→FISMA-CIRCIA-ZTA-EO14028CIRCIA, Zero Trust Architecture, EO 14028 + 14110 + OMB Memoranda
IACS-UR-E27-Logging-Forensics-EventCaptureIACS UR E27 - Equipment Logging + Forensic Readiness + Event Capture + Tamper Detection2 targets
→FISMA-3554-Agency-ResponsibilitiesFederal Agency Responsibilities (44 USC 3554) - CIO + CISO + Program + Reporting
→FISMA-NIST-800-53-RMF-800-171-FIPSOperationalisation via NIST 800-53 + 800-37 RMF + 800-171 + FIPS 199 + FIPS 200
Coverage crosswalk

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

The table above lists candidate mappings. A crosswalk answers the narrower question you are probably here for: which FISMA 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 FISMA
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.

FISMA 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 FISMA (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 8% 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 FISMA 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 FISMA comparisons

Stop Paying Consultants to Read Spreadsheets

Cross-framework mappings across 1,016 frameworks, at a fraction of consulting costs.

$0/forever

Free

  • ✓ 1,016 framework browser
  • ✓ Cross-framework mappings (316K+)
  • ✓ 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 FISMA?

IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems has 102 controls across its framework, while FISMA covers 50 controls. Direct mapping analysis identifies 8 overlapping controls (8% coverage). The frameworks diverge most significantly in UR E27 section 4: security capabilities – IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems, where 41 IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems controls have no direct FISMA equivalent.

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

Of 102 total IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems controls, 8 map directly to FISMA controls, representing 8% coverage. The remaining 94 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 FISMA?

94 IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems controls have no direct equivalent in FISMA. The highest concentration of gaps is in UR E27 section 4: security capabilities – IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems with 41 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 FISMA?

The domain with the highest gap count is UR E27 section 4: security capabilities – IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems (41 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.