CertRadar

Compliance evidence

SOC 2 — domain & certificate controls

US SaaS companies selling to enterprises — the most common compliance ask for B2B software.

Authority: AICPA (American Institute of Certified Public Accountants)

What SOC 2 actually requires

SOC 2 applies to any service organization handling customer data. Type I attests that controls are designed appropriately at a point in time; Type II attests that controls operated effectively over 3-12 months. The Trust Services Criteria cover Security (required), Availability, Processing Integrity, Confidentiality, and Privacy. Cryptographic identity — TLS certificates on systems that handle customer data — falls under the Security criterion.

Full name: SOC 2 (System and Organization Controls 2).

Controls that touch certificates and domains

These are the 4 controls most directly affected by TLS certificate and domain lifecycle. CertRadar produces evidence bundles mapped to each.

ControlTitleHow CertRadar helps
CC6.1Logical and Physical AccessEvidence that access to systems handling customer data is protected by TLS, with current certificate inventory.
CC6.6Boundary ProtectionDirect fit: boundary protection includes valid, unexpired TLS certificates on all public-facing endpoints.
CC6.7Transmission of DataEvidence that data in transit is encrypted using current, trusted certificates.
CC7.2Monitoring for AnomaliesOngoing monitoring of certificate expiry, issuer changes, and chain health with documented alert thresholds.

What the evidence pack contains

CertRadar’s one-click export for SOC 2 includes:

Example domains in SOC 2 scope

Representative domains often monitored for SOC 2 evidence. Check any of them live:

Ship the SOC 2 evidence your auditor asks for.

CertRadar gives security, IT, and compliance teams a complete inventory of every domain and cert your company owns — plus a one-click evidence pack mapped to SOC 2 controls. Beta in weeks. Early members get a lifetime Pro discount.

Join the waitlist

Other frameworks