Organization-scoped workspaces
Clerk organization context and server-side repository filters keep product records within the selected tenant.
For managed service providers
Evaluate external findings inside explicit organization boundaries
Use verified scope, organization-scoped records, and bounded reports to support a managed vulnerability workflow without mixing customer data or authority.
Three assets free for 14 days. Ownership verification and explicit authorization are required before scanning.
Tenant-scoped records
Assets, findings, scans, schedules, reports, notifications, and audits are queried within the active organization.
Per-target authorization
Every eligible asset needs current control evidence and an explicit policy record; an import alone grants no scan authority.
Auditable decisions
Lifecycle changes, authorization, deletion, and scan-control actions create bounded organization-scoped audit history.
Operating workflow
From explicit scope to a maintained finding record
The product keeps verification, authorization, execution, and remediation as separate decisions.
- 1
Establish customer authority
Keep documented authorization outside the platform and complete the in-product control proof for the exact organization and targets.
- 2
Review scope and policy
Select only verified assets, confirm the displayed checks and exclusions, and keep admission separate from authorization.
- 3
Operate and report
Schedule within quotas, triage trusted results, record decisions, and produce reports scoped to that organization.
Product fit
A focused external vulnerability workflow
Bulk activation tools
Import, filter, verify, authorize, and schedule bounded groups of eligible assets through explicit steps.
Lifecycle and bulk actions
Apply supported finding and scan actions with role checks, audit events, and bounded partial-failure results.
Customer-safe output
Reports and notifications use sanitized trusted results rather than raw scanner output, bodies, cookies, or credentials.
Know where the workflow fits
A clear boundary makes the automated results easier to use and explain.
Useful when
- Each managed organization can maintain its own verified scope and authorized operators.
- The service model includes human review of findings, remediation context, and exceptions.
- Reports need to remain bounded to one organization and the exact scans represented.
Plan separately for
- A cross-customer multi-tenant operations console, reseller billing, white labeling, or delegated customer administration unless separately confirmed in the product.
- Contractual authorization, customer consent, data-processing terms, and service-specific legal obligations.
- Penetration testing, internal network assessment, or an assurance statement beyond the selected automated scan profile.
Start with a scope your team can own
Treat every customer boundary, target authorization, and report scope as explicit. Contact the team to evaluate the current workflow against your delivery model.
Your first scan is one verified domain away
Three assets free for 14 days. No card required.
Start free