Multi-Factor Authentication

Current status page for MFA and related identity controls in Disclosurely.

Multi-factor authentication adds a second identity check beyond a password before a user can access an application.

What Disclosurely Supports

Public materials currently focus on account authentication, session management, and role-based access controls.
Enterprise identity controls such as SSO and enforced MFA should be reviewed against current product availability during procurement.
Buyers can use this page to separate current authentication controls from planned or customer-specific identity requirements.

Disclosurely does not currently present enforced MFA as a generally available production control in public documentation.
Disclosurely does not claim support for authenticator apps, SMS codes, hardware security keys, or recovery workflows unless confirmed in current product materials.
Disclosurely does not claim that MFA alone resolves access governance, user provisioning, or investigation-role design.

Ask whether enforced MFA is available for the deployment you are buying.
Confirm whether SSO or identity-provider integration is available or planned.
Review password, invitation, and session behaviour.
Confirm how administrator and case-handler roles are assigned and revoked.
Document any compensating controls your organisation requires until MFA is available.

Do not assume it is available from public content alone. Confirm current availability during procurement or product review.

Many enterprise buyers expect MFA for administrative access. If MFA is required by policy, record that requirement during security review.

Review password handling, session controls, least-privilege permissions, administrator access, user offboarding, and audit history.