- ClassificationCategoryData Protection & PrivacyDomainSupply Chain SecurityFramework FamilyOther
- Regulatory ContextTypeFrameworkLegal InstrumentGuidanceSectorHealthcare SectorIndustryHealthcare & Life Sciences
- Region / PublisherRegionAsia-PacificRegion DetailNew ZealandPublisherHealth New Zealand | Te Whatu Ora (HISO)
- VersioningVersionHISO 10029.4:2025 (replaces HISO 10029.4:2023)Effective DateApril 2025Issue DateApril 2025
- AdoptionAdoption ModelIndustry RequirementImplementation ComplexityHigh
- Official ReferenceOpen Link in New TabSource
License included / downloadable: Yes
HISO 10029.4:2025 is published free by Health New Zealand | Te Whatu Ora under the Creative Commons Attribution 4.0 International license, and the platform links to the official guidance, Helper Document and FAQ.
Framework text is licensed by its publisher and is included only where stated above.
- HISO 10029.4:2025 is Health New Zealand's cyber security guidance for suppliers to the New Zealand health sector.
- Released April 2025, it replaces HISO 10029.4:2023 and is the fourth companion to the core framework, HISO 10029:2022.
- It lists 68 numbered requirements, HSUP01 to HSUP68, across the five functional processes, each with implementation guidance.
- The guidance has no legislative mandate, but Health New Zealand expects its third parties to align and conform with it.
- SmartSuite Compliance Management tracks HSUP01 to HSUP68 as requirements with owners, status, and evidence.
Overview
HISO 10029.4:2025, the Health Information Security Framework Guidance for Suppliers, is Health New Zealand | Te Whatu Ora's cyber security guidance for suppliers to the New Zealand health sector: service providers of on-premises or cloud services, such as software resellers, medical device resellers or implementors, internet service providers, outsourced service providers and software as a service providers. It was released in April 2025 and is the edition Health New Zealand now publishes; an earlier edition, HISO 10029.4:2023, preceded it.
It is the fourth companion to the core framework, HISO 10029:2022. Section 2 lists 68 numbered requirements, HSUP01 to HSUP68, grouped under the five functional processes: 17 under Plan, 13 under Identify, 27 under Protect, 7 under Detect and 4 under Respond. Section 3 gives each one implementation guidance. The guidance is a set of recommendations, and section 1 says there can be other ways of meeting a requirement. The supplier FAQ states that HISF has no legislative mandate, and also that Health New Zealand expects its third parties to align and conform with it.
A supplier works in three steps (section 1): understand the core framework, read this guidance and its requirements, then use the HISF tools, templates and approved materials to meet them. Health New Zealand also publishes a Helper Document that maps each HSUP requirement to Secure Controls Framework controls, and a supplier FAQ with answers on privacy, data location, alternative frameworks and the agency's cyber risk assurance process.
Why does it matter?
Health New Zealand says it will assess the confidentiality, integrity and availability of data, systems and services using HISF, and that a third party's adoption, alignment and maturity will be the principal measures of its cyber posture (supplier FAQ, question 13). For a supplier, HSUP01 to HSUP68 become the questions customers ask. They run from policies and personnel screening to cloud, logging and incident handling, and they include a duty to notify customers of related incidents on agreed timelines (HSUP65).
Key benefits include:
- One requirement set for suppliers
The 68 HSUP requirements in section 2 give a supplier one numbered list to work from, grouped by the five HISF functional processes.
- A supplier is also an acquirer
HSUP67 requires suppliers to evaluate their own suppliers before and after onboarding, and HSUP68 requires security requirements in the agreements with them.
- Intervals to plan around
The guidance sets annual tests of the incident response plan and of business continuity and disaster recovery plans, and re-screening of privileged users every year.
- Evidence for a conformance claim
Controls come with an implementation guide, so a supplier can show how each requirement is met rather than assert it.
- Crosswalk to what you already hold
The Helper Document maps HSUP requirements to Secure Controls Framework controls, so ISO 27001 or NIST CSF 2.0 work can be reused (FAQ question 8).
How does it work?
Section 3 is a table with four columns: functional process, control area, requirement and guidance. Control areas run from information security policy, human resource security and asset lifecycle security through incident management, business continuity, cryptography, identity and access management, physical security, cloud security and system development to risk management and operations security. Operations security covers backups, change, patch and vulnerability, configuration and capacity management, endpoint security, data leakage prevention, and logging and monitoring.
The guidance sets concrete intervals. Personnel verification repeats at least every three years, and annually for privileged users. The incident response plan, business continuity plan and disaster recovery plan are each tested at least annually, with a failover and failback exercise annually for critical services. For patching, it says to define timeframes for emergency patching, typically within 48 hours of release. Backups are tested for restoration (HSUP49).
Incident handling is specific to the health sector. HSUP65 requires incidents and near misses to reach senior management or the Board through a nominated Information Security Officer, and customer-related incidents to be notified to the customer on agreed timelines. The guidance adds that incidents affecting health sector customers are to be reported to Te Whatu Ora, where applicable, to the NCSC, CERT NZ and the Office of the Privacy Commissioner within 24 hours of detection.
Key Elements
- Supplier definition (section 1)
A service provider of on-premises or cloud services, including software and medical device resellers or implementors, internet service providers, outsourced providers and software as a service providers.
- 68 requirements (section 2)
HSUP01 to HSUP68 across Plan, Identify, Protect, Detect and Respond, including HSUP10 on Board accountability and HSUP38 on reporting cyber metrics to the Board.
- Cloud requirements
HSUP13, HSUP26 and HSUP43 to HSUP45 cover planned maintenance, cloud assurance, a cloud-ready architecture, secure APIs and protection in multi-tenant environments.
- Incident management
HSUP07, HSUP21, HSUP65 and HSUP66 cover the process, roles, reporting to management and customers, and protection of evidence.
- Supplier relationships
HSUP67 and HSUP68 cover evaluating sub-suppliers and putting security requirements in their agreements.
- Helper Document and FAQ
The Helper Document maps each HSUP requirement to Secure Controls Framework controls and resources, and the FAQ explains Health New Zealand's expectations of third parties.
What does it cover?
Section 1 defines suppliers as service providers of on-premises or cloud services to the health sector. Health New Zealand's cyber hub extends the guidance to their sub-contractors, and its supplier FAQ is aimed at suppliers who supply services or products to Health New Zealand. Hospitals, micro to small organizations and medium to large organizations follow the other segment guidance documents, not this one. The guidance covers security. Privacy is a separate set of requirements in the FAQ, found in the Privacy Act 2020 and the health privacy code.
What are its objectives?
Section 1 states the purpose of the guidance, and the surrounding documents show what it is meant to achieve for suppliers.
Give suppliers cyber security guidance with the detailed control implementation for every HSUP requirement.
Keep suppliers working from the core framework, HISO 10029:2022, so that segments, building blocks and functional processes are applied consistently.
Link each requirement to national and international standards, and to the Secure Controls Framework crosswalk for reuse of existing certifications and reports.
Make conformance assessable through a self-audit against the HSUP requirements.
Give Health New Zealand a consistent basis for third-party cyber risk assurance.
Framework in Context
The supplier guidance sits under the core framework, HISO 10029:2022, which explains the framework's obligations, segments and maturity scale; this page covers only the supplier requirements. The FAQ places HISF beside the Privacy Act 2020, including information privacy principle 5 on security safeguards, and the Privacy Act 2020 breach duty to notify the Privacy Commissioner as soon as practicable when a breach is likely to cause serious harm. It cites the Health (Retention of Health Information) Regulations 1996 for a ten-year retention period and says offshore storage of health information must meet New Zealand privacy law.
Common Framework Mappings
HISF requirements are mapped to the Secure Controls Framework, a meta-framework of more than 1200 controls, and Health New Zealand says NIST CSF 2.0 and ISO 27001 are mapped in it as well. Organizations use these mappings, and the frameworks below, to reuse existing evidence.
Mapped frameworks include:
CIS Controls v8.1
GDPR
HIPAA
ISO 27001:2022
ISO 27002:2022
ISO 27701
NIST CSF 2.0
SOC 2
How SmartSuite Supports the HISF supplier guidance
SmartSuite provides the system for managing controls, evidence, mappings, assessments, and reporting.
Track HSUP01 to HSUP68 in Compliance Management as requirements with owners, status and evidence, and use Third Party Risk Management for your own sub-suppliers, Operational Resilience & Business Continuity for the annual recovery tests and Cyber & IT Risk for vulnerabilities and patching.
HSUP Requirement Library
Load HSUP01 to HSUP68 under Plan, Identify, Protect, Detect and Respond with an owner, implementation status and linked evidence for each.
Crosswalk Records
Record the Secure Controls Framework control, ISO 27001 control or NIST CSF 2.0 outcome behind each requirement, so gaps are visible before a customer asks.
Annual Test Calendar
Schedule the incident response test, business continuity and disaster recovery tests, failover and failback exercise, and yearly privileged-user checks, and attach the results.
Sub-supplier Assurance
Evaluate your own suppliers before and after onboarding and track the contract clauses HSUP67 and HSUP68 call for in Third Party Risk Management.
Customer Incident Log
Log each incident with detection time, customer notice and the 24-hour reports the guidance describes, with the evidence preserved under HSUP66.
Vulnerability and Patch Tracking
Track identified vulnerabilities and patch status against the timeframes you set for emergency patching in Cyber & IT Risk.
Related frameworks

