FourCore ATTACK: Google SecOps attack simulation

Know whether Google SecOps stops and sees a real attack. FourCore ATTACK runs safe endpoint, network and email attacks and reads Google SecOps to score every step.

Simulated step

Test payload sent to a mailbox as an attachment

Blocked.

Google SecOps event for the test email

EndpointNetworkEmail

Example. Names removed.

How Google SecOps scores a simulation.

FourCore ATTACK shows whether Google SecOps stopped or saw each step of a real attack, and what to change when it didn't.

  1. 01 · Simulate

    A safe attack runs

    FourCore ATTACK runs real attacker techniques, mapped to MITRE ATT&CK, against your endpoint, network and email controls. Nothing destructive runs, and each test cleans up after itself.

  2. 02 · Read

    Google SecOps is checked

    FourCore reads the security events in Google SecOps for each test and ties each result to the files and activity from each test.

  3. 03 · Score

    Blocked, detected or missed

    Every step gets a result with the evidence behind it. A gap gets a fix to apply and the same test runs again to confirm it's closed.

Simulations Google SecOps can score

  • Endpoint
  • Network
  • Email

Test payload sent to a mailbox as an attachment

Blocked

Google SecOps event for the test email

Example

Built for Google SecOps.

Endpoint, network and email in one place
See how your defenses hold up across endpoints, the network and email, from the logs Google SecOps already collects.
Credit only for real detections
A step counts as detected only when Google SecOps saw the simulated activity itself.

What each result means.

Every simulated step gets one result, with the Google SecOps evidence behind it.

Blocked
A control stopped the step.
Detected
The step ran and Google SecOps recorded it as a threat.
Missed
The step ran and nothing in Google SecOps matched it. You get a fix and a retest.

Questions

How do you test whether Google SecOps blocks phishing?

FourCore ATTACK sends safe test emails with malicious-style attachments to test mailboxes, then reads Google SecOps to show which were blocked and which were delivered, with a fix for each gap.

How do you test Google SecOps against a real attack?

Run a breach and attack simulation. FourCore ATTACK safely runs the techniques a real attacker would use against your endpoint, network and email controls, and Google SecOps's own data shows what it stopped and what it missed.

Which simulations can Google SecOps score?

Endpoint, Network, Email simulations.

How does FourCore know whether Google SecOps caught an attack?

FourCore reads the security events in Google SecOps for each test and ties each result to the files and activity from each test, so every step shows whether it was blocked, detected or missed.

Does FourCore change anything in Google SecOps?

No. FourCore only reads from Google SecOps, through its API, with credentials your team creates.

Is it safe to run simulations?

Yes. FourCore ATTACK simulations are controlled and non-destructive, run within rules of engagement you agree, and clean up after themselves.

Test Google SecOps against a real attack.

Bring a threat or a technique. We run it safely and review what was blocked, detected or missed with you.