samaritan // enterprise
Built for large environments.
Samaritan is free. This page is for organizations whose scale, compliance requirements, or infrastructure complexity means the standard setup conversation is not enough, and who want to talk to a person first.
#scale
What large-environment deployments look like
#capabilities
What's different at scale
#compliance
Audit trails and compliance reporting
Every finding Samaritan produces is retained as a structured audit record: affected asset, matched CVE ID, CVSS score, severity, timestamps, and the full evidence chain that triggered the match. These records are exportable as structured JSON (one record per ScanResult). Raw probe data is not retained beyond the scan window; only the synthesized ScanResult payloads, which simplifies what your legal team needs to review. [Roadmap: SOC 2 Type II evidence export and HIPAA-formatted audit reports are planned for a future release.]
#scale
Multi-target, high-volume deployments
Samaritan can run many concurrent scans across large target lists without per-target setup. Scan concurrency, rate limits, and target list size are configurable at the workspace level. For environments with many targets, bulk target import is available via CSV or API. Retention windows, region selection, and scan frequency are all configurable.
#detection-rules
CVE coverage for your infrastructure
The default detection set covers known CVEs for commonly-exposed services: web servers, databases, admin panels, debug endpoints, storage services, and TLS certificate issues. For infrastructure with non-standard services or specific version constraints, custom detection signatures can be added. Coverage is updated as new CVEs are disclosed for service types Samaritan encounters.
#access
Access controls and SSO
Workspace access supports SSO via SAML 2.0 (Okta, Google Workspace, Azure AD). Role-based access controls let you scope what each team member can see: security engineers get full incident context; developers can see findings affecting their services without seeing unrelated org-wide telemetry. Audit logs of access to Samaritan itself are available separately from your infrastructure audit logs.
Before the conversation
Questions that come up most often.
External surface discovery starts immediately once you register a target - no credentials needed, nothing to install. For environments with many targets, bulk target import is available via CSV or API. Most teams have their first scan results within minutes of registering their first target. Custom detection signatures typically take 1-2 additional days to configure.
#talk-to-the-team
Have a large environment?
Tell us about your infrastructure and we will set up a call with an engineer (not a sales rep) who can walk through the specific onboarding path for your environment.
Prefer email?
enterprise@samaritan.io →