Introspectus
Start Free Trial

12 Days of Hackmas – Day 08

Sleigh-Ride Lateral Movement: How Attackers Travel After Initial Compromise

Executive Summary

Once attackers breach the initial defences, their goal shifts to exploration, privilege escalation and control. This phase, known as lateral movement, allows them to spread through systems like Santa visiting every chimney in a network. During the Christmas period, reduced staffing and delayed response times make it easier for attackers to move quietly between servers, endpoints and cloud environments. Executives should understand that a single compromised workstation can quickly become a full-scale incident if lateral movement isn’t contained.

How the Attack Works

After gaining an initial foothold, attackers use legitimate administrative tools and stolen credentials to expand their access. Common techniques include exploiting weak service accounts, reusing cached passwords, and leveraging tools like PowerShell, PsExec, or Remote Desktop Protocol (RDP). Attackers often disguise their activity as normal administrative behaviour to avoid detection.

The process typically unfolds in four stages:

  1. Credential Harvesting – Extracting cached or stored credentials from memory, password vaults or compromised systems.
  2. Privilege Escalation – Exploiting vulnerabilities or misconfigurations to gain higher-level access.
  3. Lateral Movement – Using remote tools to connect to additional systems and deploy malware or reconnaissance utilities.
  4. Persistence – Establishing hidden accounts or scheduled tasks to maintain control over the environment.
Without strong administrative control, attackers can move laterally across departments, reaching critical assets such as Active Directory, databases or backups, often unnoticed until major damage occurs.

Australian Context / Case Study

Australian organisations have seen multiple high-impact incidents where poor privilege management allowed attackers to move laterally. In 2022, Medibank suffered extensive network compromise after attackers gained access through a single remote desktop account. Due to excessive administrative privileges and unmonitored internal traffic, the attackers accessed servers, disabled backups, and deployed ransomware organisation-wide.

The ACSC’s Cyber Threat Report consistently notes that lateral movement is a critical phase in most major Australian data breaches, often enabled by weak segregation and insufficient application control.

How the Essential Eight Mitigates the Risk

The Essential Eight directly targets the techniques attackers use for lateral movement:

  • Restrict Administrative Privileges: Limits who can perform system changes, reducing the ability of attackers to escalate privileges or access sensitive assets.
  • Multi-Factor Authentication (MFA): Prevents attackers from reusing stolen credentials to move between systems.
  • Application Control: Blocks unauthorised tools (like PsExec or Cobalt Strike) commonly used for lateral movement.
  • Patch Operating Systems and Applications: Closes vulnerabilities exploited to gain elevated access or move laterally.
  • User Application Hardening: Disables risky features that attackers can exploit for initial or lateral access (e.g., PowerShell remoting, SMBv1).
  • Regular Backups: Ensures that if lateral movement leads to ransomware deployment, systems can be restored without paying ransoms.

When implemented at Maturity Level Two or above, these controls severely limit an attacker’s ability to expand beyond the first compromised endpoint.

Executive Takeaways

  1. Review and minimise administrative privileges – implement least-privilege access.
  2. Enforce MFA across all privileged and remote connections.
  3. Ensure application control policies block non-approved administrative tools.
  4. Patch all systems regularly and verify that remote management interfaces are secured.
  5. Segment networks to isolate critical servers and backups from standard user networks.
  6. Conduct red team or internal threat-hunting exercises to detect lateral movement techniques.

With layered defences through the Essential Eight, organisations can ensure that even if attackers sneak into one system, their sleigh ride across the network ends before they reach the crown jewels.

How Introspectus Helps

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 Challenge with Patch Operating Systems

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.

Patch Operating Systems Overview

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.

How Introspectus Works

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.

The Challenge with Patch Applications

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.

Patch Applications Overview

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.