Skip to main content
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: 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.
See Frameworks & controls for more on working with controls. To back controls with automated tests and write MCP evidence that cites code + test paths, see Address and evidence controls with tests.

​
Add formal evidence to a measure

Measures are the actions that mitigate your risks, and they hold formal evidence records.
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 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.
Integrations and automated evidence are typically managed by workspace admins.

​
Manage audits

Audits track your compliance audits and certifications against frameworks.
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.
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.
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.