News for hackers. Stuff that matters.
Re:PoE basics and beyond: What every engineer should know by benhurmarcel on Wednesday October 22, 2025 @07:21AM (#45667449)
If one of those cameras is outside, did you consider the case of someone plugging in his laptop on that ethernet cable? He'd be on your local network.
Re:PoE basics and beyond: What every engineer should know by matt-p on Wednesday October 22, 2025 @07:36AM (#45667567)
You would normally put CCTV on its own vlan for this reason.
Re:PoE basics and beyond: What every engineer should know by EvanAnderson on Wednesday October 22, 2025 @09:34AM (#45668917)
Absolutely. Ideally one with Private VLAN[0] functionality and an upstream router configured to allow the CCTV server to pull video streams from the camera while disallowing any outbound communications from the cameras themselves.

[0] https://en.wikipedia.org/wiki/Private_VLAN

Re:PoE basics and beyond: What every engineer should know by teddyh on Wednesday October 22, 2025 @07:35AM (#45667551)
Zero-trust networking.
Re:PoE basics and beyond: What every engineer should know by transpute on Wednesday October 22, 2025 @08:25AM (#45667989)
Re:PoE basics and beyond: What every engineer should know by bc569a80a344f9c on Wednesday October 22, 2025 @09:15AM (#45668639)
MACSec is irrelevant for this purpose. MACSec encrypts points to point links, it doesn’t authenticate. That’s what 802.1x is for.
Re:PoE basics and beyond: What every engineer should know by RationPhantoms on Wednesday October 22, 2025 @11:50AM (#45670987)
No it isn't. Most MACsec-capable platforms have a "must-secure" or "should-secure" transmission mode.

If the security association isn't completed on a "must-secure" configured port then no traffic is transmitted. One would need access to the pre-shared keys to successfully use the link.

Now, could one perform a side-channel attack of the memory on the camera and get access to them? Maybe.

Re:PoE basics and beyond: What every engineer should know by mkipper on Wednesday October 22, 2025 @01:01PM (#45672024)
This is veering into pedantry, but from what I can understand of that setting (I'm not a sysadmin guy but have used MACsec on embedded stuff), that's just as much of an 802.1X feature as a MACsec feature.

Sure the switch will only accept encrypted L2 traffic...but that encrypted link is set up via MKA, which is a part of the 802.1X standard. If you don't have 802.1X authenticating the endpoint, you don't have MKA setting up the encrypted link between that endpoint and the switch and you don't have MACsec.

So if you're trying to prevent a bad guy from getting on your LAN, you need 802.1X, whereas MACsec is an optional extra (a very useful extra if you're worried about MITM attacks). But 802.1X is still doing the heavy lifting w.r.t access control.

Re:PoE basics and beyond: What every engineer should know by brohee on Wednesday October 22, 2025 @01:25PM (#45672329)
802.1x-2010 includes MACsec. 802.1x without MACsec is mostly a joke, (802.1x-2002 IIRC) you just get a legit device to open the port...
Re:PoE basics and beyond: What every engineer should know by eqvinox on Thursday October 23, 2025 @09:09AM (#45681384)
> This is veering into pedantry,

It's not veering, it's a full on car crash ;)

You run MACsec either with 802.1X, or with your switch vendor's favorite color of proprietary switch-to-switch 802.1X replacement. MACsec without 802.1X [or equivalent] is a bit like TLS without certificates. It exists in a few places because some people have really weird custom requirements (TLS with pre-shared keys… TLS with NULL encryption…) but those things shouldn't drive a discussion outside their special usage areas.

In that sense: MACsec implies and requires 802.1X. Exceptions confirm the rule.

Re:PoE basics and beyond: What every engineer should know by graealex on Thursday October 23, 2025 @10:46AM (#45682432)
What's everyone here talking about?

The absolute low-tech solution would be to dedicate a switch for it.

If you have decent infrastructure with a managed switch, you can easily create a VLAN.

Besides the fact that the female RJ45 is usually inside the dwelling. You'd have to unmount the camera, pull out the cables and connect to it, all at typical heights of 6' and above. That's maybe a concern in commercial setups, although then we're circling back to VLAN.

Re:PoE basics and beyond: What every engineer should know by tehlike on Wednesday October 22, 2025 @10:07AM (#45669412)
Vlan is the answer.
Re:PoE basics and beyond: What every engineer should know by beala on Wednesday October 22, 2025 @10:13AM (#45669481)
This is a pretty significant lift for most home networks, both in terms of cost and complexity, but I agree it’s the right way to go. If you’re upgrading to a PoE switch, you might as well go all the way and make it a managed switch.
Re:PoE basics and beyond: What every engineer should know by thmsths on Wednesday October 22, 2025 @11:50AM (#45670986)
I would assume that putting a router between the POE switch and the rest of the network would work too and basic routers are cheap.
Re:PoE basics and beyond: What every engineer should know by mmmlinux on Wednesday October 22, 2025 @12:45PM (#45671789)
When you get to the point of building out your own ip security camera system and then worrying that some hacker is going to roll up and plug in to one of your cameras. you probably already have vlans going.
Re:PoE basics and beyond: What every engineer should know by tehlike on Thursday October 23, 2025 @10:22AM (#45682143)
The more likely scenario is camera firmware being compromised and either allowing outbound or inbound connections, either of which can be prevented with a firewall+vlan
Re:PoE basics and beyond: What every engineer should know by bityard on Wednesday October 22, 2025 @12:16PM (#45671399)
If someone can roll up to your property undetected and get physical access to the network, then the security cameras aren't even doing their job.
Re:PoE basics and beyond: What every engineer should know by nucleardog on Wednesday October 22, 2025 @01:10PM (#45672136)
I did. Implemented a "simple" solution (simple for anyone who is going to be setting up their own IP camera system and NVR):

Cameras are on their own VLAN. Port isolation is enabled so they can't connect to each other. Only connectivity allowed to/from that VLAN is from the cameras to the router for NTP, and from the NVR to the cameras.

So if you plug in you can... check the current time on my router. Maybe see how many other cameras are on that segment? Likely not going to get very far given you're already caught on camera, an alert's been fired, and pretty soon I'm going to be making a call to the police.