Security
Conditional access, multi-factor authentication, threat protection, security health, and the administrator team.
The Security section is where you harden the login surface and govern who can do what. It brings together six areas, reachable from the Security navigation of the Admin Console (Admin Console users sits under Governance):
- Conditional access — decide when a second factor, step-up, or block applies, based on attributes, network location, device state, risk, and time. Includes authentication policies, device compliance policies, and network zones.
- Multi-factor authentication — the global MFA factors you enable for everyone (TOTP, passkeys, security keys, SMS, email, recovery codes), enrollment, and per-directory requirements.
- Threat protection — automatic defenses against bots, brute force, credential stuffing, and breached passwords.
- Security health — a dashboard that scores your configuration against established security frameworks and points you at the gaps.
- Admin Console users — managing the administrator team and what each access level can do.
- Break-glass emergency access — regain administrative access in an emergency, through a dedicated hardware-key standby account, with strong controls and a full audit trail.
How the pieces fit together
The platform separates the catalog of what is possible from the rules that decide when:
- Multi-factor authentication sets which factors exist and can be enrolled at all. Without an enabled factor, no policy can require it.
- Authentication policies then decide, per situation, whether MFA (or a stronger assurance level) is actually demanded — pulling in network zones and device compliance as conditions.
- Threat protection runs underneath every login independently of policies, throttling abuse and blocking known-bad credentials. It also honors network zones as trusted-bypass lists.
- Security health continuously inspects all of the above and tells you where your configuration falls short of a chosen framework.
Most threat-protection defenses are on by default, so a new instance is already protected before you configure a single policy.
Where to go next
- Start with multi-factor authentication to choose your factors.
- Review threat protection to confirm the defaults match your risk appetite.
- Use conditional access to apply stricter rules to sensitive groups, networks, or applications.
- Check the security health dashboard to measure your posture against a framework.
- To harden a single high-value application rather than the login surface, apply a Financial-grade API security profile. It is configured on the application itself, under Integrations, and affects only that application.