Cross-Framework Mapping

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

Name: IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems to FISMA Control Mapping Dataset
Creator: TheArtOfService

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.

Controls Mapped

Gaps Found

42%

Coverage

According to the TheArtOfService Compliance Knowledge Graph:

IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems maps to FISMA with 42% coverage across 8 directly mapped controls. Analysis of 19 IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems controls identifies 11 compliance gaps — primarily concentrated in IACS UR E26 Survey + Approval.

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

Control Mappings

Showing 13 of 13 mapped controls across 8 domains. Sign up to explore all 332K+ mappings across 723 frameworks.

IACS UR E26 Detect(1 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 - Risk + Plan(3 mappings)

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 - Access + IAM(1 mappings)

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 - Remote + Wireless + Physical(1 mappings)

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(2 mappings)

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 Hardening + Communications(2 mappings)

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 User Auth(1 mappings)

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(2 mappings)

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

Related Comparisons

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

Other FISMA comparisons

BSI IT-Grundschutz vs FISMA3 mappings Vietnam Law on Cybersecurity (No. 24/2018/QH14) vs FISMA3 mappings Vermont Artificial Intelligence and Consumer Data Act (AICDA) vs FISMA3 mappings US Gramm-Leach-Bliley Act (GLBA) - Higher Education Safeguards Rule vs FISMA3 mappings US EPA Safe Drinking Water Act (SDWA) - Cybersecurity Requirements vs FISMA3 mappings UK Defence Standard 05-138 - Cyber Security for Defence Suppliers vs FISMA3 mappings TEFCA - Trusted Exchange Framework and Common Agreement vs FISMA3 mappings Protective Security Policy Framework (PSPF) Release 2024 vs FISMA3 mappings

Stop Paying Consultants to Read Spreadsheets

AI-powered compliance intelligence across 723 frameworks — at a fraction of consulting costs.

$0/forever

Free

✓ 723 framework browser
✓ Cross-framework mappings (332K+)
✓ 824 compliance assessments
✓ 3 AI queries & searches per day

Get Started Free

Recommended

$49/month

Professional

✓ Unlimited AI Compliance Advisory
✓ Unlimited full-text search
✓ Framework self-assessment
✓ PDF, Excel & CSV exports

Start 7-Day Free Trial →

Popular framework comparisons

NIST CSF vs NIST 800-53 ISO 27001 vs NIST CSF CMMC vs NIST 800-53 FedRAMP vs NIST 800-53 NIST CSF vs SOC 2 HIPAA vs NIST 800-53 ISO 27001 vs SOC 2 ISO 27001 vs ISO 27701

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 19 controls across its framework, while FISMA covers 12 controls. Direct mapping analysis identifies 8 overlapping controls (42% 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 FISMA equivalent.

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

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

11 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 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 FISMA?

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.

Related Resources

How to Map Controls Across Frameworks|Multi-Framework Compliance Guide|Compliance Glossary

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.