> For the complete documentation index, see [llms.txt](https://intuitem.gitbook.io/ciso-assistant/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://intuitem.gitbook.io/ciso-assistant/product-docs/features/applied-controls-analytics.md).

# Applied controls analytics

The **Applied controls analytics** view turns the controls list into a one-page picture: how many controls do we have, how are they spread across status / priority / category / CSF function, what's overdue, who owns the most.

It complements the table — same data, different lens — and respects whatever filters were active on the table when you opened it.

## Where to find it

* **From the controls table** — the chart-pie icon (`Applied controls analytics`) in the toolbar of `/applied-controls`. The filters currently applied to the table are carried over verbatim, so the analytics page reflects the exact slice you were looking at.
* **From an audit's action plan** — each compliance assessment detail page has an `Action plan` sub-route with its own analytics button. Same dashboard, scoped to the controls in that audit's action plan.
* **From a risk assessment's action plan** — same pattern.
* **From an EBIOS RM study's action plan** — same pattern.

When you open the analytics page from the table with active filters, a violet pill above the dashboard reads *"Analytics reflect the filters applied on the table."* — your reminder that the numbers below are not your whole estate.

## What it shows

The dashboard surfaces several blocks, all computed live from the filtered queryset (no scheduled refresh, no cache):

| Block                 | What it answers                                                                                               |
| --------------------- | ------------------------------------------------------------------------------------------------------------- |
| **Total controls**    | The headline count for the filtered set                                                                       |
| **Total annual cost** | Sum of computed annual costs across the filtered set                                                          |
| **By status**         | Counts and cost per status bucket — To do, In progress, On hold, Active, Degraded, Deprecated, plus "not set" |
| **By priority**       | Counts and cost per P1 / P2 / P3 / P4                                                                         |
| **By category**       | Counts and cost per category                                                                                  |
| **By CSF function**   | Counts and cost per Identify / Protect / Detect / Respond / Recover (when set)                                |
| **ETA distribution**  | Five buckets — overdue / due within 30 days / due within 90 days / later / no ETA set                         |
| **Top owners** (10)   | Owners with the most controls; each broken down internally by status                                          |
| **Top domains** (10)  | Domains with the most controls                                                                                |

## Cost computation

Per-control annual cost combines the `build` and `run` blocks from the control's cost JSON:

* `build.fixed_cost / amortization_period` + `(build.people_days × daily_rate) / amortization_period`
* `run.fixed_cost` + `(run.people_days × daily_rate)`

`daily_rate` comes from **Settings → General → Daily rate** (defaults to 500 in the configured global currency). Controls without a `cost` block contribute zero — they're still counted under **Total controls**, just not under **Total annual cost**.

## Other view modes for applied controls

The controls table exposes two alternative views alongside this one:

* [**Flash mode**](/ciso-assistant/product-docs/features/flash-mode.md) — flashcards for rapid posture establishment.
* [**Kanban mode**](/ciso-assistant/product-docs/features/kanban-mode.md) — drag-and-drop status board with swimlanes per domain.

All three (analytics, flash, kanban) share the same filter passthrough — clicking any of them from the table carries the current filter querystring over.

## Related

* [Dashboards](/ciso-assistant/product-docs/features/dashboards.md) — composed metric surfaces built from Metrology widgets
* [Audit advanced analytics](/ciso-assistant/product-docs/features/audit-analytics.md) — equivalent dashboard scoped to a single audit
* [Insights](/ciso-assistant/product-docs/features/insights.md) — PRO/Enterprise cross-cutting views (impact graph, priority/effort matrix, timeline)
* [Applied controls](/ciso-assistant/product-docs/concepts/operations/applied-controls.md)


---

# 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://intuitem.gitbook.io/ciso-assistant/product-docs/features/applied-controls-analytics.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.