> For the complete documentation index, see [llms.txt](https://docs.bsure.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bsure.io/v1/user-guides/security/dashboard.md).

# Dashboard

#### Security tiles

* **User accounts:** User accounts not logged in last 90 days should be reviewed to ensure that they should still be active, and if not they should be disengaged
* **Guest accounts:** Inactive guest accounts should be removed as a guest account with rights can be just as dangerous as a member of the company
* **Multi-factor Authentication:** Users without multi factor authentication configured could be a security risk. What will happen if someone guess the correct password to one of these accounts? Break the glass accounts should also have a separate MFA method configured ref <https://learn.microsoft.com/en-us/entra/identity/role-based-access-control/security-emergency-access>.
* **Administrative privileges:** Users with administrative privileges will provide you with information on active [Entra ID roles](https://learn.microsoft.com/en-us/entra/identity/role-based-access-control/permissions-reference) assigned to users or applications
* **Service principals:** Service Principals is often used when integrating third party solutions with Entra ID. They have an application id and a secret just as a member user have username and password. These Service Principals skips all security measures such as conditional access and the can be used from everywhere. Giving these "users" high permissions, such as read all mailboxes, create users and such means that you should monitor usage of these Service Principals. Where do the sign in from and did you know that these permissions was given the holder of the application id and the corresponding secret value? Consider adopting [Microsoft best practice guidance](https://learn.microsoft.com/en-us/entra/architecture/secure-best-practices#service-principals-credentials)

<figure><img src="/files/WksxjT72a0VWw3AcLApO" alt=""><figcaption></figcaption></figure>

#### Sign in map

Simply a world map showing which countries your member users have successfully signed in from the last 14 days. Look at the map for unwanted sign-ins from specific countries such as i.e Russia or China

<figure><img src="/files/pYPPXKFzyeF9ZXU8ej5h" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bsure.io/v1/user-guides/security/dashboard.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
