Techbanq

Cloud security · Azure

In Azure, the whole posture is decided in identity

In Azure the decisions that matter are made in Entra, in conditional access and in the privileged roles that can rewrite the tenant. An assessment reviews that identity plane, the Defender findings and the policy state together, because a network diagram tells you almost nothing about who in your tenant can already reach production.

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

Market
Saudi Arabia
Written for
CISO, CIO
Decision
Measure an Azure tenant's security posture

Cybersecurity credentials

  • National Cybersecurity Authority, Saudi Arabia

    NCA registration

    Registered cybersecurity service provider

  • ISO

    ISO/IEC 27001

    ISO/IEC 27001 certified

Certifications & registrations

Coverage

The parts of an Azure tenant that decide its security posture

Azure posture concentrates in identity, so the review weights it accordingly. These are the areas we read, and what a weakness in each one lets someone do.

Privileged roles

How many accounts hold Global Administrator and equivalent roles, whether they are permanent or activated on demand, and whether privileged access is time-bound.

What a weakness there exposes: A standing global administrator is a permanent master key; the number of them is often the single most important finding.

Conditional access

The policies that decide when a sign-in is allowed, whether they cover every critical application, and the gaps and exclusions that quietly bypass them.

What a weakness there exposes: A single excluded application or user group is the hole the whole policy set is bypassed through.

Legacy and weak authentication

Whether legacy protocols that cannot enforce multi-factor are still permitted, and how completely strong authentication is required across the tenant.

What a weakness there exposes: A legacy protocol left on is a route that ignores every conditional-access rule built above it.

Guests and external access

External identities invited into the tenant, what they can see, and whether their access was ever reviewed after the project that created it ended.

What a weakness there exposes: A guest account from a finished engagement is standing external access nobody is watching.

Defender and policy state

What Defender for Cloud is turned on for, the posture score and its open recommendations, and whether Azure Policy is enforcing or merely reporting.

What a weakness there exposes: A policy set to audit rather than enforce reports the drift it was bought to prevent.

Where the risk sits

In Azure, the network is not where the important decisions are made

A security review carried over from an on-premises habit starts with the network — subnets, firewalls, what talks to what. In Azure that instinct reads the least important layer first. The tenant is fronted by Entra, and almost every consequential action, from reading a storage account to reassigning a subscription, is authorised by an identity holding a role under a set of conditional-access rules. An attacker who has phished a credential does not attack the network; they sign in, and what they can then do is decided entirely by the identity configuration.

So the assessment is weighted to identity, and its central output is a map of who can reach what. The findings that change a tenant's security are almost always there: too many permanent global administrators, a conditional-access set with an exclusion that swallows the rule, a legacy protocol still accepting authentication that bypasses every modern control, a guest from a closed project who can still read a subscription. None of these is visible on a network diagram, and all of them are plain once the identity plane is read against a baseline.

The identity plane

How every identity in the tenant resolves to a level of access

Read left to right: the identities that exist, the controls that decide what each sign-in may do, and the access that results. The review reads the middle column hardest, because that is where a single exclusion changes the whole outcome.

A converging diagram: member users, guests and non-human identities pass through Entra, conditional access and privileged roles, which resolve to reach across subscriptions and, for privileged identities, the ability to rewrite the tenant itself.

  • Member users

    Staff accounts, their role assignments and how they authenticate.

  • Guest identities

    External accounts invited in, often long after the reason for them ended.

  • Service principals and managed identities

    Non-human identities that automation uses, which rarely get reviewed.

What we do

Entra, conditional access and privileged roles

Every sign-in is evaluated here. A role decides how much an identity may do; a conditional-access policy decides whether the sign-in is allowed at all — and an exclusion or a legacy protocol is a way around it.

  • Reach to subscriptions and resources

    What each identity can read, change or delete once the sign-in resolves.

  • Ability to rewrite the tenant

    The privileged identities that can change the controls themselves — the finding that outranks the rest.

A network diagram shows none of this. The identity plane is the tenant's real attack surface, and it is read, not exploited.

Our role

What we review across the tenant and what your team hardens

  1. 01

    We read the identity plane first

    The review is weighted to Entra, conditional access and privileged roles, because that is where an Azure tenant's risk concentrates, then extends to Defender and policy state around it.

  2. 02

    We map who can reach what

    The central deliverable is that map, with the privileged identities that can change the controls themselves flagged above everything else, because that finding outranks the rest.

  3. 03

    Your team tightens identity

    Reducing standing administrators, closing a conditional-access exclusion or retiring a legacy protocol are changes your team makes, because each one affects who can work and needs your operational judgement to time.

When to tighten a privileged role or remove a legacy path is your operational call, since each one changes who can work; we read the identity plane against a baseline, rank the findings by who they let in, and write the change that closes each.

Common questions

What buyers ask

How does an Azure assessment differ from the AWS one?+

The method is the same — a read-only review against a baseline — but the weight falls differently. An AWS review spreads fairly evenly across identity, network, logging, encryption and data exposure. An Azure review concentrates on identity, because Entra fronts the whole tenant and the findings that change a tenant's security are almost always in privileged roles, conditional access and legacy authentication rather than in the network. The two also read different native tooling — the AWS security tooling and Defender for Cloud respectively — and against different benchmarks. If you run both clouds, the assessments are related in shape but genuinely separate in content; one does not stand in for the other.

Does Microsoft Defender for Cloud already do what this assessment does?+

It is an important input and we read its posture score and recommendations closely, but it is a tool reporting findings, not a judgement about your tenant. It scores against a general standard, does not weigh a recommendation by what it actually exposes in your case, and cannot tell you that two of its findings chain together into a path to global administrator. The assessment uses Defender's output as one source among several, adds the reasoning about privileged access and conditional-access gaps that a score cannot express, and returns a ranked, contextual picture rather than a list. Where Defender is not fully turned on — which is common — that gap in coverage is itself one of the first findings.

Which Entra roles do you need to run the review?+

Read-only directory and security reader roles, plus reader access to the subscriptions in scope — nothing that can change a setting. The whole review is conducted by reading configuration, which is deliberate: it keeps the engagement safe for you and clean for the record, since an external party holding a role that can alter identity in production would be a finding in its own right. Where a specific check needs to see something the standard reader roles do not expose, we name exactly what and why, and you decide whether to grant it for the duration rather than up front.

Next step

Grant a directory reader role

A read-only assessment of the Azure tenant led by the identity plane, returning who can reach what, the privileged-access and conditional-access gaps, and the fix for each — before a penetration test is scoped.

Grant a directory reader role

What happens next

  1. 1We reply within one business day.
  2. 2A 30-minute scoping call with a senior consultant.
  3. 3A written proposal with scope, team, and timeline.

Or reach us directly

By submitting this form you agree to our Terms of Use and Privacy Policy.