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
FTC Safeguards Rule Assessment
Support an FTC Safeguards Rule conversation with dated evidence, ownership, and a clear boundary around what a review cannot establish.
Run a free domain scoreJoin Open BetaLast reviewed September 25, 2026.
An FTC Safeguards Rule assessment should connect a safeguard question to the evidence that can actually answer it. SCOUTz helps an MSP organize observable public and approved tenant evidence while leaving policy ownership, risk assessment, service-provider decisions, and operational proof with the business.
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 does the rule conversation need first?
A defined safeguard question, a responsible owner, and the source that can support the answer. This avoids treating an assessment label as a substitute for the company's information-security program.
The practical test is whether another person can understand the claim, identify its source, and decide what should happen next without treating an unknown as a pass.
Where does public evidence help?
It can support narrow questions about published mail, certificate, header, and exposure conditions. The observation is useful because it is dated and reproducible. It is not a complete rule assessment.
The practical test is whether another person can understand the claim, identify its source, and decide what should happen next without treating an unknown as a pass.
What remains outside the review?
Policies, contracts, training, incident response, risk analysis, and business decisions that the source cannot read. Those become explicit customer or MSP work items rather than silent assumptions.
The practical test is whether another person can understand the claim, identify its source, and decide what should happen next without treating an unknown as a pass.
Evidence, support, and boundary
Evidence stateWhat it supportsBoundary
Public domain evidenceA bounded technical questionNot proof of the full information-security program
Approved tenant configurationSupported identity and application contextNot proof of governance or employee practice
Policies and owner attestationsProgram and responsibility contextMust be supplied and maintained by the business
Worked example
The MSP uses one observed email-control record to open a conversation about a safeguard owner, then asks for the policy and incident process that public evidence cannot provide. The report keeps both facts and unknowns visible.
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. The public domain layer dispatches 35 collectors and can reach 123 distinct finding types. When a customer approves the next step, the read-only cloud layer is a superset with 93 collectors and 370 reachable finding types. Platform-wide, 601 finding types across 91 emitting modules include fusion and correlation logic that runs on top of collector output.
Every finding carries authored business-language explanation, consequence, recommendation, and the evidence it came from. The ledger separates 440 scored findings, 107 context observations, and 22 declared non-reads. 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.
Does this page provide legal advice?
No. It describes an evidence workflow and its boundaries. The MSP and customer should use qualified legal and compliance advice for their specific obligations.
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
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 →SCOUTz OPEN BETA
Point SCOUTz at your next prospect. Walk in with a defensible answer.
Join Open Beta with a real MSP workflow. A person reviews every application before a workspace goes live. SCOUTz runs without an agent or install and never changes a configuration on its own.
SCOUTz prepares the conversation. The relationship and the sale stay yours.