ASSESS · SOLUTION

MSP Security Assessment

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
A dated Microsoft 365 review with identity and access findings highlighted for investigation.
Real Microsoft 365 review · client details removed. Planning values are dated examples, not offers. Price current work using your Settings hourly rate × reviewed LOE.

EVIDENCE · INSIGHT · PROOF

Every finding comes with what it means, what to do and how to verify it.

01

Find

Keep the dated observation and source.

02

Explain

Separate the finding from its possible consequence.

03

Plan

Assign an owner, prerequisites and estimated effort.

04

Price

Your hourly rate in Settings × LOE in hours.

05

Verify

Reassess against the baseline; record what changed.

A work plan is an estimate, not guaranteed revenue. The MSP approves and performs the work.

Last reviewed September 25, 2026.

An MSP security assessment should match the sales stage and the evidence the customer has authorized. SCOUTz starts with a bounded public review, adds a read-only Microsoft 365 posture review when the customer approves it, and keeps verification separate from both.

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.

Which assessment should an MSP run first?

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.

When does a cloud review make sense?

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.

How should an MSP verify work?

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.

Evidence, support, and boundary

Evidence stateWhat it supportsBoundary
Public domain reviewA sourced first conversationCannot establish internal identity, endpoint, or recovery practice
Customer-approved Microsoft 365 reviewSupported tenant configuration and metadata contextDoes not read content or prove every operational practice
Pinned baseline and rescanAn observable before-and-after recordOnly covers checks that the source can read

Worked example

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.

How SCOUTz gets the MSP there

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.

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.

Is SCOUTz a blended security score?

No. Domain and cloud evidence retain separate access models and separate grades. A quiet result or unread check never becomes a clean result.

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

Your next prospect meeting is already on the calendar.

Bring dated evidence, clear limits, and useful questions.

Read site privacy