Skip to main content

A cyber security framework is a map, not a magic shield. An information security framework gives an organisation a structured way to understand risks, select safeguards and review whether they work. It helps turn disconnected security tasks into a coordinated programme, but it does not replace obligations under laws, regulations or contracts.

Choosing a framework can feel like choosing between competing maps, especially when your organisation has its own risks, customers and compliance needs. The New Zealand National Cyber Security Centre’s framework groups the work into five functions: Guide and Govern, Identify and Understand, Prevent and Protect, Detect and Contain, and Respond and Recover. This article explains how to choose a framework that fits, map its requirements to your organisation, test the controls in practice and monitor progress over time. It also clarifies how ISO/IEC 27001 and ISO/IEC 27002 work together, so you can make informed decisions rather than simply collect controls.

Key Takeaways

  • Choose a framework that fits your organisation’s risks, sector and obligations, rather than adopting controls simply because they’re familiar.
  • Understand the different roles of ISO/IEC 27001, which sets requirements for an information security management system, and ISO/IEC 27002, which provides supporting controls guidance.
  • Map framework requirements to existing safeguards, then test and monitor how well they work in practice.
  • Unisphere Solutions’ Minimum Viable Protection methodology can help assess cyber posture against risk appetite and shape a practical remediation roadmap.

What is a cyber security framework?

A cyber security framework is a structured way to identify security risks, select controls and guide improvement. In New Zealand, the NCSC framework supports public and private organisations, while government departments also operate within Protective Security Requirements.

Frameworks, Standards and Attestations

Frameworks organise security practices; standards set requirements or guidance; attestations assess whether specified criteria are met; and regulations create legal obligations. Knowing the difference helps organisations choose what addresses their actual risks and obligations, rather than treating every document as interchangeable.

The National Cyber Security Centre’s framework has five functions: Guide and Govern, Identify and Understand, Prevent and Protect, Detect and Contain, and Respond and Recover. NIST and the National Cyber Security Centre develop frameworks; ISO develops standards. PCI DSS sets payment-card requirements, while SOC 2 is an attestation based on five Trust Services Criteria.

NIST Functions and Profiles

The NIST CSF groups cyber security outcomes into functions, categories and sub-categories, while profiles describe how those outcomes fit an organisation’s needs. NIST CSF 2.0 uses six functions: Govern, Identify, Protect, Detect, Respond and Recover.

A profile can describe an organisation’s current practices or its target outcomes. Comparing the two helps define priorities and explain the security risk to decision-makers. The NIST CSF details 22 categories and more than 100 sub-categories, giving organisations a way to structure work without assuming every activity applies equally.

Control Counts and Framework Scope

Control counts vary because frameworks have different purposes, detail and scope. CIS Critical Security Controls, for example, comprise 18 prioritised actions; its first implementation group includes 56 safeguards. By contrast, the SAM for Compliance listing of ISO/IEC 27001:2022 contains 234 controls.

Those figures do not directly show which framework is stronger. A broad framework can guide governance, while a sector-specific standard or compliance requirement may prescribe narrower security controls. In New Zealand, the Health Information Security Framework provides health-sector guidance, and the NCSC framework complements an organisation’s risk management process. Match the scope to your information, obligations and operating context.

ISO/IEC 27001 certification and ISO/IEC 27002 controls guidance

ISO/IEC 27001:2022 sets requirements for an Information Security Management System, or ISMS. An organisation can seek certification against this standard to demonstrate that its management system meets the applicable requirements. ISO/IEC 27002:2022 supports that work with guidance on security controls, but it isn’t independently certifiable. Think of ISO/IEC 27001 as the management system’s blueprint and ISO/IEC 27002 as practical guidance for selecting safeguards.

Control counts describe different things, so they’re not a simple measure of strength. The SAM for Compliance listing contains 234 controls for ISO/IEC 27001:2022 and 1,249 for ISO/IEC 27002:2022. CIS Critical Security Controls take a prioritised approach, grouping safeguards into three Implementation Groups. Group 1 includes 56 safeguards described as essential cyber hygiene. These groups help organisations stage improvements according to their cybersecurity priorities and capacity.

Use a framework to identify control gaps by comparing its requirements with existing policies, systems and evidence. Record each control as in place, partly in place or not in place, then note its owner, supporting evidence and unresolved risk. This turns a broad cybersecurity framework into a practical risk management view: decision-makers can set expectations, measure progress and focus effort on gaps most relevant to resilience and incidents.

For a New Zealand perspective, CERT NZ’s Top 10 Critical Controls offers another practical reference point. Compare its recommendations with ISO and CIS measures, then map overlaps rather than creating duplicate tasks. The right combination depends on your sector, obligations and security risk. An independent advisory approach can help make those choices clearer.

Information security framework: How to choose and apply one

Choosing, mapping, testing, and monitoring frameworks

