Vulnerabilities & Risk

Penetration Testing, Scope and Rules of Engagement

how an ethical hack is planned, run and reported

2 min readupdated by Syed Khaleel Ahmed

A penetration test (pen test) is an authorized, scoped attempt to break into systems the way a real attacker would, followed by a report on what worked and how to fix it. The goal is not to "win" but to give the organization evidence it can act on.[1]

Written permission. A test without authorization is a crime in most places. Before anything starts, both sides agree:

  • Scope: exactly which systems, applications, networks, people and locations are in bounds, and which are off limits.
  • Rules of engagement (RoE): what techniques are allowed (for example social engineering or denial of service?), testing windows, how to handle sensitive data, and an emergency contact if something breaks.
  • Authorization letter: a signed document naming the testers, which they can show if challenged. This is sometimes called a "get out of jail" letter.

Types by knowledge

  • Black box: the tester starts with almost nothing, like an outsider.
  • Grey box: partial knowledge, such as a normal user account.
  • White box: full access to documentation and source code, for the most thorough coverage.

Typical phases

  1. Planning: goals, scope, rules.
  2. Reconnaissance: gather information.
  3. Scanning and enumeration: map hosts, services and users.
  4. Gaining access: exploit weaknesses carefully.
  5. Post-exploitation: see how far access goes, such as moving sideways or reaching sensitive data, without causing harm.
  6. Cleanup: remove tools and test accounts.
  7. Reporting.[2]

The report is the product

A good report has an executive summary for non-technical readers, then detailed findings. Each finding states what was found, where, evidence (screenshots and steps to reproduce), the risk rating and why it matters, and clear remediation advice. Findings are ranked so the team knows what to fix first. A great report also notes what was done well.

A red team exercise goes further: it simulates a stealthy adversary against the organization's people, processes and detection, usually with a broader goal. A bug bounty invites independent researchers to report flaws for rewards under published rules.

Sources

  1. NIST SP 800-115: Technical Guide to Information Security Testing and Assessment
  2. Penetration Testing Execution Standard (PTES)

Test yourself

My notes

Private — saved only on this device, never sent anywhere.