ITU-T X.805 - Security Architecture for End-to-End CommunicationsvsBS 65000:2014 - Guidance on Organizational Resilience
See exactly how ITU-T X.805 - Security Architecture for End-to-End Communications controls map to BS 65000:2014 - Guidance on Organizational Resilience. Pre-computed mappings, identified gaps, and coverage analysis.
According to the TheArtOfService Compliance Knowledge Graph:
ITU-T X.805 - Security Architecture for End-to-End Communications maps to BS 65000:2014 - Guidance on Organizational Resilience with 8% coverage across 1 directly mapped controls. Analysis of 13 ITU-T X.805 - Security Architecture for End-to-End Communications controls identifies 12 compliance gaps — primarily concentrated in X.805 Threats + Application.
Source: TheArtOfService Knowledge Graph | 13 controls analysed | 706 frameworks | 324K+ cross-framework mappings
Control Mappings
Showing 1 of 1 mapped controls across 1 domains. Sign up to explore all 324K+ mappings across 706 frameworks.
X.805 Security Dimension 7 - Availability(1 mappings)
Related Comparisons
Other ITU-T X.805 - Security Architecture for End-to-End Communications comparisons
Other BS 65000:2014 - Guidance on Organizational Resilience comparisons
Stop Paying Consultants to Read Spreadsheets
AI-powered compliance intelligence across 706 frameworks — at a fraction of consulting costs.
Free
- ✓ 706 framework browser
- ✓ Cross-framework mappings (324K+)
- ✓ 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 ITU-T X.805 - Security Architecture for End-to-End Communications and BS 65000:2014 - Guidance on Organizational Resilience?
ITU-T X.805 - Security Architecture for End-to-End Communications has 13 controls across its framework, while BS 65000:2014 - Guidance on Organizational Resilience covers 26 controls. Direct mapping analysis identifies 1 overlapping controls (8% coverage). The frameworks diverge most significantly in X.805 Threats + Application, where 1 ITU-T X.805 - Security Architecture for End-to-End Communications controls have no direct BS 65000:2014 - Guidance on Organizational Resilience equivalent.
How many controls map between ITU-T X.805 - Security Architecture for End-to-End Communications and BS 65000:2014 - Guidance on Organizational Resilience?
Of 13 total ITU-T X.805 - Security Architecture for End-to-End Communications controls, 1 map directly to BS 65000:2014 - Guidance on Organizational Resilience controls — representing 8% 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 ITU-T X.805 - Security Architecture for End-to-End Communications to BS 65000:2014 - Guidance on Organizational Resilience?
12 ITU-T X.805 - Security Architecture for End-to-End Communications controls have no direct equivalent in BS 65000:2014 - Guidance on Organizational Resilience. The highest concentration of gaps is in X.805 Threats + Application 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 ITU-T X.805 - Security Architecture for End-to-End Communications and BS 65000:2014 - Guidance on Organizational Resilience?
The domain with the highest gap count is X.805 Threats + Application (1 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.