Introspectus provides real time, analytical information about your IT environments so that you can make data-driven decisions.
The Christmas period, with its flurry of financial transactions, supplier payments and executive absences, presents an ideal environment for Business Email Compromise (BEC) attacks. Cybercriminals exploit festive distractions and reduced staffing to impersonate senior executives or trusted suppliers. These fraudulent communications often request urgent payments, changes to bank details, or confidential data. BEC remains one of the most financially damaging forms of cybercrime in Australia, costing organisations millions each year.
Business Email Compromise attacks rely on social engineering and psychological manipulation rather than technical exploitation. Attackers often start by conducting reconnaissance on the organisation, identifying finance staff and executives through LinkedIn or company websites. They then register look-alike domains or compromise legitimate email accounts through phishing or credential stuffing.
Once they gain access or craft a convincing spoof, they send urgent, plausible messages like an email appearing to come from the CEO requesting an ‘end-of-year supplier payment’ before the finance cutoff. Because the requests appear legitimate and time-sensitive, recipients often bypass verification procedures, resulting in funds being transferred to attacker-controlled accounts.
In some cases, attackers compromise supplier accounts and modify invoices so that payments are redirected to fraudulent bank details, creating long-lasting trust and reconciliation issues between business partners.
Scammers stole more than $152.6 million from Australians using BEC attacks in 2024. This was an increase of 66 per cent from 2023, which reported $91.6 million in losses according to the Targeting Scams report by the National Anti-Scams Centre. One notable case involved a NSW-based construction company which received fraudulent invoices totalling $41,800 from criminals who spoofed the email of a trusted supplier.
After making the payment, the victim texted the remittance to the supplier using a known mobile number and was told the bank details were incorrect. The victim immediately reported the incident to police via ReportCyber, who were able to recover the full amount.
In a more unfortunate case, a Tasmanian woman had $120,000 stolen after scammers intercepted her email correspondence with a construction company she had hired to renovate her home. Using a spoofed email address that closely mimicked the legitimate business, the criminals claimed the company had updated its banking details and sent a new invoice. The invoice was an exact replica of the original, except the payment details had been replaced with the scammers’ account. Due to a delay in reporting, the money was not recoverable.
The ACSC’s Essential Eight provides robust protection against the root causes of Business Email Compromise by reducing the likelihood of account compromise, limiting attacker movement, and enabling rapid recovery:
Together, these controls not only reduce the technical risk of compromise but also support governance and compliance obligations under the Security of Critical Infrastructure (SOCI) Act and Australian Privacy Principles (APPs).
A strong combination of Essential Eight maturity, staff vigilance, and process integrity ensures organisations stay on the ‘Nice List,’ protecting both finances and reputation during the festive season.
Each agent compares the current patch list against what is actually installed on its device. Any gap between what has been released and what is deployed is immediately surfaced. Critically, Introspectus pays particular attention to the timing of patch deployment not just whether a patch is present, but when it was applied.
This temporal dimension is central to Essential Eight compliance, where the difference between a patch applied on day two versus day thirty can mean the difference between maturity levels, and between an environment that was protected and one that was exposed.
This combination of daily patch intelligence, severity-based filtering, agent-level validation, and deployment timing analysis gives organisations a real-time, evidence-based view of their operating system patch posture mapped directly to the ISM controls applicable to the Essential Eight patch operating systems strategy.
The visibility gap here is particularly consequential. A patch may be approved and scheduled, yet never successfully applied due to a failed deployment, a device that was offline during the maintenance window, a reboot that was deferred, or a system that exists outside managed channels entirely.
Organisations that rely solely on deployment tooling to confirm patch status are measuring intent, not reality. The ACSC is explicit on this point: organisations need to confirm patches have been applied successfully, not merely that they were dispatched.
Within the Essential Eight framework, patching operating systems is a core and non-negotiable control. The ACSC sets clear expectations: patches for internet-facing infrastructure must be applied within 48 hours when identified as critical or where working exploits exist, and within two weeks for standard releases.
Patches for workstations, servers, and network devices must be applied within one month, with tighter timeframes applying in high-threat environments. Critically, the ACSC also mandates that vulnerability scanning occurs at least daily for internet-facing systems and at least fortnightly for workstations and non-internet-facing infrastructure not to replace patching, but to confirm it has actually occurred.
From this inventory, Introspectus performs targeted web intelligence gathering. For each application identified, the platform locates the top five authoritative sources of patch and release information vendor security advisories, release notes, and vulnerability databases and retrieves that content into a central repository.
Aletheia, Introspectus’s AI analysis agent, then reads and analyses this content to extract the intelligence that matters for application patching: the latest available version, whether a release addresses a security vulnerability, the severity of that vulnerability, and all information relevant to the Essential Eight application patching requirements. This structured intelligence is mapped directly to the applicable ISM controls, producing defensible, audit-ready evidence of an organisation’s application patch compliance posture.
A critical and frequently overlooked problem is the visibility gap. Organisations may believe their applications are current when, in reality, patches have silently failed, devices have missed deployment windows, or software has been installed outside of managed channels entirely.
Without continuous inspection at the endpoint level, these gaps go undetected until an audit or, worse, a breach.
Within the Essential Eight standard, patching applications is a dedicated and non-negotiable control. The ACSC specifies clear timeframes: critical vulnerabilities in internet-facing services must be addressed within 48 hours, commonly used applications such as office productivity suites, web browsers, email clients and PDF software must be patched within two weeks of release, and all other applications within one month.
For organisations in high-threat environments, the bar is higher still. Meeting these requirements consistently across hundreds of distinct applications deployed across thousands of endpoints is not achievable through manual effort alone.