I used to think - and tell our clients - that multi-factor authentication (MFA) would be all they'd need to keep threat actors out of their systems.
We implemented all of these security measures for a client:
- a very good email filter
- security awareness training
- automated phishing simulation campaigns
- app-based multi-factor authentication in Microsoft 365
So how did their account get popped? A phishing email got through the filter and the recipient opened the email, clicked a link, and provided not only her Microsoft 365 email address and password but also her MFA code - straight to the threat actor.
We were *this close* to wrapping up our SASE implementation, which would have prevented the threat actor from getting in even with the MFA code, but this isn't horseshoes, so it didn't.
Just as MFA was the thing that stopped breaches 10 years ago, today, not at least discussing SASE is nearly malpractice.
Years ago, one could pretty well assume that most of an organization's PCs lived in an office behind one public IP address, so an org's security team could rely on that IP address to distinguish your org's PCs from all of the other PCs on the internet. Security teams could deny access to cloud services like Microsoft 365 except for PCs at your office.
Today, many organizations' PCs permanently live outside their HQ, so security teams can no longer rely on their office's public IP address to distinguish their trusted PCs from any other PC on the internet.
Here's where SASE products come in. By putting SASE software on your PCs, and routing their internet traffic through your dedicated SASE public IP address, we can once again rely on your public IP address to identify your org's PCs from threat actors' PCs.
Now that we can once again identify your trusted PCs by their SASE IP address no matter where they are on the planet, we can configure Microsoft 365 to allow only your PCs to connect, denying access to threat actors' PCs because they aren't on your dedicated SASE IP address. Even if a threat actor has your Microsoft 365 password and multi-factor authentication code, they still couldn't get in.