What is breach detection?

Breach detection is the process of identifying unauthorized access to systems or data by analyzing audit logs, sign-in records and other activity across the environment. It matters most against attackers who use real credentials, because no single action they take looks wrong on its own. Only the pattern does.

How long do intruders go unnoticed?

IBM's 2025 Cost of a Data Breach report put the average time to identify and contain a breach at 241 days. Much of that time passes because the intruder signs in with a valid password, often obtained through credential theft, and does work that resembles an administrator's.

What do audit trails record?

An audit trail is a time-stamped record of who did what, from where, and with what result. The sources that matter most for detection are:

  • Identity logs: sign-ins, failed attempts, new accounts, privilege changes and multi-factor prompts.
  • API logs: on object storage and cloud services, every request to read, write, delete or change settings is an API call, and the log records the caller, the action, the target and whether it succeeded.
  • Backup and storage logs: job changes, retention edits, restore-point deletions and console sign-ins.
  • Endpoint and network logs: processes started on servers and unusual outbound transfers.

An attacker with enough access may try to clear logs, which is why copies are streamed to a separate system as they are written.

Why are access keys watched closely?

Object storage and cloud services authenticate programs with access keys rather than passwords. A newly created key, a key used from an unfamiliar network, or an old key that suddenly becomes active is a strong signal, because attackers create keys to keep access that survives a password reset. Alerts on key creation and on first use from a new location catch this early.

Why does correlation matter more than any single alert?

A login at an odd hour, a script that runs once, a file that is deleted: each is ordinary alone. Detection comes from lining them up. Logs flow into a SIEM, a system that collects events from many sources and orders them on one timeline, where a pattern becomes visible: a sign-in from a new location, then a new administrator account, then a new access key, then a bulk deletion.

Many teams send identity and endpoint logs to the SIEM but leave backup and storage audit logs out. Attackers who plan to encrypt production usually work on the backups first, so those logs often hold the earliest evidence, in the form described under backup tampering.

What does detection not do?

Detection finds an attack but does not stop one. An alert that reaches no one changes nothing, and recovery cannot depend on alerts arriving in time. An immutable backup holds whether or not anyone noticed.

Frequently asked questions

What is the difference between breach detection and breach response?

Detection finds the intrusion. Response contains it, removes the attacker and restores affected systems. Detection supplies the start time and scope that response works from.

Can detection work after an attack has ended?

Yes. Retained logs and older restore points help date when the attacker first arrived and what was reached, which matters for notification duties.

Which storage events are worth sending to a SIEM?

Deletion bursts, retention or permission changes, new or unusually used access keys, disabled jobs and failed or unusual sign-ins to the backup console.