NIST Cybersecurity Framework 2.0vsSecurity of Critical Infrastructure Act 2018 (SOCI)
See exactly how NIST Cybersecurity Framework 2.0 controls map to Security of Critical Infrastructure Act 2018 (SOCI). Pre-computed mappings, identified gaps, and coverage analysis.
Need this as a report you can hand to an assessor? A coverage crosswalk for this pair can be built to order.
According to the TheArtOfService Compliance Knowledge Graph:
NIST Cybersecurity Framework 2.0 maps to Security of Critical Infrastructure Act 2018 (SOCI) with 14% coverage across 15 directly mapped controls. Analysis of 106 NIST Cybersecurity Framework 2.0 controls identifies 91 compliance gaps, primarily concentrated in GV - Govern.
Source: TheArtOfService Knowledge Graph | 106 controls analysed | 686 frameworks | 309K+ cross-framework mappings
Control Mappings
Showing 20 of 31 mapped controls across 5 domains. Sign up to explore all 309K+ mappings across 686 frameworks.
GV - Govern(11 mappings)
ID - Identify(6 mappings)
PR - Protect(3 mappings)
+11 more mappings
Plus AI-powered gap analysis, compliance advisory, PDF exports, and cross-mapping for all 686 frameworks.
Create Free Account →Free forever, no credit card required
A NIST Cybersecurity Framework 2.0 to Security of Critical Infrastructure Act 2018 (SOCI) crosswalk, built to order
The table above lists candidate mappings. A crosswalk answers the narrower question you are probably here for: which Security of Critical Infrastructure Act 2018 (SOCI) controls your existing NIST Cybersecurity Framework 2.0 work already satisfies, which are real gaps, and the reasoning behind every claim so you can check it. One pair, $299, one time.
This direction has not been through crosswalk review and sign off, so no coverage figure is published for it. Reporting an unreviewed number would be worse than reporting none. It can be built to order at the same price as a pair that is already on the shelf.
If the two frameworks turn out to have too little in common for a crosswalk to help you, we say so and refund it rather than send a number worth nothing.
This direction has not been through crosswalk review and sign off, so no coverage figure is published for it. Reporting an unreviewed number would be worse than reporting none. It can be built to order at the same price as a pair that is already on the shelf.
If the two frameworks turn out to have too little in common for a crosswalk to help you, we say so and refund it rather than send a number worth nothing.
- Every evidenced control, with the reasoning behind it
- Every gap, with what it requires
- Its level of review stated plainly, not a bare number
Why this page shows two different percentages. The 14% in the header counts how many NIST Cybersecurity Framework 2.0 controls carry at least one candidate mapping in the graph, before any review. The crosswalk percentage counts something stricter: how many Security of Critical Infrastructure Act 2018 (SOCI) controls are actually evidenced, after a pass that argued against each mapping and kept only what survived. They answer different questions and they are not meant to agree.
A crosswalk narrows the work. It does not replace an audit, and your assessor may take a different view on individual controls. Mappings between frameworks are judgements, not text printed in either standard, which is why every claim in the report shows its reasoning. Questions go to support@theartofservice.com.
Related Comparisons
Other NIST Cybersecurity Framework 2.0 comparisons
Other Security of Critical Infrastructure Act 2018 (SOCI) comparisons
Stop Paying Consultants to Read Spreadsheets
AI-powered compliance intelligence across 686 frameworks, at a fraction of consulting costs.
Free
- ✓ 686 framework browser
- ✓ Cross-framework mappings (309K+)
- ✓ 824 compliance assessments
- ✓ 3 AI queries & searches per day
Professional
- ✓ Unlimited AI Compliance Advisory
- ✓ Unlimited full-text search
- ✓ Framework self-assessment
- ✓ PDF, Excel & CSV exports
What are the key differences between NIST Cybersecurity Framework 2.0 and Security of Critical Infrastructure Act 2018 (SOCI)?
NIST Cybersecurity Framework 2.0 has 106 controls across its framework, while Security of Critical Infrastructure Act 2018 (SOCI) covers 35 controls. Direct mapping analysis identifies 15 overlapping controls (14% coverage). The frameworks diverge most significantly in GV - Govern, where 24 NIST Cybersecurity Framework 2.0 controls have no direct Security of Critical Infrastructure Act 2018 (SOCI) equivalent.
How many controls map between NIST Cybersecurity Framework 2.0 and Security of Critical Infrastructure Act 2018 (SOCI)?
Of 106 total NIST Cybersecurity Framework 2.0 controls, 15 map directly to Security of Critical Infrastructure Act 2018 (SOCI) controls, representing 14% coverage. The remaining 91 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.
What are the compliance gaps when mapping NIST Cybersecurity Framework 2.0 to Security of Critical Infrastructure Act 2018 (SOCI)?
91 NIST Cybersecurity Framework 2.0 controls have no direct equivalent in Security of Critical Infrastructure Act 2018 (SOCI). The highest concentration of gaps is in GV - Govern with 24 unmapped controls. These gaps represent areas where additional controls, policies, or documentation must be created to achieve compliance with both frameworks.
Which control domains have the most gaps between NIST Cybersecurity Framework 2.0 and Security of Critical Infrastructure Act 2018 (SOCI)?
The domain with the highest gap count is GV - Govern (24 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.
Related Resources
This platform provides educational compliance tools, not legal, regulatory, or professional compliance advice. Cross-framework mappings are AI-assisted interpretations and do not reproduce or replace official standards. Framework names and trademarks belong to their respective owners. Consult qualified professionals for your specific compliance requirements. See our Terms of Service.