Disabled security agent: when EDR or antivirus goes quiet

Attackers often stop or tamper with endpoint protection before acting. How to detect agents going silent, service stops, and exclusion changes, and how tamper protection and heartbeat monitoring catch them.

Lesson 9 of 16 · 10 min read · practice only with authorization

Diagram

An endpoint that stopped reporting

Follow the path. One example at a time.

Step 1 of 4

Heartbeat

The console shows a host last seen hours ago while it is still on the network.

Illustration: Heartbeat
host FIN-LT-044   last_seen 2026-11-02 21:14   network: DHCP lease renewed 2026-11-03 02:10

The example on the open step is one illustration, or the fix you can paste into an application you own.

What this page is made of

3 pieces. Each one says what fails, who is affected, what you would notice, and what you change.

  1. Silent agents

    What fails
    An agent that stops sending telemetry hides everything after it.
    Who is affected
    Investigators, and the host’s user.
    What you would notice
    Hosts seen by the network but not by EDR.
    What you change
    Correlate EDR heartbeats with DHCP, VPN, or identity sign-ins.
  2. Exclusions

    What fails
    Adding a folder exclusion lets files there run unscanned.
    Who is affected
    The host.
    What you would notice
    Defender event 5007 with new exclusion paths.
    What you change
    Manage exclusions centrally and alert on local changes.
  3. Tamper protection

    What fails
    Without it, local admins can stop the agent.
    Who is affected
    Every endpoint.
    What you would notice
    Tamper protection off in the console.
    What you change
    Enable it tenant-wide.

Linux and macOS

On Linux, watch for systemctl stop on the agent unit in auditd or journald; on macOS, watch for unloading the agent’s launch daemon. Heartbeat correlation works the same everywhere.

$ journalctl -u falcon-sensor --since "2026-11-02" | tail -3
Nov 02 21:14:07 web-07 systemd[1]: Stopping falcon-sensor...
Nov 02 21:14:08 web-07 systemd[1]: falcon-sensor.service: Deactivated successfully.

Check yourself

Recognition and the fix. Nothing here is a procedure.

1 / 3

A laptop renewed its DHCP lease at 02:10 but EDR last saw it at 21:14. What does that suggest?

Sibling techniques

Pages at the same depth, plus a lab and a glossary card for this one.

This page stands on its own. The lab and the glossary card are the next reading.

Practice

  1. LabControl benchA failure is described. Choose the control that changes the outcome.

Glossary

  1. CardDisabled security agentThe tool that should report tampering has been stopped.