Guide
Getting started
Follow these steps to deploy a scanner, define scope, and run your first scan.
Prerequisites
- mipo is deployed and reachable over HTTPS.
- You have owner or admin access.
- At least one Linux host can run the scanner (a static Go binary, no runtime deps) and reach mipo on 443.
01
Register a scanner
- In Config > Scanners, add a scanner and give it a descriptive name.
- mipo generates a one-time provisioning command (short TTL).
- Run it on the target Linux host; the scanner registers and receives a permanent API key (shown once).
- The scanner begins heartbeating every 60 seconds.
02
Define target subnets
- Create subnets in CIDR notation (e.g. 192.168.1.0/24). IPv4 and IPv6 are both supported.
- Assign at least one provisioned scanner to each subnet.
- Group related subnets for easier reuse across templates.
03
Add port lists
- Built-in lists cover common services (web, database, mail).
- Create custom lists for your services; ports default to TCP.
- Port lists are reusable across multiple scan templates.
04
Build a scan template
- Combine subnets (the "where") with port lists (the "what").
- Templates are only eligible to run when their subnets have scanners assigned.
05
Run your first scan
- Select an eligible template and launch it.
- Watch real-time progress as scanners report back through ingest.
- Open the completed scan to read per-host port state.
06
Set up schedules
- Attach a cron schedule or preset cadence to a template.
- Jitter randomizes start times to avoid predictable scan patterns.
- Schedules can be disabled/enabled without deletion.