Everyday Guidebooks
Cover of The Authorized Tester's Scope

Cybersecurity & IT

The Authorized Tester's Scope

A Practical Guide to Defining Boundaries and Rules of Engagement Before a Security Assessment

by Todd Michael

Available now

A security assessment starts long before the first technical test. It starts with a shared understanding of what is permitted, when work may happen, what must not be touched, and whom to call if something goes wrong.

The Authorized Tester's Scope is a practical starting point for readers exploring ethical hacking for beginners and preparing for security certification study. Through fictional workplace scenarios, you will learn to turn a vague request into a documented set of boundaries, identify gaps in authorization, and distinguish a confirmed target from an assumption.

Build a scope record that covers systems, testing windows, prohibited actions, and emergency contacts. Practice asking clarifying questions, recording decisions, and pausing work when access, ownership, or conditions change. Checklists and short exercises help you apply each lesson without requiring a home lab or advanced technical skills.

This independent guide teaches assessment preparation, not legal advice or a substitute for an organization's authorization process.

Contents
  1. 1. Permission Before Testing
  2. 2. The People Behind the Permission
  3. 3. From Request to Written Authorization
  4. 4. Naming Permitted Targets
  5. 5. Shared Systems and Third-Party Boundaries
  6. 6. Setting Testing Windows
  7. 7. Documenting Prohibited Actions
  8. 8. Emergency Contacts and Escalation
  9. 9. Rules of Engagement That People Can Use
  10. 10. Resolving Ambiguous Scope
  11. 11. When Conditions Change
  12. 12. Protecting Assessment Records
  13. 13. Scenario Practice for Certification Candidates
  14. 14. Build and Review Your Scope Package
  15. Other Books by Todd Michael

Read a sample: 1. Permission Before Testing

Maya has just joined the security team at a fictional company called Northstar Outfitters. On Tuesday morning, a colleague from sales sends her a message:

> “We’re launching the new customer portal soon. Can you check it for security issues? Anything you find would be helpful.”

Maya wants to make a good impression. The portal’s public address is included in the message, and she knows several ways to begin examining a website. But before opening a testing tool, she notices what the request does not say.

Does the sales colleague have authority to approve an assessment? Is the public website the only intended target, or does the request include the systems behind it? Is the portal connected to live customer information? When can testing take place? Who should Maya contact if the site becomes unavailable?

The message gives Maya a reason to start a conversation. It does not yet give her a dependable basis for testing.

That distinction is the starting point for this book. Security assessment is not defined only by the techniques an assessor uses or the good intentions behind them. It is also defined by permission, boundaries, and the ability to explain what actions were approved before those actions begin.

An authorized security assessment is a review of systems, applications, services, or processes conducted with appropriate permission and within agreed limits. Its purpose is to help an organization understand security conditions, identify weaknesses, or evaluate particular controls.

The assessment might involve reviewing configuration information, interviewing staff, examining an application, or performing technical tests. Its exact form depends on the objective and the authorization. A narrow review of a test application and a broader assessment of a production environment are not interchangeable simply because both are called security testing.

Authorization connects the activity to the people and resources involved. It should answer questions such as:

- Who is permitted to perform the work? - Who is approving it, and what resources can that person approve testing against? - What is the assessment intended to accomplish? - Which targets and activities are included? - When may the work occur? - What restrictions and communication procedures apply?

The answers need to be recorded in a form the relevant participants can use. Depending on the organization and engagement, that record might be an approved assessment plan, a signed agreement, a documented internal approval, or a package combining several records. The label matters less than whether the record clearly establishes the permission and operating boundaries needed for the work.

A person’s enthusiasm about security does not create that permission. Neither does the fact that a system is reachable from the internet, appears in a search result, or belongs to an organization that has invited the assessor to discuss an engagement. Accessibility is a technical condition; authorization is a decision made through the appropriate process.

Nor should authorization be treated as a general badge that allows an assessor to improvise freely. Permission to review one application does not automatically extend to every server, vendor service, user account, or connected environment encountered along the way. The assessor’s job includes recognizing where the documented permission ends.

In Maya’s situation, the sales colleague may have a legitimate business reason to ask for help. The upcoming launch could make an assessment valuable. The colleague might even be the person who raised the project internally.

Those facts make the request worth pursuing. They do not resolve the authority question.

A request for help communicates interest or need. Authorization establishes that the proposed work has been approved by someone with appropriate authority, for identified resources and activities, under stated conditions. One person may be able to provide both, but Maya should establish that rather than assume it.

Consider the difference between these two messages:

> “Can you check the customer portal before launch?”

> “The approved assessment covers the production customer portal at the identified address, during the agreed testing window, using the methods and restrictions in the assessment plan. The application owner and designated approver have confirmed the plan.”

The second message contains more useful direction, but even it refers Maya to the underlying plan. She would still need to read that plan, confirm that it applies to her work, and understand any unresolved conditions. A confident-sounding message is not a substitute for an accessible, internally consistent authorization record.

The distinction protects the people requesting the work as well as the assessor. A colleague may not know that the portal relies on a vendor-operated identity service or that a launch rehearsal is scheduled for the same afternoon. Asking questions gives the organization a chance to coordinate those details before testing creates confusion or disruption.

Maya can respond constructively without acting prematurely:

> “I’d be glad to help scope a review. Before testing begins, could you connect me with the portal owner and the person who can approve the assessment? We’ll also need to confirm the targets, timing, restrictions, and operational contacts.”

This is not a refusal to help. It is the first useful step toward helping.

Scope describes what is included in an assessment and, where necessary, what is excluded. It turns a broad objective into a boundary the assessor can recognize while working.

For Maya, “the customer portal” sounds specific until she asks what the phrase covers. It might refer to the public website, the application behind it, an application programming interface, a test environment, administrative features,…

More Cybersecurity & IT

Cover of The White Hat Bible, Volume 1The White Hat Bible, Volume 1Available nowCover of The White Hat Bible, Volume 2The White Hat Bible, Volume 2Available nowCover of The White Hat Bible, Volume 3The White Hat Bible, Volume 3Available nowCover of The White Hat Bible, Volume 4The White Hat Bible, Volume 4Available nowThe White Hat Bible, Volume 5Available nowCover of The White Hat Pocket GuideThe White Hat Pocket GuideAvailable now

About Todd Michael

Todd Michael is an American author and the founder of ToddMichael.tv. He writes practical, plain-English books on money, health, preparedness, technology, games, humor and more.

About the author Todd Michael · Todd Michael’s author site

Part of the ToddMichael.tv network.