Cross-Framework Mapping

IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board SystemsvsFTC GLBA Safeguards Rule (16 CFR Part 314)

See exactly how IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems controls map to FTC GLBA Safeguards Rule (16 CFR Part 314). Pre-computed mappings, identified gaps, and coverage analysis.

11
Controls Mapped
8
Gaps Found
37%
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 FTC GLBA Safeguards Rule (16 CFR Part 314) with 37% coverage across 7 directly mapped controls. Analysis of 19 IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems controls identifies 12 compliance gaps, primarily concentrated in IACS UR E26 Survey + Approval.

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

Control Mappings

Showing 11 of 11 mapped controls across 7 domains. Sign up to explore all 310K+ mappings across 686 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
FTC-Safeguards-9-Elements9 Safeguard Elements - Access, Inventory, Encryption, Secure-Dev, MFA, Disposal, Change-Mgmt, Monitoring, Pen-Test (16 CFR 314.4(c))

IACS UR E26 Identify - Risk + Plan(4 mappings)

IACS-UR-E26-Identify-Plan-Risk-Survey-DocumentationIACS UR E26 Identify Goal - Ship Cyber Resilience Plan + CBS Risk Assessment + Survey + Documentation4 targets
FTC-Safeguards-EffectiveDate-Small-InstitutionEffective Date, Small Institution Exemption and Sectoral Coordination (16 CFR 314.5, 314.6)
FTC-Safeguards-IR-Plan-BoardReporting-FTC-NotificationWritten Incident Response Plan + Board Reporting + FTC Breach Notification (16 CFR 314.4(h), (i), (j))
FTC-Safeguards-Risk-AssessmentWritten Risk Assessment (16 CFR 314.4(b))
FTC-Safeguards-ServiceProvider-EvaluationService Provider Oversight + Program Evaluation + Personnel Training (16 CFR 314.4(d-g))

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
FTC-Safeguards-9-Elements9 Safeguard Elements - Access, Inventory, Encryption, Secure-Dev, MFA, Disposal, Change-Mgmt, Monitoring, Pen-Test (16 CFR 314.4(c))

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
FTC-Safeguards-9-Elements9 Safeguard Elements - Access, Inventory, Encryption, Secure-Dev, MFA, Disposal, Change-Mgmt, Monitoring, Pen-Test (16 CFR 314.4(c))

IACS UR E26 Respond + Recover(1 mappings)

IACS-UR-E26-Respond-Recover-IncidentResponse-Recovery-Backup-LessonsIACS UR E26 Respond + Recover Goals - Incident Response + Communication + Recovery + Backup + Lessons Learned
FTC-Safeguards-IR-Plan-BoardReporting-FTC-NotificationWritten Incident Response Plan + Board Reporting + FTC Breach Notification (16 CFR 314.4(h), (i), (j))

IACS UR E27 User Auth(1 mappings)

IACS-UR-E27-Equipment-UserAuth-Authentication-AuthorizationIACS UR E27 - Equipment User Authentication + Authorization + Session Management + Privileged Access
FTC-Safeguards-9-Elements9 Safeguard Elements - Access, Inventory, Encryption, Secure-Dev, MFA, Disposal, Change-Mgmt, Monitoring, Pen-Test (16 CFR 314.4(c))

IACS UR E27 Logging + Forensics(2 mappings)

IACS-UR-E27-Logging-Forensics-EventCaptureIACS UR E27 - Equipment Logging + Forensic Readiness + Event Capture + Tamper Detection2 targets
FTC-Safeguards-9-Elements9 Safeguard Elements - Access, Inventory, Encryption, Secure-Dev, MFA, Disposal, Change-Mgmt, Monitoring, Pen-Test (16 CFR 314.4(c))
FTC-Safeguards-IR-Plan-BoardReporting-FTC-NotificationWritten Incident Response Plan + Board Reporting + FTC Breach Notification (16 CFR 314.4(h), (i), (j))
Coverage crosswalk

A IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems to FTC GLBA Safeguards Rule (16 CFR Part 314) crosswalk, built to order

The table above lists candidate mappings. A crosswalk answers the narrower question you are probably here for: which FTC GLBA Safeguards Rule (16 CFR Part 314) 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 FTC GLBA Safeguards Rule (16 CFR Part 314)
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.

FTC GLBA Safeguards Rule (16 CFR Part 314) 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 FTC GLBA Safeguards Rule (16 CFR Part 314) (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 37% 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 FTC GLBA Safeguards Rule (16 CFR Part 314) 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 FTC GLBA Safeguards Rule (16 CFR Part 314) comparisons

Stop Paying Consultants to Read Spreadsheets

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

$0/forever

Free

  • 686 framework browser
  • Cross-framework mappings (310K+)
  • 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 FTC GLBA Safeguards Rule (16 CFR Part 314)?

IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems has 19 controls across its framework, while FTC GLBA Safeguards Rule (16 CFR Part 314) covers 11 controls. Direct mapping analysis identifies 7 overlapping controls (37% 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 FTC GLBA Safeguards Rule (16 CFR Part 314) equivalent.

How many controls map between IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems and FTC GLBA Safeguards Rule (16 CFR Part 314)?

Of 19 total IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems controls, 7 map directly to FTC GLBA Safeguards Rule (16 CFR Part 314) controls, representing 37% coverage. The remaining 12 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 FTC GLBA Safeguards Rule (16 CFR Part 314)?

12 IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems controls have no direct equivalent in FTC GLBA Safeguards Rule (16 CFR Part 314). 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 FTC GLBA Safeguards Rule (16 CFR Part 314)?

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.