Cross-Framework Mapping

OWASP Top 10 for LLM Applications 2025vsRussia Federal Law on Personal Data (152-FZ)

See exactly how OWASP Top 10 for LLM Applications 2025 controls map to Russia Federal Law on Personal Data (152-FZ). Pre-computed mappings, identified gaps, and coverage analysis.

4
Controls Mapped
4
Gaps Found
25%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

OWASP Top 10 for LLM Applications 2025 maps to Russia Federal Law on Personal Data (152-FZ) with 25% coverage across 2 directly mapped controls. Analysis of 8 OWASP Top 10 for LLM Applications 2025 controls identifies 6 compliance gaps — primarily concentrated in Monitoring and Testing.

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

Control Mappings

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

Prompt Security(1 mappings)

OWASPLLM-1Prompt Injection and System Prompt Leakage (LLM01 + LLM07)
RUSPD-2Lawful Basis, Consent, Notice

Sensitive Information and Privacy(3 mappings)

OWASPLLM-3Sensitive Information Disclosure and Privacy (LLM02)3 targets
RUSPD-1Scope, Definitions, Principles under 152-FZ
RUSPD-2Lawful Basis, Consent, Notice
RUSPD-4Special Categories, Biometric Data

Related Comparisons

Other OWASP Top 10 for LLM Applications 2025 comparisons

Other Russia Federal Law on Personal Data (152-FZ) 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 OWASP Top 10 for LLM Applications 2025 and Russia Federal Law on Personal Data (152-FZ)?

OWASP Top 10 for LLM Applications 2025 has 8 controls across its framework, while Russia Federal Law on Personal Data (152-FZ) covers 8 controls. Direct mapping analysis identifies 2 overlapping controls (25% coverage). The frameworks diverge most significantly in Monitoring and Testing, where 1 OWASP Top 10 for LLM Applications 2025 controls have no direct Russia Federal Law on Personal Data (152-FZ) equivalent.

How many controls map between OWASP Top 10 for LLM Applications 2025 and Russia Federal Law on Personal Data (152-FZ)?

Of 8 total OWASP Top 10 for LLM Applications 2025 controls, 2 map directly to Russia Federal Law on Personal Data (152-FZ) controls — representing 25% coverage. The remaining 6 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping OWASP Top 10 for LLM Applications 2025 to Russia Federal Law on Personal Data (152-FZ)?

6 OWASP Top 10 for LLM Applications 2025 controls have no direct equivalent in Russia Federal Law on Personal Data (152-FZ). The highest concentration of gaps is in Monitoring and Testing 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 OWASP Top 10 for LLM Applications 2025 and Russia Federal Law on Personal Data (152-FZ)?

The domain with the highest gap count is Monitoring and Testing (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.