Deep packet inspection is dead, and here's why (2017)
security.ias.edu
Deep packet inspection is dead, and here's why (2017)
1–10 of 126 posts
Re: Deep packet inspection is dead, and here's why (2017)
#2https://www.sonicwall.com/en-us/products/firewalls/security-...
Re: Deep packet inspection is dead, and here's why (2017)
#3Re: Deep packet inspection is dead, and here's why (2017)
#4Not a very informative article. All it manages to say is that deep packet inspection does not work with encrypted traffic. I think author is not aware of transparent deep packet inspection of SSL traffic. Here is one such product doing it. https://www.sonicwall.com/en-us/products/firewalls/security-...
Re: Deep packet inspection is dead, and here's why (2017)
#5Re: Deep packet inspection is dead, and here's why (2017)
#6Not a very informative article. All it manages to say is that deep packet inspection does not work with encrypted traffic. I think author is not aware of transparent deep packet inspection of SSL traffic. Here is one such product doing it. https://www.sonicwall.com/en-us/products/firewalls/security-...
Re: Deep packet inspection is dead, and here's why (2017)
#7Not a very informative article. All it manages to say is that deep packet inspection does not work with encrypted traffic. I think author is not aware of transparent deep packet inspection of SSL traffic. Here is one such product doing it. https://www.sonicwall.com/en-us/products/firewalls/security-...
Re: Deep packet inspection is dead, and here's why (2017)
#8Re: Deep packet inspection is dead, and here's why (2017)
#9The author suggests towards the end to analyze DNS queries, but that's on the best way [1] to be encrypted as well (finally). [1] https://wiki.mozilla.org/Trusted_Recursive_Resolver
That being said, this is at the OS level. An app such as Firefox could still override those settings or provide their own implementation.
Re: Deep packet inspection is dead, and here's why (2017)
#10The author suggests towards the end to analyze DNS queries, but that's on the best way [1] to be encrypted as well (finally). [1] https://wiki.mozilla.org/Trusted_Recursive_Resolver
In a corporate environment, managed devices can be configured to force the use of specific DNS settings. The same type of implementation (MITM) could be used to analyse the requests. That being said, this is at the OS level. An app such as Firefox could still override those settings or provide their own implementation.