VERIFY · SOLUTION

Evidence-Based Security Assessment

Use evidence states instead of a blended score to explain findings, unknowns, and the next decision an MSP and client must make.

Run a free domain scoreJoin Open Beta

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.

EVIDENCE · INSIGHT · PROOF

A real review is a starting point—not a readiness verdict.

01

Observed evidence

Retain the finding, source and date.

02

Customer-confirmed

Record purpose, owner and agreed context.

03

Gap

State what needs review or an approved change.

04

Not assessed

Show unread sources and work not tested.

Keep Microsoft Secure Score, SCOUTz findings and operational confirmation separate. Illustrative evidence states—not a live tenant result, readiness score or certification. These are evidence attributes, not mutually exclusive organizational verdicts.

EVIDENCE · INSIGHT · PROOF

What you can know before they let you in, and after.

01

Before consent

Published domain, DNS, email authentication, certificates and external evidence.

02

With read-only consent

Supported Microsoft 365 identity, app, permission, licensing and configuration evidence.

03

Never inferred

No message bodies, private files, chats or prompts. Unread is not clean.

35 public sources for a domain scan; 92 sources with read-only Microsoft 365 consent. Sources may be unavailable; reviews are coverage-dependent, not universal.

Last reviewed September 25, 2026.

An evidence-based security assessment explains what was observed, why it matters, what remains unknown, and who owns the next decision. SCOUTz uses dated sources and four check states instead of hiding unread checks inside a single score.

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.

What is different from a score gauge?

A score gauge compresses many assumptions into one number. Evidence states keep the source and limitation beside the conclusion. SCOUTz separates verified working, needs attention, worth noting, and could not be read. A reader can see the record behind each state.

Why do declared non-reads matter?

Because an unrun check is not a pass. The platform's ledger includes 22 declared non-reads so a quiet result cannot be mistaken for a clean one.

How does evidence support verification?

A pinned baseline gives the next review something specific to compare. The later result can say what changed, what did not, and what the source still could not establish.

Evidence, support, and boundary

Evidence stateWhat it supportsBoundary
Verified workingA supported positive observationNot a guarantee beyond the source
Needs attentionA prioritized next actionNot proof of exploitability
Could not be readA clear evidence requestNever a clean result

Worked example

The report says a check could not be read because the required source was not authorized. The scorecard keeps that state under NOT ASSESSED THIS SCAN, so the owner sees the gap instead of a misleading green result.

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.

How many finding types does SCOUTz support?

The current platform describes 601 distinct finding types across 91 emitting modules, including fusion and correlation logic beyond the collector output. The public domain layer reaches 123 and the cloud layer reaches 370.

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.

Your next prospect meeting is already on the calendar.

Bring dated evidence, clear limits, and useful questions.

Read site privacy