> Any modern enterprise WiFi setup will support containing rogue APs. So this vector won't work if configured correctly

You misunderstood the issue. Modern enterprise wifi won’t detect a “rouge AP” that’s setup near a worker’s home (or coffee shop), only ones in radio range of the corporate APs.

Not quite on the enterprise wifi side, but I have been pleasantly surprised that iOS has alerted me when I connect to a wifi network with the same name, at a new location. So endpoints can play a part in this.

I’m not sure if there is some kind of MDM policy that would restrict locations that are valid for wifi use, but expect it is coming soon.

> Not quite on the enterprise wifi side, but I have been pleasantly surprised that iOS has alerted me when I connect to a wifi network with the same name

Actually, that’s the exact opposite of what I was quoting. That’s client side detection, not “rogue ap containment” which is an entirely different thing. Rogue AP containment is where a Wi-Fi controller detects unauthorized APs within its AP’s radio range and sends client disconnects to the devices connected to it, effectively isolating (“containing”) users from it.

Not only that, the newer WiFi standards are doing away with the dissociation attacks (which is what they are) that some vendors had been selling as "containment" because they're also quite obviously a denial of service attack vector.

You can imagine what happens when two corporations are in adjacent spaces in the same building and both have their WiFi configured to "contain" the neighboring tenant's access points.

> You can imagine what happens when two corporations

I don’t need to imagine, I’ve done it to my apartment complex before by mistake. I have an Aruba 3200XL controller and a bunch of APs (couple 335s, couple 225s, and some older 105s, with the 105s being used as Air and Spectrum monitors). Decided to see the impact and quickly learned all my neighbors lost WiFi access.