> For the complete documentation index, see [llms.txt](https://docs.docontrol.io/docontrol-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docontrol.io/docontrol-user-guide/risk-management/misconfigurations-premium/security-checks/security-check-activity.md).

# Security check activity

For each security check, you can inspect its audit log to investigate scan results and any manual overrides.

Detailed audit trails of checks and manual overrides serve as evidence for frameworks like SOC 2, ISO 27001, or internal controls, demonstrating that misconfigurations are monitored and handled through DoControl's controlled process.

The Activity tab displays a history of all user and system activities for each security check in chronological order, enabling you to:

* **Audit decisions, investigate changes**, and understand the lifecycle of each security check
* **Get clear accountability** of what was changed and when, based on time‑stamped logs of misconfiguration detections 
* **Enforce** internal policies around exceptions for misconfigurations

<div align="left"><figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FXn3Mx92MjAOHzPkfJlqJ%2FMisconfig%20activity%20tab.png?alt=media&amp;token=39d89392-5a31-403d-9251-2b908fe40321" alt=""><figcaption></figcaption></figure></div>

{% hint style="info" %}
The Activity tab displays the **changes** in a security check's status (for example, fail to pass). It does not show the result for each daily scan if it has the same status as the previous scan.&#x20;
{% endhint %}


---

# 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.docontrol.io/docontrol-user-guide/risk-management/misconfigurations-premium/security-checks/security-check-activity.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.