PCI DSS ↔ US Employment Law - Federal Baseline
2 canonical controls in Keel's library satisfy clauses ofboth PCI DSS and US Employment Law - Federal Baseline. Implement each once, attach the evidence once, and it counts toward each standard. The overlap is the work you don't repeat.
Controls that satisfy both
| Canonical control | PCI DSS clauses | US Employment Law - Federal Baseline clauses |
|---|---|---|
| Data retention & secure disposal Data is retained per policy and securely destroyed when no longer needed. | 3.2 | us.wage-hour.recordkeeping, us.recordkeeping.eeo, us.recordkeeping.i9-retention |
| Personnel security (HR) Background screening, confidentiality agreements, and onboarding/offboarding security steps. | 12.7 | us.hiring-onboarding.i9, us.hiring-onboarding.fcra-background, us.privacy.polygraph |
Clause identifiers (PCI DSS and US Employment Law - Federal Baseline) are referenced factually for mapping. Keel is not affiliated with or endorsed by the bodies that publish these standards. Control descriptions are Keel's own; a framework's full authored control count is on itsframework page.
Why this is one project, not two
On a crosswalk-native model, US Employment Law - Federal Baseline mostly lights up controls you already built forPCI DSS. You're not re-uploading the same screenshot for a second audit. You apply the framework and see the genuine delta worth working. That's the whole idea behind collect once, comply everywhere.