Solutions
Is this designed for my work?
The same workflow, three different jobs. Each one maps to a plan, and each plan is enforced on the server rather than in the interface.
Security engineer
Defend a change inside the maintenance window
You own an estate and you need to know what the configuration actually permits before you touch it, and to be able to show your work afterwards.
A typical week
Export the running configuration, analyze the policy, object and logging modules, review the high severity findings against what you know about the environment, and keep the report as the record of what was checked before the change.
- Findings that point at the exact rule or object rather than a category.
- A severity you can override, with the reason stored beside the original machine result.
- A history of every snapshot, so the next review starts from the last one.
Independent consultant
One export becomes a deliverable a client will pay for
You are engaged to assess someone else's firewall and the value you sell is the write-up, not the scan.
A typical week
Analyze the client snapshot, review and edit the client-facing wording, build the remediation plan from the findings you kept, insert the diagram, and publish a white-label revision under your own brand profile.
- White-label reports with a saved brand profile and per-client projects.
- A WBS handoff with effort ranges you can price against.
- Report revisions and a client-facing change log, so a second version does not overwrite the first.
Managed service provider
A team working across many client estates
Several engineers, many clients, and a need to know who changed what.
A typical week
Shared client workspaces, roles for owner, engineer and viewer, organization-level branding on every deliverable, and an audit history covering scope changes, overrides and published reports.
- Multiple users with roles, which lower plans deliberately do not have.
- Organization branding and shared report settings.
- An audit trail over every action that affects evidence, scope or a published report.
Plan mapping
Only MSP and Enterprise have more than one user. That is a data-model rule, not an interface one.
| Role | Plan | Users | Assessment Cycles |
|---|---|---|---|
| Security engineer | Engineer | 1 | 5 |
| Independent consultant | Consultant | 1 | 25 |
| Managed service provider | MSP | 5 | 100 |
Free Preview, Single Assessment, Engineer and Consultant are single-user accounts. The service refuses to add a second member on those plans.
One Assessment Cycle
One logical firewall environment, one primary configuration snapshot and the complete workflow around it.
Learn moreAnalyze a configuration and see the evidence.
Create an account, upload a supported export and choose your scope. The raw file is deleted as soon as it is normalized.