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
Connect cyber-insurance questions to dated evidence, clear ownership, and an honest list of what remains unverified.
Run a free domain scoreJoin Open Beta
EVIDENCE · INSIGHT · PROOF
What does the supported source show?
Which operational answers need the customer or MSP?
What remains unresolved or untested?
Document the owner and obtain appropriate insurance advice.

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.
Because a yes or no answer can hide scope, exceptions, date, and ownership. A source-labeled record gives the MSP something to validate with the customer and something to revisit when the application or renewal changes.
Supported public and read-only tenant observations that relate to application questions. The MSP must still interpret the carrier's exact wording and gather evidence outside the product where the source cannot answer the question.
Anything that depends on policy execution, recovery testing, incident history, or a source the review did not read. Unverified is a useful work item, not an admission to hide.
The application asks whether MFA is enforced. The MSP attaches the supported tenant state, lists exceptions and unread accounts, names the owner, and records the source date. It does not turn one policy object into a guarantee of every sign-in path.
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. It helps organize defensible evidence and unknowns. The carrier, broker, customer, and MSP decide how the application is completed and interpreted.
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.