
SOC 2, built in rather than bolted on.
You should be building to compliance rather than fixing to it. Having it run inside the workflow while you build is, to me, immeasurable.

SOC 2 compliance means putting the relevant controls into practice. Prepare for a SOC 2 Type 2 report with requirements for your agents, checks before merge and evidence ready for your auditor.

Enterprise buyers ask for evidence of your security controls. Security questionnaires bring those questions into the buying process. A SOC 2 report helps you show how your controls are designed and how they operate.
Used when buyers want to see that your controls are designed appropriately on a given date. Issued by an independent CPA firm.
Used when buyers want evidence that controls operated over a defined period. Issued by an independent CPA firm.
Ask your buyer which report they need.
SOC 2 is an AICPA attestation report on your controls against the Trust Services Criteria. It is a report, not a certification.
SOC 2 is not a certification. It is an attestation report issued by an independent CPA firm using the AICPA Trust Services Criteria. A SOC 2 Type 2 report examines how controls operated over a defined period, rather than certifying the company.
Code volume grows and changes move fast. Evidence can fall behind the work. Your security and compliance requirements need to be part of the engineering workflow, rather than reconstructed afterwards.
| Topic | SOC 2 | ISO 27001 | ISO 42001 |
|---|---|---|---|
| What it is | Attestation report | Certification of an information security management system | Certification of an AI management system |
| Who issues it | Independent CPA firm | Accredited certification body | Accredited certification body |
| What it covers | Controls against the Trust Services Criteria in your scope | Your ISMS and Annex A controls, within the certified scope | Your AI management system, including AI risk, impact assessment and the AI system life cycle |
| Validity | The report covers a period; buyers usually expect a recent report | 3-year certificate with annual surveillance audits | 3-year certificate with annual surveillance audits |
| Common buyers | US-led buyers often ask for SOC 2 | UK and EU buyers often ask for ISO 27001 | Buyers with AI-specific governance questions |
Keldyn MCP gives coding agents your SOC 2 requirements before they build.
Secure design →The compliance gate checks every change against your requirements before it merges.
Compliance gate →Policies drafted from proven templates and the facts you confirm.
Documents →Evidence from your tools and your checks, ready for your auditor. Your Trust Centre shares your security work with buyers.
Evidence and audit →Qualified auditors and security specialists are your customer success team. Keldyn prepares you for audit and introduces auditors.
Explore Trust Centre →SOC 2 controls built into Kyance’s agentic commerce platform.

You should be building to compliance rather than fixing to it. Having it run inside the workflow while you build is, to me, immeasurable.

It means implementing and operating controls relevant to the Trust Services Criteria in your scope. An independent CPA firm assesses those controls and issues a report.
A SOC 2 Type 2 report covers how controls operate over a defined period. Type 1 covers their design at a point in time. Ask your buyer which report they need.
No. An independent CPA firm issues the report. Keldyn prepares you and introduces auditors.
Yes. Controls overlap, and Keldyn covers both SOC 2 and ISO 27001.
“You should be building to compliance rather than fixing to it.”
Tim Brown



