Bleeping computer was blocking my vpn but that also sounds common. Not only is there heaps of controls through conditional access policies where you can use device compliance policies and mass download defender for office 365 rules to detect these things, Microsoft also allow a bunch of ways to circumvent that through publishing enterprise apps and leave it to you not to lose your keys. I use one such app a lot called pnp powershell so my powershell can access basically everything and do anything so I can script largely migrations and audits of those migrations into sharepoint. While I do remove that app at the end of my projects, most people just move on.
Of course pure speculation. It’s just not even hard to either footgun yourself, and fortinet have been known to be shooting themselves in the foot, even assuming they tried to put controls in, in the first place.
I’ll read the actual article when I get home to see how impacted I will be though. As a customer, seller and with certifications. Not to mention, maybe there’s something for me to learn about the whole thing anyway.
A bad look indeed. But I do not think microsoft uses fortigate in front of their sharepoint service? I could be mistaken tho. Perhaps a large customer can bring-their-own-firewall in front of sharepoint?
Ouch, this can’t be a good look for a cybersecurity company.
I deploy so many of these things. I don’t even know what to say.
Fortinet as a security company is like asking a sieve to hold water.
The amount of cvss 10 scores show they’ve got the high score.
If they protect their own network with Fortigate devices no matter the utp atp whatever, they’ve probably been breached for a while.
Hard not to be cynical.
The article reads like it was sharepoint cloud service?
Bleeping computer was blocking my vpn but that also sounds common. Not only is there heaps of controls through conditional access policies where you can use device compliance policies and mass download defender for office 365 rules to detect these things, Microsoft also allow a bunch of ways to circumvent that through publishing enterprise apps and leave it to you not to lose your keys. I use one such app a lot called pnp powershell so my powershell can access basically everything and do anything so I can script largely migrations and audits of those migrations into sharepoint. While I do remove that app at the end of my projects, most people just move on.
Of course pure speculation. It’s just not even hard to either footgun yourself, and fortinet have been known to be shooting themselves in the foot, even assuming they tried to put controls in, in the first place.
I’ll read the actual article when I get home to see how impacted I will be though. As a customer, seller and with certifications. Not to mention, maybe there’s something for me to learn about the whole thing anyway.
A bad look indeed. But I do not think microsoft uses fortigate in front of their sharepoint service? I could be mistaken tho. Perhaps a large customer can bring-their-own-firewall in front of sharepoint?