Over the last few weeks, I’ve been working on making ConfigSentry much easier to understand before someone runs their first audit.
The product had developed quickly, but parts of the website had not kept pace. I knew what ConfigSentry did because I was building it every day, but that did not mean I was explaining it clearly enough.
What I wanted to make clearer
- What ConfigSentry actually checks in a FortiGate configuration
- Who the product is designed for
- How manual, SSH, and collector-based audits work
- What is included in the engineer and executive reports
- How uploaded configurations and audit data are handled
- How the free evaluation and paid options differ
Less marketing language, more useful detail
I’ve been replacing vague product claims with practical explanations, screenshots, sample reports, and clearer descriptions of the audit workflow.
I want engineers and security teams to be able to judge ConfigSentry from the evidence. They should be able to see what the product checks, understand the limitations, and decide whether it fits their environment without sitting through a sales process first.
A better route into the product
The public website and the ConfigSentry application now feel more connected. It is easier to move from learning about the product to reviewing sample output and then running an authorised audit.
There is still plenty more to improve, but this update gives ConfigSentry a clearer foundation and makes the product easier to evaluate honestly.
You can review the product pages, look through the sample reports, or run a free ConfigSentry audit with an authorised FortiGate configuration.