Techbanq

Cybersecurity · Entra ID

Every door in a Microsoft estate opens with an Entra ID token

Mail, files, the ERP, the VPN and the admin portals all defer to the same tenant, and most tenants still carry the defaults and emergency grants of their first migration. We harden Entra ID in an order that works: privileged roles first, then conditional access people can live with, then the legacy paths that bypass both.

Server racks in a controlled-access facility

Serving Saudi Arabia from our Riyadh office and our engineering hubs in Lahore and Karachi

Cybersecurity credentials

  • National Cybersecurity Authority, Saudi Arabia

    NCA registration

    Registered cybersecurity service provider

  • ISO

    ISO/IEC 27001

    ISO/IEC 27001 certified

Certifications & registrations

The programme

The order an Entra ID tenant is walked back to least privilege

The sequence is deliberate: the people who will write and approve every later policy have their own privilege accounted for first, and nothing is enforced before the sign-in logs prove what it would break.

  1. 01

    Privileged roles resolved

    Every path to admin is traced — direct assignments, group memberships, eligible activations, application permissions — then standing grants are replaced with time-boxed, approved activations and a break-glass account that is watched.

    • Role assignments
    • PIM
  2. 02

    Conditional access designed

    Policies are written around the estate's real shape — who signs in from where, on what devices — and run in report-only mode against live traffic until the exceptions are known and owned.

    • Conditional access
    • Sign-in logs
  3. 03

    Legacy authentication retired

    The protocols that ignore every modern control — basic auth, old mail clients, scripted logins — are found in the logs, their dependents fixed or fenced, and then the door is closed for good.

    • Auth policies
  4. 04

    App consent governed

    The registrations and consents that accumulated over years are inventoried, the over-permissioned and abandoned ones revoked, and user consent routed through an admin workflow so the sprawl cannot rebuild itself.

    • App registrations
    • Consent policy

The report-only rehearsal

Every policy runs first in report-only mode against weeks of real sign-ins. The rollout that skips this step discovers its mistakes as a helpdesk queue on a Monday morning.

A tenant hardened in this order never has to choose between security and a working Monday.

The design test

Conditional access people can live with is the only kind that survives

A conditional access policy is a rule about people's working day, and rules about working days get repealed when they are wrong. The policy that challenges a salesperson for a second factor forty times before lunch, or locks a board member out of mail in an airport, does not make the estate safer — it generates the executive exception, and the exception becomes the hole. So we design from the sign-in logs rather than from a template: where your people actually work, which devices they genuinely use, which applications carry the data worth protecting hardest. The controls land where the risk is, and daily work on a compliant device from a usual place stays quiet.

The other half of a liveable design is honesty about the break-glass path. Some day a policy will misfire, a token service will stumble, or the person with the phone will be unreachable — and the organisation that has no rehearsed emergency access invents one under pressure, usually by weakening something permanently. A monitored break-glass account, excluded from the policies it exists to survive and alarmed the moment it is used, is not a weakness in the design. It is the reason the rest of the design can afford to be strict.

The accumulation

The quiet weaknesses a busy tenant collects over the years

None of these was a decision. Each is the residue of a migration, an emergency or a convenience, and each is the kind of finding a tenant review exists to surface.

  1. 01

    The Global Administrators nobody counted

    Admin was granted to unblock a migration, to a consultant who has left, to a service account a vendor asked for. Years later a dozen identities can do anything to everything, and compromising any one of them is compromising the tenant. Most of them need a narrow role or none at all.

  2. 02

    The protocol that ignores every policy

    Legacy authentication predates conditional access and multi-factor prompts, so a password sprayed against an old protocol endpoint is tested against nothing but the password itself. As long as one legacy path stays open, the modern controls guard the front door of a house with an open window.

  3. 03

    The consented app nobody remembers

    A user clicked accept on a productivity tool in 2021 and granted it standing rights to read mail. The trial ended; the consent did not. An attacker who compromises that vendor — or registers a lookalike app of their own — inherits access no password reset revokes.

  4. 04

    The hybrid link that carries weakness upward

    Most tenants still synchronise from an on-premises Active Directory, and the sync means the weaker estate sets the bar: a compromised domain controller or an over-trusted sync server can mint its way into the cloud. The boundary between the two directories deserves the same scrutiny as either one.

Our role

What we harden in Entra ID and what your admins keep in hand

  1. 01

    The map before the change

    We resolve effective privilege through every path and read months of sign-in logs before proposing a single policy, because a hardening plan built on how the tenant is assumed to work becomes a lockout plan.

  2. 02

    Policies negotiated, then enforced

    Conditional access and the legacy shutdown are agreed with the teams they govern, rehearsed in report-only mode, and enforced with a rollback — so each step lands without becoming the incident.

  3. 03

    A tenant your team can keep strict

    The role model, the policy set and the reasoning behind each are documented and handed over, with your administrators making the final changes themselves — because a tenant only outsiders understand drifts back to its defaults.

How much sign-in friction each population carries, and which legacy dependencies are worth fixing versus fencing, are your calls; we bring the evidence, the order and the rehearsal that make those calls safe to enforce.

Common questions

What buyers ask

Will conditional access lock our executives out when they travel?+

Not if it is designed from your sign-in data rather than from a template. Travel is a known pattern, and the design accounts for it: a compliant, registered device satisfies the device signal wherever it connects, step-up challenges replace hard blocks for unusual locations, and the policies are rehearsed in report-only mode against months of real sign-ins — including your travellers' — before anything is enforced. The lockout stories almost always come from policies written in an afternoon and switched straight to enforce. The residual case, a lost device in another country, is handled by the monitored break-glass path, which is rehearsed rather than improvised.

Can we switch off legacy authentication without breaking older applications?+

Yes, if the shutdown is driven by evidence instead of a date. The sign-in logs already record every authentication that uses a legacy protocol — which account, which application, from where, how often. That list is usually shorter than feared: a few service accounts, an old multifunction printer that scans to mail, a script somebody wrote years ago. Each dependent is either moved to modern authentication, replaced, or fenced behind a narrowly scoped exception with an expiry, and only then is the protocol blocked tenant-wide. The order matters because a blanket block on day one turns an inventory problem into an outage, and the rollback that follows tends to stay open for years.

How many Global Administrator accounts should a tenant keep?+

Very few — enough for continuity, and no more. The pattern that works is a small number of individually named accounts whose admin rights are eligible rather than standing, activated per task through an approval and expiring within hours, plus one or two break-glass accounts that are excluded from conditional access, stored offline and alarmed the instant they sign in. What the number replaces matters more than the number itself: the dozens of standing grants that accumulate through migrations and vendor requests, most of which can be cut to a narrow role like Exchange or User Administrator, or removed entirely. Every standing Global Administrator is a full-tenant compromise waiting on one phished credential.

Next step

Review your tenant with us

A tenant review that names who effectively holds privileged roles today, which sign-ins still use legacy protocols, and the hardening order that closes both without a lockout.