CIS Controls v8.1 is a prioritized set of 18 Controls and 153 Safeguards, in three Implementation Groups, with a new Govern function.

ISO/IEC 27001:2022 specifies requirements for an information security management system: Clauses 4 to 10, risk treatment, the Statement of Applicability and 93 Annex A controls.

ISO/IEC 27002:2022 is the reference set of 93 information security controls in four themes, with attributes and implementation guidance, that supports an ISO/IEC 27001 ISMS.

ISO/IEC 27701:2025 specifies requirements for a stand-alone privacy information management system (PIMS) for PII controllers and processors, replacing the 2019 edition.
Frequently Asked Questions For New Zealand HISF Suppliers 2023 (Health Information Security Framework for Suppliers)
HISO 10029.4:2025 is the Health Information Security Framework Guidance for Suppliers, released by Health New Zealand | Te Whatu Ora in April 2025. Section 1 defines suppliers as service providers of on-premises or cloud services to the health sector, such as software resellers, medical device resellers or implementors, internet service providers and software as a service providers. Health New Zealand's cyber hub extends it to their sub-contractors.
No law requires it, and the FAQ says so. In practice Health New Zealand expects its third parties to conform to HISF, and its FAQ says their adoption, alignment and maturity will be the principal metrics for judging cyber posture. Section 1 adds that the guidance is a set of recommendations and other ways of implementing a control are possible.
Section 2 lists 68 requirements numbered HSUP01 to HSUP68. They fall under the five functional processes: 17 under Plan, 13 under Identify, 27 under Protect, 7 under Detect and 4 under Respond. Section 3 sets out each requirement beside implementation guidance, grouped by control area from information security policy to logging and monitoring.
HSUP65 requires customer-related incidents to be notified to the customer on agreed timelines. The incident management guidance adds that incidents affecting health sector customers are to be reported to Te Whatu Ora, where applicable, to the NCSC, CERT NZ and the Office of the Privacy Commissioner within 24 hours of detection. Separately, the Privacy Act 2020 requires notice to the Privacy Commissioner as soon as practicable when a breach is likely to cause serious harm.
Yes, in part. HISF requirements are mapped to the Secure Controls Framework, which also maps ISO 27001 and NIST CSF 2.0, so a supplier can download the crosswalk, select the controls for the framework it holds and find the gaps against HISF (FAQ question 8). The Helper Document sets the HSUP requirements beside the SCF controls. Independent reports such as ISO 27001 or SOC 2 Type II also appear in the guidance as evidence a supplier can request from its own providers.

Put this framework to work in SmartSuite
Manage controls, risks, evidence, and audits in one platform designed for modern governance, risk, and compliance.


