Cross-Framework Mapping

Azure Security BenchmarkvsILO Declaration on Fundamental Principles and Rights at Work (Core Conventions)

See exactly how Azure Security Benchmark controls map to ILO Declaration on Fundamental Principles and Rights at Work (Core Conventions). Pre-computed mappings, identified gaps, and coverage analysis.

1
Controls Mapped
53
Gaps Found
2%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

Azure Security Benchmark maps to ILO Declaration on Fundamental Principles and Rights at Work (Core Conventions) with 2% coverage across 1 directly mapped controls. Analysis of 54 Azure Security Benchmark controls identifies 53 compliance gaps — primarily concentrated in Identity Management.

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

Control Mappings

Showing 1 of 1 mapped controls across 1 domains. Sign up to explore all 332K+ mappings across 718 frameworks.

Azure Security Benchmark: Identity & Access in Cloud(1 mappings)

ASB-08Privileged access in cloud environments
ILO-FPRW-Cat1-FOA-CollectiveBargaining-C87-C98ILO Fundamental Category 1 - Freedom of Association (C87) + Effective Recognition of Right to Collective Bargaining (C98) + Trade Unions

Related Comparisons

Other Azure Security Benchmark comparisons

Other ILO Declaration on Fundamental Principles and Rights at Work (Core Conventions) comparisons

Stop Paying Consultants to Read Spreadsheets

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

$0/forever

Free

  • 718 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 →

What are the key differences between Azure Security Benchmark and ILO Declaration on Fundamental Principles and Rights at Work (Core Conventions)?

Azure Security Benchmark has 54 controls across its framework, while ILO Declaration on Fundamental Principles and Rights at Work (Core Conventions) covers 8 controls. Direct mapping analysis identifies 1 overlapping controls (2% coverage). The frameworks diverge most significantly in Identity Management, where 5 Azure Security Benchmark controls have no direct ILO Declaration on Fundamental Principles and Rights at Work (Core Conventions) equivalent.

How many controls map between Azure Security Benchmark and ILO Declaration on Fundamental Principles and Rights at Work (Core Conventions)?

Of 54 total Azure Security Benchmark controls, 1 map directly to ILO Declaration on Fundamental Principles and Rights at Work (Core Conventions) controls — representing 2% coverage. The remaining 53 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping Azure Security Benchmark to ILO Declaration on Fundamental Principles and Rights at Work (Core Conventions)?

53 Azure Security Benchmark controls have no direct equivalent in ILO Declaration on Fundamental Principles and Rights at Work (Core Conventions). The highest concentration of gaps is in Identity Management 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 Azure Security Benchmark and ILO Declaration on Fundamental Principles and Rights at Work (Core Conventions)?

The domain with the highest gap count is Identity Management (5 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.