THE ALIGNR CONTROLS LIBRARY

Set the standard.
See the evidence.

Start with our standard Alignr Baseline library, or build your own controls and standards from integration data. Define what good looks like for each client, then check the evidence against it.

18 baseline controls5 areas of coverage5 distinct outcomes
Your standard. Verified.Alignr Baseline
Identity protection

Multi-factor authentication

Evidence → Control → Outcome
Account statusActive
MFA registrationNot registered
Needs attention

An active account has no registered MFA method.

A clear outcome, backed by evidence.

Define your standard

Use the standard library or create your own controls from integration data.

Evaluate the evidence

Check observed facts against each control.

Explain the outcome

Keep findings and coverage gaps distinct.

A BASELINE, NOT A CEILING

Our library to get started.
Your standards to make it yours.

Start with the standard library

Use the controls shipped with Alignr as a starting point for consistent technical alignment across your clients.

Build from your integration data

Create your own controls using the facts supplied by connected tools. Define the conditions and thresholds that matter to your service.

Shape your own standards

Bring controls together around your operating standards, with client-specific requirements and exceptions reflected in the review.

ALIGNR BASELINE

Know what’s being checked.

Explore the baseline checks across your environment. Each result depends on the connected integrations and evidence available.

18 of 18 controls

Identityhigh priority

No MFA bypass in effect

No account should carry an active MFA bypass. A bypass is sometimes granted for a genuine device-loss emergency, but one left switched on is a standing hole in the MFA policy it was meant to be a temporary exception to.

Explore this control
COVERAGE IS PART OF THE ANSWER

No evidence.
No assumed pass.

A missing connection or an empty result should never look like a healthy environment. Alignr records the difference.

Pass

The observed evidence meets the control.

Fail

The observed evidence does not meet the control.

No data

A supporting integration is connected and mapped, but the required facts have not arrived.

Not covered

The required evidence is not supplied by this client’s connected, mapped integrations.

Not applicable

The control is disabled or excluded for this organisation, with a recorded reason.

YOUR CLIENTS. YOUR STANDARD.

Bring technical alignment
into the everyday.

See how controls connect to findings, technician actions and client conversations.

Join Waitlist for Early Access