Blog

Preparing for SOC 2 Type II Without Putting a Fake Badge on the Site

What “preparing for SOC 2” should mean for a DX platform: controls, evidence, honesty — and why fake certification seals destroy trust with platform teams.

2026-10-01 · 8 min read · AethelLayer

Platform teams can smell theater

SDK buyers who already run Datadog and Okta will open your security page looking for two things: what is live today, and what is a promise. A PNG of a SOC 2 seal you have not earned is an insult. They will not install your probe.

AethelLayer says it plainly: we are preparing for SOC 2 Type II. That is access reviews, change evidence, vendor inventory, incident process. It is not certification. The Disclaimer exists for a reason.

What we will show instead of a sticker

Hashed identity. Org RLS. Keyed ingest. Human-approved tickets. Optional AI that stays off unless you bring a key. Subprocessors named. A mailbox for coordinated disclosure.

Enterprise SSO, SCIM, audit export, and VPC are scoped on a call. Listing them as self-serve checkmarks on Starter would be another kind of lie.

How to read any vendor’s 'coming soon' SOC 2

Ask for the date of the last access review, the list of subprocessors, and whether production tickets can auto-file. If they cannot answer without a slide, they are not preparing. They are marketing.

Capture the failure before they leave

Capture the failure before they leave. Book early access or talk to sales, then install @aethellayer/sdk when you are onboarded.