AI agents investigate every alert, add context, and prepare cases for response, on a full-stack SecOps platform that captures and correlates all your security data.
Cloud-based SIEM platform providing visibility across all your data sources
Every alert investigated, with a verdict and the evidence behind it
Manage your external footprint, publicly available data, and Dark Web leaks
Log management and threat detection across any of your log sources
Get ultimate assurance that your environment is free from threat actors
Fully featured distrubuted NDR for on-premises and public cloud environments
A SecOps platform purpose-built for industrial and OT environments
Integrated endpoint agent providing deep visibility, response and forensics
Deploy honeypots and honeytokens and stay ahead of threat actors
24x7 security operations from our Australian SOC. AI investigates every alert, and experienced analysts validate findings and contain threats around the clock.
24x7 managed detection and response across endpoint, network, cloud, identity, and log sources
AI investigations and 24x7 MDR on the Microsoft Sentinel you already own
Eyes-on-glass SOC and continuous threat hunting
Expert hunters and AI agents find attacker activity your alerts missed
Quickly recover from cyber attacks and breaches
ThreatDefence is the only SecOps as a Service company providing broad coverage across your entire technology stack with evidence-based security.
We provide security teams with full-stack SecOps infrastructure – you get deep visibility from day one, gain control over your security data, and get access to a comprehensive set of ready-to-use tools, detections, workflows, playbooks and scenarios.
24x7 SOC, Continuous Monitoring, Threat Containment and Incident Response
Visibility and actionable insights for all IT assets
Leverage our Cyber Range to train defenders based on real-world scenarios and simulations
OT and industrial cyber security services for critical infrastructure
Monitoring, evidence and a 24×7 SOC in one platform
Compliance monitoring, evidence and board reporting
Privacy Act reform impacts, obligations, and practical security considerations
Monitoring and compliance support for critical infrastructure environments
A practical guide to securing critical infrastructure with continuous monitoring
A practical buyer’s guide for schools evaluating SIEM and SOC services
A practical guide to selecting the right SIEM and SOC service for local government
Articles on security operations, AI and compliance
Events, awards and company news
Read what our customers say about us
Solution briefs and datasheets
How we keep your data secure
Technical support and knowledge base
Guides, case studies, and advisories in one place
How AI agents investigate alerts and run security operations
Free ebook: a practical guide to adopting an AI SOC platform
A practical guide to incident response and digital forensics
Where SOAR playbooks fit and where AI agents take over
Free ebook: modern security operations with Microsoft Sentinel
How the framework is structured and what changes from the Essential Eight
How an attack unfolds stage by stage and how to detect each one
November 16, 2026
November 13, 2026
November 10, 2026
We provide end-to-end SecOps solutions for Managed Security Service Providers (MSSPs), Managed Service Providers (MSPs), and Value-Added Resellers (VARs).
Find out how you can become a ThreatDefence partner.
Protect your entire technology stack and build your SecOps on your own pace
White-labeled AI SOC for every client tenant, co-managed with our SOC team
Launch your SOC business without any upfront investment
Embed security operations, threat intelligence and exposure data in your product
Sovereign SOC for Australian MSPs and MSSPs, with onshore analysts and client data
Set the rules for closing alerts automatically, with evidence checks and review
How MSPs deliver branded security monitoring with a SOC partner
ThreatDefence was an official partner of the Cyber Resilience Summit NSW, 29 October 2026 at Hilton Sydney.
Our team was back at BSides Canberra, and our cyber quiz was a hit again.
Two days in Perth with our partner Ever Nimble, on security operations and cyber resilience.
Sponsors of the AUSCERT Cyber Security Conference on the Gold Coast.
Sponsors of the Gartner Security & Risk Management Summit in March.
Sponsors of the Cyber Security for Critical Assets Summit in Perth, February 2026.
Expert conversations with speakers and attendees at CyberCon Melbourne 2025.
Account takeover is when an attacker gains control of a legitimate user account and acts with that user’s access. In a business tenant, one staff account opens mail, files, chat, and every application connected to single sign-on.This guide follows a single takeover from the first sign-in to cleanup, record by record. It shows what an investigator sees in the logs, what each record means, and where the attack could have been stopped.
A business account is worth far more than a personal one, because the identity behind it is trusted by the HR system, the finance system, and every other application the organization has connected. An attacker who signs in once inherits all of it.
Attackers use that access in a few recognizable ways.
The attacker reads mail to find a payment in progress, then redirects it. This is the most common goal against finance, sales, and executive accounts, and the business email compromise guide follows it stage by stage.
Customer lists, contracts, and personal records are downloaded for resale or extortion.
The account’s VPN or cloud access becomes the first step of a wider intrusion, including ransomware.
Phishing sent from a trusted address reaches the victim’s customers and suppliers, which compromises the next organization.
The working session is sold to someone who will do any of the above. A quiet first sign-in followed days later by activity from a different network usually means the account was sold.
No role is exempt. Senior staff are targeted for authority, finance staff for payments, IT staff for privilege, and executive assistants because they hold delegated access to someone else’s mailbox. Junior staff are targeted because their account is a way to phish everyone else from inside.
Every takeover begins with the attacker obtaining something the identity system accepts: a password, a session, an approval, or a new authentication method.
The user signs in through a proxy page that passes everything to the real service and keeps the session cookie that comes back. The session hijacking guide walks through the relay step by step.
Passwords leaked from other services are tried against the business account, or a handful of common passwords are tried against every account. Both succeed where an account has no second factor, and the password spraying and credential stuffing guide shows what each looks like in the logs.
Malware on a computer the employee uses copies the passwords and sessions saved in the browser, and the attacker loads the session without ever seeing a prompt. The infostealer guide covers what is taken and how to respond.
With the password already in hand, the attacker triggers repeated multi-factor prompts until the user approves one. The MFA fatigue guide ranks the methods that resist it.
The attacker phones the help desk as the user, claims a lost phone, and asks for a password reset or a new authenticator. Public information about the employee is often enough to pass basic checks.
The user is asked to approve an application that requests access to mail and files. Every screen is genuine. The application then reads the mailbox directly, with no sign-in by the attacker at all.
The attacker persuades a mobile carrier to move the user’s phone number to a new SIM card, and receives the codes sent by text message.
Each method leaves a different first record. The example that follows uses the relay route.
The account belongs to a sales manager at a mid-sized company using Microsoft 365. The sequence below is typical of takeovers that begin with a phishing link.
The attacker secured their access within five minutes, and nothing in the first four hours was visible to the user. The response that felt complete, a password reset, left the authenticator in place, and that one method was enough to undo the reset.
Most of the story above comes from sign-in records. Each one answers several questions, and the answers together separate an attacker from an employee.
The record gives the address, the country, and the network provider. A hosting company or anonymizing service is unusual for a person at work, and a consumer broadband provider in the right city can still be a proxy.
A registered or managed device carries an identifier and a compliance state. A blank device field, for a user who always works from a company laptop, is a finding.
The record names the browser and operating system. A user on a Windows laptop does not suddenly sign in from a Linux browser or an automation library.
The record shows what was being opened. Attackers favor the web portal and mail, and sign-ins to administration or scripting interfaces by ordinary users deserve attention.
The authentication details show whether the user completed multi-factor authentication in this sign-in or the requirement was met by a claim already in the token. The second case, from a new location, points to a reused session.
The record lists which access policies applied and whether each passed, failed, or did not apply.
A session identifier links every sign-in that grew from one authentication. One session seen from two networks is the signature of a stolen session.
Microsoft writes the same session identifier into Exchange Online, SharePoint, and Teams audit records. A mail read, a download, or a new inbox rule can be matched to the exact sign-in behind it, which separates the attacker’s actions from the real user’s during the same hours.
Interactive records show a person signing in, and non-interactive records show applications renewing tokens in the background. An attacker’s continued access appears mostly in the non-interactive log, which many teams never review.
Unfamiliar sign-ins happen every day. People travel, change phones, and work from cafes. The surrounding pattern decides which ones matter.
Asking the user settles most ambiguous cases. The question goes through a channel other than email, since the mailbox may be in the attacker’s hands, and it names the place and time of the sign-in. A user who cannot be reached on a privileged or finance account is a reason to contain first and ask afterward.
Most organizations already receive alerts about unfamiliar sign-ins and ignore them, because there are too many and most are harmless.
A single unfamiliar sign-in is weak evidence. The same sign-in followed within an hour by a new authentication method is strong. Detection should be written around pairs and sequences:
For each user, a baseline of the usual countries, network providers, devices, and working hours turns a vague alert into a specific one. A sales director who travels weekly needs a different baseline from a payroll officer who has signed in from one office for three years.
The same signal deserves a different response depending on the account. Administrators, finance staff, executives, and their assistants should sit in a higher tier, with a lower threshold for action and faster containment.
For each detection, agree what happens: who is told, whether sessions are revoked automatically, and at what point the account is blocked. Revoking a session costs the user one fresh sign-in, which makes it a good candidate for automatic action on the strongest signals.
Non-interactive sign-ins and application sign-ins are separate log categories, and each has to be selected for export. Collected and kept beyond the default retention, they are the difference between seeing a takeover and reconstructing one weeks later.
The investigation is the same in Google Workspace. The records have different names and live in the Admin console’s audit and investigation tool.
Each containment step removes one thing the attacker holds, and the order decides whether a gap is left between steps.
The session hijacking guide sets out what each of these actions ends and what it leaves in place.
The exposure window runs from the attacker’s first sign-in to the moment the last foothold was removed. In the example, that is from 09:21 until the authenticator was deleted, a day or more after the password reset.
Within the window, separate what was touched, what was copied, and what was reachable.
Audit records list the messages opened, the files downloaded, and the items sent.
A mailbox or folder synchronized to a client counts as taken in full.
Shared mailboxes, team sites, and applications behind single sign-on were open to the session. Where logs are thin, the assessment has to consider reach as well as recorded activity.
Then widen the search. Look for other accounts signed in from the same sources, colleagues who received the same phishing message, and recipients of anything the account sent. One takeover is usually part of a campaign.
Each step in the example has a control that breaks it.
The strongest pairing is phishing-resistant authentication with a device requirement, backed by monitoring that connects a risky sign-in to what happens in the hour after it. The MFA fatigue guide gives a rollout order for passkeys and security keys.
After any takeover, the people responsible for the business want answers in plain terms.
The answer names the method and says whether the same route is open for other staff.
The answer is the exposure window, with both ends dated.
The answer lists specific mail, files, and systems, with an honest statement of what could not be determined.
The answer says to whom, and whether those recipients have been warned.
The answer covers the other accounts caught by the same campaign.
Regulators, customers, or individuals may need notice, depending on the data involved.
The answer names the control that would have stopped it and the date that control will be in place.
A written answer to each, with the evidence behind it, is the record that insurers, auditors, and regulators later ask for.
ThreatDefence triages a suspicious sign-in the way this guide reads one: the network it came from, the user agent, the authentication steps, and what the session went on to do. AI agents assemble that record for every identity alert, analysts confirm the verdict, and a confirmed takeover is contained under agreed authority.
For a takeover found late, our responders rebuild the timeline across Microsoft 365, Entra ID, and Google Workspace. They confirm that every foothold is gone, including authentication methods, mailbox rules, and application grants.
Experiencing a breach?
Our incident response team answers 24x7, with or without a retainer.
Explore Identity Threat Detection and Response
Ask about a free Microsoft 365 forensic review, covering six months of activity in your tenant.
CountryAustraliaUnited StatesNew ZealandUnited KingdomCanadaSingaporeOtherI'm an MSP, MSSP, or reseller
Δ
Corporate account takeover is the compromise of a business user or service account, where an attacker signs in as that identity and uses its access. In banking the same term has a narrower meaning: fraud against a company’s online banking account, usually ending in unauthorized wire or payroll transfers. Both start the same way, with credentials or a session taken from an employee.
No. In Microsoft Entra ID an administrator’s reset ends the sessions that were opened with the old password, but it leaves authentication methods the attacker registered, application grants, inbox rules, and forwarding. With a method of their own on the account, an attacker can complete a self-service password reset and return. The reset has to be followed by session revocation and removal of everything that was added.
Disable sign-in first when the account is privileged or the attacker is still active, and keep it disabled until the review is finished. For a standard account with no live activity, a password reset followed by session revocation is the starting point. Disabling has one blind spot: mail still arrives at a disabled mailbox and its forwarding rules still run, so rules and forwarding are removed either way.
For downloads and synchronization, yes. The Microsoft 365 audit log and Google Workspace Drive log events record downloads, sync activity, and sharing changes by account, time, and address. Files previewed in a browser leave thinner records. Where the session identifier is recorded, each file event can be matched to the attacker’s session. Data the account could reach that shows no events is reported as accessible, with the reason stated.
Entra ID keeps sign-in logs for 30 days with paid licenses and 7 days on the free tier. The Microsoft 365 audit log, which holds mail, file, and inbox rule activity, keeps records for 180 days by default. Google Workspace keeps most audit and investigation log events for six months. Anything older exists only where logs were forwarded to a SIEM or an archive.
It becomes one when personal information was accessed, or is likely to have been, and the law that applies treats that as notifiable. The assessment starts from what the account could reach and what the audit records show was opened or downloaded. In Australia, the Privacy Act expects an assessment of a suspected eligible data breach within 30 days. In the United States, each state has its own notification law. Involve legal counsel from the day the takeover is confirmed.
Account takeover is the compromise of the account itself, whatever the attacker does next. Business email compromise is a payment fraud that often uses a taken-over mailbox, though some cases rely only on a lookalike domain and never touch the victim’s tenant. A takeover can equally end in data theft, internal phishing, or a network intrusion with no payment fraud involved.
The most common route is a phishing page that relays the sign-in and keeps the session issued after the second factor. Others are prompts sent repeatedly until one is approved, session cookies copied by malware, device code and consent requests on genuine Microsoft pages, a help desk talked into registering a new method, and SIM swaps against text message codes. Passkeys and security keys close the relay and prompt routes.
Session Hijacking and Token Theft
Business Email Compromise: Stages and Detection
Incident Response and DFIR Services