Crosswalk pair
ESG Essentials and SOX (Sarbanes-Oxley) Section 404, control by control
7 canonical controls in Keel’s library satisfy clauses of both ESG Essentials and SOX (Sarbanes-Oxley) Section 404. 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.
7
Controls that satisfy both
Canonical controls that crosswalk to at least one clause of each.
36
In Keel’s library for ESG Essentials
19% of them also map to SOX (Sarbanes-Oxley) Section 404.
29
In Keel’s library for SOX (Sarbanes-Oxley) Section 404
24% of them also map to ESG Essentials.
21
Evidence artifacts expected
Across the shared controls, from Keel’s evidence guidance. Gathered once.
-
ESG Essentials 19%
7 controls of 36 in Keel’s library for ESG Essentials also map to SOX (Sarbanes-Oxley) Section 404.
-
SOX (Sarbanes-Oxley) Section 404 24%
7 controls of 29 in Keel’s library for SOX (Sarbanes-Oxley) Section 404 also map to ESG Essentials.
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 | ESG Essentials clauses | SOX (Sarbanes-Oxley) Section 404 clauses |
|---|---|---|
| Governance & Risk | ||
| Anti-corruption & bribery Bribery and facilitation payments are prohibited, with training for relevant staff. | G.3 | P1 |
| Code of business conduct A code of conduct - including conflicts of interest - acknowledged by staff. | G.2, G.4 | P1 |
| Information security policy A board-approved policy set covering information security and the handling of personal data, sized to the scale of the organization and the type of activities it actually carries out, reviewed at least annually and communicated to the workforce. The policy set states the direction the organization is taking on information security - what it commits to, and what it requires of everyone doing work for it - so it sets where the programme is going rather than only recording what it already does. One or more named individuals are designated to coordinate the programme the policies describe - the person in charge of it, named rather than implied, with the designation recorded in writing, made known to the people who need it and kept current as roles change - so there is someone who answers for the policies being carried out and not only for their being published. How far the policies go, and how far the measures they require go, is judged against four things together: the organization’s size, complexity and capabilities; its technical infrastructure and the security capabilities of its hardware and software; what the measures cost; and how likely the risks they address are and how much damage they would do. A policy may be changed at any time, provided the change is documented and is actually put into effect rather than only written down. | G.9 | P12 |
| Management review Leadership reviews how the management system is performing at planned intervals and decides what to do about it: what will be improved, and what about the system itself has to change. Each decision leaves the review with a named owner and a date rather than as a sentiment in the minutes, the previous review’s decisions are picked back up at the next one so nothing is decided twice and never done, and the record of the review and its outputs is retained. | G.14 | P16 |
| Whistleblower channel A confidential, non-retaliatory channel to report misconduct. | G.5 | P14 |
| Third-party Risk | ||
| Third-party / vendor risk management Due diligence, contractual safeguards, and ongoing monitoring of vendors that handle your data: the agreement obliges the vendor to comply in its own right with the security requirements that apply to it - an absolute standard, not a promise to match whatever you happen to do - to pass those obligations down to any subcontractor it brings in BY ENTERING INTO a contract or equivalent written arrangement with that subcontractor rather than by merely requiring equivalent practice of it, and to report to you, within a stated time, security incidents it becomes aware of and confirmed breaches of your data. Where a contract is not the instrument available, an equivalent written arrangement carrying the same obligations discharges the duty. The same obligations, together with the separation that keeps a related organization out of data it is not entitled to, are written into the governing document of any other arrangement that puts your data in the hands of a sponsor, parent, affiliate or plan. Diligence is not confined to security where the relationship warrants more: for suppliers significant enough to matter, the organization states the standards of conduct it expects of them - how they behave commercially and how they treat the environment around their operations - and screens candidates and incumbents against those stated expectations as part of the same selection and monitoring cycle, rather than accepting a signature on a code as evidence of it. | G.7, E.7 | P11, P15 |
| People & Culture | ||
| Security awareness training Ongoing security and data-handling awareness training for all personnel, with completion tracking, and periodic security updates - reminders, bulletins and alerts - issued to the workforce between training cycles. New joiners are trained within a defined period of starting, anyone whose work is affected is retrained within a defined period after a material change to the policies or procedures, and every completion is recorded. | S.5 | P4, P14 |
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 these 7 controls
- AI Governance Essentials
- Amazon Appstore Child-Directed Apps
- Apple App Store Kids Category
- CIS Critical Security Controls
- COPPA
- 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
- US Employment Law - Federal Baseline
Nearby pairs
- SOX (Sarbanes-Oxley) Section 404 and ISO/IEC 27001 24 shared controls
- SOX (Sarbanes-Oxley) Section 404 and SOC 2 23 shared controls
- SOX (Sarbanes-Oxley) Section 404 and NIST SP 800-53 20 shared controls
- SOX (Sarbanes-Oxley) Section 404 and HIPAA 16 shared controls
- SOX (Sarbanes-Oxley) Section 404 and PCI DSS 16 shared controls
- SOX (Sarbanes-Oxley) Section 404 and NIST Cybersecurity Framework 15 shared controls
The thesis
Why this is one project, not two
On a crosswalk-native model, SOX (Sarbanes-Oxley) Section 404 mostly lights up controls you already built for ESG Essentials. 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 SOX (Sarbanes-Oxley) Section 404 to the work you already did
Apply both frameworks in one workspace and see the overlap measured against the controls you already hold.