Cross-Framework Mapping

Indiana Consumer Data Protection ActvsIEC 62351 - Power Systems Communication Security

See exactly how Indiana Consumer Data Protection Act controls map to IEC 62351 - Power Systems Communication Security. Pre-computed mappings, identified gaps, and coverage analysis.

2
Controls Mapped
6
Gaps Found
12%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

Indiana Consumer Data Protection Act maps to IEC 62351 - Power Systems Communication Security with 12% coverage across 1 directly mapped controls. Analysis of 8 Indiana Consumer Data Protection Act controls identifies 7 compliance gaps — primarily concentrated in Indiana CDPA Coord + Multi-Jurisdictional.

Source: TheArtOfService Knowledge Graph | 8 controls analysed | 718 frameworks | 332K+ cross-framework mappings

Control Mappings

Showing 2 of 2 mapped controls across 1 domains. Sign up to explore all 332K+ mappings across 718 frameworks.

Indiana CDPA Security + Breach + Records(2 mappings)

INCDPA-Security-ReasonablePractices-Breach-Notification-Records-Encryption-PseudonymisationIndiana CDPA Security + Reasonable Practices + Breach Notification + Indiana Breach Notification Law (IC 24-4.9) + Records + Encryption + Pseudonymisation + De-Identification2 targets
62351-8Role-based access control (RBAC)
62351-9Cyber security key management

Related Comparisons

Other Indiana Consumer Data Protection Act comparisons

Other IEC 62351 - Power Systems Communication Security comparisons

Stop Paying Consultants to Read Spreadsheets

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

$0/forever

Free

  • 718 framework browser
  • Cross-framework mappings (332K+)
  • 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 Indiana Consumer Data Protection Act and IEC 62351 - Power Systems Communication Security?

Indiana Consumer Data Protection Act has 8 controls across its framework, while IEC 62351 - Power Systems Communication Security covers 34 controls. Direct mapping analysis identifies 1 overlapping controls (12% coverage). The frameworks diverge most significantly in Indiana CDPA Coord + Multi-Jurisdictional, where 1 Indiana Consumer Data Protection Act controls have no direct IEC 62351 - Power Systems Communication Security equivalent.

How many controls map between Indiana Consumer Data Protection Act and IEC 62351 - Power Systems Communication Security?

Of 8 total Indiana Consumer Data Protection Act controls, 1 map directly to IEC 62351 - Power Systems Communication Security controls — representing 12% coverage. The remaining 7 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping Indiana Consumer Data Protection Act to IEC 62351 - Power Systems Communication Security?

7 Indiana Consumer Data Protection Act controls have no direct equivalent in IEC 62351 - Power Systems Communication Security. The highest concentration of gaps is in Indiana CDPA Coord + Multi-Jurisdictional with 1 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 Indiana Consumer Data Protection Act and IEC 62351 - Power Systems Communication Security?

The domain with the highest gap count is Indiana CDPA Coord + Multi-Jurisdictional (1 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.