Direct answer
Can MSSPs use PhishNet for multiple clients? Yes, the product model supports scoped dashboards and export profiles by country, sector, brand and confidence state.
Problem
Service providers cannot sell a slow dashboard or noisy flat feed. They need fast snapshots, client-specific filters, explainable source quality and exportable data.
PhishNet unique data
PhishNet exposes fresh feeds, brand pressure, source factory status, evidence workbench links, campaign/kit clusters, active OSINT categories and graph relationships.
Public-safe proof module
Public proof can show source families, confirmation split, country comparison and sanitized examples while client data remains authenticated.
Integration path
API/export paths include JSONL, CSV, STIX, MISP, PDF summaries and graph/campaign outputs with provenance and confidence.
Conversion path
CTA: request API schema, sample dataset or MSSP packaging call.
How PhishNet uses this
Inside PhishNet this topic is treated as operational graph context: observations are linked to sources, evidence, Belgian relevance, confirmation state, liveness, campaigns and exports. Public pages explain the method; authenticated users can pivot into the full platform workflow when a signal needs investigation or handoff.
Selected sources and research
These pages combine PhishNet platform knowledge with public research, official Belgian sources and open OSINT documentation.
Common questions
Can MSSPs use PhishNet for multiple clients?
Yes, the product model supports scoped dashboards and export profiles by country, sector, brand and confidence state.
Does the API trigger heavy collection?
No. User-facing APIs should read cached snapshots and graph projections.