⚔️ Attack Smarter. Defend Harder. Get the OFF / DEF Training Bundle Now ⚔️

Assumed Breach Assessment

Already Inside.
Now What?

Red Siege testers start where real attacks do, as a compromised user inside your network, and show how far an attacker could get.

Red Siege knight illustration: Swordsman

Start Where the Attacker Starts

A traditional internal test plugs a laptop into your network and starts scanning. Real attackers rarely work that way: they phish a user or use stolen credentials and begin with that person’s access. An Assumed Breach Assessment starts there, as a compromised employee or a malicious insider, and asks what that access can reach. You learn how attackers could exploit the gaps already inside your network, whether your tools and team catch them, and what to fix first.

Get Started

A Realistic Starting Point

Testing begins from a real user’s access on your standard workstation, the way most breaches actually begin.

Paths to Your Data

We follow an attacker’s path to the data and processes that matter most to you, not just to domain admin.

Defenses Put to Work

See whether your security tools, processes, and people spot and contain an attacker who is already inside.

Fixes You Can Verify

Prioritized findings with short- and long-term recommendations, a validation step for each fix, and evidence that supports compliance.

Our Approach

How We Test From the Inside

Every engagement follows the same four steps, built around your data and your environment.

Red Siege knight illustration: Laptop Knight
  1. Start with what would hurt

    Before testing we ask which data or process, if lost, stolen, compromised, or destroyed, would have the biggest impact on your organization. That answer becomes the target of the test, because an attacker is after your data, not a trophy.

  2. Set up realistic access

    We agree on the scenario, a phished employee or a malicious insider, and how we connect: a shipped laptop, VPN, remote desktop, or on site. We ask for your standard workstation image and a representative account, ideally a recently separated employee’s, not a clean account created for the test.

  3. Move like a real attacker

    From that foothold we do what attackers do: hunt file shares and Active Directory for credentials, target service accounts, test password reuse, and move toward your critical data. We try the simple paths before the sophisticated ones, and domain admin is a tool along the way, not the finish line.

  4. Report for leaders and defenders

    An executive summary that shows business impact and root causes, technical findings rated by risk, short- and long-term fixes, and a validation section for each finding so your team can confirm the fix without waiting for a retest.

Built Around How Breaches Really Start

Attackers often don’t need to break in. They phish a user or log in with stolen credentials, then look around. We do the same, using the tools already on the workstation and the access a real employee has. Telling your executives we reached domain admin means little. Showing them who could reach your trade secrets or customer records, and how, gives them something to act on,

because getting in is only the beginning.

Get Offensive Now

“Domain admin is a tool. It is not a destination. It is not where we are trying to arrive.”

Mike Saunders, Principal Security Consultant, on why an assumed breach test goes after the data, not the domain controller. Watch the SiegeCast

Details on Assumed Breach Assessment

Mike Saunders walks through an assumed breach test against a well-funded, well-defended organization, where one set of credentials on an overly permissive file share led, step by step, to full compromise. He breaks down each failure in the chain and what the client could have done to stop it.

Learn More