Digital Forensics Services: What to Preserve After a Breach

What to protect in the first hours after an unauthorized admin account appears, and how forensic examiners preserve evidence that holds up with counsel and regulators.

By the Total 360 Security team14 min read
Digital forensics workbench with a write blocker cabled to a laptop and a sealed drive in an anti-static bag

When an unauthorized administrative account appears on a domain controller, the first rule is to change as little as possible until outside counsel has retained a forensic examiner. Digital forensics services then preserve the evidence as a bit-by-bit image under a documented chain of custody, separate what the logs prove from what the examiner infers, and write findings that counsel can defend in front of an insurer or a regulator.

If you are reading this the morning after, the instinct is to fix the problem fast. Resist it for the next few hours. The domain controller is the one machine where a reboot, a cleanup tool or a quick password reset can erase the answers you will need in six weeks, when your insurer or a state regulator starts asking how the account got there and whether anyone took data with it.

What should happen in the first hours after an unauthorized admin account is found?

Work through these in order, and do not skip ahead to the technical work until the first three are done.

  1. Call outside counsel first, before the IT team. Counsel decides how the investigation is structured and who it answers to. That decision shapes whether your forensic findings can later be protected by privilege, so it has to come before the first log is opened.
  2. Tell staff, in plain words, what not to do. Nobody touches the domain controller. Nobody runs antivirus on it. Nobody discusses the incident by email or chat on the affected network. An attacker with domain access may be reading those messages, and you do not want them to know what you have noticed.
  3. Export the security event logs before the formal investigation starts. Domain controller security logs overwrite themselves at a fixed size. If the account was created overnight on a busy server, the records from that night may already be shrinking. Counsel or the examiner should direct the export and record who ran it, from which machine, and when.
  4. Write down everything that has already happened. Who saw the alert, who logged on to look, what commands were run and at what time. Early, untidy notes are worth more than a tidy account reconstructed a week later from memory.
  5. Decide with the examiner whether the server stays connected. That decision is covered in the next section, because it is the one most likely to be made badly under pressure.

The reason for this order is simple. Every hour spent on cleanup before counsel and the examiner are involved is an hour in which the evidence can change without anyone being able to say how.

Why does rebooting or cleaning up the server destroy evidence?

Why does rebooting or cleaning up the server destroy evidence?, Total 360 Security

Evidence on a running machine lives in two places, and they behave differently. Volatile memory holds what is happening right now: running processes, active network connections, logged-on sessions and, on some systems, encryption keys. Disk artifacts record what has already happened, including the traces left by programs that ran earlier.

Three ordinary reflexes overwrite that state. Rebooting clears memory. Antivirus and cleanup tools change files and registry entries, and they often do it before anyone has captured what they touched. Resetting the suspicious account changes the very record that shows when it was created and by whom.

Containment is where this gets hard. Disconnecting a machine from the network stops an active attacker and keeps memory intact, because the machine keeps running. Powering it off stops the attacker too, but it destroys memory. Neither choice is free. Let the examiner make the call where you can. When you have to act first because an attacker is moving laterally, write down what you did and when, so the gap in the record can be explained.

What vanishes on reboot

Running processes, open network connections, logged-on sessions, loaded malware that exists only in memory, and any encryption keys held in RAM. Some attackers deliberately run only in memory so that a reboot wipes them out completely. The only record of that activity may be the memory capture, and it is gone the moment the machine restarts.

What survives a reboot but can still change

Disk artifacts such as file system metadata, registry hives and event logs survive a restart, but they are not frozen. Normal use keeps writing to them. Logs roll over, temporary files are cleared, and a cleanup script can rewrite registry keys. The examiner wants them in their current state, captured under an image and a hash, before anything else touches the disk.

When containment has to come first

