this post was submitted on 22 Nov 2023
4 points (100.0% liked)
Homelab
371 readers
9 users here now
Rules
- Be Civil.
- Post about your homelab, discussion of your homelab, questions you may have, or general discussion about transition your skill from the homelab to the workplace.
- No memes or potato images.
- We love detailed homelab builds, especially network diagrams!
- Report any posts that you feel should be brought to our attention.
- Please no shitposting or blogspam.
- No Referral Linking.
- Keep piracy discussion off of this community
founded 11 months ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Anything that has internet access like your IoT can be C&C utilizing stateful connections. An outbound socket is built, and reflected traffic can come back in. Your IoT devices especially should not be exposed to the internet. They can't even have an antivirus agent installed on them.
That's actually no longer true... kinda. You can't install AV on them, but there are security companies filling the niche of embedded IoT security. Now, you won't see this in your average consumer device, but on the commercial market there is a growing demand for some way to secure an embedded device from malicious software/firmware modifications.
You can SPAN internal traffic to an IDS device currently. Or, if internal network throughput isn't an issue, you can force east-west traffic through an IPS with DPI enabled instead.
That's historically how east-west would be mediated within an enterprise environment for devices incapable of being secured with agents.
Absolutely, and I've implemented similar east-west controls (as either prevent-first or for detection). You'll get no argument from me on that. I'm just noting an interesting trend as IoT devices become more ubiquitous in commercial and industrial environments, and some of those devices must (for whatever reason) have access to some part of the network or internet.