Skip to content

v1.80.0 ·

The pack nobody asked for by name

People ask for "SSAE 16 guidance, like SOC 2". SSAE 16 is the retired AICPA standard behind SOC 1 reports. It replaced SAS 70 in 2011 and was replaced by SSAE 18 in May 2017. SOC 1 has no fixed criteria: each company writes its own control objectives. What auditors test in practice are IT general controls, and some of those overlap the SOC 2 pack's controls. Nothing in the product said so, and a search for "SSAE 16" or "SOC 1" found nothing.

What changed

I did not build a SOC 1 pack. A SOC 2 report is tested against fixed criteria, so a pack can check them. SOC 1 objectives differ from company to company, and a pack would have to guess them. So there is a short section in packages/content/docs/hygiene-and-compliance.md instead, "SSAE 16, SSAE 18, SOC 1 and SOC 2". It says what the old names mean, who writes SOC 1 control objectives, and plainly that no SOC 1 pack exists or is planned. It maps four areas a SOC 1 auditor usually tests to the SOC 2 checks that leave related evidence.

Each of the four says what the checks do not cover. Who may grant or remove user access is the example. That gap is most of what a SOC 1 auditor tests about access, so leaving it out would have overstated the trail.

To make it findable, packs gain an optional asked_for_as field. The SOC 2 pack sets it to SOC 1 and SSAE 16. The init picker has no search, so those names appear in the SOC 2 option's hint, and aidlc compliance list prints them in text and in --json. The field is bounded at 40 characters and may not contain {{.

Why this way

Each choice was picked so the product says less, not more.

The note is kept honest by a test, not by care. It marks every check as one that leaves evidence or one that is only applied. A test reads the note, compares each mark with what the pack declares, and fails if one drifts. The guard that rejects phrases like "SOC 2 compliant" now also catches SOC 1 and SSAE claims. It reads the docs page sentence by sentence, because a claim can wrap across two lines.

The pack version stays at 0.2.0. The installed layer file is unchanged, so no project is offered an upgrade with nothing in it. A pack without the new field shows nothing extra.

What it does not do

It does not make anyone ready for a SOC 1 audit. It is a mapping, with its gaps written down, for a team that was asked for the old name. This is a minor release, because a pack field is new and two commands print it. Nothing was removed.