If the attacker is actively exfiltrating data or spreading to other machines, stopping the damage may outweigh preserving memory. In that case, isolate the affected network segment or disconnect the machine, and write down the time and the method. Do not power it off unless the examiner or counsel has agreed to it. The order of collection matters, so the most fragile evidence is captured first, and the examiner should set that order.

What do digital forensics services include in a corporate breach investigation?

The National Institute of Standards and Technology's guide to forensic examination of digital evidence describes four steps: assessment, acquisition, examination and reporting. Professional firms work through the same sequence, and knowing it tells you what you will receive and roughly when.

Assessment settles scope: which systems are involved, what question the investigation must answer, what data might be in play and what legal obligations apply. Acquisition makes the copies. Examination analyzes them. Reporting turns the findings into a document that counsel, insurers and regulators can read.

Assessment and acquisition

The central product of acquisition is a forensic image: an exact bit-by-bit copy of the storage, including active files, slack space and unallocated space, where deleted material can still be recovered. Court-accepted tools generate a hash value for the image, a fixed fingerprint. If a single bit changes, the hash changes, so anyone can later confirm the copy matches what was taken. Acquisition uses write blockers, which stop the examiner's own tools from modifying the source drive, and validated imagers, so the copy can be defended as accurate.

Not every machine can simply be taken offline. A production domain controller, a file server or a virtual machine cluster may have to keep running for the business to survive. In those cases the examiner uses live capture tools to collect memory and selected volumes while the system runs, and records exactly what was collected and how. That is a trade-off, and it should be discussed with counsel before it is done.

Examination and reporting

Examination works through the images and captures for the questions set at assessment: how the account was created, what else changed, whether data left the network. Reporting then sets out what was found, how it was found and what could not be determined. The report should be readable by a general counsel and by a board member who has not seen the raw data.

How is chain of custody kept, and how is privilege built around it?

How is chain of custody kept, and how is privilege built around it?, Total 360 Security

Chain of custody is a written log of every person who handled the evidence, when they did it and why. Each hash value is taken at acquisition and checked at every handoff, so a later reader can confirm that what reached the lab is what left the server. Anyone who copies a file to a desktop to look at it, even innocently, belongs in that log. An undocumented step is usually the first thing opposing counsel finds, and it can undermine the whole body of work that followed.

Privilege is less a label than a structure. Outside counsel should retain the forensic firm, the engagement letter should state that the work is to help counsel give legal advice, and the forensic work should be kept separate from routine remediation reports, which may not be privileged. Those routine reports matter too, because the company still has to fix the systems. Confirm this structure with your counsel before the first image is made. The rules vary by jurisdiction and by facts, and this is not legal advice; it is a description of how the engagement is usually built.

Chain of custody and hash values

Ask the firm to show you the custody log template before work begins, and to confirm that every transfer will be recorded with a timestamp, a name and a hash check. Keep the original media sealed and stored where access is logged. The examiner works from verified copies.

Privilege is built into the engagement

Texas courts require computer-based evidence to be authenticated before it is admitted, under Texas Rules of Evidence 901 and 902(13) and Texas Business and Commerce Code section 322.013. That makes a clean, documented custody record worth paying for in its own right, whether or not the matter reaches a courtroom. Counsel, not the IT team, should decide how the forensic firm is retained and what the report is for.

What are indicators of compromise, and how do they uncover persistence?

An indicator of compromise is a specific, observable sign that an attacker was present or acted: an account created, a service installed, a file dropped, a connection made to an unfamiliar address. Examiners look for them in a deliberate order, because an attacker who has created an administrative account usually plans to come back.

Start with account and group events. On Windows, event ID 4720 records a user account being created. Event IDs 4728 and 4732 record a user being added to a security-enabled global or local group. An account that appears in an administrative group without an authorized change is the first indicator to confirm. After that, check for new scheduled tasks, new or modified services, changed group policy and additional accounts, since persistence is often spread across several places so that removing one does not end access.

