Article

Beyond MFA: Building a Zero Trust Security Strategy

Multi-factor authentication is a floor, not a strategy. What the rest of a coherent approach looks like, in plain language.

2 min read
Share

Multi-factor authentication is the single most effective security control most organizations can deploy, and deploying it is genuinely worth celebrating. It is also not a security strategy, any more than locking the front door is a plan for keeping a building safe.

What MFA does and does not address

MFA addresses one specific failure: an attacker with a valid password but nothing else. That is a common and important case.

It does less for several others:

  • A session token stolen after authentication has already succeeded.
  • An attacker who gets the user to approve a prompt they did not initiate.
  • An account with far more standing access than the role requires.
  • A compromised device where the legitimate user is authenticating normally.
  • An application integration holding broad permissions nobody reviews.

The ideas worth organising around

Verify explicitly

Make access decisions on current signals — identity, device state, application, sensitivity — rather than on where the connection appears to originate. Being on the office network is not evidence of anything.

Grant the least privilege that works

Most accounts accumulate access and rarely shed it. Administrative rights in particular are better granted for a defined period and purpose than held permanently.

Assume breach

Design so that one compromised account or device does not become access to everything. This is mainly about segmentation and about limiting what any single identity can reach.

A sequence that tends to work

  1. Consolidate identity so there is one authoritative place access is decided.
  2. Move to phishing-resistant authentication methods.
  3. Establish device management and define what a healthy device means.
  4. Apply conditional access, starting in report-only mode.
  5. Reduce standing administrative privilege.
  6. Review application and integration permissions, which are frequently the least examined area.
  7. Make sure you would know if something went wrong — logging and alerting that someone actually reads.

The honest framing

Zero Trust is a direction of travel, not a product and not a project with a completion date. Any vendor offering to sell you Zero Trust as a finished state is selling something else.

The useful question is not whether you have achieved Zero Trust. It is whether each access decision in your environment is made on evidence, and whether you could explain the reasoning.

Working through something like this?

If any of this is relevant to a decision you are facing, we are happy to talk it through — no obligation either way.