Choose a framework based on your obligations, threats and desired outcomes. Then map, test and monitor its controls as your organisation changes. Think of a framework like a checklist: it helps you check the right things, but you still need to tailor it to your business.

Mapping Security Domains

Mapping security domains means lining up similar security goals and controls across frameworks. It’s like comparing two project plans to see where they cover the same tasks, so you can avoid doing the same work twice. The National Cyber Security Centre planned to map its framework to NZISM, NIST categories and ISO 27000-series domains. Use that structure to record each requirement, its evidence, owner and remaining gap, while noting where framework versions differ.

Informative References and Mappings

Informative references show how an outcome in one framework relates to controls in another. Think of them as a cross-reference in a filing system: they help you find related work and spot what’s missing. A mapping is a guide, not proof that requirements are identical. Compare the wording, scope and evidence, then record any differences. Revisit the mapping when either framework changes version or your operating context shifts.

Comparing Frameworks

NIST CSF organises cybersecurity outcomes; ISO 27001 sets ISMS requirements; CIS Controls prioritise safeguards; NZISM addresses New Zealand government security needs. For government agencies, NZISM informs controls, and its system assurance process applies to ICT systems. System assurance is like checking a building before people move in: it helps establish whether the system meets the required security expectations. Suppliers align with relevant security expectations through their contracts and system access. Choose based on obligations and risk, not familiarity alone.

Risks of Frameworks Without Tailoring

Using an information security framework without tailoring it can direct effort towards controls that do not address your critical threats, while leaving relevant gaps unnoticed. A generic maturity score may also obscure differences in systems, information and responsibilities. Test controls against realistic scenarios, track whether they achieve their intended outcomes, and monitor changes. Review priorities when threats, systems or business needs change.

Unisphere Solutions: Cyber Security & Risk Management using the patented Minimum Viable Protection methodology

Unisphere Solutions helps organisations turn framework findings into practical cyber security priorities through its patented Minimum Viable Protection methodology. It assesses and scores an organisation’s cyber risk appetite, evaluates its cyber posture and provides a remediation roadmap aligned with that appetite.

This support is useful when a framework assessment has surfaced gaps, but leaders need a clear way to decide what to address first. Rather than treating every control as equally urgent, the methodology connects remediation planning with the organisation’s defined tolerance for cyber risk. This gives decision-makers a clearer basis for aligning security measures with business needs.

For organisations needing broader strategic direction, Virtual CIO and Executive IT Leadership can connect technology decisions with organisational priorities. The next step is to discuss your framework, current security position and desired outcomes.

Contact Unisphere Solutions

Make your next security decision count

Frameworks create value when they shape real decisions, not just policy documents. Connect each priority in your information security framework to a business owner and a clear reason for action. This gives leadership a practical way to weigh security work against operational needs and revisit priorities as the organisation changes.

Unisphere Solutions supports this work through Cyber Security & Risk Management using its patented Minimum Viable Protection methodology. Organisations can also draw on Virtual CIO and Executive IT Leadership for strategic support without a full-time role, or Artificial Intelligence and Digital Transformation advisory when technology change affects risk decisions. The focus is on aligning security priorities with the organisation’s direction.

A clear owner and business purpose behind each decision give your security programme a stronger foundation for progress.

Frequently Asked Questions

What is an information security framework?

An information security framework provides a shared operating model for decisions about protecting information. It clarifies who approves security policies, who owns safeguards and what evidence supports those decisions. For example, a business can link its access policy to role changes, so managers know when to request permission updates and staff know who authorises them.

What are the main information security frameworks used in New Zealand?

Common options include NZISM, the National Cyber Security Centre Cyber Security Framework, ISO/IEC 27001 and NIST CSF. Health-sector guidance comes in versions tailored to different organisations, like maps for different journeys: HISO 10029.1:2023 is for hospitals, HISO 10029.2:2023 for micro to small organisations, HISO 10029.3:2023 for medium to large organisations, and HISO 10029.4:2025 for health-sector suppliers.

How do you choose an information security framework for a New Zealand business?

Start by deciding what assurance the business needs to demonstrate. A procurement process may call for recognised certification, while internal governance may need a practical way to direct improvements. Compare each option’s evidence expectations, implementation effort and ability to support that outcome. This keeps the choice tied to a business decision, not just the framework’s name.

What are the steps to implement an information security framework?

Once leadership approves the approach, translate relevant requirements into policies and work instructions people can follow. Assign an accountable owner to each procedure, then build it into existing workflows, such as staff onboarding, supplier approval or system changes. Explain responsibilities to affected teams and retain evidence where they already work. This makes the framework part of normal operations, not a separate manual.

What New Zealand privacy and cybersecurity laws should an information security framework address?

A framework should account for applicable legal, regulatory and contractual obligations. The material links information and ICT systems management to the Public Records Act 2005 and identifies the Health Information Privacy Code 2020 as covering privacy expectations for health information in New Zealand.