White-Label Security Assessment for MSPs
Deliver an MSP-branded security assessment with client-safe explanation, operator evidence, and clear source boundaries.
Open the related path →ASSESS · SOLUTION
Choose the right evidence-led MSP security assessment for a prospect, an authorized tenant, or a verification step.
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.
Start with public evidence when the account is still a prospect. The domain layer dispatches 35 collectors and can reach 123 distinct finding types without credentials or an agent. It can establish published configuration and exposed signals, not internal operations.
Use a customer-approved cloud review after the question is clear and the customer understands the access boundary. The cloud path is a superset: 92 sources and 370 reachable finding types through supported, read-only Microsoft 365 configuration and metadata.
Pin the starting evidence, perform the agreed work, and rescan only the supported source. A verification result should name the source, timestamp, check, and remaining unknowns. It should not imply that one changed record proves the entire environment is safe.
A prospect's mail policy is visible publicly, but its administrator assignments are not. The responsible report shows the policy as observed and the administrator question as unknown. The MSP can ask for the tenant review without pretending the public record answered both 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. Domain and cloud evidence retain separate access models and separate grades. A quiet result or unread check never becomes a clean result.
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
Deliver an MSP-branded security assessment with client-safe explanation, operator evidence, and clear source boundaries.
Open the related path →Use a customer-approved, read-only Microsoft 365 posture review for MSP prospects with a clear permission-to-question map.
Open the related path →Bring dated evidence, clear limits, and useful questions.