- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
08-24-2022 05:40 PM
Hi all, Zach here again from the VaaS team. I wanted to discuss a recent issue that we had that could be effecting your environment if External Discovery is not configured properly and if you have certificates being virtually hosted via SNI.
SNI virtual hosting allows multiple sites and certificates to be hosted on the same IP address. When an External Discovery is performed, the scanner is scanning the public IP address for TLS certificates and will match the results against the registered domains. However, this discovery is only able to discover the default certificates installed at a given IP address. If a certificate is installed using SNI and it is not the default certificate, it might not be found during this discovery.
To address this, you can add the FQDN explicitly as a target for External Discovery and VaaS should pick up the correct certificate then.
As always you can post below if you have any additional questions or open a ticket with support if needed. Thanks!
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

