Upload or collector retrieval
Start with a manual export or a read-only collector path.
How It Works
ConfigSentry turns FortiGate configurations into structured findings that reflect operational risk, affected FortiGate areas, and report-ready evidence.
Workflow
Start with a manual export or a read-only collector path.
Policies, objects, services, interfaces, VDOMs, and relationships are mapped.
Checks run against the structured model using the selected template.
Severity-ranked results highlight risk, context, and likely remediation.
Engineer and executive reports support follow-up and history.
Context
Policy example
Finding logic
ConfigSentry evaluates the policy together with the linked address group, service scope, and logging state.
That means the finding reflects broad exposure, weak auditability, and the affected FortiGate area rather than only showing that a rule exists.
Methodology
The configuration is modelled before analysis so checks use meaningful relationships, not only raw text matches.
Checks run consistently across policy, objects, services, admin settings, and posture signals.
Mappings support control discussion and evidence gathering, but they are not a compliance guarantee by themselves.
Outputs
Detailed findings, affected sections, and remediation-oriented context.
A clearer posture and priority summary for leadership and governance review.
A consistent basis for reruns, comparison, and evidence-led follow-up.
Next step
The clearest way to judge the workflow is to review the sample outputs or run your own FortiGate audit.