Automation & Quick Scans¶
Two separate places to automate and trigger scans:
- Scan Schedules — automatic recurring scans at https://bcp.bytecode.team/monitoring/schedules/.
- Quick Scan — admin's manual scan of specific users at https://bcp.bytecode.team/settings/quick-scan/.
Scan Schedules¶
Automate scans so you don't have to press buttons manually.
Creating a schedule¶
Monitoring → Schedules → New Schedule and configure:
- Scan type — HIBP / Pastebin / Code (GitHub+GitLab) / Ransomware.
- Frequency — hourly / every 6 hours / daily / weekly / monthly.
- Start time — when to begin the first run (e.g., 02:00 UTC to avoid load during work hours).
- Linked report (optional) — attach this schedule to a specific report. Every time the scan runs, that report is refreshed with new data. Useful if you want a report to be "always fresh right before the meeting."
How linking to a report works¶
If schedule A is linked to report R:
- Schedule A fires and runs the scan.
- The scan finishes.
- Report R is regenerated with the fresh data.
- If report R has a delivery method (Slack channel) — the fresh version is sent.
This is convenient for weekly CISO reports: pin a scan schedule right before Monday 09:00, and the report always contains data current as of that morning.
Frequency picks¶
| Scan type | Recommended frequency |
|---|---|
| HIBP | daily |
| Pastebin | hourly |
| Code (GitHub/GitLab) | hourly |
| Ransomware | every 6 hours |
Quick Scan (admin)¶
An admin's tool for a manual scan of specific users — separate from schedules.
Settings → Quick Scan → https://bcp.bytecode.team/settings/quick-scan/.
Useful for:
- New employee onboarding — a fresh person joined, want to check whether their emails are in HIBP, whether their GitHub has leaked secrets.
- Ad-hoc check — someone changed roles or got access to sensitive systems, verify their security posture.
- Investigation — a specific person's account is suspicious, run a full check right now.
How it works¶
- Pick users — a checkbox list of employees.
- Pick scan types — which sources to check for these users.
- Run — the scan starts in the background.
- Results land in the same alerts dashboard, tagged as manual scans initiated by admin.
Runtime
Quick Scan of many users can take considerable time — the platform iterates over each user separately and hits external APIs. You can leave the page; the scan continues in the background, and Slack notifications about progress will appear if enabled.