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 Discovery Questionnaire for MSPs
Use an evidence-first security discovery questionnaire with plain-language questions tied to observable states and unknowns.
Run a free domain scoreJoin Open BetaLast reviewed September 25, 2026.
A security discovery questionnaire works better when each question follows an evidence state. SCOUTz helps an MSP ask plain-language questions after showing what is known, what is unknown, and which source would answer the next part.
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.
Why put evidence before self-reported answers?
Evidence gives the customer something concrete to correct, explain, or own. A questionnaire that begins with broad claims invites optimistic answers. A sourced observation makes the next question specific without being accusatory.
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.
Which questions should come first?
Questions about ownership, purpose, last review, exceptions, and the next source needed. The MSP can ask who decides, how the control is checked, what happens when it fails, and how a change will be verified.
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.
How should unknowns be handled?
Keep them visible and write the requested evidence beside them. Unknown means the current source did not establish the answer. It is not a green response and not a reason to invent one.
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
Observed stateA correction or ownership questionNot the complete operational story
Unknown stateA permission or evidence requestNot a failure or a pass
Customer answerContext and next actionShould remain labeled as self-reported
Worked example
Instead of asking whether email security is good, the MSP shows the published policy, asks who owns the sender list, asks when it was reviewed, and asks what record would demonstrate a change.
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.
How many discovery questions should an MSP ask?
Ask only the questions needed for the decision in front of you. SCOUTz helps prioritize them from the evidence rather than starting with an unbounded questionnaire.
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 Assessment for Prospects
Prepare a prospect conversation with a sourced security assessment, explicit unknowns, and a 30-minute first-meeting script.
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.