> For the complete documentation index, see [llms.txt](https://docs.intuneassistant.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intuneassistant.cloud/intune-assistant/security-insights/controls.md).

# Controls

## What it does

The Controls page lists every control Security Insights judges, with its result in the latest check. Open a control to see why it has that result, which accounts are involved, how it moved over time and what to do about it.

There are 21 controls: 11 about Entra ID and sign-in, and 10 about Exchange Online and Defender for Office 365.

## How to use it

1. Select **Security Insights > Controls** in the sidebar.
2. Filter by result with **All**, **Fail**, **Could not check**, **Accepted**, **Pass** and **Not applicable**. Each shows its count.
3. Use **Search controls** to match a name or reason.
4. Select a row to open the control.

Selecting a severity on the Overview opens this page filtered on failing controls of that severity, with a chip "High severity only · clear".

## What each row shows

The result, the severity, the name, the reason, and for account controls the number of accounts, for example "3 privileged accounts". Rows are sorted failing first, then could not check, accepted, not applicable and pass; within each by severity.

## A control in detail

| Block                                | Shows                                                                                                                             |
| ------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------- |
| Header                               | The result, the severity, when it was checked, the name and, for Fail, Could not check and Accepted, the reason                   |
| What was measured                    | The values the result is based on. Nothing is shown when nothing was measured                                                     |
| What this checks                     | The description, the data it reads and a licence note when it needs one                                                           |
| History                              | The result in each stored check over the last 90 days and a sparkline of the main number. It appears from the second stored check |
| What to do                           | Guidance with steps, shown when the control does not pass                                                                         |
| Accounts                             | For account controls: the accounts that fail, are accepted or pass. Open a row to sanction the account or accept it for a while   |
| Conditional Access policies involved | The ids of the policies that played a part. Open them in the Entra admin center under Protection > Conditional Access             |

## The controls

### Entra ID and sign-in

These are read when you run a check yourself and by the scheduled check.

| Control                                     | Severity | What it checks                                                                                               | Needs       |
| ------------------------------------------- | -------- | ------------------------------------------------------------------------------------------------------------ | ----------- |
| MFA required for all users and all apps     | High     | One enabled Conditional Access policy requires MFA for every user and every app without weakening carve-outs | Entra ID P1 |
| Every member user has MFA registered        | High     | No enabled member user is without a registered MFA method                                                    |             |
| Every privileged account has MFA registered | High     | No privileged role holder is without a registered MFA method                                                 |             |
| Only sanctioned privileged accounts         | High     | Every privileged role holder (active, eligible or via group) is a sanctioned account                         |             |
| Only sanctioned Global Administrators       | High     | Every Global Administrator (active, eligible or via group) is a sanctioned account                           |             |
| Passwords do not expire                     | High     | The default domain is set to never expire passwords                                                          |             |
| User consent to apps is restricted          | Medium   | Users may only consent to low-risk permissions of verified publishers, or not at all                         |             |
| Security Defaults is off                    | Low      | Security Defaults should be off when Conditional Access is used. Not applicable without Entra ID P1          |             |
| Guest access is limited                     | Low      | Guests do not have member-level access and not everyone can invite guests                                    |             |
| Users cannot create security groups         | Low      | Regular users are not allowed to create security groups                                                      |             |
| Company branding is configured              | Low      | Company branding is set up on the sign-in pages                                                              |             |

### Exchange Online and Defender for Office 365

These controls need the Exchange Online data of the **scheduled check of your Worker**. The check you start yourself does not read it, so these controls show **Not applicable** for it. If the Worker could not read Exchange (the `Exchange.ManageAsApp` role or the Entra role is missing), they show **Could not check**. They are never shown as passed.

| Control                                        | Severity | What it checks                                                                                                                                          | Needs                   |
| ---------------------------------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------- |
| Anti-phishing protection is applied            | Medium   | A preset security policy, or a custom anti-phishing policy with spoof intelligence and quarantine, applies to every recipient                           |                         |
| Anti-spam protection is applied                | Medium   | A preset policy, or an anti-spam policy that quarantines high confidence spam and phishing and keeps quarantine for 30 days, applies to every recipient |                         |
| Anti-malware protection is applied             | Medium   | A preset policy, or an anti-malware policy with zero-hour purge and the common attachment filter for the risky file types, applies to every recipient   |                         |
| Outbound spam limits are applied               | Medium   | A preset policy, or an outbound spam policy that limits recipients per hour and per day and blocks a user who reaches the limit                         |                         |
| Safe Links is applied                          | Medium   | A preset policy, or a Safe Links policy that scans URLs in mail, Teams and Office apps, applies to every recipient                                      | Defender for Office 365 |
| Safe Attachments is applied                    | Medium   | A preset policy, or a Safe Attachments policy that blocks, together with protection for SharePoint, OneDrive and Teams                                  | Defender for Office 365 |
| Shared mailboxes cannot sign in                | Medium   | No shared mailbox has its account sign-in enabled                                                                                                       |                         |
| The unified audit log is on                    | Low      | Audit log ingestion is turned on for the organisation                                                                                                   |                         |
| Mailbox auditing is on for every mailbox       | Low      | Auditing is not disabled for the organisation and no mailbox has it turned off                                                                          |                         |
| Calendars are not shared with anonymous people | Low      | No sharing policy shares calendar information with anonymous people                                                                                     |                         |

## When a control could not be checked

A control shows **Could not check** when the data it needs could not be read, for example a missing role or consent. It is never counted as passed. The **Coverage of this check** block on the [Overview](https://docs.intuneassistant.cloud/intune-assistant/security-insights/overview.md) names the data source and what to do.
