Crosswalk pair
CIS Critical Security Controls and US Employment Law - Federal Baseline, control by control
1 canonical control in Keel’s library satisfies clauses of both CIS Critical Security Controls 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.
The overlap
What the two libraries have in common
Every figure here counts canonical controls in Keel’s library, not clauses of either standard. Each standard’s own authored count is on its framework page.
1
Controls that satisfy both
Canonical controls that crosswalk to at least one clause of each.
18
In Keel’s library for CIS Critical Security Controls
6% of them also map to US Employment Law - Federal Baseline.
11
In Keel’s library for US Employment Law - Federal Baseline
9% of them also map to CIS Critical Security Controls.
3
Evidence artifacts expected
Across the shared controls, from Keel’s evidence guidance. Gathered once.
-
CIS Critical Security Controls 6%
1 control of 18 in Keel’s library for CIS Critical Security Controls also maps to US Employment Law - Federal Baseline.
-
US Employment Law - Federal Baseline 9%
1 control of 11 in Keel’s library for US Employment Law - Federal Baseline also maps to CIS Critical Security Controls.
The mapping
Controls that satisfy both
Each row is one control in Keel’s library and the clauses it answers on each side. Do the work once; both columns are then evidenced by the same artifacts.
| Canonical control | CIS Critical Security Controls clauses | US Employment Law - Federal Baseline clauses |
|---|---|---|
| Data retention & secure disposal Data is retained per policy and securely destroyed when no longer needed. The hardware and media that held it reach a defined final disposition at end of life, by a route the organization has decided in advance rather than by whatever happens to the box; and any media that stays in service is cleared of that data before it is reused, reassigned, or passed to anyone else. | 3.5 | us.recordkeeping.eeo, us.recordkeeping.i9-retention |
Beyond the pair
Where else this work counts
A framework is lit when a shared control above also maps to it. Unlit means none of them do — an absence, not a judgment about that standard.
Also reached by this control
- AI Governance Essentials
- Amazon Appstore Child-Directed Apps
- Apple App Store Kids Category
- COPPA
- ESG Essentials
- EU AI Act
- GDPR
- Google Play Families
- HIPAA
- ISO 9001
- ISO/IEC 27001
- ISO/IEC 42001
- NIST AI Risk Management Framework
- NIST Cybersecurity Framework
- NIST SP 800-171
- NIST SP 800-53
- PCI DSS
- SOC 2
- SOX (Sarbanes-Oxley) Section 404
Nearby pairs
- CIS Critical Security Controls and ISO/IEC 27001 17 shared controls
- CIS Critical Security Controls and NIST SP 800-53 17 shared controls
- CIS Critical Security Controls and PCI DSS 16 shared controls
- CIS Critical Security Controls and SOC 2 15 shared controls
- CIS Critical Security Controls and HIPAA 14 shared controls
- CIS Critical Security Controls and NIST Cybersecurity Framework 13 shared controls
The thesis
Why this is one project, not two
On a crosswalk-native model, US Employment Law - Federal Baseline mostly lights up controls you already built for CIS Critical Security Controls. 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.
Next step
Add US Employment Law - Federal Baseline to the work you already did
Apply both frameworks in one workspace and see the overlap measured against the controls you already hold.