Secure Enterprise Workplace
Security in the enterprise workplace is not a checklist. It is a set of decisions about identity, administrative access, endpoint control, recovery and the exceptions people make under pressure.
Security in a workplace is rarely defeated by one missing setting. It is weakened through the ordinary decisions around who can administer what, which devices are trusted, how exceptions are granted, and whether the organisation can still operate when a control or provider fails.
This is a collection of writing about those decisions in Microsoft-based enterprise workplaces. It is not a product catalogue, and it does not promise that every risk has a technical answer.
Start here
The MSA Key Leak: Why Your “Double Key” Wasn’t a Deadbolt
Encryption controls still rely on the identity system that authorises them. The important question is not whether a control exists, but which failure it was designed to survive.
Patch Less
When vulnerability pressure rises, a better operating model can reduce exposure more effectively than trying to package and deploy everything faster.
Who Holds the Keys to Your Patching?
Patching platforms are high-trust systems. This looks at the permissions they need and the ones they should not receive.
Decide the Tier, Not the Exception
Security hardening works when decisions are made once for meaningful groups, rather than negotiated one exception at a time.
Controls need an operating model
Holistic Approach to Conditional Access Exclusions
Conditional Access exclusions need scope, approval, expiry, auditability and a named owner. The exception process is part of the control.
Day 2 without Microsoft
Business continuity starts where a normal outage plan ends: when the provider is not bringing you back and the response tools sit inside the platform you have lost.