The table below shows the main Windows artifacts an examiner reviews, what each one can show and what it cannot. Treat each one as a single line of evidence. None of them is a verdict on its own.

ArtifactWhat it can showWhat it does not show
NTFS $MFT (Master File Table)File creation, modification and deletion records, and where files were placedWho created a file, or what its contents were
USN journalA sequence of file system changes, including renames and deletions, over a periodWhy a change was made, or whether the journal covers the full period of interest
ShimCache (AppCompatCache)That a program file was present on the system and was indexedThat the program ran. Presence is not execution
AmcacheProgram execution and installation records, with file hashes and paths in many casesWhat the program did while it was running
PrefetchThat an executable ran, with run counts and last-run times, when the feature is enabledActivity beyond the fact of execution, and is often disabled on servers
ShellBagsFolders a user opened and viewed in Windows ExplorerWhether any file in those folders was copied or opened
Recycle BinFiles a user deleted through normal means, with original paths and deletion timesFiles removed by other methods, or files still present elsewhere
Windows event logsLogons, account changes, process creation and policy changes, if logging was configuredEvents that were never logged, or records that rolled over before export

Start with account and group events

Confirm the account creation time, the creating account, and every group it joined. Then compare those times against your change records. An authorized administrator and a compromised one can look identical in a single log line, so the examiner needs the surrounding context.

Testing an indicator before it goes in a report

Every indicator should be tested against a second, independent source before it appears in a finding. A ShimCache entry showing a tool was present does not prove the tool was used. A prefetch file showing a run does not prove what the tool did. Examiners who report a single artifact as proof of execution will be challenged, and the challenge usually succeeds.

Proving data left the network

Proving that someone looked at data is much easier than proving that data was taken. Check network egress records, firewall and proxy logs, cloud-sync logs, browser artifacts and folder-navigation traces. Then state plainly where the record stops. No evidence of exfiltration is not the same as evidence that nothing was taken, and the report should say so.

What must the forensic report show for an insurer and a regulator?

Write the report for two readers at once: counsel, who will test every sentence, and a board member who will read it cold and needs to understand what happened and what is still unknown. Keep the findings in plain language, with timestamps and the source of each one. Separate what the logs show from what the examiner infers, and list the limits of the work without hedging them into vagueness.

Be realistic about what the report can do. It can establish facts, document the response and support a claim. It cannot promise that a claim will be paid, and no firm can honestly promise that a claim will not be denied or reduced.

Does a Texas breach notice turn on acquisition or access?

Under Texas Business and Commerce Code section 521.053, the notification decision turns on whether personal information was acquired, not merely accessed. A report that only says an account was accessed does not answer that question, and counsel will need more to decide whether notice is required. Ask the examiner to address acquisition directly, to state the evidence for and against it, and to say what could not be determined. An honest "cannot determine" is more useful than an inference dressed up as a finding.

The stakes are real. SecurityWeek reported in 2026 that a Texas-based healthcare firm, AngMar Management Services, was among breaches compromising more than 250,000 individuals, which triggered state notification duties. Mid-market organizations do not have to be large to face the same obligations.

What the carrier needs to see

Read your cyber policy before you hire anyone. Many carriers require notice within a set window and may expect you to use particular vendors or obtain approval before engaging a firm. A forensic firm hired outside those terms can put coverage at risk even if the technical work is excellent. Ask your broker to confirm the notice window and the panel requirements in writing, and bring them into the conversation early.

Should the IT provider investigate, or an independent forensic firm?

The answer is usually both, with clear roles. Your existing IT provider is essential for facts about the environment: how the network is laid out, which systems hold what, what was changed in the last quarter and who has administrative rights. But it should not be the party grading its own response, especially if it created or maintained the compromised account. Independence is what makes the findings usable in front of an insurer or a regulator.

