While most Australians are enjoying festive celebrations, cybercriminals are hard at work testing billions of stolen usernames and passwords. Credential stuffing and brute-force attacks are relentless, automated campaigns designed to exploit weak or reused passwords. Executives and privileged users are particularly at risk during the Christmas period, when travel and remote logins increase. Attackers know that a single compromised account can provide access to sensitive business data or even allow them to bypass other defences. This ‘credential coal’ in the corporate stocking is one surprise every executive should avoid.
Credential stuffing leverages large databases of username-password pairs obtained from previous data breaches. Attackers use automated tools to test these credentials across multiple websites and cloud services, exploiting password reuse. Brute-force attacks, meanwhile, systematically attempt combinations of common passwords or patterns until access is achieved. Once an account is compromised, attackers can pivot to internal systems, escalate privileges, or launch further phishing campaigns.
The threat is magnified for executives, whose accounts often have broad system access or contain high-value information. Remote logins, mobile access and personal email forwarding rules provide multiple potential entry points. Holiday periods offer attackers the perfect storm: fewer staff to monitor logs, slower response times and executives using unfamiliar devices while travelling.
In recent years, several Australian organisations have reported credential-based breaches linked to password reuse. In FY2024–25, Cybercriminals are continuing their aggressive campaign of credential theft, purchasing stolen usernames and passwords from the dark web to access personal email, social media or financial accounts.
During the last holiday period, a new brute-force attack campaign leveraging the FastHTTP Go library was identified. This high-speed attack targeted Microsoft 365 accounts globally, aiming to gain unauthorised access through brute-force login attempts and spamming multi-factor authentication (MFA) requests. Campaigns like these use credential lists purchased on dark web forums, with many successful intrusions traced to reused or weak passwords.
The Essential Eight framework mitigates credential attacks by addressing both prevention and detection layers:
Achieving maturity across these controls creates multiple layers of protection. Even if one control fails, others will prevent or limit the attack’s success.
By combining Essential Eight maturity with disciplined credential management, executives can turn their ‘credential coal’ into a shining example of Christmas cyber preparedness.
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.