Cybersecurity 203: Smart Devices & Content Delivery Networks CDNs Reverse Engineered

One of cybersecurity professionals worst nightmare is a content delivery network with smart devices.

Why are Content Delivery Networks CDNs disliked by cybersecurity experts and why are these coupled with “smart devices”?

Let’s first start with a basic smart tv, made by Samsung placed behind an Intrusion Detection and Protection System with Snort/Suricata and a firewall.

Step 1: You go purchase your awesome new “smart television” - go consumer, you have no clue what you actually purchased.

Step 2: The consumer, who is tech and cybersecurity saavy, decides to establish a dedicated LAN behind their IDS/IPS pfSense appliance and connect the television set through a monitored solution.

Step 3: The consumer, tech and cybersecurity saavy can’t get the smart tv to connect…

Why? Because Smart XYZ are “neurotechnology” enabled and linked to CDNs for the “Metaverse” which is basically a self perpetuated reality for the given person to keep them happy, consuming and not interrupting any of the big boys with big toys in the world. Predictable consumption has been the dream of the industrialists, big tech, big pharma and big media and with neurotechnology enabled “Smart Devices” in nearly every home and hand, television now runs the world (e.g. neurotechnology: optogenetics).

So, getting back to our tech saavy consumer who is not able to connect their Smart TV that requires a Content Delivery Network CDN. How to bypass the built-in settings?

Option #1: let the TV connect and get configured using a separate VLAN that is wide open and isolated named the same as the other VLAN not active with different settings that blocks the CDN. Then after the TV is initially configured, hot-swap the VLANs and wa-la, you tricked the “Smart TV and CDN” :)

Reverse engineered, the init config per say was based upon a given bioinformatic dataset that was then hijacked into a non-CDN, but utilized to gain entry. This is one of the tactics of neurohacking as well, capture the initial bioinformatic and bioenergetic signals and then utilize to neurohack (side-note).

Option #2: based upon the above working, the trick is to trick the “smart device” into thinking it’s connected to its’ content delivery network and then go from there. Why does a CDN even matter? Cause it is a precision tailor ad delivery neurotechnology platform based upon the thoughts of the person. Nielsen Company was the largest investor in neurotechnology pre 2010 as well as Microsoft and Stanford w/r/t research, MIT is also in the neurotechnology R&D wheelhouse. This is why not everyone’s commercials and ads are exactly the same when they’re utilizing “Smart Devices”, “Content Delivery Networks” when coupled with non-invasively dosed Brain Machine Interface niBMIs immersed a given person in a neurotechnology bubble, dubbed “metaverse”… ever wandered what the “metaverse” really is? It’s a reality for those that can’t cut it in the real world or choose to check out into some digital reality for whatever reason (military take-over of a country without the population knowing, big tech take-over of a nation without the nation knowing, the sky is the limit with this technology).

So, there you have it, how to setup a “Smart TV” with Content Delivery Network CDN and why it just doesn’t simply work behind a secure IDS/IPS/Firewall such as pfSense.