Skip to content
ConfigProof
THE CONFIGPROOF WAY

Analyze, Validate, Prove

Complexity in
Clarity out

Bring configuration data into one clear picture of your security posture

Explore the workflow
A configuration file, or the collector on your own network
Scroll to reveal
01/03
Evidence, not guesswork

A configuration tells a story
Make every detail count

Every result carries its source
Every conclusion shows its limits

Built for the engineer
Ready for the client

How it works

Four steps between a configuration export and something you can hand over

  1. 01

    Upload XML

    Upload a supported firewall configuration export. The file is parsed with external entities and network access disabled.

  2. 02

    Select scope

    ConfigProof shows which modules it detected. You choose which ones receive full control analysis, and acknowledge the scope.

  3. 03

    Review findings

    Each finding shows its evidence, its affected entities and its limits. You confirm, override or exclude before anything is published.

  4. 04

    Export report

    Generate a client-ready PDF revision, a WBS handoff and a configured-topology diagram from the findings you kept.

Four modules, one workflow

Each one takes the output of the last, so nothing is retyped between analysis and delivery

XML Analysis

Parsing, normalization and a reference graph over the supported configuration, with vendor and version detected from content.

Findings and Evidence

Deterministic controls produce findings with a stable control ID, an evidence level, affected entities and an exact configuration path.

WBS Planner

A focused handoff: phases, tasks, low and high effort ranges, dependencies and acceptance criteria, exportable as PDF or CSV.

Diagram Canvas

A configured-topology starting point, editable on a canvas, with provenance on every node and edge.

Proof of output

One finding, one report spread and one diagram excerpt, so you can judge the deliverable before you sign up

Two report templates

Professional Assessment for a balanced executive and technical read, Technical Detailed for a denser engineering record. Automatic table of contents, configurable cover, immutable revisions.

Open the sample report

Anatomy of one finding

Not a paragraph of advice. A control ID, an exact configuration path, the entities it affects, the evidence level behind it and what it does not prove.

PAN-SEC-001CriticalDerived

Allow rule matches any source and any destination

Configuration path
/config/devices/entry/vsys/entry/rulebase/security/rules/entry[@name='temp-allow-all']
Affected entities
1 security rule, 2 zones
Not proven from this export
Whether the rule carries live traffic. Hit counts and session state are not present in a configuration export.
See the control library

Who this is for

Three ways the same workflow gets used

Security engineers

Review your own estate, defend a change inside a maintenance window and keep a record of what was checked.

See the scenario

Independent consultants

Turn one configuration export into a branded assessment, a remediation plan and a diagram your client can act on.

See the scenario

Managed service providers

Shared client workspaces, roles, organization branding and an audit history across the team.

See the scenario

Start with one assessment

A single device analysis from $79, or a monthly plan from $49. The free analysis costs nothing, takes a card that is never charged, and its exports need a plan

See all six plans