TheArtOfService
Cross-Framework Mapping

Azure Security BenchmarkvsNew Zealand Information Security Manual (NZISM)

See exactly how Azure Security Benchmark controls map to New Zealand Information Security Manual (NZISM). Pre-computed mappings, identified gaps, and coverage analysis.

10
Controls Mapped
44
Gaps Found
17%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

Azure Security Benchmark maps to New Zealand Information Security Manual (NZISM) with 17% coverage across 9 directly mapped controls. Analysis of 54 Azure Security Benchmark controls identifies 45 compliance gaps — primarily concentrated in Identity Management.

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

Control Mappings

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

Azure Security Benchmark: Cloud Governance(5 mappings)

ASB-02Cloud security policy and strategy
→NZISM-3Personnel Security, Physical Security, and Cryptography
ASB-03Cloud risk assessment2 targets
→NZISM-1NZISM Governance, Documentation, and Classification System
→NZISM-3Personnel Security, Physical Security, and Cryptography
ASB-04Regulatory compliance for cloud services
→NZISM-2Certification and Accreditation (C&A) for Government Systems
ASB-05Cloud security roles and responsibilities
→NZISM-3Personnel Security, Physical Security, and Cryptography

Azure Security Benchmark: Data Protection in Cloud(1 mappings)

ASB-12Encryption of cloud-stored data
→NZISM-3Personnel Security, Physical Security, and Cryptography

Azure Security Benchmark: Cloud Infrastructure Security(2 mappings)

ASB-16Virtual network segmentation
→NZISM-5Network Security, System Hardening, and Application Security
ASB-17Container and serverless security
→NZISM-3Personnel Security, Physical Security, and Cryptography

Azure Security Benchmark: Cloud Operations & Monitoring(2 mappings)

ASB-21Cloud security monitoring and logging
→NZISM-5Network Security, System Hardening, and Application Security
ASB-23Cloud vulnerability management
→NZISM-5Network Security, System Hardening, and Application Security

Related Comparisons

Other Azure Security Benchmark comparisons

Azure Security Benchmark vs NIST SP 800-14620 mappingsAzure Security Benchmark vs NIST SP 800-14520 mappingsAzure Security Benchmark vs NIST SP 800-14420 mappingsAzure Security Benchmark vs MTCS (Singapore)20 mappingsAzure Security Benchmark vs ISMAP (Japan)20 mappingsAzure Security Benchmark vs ISO 2701720 mappingsAzure Security Benchmark vs NIST SP 800-19020 mappingsAzure Security Benchmark vs ISO 2701820 mappings

Other New Zealand Information Security Manual (NZISM) comparisons

OWASP DevSecOps Maturity Model (DSOMM) vs New Zealand Information Security Manual (NZISM)4 mappingsNIST SP 800-146 vs New Zealand Information Security Manual (NZISM)4 mappingsNIST SP 800-145 vs New Zealand Information Security Manual (NZISM)4 mappingsNIST SP 800-144 vs New Zealand Information Security Manual (NZISM)4 mappingsISO 27018 vs New Zealand Information Security Manual (NZISM)4 mappingsAWS Well-Architected Security Pillar vs New Zealand Information Security Manual (NZISM)4 mappingsISO 27017 vs New Zealand Information Security Manual (NZISM)4 mappingsNIST SP 800-190 vs New Zealand Information Security Manual (NZISM)4 mappings

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 →

Popular framework comparisons

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

What are the key differences between Azure Security Benchmark and New Zealand Information Security Manual (NZISM)?

Azure Security Benchmark has 54 controls across its framework, while New Zealand Information Security Manual (NZISM) covers 8 controls. Direct mapping analysis identifies 9 overlapping controls (17% coverage). The frameworks diverge most significantly in Identity Management, where 5 Azure Security Benchmark controls have no direct New Zealand Information Security Manual (NZISM) equivalent.

How many controls map between Azure Security Benchmark and New Zealand Information Security Manual (NZISM)?

Of 54 total Azure Security Benchmark controls, 9 map directly to New Zealand Information Security Manual (NZISM) controls — representing 17% coverage. The remaining 45 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 New Zealand Information Security Manual (NZISM)?

45 Azure Security Benchmark controls have no direct equivalent in New Zealand Information Security Manual (NZISM). 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 New Zealand Information Security Manual (NZISM)?

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.

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.