A security product should be understandable before a visitor is asked to trust it. This update focused on making the public ConfigSentry experience clearer, more direct, and more closely connected to the product itself.
The aim was not to add more marketing words. It was to help a first-time visitor answer the practical questions that matter.
What the public site should make clear
- What ConfigSentry checks
- Who the product is for
- How a FortiGate audit is run
- What the reports contain
- How security and data handling are approached
- What the product costs and how to start
A stronger product-led path
The homepage and supporting pages are being shaped around real outcomes: finding risky configuration, understanding remediation, producing usable reports, and moving from a one-off audit to recurring review where needed.
Clearer navigation also makes it easier to move between the public information and the application instead of treating them as separate experiences.
Clarity remains the priority
Future updates will continue to favour plain explanations, visible limitations, practical examples, and easier routes to try the product. The goal is to let people judge ConfigSentry from the evidence rather than from vague claims.
Next step: Explore the product pages, review the sample output, or run a ConfigSentry audit with an authorised FortiGate configuration.