SecureAxis Responseby SecureAxis

In development · part of SecureAxis Risk pilots

SecureAxis decides. Your EDR enforces.

Response actions through the EDR you already run, each with a reason, a named approver and a record your auditors can read.

SentinelOne first. Microsoft Defender and CrowdStrike next. No second agent on every machine.

Illustration with sample data.

Use the EDR you already paid for

Another agent on every laptop means another thing to deploy, patch and argue about. Response works through the one you have.

  • Bring your own EDR. SentinelOne today; Microsoft Defender and CrowdStrike are next.
  • A short list of actions. Isolate a device, release it, or block a file hash.
  • Every action needs a reason and a person. Nothing happens without a stated reason and a named approver.

How it works

  1. RecommendAn analyst, or a rule in SecureAxis Risk, proposes an action with the reason behind it.
  2. ApproveA named person approves it. With four-eyes turned on, the approver has to be someone other than the person who recommended it.
  3. Enforce, or rehearseThe action goes to your EDR. Until you switch enforcement on, it runs as a dry run and records exactly what would have been sent.
  4. Keep the recordWho recommended, who approved, what was sent and what happened, on the record for your auditors.

Every action is evidence

Incident response usually leaves its trail across chat threads, tickets and console logs. Response keeps one record per action, alongside the rest of your evidence in SecureAxis Risk, so the answer to “who isolated that machine, and why?” is a single lookup.

Dry-run mode makes it safe to start: run it for weeks, read what it would have done, and turn enforcement on only when you trust it.

Where it stands

Response is in development as part of SecureAxis Risk. The SentinelOne connection comes first; Microsoft Defender and CrowdStrike follow. There are no customers yet.

Pilots are open for a small number of organisations, starting in dry-run mode.

Questions

Does it install another agent?

No. Response sends actions through the EDR you already run, so there is no second agent on every machine.

Which EDR products does it support?

SentinelOne first. Microsoft Defender and CrowdStrike are next.

What actions can it take?

Isolate a device, release it from isolation, and block a file hash. Each one needs a reason and a named approver.

Can we try it without it doing anything?

Yes. Dry-run is the default: every approval records exactly what would have been sent, and nothing reaches your EDR until you switch enforcement on.

Can the same person recommend and approve?

Not when four-eyes is turned on. The approver then has to be someone other than the person who recommended the action.

Is it a separate product from SecureAxis Risk?

It is being built as part of SecureAxis Risk, and its records sit in the same evidence vault. Pilots include both.

Request a pilot

We're opening pilots for a small number of organisations. Tell us about your environment and we'll reply by email.

Frameworks in scope (optional)
Also interested in (optional)

We reply by email from hello@secureaxis.net. No newsletter. Prefer email? Write to hello@secureaxis.net.