I'm worried about this development. One the one hand, ubiquitous encryption is simply required for security on the internet. Things like lets encrypt and warning on http are great improvements. On the other hand, the owner of a network has some right to look into the packets on that network. Especially if the owner of the network also owns the end-points of that traffic. My main use-case here isn't corporate networks…
Deep packet inspection is dead, and here's why (2017)
101–110 of 126 posts
Re: Deep packet inspection is dead, and here's why (2017)
#102It's not dead. Encryption has (unjustifiably) pushed the enterprise to install fake catchall certificates on proxies so they can snoop plain-text traffic. (Why anyone would ever think this is a good idea is beyond me.)
There's also the opposite of what the initial boon of DPI gave you for egress traffic and instead doing DPI on ingress traffic in places in front of critical applications using things like SSL bump and so on. This seems worse but better in a way, where the DPI is part of the secure system instead of doing a carte blanche decrypting streams (the traffic that the internal secure system receives is in fact the traffic that it is party to instead of just wile e coyote to the universe). It's very hard to detect targeted attack to third party enterprise webapps otherwise.
Re: Deep packet inspection is dead, and here's why (2017)
#103Earlier quoted context omitted.
How else are you going to catch APT (Advanced Persistent Threat) data exfiltration/control channel traffic? Assumption 1: Machines on your network are already compromised and fully owned by a sophisticated and extremely difficult to detect rootkit. This is true of every large business. There is always that guy who will click on any link or open the document from what appears to be their co-worker. Assumption 2: APT t…
> There is always that guy who will click on any link or open the document from what appears to be their co-worker. Which is another reason why DPI is ineffective. The smart malware will identify when its connection is presenting a custom root certificate rather than the expected one and not proceed with its suspicious activities (if not deploy some kind of steganography). Then the same "that guy" will plug his perso…
And if the malware doesn't work because it has certificate pinning, well, that's a win too. Its not a 100% solution, but you can significantly raise the bar on your attackers.
Re: Deep packet inspection is dead, and here's why (2017)
#104A few years ago, one of the best managers I ever worked for left to become the CTO of a company doing pattern analysis of network traffic, rather than Deep Packet Inspection. The premise was that most of the internet traffic on your network follows the same typical patterns, but nefarious traffic doesn't. Drop their system into the network and voila, you can start to find the weird things going on that seem out of th…
Re: Deep packet inspection is dead, and here's why (2017)
#105The IP protocols have some expectation of end-to-end packet delivery. Over time we found ways in which networks could be kept "working" with this requirement relaxed. Except what could be known to "work" was just whatever was tested by the manufacturers of various middle-boxes, making change and development of new ways of solving problems harder than it should be.
The less visibility middle-boxes have into what the the traffic is, the less they are able to selectively screw things up and the internet will be more reliable for it.
Re: Deep packet inspection is dead, and here's why (2017)
#106Earlier quoted context omitted.
Techies don't "know" this, I want to be abundantly clear that having a technical background doesn't make you more savvy to security concerns -- if this were true, the prevalence of security problems throughout the industry wouldn't be nearly as pervasive. Security isn't about being perfect, so stop pushing that false narrative. It's about being good enough, and plenty of companies making smart TVs can certainly becom…
I'm not talking security. I'm talking user-hostile practices and bad engineering.
Re: Deep packet inspection is dead, and here's why (2017)
#107Earlier quoted context omitted.
Techies don't "know" this, I want to be abundantly clear that having a technical background doesn't make you more savvy to security concerns -- if this were true, the prevalence of security problems throughout the industry wouldn't be nearly as pervasive. Security isn't about being perfect, so stop pushing that false narrative. It's about being good enough, and plenty of companies making smart TVs can certainly becom…
I'm not talking security. I'm talking user-hostile practices and bad engineering.
Re: Deep packet inspection is dead, and here's why (2017)
#108Earlier quoted context omitted.
yeah, while that's true, a manufacture like amazon or apple is much more likely to update your device since they are still hoping to sell you content. You think your offbrand Smart TV is going to update past a couple bugs? They already made all the money they are going to make off that TV and they are done. Still have to trust the manufacture for that to work, but at lease you're not just left wide open there. (I mea…
That's where RokuTV has an edge. They deploy firmware updates and have a consistent track record of supporting old hardware better than any of the consumer electronic giants with proprietary systems.
I prefer to just have a screen and a box though. I cut the wifi out of my TV and only plug it in to update firmware a few times/year.
Re: Deep packet inspection is dead, and here's why (2017)
#109Earlier quoted context omitted.
Smart TVs can be left unconfigured and not plugged in via Ethernet.
I would also smash any 2.4gz antennas inside the TV for a good measure. They might not have access to your WiFi network, but the XFinitiWiFi is available to any TV maker for a modest sum of money. That, or you can buy a commercial display instead of a TV.
Might need to invest in a large Faraday cage
Re: Deep packet inspection is dead, and here's why (2017)
#110I'm worried about this development. One the one hand, ubiquitous encryption is simply required for security on the internet. Things like lets encrypt and warning on http are great improvements. On the other hand, the owner of a network has some right to look into the packets on that network. Especially if the owner of the network also owns the end-points of that traffic. My main use-case here isn't corporate networks…