21 CFR Part 58 — Good Laboratory Practice (GLP)vsIACS Unified Requirements E26/E27 — Cyber Resilience of Ships and On-Board Systems
See exactly how 21 CFR Part 58 — Good Laboratory Practice (GLP) controls map to IACS Unified Requirements E26/E27 — Cyber Resilience of Ships and On-Board Systems. Pre-computed mappings, identified gaps, and coverage analysis.
According to the TheArtOfService Compliance Knowledge Graph:
21 CFR Part 58 — Good Laboratory Practice (GLP) maps to IACS Unified Requirements E26/E27 — Cyber Resilience of Ships and On-Board Systems with 3% coverage across 1 directly mapped controls. Analysis of 31 21 CFR Part 58 — Good Laboratory Practice (GLP) controls identifies 30 compliance gaps — primarily concentrated in Test Articles and Protocol (Subparts F & G).
Source: TheArtOfService Knowledge Graph | 31 controls analysed | 693 frameworks | 819K+ cross-framework mappings
Control Mappings
Showing 1 of 1 mapped controls across 1 domains. Sign up to explore all 819K+ mappings across 693 frameworks.
Facilities (Subpart C)(1 mappings)
Related Comparisons
Other 21 CFR Part 58 — Good Laboratory Practice (GLP) comparisons
Other IACS Unified Requirements E26/E27 — Cyber Resilience of Ships and On-Board Systems comparisons
Stop Paying Consultants to Read Spreadsheets
AI-powered compliance intelligence across 693 frameworks — at a fraction of consulting costs.
Free
- ✓ 693 framework browser
- ✓ Cross-framework mappings (819K+)
- ✓ 824 compliance assessments
- ✓ 3 AI queries & searches per day
Professional
- ✓ Unlimited AI Compliance Advisory
- ✓ Unlimited full-text search
- ✓ Framework self-assessment
- ✓ PDF, Excel & CSV exports
What are the key differences between 21 CFR Part 58 — Good Laboratory Practice (GLP) and IACS Unified Requirements E26/E27 — Cyber Resilience of Ships and On-Board Systems?
21 CFR Part 58 — Good Laboratory Practice (GLP) has 31 controls across its framework, while IACS Unified Requirements E26/E27 — Cyber Resilience of Ships and On-Board Systems covers 22 controls. Direct mapping analysis identifies 1 overlapping controls (3% coverage). The frameworks diverge most significantly in Test Articles and Protocol (Subparts F & G), where 5 21 CFR Part 58 — Good Laboratory Practice (GLP) controls have no direct IACS Unified Requirements E26/E27 — Cyber Resilience of Ships and On-Board Systems equivalent.
How many controls map between 21 CFR Part 58 — Good Laboratory Practice (GLP) and IACS Unified Requirements E26/E27 — Cyber Resilience of Ships and On-Board Systems?
Of 31 total 21 CFR Part 58 — Good Laboratory Practice (GLP) controls, 1 map directly to IACS Unified Requirements E26/E27 — Cyber Resilience of Ships and On-Board Systems controls — representing 3% coverage. The remaining 30 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.
What are the compliance gaps when mapping 21 CFR Part 58 — Good Laboratory Practice (GLP) to IACS Unified Requirements E26/E27 — Cyber Resilience of Ships and On-Board Systems?
30 21 CFR Part 58 — Good Laboratory Practice (GLP) controls have no direct equivalent in IACS Unified Requirements E26/E27 — Cyber Resilience of Ships and On-Board Systems. The highest concentration of gaps is in Test Articles and Protocol (Subparts F & G) with 5 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 21 CFR Part 58 — Good Laboratory Practice (GLP) and IACS Unified Requirements E26/E27 — Cyber Resilience of Ships and On-Board Systems?
The domain with the highest gap count is Test Articles and Protocol (Subparts F & G) (5 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.
Related Resources
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.