News for hackers. Stuff that matters.
Re:The Nearest Neighbor Attack by cortesoft on Monday November 25, 2024 @01:29PM (#42238707)
My conclusion is that being on the corporate Wi-Fi should not give you access to anything. There should not have been any advantage to getting on the Wi-Fi, it should be treated like the public internet.

A separate VPN, with MFA, should be required to access anything.

Re:The Nearest Neighbor Attack by sleepybrett on Monday November 25, 2024 @01:49PM (#42238961)
it should be a factor (defense in depth) but not the ONLY factor.
Re:The Nearest Neighbor Attack by alsetmusic on Monday November 25, 2024 @05:25PM (#42240780)
My current org restricts wifi by user and by device in Active Directory. Thus you need to be whitelisted twice to get access.

We use 2fa pretty much everywhere, but I don't think we use it there. But it certainly wouldn't hurt as yet another layer.

Wifi adapters should be disabled via Group Policy for wired devices anyway.

Re:The Nearest Neighbor Attack by sam_lowry_ on Tuesday November 26, 2024 @10:19AM (#42246500)
Active Directory?

You are already powned.

Re:The Nearest Neighbor Attack by UltraSane on Tuesday November 26, 2024 @12:01AM (#42242742)
When WiFi security was really bad I worked at a company that didn't use it at all. You connected to the WiFi without any authentication and then had to connect to a VPN server that used 2FA auth.
Re:The Nearest Neighbor Attack by rocqua on Tuesday November 26, 2024 @02:29AM (#42243334)
Corporate WiFi based on a password and a device certificate is fine. For BYO devices, you have a separate WiFi network that does require a VPN to reach the corporate network.
Re:The Nearest Neighbor Attack by legulere on Tuesday November 26, 2024 @03:11AM (#42243544)
Also a VPN is just another perimeter. You wouldn't want a single device like a printer getting successfully attacked leading to everything in your network getting compromised. The real solution is to use a zero trust architecture