Daily and weekly schedules
See the exact next-run time, pause or resume schedules, and prevent duplicate materialization.
Continuous vulnerability scanning
Keep external exposure in a repeatable security workflow
Schedule authorized scans, consolidate repeated observations into durable findings, and keep remediation status visible between runs.
Three assets free for 14 days. Ownership verification and explicit authorization are required before scanning.
Scheduled, not vague
Choose daily or weekly UTC schedules for assets that have completed ownership verification and policy authorization.
One finding, useful history
Repeated observations attach to the same deduplicated finding instead of inflating the remediation queue.
Controls stay in force
Deployment, organization, and asset-level emergency stops remain authoritative over queued or scheduled work.
How it works
From owned scope to a remediation queue
Every run starts from a verified target and an explicit policy—not an open-ended scanner instruction.
- 1
Verify and authorize
Prove control of the registrable domain, review the exact target, and accept the documented Safe External policy.
- 2
Choose the cadence
Apply a daily or weekly UTC schedule without silently launching an immediate scan.
- 3
Review and retest
Move findings through acknowledgement, remediation, risk, and dispute states while preserving scan observations.
Platform workflow
Useful security context without an oversized console
Deduplicated findings
Track one retained issue across multiple scan observations with organization-scoped counts.
Lifecycle ownership
Use open, acknowledged, resolved, reopened, accepted-risk, and false-positive workflows with bounded notes.
Scan and finding history
Connect each trusted observation to its scan while keeping raw scanner output out of the product database.
Reports and notifications
Create bounded reports and receive configured scan-completion or critical-finding transactional email.
Operational controls
Cancellation, retries, leases, quotas, admission, and emergency stops are enforced by the server and worker.
What this does not replace
Clear boundaries make automated findings more useful and safer to operate.
- Continuous means recurring scheduled or explicitly queued scans—not passive real-time packet or endpoint monitoring.
- New assets still require ownership verification, exact policy authorization, entitlement, and production admission before execution.
- Maintenance windows, quotas, provider outages, and emergency stops can delay or prevent a scheduled run.
- Automated external scanning does not replace a scoped penetration test, internal assessment, code review, or compliance certification.
Your first scan is one verified domain away
Three assets free for 14 days. No card required.
Start free