How the web app is organized¶
The web app at breachspider.com/app is organized around decisions, not lists. Every number opens the devices behind it, and every finding links to its source.
The menu¶
| Group | Screens | Use it to |
|---|---|---|
| (top) | Overview, Progress, Fix first | See exposure, how it moves, and what to do first |
| Inventory | Assets, Sites, Changes | Keep your devices, compare places, see what changed |
| Intelligence | Lifecycle, Firmware, Windows, Research | Support status, firmware currency, Windows patch level, CVE search and watchlist |
| Operations | QR and identifiers, Maintenance, Backups & integrity, Reports | Run the plant's records and produce evidence |
| Administration | Integrations, Clients (MSSP only), Settings | Keys, connected apps, webhooks, team, audit log |
| Help | Training, Documentation | Courses, and these pages |
Pages reached from other screens: Import (from Assets), Data quality (from Assets when devices need attention), the device panel and the CVE record (from any device or CVE, see Assets).
Operations screens are turned on per organization
QR and identifiers, Maintenance and Backups & integrity appear only when asset operations are turned on for your organization. The documents vault inside Backups & integrity is turned on separately.
On every screen¶
- Data as of: at the foot of the menu, when the results you are looking at were computed.
- Search in the top bar finds assets and CVEs.
- Theme: light or dark, remembered for you.
- Organization switcher (MSSP accounts): choose your own devices or one client. The client stays named at the top of every screen, and nothing from the previous client stays on screen.
- Undo: device edits and removals, site changes, deleted reports, bulk edits, recorded actions, imports and acknowledgements can each be undone. An undo is refused if the item changed again since, so a later change is never lost.
Roles¶
| Role | Can |
|---|---|
| Owner | Everything, including deleting the organization |
| Admin | Change settings, keys, connected apps and the team; manage the vault |
| Viewer | See everything and change nothing |
Owners and admins invite members as admins or viewers in Settings.
How results are kept¶
Each device's last check is stored with its result hash and status hash. Every device is checked again every night (and when you run a check), and the differences between checks become Changes. Screens read the stored result, so they open quickly; the device panel shows when each device was last checked.
Wording you will see¶
| Word | Meaning |
|---|---|
| Confirmed | The CVE is confirmed for the version the device runs |
| Known-exploited | The CVE is in the known-exploited vulnerabilities catalog |
| Needs review | The engine is not sure of the product or version: a person should confirm |
| Fix available | A fix is named for at least one finding |
| Derived | A target version computed from the end of an affected range, not stated by the vendor |
| Not published or not held | No lifecycle source for the vendor, or the vendor states no date. Never means supported |
| Simulated for the demo | History generated for demo workspaces only; never in your organization |