MSSPs
Scan Many Client Surfaces to One Standard.
A managed service lives on repeatability. If two clients are scanned differently, their scores can’t be compared, and neither can this month’s report and last month’s.
The Deepinfo Platform runs each client surface through the full External Attack Surface Management engine, and its API carries the rest of your delivery, from onboarding to scheduled reports.
| Client A | Client B | Client C | |
|---|---|---|---|
| WHOIS | checked | checked | checked |
| IP WHOIS | checked | checked | checked |
| DNS | checked | checked | checked |
| SSL | checked | checked | checked |
| Ports | checked | checked | checked |
| Web data | checked | checked | checked |
| HTTP | checked | checked | checked |
| Report |
One score axis
Positions on one scale; the scale has no published numbers.Client A; Client B; Client C
A scheduled PDF report per client
Collection is infrastructure. Judgment is the service.
Internet-scale collection is an engineering program of its own: registrations, DNS, certificates, port scans and web data, kept with history. Most service providers would rather spend that effort on analysts and clients.
The platform runs the collection and the scanning. Your team keeps the client relationship, the triage and the advice.
From Signed Client to Scheduled Report.
-
01
Onboard
Add the client’s domains, or a whole seed list in one API call. Turn discovery on for the seeds and the platform proposes related subdomains, IPs and domains.
-
02
Scope
Approve or ignore what discovery proposes, by filter. Tag assets by business unit and weight the ones that matter most; smart discovery rules can approve matches automatically.
-
03
Monitor
Approved assets are scanned across all data layers. Issues arrive with evidence, a severity and, for CVEs, CVSS, EPSS and CISA KEV.
-
04
Report
Schedule executive summaries and weekly progress reports as PDFs, daily, weekly or monthly. Notification rules cover the events each client cares about.
One Filter Body Drives Each Bulk Step.
Each step above is an API call, so your delivery tooling can run it. Asset Create takes a client’s seed list of domains, subdomains and IPs, and scans each one automatically.
From there, one filter syntax drives the bulk work: approve what discovery proposed, tag and weight assets, accept risk, mark issues resolved, or export every match without paging.
- Filter-driven bulk actions
- Asset search with that filter syntax
- Exports as CSV or JSON
- Rate limits per key and endpoint, set by plan
Filterfilter.jsonsent
-
must
asset_typeeq domain -
must_not
tagsin staging
-
acme.example
-
shop.acme.example (not selected)
subdomain
-
acme-staging.example (not selected)
tagged staging
-
acme-group.example
-
198.51.100.10 (not selected)
IP address
Request
POST /v1/easm/assets/search:export
{
"filters": {
"must": [
{
"name": "asset_type",
"type": "eq",
"value": "domain"
}
],
"must_not": [
{
"name": "tags",
"type": "in",
"value": ["staging"]
}
]
},
"sort": [
{
"field": "added_date",
"order": "desc"
}
]
}curl -X POST \
"https://api.deepinfo.com/v1/easm/assets/search:export" \
-H "apikey: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d @filter.json
No Client Gets a Thinned-Out Engine.
Every surface you bring gets the full engine. That is what makes one client’s score comparable with the next, and this quarter’s with the last.
| Discovery | Seed-based discovery with smart discovery, smart monitoring and custom rules. Your analysts approve or ignore candidates, or let a rule approve them. |
|---|---|
| Scanning | WHOIS, IP WHOIS, DNS, SSL, TCP and UDP ports, web data and HTTP on each asset, with history per layer |
| Prioritization | A security score per asset and per domain, and each CVE ranked by CVSS, EPSS and CISA KEV |
| Workflow | Issue states with history, and bulk decisions by filter |
| Compliance | Issues classified against OWASP Top 10 2021, PCI DSS 4.0 and 3.2, HIPAA, CWE, CAPEC and WASC |
| Lookalikes | Brand Risk Protection matches domains to client brand keywords, from exact to fuzzy and confusable matches, then monitors the ones you approve |
| Third parties | Third-Party Risk Management scans a client’s vendors as portfolios, scored like the client’s own surface |
| Reporting | PDF reports from executive summary to issue detail, on demand or scheduled, and notification rules on platform events |
Which modules run for each client depends on the scope you agree for that client.
Deliver the Platform or Build on the Data.
Partner program
Deliver the Platform
MSPs and managed-service providers are one of the partner types in the Deepinfo partner program. Commercial terms and enablement are set out in the partner agreement.
Data & API
Build Your Own Service on the Index
Some providers run their own tooling and need only the data underneath. Deepinfo Data Feeds and API Services deliver that index as files and endpoints.
Customer story
A Cybersecurity Ratings Provider
Sources internet-scale data through Deepinfo APIs and Data Feeds for the scoring product it sells, instead of running its own collection.
Questions About MSSPs
How are client environments set up for a managed service?
That is agreed with the partner team, based on how you deliver today: how client surfaces, user access and report delivery are arranged. The engine, the scoring and the API don’t change between arrangements.
Do clients need to install anything?
No. Discovery and scanning work from outside, on what each client exposes to the internet: DNS, certificates, WHOIS, open ports and web responses. Nothing is deployed in a client’s environment.
Do we need our clients’ authorization to monitor them?
Yes. Our Terms of Service allow monitoring only of infrastructure you own or are explicitly authorized to assess, so client authorization belongs in your service agreement.
Which reports does the platform produce?
The EASM Executive Summary, Weekly Progress, Asset Detail, Vulnerability Detail, Vulnerability Overview, Issue Overview and Issue Detail reports, and the CTI Email Breach Summary.
Can we use the data without the platform?
Yes. Deepinfo API Services and Data Feeds deliver the index itself, as endpoints and bulk files, for providers that run their own tooling. It is the same index the platform runs on.
How do API rate limits work?
Limits depend on your plan and apply per API key and per endpoint. Every response carries headers with the remaining allowance. See rate limits.
How does pricing work for partners?
Platform pricing depends on the scope you monitor, and partner terms are set in the partner agreement. See pricing, or start with the partner application.
Bring Your Client Roster. We’ll Scope the Fit.
Most partnerships start with a short call about your clients, your service catalog and how you deliver today.