Data flow
Where your firewall configs and logs go, and every place they do not.
Your running config, traffic logs and engagement files are read in the browser and held in memory. They are never uploaded, synced or sent anywhere.
What happens to each file
| File | Where it is read | Where it is kept | Leaves the workstation? |
|---|---|---|---|
| Configuration (PAN-OS XML, FortiOS backup, ASA running config, FMC export or Check Point export) | Browser | Browser memory until the tab closes | No |
| Traffic log (PAN-OS CSV, FortiGate or FortiAnalyzer log, ASA syslog, FTD syslog or Check Point logs) | Browser | Browser memory until the tab closes | No |
| Engagement (JSON, optionally encrypted) | Browser | A file you save to local disk | Only if you copy it |
| Firm profile (letterhead, logo, rate card) | Browser | This browser’s local storage, and a firm file if you export one | Only if you copy it |
| Reports and change package | Generated in the browser | Files you download, optionally as a password-protected zip | Only if you send them |
What never happens
- No upload to the container or any server. The container has no database and does not write evidence to disk.
- No account, sign-in or sync.
- No telemetry, analytics or update check from the app. Usage is counted locally, and the counts leave only in a usage report you save, read and upload yourself when you renew.
- No connection to Panorama, FortiAnalyzer or a firewall. The tool never holds a firewall credential.
Handle saved files like the evidence
A saved engagement contains the customer rulebase, traffic sessions, zone mapping, observations and source hashes. Store and transfer it under the same controls as the files it came from.
To lock it, add a passphrase on Evidence setup. Every save is then gzipped and sealed with AES-256-GCM under a key derived with PBKDF2-HMAC-SHA256 (600,000 iterations), with a fresh salt and IV on every save, all in the browser through Web Crypto. The engagement name, plant count and save time stay readable, and are bound to the ciphertext so they cannot be altered. The passphrase is held in the tab’s memory only and cannot be recovered.
Deliverables can be exported as a password-protected zip in the WinZip AES-256 format. File names in the zip stay readable; contents do not.
Last updated 2026-10-02.