RedStrikeby Encyfr

Scanning

Running a Scan

Launch, monitor, schedule, and stop scans against your targets — from the dashboard or the API.

2 min read

A scan runs a profile's tools against one target and produces verified findings. This page covers launching, watching, scheduling, and stopping scans.

TL;DR

Open a verified target, click Run scan, pick a profile, and confirm. Watch phases stream live. Schedule recurring scans for continuous coverage, or launch them from the API for CI pipelines. Only verified targets can be scanned.

Launch a scan

From a target's page, click Run scan and choose:

  • Profile — Light, Standard, or Deep (see Scan Profiles).
  • Scope — which hosts, ports, or paths are in play.
  • Schedule — run once now, or repeat on a cron-like cadence.

A scan can only start against a target in the Verified state. If Run scan is disabled, finish ownership verification first.

Watch it live

While a scan runs, the console streams status over a live connection. You'll see the current phase, hosts discovered, tools executing, and findings as they're confirmed. You can leave the page and come back — progress is persisted server-side.

PhaseWhat's happening
QueuedWaiting for an available worker
DiscoveryEnumerating hosts, ports, and services
ScanningRunning the profile's tools
VerifyingConfirming exploitability of candidates
CompleteFindings are finalized and deduplicated

Schedule recurring scans

Continuous coverage comes from recurring scans. On the target, open Schedule and choose a cadence:

Nightly   — every day at 02:00 in your org timezone
Weekly    — every Monday at 06:00
Custom    — a cron expression, e.g. "0 3 * * 1,4"

Each run reuses the profile and scope you configured, and findings are tracked against the same target so history stays intact.

Launch from the API

Automate scans in CI or from scripts:

curl -X POST https://api.redstrike.io/v1/scans \
  -H "Authorization: Bearer $REDSTRIKE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "target_id": "tgt_123", "profile": "standard" }'

The response includes a scan_id you can poll for status. See the API Reference for the full endpoint list.

Stop or cancel

Click Stop on a running scan to cancel it gracefully; already-verified findings from that run are kept. A stopped scan is marked Cancelled and does not affect the target's scan history.

Rate limits and fairness

Scans are queued per organization and workers are shared fairly, so a large deep scan won't starve quick ones. If you hit a concurrency limit, additional scans wait in Queued until a slot frees up.

Next