External Attack Surface Review for MSPs
Use a passive external attack surface review to explain what a prospect publishes, what it means, and what it cannot prove.
Open the related path →PROSPECT · SOLUTION
Security Assessment for Prospects
Prepare a prospect conversation with a sourced security assessment, explicit unknowns, and a 30-minute first-meeting script.
Run a free domain scoreJoin Open BetaLast reviewed September 25, 2026.
A security assessment for a prospect should create a responsible reason to talk, not pretend to know the customer's internal environment. SCOUTz starts with public evidence, turns findings into questions, and gives the MSP a 30-minute first-meeting path that begins somewhere real.
SCOUTz keeps the source, timestamp, boundary, and next choice together. That makes the page useful to the seller, the owner, and the operator who receives the work after the meeting.
What should the first five minutes cover?
State why the account is relevant, show one dated observation, and ask permission to test whether the consequence matters. The goal is a shared question, not a surprise report or a forced product demonstration.
The practical test is whether another person can understand the claim, identify its source, and decide what should happen next without treating an unknown as a pass.
What should the middle of the meeting do?
Move from observation to ownership, current practice, and the next evidence needed. A useful question names what was observed and what remains unknown. It lets the owner or IT contact correct the record without losing the thread.
The practical test is whether another person can understand the claim, identify its source, and decide what should happen next without treating an unknown as a pass.
What should the last five minutes produce?
A bounded next choice: stop, authorize a deeper review, or scope a first work item. The meeting should end with an owner and a next step, not an unqualified promise to send a generic proposal.
The practical test is whether another person can understand the claim, identify its source, and decide what should happen next without treating an unknown as a pass.
Evidence, support, and boundary
Evidence stateWhat it supportsBoundary
One dated public observationA specific opening questionNot proof of current compromise
Business consequence languageAn owner-level conversationNot a modeled dollar loss
Explicit unknownsA permission requestNot permission to collect everything
Worked example
Minute 1: explain why the account is worth attention. Minute 8: show the mail-authentication record. Minute 18: ask who owns the policy and what the renewal requires. Minute 28: agree whether a customer-approved review is useful.
This example is deliberately narrow. A finding can start a useful business conversation without proving a breach, a clean environment, a complete compliance program, or a commercial outcome. The report should say which of those statements it can support and which remain for the MSP and customer to establish.
How SCOUTz gets the MSP there
SCOUTz begins with the least intrusive source that can answer the question. The public domain layer dispatches 35 collectors and can reach 123 distinct finding types. When a customer approves the next step, the read-only cloud layer is a superset with 93 collectors and 370 reachable finding types. Platform-wide, 601 finding types across 91 emitting modules include fusion and correlation logic that runs on top of collector output.
Every finding carries authored business-language explanation, consequence, recommendation, and the evidence it came from. The ledger separates 440 scored findings, 107 context observations, and 22 declared non-reads. A check that could not be read appears as NOT ASSESSED THIS SCAN, so the next choice is visible instead of hidden inside a score.
The MSP still owns authorization, interpretation, customer communication, remediation, and the final commercial decision. SCOUTz supplies the record and the route. That boundary is what makes the output safe to use in a real relationship.
Frequently asked questions
What does SCOUTz actually read?
The public domain layer reads disclosed public records and signals. A customer-approved Microsoft 365 review reads supported configuration and metadata through a read-only connection. SCOUTz does not read messages, files, documents, chats, or prompts.
Does an unknown result count as clean?
No. A check that could not be read is declared as a non-read. It remains visible on the record and is not converted into a pass or a blended score.
Can an MSP use its own branding?
Yes. Client-safe output is designed for the MSP's name, logo, colors, contact details, and delivery motion while operator evidence remains available to the team doing the work.
What happens after the first result?
The MSP reviews the evidence, agrees the next action with the customer, performs the work through its own process, and uses a supported rescan or source refresh to show what changed.
Does a prospect assessment replace discovery?
No. It makes discovery more specific. The evidence gives the MSP a starting question, while the prospect supplies context, ownership, priorities, and the decision path.
Keep the evidence attached to the work.
Read the methodology, review the trust boundary, see the sample report, compare pricing, and run the public tools before you choose the next step.
RELATED SOLUTIONS
Security Discovery Questionnaire for MSPs
Use an evidence-first security discovery questionnaire with plain-language questions tied to observable states and unknowns.
Open the related path →SCOUTz OPEN BETA
Point SCOUTz at your next prospect. Walk in with a defensible answer.
Join Open Beta with a real MSP workflow. A person reviews every application before a workspace goes live. SCOUTz runs without an agent or install and never changes a configuration on its own.
SCOUTz prepares the conversation. The relationship and the sale stay yours.