Skip to main content
Evidence is how you show a control is actually in place. Audits are how you track a certification against a framework. Both hang off the same controls, so a status change and the file that supports it stay next to each other.

​
Ways to capture evidence

Three ways to record it: Knowledge connectors (Google Drive, Confluence, Notion, Otter) feed Knowledgebase search. They do not produce automated control evidence.

​
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.
Working the control itself is on Frameworks & controls. Backing a code-relevant control with a test, and writing MCP evidence that cites the code and the test path, is on Address and evidence controls with tests.

​
Add formal evidence to a measure

A measure is the action you take against a risk. Formal evidence records (a file or a link, with a description) live on the measure, not only as a note on the control.
1

Open a measure

Go to Measures in the sidebar and select a measure to open its detail page.
2

Go to the Evidences tab

Select the Evidences tab, then Add evidence.
3

Upload a file or add a link

Choose Upload or Link, provide the file or URL and an optional description, then select Add evidence.

​
Automated evidence from integrations

Connect a tool under Integrations and Keldyn pulls evidence on a schedule. On that integration’s 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.
Integrations and automated evidence are typically managed by workspace admins.

​
Manage audits

An audit record is one engagement or certification against a framework: dates, state, the controls in scope, and the report PDF.
1

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.
2

Link controls in scope

Open the audit and use Link control to attach the controls covered by the audit.
3

Upload the report

In the Audit report section, select Upload report to attach the final PDF produced for the audit.
States: Not started, In progress, Completed, Rejected, Outdated. Trust Center visibility is None, Private, or Public. Public is what visitors of your Trust Center can see.
Audits are part of the GRC section and are usually managed by admins.

​
Next steps

Connect your AI tools

Use the Keldyn MCP server so assistants can query controls and track evidence on your behalf.

Address & evidence controls

Implement controls with unit tests and update evidence via MCP to cite code + test paths.