Compliance packs for regulated APIs: PCI-DSS and SOC 2 as code
Every regulated API I have onboarded followed the same pattern. The team
builds the API, wires up auth, ships to staging, and then someone from
security asks for the compliance checklist. The answers live in a thread.
The fixes come back as rework. The API ships late, or it ships with a
waiver nobody remembers signing.
The fix is not a better checklist. The fix is to stop treating compliance
as a review step and start treating it as config.
One line in the spec
In
api-onboarding-kit ,
a consumer declares its compliance baseline the same way it declares its
auth method. One line:
policies : - compliance:pci-dss
Enter fullscreen mode
Exit fullscreen mode
That line is a bundle, not a flag. It expands into the policies the
baseline actually requires. The PCI-DSS pack expands to JWT auth, a
standard rate limit, and an office IP allowlist. The SOC 2 pack expands
to JWT auth and the standard rate limit.…