Where your business
stands today
A board-ready self-assessment mapped to the ASD Essential Eight, Privacy Act 1988, and the Notifiable Data Breaches Scheme.
7 priority actions
A board-ready self-assessment mapped to the ASD Essential Eight, Privacy Act 1988, and the Notifiable Data Breaches Scheme.
What the numbers mean for the business, and the single decision to make.
Sample Company Pty Ltd shows a developing cyber and privacy readiness posture at 62%, with four critical weaknesses that should be closed within the next 30 to 90 days.
The strongest areas are individual rights handling and privacy notice coverage. The most material weaknesses relate to application control, privileged access governance, backup restoration testing, and incident response readiness. Together these gaps increase exposure to ransomware, account compromise, business interruption, and regulatory scrutiny under the Privacy Act 1988.
Eight domains, weighted into the overall score. Four are in the critical band (<55%).
| Domain | Score | Status | Business meaning |
|---|---|---|---|
| Application Control & Hardening | 45% | Critical | Unapproved software and scripts may execute, increasing malware and ransomware exposure. |
| Patch Management | 58% | High | Patch timelines are inconsistent, especially for third-party applications and internet-facing systems. |
| Access Control & Privileges | 50% | Critical | Privileged accounts and MFA controls need stronger enforcement to reduce account takeover risk. |
| Backup, Recovery & Resilience | 61% | High | Backups exist, but restoration evidence and recovery objectives are not mature enough. |
| Privacy Governance | 74% | Moderate | Privacy policy is present, but data inventory and collection notice controls need improvement. |
| Data Use, Disclosure & Retention | 63% | High | Retention, overseas disclosure, and vendor controls require better documentation. |
| Individual Rights | 78% | Developing | Access and correction processes exist, but evidence and ownership should be formalised. |
| Incident Response & Breach | 52% | Critical | The organisation may not be able to assess, contain, notify, and document a breach under pressure. |
Ranked by business impact. Critical items first.
| Priority | Finding | Impact | Recommended action |
|---|---|---|---|
| Critical | No formal application allowlisting across workstations and servers. | Malware, unapproved scripts, and ransomware can execute with limited prevention. | Implement Microsoft Defender Application Control, AppLocker, or equivalent for high-risk endpoints first. |
| Critical | MFA is not enforced consistently across all internet-facing services. | Stolen credentials can lead to email compromise, data theft, and fraudulent payment instructions. | Require MFA for Microsoft 365, VPN, remote access, admin portals, and privileged actions within 30 days. |
| High | Backup restoration is not tested quarterly with documented RTO/RPO metrics. | Backups may fail during ransomware recovery, extending downtime and financial loss. | Run a partial restore test, record recovery time, document evidence, and schedule quarterly testing. |
| High | No board-approved data breach response plan aligned with the NDB Scheme. | The organisation may miss assessment, notification, and customer communication obligations after a breach. | Adopt the Incident Response Plan template in Appendix C and run a tabletop exercise within 60 days. |
| High | Vendor data processing agreements are incomplete or not centrally tracked. | Third-party handling of personal information may create APP 8 and APP 11 exposure. | Create a vendor register and require DPAs for providers with access to personal information. |
Turning the score into owned, sequenced action.
Credential compromise is the fastest path from email to full business compromise.
Backups only reduce risk if the organisation can prove that restoration works under realistic conditions.
Privacy maturity depends on evidence. The business should be able to show what it collects, where, and who receives it.
An incident plan reduces confusion when time pressure is highest and evidences reasonable preparation.
Sequenced actions with owners and the evidence to keep for your board or insurer.
| Timing | Objective | Actions | Owner | Evidence to keep |
|---|---|---|---|---|
| Days 1–30 | Close the most exposed attack paths. | Enforce MFA; remove dormant accounts; identify end-of-life systems; test one backup restore; disable internet macros. | IT Manager / MSP | MFA policy, account review log, backup restore record, patch inventory. |
| Days 31–60 | Build operational proof and privacy evidence. | Create data inventory; update Privacy Policy and collection notices; document vendor list; adopt incident response plan. | Operations / Privacy Lead | Data inventory, policy version history, vendor register, approved incident plan. |
| Days 61–90 | Validate resilience; prepare for scrutiny. | Run incident tabletop; complete vendor DPA review; implement allowlisting pilot; document quarterly review process. | Leadership / IT / Legal | Tabletop minutes, signed DPAs, pilot report, review calendar. |
Why each area matters, and the obligation it supports — to justify the program internally.
| Area | Relevant framework | Why it matters |
|---|---|---|
| Application control, macros, hardening | ASD Essential Eight Strategies 1, 3, 4 | Prevents unapproved software, malicious documents, and drive-by compromise. |
| Patch management | ASD Essential Eight Strategies 2, 6 | Reduces exploitation of known vulnerabilities in apps and operating systems. |
| Access and MFA | ASD Essential Eight Strategies 5, 7; APP 11 | Supports reasonable steps to protect systems and personal information. |
| Backup and recovery | ASD Essential Eight Strategy 8; APP 11 | Reduces ransomware impact and supports business continuity. |
| Privacy governance | Privacy Act 1988 APPs 1–5 | Requires transparent management, collection notices, and lawful collection. |
| Data use, overseas disclosure, vendors | Privacy Act 1988 APPs 6–11 | Controls use, disclosure, retention, security, and overseas transfer of data. |
| Access and correction rights | Privacy Act 1988 APPs 12–13 | Requires processes for individual access to and correction of their data. |
| Breach response | NDB Scheme; Cyber Security Act 2024; SOCI | Defines assessment, notification, reporting, and incident-record expectations. |
Editable policies you can adapt to your business — the practical takeaway.
All users must use unique credentials and approved MFA for business systems. Privileged accounts must use phishing-resistant MFA where available and must not be used for email, browsing, or routine business activity.
Business-critical data must be backed up at least daily and stored in a format that cannot be modified or deleted using ordinary production credentials.
Privacy notice, retention schedule, and vendor checklist.
Purpose: give individuals a clear notice at or before collection of personal information (APP 5).
We collect your personal information to provide services, manage appointments, communicate with you, process payments, and meet legal obligations. If you do not provide required information, we may be unable to deliver the requested service.
| Data category | Retention period | Disposal method | Owner |
|---|---|---|---|
| Customer records | Per legal/business need (e.g. 7 yrs post-relationship) | Secure deletion or de-identification | Operations |
| Financial records | Align to ATO/tax obligations | Secure archive, then deletion | Finance |
| Employee records | Align to employment record obligations | Secure deletion after retention ends | HR |
| Marketing leads | Until consent withdrawn or no longer needed | CRM deletion or suppression list | Marketing |