Skip to content

Check whether MFA is required

Machine verified A machine ran this on our install and checked the result against the CLI. A test report is linked. CLI 0.4.0, checked 2026-10-28.

Is MFA required here?

Ask which MFA policy your organisation runs. Then read it yourself, and know what changes if you turn it up.

What you get: the organisation’s MFA policy mode in one word, and what each mode means for the people who sign in.

Ask in plain words:

quox · talking to Quox

What is my MFA policy mode?

▤ AOCL │ L1 identity complete · allowed · 1ms

▤ AOCL │ L3 policy gate complete · proceed · 9ms

◐ QUOX │ cli ✔ QUOX │ cli │ 0 exit code, 7483 duration ms · 11.1s

⛓ AEE │ envelope opened · ops.tool · quox_cli ok

⛓ AEE │ envelope opened · stream_success

Your org's MFA policy mode is optional. I read that live just now.

Users can enrol in MFA, but nothing forces them to. The other modes are  disabled  and  
required  [K1]. If you switch to  required , enrol your users first and change the
setting second. Anyone without MFA enrolled gets blocked at login once it's on [K2].

Sources: [K1] Install dependencies; [K2] STATUS_AND_LIMITS, Auth + Enterprise
Enforcement

24.2s · 1 tool · 0 approvals

A real turn on our own install (CLI 0.3.1, 28 Oct 2026), replayed at speed. Names changed. Type the same words into quox.
✔ Machine verified against the CLI on 28 Oct 2026 · test report mvrj7v

Quox read the live MFA policy for your organisation and changed nothing. The policy has three modes: disabled, optional and required. Under optional people can enrol in MFA but nothing makes them.

mfa get
quox security mfa getOrg MFA Policy────────────────────────mode   optional
From a real run on the demo profile.

quox security mfa set <mode> takes disabled, optional or required. That one writes, so run it on purpose. Before you set required, make sure your people have enrolled: anyone without MFA enrolled is blocked at sign in once it is on.