Broker guide
Essential Eight for Mortgage Brokers
Asked which cyber controls protect your client files? Learn the Essential Eight strategies and maturity levels, and how a small brokerage applies them.
- Published
- Updated
The Essential Eight is a set of cyber security strategies from the Australian Cyber Security Centre to protect internet-connected systems. At a mortgage brokerage, the controls reduce the risk of account takeovers and help stop harmful software from running on staff laptops. They also protect the backups you need to recover client files.
The Eight Strategies
The eight strategies work together. The Australian Signals Directorate (ASD) sets out the controls for each strategy in its 2023 Essential Eight Maturity Model. Essential 8 is another spelling of the same framework.
| Strategy | What it protects in a brokerage |
|---|---|
| Patch applications | Updates close known security flaws in the browser, email client and PDF software you use to open client documents. |
| Patch operating systems | Updates fix flaws in the software that runs each laptop and provides access to the files on it. |
| Multi-factor authentication | A second form of proof at sign-in helps protect client records and mailboxes if a password is stolen. |
| Restrict administrative privileges | Limiting who has administrator access reduces the damage a compromised everyday account can do to systems and files. |
| Application control | Allowing only approved software to run helps stop an unapproved program downloaded from email from running on a broker’s laptop. |
| Restrict Microsoft Office macros | Restricting macros reduces the chance that code embedded in a spreadsheet or document runs when you open it. |
| User application hardening | Turning off unneeded browser functions reduces the ways harmful web content can reach the laptop. |
| Regular backups | Protected copies give you a way to recover records and settings after deletion, equipment failure or ransomware. |
Maturity Levels
Maturity Level One is a practical first target for a small brokerage applying the Essential Eight. Choose your eventual target based on the risk to your client records, the systems you use and any requirements in your own agreements.
- At Level Zero, gaps remain in the protections needed for Level One.
- Level One addresses common attacks that exploit weaknesses such as stolen passwords or missing software updates.
- At Level Two, the controls address attackers who invest more effort in picking targets and getting past controls.
- Level Three is designed for more adaptive attackers who spend more time finding and exploiting weaknesses specific to their target.
ASD recommends reaching the same level across all eight strategies before moving higher. Appendix A of the model sets out the full Level One requirements. Use it to assess each control, including where it applies and how you can show that it works.
ASD has since published ASD Essentials for enterprise IT, which assesses whether security actions achieve their intended results. If your aggregator asks about the newer framework, use ASD’s transition guidance to see where you can reuse your Essential Eight evidence.
Apply It to a Small Brokerage
In this example, a principal broker, a second broker and a loan processor use managed laptops, a cloud customer relationship management (CRM) system, hosted email and cloud document storage. The principal approves access and owns the brokerage’s security decisions. A contracted IT provider manages the laptops, while the loan processor keeps the control records and coordinates backup checks.
| Strategy | Who runs it for the brokerage | What the vendor runs or supplies |
|---|---|---|
| Patch applications | The IT provider manages updates for browsers, email clients, PDF readers and any installed CRM or storage app. | Cloud vendors patch the hosted applications they operate. |
| Patch operating systems | The IT provider tracks updates on all three laptops and replaces unsupported systems. | Cloud vendors patch the operating systems on the servers they manage. |
| Multi-factor authentication | The principal requires it for staff accounts in the CRM, email and document storage. The IT provider enables it and checks enrolment. | Each cloud vendor supplies its sign-in controls or supports a connection to the brokerage’s sign-in service. |
| Restrict administrative privileges | The principal approves administrator access. The IT provider keeps admin accounts separate from routine email and client file work and reviews cloud admin roles. | Cloud vendors manage their own staff’s access to the services they operate. |
| Application control | The IT provider enforces an approved software list on the laptops, including for programs opened from downloads or temporary folders. | Cloud vendors control what runs on the infrastructure they manage. |
| Restrict Microsoft Office macros | The IT provider disables macros where staff have no business need and blocks macros in files from the internet, including spreadsheets sent by email. | The office software vendor supplies the controls. The brokerage’s IT provider sets and enforces the policy on its laptops. |
| User application hardening | The IT provider locks browser security settings, blocks web ads and disables unneeded browser features on the laptops used for the CRM and cloud files. | Cloud vendors secure their own applications and infrastructure. The IT provider manages the browsers staff use to reach them. |
| Regular backups | The processor checks that CRM records, email and document storage are covered. The IT provider protects the backup copies and tests recovery to a common point in time. | Cloud vendors provide the backup and recovery features specified in their agreements. Ask what each can restore after a staff member deletes a file or record. |
Use the ASD cloud shared responsibility guide to draw that line for each service. For example, the CRM vendor can patch its servers while the brokerage still has to protect its own CRM accounts. Have the processor pick a dummy client record and its linked document for a restore test so you can see whether the recovered record still points to the right file.
Evidence for Aggregators and Insurers
Keep a dated record of what each control covers, who manages it and what you observed when you checked it. An aggregator, lender or insurer can use those records to understand which protections apply to client files. The ASD assessment process guide puts observed test results above screenshots or policy statements as evidence that a control works.
- Keep a laptop and software inventory, update reports and tickets for overdue patches.
- Save sign-in policy exports, staff enrolment reports and the approved list of administrator accounts.
- Keep the application control, macro and browser settings with results from safe checks on a representative laptop.
- Keep each cloud provider’s responsibility statement, service terms and relevant assurance reports. Record gaps where you need a provider to confirm what it covers.
- Keep backup job records and a restore test report showing what you recovered, the recovery point and any missing records or files.
- Record each exception with its owner, reason, scope, replacement protection and next review date.
Answer questions about maturity against the scope you assessed and the level you can substantiate. If you’re still working towards Level One, give the control status and the next action for each gap. Redact client details and account identifiers before you share evidence.