Skip to content

Template, read 16 November 2026

Red team rules of engagement: what they cover and a template

Open the scoping sheetSee the frameworks table

Download the templates

Free to reuse under CC BY 4.0. Open the scoping sheet to print it.

What are rules of engagement in a red team test?

Rules of engagement are the detailed guidelines and constraints for a security test, set before it starts. NIST says they give the test team authority to conduct defined activities without needing further permission.

SP 800-53 adds that all parties agree to the rules before testing starts, that they should be matched to the techniques adversaries are expected to use, and that rules and contracts can set expectations for protecting information the testers may see.

What goes into a rules of engagement template?

A template needs seven parts, following NIST SP 800-115 Appendix B. The table gives each part, what NIST says it holds and a prompt to fill in. Replace the prompts with your answers.

Table for: What goes into a rules of engagement template
PartWhat it holds (NIST SP 800-115)Fill in
1. IntroductionPurpose, scope, assumptions and limitations, risks, document structure.Who is tested, who tests, why; boundaries; known risks and how they are reduced.
2. LogisticsPersonnel with contact points, test schedule, test site, test equipment.Names and phones; dates and hours; where testers work from; how tester systems are told apart from yours.
3. Communication strategyGeneral communication; incident handling and response with halt criteria and call tree.Meeting rhythm and channels; who can halt the test; call tree; how testing resumes.
4. Target system or networkSystems to be tested, authorized and unauthorized addresses, the exclude list.Address ranges, hosts, applications; systems that must not be touched.
5. Testing executionAllowed and unallowed activities, non-technical components, technical components, data handling.Techniques allowed; social engineering limits; physical access rules; files that may be installed; data rules.
6. ReportingReport contents and frequency, with a template as an appendix.Daily or weekly status; final report layout.
7. Signature pageAccountable parties sign; at minimum the test team lead and senior management such as the CISO.Names, titles, signature, date.

What must the red team test plan add?

For threat-led tests the TIBER-EU red team test plan adds scenario details. It must give the communication channels, the tactics, techniques and procedures allowed and not allowed, ethical limits for social engineering and how privacy is safeguarded, and the risk management steps the testers will follow.

Each scenario also needs the simulated threat actor and its goals, the target functions and systems, the flags, each attack path with prerequisites and possible leg-ups, the schedule split into in, through and out phases, and any particulars of the infrastructure.

Who signs the rules of engagement?

At a minimum the test team lead and the organization's senior management sign. NIST names the chief security officer, chief information security officer and chief information officer as examples.

In TIBER-EU, the control team and the authority approve the test plan, and changes after approval need the control team lead and the test managers. See legal authorization for the letter that goes with it.

Sources

  1. NIST CSRC Glossary, rules of engagement, read 16 November 2026
  2. NIST SP 800-115, Technical Guide to Information Security Testing and Assessment, September 2008, read 16 November 2026
  3. NIST SP 800-53 Rev. 5, control CA-8 Penetration Testing, read 16 November 2026
  4. European Central Bank, TIBER-EU Red Team Test Plan Guidance, 2025, read 16 November 2026
  5. EUR-Lex, Commission Delegated Regulation (EU) 2025/1190 (TLPT technical standards), read 16 November 2026

Last reviewed 16 November 2026.