| ▲ | lima 3 hours ago | |||||||||||||||||||||||||||||||||||||||||||||||||
The company also should have restricted network access to the port in the conference room so that an unknown device like a Raspberry Pi could not make an Ethernet connection from that spot Bad take - the actual problem is that there was a trusted network in the first place. This kind of network access control is trivial to bypass, and trusted devices can get compromised. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | Symbiote 2 hours ago | parent [-] | |||||||||||||||||||||||||||||||||||||||||||||||||
It's not my field, but at least at my work the network can somehow tell the difference between an authorized user and not. It is not simply using the MAC address. A guest device connected to the ethernet port in the conference room has the same access as a device connected to the guest wifi, a staff laptop has it's usual access. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||