Cross-Framework Mapping

ISO/IEC 30111:2019vsNew Zealand Information Security Manual (NZISM)

See exactly how ISO/IEC 30111:2019 controls map to New Zealand Information Security Manual (NZISM). Pre-computed mappings, identified gaps, and coverage analysis.

6
Controls Mapped
28
Gaps Found
15%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

ISO/IEC 30111:2019 maps to New Zealand Information Security Manual (NZISM) with 15% coverage across 6 directly mapped controls. Analysis of 34 ISO/IEC 30111:2019 controls identifies 33 compliance gaps — primarily concentrated in Clause 6: Vulnerability Handling Process.

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

Control Mappings

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

Clause 1-4: Introduction(2 mappings)

30111-1Scope
NZISM-5Network Security, System Hardening, and Application Security
30111-3Terms and definitions
NZISM-5Network Security, System Hardening, and Application Security

Remediation Planning(1 mappings)

30111-6.5Remediation Strategy Selection
NZISM-5Network Security, System Hardening, and Application Security

Clause 6: Vulnerability Handling Process(1 mappings)

30111-6.5Remediation Strategy Selection
NZISM-5Network Security, System Hardening, and Application Security

Clause 7: Vendor Process Management(1 mappings)

30111-7.3Quality assurance of remediation
NZISM-5Network Security, System Hardening, and Application Security

Clause 8: Post-Release Activities(1 mappings)

30111-8.1Post-release monitoring
NZISM-5Network Security, System Hardening, and Application Security

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 ISO/IEC 30111:2019 and New Zealand Information Security Manual (NZISM)?

ISO/IEC 30111:2019 has 34 controls across its framework, while New Zealand Information Security Manual (NZISM) covers 8 controls. Direct mapping analysis identifies 6 overlapping controls (15% coverage). The frameworks diverge most significantly in Clause 6: Vulnerability Handling Process, where 4 ISO/IEC 30111:2019 controls have no direct New Zealand Information Security Manual (NZISM) equivalent.

How many controls map between ISO/IEC 30111:2019 and New Zealand Information Security Manual (NZISM)?

Of 34 total ISO/IEC 30111:2019 controls, 6 map directly to New Zealand Information Security Manual (NZISM) controls — representing 15% coverage. The remaining 33 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping ISO/IEC 30111:2019 to New Zealand Information Security Manual (NZISM)?

33 ISO/IEC 30111:2019 controls have no direct equivalent in New Zealand Information Security Manual (NZISM). The highest concentration of gaps is in Clause 6: Vulnerability Handling Process with 4 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 ISO/IEC 30111:2019 and New Zealand Information Security Manual (NZISM)?

The domain with the highest gap count is Clause 6: Vulnerability Handling Process (4 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.