rules of engagement
A written agreement that sets out what security testers may and may not do, including the targets, dates, methods and who to call in an emergency.
In more detail
Attacking someone else's systems without permission can be a crime, so the rules of engagement are signed before any scan or test starts. They name the systems in scope and those off limits, the allowed techniques, the testing windows, how sensitive findings are handled and who to call if something breaks. Testers keep a copy to hand as proof that their activity is authorised.
Example
Before testing a vendor's API: written permission, scope, times, and who to call if something breaksRelated terms
- penetration test — An authorised, simulated attack in which testers try to break into a system the way a real attacker would, to find weaknesses before criminals do.
- second-party audit — An audit where a customer, or someone acting for it, checks one of its suppliers.
- vendor lifecycle — The stages an organisation takes a supplier through: choosing it, signing the contract, onboarding it, monitoring it and finally offboarding it.
Taught in
- Vendor & Third-Party Risk Management Programs — Cybersecurity Fundamentals, GRC & Cryptography