Before you engage any forensic firm, put these questions to it in writing and keep the answers:

  • Who is the named examiner, and what is their training and prior testimony?
  • What access controls protect your evidence in the firm's lab?
  • What is the full inventory of tools the firm uses, and their versions?
  • Can you provide a current certificate of insurance?
  • What is the retention and destruction policy for evidence and for work product?
  • Has the firm given testimony in Texas courts, and in what matters?
  • What conflict checks will you run against the parties involved?
  • Is every report subject to peer review before it is delivered?

A firm that answers these clearly is one you can work with. A firm that cannot is telling you something about how its findings will hold up.

Total 360 Security works in this space as the program and governance layer rather than as the forensic lab. Our role is to help a client run the environment it needs for a defensible response: clear ownership, the right logs kept, and a documented process for bringing in independent examiners. Check our overview of what a virtual CISO covers if you want to see how that work is organized.

How does readiness decide whether an investigation can answer the board?

Most of the evidence an investigation will need is decided long before any incident. Log retention periods, identity controls, asset inventories and backup integrity determine whether the questions a board asks after a breach can be answered at all. If domain controller logs roll over in three days, no examiner can recover what happened on day four. If nobody knows which servers hold personal data, no one can say what was acquired.

That is why incident readiness belongs inside an ongoing Enterprise Security Risk Management program rather than in a binder on a shelf. Total 360 Security designs, runs and reports security programs that cover all 13 risk domains, from physical and cyber controls through business continuity, crisis management and board reporting. The same discipline that keeps those domains current is what makes a forensic response defensible when it is needed. You can read more in our guide to what enterprise risk management covers.

If you want to know whether your current logging, identity and backup arrangements would support an investigation like the one described here, book a 30-minute risk discussion through our consultation page, or review our approach to enterprise security risk management. You can also send the contact inquiry or call 817-677-0515 to review your incident readiness and digital forensics preparedness. Imaging drives and giving legal advice are work for a qualified forensic examiner and your own counsel.

Frequently asked questions

How long does a corporate digital forensics investigation take?

Typical Texas engagements, scoped with named deliverables, look like this: imaging in 1 to 3 business days, artifact recovery in 1 to 2 weeks, exfiltration analysis in 2 to 4 weeks, and the expert report and any testimony in 2 to 6 weeks. The number of systems involved and whether testimony is needed will change these figures, so treat them as typical rather than guaranteed.

What is a forensic expert called?

Usually a digital forensic examiner or forensic analyst. Ask the firm for the named examiner, their training and their prior testimony in writing. Total 360 Security's leadership holds CPP, CISSP and CISM credentials and is Texas DPS-licensed, but those describe program leadership and are not a substitute for a named forensic examiner.

Does Texas breach notice depend on whether data was acquired?

Under Texas Business and Commerce Code section 521.053, the decision turns on whether personal information was acquired, not merely accessed, and a report that shows only that an account was accessed does not answer that question. Counsel decides what notification requires. The examiner's job is to address acquisition directly and to state what could not be determined.

What does a cyber insurer expect in a forensic report?

Timestamped, sourced findings, a clear line between what is shown and what is inferred, the limits of the work, and notice within the window the policy sets. Check the policy before hiring a firm, because carriers may expect particular vendors. No firm can promise that a claim will not be denied or reduced.

Are digital forensics services in demand?

Yes. MarketsandMarkets sizes the US digital forensics market at $3,952.2 million in 2025, projected to reach $6,160 million by 2030 at a 9.3% compound annual growth rate, driven by rising cybercrime and regulatory requirements [1]. Demand is growing, and that makes it more important to choose a firm carefully rather than in a panic.

Total 360 Security provides virtual Chief Security Officer, vCISO, and Enterprise Security Risk Management programs for mid-market organizations. They design, run, and report security programs covering all 13 risk domains rather than just offering advisory decks or point solutions. The firm is Texas DPS-licensed with CPP, CISSP, and CISM credentials.

Serving Texas, California, Nevada, New Mexico.