Hacker News new | ask | show | jobs
by ssss11 1135 days ago
In my experience with large corporates they architect their environment for the Microsoft ecosystem - windows, AD, M365 apps and so on.

This means they only have to worry about making stuff work and be secure for windows clients. This means they can easily save time and money by saying “only use windows clients”.

1 comments

> This means they can easily save time and money by saying “only use windows clients”.

That claim needs to be annually tested and verified by independent blue and red teams written up in an official report that measures overall org. productivity as claimed and in actual reality.

Who pays for the Red and Blue teams? Is their salary set by the amount (or lack) saved? What if the difference isn’t great? What hiring bar do you set for them (again, aligned with budget)?

What you’re saying makes 110% meritocratic sense, but there’s no way this would ever fly in a penny-pinching enterprise environment. There’s a reason that enterprise sales/support is a gigantic business constantly competing to win contracts.

It's not about "productivity" but paperwork compliance, those old school companies live and die by the certifications and Microsoft has tons of rubber stamping of anything you would want which makes them happy.

Nobody in those old style companies are ever evaluating tech on it's merits.

There's always better solutions, sometimes even much cheaper in some categories but they really want the stamps.

..or just companies that are serious about preventing data leaks and have some traceability to identify when or what happens in case of breach.
Data leaks in those companies are not about the security of the data itself but about who can cover themselves in case of a leak.

If you can demonstrate all the compliance, that's an insurance when something happens, regardless of the actual security value it provides which is rarely evaluated anyways.

Companies working this way really aren't tech companies and they don't behave as such.