Skip to content
StrikeCyberStrikeCyber
Field Manual · Concept

Rules of Engagement

Reviewed 13 November 2026Concept 1 min read

Quick answer

Rules of engagement are the agreed boundaries for a penetration test or red team exercise: what is in scope, what techniques are allowed, when testing happens, who to contact, and what to do if something goes wrong. They protect both the organisation and the testers and are agreed in writing before any testing starts.

On this page
01

What They Cover

  • Scope: systems, IP ranges, applications, locations and accounts in and out of scope.
  • Techniques: whether phishing, physical access, denial of service or social engineering are allowed.
  • Timing: testing windows, blackout periods and duration.
  • Contacts: emergency contacts on both sides and how to reach them.
  • Critical findings: how and when serious issues are reported during testing.
  • Data handling: how evidence and any accessed data are protected and destroyed.
  • Stop conditions: when testing must pause, such as signs of a real attacker.
  • Authorisation: written approval from someone with authority over every system in scope, including third-party hosting.
02

Why It Matters

Unclear rules cause outages, legal risk and wasted effort. Clear rules let testers work confidently and produce results you can trust.

03

Common Mistakes

  1. Forgetting to get permission from cloud or hosting providers where required.
  2. Leaving third-party systems ambiguous.
  3. No agreed deconfliction process for red team exercises.
  4. No plan for what happens if testers find evidence of a real compromise.
04

Regulatory and Framework Context

For Australian organisations, formal rules of engagement are expected in regulated testing such as CORIE and APRA-driven assessments.

Latest intel on this topic

Updated hourly from the daily briefing.

Common questions

Who should sign the rules of engagement?

Someone with authority over all in-scope systems, and the testing provider. Third-party owners may also need to authorise.

What if testers find a real attacker?

Good rules of engagement require testers to stop and alert you immediately, then agree next steps.

Change log

  1. 13 November 2026First published.
1300 654 898