For architects, security leads and Salesforce partners working with New Zealand health information. It goes one level deeper than Mapping Salesforce Security to NZISM, the NZ Privacy Act and ISO 27001, which treats HISO 10029 as one framework among several.
TL;DR
- HISO 10029 is the Health Information Security Framework (HISF), published by Health New Zealand | Te Whatu Ora. The core is HISO 10029:2022, and suppliers, including SaaS providers, follow the 2025 supplier part, HISO 10029.4:2025.
- It has no legislative mandate, and it still has teeth. Health NZ expects suppliers to align with it and uses HISF maturity as its principal measure of a third party's cyber posture. The Privacy Commissioner pointed to HISF when describing what Rule 5 of the Health Information Privacy Code is likely to require.
- The requirements are short; the detail is guidance. MFA, TLS, SIEM forwarding and access review cadences all live in the guidance under each requirement, not in the requirement itself.
- Salesforce certifies the platform; your org configuration is yours. The framework says so itself for SaaS. Identity, access reviews and logging are where Salesforce orgs often fall short.
- It does not require New Zealand data residency. Offshore storage is a risk to assess, not a prohibition.
What You'll Learn
- What HISO 10029 consists of in 2026, and which part applies to you
- Why "no legislative mandate" does not mean optional
- How each HISF control area maps to Salesforce settings and evidence
- Where Salesforce's certifications stop and your org configuration starts
- How to approach Health NZ's supplier self-assessment workbook for a Salesforce org
The Problem
A Health NZ contract, a PHO agreement or a procurement questionnaire asks whether your Salesforce solution aligns with HISO 10029. You open the framework expecting a checklist of settings and find something else: a core document about principles, four segment guides, requirement statements one sentence long, and a self-assessment workbook in Excel.
Search does not help much. "HISO 10029 Salesforce" returns generic HIPAA posts. Many links to the framework still point at tewhatuora.govt.nz addresses that now land on the Health NZ homepage. And nothing translates "the complete lifecycle of the account(s) ... is managed" into what to check in Setup.
Common Questions This Article Answers:
- Does HISO 10029 apply to a Salesforce partner or ISV?
- Is HISO 10029 mandatory?
- Which Salesforce settings provide evidence for each HISF requirement?
- Does HISO 10029 require health data to stay in New Zealand?
Quick Answer
Find your segment first. A medium to large health organisation that is not a hospital (typically more than 25 staff or a population over 10,000) uses HISO 10029.3 (requirements HML01 to HML75). A supplier to the health sector, which explicitly includes SaaS providers, uses HISO 10029.4:2025 (HSUP01 to HSUP68). Each requirement is scored on a maturity scale from 1 (None) to 5 (Embedded); there are no baseline or enhanced tiers. For Salesforce, Salesforce's certifications cover the platform, but the framework assigns user accounts and identities to the SaaS customer. So your evidence comes from the org: MFA and SSO configuration, permission sets and a role-based access matrix, quarterly user and monthly privileged access reviews, Shield Platform Encryption or a documented key decision, and logs exported to a SIEM, because native Salesforce logs age out and are not a system of record. Data can sit in Salesforce's Australian region or elsewhere offshore, provided the risk is assessed and written down.
What HISO 10029 Is in 2026
The framework is a family of documents, and the edition matters.
| Document | Covers | Requirement IDs |
|---|---|---|
| HISO 10029:2022 | The core framework: obligations, principles, maturity model | None (it points to the segment guides) |
| HISO 10029.1:2023 | Public and private hospitals | Segment-specific |
| HISO 10029.2:2023 | Micro to small organisations (typically up to 25 staff) | Segment-specific |
| HISO 10029.3:2023 | Medium to large organisations | HML01 to HML75 |
| HISO 10029.4:2025 | Health sector suppliers and their sub-contractors | HSUP01 to HSUP68 |
Three things about the design surprise people who expect an ISO-style standard.
It is built on the NIST Cybersecurity Framework. The core says it moved away from "the ISO-centric model used previously". Its five functions are Plan, Identify, Protect, Detect and Respond, and it maps to other catalogues (NZISM, CIS, CSA's Cloud Controls Matrix, ISO 27002 and others) rather than copying any of them.
It is not pass or fail. The core calls itself "an approach to cyber security rather than a 'yes' and 'no' standard". Each requirement gets a maturity score from 1 (None) to 5 (Embedded), and I could not find a published target level that suppliers must reach.
Privacy is out of scope. The Health Information Privacy Code 2020 covers privacy; HISF covers security of the information.
If you work from an older copy, check the supplier part. HISO 10029.4:2025, released in April 2025, is now the only supplier edition Health NZ lists, in place of the 2023 supplier guide, and a lot of the material online still cites the old one.
Does It Apply to You?
The core says its obligations and principles "apply to all health organisations within New Zealand". The supplier part defines a supplier as a provider of on-premises or cloud services, and names software as a service providers in its examples. A Salesforce implementation partner, an ISV with health customers, or a managed service provider running an org for a health organisation falls in the supplier segment. Whether Salesforce itself is assessed against HSUP depends on the contracting chain; Health NZ publishes nothing specific on that.
Is it mandatory? Health NZ's supplier FAQ answers directly: "HISF does not have a legislative mandate". The same FAQ then says Health NZ "expects third parties to align and conform with the HISF", and that HISF maturity will be the principal metric for evaluating the cyber posture of all third parties. When it explains why cyber security matters, the FAQ lists the Privacy Act's information privacy principle 5, commercial agreements such as the PHO Service Agreement and data sharing and remote access agreements, and a professional duty of care that it describes as aligning with industry standards such as HISF. In practice the framework reaches you through procurement and contracts, so check whether yours reference it.
The regulator has added weight. In the Manage My Health inquiry, published in May 2026, the Privacy Commissioner found breaches of Rule 5 of the Health Information Privacy Code, the rule requiring reasonable security safeguards. The Commissioner's release described NCSC and HISF standards as useful indications of what is likely to be required under Rule 5, and the findings noted that multifactor authentication was available but not required for all users. In practice, a health organisation that cannot show reasonable alignment with HISF will find it hard to argue its safeguards were reasonable.
Requirements Versus Guidance
This distinction decides how you answer questionnaires. The requirement statements are short and technology-neutral. HSUP34 reads, in full: "User accounts are authenticated and circumventing the authentication process is prevented." It says nothing about MFA.
MFA appears in the guidance under that requirement, which recommends multi-factor authentication "for all user accounts and especially those with heightened privileges". The same pattern holds everywhere. TLS, key management practices, tamper-proof logs and SIEM forwarding are all guidance. The framework specifies no encryption algorithm and no log retention period. The one hard number on incidents is in the HSUP65 guidance: incidents affecting health sector customers are to be reported to Health NZ and, where applicable, NCSC, CERT NZ and the Privacy Commissioner within 24 hours of detection.
So write "the HISF guidance recommends", not "HISO requires", when you describe these controls. And use the guidance anyway, because it is what an assessor will read when deciding whether your score is a 3 or a 5.
Control by Control: HISF to Salesforce
The IDs below are from the supplier part (HSUP) with the medium to large equivalent (HML) beside them. The Salesforce column is my mapping, not Health NZ's.
| Control area | HSUP / HML | What the guidance looks for | Salesforce evidence |
|---|---|---|---|
| Account lifecycle and leavers | HSUP33, HSUP04 / HML38, HML04 | Accounts managed from creation to removal; documented joiner, mover and leaver steps | User provisioning process, deactivation records, frozen and inactive user reports |
| Authentication | HSUP34 / HML39 | MFA for all users, especially privileged ones; SSO at organisational level | MFA enforcement on all internal users, SSO configuration, passkeys for privileged users |
| Access authorisation | HSUP35 / HML40 | Access defined by business need; reviews at least quarterly for users and monthly for heightened permissions | Permission set and permission set group design, a role-based access matrix, review records |
| Privileged access | HSUP36 / HML41 | Only authorised users and services hold privileged rights | Holders of Modify All Data, View All Data, Customize Application and Manage Users, reviewed monthly |
| Cryptography and keys | HSUP32 / HML37 | Rules for encryption and key management, including logging of key activity | Default encryption at rest, Shield Platform Encryption, tenant secret rotation, BYOK or Cache-Only Key Service if chosen |
| Logging | HSUP61 / HML70 | Logs with user and system identifiers, kept per retention policy, unalterable, forwarded centrally | Event Monitoring log files, Setup Audit Trail, Login History, Field Audit Trail, export to a SIEM |
| Cloud risk and assurance | HSUP26 / HML30 | A risk assessment method for cloud services | Your cloud risk assessment of Salesforce, Salesforce's compliance reports, data location decision |
| Multi-tenant cloud | HSUP45 / HML53 | Controls for information in a multi-tenant environment; the SaaS customer owns identities and access | Sharing model, org-wide defaults, guest user and Experience Cloud configuration |
| Secure baseline | HSUP52 / HML60 | A standard baseline configuration | Health Check score and a documented baseline, such as the independent Security Benchmark for Salesforce |
| Change control | HSUP16 / HML18 | A documented change process | Source control, pull request reviews, deployment pipeline records |
| Production separation | HSUP50 / HML58 | Separate production and non-production environments | Sandbox strategy, data masking in sandboxes, no real data in developer orgs |
| Data leakage | HSUP55 / HML69 | Detect and prevent unauthorised disclosure | Transaction Security policies, report export controls, email and file sharing restrictions |
| Backup and restore | HSUP15, HSUP48, HSUP49 / HML17, HML56, HML57 | A backup procedure, protected copies, tested restores | Backup tool or export schedule, restore test records |
| Incident handling | HSUP07, HSUP65 / HML07, HML75 | An incident process; customer incidents notified as agreed, and reported within 24 hours of detection | Incident runbook covering Salesforce, alerting from Event Monitoring or the SIEM |
| Supplier evaluation | HSUP67, HSUP68 / HML25, HML36 | Suppliers evaluated before and after onboarding; security terms in agreements | Assessment of Salesforce and every connected app and AppExchange package |
Two rows deserve more than a table cell.
Access reviews have real cadences. The HSUP35 guidance is one of the few places with numbers: reviews at least quarterly for ordinary access and at least monthly for heightened permissions. In Salesforce terms, "heightened" means anyone holding Modify All Data, View All Data or the admin permissions above, through a profile, permission set or permission set group. A monthly report of those holders, signed off by a named person, is cheap evidence for a maturity score many orgs cannot currently support.
Supplier evaluation includes your connected apps. HSUP67 asks for suppliers to be evaluated before and after onboarding. Every connected app with a refresh token and every AppExchange package with data access is a supplier relationship in practice. If your evidence covers only Salesforce, Inc., the assessor will notice the integrations.
Where Salesforce Stops and You Start
Salesforce publishes a long list of certifications, including ISO 27001, ISO 27017, ISO 27018, SOC 2, IRAP for its Australian Hyperforce services, and country health schemes such as NEN 7510 for the Netherlands. It does not publish a HISO 10029 or NZISM statement, and its compliance portal has no New Zealand category.
That matters less than it sounds, because the framework places most of the work on you anyway. The HSUP45 guidance says that when using SaaS, "organisations are responsible for user accounts and identities to form a secure basis for controlling access to resources." Salesforce's ISO and SOC reports say nothing about your org-wide defaults, your guest user, or who holds View All Data. Use the platform certifications for the cloud assurance rows (HSUP26, HSUP45) and evidence the rest from your org.
Logging Is Often the Gap
The HSUP61 guidance asks for logs stored per your retention policy and the customer's, kept so "that they cannot be altered in any way", and transferred centrally, for example to a SIEM. Compare that with native Salesforce retention:
| Source | Retention |
|---|---|
| Setup Audit Trail | 180 days |
| Login History | 6 months (up to 20,000 records) |
| Field history (without Field Audit Trail) | 18 months, 24 via the API |
| Event Monitoring log files (Shield or the Event Monitoring add-on) | 1 year by default |
Salesforce's own documentation says event log files "aren't a system of record for user activity". So even with Shield, the guidance's tamper-proof and central storage points come from exporting logs to a SIEM you control. Without Shield, start with the free event types described in Free Salesforce Event Monitoring: Build a Security Baseline from EventLogFile Without Shield, and export them before they expire.
Data Location: No Residency Requirement
HISF does not require health information to stay in New Zealand. The supplier FAQ says there is "no strict prohibition on storing PHI outside New Zealand", provided offshore storage complies with New Zealand privacy law and the data is protected to the same standards as it would be in New Zealand. Data sovereignty appears in the guidance as something to consider in acquisition, backup and supplier agreements, not as a rule.
Salesforce has no New Zealand Hyperforce region; Australia is the nearest. Record the region, the jurisdiction risk and your reasoning in the cloud risk assessment (HSUP26). Salesforce Data Sovereignty in New Zealand covers the residency and CLOUD Act questions in detail.
Filling In the Self-Assessment Workbook
Health NZ publishes an assessment guidance workbook for suppliers: 44 questions covering all 68 HSUP requirements, each scored from HISF1 (None) to HISF5 (Embedded), with up to five representative evidence artefacts per question. It also publishes a helper document that maps each HSUP requirement to Secure Controls Framework controls, with links to resources such as the relevant NZISM chapters. If you are already certified to ISO 27001 or NIST CSF 2.0, the FAQ suggests starting from that mapping and closing the gaps.
For a Salesforce org, three habits make the workbook easier:
- Answer for the org, not the platform. Attach Salesforce's reports for the platform rows, then evidence the org for the rest.
- Keep the evidence reproducible. A saved query or report that lists privileged users is better evidence than a screenshot, because you can run it again at the next review.
- Score honestly. A 3 with a dated plan is more credible than a 5 the evidence does not support, and the framework is designed to show improvement over time.
If you use sf-audit to review the org, version 1.28.0 cites these requirement IDs on the findings they apply to. A finding carries the HSUP requirement and its HML equivalent, so a supplier and a health organisation each see their own part, and --frameworks hiso-supplier or hiso-provider limits a report to one of them. Each citation also says whether it comes from the Secure Controls Framework crosswalk, the same one Health NZ's helper document uses, or from sf-audit's own reading of the requirement. A citation means the finding is relevant to that requirement. It does not score the requirement for you, and a clean report is not evidence of HISF5.
Frequently Asked Questions
Q: Is HISO 10029 mandatory for Salesforce partners?
A: Not by law. Health NZ's FAQ states that HISF has no legislative mandate, but Health NZ expects suppliers to align with it and uses HISF maturity to evaluate third parties. In practice it reaches you through procurement and contracts, so check whether yours reference it.
Q: Which part of HISO 10029 applies to a Salesforce ISV or consultancy?
A: The supplier part, HISO 10029.4:2025, with requirements HSUP01 to HSUP68. It explicitly includes software as a service providers and sub-contractors.
Q: Does HISO 10029 require MFA?
A: The requirement (HSUP34) says accounts are authenticated and the process cannot be circumvented. The guidance under it recommends MFA for all users, especially privileged ones. Salesforce already requires MFA for internal users, so the evidence is your enforcement configuration and any exceptions.
Q: Do we need Salesforce Shield to align with HISO 10029?
A: Not strictly. HISF does not mandate customer-held keys or a specific logging product. Shield makes the cryptography and logging rows much easier to evidence, but a documented key decision and log export to a SIEM can also support a reasonable score.
Q: Does health data have to stay in New Zealand?
A: No. The supplier FAQ says there is no strict prohibition on storing personal health information outside New Zealand. The offshore location must be risk assessed and the security expectations still apply.
Key Takeaways
- Pick the right part: HISO 10029.4:2025 for suppliers, HISO 10029.3 for medium to large providers.
- No legislative mandate does not mean optional. Health NZ's expectations and the Privacy Commissioner's reading of Rule 5 both point to HISF.
- Quote the guidance as guidance. The requirements are technology-neutral; MFA, TLS and SIEM forwarding are recommendations under them.
- Evidence the org, not just the platform. Identity, access reviews, sharing and connected apps are yours.
- Fix logging first. Native retention ages out, and event log files are not a system of record.
What's Next?
Recommended Reading:
- Mapping Salesforce Security to NZISM, the NZ Privacy Act and ISO 27001, for the wider framework mapping
- Why Salesforce Health Cloud Needs Its Own Security Review, for what a review of a health org checks
- Salesforce Data Sovereignty in New Zealand, for the offshore hosting question
Action Items:
- Confirm which HISO 10029 part your contracts reference, and get the 2025 supplier part if you are a supplier.
- Run a report of every user holding Modify All Data, View All Data, Customize Application or Manage Users, and schedule it monthly.
- Check where your Salesforce logs go after they age out of the org, and fix that before the next assessment.
Resources & References
- Health NZ: Health security frameworks
- HISO 10029:2022 Health Information Security Framework (PDF)
- Health NZ: Cyber security resources for health suppliers
- HISF for suppliers: FAQ (PDF)
- HISF for suppliers: helper document (PDF)
- Privacy Commissioner: Manage My Health and Health NZ breached the Privacy Act
- Privacy Commissioner: Manage My Health inquiry, phase one full report (PDF)
- Salesforce Help: Multi-factor authentication for direct logins
- Salesforce Help: Shield Platform Encryption
- Salesforce Developers: EventLogFile retention
- Salesforce compliance portal
Responses
Checking your session.
Loading responses.