![]() While DNSFilter does not play a role in mitigation or prevention of the Log4j threat, we do protect our users from malicious domains queried from your infrastructure. Of course, we recommend doing a complete review of all of your software, as due to the nature of the exploit, it is not something DNSFilter can intercept and protect you from-but you don't have to worry about DNSFilter itself. We've done a full internal audit of all aspects of the DNSFilter software stack, including our dashboard, backend software, databases, and our roaming clients, and can confidently say that we have no exposure to the log4j vulnerability from any angle. On the off-chance you missed it, the nitty gritty details are here. If you've been on the internet at all in the last 72 hours, you've undoubtedly heard that you should be concerned about the Log4j exploit and that lots of your software is currently vulnerable to it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |