Essential Eight
Go to our ASD Essentials assessment
Our assessment against the framework ASD Essentials is replacing. It covers PezPC's own environment against the ACSC maturity model, plus what PezNet the software contributes to yours. No external audit has been performed and no assessor has signed anything off.
Two things make this framework easy to misrepresent, and both are handled explicitly below. First, most of the eight are properties of the environment software is deployed into rather than of the software itself, so each strategy states PezPC's own position and, separately, what PezNet gives you towards yours. Second, the maturity levels are not a score to average: the ACSC's model grades each strategy from Zero to Three, where Zero simply means the Level One requirements are not fully met, and it asks organisations to reach the same level across all eight before climbing. That makes an overall level equal to the weakest strategy, which is why ours is what it is.
This sits beneath ASD Essentials (formerly Essential Eight), which has the row in the standards table of the main privacy policy. The standard itself is published by its own authority: ACSC maturity model.
Overall: Maturity Level Zero, not audited
That reads worse than it is, so here is exactly what it means. The ACSC asks organisations to reach the same level across all eight strategies before climbing, so an overall figure is the weakest strategy rather than an average of them. Five of the eight sit at Level Zero and two already meet Level One, with one not applicable. Application control is not implemented at all, and the two patching strategies fall short on the scanning cadence the model specifies rather than on whether patches get applied. Level One is what the ACSC suggests is generally suitable for a small to medium business, and it is what we would target.
How this relates to ASD Essentials
ASD is moving from the Essential Eight to ASD Essentials. Both stay published during the transition and ASD has not set a retirement date, so this page stays too, and some organisations still have obligations that name the Essential Eight.
The grades below do not carry over. ASD is clear that a maturity level does not translate into a rating under its new framework, because the two measure different things, so a strategy at Level One here can sit lower there. Each strategy below links to the actions ASD maps it to.
Preventing malware delivery and execution
| 1 | Application control | Level Zero |
PezPC does not operate application allowlisting on its own servers, so this strategy sits at Level Zero and is what caps the overall figure. For your install it is a property of the operating system, configured by whoever administers it: PezNet installs as an ordinary service and neither implements nor interferes with allowlisting.
ASD Essentials: Trustworthy software
· ASD Essentials: Secure configuration management
Next level: Level One would require application control on workstations, restricting execution to an approved set and preventing it from user profile and temporary folders.
|
| 2 | Patch applications | Level Zero |
PezPC applies patches to the software it runs, and pins forward off known-vulnerable dependencies when advisories land. What is missing is the cadence the model actually specifies: there is no vulnerability scanner running daily against internet-facing services and no automated asset discovery, so this is Level Zero on the letter of the requirement rather than on the spirit of it. PezNet helps you here: an install checks for releases daily and can apply one without a manual download, though it never forces the update.
ASD Essentials: Vulnerability management
· ASD Essentials: Asset identification
· ASD Essentials: Legacy system management
Next level: Level One would require a vulnerability scanner run at least daily against internet-facing services and at least weekly against browsers, office suites, email and PDF software; patches applied within two weeks, or within 48 hours where an exploit exists.
|
| 3 | Configure Microsoft Office macro settings | Not applicable | PezPC does not run Microsoft Office macros in its production environment, and PezNet neither processes, generates nor opens them. Exported spreadsheets are plain data with no macro content. There is no macro surface to harden on either side. ASD Essentials: Trustworthy software · ASD Essentials: Secure configuration management |
| 4 | User application hardening | Level Zero |
On PezPC's side this is largely unassessed: browser and endpoint hardening is not centrally enforced. On the product side PezNet does real work towards yours, serving a Content Security Policy that forbids inline script so page behaviour lives in separate modules, and marking cookies HttpOnly and, over HTTPS, Secure. Hardening the browsers your staff use to reach it remains yours.
ASD Essentials: Secure configuration management
· ASD Essentials: Content filtering
Next level: Level One would require browsers configured not to process Java or web advertisements from the internet, with those settings not user-changeable, and Internet Explorer 11 disabled or removed.
|
Limiting the extent of incidents
| 5 | Restrict administrative privileges | Level One |
The strongest of the eight on both sides. PezPC grants PezNet Portal administrator rights as a single explicit flag, never inherited, and publishes every screen it unlocks. PezNet ships a flat least-privilege permission model with no super-user that bypasses it, no impersonation feature, no support login and no vendor back door; rights are granted per group and can be denied per user. The gap against the model is process rather than capability: privileged access is not re-validated on a defined cycle.
ASD Essentials: Identity, credential and access management
· ASD Essentials: Least privilege access
· ASD Essentials: Secure administration
· ASD Essentials: Network segmentation and segregation
Next level: Level Two would require privileged access to be automatically disabled after twelve months unless revalidated, and after 45 days of inactivity, with privileged activity centrally logged.
|
| 6 | Patch operating systems | Level Zero |
PezPC patches the operating systems of its own servers, but without the scanning cadence the model specifies, so the same Level Zero reasoning as patching applications applies. For a self-hosted install this is entirely yours: PezNet does not manage, monitor or report on the host operating system's patch level.
ASD Essentials: Vulnerability management
· ASD Essentials: Asset identification
· ASD Essentials: Legacy system management
Next level: Level One would require a vulnerability scanner run at least fortnightly against operating systems, patches applied within one month, and within 48 hours for internet-facing services where an exploit exists.
|
| 7 | Multi-factor authentication | Level One |
Available and used on PezPC's Portal accounts. From version 0.3.0, PezNet can require it at sign-in, with the setting Require a second factor at sign-in under Settings > Single sign-on > Enforcement. It has three states. Off, the default, asks for nothing beyond the password or the single sign-on. Always asks every sign-in for a PezNet factor, a passkey or an authenticator app, single sign-on included, whatever the identity provider says. Unless IdP did MFA does the same, except that a single sign-on whose identity provider reports it did MFA is left alone. Anybody who holds no factor must set one up before anything else opens, and signing in with a passkey is never asked again, because the passkey already is the factor. The policy binds everybody who can reach the company, not only its own people: a person who can reach several companies is held to the strictest policy among them, so a client company that turns it on binds technicians whose home company has it off. PezNet also goes beyond the strategy by demanding a fresh step-up before any stored credential is revealed, recording the reveal. Turning the policy on is your configuration decision: it is off by default, and PezNet does not mandate it.
ASD Essentials: Identity, credential and access management
Next level: Level Two would require multi-factor authentication to be phishing-resistant, and to be used by all privileged users and for access to important data repositories, with successful and unsuccessful events centrally logged. For your install the gap is now mostly configuration rather than capability: passkeys are phishing-resistant once the installation has a public address set, Always makes a factor compulsory for every user, privileged or not, and every answer at the second step, right or wrong, is written to the person's sign-in history. Two parts stay with you. PezNet still accepts an authenticator code, which is not phishing-resistant, so that part rests on your people using passkeys or on an identity provider that enforces phishing-resistant MFA. And the sign-in history stays inside PezNet until you collect it into a central log.
|
Recovering data and system availability
| 8 | Regular backups | Level Zero |
PezPC backs up its database. The shortfall is testing: restoration is not exercised on a documented schedule, which Level One asks for. PezNet makes this easier for you than most software by keeping everything, including attachments and photographs, in one PostgreSQL database, so a consistent backup is a single ordinary dump rather than a coordination problem across services. Taking it, storing it off the server and testing a restore is yours.
ASD Essentials: Regular and proven backups
Next level: Level One would require backups retained in line with continuity requirements, restoration tested when first implemented and on any infrastructure change, and unprivileged accounts prevented from modifying or deleting backups.
|