MSP Security Assessment
Choose the right evidence-led MSP security assessment for a prospect, an authorized tenant, or a verification step.
Open the related path →ASSESS · SOLUTION
Use NIST CSF functions as a conversation map for small-business evidence, ownership, and explicit unknowns.
Run a free domain scoreJoin Open Beta
EVIDENCE · INSIGHT · PROOF
Keep the dated observation and source.
Separate the finding from its possible consequence.
Assign an owner, prerequisites and estimated effort.
Your hourly rate in Settings × LOE in hours.
Reassess against the baseline; record what changed.
Last reviewed September 25, 2026.
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.
Use Identify, Protect, Detect, Respond, and Recover as questions for evidence and ownership. A framework gives the conversation a shared vocabulary. It does not create evidence that the source cannot read.
Each row should say what was seen, why it matters, who owns the decision, and what is still unknown. This turns a framework conversation into a sequence of choices instead of a scorecard with no route forward.
No. Recovery, response, and ownership need operational evidence, customer answers, or a supported tenant source. A quiet surface is not a clean control.
The MSP starts with a public mail-authentication observation, connects it to Protect, names the owner of mail policy, and asks whether the renewal or payment process needs stronger enforcement. The other functions remain open questions.
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.
SCOUTz begins with the least intrusive source that can answer the question. 35 public sources for a domain scan; 92 sources with read-only Microsoft 365 consent. See the methodology for the full unit ledger.
Every finding carries authored business-language explanation, consequence, recommendation, and the evidence it came from. 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.
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.
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.
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.
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.
No. SCOUTz keeps evidence states and unknowns visible instead of collapsing them into a single maturity or security number.
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
Choose the right evidence-led MSP security assessment for a prospect, an authorized tenant, or a verification step.
Open the related path →Deliver an MSP-branded security assessment with client-safe explanation, operator evidence, and clear source boundaries.
Open the related path →Bring dated evidence, clear limits, and useful questions.