> ## Documentation Index
> Fetch the complete documentation index at: https://docs.keldyn.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Evidence & audits

> Attach evidence to controls and measures, use automated integration evidence, and manage audits and certifications in Keldyn.

Evidence proves that your controls are actually in place, and audits track your certifications against frameworks. Keldyn keeps both close to your controls so your compliance posture stays current.

## Ways to capture evidence

Keldyn supports three complementary kinds of evidence:

| Type                            | Where                                                                 | Best for                                                        |
| ------------------------------- | --------------------------------------------------------------------- | --------------------------------------------------------------- |
| **Control notes & attachments** | On a control in Org Controls or a use case's Compliance/Security tabs | Quick notes, files, or links tied directly to a control.        |
| **Measure evidence**            | The **Measures** area (GRC)                                           | Formal evidence records (files or links) attached to a measure. |
| **Automated evidence**          | **Integrations**                                                      | Evidence collected continuously from connected tools.           |

## Add evidence to a control

Expand a control on the **Org Controls** page or a use case's **Compliance**/**Security** tab. In the control's **Evidence** area you can:

* Write notes describing how the control is satisfied.
* **Upload file** to attach a document.
* **Add link** to reference an external location.

See [Frameworks & controls](/frameworks-and-controls) for more on working with controls.

## Add formal evidence to a measure

Measures are the actions that mitigate your risks, and they hold formal evidence records.

<Steps>
  <Step title="Open a measure">
    Go to **Measures** in the sidebar and select a measure to open its detail page.
  </Step>

  <Step title="Go to the Evidences tab">
    Select the **Evidences** tab, then **Add evidence**.
  </Step>

  <Step title="Upload a file or add a link">
    Choose **Upload** or **Link**, provide the file or URL and an optional description, then select **Add evidence**.
  </Step>
</Steps>

## Automated evidence from integrations

Connect external tools under **Integrations** so Keldyn collects evidence for you. On an integration's detail page:

* **Evidence sources** shows what data is fetched, which controls it covers, and how fresh it is.
* **Controls covered** shows the live evidence status per control, merged across all connected providers.

<Note>
  Integrations and automated evidence are typically managed by workspace admins.
</Note>

## Manage audits

Audits track your compliance audits and certifications against frameworks.

<Steps>
  <Step title="Create an audit">
    Go to **Audits** in the GRC section and select **New Audit**. Give it a name, framework, state, validity dates, and Trust Center visibility.
  </Step>

  <Step title="Link controls in scope">
    Open the audit and use **Link control** to attach the controls covered by the audit.
  </Step>

  <Step title="Upload the report">
    In the **Audit report** section, select **Upload report** to attach the final PDF produced for the audit.
  </Step>
</Steps>

An audit moves through states as it progresses: **Not started**, **In progress**, **Completed**, **Rejected**, or **Outdated**. You can set an audit's Trust Center visibility to **None**, **Private**, or **Public** to control whether it appears in your public Trust Center.

<Tip>
  Audits are part of the GRC section and are usually managed by admins.
</Tip>

## Next steps

<Card title="Connect your AI tools" icon="plug" href="/keldyn-mcp-server" arrow={true}>
  Use the Keldyn MCP server so assistants can query controls and track evidence on your behalf.
</Card>