FortiGate configurations can contain sensitive information. This page explains, in plain English first, how ConfigSentry handles configuration reviews, what may be retained, and what to check before uploading production configs.
The short version
At a glance
ConfigSentry performs a read-only review of FortiGate configuration data and produces reports and findings from that review. Configuration files can contain sensitive operational information and may contain personal data depending on how an environment is configured.
For the normal hosted path, secret material such as passwords, private certificates, and keys is stripped before the configuration is added to the queue database. It is then processed and generally removed from the queue database within a few minutes.
You can start with manual upload before using a collector. If a manual audit is run with "Do not save results on website" selected, the configuration is processed directly in memory only and is not saved in the queue database or another database table.
Reports, findings, audit history, and related account metadata may remain until deleted. Deleted live records are removed immediately, while periodic database backups may retain deleted data for up to 30 days.
Collector-based collections can be configured so appliance credentials remain on the customer collector host rather than being stored in the website.
ConfigSentry is for audit, reporting, and review. It does not push changes to firewalls, does not perform automatic remediation, and leaves remediation under the customer’s own change control.
Handling flow
A FortiGate configuration is provided either by upload or by an approved collection workflow.
For the normal hosted audit path, passwords, private certificates, keys, and similar secret material are stripped before the configuration is added to the audit queue table.
Hosted queued configurations are generally processed within a few minutes and then removed from the queue database. Manual audits using "Do not save results on website" are processed directly in memory only.
Reports, findings, and history may remain until deleted through normal account workflows. Live records are then removed immediately, while backups may persist for up to 30 days.
Direct answers
What should evaluators know before uploading?
ConfigSentry is currently being offered as an early free trial. A self-service Data Processing Agreement is not currently available. Firewall configuration files can contain sensitive operational information and may contain personal data depending on how an environment is configured. Please only upload configuration files that you are authorised to submit. If your organisation requires a Data Processing Agreement, supplier security review, subprocessor details, or specific data-handling terms before uploading production firewall configurations, contact Secdit before using the service.
Is ConfigSentry read-only?
Yes. It is designed for review, not change deployment.
Does it push changes to FortiGate?
No. Remediation remains under customer change control.
What data does it process?
Raw FortiGate configuration data for audit, plus the resulting findings, scores, reports, and related service metadata.
How are hosted audits handled?
For the normal hosted path, secret material is stripped before the configuration is added to the audit queue table, processed, and generally removed from the queue database within a few minutes.
What happens with the no-save manual option?
If a manual audit is run with "Do not save results on website" selected, the configuration is processed directly in memory only and is not saved in an audit queue or other database table.
What may be retained?
Audit results, findings, reports, history, and related account metadata may remain until deleted. Deleted live records are removed immediately, while periodic database backups may retain deleted data for up to 30 days.
Where is the service hosted?
Hosted with Hetzner in Nuremberg, Germany.
How are collector credentials handled?
Collector-based collections can be configured so appliance credentials remain local to the customer collector host.
How is access to the service protected?
Authenticated account access is required, MFA-supported access helps protect sensitive audit output, public web traffic uses HTTPS with TLS 1.2, internal database connections use TLS with certificate authentication, and passwords are stored in encrypted and/or hashed form.
What staff access is stated publicly?
Support staff have minimal account access. They can see general account information, user email, account members and roles, submitted support messages, and account-related error logs. They cannot see audit report contents.
How can deeper review be discussed?
Use the normal account workflow for audit cleanup and contact Secdit at support@secdit.com or via the contact page if your review needs more detail on backup handling, supplier review, or handling specifics not stated on this page.
Hosting and access context
ConfigSentry data is hosted with Hetzner in Nuremberg, Germany. Hetzner publishes information about its ISO 27001:2022 certified ISMS and the data-centre scope it says is covered. That is hosting-provider information, not a claim that Secdit or ConfigSentry is ISO 27001 certified.
Sensitive audit output should be treated as security-relevant data. ConfigSentry requires authenticated access to the service, MFA-supported access helps protect audit history, findings, and reports, public web traffic uses HTTPS with TLS 1.2, internal database connections use TLS with certificate authentication, and passwords are stored in encrypted and/or hashed form.
Support staff can see general account information such as account name, ID, user email, account members and roles, submitted support messages, and account-related error logs. They cannot see audit report contents.
ConfigSentry can surface findings and support remediation planning, but customer teams still decide what to change, when to change it, and how those changes are approved and implemented.
Important limits
ConfigSentry does not certify compliance, and this page should not be read as a statement that a reviewed firewall is compliant with any standard.
ConfigSentry helps structure technical review, but it does not replace engineer judgement, internal review procedures, or environment-specific validation.
ConfigSentry does not push configuration changes to firewalls and should not be treated as an automatic remediation system.
Information published by Hetzner about its own ISMS or data-centre certification scope should not be treated as product certification for Secdit or ConfigSentry.
Security review questions
This page states that live audit, report, and related account records are removed immediately when deleted, while periodic database backups may retain deleted data for up to 30 days. Ask Secdit directly if your review needs more backup-handling detail.
This page states that public web traffic uses HTTPS with TLS 1.2, internal database connections use TLS with certificate authentication, passwords are stored in encrypted and/or hashed form, and hosted queued audit data is short-lived. Ask separately if your review needs deeper implementation detail.
Publicly stated support access is limited to general account information, account members and roles, support messages, and account-related error logs. Audit report contents are not visible to support staff.
ConfigSentry is currently being offered as an early free trial. A self-service Data Processing Agreement is not currently available. Organisations that need a DPA, supplier security review, subprocessor detail, or specific data-handling terms before uploading production firewall configurations should contact Secdit before using the service.
Downloaded reports, exported files, collector hosts, and any local copies of configurations remain part of the customer’s own security scope and should be handled under the customer’s normal controls.
Next step
Run an audit when your review is comfortable with the handling approach, or check pricing if you still need commercial detail.