For MSPs, MSSPs and security consultancies
Run client assessments with clear boundaries.
Run web, API, network and server pentests for every client from one workspace with ShieldProbe Assess, our pentest module. The AI drafts each finding. Your team approves it before the client sees it.
Example client book
Fictional clientsSelect a client to see where its pentest stands:
Findings released
The engagement lead approved drafts; the client requested a retest.
- Boundary
- Example web application / agreed roles
- Next owner
- Your assigned pentester
- Authorization
- The client's written authorization is recorded before testing, along with who can view and deliver the evidence.
Penetration testing for MSPs, without hiring a bigger test team.
Our AI runs each client pentest. Your engagement leads and pentesters review the draft findings and release the report, so you add assessment capacity without adding headcount.
- A separate space for each client, with its own pentests, findings and reports.
- Client logins that see only their own pentests.
- Your engagement leads and pentesters review the AI's draft findings and release reports.
- Clients never see your other clients, unapproved findings, or your prices, credits and billing.
- A client admin can build a pentest and run discovery; you approve the scope, pay with your credits and launch it.
- Clients request retests and dispute findings in the app.
- A Client Health view across your client book.
How the commercial model works.
For occasional client engagements, see consultants. To refer or resell instead, see resellers.
- Credits
- Your MSP workspace pays with credits.
- Pricing
- Pentests are priced per service or hourly, set once for your workspace.
- Your clients
- Your clients never pay ShieldProbe and never see your prices, credits or billing.
- Modules
- Assess only: Defend, Fix and Continuous are not part of an MSP workspace.
Every client in its own space.
Each client’s authorization, targets, access and reports stay with that client.
Assess supports web applications, APIs, networks and servers. Internal access and test accounts are set up per client.
Review supported assessment scopePer-client onboarding
- Record the asset owner and written testing permission.
- Agree user roles, access path, windows and stop conditions.
- Identify who can view findings and deliver the report.
- Set remediation ownership, retest boundaries and support contacts.
Deliver pentest evidence your client can act on.
The AI runs the test and drafts the findings. Your engagement leads and pentesters review each draft and release the report. Clients see a finding only after your team approves it.
The report tells your client's security and engineering owners what was tested, what remains uncertain and what should happen next.
Read the illustrative sample reportPlan recurring work
Set each client’s testing cadence around their releases and risk. A retest checks a known finding; new applications or wider scope are a new engagement.
The 48-hour delivery and 12-month retest offers depend on scope, access readiness and engagement terms.
How often to test a client, and what makes a pentest audit-grade.
How to start
From your application to your first client.
- YouApply
We review fit and agree terms.
- ManticoreAISwitch on MSP mode
Your subscription and active assessments carry over.
- YouAdd your clients
Invite each client's people.
We switch on MSP mode once terms are agreed.