# Security health

A dashboard that scores your configuration against established security frameworks and shows where the gaps are.

The Security Health dashboard inspects your live configuration and scores it against established security frameworks. It turns abstract compliance requirements into a concrete checklist, shows where you fall short, and links each gap to the screen that fixes it.

Open it under **Security → Security health**.

[Image: The Security health page with its check results]

## How it works

Each time you open the page, the platform reads your current settings — password policies per directory, MFA factors, threat-protection toggles, session timeouts, administrator setup, application redirect URIs, and more — and evaluates a catalog of checks against them. Nothing is stored or simulated; the score always reflects the configuration as it stands right now.

Every check returns one of:

- **Pass** — the configuration meets the requirement.
- **Open** — a gap that lowers your score (a failure or a warning).
- **Not applicable / not supported** — the check does not apply, or it tests a capability the platform cannot satisfy today. These are shown separately and do **not** count against your score.

## Frameworks

The same configuration is judged against several frameworks side by side, each on its own tab. A given setting may pass one framework and fail another, because each states its own bar — for example, frameworks differ on the minimum password length they require. The tabs appear in this order:

| Framework | Focus |
|---|---|
| **Best practices** | General hardening recommendations for identity systems. |
| **BSI C5** | The German cloud-computing compliance criteria catalog. |
| **NIST SP 800-63B** | The US digital-identity authenticator and assurance-level standard. |
| **NIS2** | The EU technical measures for essential and important entities. |
| **DORA** | EU 2022/2554 — the digital operational-resilience act for financial entities. |
| **ISO/IEC 27001** | Annex A identity and authentication controls. |
| **CIS Controls v8** | Account and access-management safeguards. |
| **PCI DSS 4.0** | Authentication requirements for card-data environments. |

Each framework tab groups its checks by topic (passwords, MFA, sessions, accounts, logging, and so on) and shows the relevant clause reference next to each check.

Two framework checks depend on configuration outside the security screens: periodic access recertification passes once at least one application is covered by a [certification workflow](https://dts-identity.com/docs/workflows/access-certifications.md), and federated single logout passes once every interactive OIDC application has a back-channel logout URI configured (see [Applications](https://dts-identity.com/docs/integrations/applications.md)).

## Best-practice checks

The **Best practices** tab is the most actionable starting point — it bundles general hardening recommendations independent of any one standard. Each check links to the screen that fixes it. The main checks are:

| Check | What it looks for | Where to act |
|---|---|---|
| Administrator MFA | Every admin-console user has an MFA factor enrolled. | [Admin Console users](https://dts-identity.com/docs/security/admin-console-users.md), [MFA](https://dts-identity.com/docs/security/multi-factor-authentication.md) |
| Owner count | The number of full-control owners is kept small. | [Admin Console users](https://dts-identity.com/docs/security/admin-console-users.md) |
| Strong factor enabled | At least one strong factor (authenticator app or WebAuthn) is available. | [MFA](https://dts-identity.com/docs/security/multi-factor-authentication.md) |
| Bot detection | The bot detection is on. | [Threat protection](https://dts-identity.com/docs/security/threat-protection.md) |
| The bot detection response | At least one form is set to Block; Monitor on every form only counts. | [Threat protection](https://dts-identity.com/docs/security/threat-protection.md) |
| Open signup | Self-service signup is gated (e.g. by a registration code) rather than fully open. | [Registration settings](https://dts-identity.com/docs/settings/registration.md) |
| Stale accounts | No active accounts have been dormant past the threshold. | [People](https://dts-identity.com/docs/directories/people.md) |
| Application redirect URIs | No application uses an insecure (plain-http, non-local) redirect URI. | [Applications](https://dts-identity.com/docs/integrations/applications.md) |
| Security notifications | Lockout and breach notifications are enabled so users hear about account events. | [Threat protection](https://dts-identity.com/docs/security/threat-protection.md) |

Session-lifetime, re-authentication, password-policy, and assurance-level (step-up) requirements are evaluated on the **standards** tabs (NIST and the others), each against that standard's own bar.

## The score gauge

At the top, a gauge summarizes your standing as a percentage — the share of *scored* checks that pass. Checks that are not applicable, not supported, or hidden are excluded from the calculation, so the score reflects only what you can actually act on. Switch framework tabs to see how your posture changes against a different standard.

## Using the dashboard

1. Pick the framework most relevant to your organization.
2. Review the **open** checks first — these are your gaps, ordered by impact.
3. Open a check to read what it expects and why. Many checks include a **remediation link** that takes you straight to the setting that resolves it (for example, the MFA, threat-protection, or administrator screens).
4. Apply the change, then reload the dashboard to confirm the check now passes.

Work through high-impact gaps before low-impact ones; the impact level is shown on each check.

## Hiding and restoring recommendations

Some best-practice recommendations may not apply to your situation. You can **hide** such a recommendation to remove it from your active list and from the score. A hidden item moves to a separate list and can be **restored** at any time.

Both hiding and restoring are recorded in the [audit log](https://dts-identity.com/docs/monitoring/audit-logs.md), with the recommendation and the administrator who acted. Only the general best-practice recommendations can be hidden — framework checks (NIST, C5, and the rest) cannot be hidden, so your compliance view stays honest.

## Related

- [Multi-factor authentication](https://dts-identity.com/docs/security/multi-factor-authentication.md) and [threat protection](https://dts-identity.com/docs/security/threat-protection.md) — the settings most checks evaluate.
- [Admin Console users](https://dts-identity.com/docs/security/admin-console-users.md) — administrator-related checks (MFA, number of owners).
- [Audit logs](https://dts-identity.com/docs/monitoring/audit-logs.md) — where hide/restore actions are recorded.
