How-to guides¶
Step-by-step instructions for the day-to-day work in BreachSpider's Operations menu, from labelling a site to handing a verified backup to an auditor. Each guide follows one job from start to finish, with the exact buttons to press.
| Guide | You will |
|---|---|
| Label a site with QR codes | Give every device an asset tag and a QR label, print them and put them on the equipment |
| Find a device on the plant floor | Scan a label or type a code to open a device, and link labels you already have |
| Plan and record maintenance | Plan work, carry it out, close it with the outcome and keep a history per device |
| Back up and verify a configuration | Set up the vault, store a PLC, HMI or device configuration, verify it and share the receipt |
| Turn a finding into a change ticket | Draft a change ticket from the vendor's statements, then copy, email or export it |
| Run operations for MSSP clients | See every client at once, add and onboard clients, assign analysts and do this work inside each client |
Before you start¶
- Operations must be on for the organization. The Operations group in the left menu (QR & Identifiers, Maintenance, Backups & integrity) appears only when it is. Backups & integrity also needs the vault. If you don't see them, ask BreachSpider to turn them on.
- Roles. The roles are owner, admin, editor and viewer. Viewers can open and read everything but cannot change anything. Editors do the day-to-day work: labels, identifiers, maintenance, backups and change tickets. Setting up the vault and a few backup settings are for owners and admins, listed in Back up and verify a configuration.
- Keep these out: BreachSpider does not store serial numbers or network addresses as identifiers. Maintenance notes say "no passwords or configuration content": keep secrets out of every free-text field.