Angola Personal Data Protection Law (Law No. 22/11)vsEU NIS2 Directive — Transport Sector Requirements
See exactly how Angola Personal Data Protection Law (Law No. 22/11) controls map to EU NIS2 Directive — Transport Sector Requirements. Pre-computed mappings, identified gaps, and coverage analysis.
According to the TheArtOfService Compliance Knowledge Graph:
Angola Personal Data Protection Law (Law No. 22/11) maps to EU NIS2 Directive — Transport Sector Requirements with 42% coverage across 13 directly mapped controls. Analysis of 31 Angola Personal Data Protection Law (Law No. 22/11) controls identifies 18 compliance gaps — primarily concentrated in Chapter I: General Provisions.
Source: TheArtOfService Knowledge Graph | 31 controls analysed | 693 frameworks | 819K+ cross-framework mappings
Control Mappings
Showing 20 of 32 mapped controls across 6 domains. Sign up to explore all 819K+ mappings across 693 frameworks.
Chapter I: General Provisions(8 mappings)
Chapter IV: Controller and Processor Obligations(7 mappings)
Chapter V: International Data Transfers(1 mappings)
Chapter VI: Data Protection Agency (APD)(2 mappings)
Chapter VII: Sanctions and Penalties(2 mappings)
+12 more mappings
Plus AI-powered gap analysis, compliance advisory, PDF exports, and cross-mapping for all 693 frameworks.
Create Free Account →Free forever — no credit card required
Related Comparisons
Other Angola Personal Data Protection Law (Law No. 22/11) comparisons
Other EU NIS2 Directive — Transport Sector Requirements comparisons
Stop Paying Consultants to Read Spreadsheets
AI-powered compliance intelligence across 693 frameworks — at a fraction of consulting costs.
Free
- ✓ 693 framework browser
- ✓ Cross-framework mappings (819K+)
- ✓ 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 Angola Personal Data Protection Law (Law No. 22/11) and EU NIS2 Directive — Transport Sector Requirements?
Angola Personal Data Protection Law (Law No. 22/11) has 31 controls across its framework, while EU NIS2 Directive — Transport Sector Requirements covers 36 controls. Direct mapping analysis identifies 13 overlapping controls (42% coverage). The frameworks diverge most significantly in Chapter I: General Provisions, where 6 Angola Personal Data Protection Law (Law No. 22/11) controls have no direct EU NIS2 Directive — Transport Sector Requirements equivalent.
How many controls map between Angola Personal Data Protection Law (Law No. 22/11) and EU NIS2 Directive — Transport Sector Requirements?
Of 31 total Angola Personal Data Protection Law (Law No. 22/11) controls, 13 map directly to EU NIS2 Directive — Transport Sector Requirements controls — representing 42% coverage. The remaining 18 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.
What are the compliance gaps when mapping Angola Personal Data Protection Law (Law No. 22/11) to EU NIS2 Directive — Transport Sector Requirements?
18 Angola Personal Data Protection Law (Law No. 22/11) controls have no direct equivalent in EU NIS2 Directive — Transport Sector Requirements. The highest concentration of gaps is in Chapter I: General Provisions with 6 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 Angola Personal Data Protection Law (Law No. 22/11) and EU NIS2 Directive — Transport Sector Requirements?
The domain with the highest gap count is Chapter I: General Provisions (6 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.