Hi all,
we have enabled deep SSL-Inspection on FG100D Cluster. Everything works fine by now, except full validation of certificates presented by the remoteserver. For example, all self-signed certificates on remote-servers are accepted by Fortigate, because there ist no issuer validation (try with test on https://filippo.io/Badfish/). I found the CLI-setting "ssl-ca-list", which should solve this problem by verifying server certificates against stored CA-Cert list in Fortigate. But - how can I import ANY trusted Root-CA certs in Fortigate, like browsers have? Is it possible to import a "trusted root-CA-package" or something like that? Thank you!
Solved! Go to Solution.
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
FGT GUI can import ca certificate bundle file.
Normally "ssl-ca-list " is disable by default, no need to enable.You just make your browser trust CA certificate in deep scan "ssl-ssh-profile " of "caname". it is common use case.
If "ssl-ca-list enable", it will force FGT check full certificate chain , it will need import Root CA certificate into FGT.
Unless you want more check, disable "ssl-ca-list" will good enough.Thanks.
any update?
Yes, you can import CA from GUI:Certificates->CA Certificates, thanks.
Jeff_FTNT wrote:Yes, you can import CA from GUI:Certificates->CA Certificates, thanks.
Thank you. I know this option in the GUI, but how I can import multiple CAs in one step? For example, when I take a look in Firefox CA-Certs, I can see about 290 trusted Root-CAs!
Deep SSL inspection with Fortigate ist not usefull, unless I have a possibility to manage my root-CAs in a prudent way. And deep-inspection without validating the issuer of remoteserver certs (which is the default setting!) results in vulnerability for man-in-the-middle attacks and non-serious webservers. Please correct me if I am wrong...
FGT GUI can import ca certificate bundle file.
Normally "ssl-ca-list " is disable by default, no need to enable.You just make your browser trust CA certificate in deep scan "ssl-ssh-profile " of "caname". it is common use case.
If "ssl-ca-list enable", it will force FGT check full certificate chain , it will need import Root CA certificate into FGT.
Unless you want more check, disable "ssl-ca-list" will good enough.Thanks.
Jeff_FTNT wrote:FGT GUI can import ca certificate bundle file.
That was the decisive tipp for me! I exported a full CA-list from Firefox, merged all .crt files in one big crt and imported this crt in Fortigate - done. I know, that I have to manage the CA-certs in Fortigate by myself now, but this is much better than nothing. Thank you Jeff!
Fortiuser wrote:You'd know our local CAs, but what about Public CAs? Would you have copied Roort Certificates from Windows certmgr.msc's "Trusted Root Certificate Authorities" or Firefox's Certificate store "Authorities"?
I know, that I have to manage the CA-certs in Fortigate by myself now...
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1710 | |
1093 | |
752 | |
446 | |
231 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.