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 18, 2026
November 16, 2026
November 13, 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.
DFIR stands for digital forensics and incident response. It is the field of cybersecurity that investigates security incidents from evidence and manages the response to them.Digital forensics establishes what happened. Incident response contains the threat and restores operations. This guide explains how the two fit together, how long each kind of evidence lasts, and the terms the field uses.
DFIR joins disciplines that grew up separately and pull in different directions.
The disciplines are combined because each needs the other. Responders cannot contain what has not been found, and investigators lose their evidence when responders rebuild systems before it is collected.
In practice the tension is about time. Investigators want to observe and collect before anything changes. The business wants systems back. The answer is fast, targeted collection, described under One System or the Whole Fleet below, so that containment does not wait for a full analysis.
The halves of DFIR have separate histories, and the differences in outlook come from them.
Digital forensics grew out of law enforcement. As computers appeared in criminal cases in the 1980s and 1990s, investigators needed ways to recover evidence from them that would stand up in court. The rules that developed were procedural. Work on a copy, never the original. Document every step. Be able to explain to a judge exactly how a conclusion was reached.
Incident response grew out of operations. In November 1988 a self-spreading program known as the Morris worm disrupted a large part of the early internet, and the response was improvised by administrators phoning each other. Within weeks the first computer emergency response team was established at Carnegie Mellon University to coordinate future incidents. The aim was to understand enough to stop the damage, restore service, and prevent a repeat.
For years the two were done by different people. Forensic examiners worked in laboratories on seized equipment. Incident responders worked in operations centers on live networks.
They merged as intrusions changed. Attackers stopped causing immediate, visible damage and began staying inside networks for weeks, using valid accounts and ordinary tools. Stopping them required finding out precisely what they had done, which is a forensic question, while they were still active, which is a response problem. An organization could no longer do one and then the other.
Each kind of evidence has a lifetime, and much of the skill in DFIR is collecting in the right order.
The table gives the order of work. Collect the short-lived evidence first, which is known as the order of volatility. Never switch off a system that may hold evidence in memory unless there is no other way to stop the damage.
The table also explains why many investigations cannot reach the start of an intrusion. If the attacker arrived six weeks ago and the firewall keeps five days, the first connection is gone.
Forensic conclusions rest on corroboration. A single record can be wrong, missing, or planted. Several independent records that agree are hard to dispute.
Take one common question: did a particular program run on this computer, and when? A Windows system records that fact in several unrelated places.
Windows workstations keep a record of programs that have run, with a count and recent run times, to speed up later launches. The feature is off by default on servers.
A separate mechanism notes programs the system has seen, with file details.
Per-user records show which programs that person started from the desktop.
Where auditing is enabled, each program start is logged with its command line and the account that launched it.
The security agent keeps its own record of the process, its parent, and its network connections.
The program file carries creation and modification times, and the file system’s change journal keeps entries even if the file was later deleted.
If the program is still running, it can be seen directly.
An attacker who deletes the program removes one of these. One who clears the event log removes another, and the clearing itself is logged. Removing all of them without a trace is extremely difficult, and gaps where records should be are evidence too.
The examiner lines these up on a timeline. When five sources agree that a program first ran at 02:14 under a service account, the finding is solid. When they disagree, the disagreement usually reveals something: a changed clock, a tampered timestamp, or a second copy of the program.
This is why forensic reports read cautiously. A good one says what the evidence shows, how many sources support it, and what could not be checked.
Processes, files, registry entries, scheduled tasks, and user activity on workstations and servers.
The contents of a running system’s memory.
Authentication, application, and security logs from systems and identity providers.
Connection records and captured traffic showing what communicated with what.
Audit and access records from cloud platforms and software services.
Message headers, mailbox access records, and rules.
Examining malicious files to learn what they do and what they contact.
Evidence from phones and tablets, where relevant.
Each source answers a different question. Endpoint evidence shows what ran. Identity logs show who signed in. Network records show what left. An investigation that relies on one source sees one part of the picture.
Our guide to endpoint forensic artifacts covers what to collect on Windows, Linux, and macOS.
Steps 3 to 6 overlap. Scoping continues during containment, and analysis continues during recovery. The steps are in order of when each must start, not when each finishes.
A serious incident needs several kinds of expertise. In a small team one person covers more than one role. In a large response each is a separate person or group.
Runs the response. Sets priorities, coordinates the technical work with the business, and keeps one current account of the facts.
Examines endpoints, memory, and logs to reconstruct what happened. Produces the timeline.
Searches the wider environment for the same attacker elsewhere. Turns each new finding into a search across every system.
Takes apart suspicious files to learn what they do, what they contact, and how to detect them.
Investigates sign-ins, tokens, mailbox access, and cloud configuration. Increasingly central, since many intrusions never touch a traditional server.
Works from traffic records to show movement between systems and data leaving.
Usually from IT operations. Plans and carries out the rebuild and restore, guided by what the investigation has cleared as safe.
Legal counsel, privacy, communications, and the insurer’s representative, who turn technical findings into decisions and statements.
Forensic work has legal consequences, which shape how it is done.
Admissibility. If evidence may be used in court, an employment dispute, or an insurance claim, it must be shown to be authentic and unaltered. This is the purpose of forensic images, hash values, and chain of custody records. Evidence gathered casually may be accurate and still be challenged.
Legal privilege. In many jurisdictions, an investigation directed by lawyers for the purpose of legal advice can be protected from disclosure. Organizations often engage a forensic provider through legal counsel for this reason. The rules vary and are easy to get wrong, so counsel should be involved early.
Notification duties. Forensic findings decide whether data breach and incident reporting obligations apply. The investigation has to answer specific questions, such as what personal information was accessed, within legal timeframes.
Expert evidence. A forensic examiner may be asked to give a report or testimony explaining findings to a non-technical audience. Clear documentation made at the time is what makes that possible months later.
Privacy and employment law. Examining an employee’s device or mailbox raises its own legal questions. Investigations into staff conduct should involve HR and legal counsel from the beginning.
A record left by an operating system or application that shows something happened, such as a file that proves a program ran.
The documented history of who collected a piece of evidence and who has handled it since.
Action that stops the attacker from doing further harm.
How long the attacker was present before detection.
Removing the attacker’s tools, accounts, and access.
An exact copy of a disk or memory, taken so the original is not altered by analysis.
A fingerprint calculated from a file. If the file changes, the hash changes, so a matching hash shows the evidence has not been altered.
A specific trace of the attacker, such as an address, a file name, or a hash, that can be searched for elsewhere.
The attacker moving from one system to another inside the network.
Any method the attacker uses to keep access after a restart or a password change.
The weakness that allowed the incident to begin.
The ordered sequence of events, each tied to its evidence.
A fast, targeted collection of the most useful evidence from a system, in place of a full disk image.
Evidence that is lost when a system is powered off.
Traditional forensics examines one system in depth, usually from a full disk image. It is thorough and slow. One system can take a day or more.
Intrusions rarely involve one system. An attacker with administrator access may have touched hundreds. Examining them one at a time is impossible in the time available.
Enterprise-scale DFIR works the other way round. It collects targeted evidence from every endpoint at once, then searches the results for the attacker’s traces. Systems that match are examined in depth.
Both approaches are used in the same investigation. Fleet-wide collection finds where the attacker has been. Deep analysis of selected systems explains exactly what happened there.
Few organizations keep a full DFIR team. The skills are built through exposure: a person learns to investigate ransomware by investigating ransomware, and most organizations, fortunately, do not provide enough practice.
A security operations center and a DFIR team do different jobs. The SOC monitors continuously and handles alerts. DFIR investigates confirmed incidents in depth. Many organizations use a SOC day to day and bring in DFIR specialists when something serious is found.
Call before systems are wiped or rebuilt.
ThreatDefence provides digital forensics and incident response 24x7. Our responders bring their own platform to an engagement, so evidence collection across endpoints, identity, network, and cloud starts in the first hours, and our SOC watches the environment while the organization recovers.
Our forensic work covers memory, disk, log, network, email, and cloud evidence, collected under court-admissible procedures with chain of custody recorded. An incident response retainer gives priority access to the DFIR team.
Experiencing a breach?
Our incident response team answers 24x7, with or without a retainer.
Explore Incident Response and DFIR
Discuss digital forensics, incident response retainers, and 24x7 monitoring for your organization.
CountryAustraliaUnited StatesNew ZealandUnited KingdomCanadaSingaporeOtherI'm an MSP, MSSP, or reseller
Δ
DFIR is short for digital forensics and incident response. Forensics works out what happened from evidence, and incident response contains the attacker and restores service. The term is used for the discipline, for the teams that practice it, and for the service organizations retain so that help is on hand when an incident is declared.
Forensics asks what happened and how we know. Incident response asks what to do now. They differ most in pace: a forensic examiner wants nothing changed until it is copied, and a responder wants the attacker out today. Done together, the first hours of collection give responders enough to contain the attacker without destroying what the examiner needs.
A DFIR analyst collects and examines evidence from endpoints, logs, networks, and cloud services to reconstruct an incident. Day to day that means building a timeline, turning each finding into a search across the other systems, advising on containment, and writing down what the evidence supports and what it leaves open.
No. A SOC watches continuously and decides which alerts are real. DFIR starts where that ends, with a confirmed incident that needs scoping, evidence, and a timeline. The handover works best when it is agreed in advance: what the SOC may contain on its own authority, when it calls DFIR, and what evidence it preserves before it acts.
A single compromised account may take a day or two, and a network-wide intrusion can take weeks. The length is set mostly by how many systems are in scope and how much evidence survived. Early findings guide containment long before the final report is written, so the business does not wait for the end of the investigation to act.
Chain of custody is the documented record of who collected evidence, when and how it was collected, and who has handled it since. It matters outside court as well, because an insurer, a regulator, or the other side in an employment dispute can challenge evidence whose handling is undocumented. Starting the record at collection takes minutes, and it cannot be reconstructed afterward.
By function: a remote collection agent that gathers evidence from many endpoints at once, memory and disk analysis tools, a log search platform, network traffic records, a malware sandbox, and a timeline that joins the results. Open-source tools cover most of these functions. What decides the outcome is whether the tooling can reach every system quickly, including servers and cloud services.
Yes. Most investigation and containment is now performed remotely using endpoint agents, authorized cloud access, and remote evidence collection tools. On-site work may still be necessary for physical evidence acquisition, inaccessible systems, infrastructure recovery, and incident coordination. Remote work also starts sooner, which matters because the shortest-lived evidence is gone within hours.
Endpoint Forensic Artifacts
Cyber Incident Response Guide
Incident Response and DFIR Services