Cross-Framework Mapping

New Zealand Information Security Manual (NZISM)vsNIST SP 800-146

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

7
Controls Mapped
1
Gaps Found
50%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

New Zealand Information Security Manual (NZISM) maps to NIST SP 800-146 with 50% coverage across 4 directly mapped controls. Analysis of 8 New Zealand Information Security Manual (NZISM) controls identifies 4 compliance gaps — primarily concentrated in Risk and Vulnerability.

Source: TheArtOfService Knowledge Graph | 8 controls analysed | 701 frameworks | 337K+ cross-framework mappings

Control Mappings

Showing 7 of 7 mapped controls across 4 domains. Sign up to explore all 337K+ mappings across 701 frameworks.

Governance and Classification(1 mappings)

NZISM-1NZISM Governance, Documentation, and Classification System
NISTSP146-1Cloud Adoption Strategy, Workload Suitability, and Decision Framework

Certification and Accreditation(1 mappings)

NZISM-2Certification and Accreditation (C&A) for Government Systems
NISTSP146-6Cloud Security and Privacy Recommendations

Personnel + Physical + Crypto(3 mappings)

NZISM-3Personnel Security, Physical Security, and Cryptography3 targets
NISTSP146-1Cloud Adoption Strategy, Workload Suitability, and Decision Framework
NISTSP146-4IaaS Operational Recommendations and Workload Hardening
NISTSP146-6Cloud Security and Privacy Recommendations

Technical Security Controls(2 mappings)

NZISM-5Network Security, System Hardening, and Application Security2 targets
NISTSP146-4IaaS Operational Recommendations and Workload Hardening
NISTSP146-6Cloud Security and Privacy Recommendations

Stop Paying Consultants to Read Spreadsheets

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

$0/forever

Free

  • 701 framework browser
  • Cross-framework mappings (337K+)
  • 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 New Zealand Information Security Manual (NZISM) and NIST SP 800-146?

New Zealand Information Security Manual (NZISM) has 8 controls across its framework, while NIST SP 800-146 covers 8 controls. Direct mapping analysis identifies 4 overlapping controls (50% coverage). The frameworks diverge most significantly in Risk and Vulnerability, where 1 New Zealand Information Security Manual (NZISM) controls have no direct NIST SP 800-146 equivalent.

How many controls map between New Zealand Information Security Manual (NZISM) and NIST SP 800-146?

Of 8 total New Zealand Information Security Manual (NZISM) controls, 4 map directly to NIST SP 800-146 controls — representing 50% coverage. The remaining 4 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping New Zealand Information Security Manual (NZISM) to NIST SP 800-146?

4 New Zealand Information Security Manual (NZISM) controls have no direct equivalent in NIST SP 800-146. The highest concentration of gaps is in Risk and Vulnerability 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 New Zealand Information Security Manual (NZISM) and NIST SP 800-146?

The domain with the highest gap count is Risk and Vulnerability (1 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.