> For the complete documentation index, see [llms.txt](https://docs.dispel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dispel.com/secure-and-govern/overview/universal-controls.md).

# Universal Controls

The 45 controls Dispel checks on your tenant, and the settings that decide whether the configurable ones pass.

Dispel checks your tenant against 45 Universal Controls. Each is based on a NIST SP 800-53 Rev 5 control and mapped to the requirements of every framework you select, so one result counts toward NIST 800-53, NERC CIP, NIS2, and the rest of the [supported frameworks](https://docs.dispel.com/secure-and-govern/overview/supported-frameworks.md). You'll find them in the app under [**Security → Compliance → Controls**](https://app.dispel.com/security/compliance/controls).

## Who owns each control

Each control is marked Platform, Configurable, or Shared.

Platform controls are part of how Dispel is built, such as encrypted tunnels and deny-by-default network access. You inherit them without doing anything.

Configurable controls depend on your organization's settings. Dispel has the capability, but the control passes only once you've turned it on. The next section lists what each one needs.

Shared controls are split between Dispel and you. Dispel checks its part, but an auditor will also expect your part: for example, PS-4 Personnel Termination assumes you deactivate people promptly when they leave.

## Turn on the Configurable controls

| Control                | Passes when                                                                                                                         | Setting                                                                                                                                                               |
| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| IA-2, IA-2(1), IA-2(2) | Two-factor authentication or SSO is enforced for the whole organization. If you rely on SSO, enforce MFA in your identity provider. | **Require two-factor authentication** or **Force Organization members to use SSO to authenticate** in [Settings → Security](https://app.dispel.com/settings/security) |
| IA-5(1)                | Passwords expire after a maximum lifetime of 1 day or more, or SSO is enforced.                                                     | **Enforce password min/max lifetime policy** in [Settings → Security](https://app.dispel.com/settings/security)                                                       |
| IA-5(1).e              | A set number of previous passwords (1 or more) is remembered, or SSO is enforced.                                                   | **Enforce password reuse policy** in [Settings → Security](https://app.dispel.com/settings/security)                                                                  |
| AC-12 (access windows) | At least one role has to request access windows.                                                                                    | Any of the **Require access windows for Organization …** options in [Settings → Security](https://app.dispel.com/settings/security)                                   |
| AU-12                  | Regions are allowed to record Browser Connect sessions.                                                                             | **Allow Regions to record Browser Connect sessions** in [Settings → Browser Connect](https://app.dispel.com/settings/browser-connect)                                 |
| AC-6                   | At least one member isn't an Organization Admin.                                                                                    | Member roles in [Users](https://app.dispel.com/members)                                                                                                               |
| AU-6 (both)            | Your organization has the Session Forensics add-on.                                                                                 | Ask your Dispel account team                                                                                                                                          |

After changing a setting, open the control, click the failing assessment objective, and click **Run Assessment** to update the result.

AC-7, AC-2(3), and SI-3 are also marked Configurable, but they pass on Dispel's defaults. Dispel rate-limits sign-in attempts and expires idle sessions on its own. **Suspend user temporarily if repeated login attempts fail** and **Enforce inactivity lockout policy** in [Settings → Security](https://app.dispel.com/settings/security) add stricter limits of your own. SI-3 is met by the disposable virtual desktops users connect through.

## What the Shared controls check

* **CM-6:** at least one compliance framework is selected.
* **CM-7:** your Regions have ACL rules. An organization with no Regions passes, since nothing can be reached.
* **CM-8:** at least one device is registered, or an asset-discovery integration has synced.
* **AC-2:** your organization has members.
* **IA-4:** your organization has no [shared accounts](https://docs.dispel.com/manage-users-and-access/users/shared-accounts.md). Each account has to belong to one person, so IA-4 fails while any shared account exists. **Remediate** on its recommendation, **Remove Shared Accounts**, opens [Users](https://app.dispel.com/members), where each one is tagged **Shared Account**. Turning off shared accounts in Settings isn't enough: IA-4 counts the shared accounts that still exist.
* **PS-4, IA-8(2), AC-12 (session timeout), and CM-3** pass on what Dispel provides: account disabling and identity-provider deprovisioning; sign-in through SAML, OAuth, OIDC, or Microsoft; session expiry; and a log of every settings change.

## How Dispel checks Platform controls

Most Platform controls are checked against how Dispel itself is built. SA-4, SI-2, and IR-8 are checked against Dispel's published [support policy](https://legal.dispel.com/support/support-policy), [maintenance windows](https://legal.dispel.com/support/maintenance-windows), and [technical and organizational measures](https://legal.dispel.com/security-and-data-protection/how-we-protect-you/technical-and-organizational-measures).

## Statuses

A control that has never been checked shows **Not Yet Assessed** until you click **Perform Baseline Assessment**. After that it shows **Passing** or **Failed**. Failed also covers controls that are only partly in place. Controls that don't apply to your selected frameworks show **N/A**. Checking a control only reads your configuration; it doesn't change it.

Click any control to see which assessment objectives passed or failed, the evidence behind each one, and the framework requirements it maps to.

## The full list

AC-12 and AU-6 each appear twice because Dispel checks two separate things against them.

| Code      | Control                                                          | Type         |
| --------- | ---------------------------------------------------------------- | ------------ |
| AC-2      | Account Management                                               | Shared       |
| AC-2(3)   | Disable Accounts                                                 | Configurable |
| AC-3      | Access Enforcement                                               | Platform     |
| AC-4      | Information Flow Enforcement                                     | Platform     |
| AC-6      | Least Privilege                                                  | Configurable |
| AC-7      | Unsuccessful Logon Attempts                                      | Configurable |
| AC-11     | Device Lock                                                      | Platform     |
| AC-12     | Session Termination (session timeout)                            | Shared       |
| AC-12     | Session Termination (access windows)                             | Configurable |
| AC-17(1)  | Monitoring and Control                                           | Platform     |
| AC-17(2)  | Protection of Confidentiality and Integrity Using Encryption     | Platform     |
| AC-17(3)  | Managed Access Control Points                                    | Platform     |
| AC-17(4)  | Privileged Commands and Access                                   | Platform     |
| AU-2      | Event Logging                                                    | Platform     |
| AU-3      | Content of Audit Records                                         | Platform     |
| AU-6      | Audit Record Review, Analysis, and Reporting (session forensics) | Configurable |
| AU-6      | Audit Record Review, Analysis, and Reporting (SOC monitoring)    | Configurable |
| AU-9      | Protection of Audit Information                                  | Platform     |
| AU-12     | Audit Record Generation                                          | Configurable |
| CM-3      | Configuration Change Control                                     | Shared       |
| CM-6      | Configuration Settings                                           | Shared       |
| CM-7      | Least Functionality                                              | Shared       |
| CM-8      | System Component Inventory                                       | Shared       |
| IA-2      | Identification and Authentication (Organizational Users)         | Configurable |
| IA-2(1)   | Multi-factor Authentication to Privileged Accounts               | Configurable |
| IA-2(2)   | Multi-factor Authentication to Non-privileged Accounts           | Configurable |
| IA-4      | Identifier Management                                            | Shared       |
| IA-5(1)   | Password-based Authentication                                    | Configurable |
| IA-5(1).e | Password History                                                 | Configurable |
| IA-8      | Identification and Authentication (Non-organizational Users)     | Platform     |
| IA-8(2)   | Acceptance of External Authenticators                            | Shared       |
| IA-11     | Re-authentication                                                | Platform     |
| IR-5      | Incident Monitoring                                              | Platform     |
| IR-8      | Incident Response Plan                                           | Platform     |
| MA-4      | Nonlocal Maintenance                                             | Platform     |
| PS-4      | Personnel Termination                                            | Shared       |
| SA-4      | Acquisition Process                                              | Platform     |
| SC-7      | Boundary Protection                                              | Platform     |
| SC-8      | Transmission Confidentiality and Integrity                       | Platform     |
| SC-10     | Network Disconnect                                               | Platform     |
| SC-12     | Cryptographic Key Establishment and Management                   | Platform     |
| SC-13     | Cryptographic Protection                                         | Platform     |
| SC-23     | Session Authenticity                                             | Platform     |
| SI-2      | Flaw Remediation                                                 | Platform     |
| SI-3      | Malicious Code Protection                                        | Configurable |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dispel.com/secure-and-govern/overview/universal-controls.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
