To any organisation looking to align with the Essential Eight’s Maturity Level Three (ML3) – Congratulations!
Having previously aligned with both Maturity Level One (ML1) and Maturity Level Two (ML2), you should already have a robust cyber security posture in place. Your organisation should already be resilient against most common types of cyber-attacks.
However, the cyber-criminals are also upping their game.
As many organisations lift their cyber resilience, the criminals are also embracing new tactics. They are resorting to increasingly sophisticated methods that circumvent common cyber controls.
What does this mean for your organisation?
Put simply, you cannot rest on your laurels. Organisations must continuously look for ways to strengthen cyber resilience. Aligning with Essential Eight ML3 will help embed continuous cyber uplift within your organisation.
What is Essential Eight Maturity Level Three?
Essential Eight ML3 helps make your organisation resilient against cyber-criminals who are increasingly skilled and adaptive.
These are attackers who don’t need to rely on off-the-shelf hacking tools. Rather, they are attackers who are adept at identifying and exploiting any weakness in a target’s environment. They are the types of attackers who will be quick to exploit any newly identified vulnerabilities.
Often, these types of cyber-criminals select their targets carefully. They invest time and effort in conducting reconnaissance and engaging in social engineering, before carefully selecting a target that will be likely to deliver a solid return on that investment. Because they tend not to be interested in smash and grab tactics, they look for organisations with inadequate logging and monitoring capabilities, so they can gain persistent access to the target’s environment.
How does Maturity Level Two differ from Maturity Level One?
While Maturity Level One focused on basic cyber resilience, and a theme of Maturity Level Two was ensuring you have an adequate incident response capability, Maturity Level Three has a focus on driving continuous improvement.
One feature of ML3 is its focus on specific timeframes. Not only do certain cyber activities need to be conducted routinely, but they need to be conducted within specific timeframes that reduce any windows of opportunity attackers may have to exploit you.
Such timeframes help ensure that your organisation is continuously upping its game in the race against the cyber-criminals.
1-APPLICATION CONTROL
All too often, vulnerable applications are exploited by cyber criminals to gain access to your environment. That is why ML1 and ML2 emphasise the importance of only allowing staff to access applications you trust.
However, while most of the focus tends to be on internet-facing applications, it is also important to remember that non-internet facing systems must also be secured.
Non-internet facing systems can pose a significant risk to your organisation. If a cyber-criminal finds a way to breach your network perimeter, they may move laterally across the network, potentially compromising non-internet facing systems as well.
That’s why ML3 takes application control to the next level. Organisations looking to align with the Essential Eight’s ML3 should ensure they are also implementing security controls on applications hosted on non-internet facing servers.
To start with, we recommend turning off any applications on non-internet facing servers that are not absolutely necessary. For example, a non-internet facing server has no need for a web browser application, yet they are often installed by default. Such applications should either be disabled or removed completely.
Additionally, ML3 requires regular analysis of event logs from non-internet facing servers. This will help detect potentially malicious activity, such as unauthorised access, whether by staff members or external individuals.
2- PATCH APPLICATIONS
Unpatched applications are routinely exploited by cyber criminals to gain access to a target’s environment. That’s why ML1 and ML2 emphasise the importance of routine patching and vulnerability scanning, so your IT teams can ensure they don’t neglect rolling out important patches.
When it comes to the Essential Eight’s ML3, software patching is taken to the next level. Not only should regular patching be a routine activity, but it sets time limits on when those patches should be implemented.
Patches of critical vulnerabilities should be rolled out within 48 hours of a patch being made available. Meanwhile, patches for non-critical vulnerabilities should be rolled out within two weeks of the patch being made available.
These tighter time constraints around patching are designed to ensure that you don’t have vulnerable applications in your environment for extended periods of time, which would provide additional opportunities for cyber criminals to compromise you.
Additionally, ML3 requires the removal of applications from your environment in cases where the vendor no longer develops security patches.
3- CONFIGURE MICROSOFT OFFICE MACROS
Macros can be a useful efficiency tool for staff who need to perform repetitive tasks using the Microsoft Office suite of applications, such as Excel. However, as discussed in ML1 and ML2, macros may be vulnerable to cyber-criminals who can exploit the automation of macros to execute malware in your environment.
That is why it is advised to disable macros unless individual staff members can demonstrate an overriding need to use them.
To align with ML3, you should only allow Microsoft Office macros to run within a sandboxed environment. A sandbox is a virtual machine that is isolated from the rest of the network and applications.
This would allow staff who need to use macros to do so without risking the rest of the organisation. They could run software that is potentially unsafe, while ensuring that any risks would be contained.
4- APPLICATION HARDENING
To align with ML1 and ML2, you would have significantly hardened your applications by deactivating most unnecessary software functionality, including Flash and JavaScript.
To align with ML3, you should also disable or remove the .NET Framework, which is a widely used open-source software development framework. While many application developers enjoy the flexibility of the .NET Framework, it does pose a range of security risks.
The .NET Framework can be vulnerable to a range of risks, including remote code execution attacks.
Additionally, ML3 requires Windows PowerShell 2.0 to be disabled or removed. PowerShell is a task automation and configuration management program from Microsoft. Unlike newer PowerShell versions, version 2.0 lacks many security features, leaving it vulnerable to a range of attacks.
5- RESTRICT ADMINISTRATIVE PRIVILEGES
User accounts with administrative privileges pose a significant risk if the credentials to those accounts are compromised. When cyber-criminals gain access to privileged accounts, they typically have the ability to access more systems, manipulate configurations, compromise highly valuable data, and run malware.
For these reasons, ML1 and ML2 emphasise the importance of restricting administrative privileges according to the Principle of Least Privilege (PoPL), while ensuring inactive administrative accounts are deactivated.
To align with the Essential Eight’s ML3, you should also ensure that privileged access to systems, applications and data repositories are restricted. Users should be limited to only what is required to undertake their duties.
Additionally, administrative activities should only take place on a dedicated secure admin workstation. This helps avoid the risk of undertaking administrative activities on a compromised endpoint.
Finally, administrative activities should be undertaken on systems and applications in accordance with just-in-time administration principles. In other words, administrative tasks, such as configuration changes, should take place as they are required, rather than far in advance, providing less time for cyber-criminals to undertake malicious acts.
6- PATCH OPERATING SYSTEMS
Just as ML3 requires you to patch applications within specific timeframes, you should also ensure Operating Systems (OS) are patched within specific timeframes.
Patches remediating critical vulnerabilities in the OS powering your workstations, non-internet-facing servers, non-internet-facing network devices, drivers, and firmware should all be rolled out within 48 hours of the patch being made available.
In cases where such vulnerabilities are deemed not to be critical, then you have one month to roll the patches out.
ML3 also requires you to ensure that the latest OS releases are always in use.
7- MULTI-FACTOR AUTHENTICATION
As we know, multi-factor authentication (MFA) is one of the most effective ways to prevent cyber-attacks. That is why ML1 emphasised the importance of rolling it out across your organisation, while ML2 sought to strengthen MFA by making it phishing resistant.
When it comes to ML3, you are also urged to implement MFA on data repositories. Data repositories are widely used in organisations where different teams of staff need access to data for a range of purposes. The data stored in these repositories is often highly valuable, making them attractive targets for cyber-criminals. By ensuring that MFA is enabled on your repositories, you can help prevent unauthorised access to your valuable data.
You should also ensure that MFA on your data repositories is phishing resistant. Using physical tokens is one effective way to achieve this.
Organisations that provide customers with access to online systems, such as customer portals, should also enable MFA on such systems.
8- REGULAR BACKUPS
The key to recovering quickly following any cyber incident is having comprehensive backups. To align with ML1, you would have ensured that your critical business data was being backed up regularly. ML2 went a step further, ensuring measures were in place that would block privileged users from modifying or deleting those backups.
To align with ML3, you also need to ensure that users, both regular and privileged, cannot access their own backups. By isolating users from their own backups, you help ensure that in the event of an account being compromised, the attacker won’t be able to pivot and tamper with that user’s backups.
The one exception to this rule is the backup administrator account. While a backup administrator needs access to all backups in cases that they need to be restored, they should be prevented from modifying and deleting backups during their retention period.
How can Virtuelle help?
Aligning with the Essential Eight’s Maturity Level Three will help your organisation achieve robust cyber resilience. However, implementing some of the measures contained in ML3 may require a degree of expertise that is beyond the capabilities of many IT teams.
With Virtuelle Security guiding you through the implementation of ML3, you can ensure you align with all its requirements and achieve a strong cyber security posture.
Virtuelle Security will work with your organisation to understand your specific circumstances. We will then tailor a program of works that help you achieve your cyber uplift goals.
Contact us today for a FREE 1:1 consultation with Robert Kirtley, our Cyber Security Director, and learn how Virtuelle Security can help protect your organisation.