Cross-Framework Mapping

Canada ITSG-33 — IT Security Risk ManagementvsISO/IEC 29134:2023

See exactly how Canada ITSG-33 — IT Security Risk Management controls map to ISO/IEC 29134:2023. Pre-computed mappings, identified gaps, and coverage analysis.

18
Controls Mapped
6
Gaps Found
33%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

Canada ITSG-33 — IT Security Risk Management maps to ISO/IEC 29134:2023 with 33% coverage across 8 directly mapped controls. Analysis of 24 Canada ITSG-33 — IT Security Risk Management controls identifies 16 compliance gaps — primarily concentrated in Security Controls.

Source: TheArtOfService Knowledge Graph | 24 controls analysed | 693 frameworks | 819K+ cross-framework mappings

Control Mappings

Showing 18 of 18 mapped controls across 2 domains. Sign up to explore all 819K+ mappings across 693 frameworks.

Risk Management Lifecycle(1 mappings)

CA-ITSG33-RM-03Continuous Monitoring
29134-9.2Report findings and recommendations

Security Controls(17 mappings)

KR-CSAP-SC-01Information Security Management3 targets
29134-1Scope
29134-3Terms and definitions
29134-9.1PIA report structure
MARSE-SC-01NIST 800-53 Moderate Baseline3 targets
29134-1Scope
29134-3Terms and definitions
29134-9.1PIA report structure
NRC73-CTL-01Access Control for CDAs3 targets
27014-1Scope
27014-3Terms and definitions
29134-3Terms and definitions
NZ-NZISM-SC-01Governance and Risk Management3 targets
29134-1Scope
29134-3Terms and definitions
29134-9.1PIA report structure
NZ-NZISM-SC-02ICT Security Controls
29134-9.2Report findings and recommendations
NZ-NZISM-SC-03Cryptography and Cloud3 targets
29134-1Scope
29134-3Terms and definitions
29134-9.1PIA report structure
PAS1192-5-SC-03Breach Management
29134-9.2Report findings and recommendations

Stop Paying Consultants to Read Spreadsheets

AI-powered compliance intelligence across 693 frameworks — at a fraction of consulting costs.

$0/forever

Free

  • 693 framework browser
  • Cross-framework mappings (819K+)
  • 824 compliance assessments
  • 3 AI queries & searches per day
Get Started Free
Recommended
$49/month

Professional

  • Unlimited AI Compliance Advisory
  • Unlimited full-text search
  • Framework self-assessment
  • PDF, Excel & CSV exports
Start 7-Day Free Trial →

What are the key differences between Canada ITSG-33 — IT Security Risk Management and ISO/IEC 29134:2023?

Canada ITSG-33 — IT Security Risk Management has 24 controls across its framework, while ISO/IEC 29134:2023 covers 23 controls. Direct mapping analysis identifies 8 overlapping controls (33% coverage). The frameworks diverge most significantly in Security Controls, where 14 Canada ITSG-33 — IT Security Risk Management controls have no direct ISO/IEC 29134:2023 equivalent.

How many controls map between Canada ITSG-33 — IT Security Risk Management and ISO/IEC 29134:2023?

Of 24 total Canada ITSG-33 — IT Security Risk Management controls, 8 map directly to ISO/IEC 29134:2023 controls — representing 33% coverage. The remaining 16 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping Canada ITSG-33 — IT Security Risk Management to ISO/IEC 29134:2023?

16 Canada ITSG-33 — IT Security Risk Management controls have no direct equivalent in ISO/IEC 29134:2023. The highest concentration of gaps is in Security Controls with 14 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 Canada ITSG-33 — IT Security Risk Management and ISO/IEC 29134:2023?

The domain with the highest gap count is Security Controls (14 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.

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.