# Conditional access

Decide when MFA, step-up, or a block applies, using authentication policies, device compliance, and network zones.

Conditional access is how you apply *the right amount of security to the right situation*, instead of forcing identical requirements on every login. A trusted office login can stay frictionless while a login from an unknown network, an unmanaged device, or a risky context is stepped up or blocked.

Three building blocks work together:

- **[Authentication policies](https://dts-identity.com/docs/security/conditional-access/authentication-policies.md)** — the decision engine. Each policy holds rules that match on conditions (who, from where, on what device, at what time, at what risk) and then decide the outcome: allow, require MFA, require a higher assurance level, or deny.
- **[Device compliance policies](https://dts-identity.com/docs/security/conditional-access/device-compliance-policies.md)** — evaluate whether an enrolled device meets your security bar (disk encryption, firewall, OS version, and so on). Their result becomes a condition that authentication policies can act on.
- **[Network zones](https://dts-identity.com/docs/security/conditional-access/network-zones.md)** — named sets of IP ranges and locations, marked trusted or left untrusted. They are referenced as conditions in authentication policies and as bypass lists in [threat protection](https://dts-identity.com/docs/security/threat-protection.md).

## How they relate

A typical flow ties all three together:

1. A user signs in. The platform knows their attributes, the **network zone** their IP falls in, and — if device trust is in use — whether their **device is compliant**.
2. The matching **authentication policy** rule fires. For example: *if the user is in the Finance group and not on a trusted network, require a phishing-resistant second factor; if their device is non-compliant, deny.*
3. The user is allowed, prompted to step up, or blocked accordingly.

Network zones and device compliance are inputs; authentication policies are where the decision is made.

## Availability

These features sit on higher tiers and, for device compliance, behind an add-on. Each page below opens with its own plan callout. In short:

- **Authentication policies** and **network zones** — Advanced and above (Trial includes a small number of each).
- **Device compliance policies** — the DIAM add-on plus a higher tier.

See [Plans & add-ons](https://dts-identity.com/docs/getting-started/plans-and-addons.md) for the full matrix.

## Where to go next

- Define [network zones](https://dts-identity.com/docs/security/conditional-access/network-zones.md) first — they are reused everywhere.
- Build [authentication policies](https://dts-identity.com/docs/security/conditional-access/authentication-policies.md) to set conditional MFA and step-up.
- Add [device compliance policies](https://dts-identity.com/docs/security/conditional-access/device-compliance-policies.md) if you manage endpoints with the device add-on.
