> For the complete documentation index, see [llms.txt](https://docs.balkan.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.balkan.id/compliance-controls-and-posture/compliance-posture.md).

# Compliance posture

Use **Dashboard → Compliance Posture** to monitor compliance results.

Admins and risk managers can access this area.

This is the operational view of Compliance. Use it to understand current framework health, investigate violations, and manage accepted risk during review.

For the configuration workflows behind posture, see [Compliance controls](/compliance-controls-and-posture/compliance-controls.md). For the rule behavior behind hidden versus visible risk, see [Suppressions and exceptions](/compliance-controls-and-posture/suppressions-and-exceptions.md). For a broader tenant-wide discovery view, see the [BalkanID Summary Dashboard](/getting-started/entitlement-data-discovery/balkanid-summary-dashboard.md).

<div data-with-frame="true"><figure><img src="/files/a8yD7e6JLDSFTiggxGzs" alt=""><figcaption></figcaption></figure></div>

***

### Summary dashboard

The summary view starts with stat tiles which highlight your current compliance posture.

* **Active Violations**
* **Violations Marked as Exception**
* **Total Exception Rules**
* **Blanket Suppression Rules**
* **Scoped Suppression Rules**
* **Total Suppression Rules**

Below the tiles, we show one card per active framework showing compliance percentage and violation counts.

Select a framework card to open its detail view.

The tile counts and framework states use the same [criteria health states](/compliance-controls-and-posture/compliance-overview.md#criteria-health-states) described in the overview.

***

### Framework detail view

Each framework has a dedicated summary view, showing a general overview of the framework from a compliance posture perspective, with information on the:

* overall compliance percentage,
* criteria health
* and violation counts.

This also includes a chart showing:

* severity levels at a glance,
* a per-integration display of violation and criteria status,
* and a detailed table for criteria health (which also show details on the controls mapped to each criteria).

You click through into the tables and charts to be taken to a filtered and granular view of the underlying violations.

This view is designed for investigation. You can move from framework-wide trends down to a single criterion or a filtered set of violations in a few clicks.

***

### Violations table

The **Violations** tab lists every compliance violation in a granular and easily-filterable manner.

Each row can show:

* Framework
* Criterion
* Severity
* Entity and entity type
* Integration
* Control which was violated (and mitigation details)
* Created date
* Exception status

You can inspect who is affected, what control triggered the finding, and whether the issue should remain active or be excepted.

You can also view further details on the control that flagged a particular violation, as well as any **mitigation recommendations**, by clicking on the control cell in the table.

***

### Add an inline exception

If a violation is not excepted, the row shows **Add Exception**.

Use it to create a scoped exception from the violation itself.

{% stepper %}
{% step %}

### Open the quick exception panel

Click **Add Exception** in the violation row.
{% endstep %}

{% step %}

### Review the violation context

The panel shows framework, criterion, severity, and entity details.

Add a reason if needed.
{% endstep %}

{% step %}

### Save the exception

Submit the exception.

BalkanID refreshes the table after success.
{% endstep %}
{% endstepper %}

After success, BalkanID confirms:

> Exception added. Matching violations will be marked as excepted.

If a violation is already excepted, the row shows an **Excepted** badge.

The badge tooltip shows the exception reason.

Admins can use the badge to jump to the matching exception rule in [Compliance controls](/compliance-controls-and-posture/compliance-controls.md#exceptions-tab).

Inline exceptions let risk managers participate in posture review without giving them full configuration access to the [Compliance controls](/compliance-controls-and-posture/compliance-controls.md) area.

***

### Out-of-date posture warning

A yellow banner appears if control configuration changed since the last scan.

It warns that summary statistics may be stale.

Queue a recompute from [Compliance controls](/compliance-controls-and-posture/compliance-controls.md#recompute-compliance-violations) to refresh the dashboard.


---

# 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:

```
GET https://docs.balkan.id/compliance-controls-and-posture/compliance-posture.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.