Cross-Framework Mapping

NIST SP 800-145vsBSI IT-Grundschutz

See exactly how NIST SP 800-145 controls map to BSI IT-Grundschutz. Pre-computed mappings, identified gaps, and coverage analysis.

22
Controls Mapped
0
Gaps Found
25%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

NIST SP 800-145 maps to BSI IT-Grundschutz with 25% coverage across 2 directly mapped controls. Analysis of 8 NIST SP 800-145 controls identifies 6 compliance gaps — primarily concentrated in Deployment Models.

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

Control Mappings

Showing 20 of 22 mapped controls across 2 domains. Sign up to explore all 324K+ mappings across 706 frameworks.

Procurement and Service Catalogue Alignment(7 mappings)

NISTSP145-7Cloud Procurement Standards Aligned to NIST SP 800-145 Definition7 targets
BSI-13Risk assessment procedures
BSI-14Vulnerability scanning and management
BSI-15Security categorization
BSI-17Continuous monitoring strategy
BSI-23Baseline configuration establishment
BSI-24Configuration change control
BSI-26System component inventory

Governance, Reporting, Education(13 mappings)

NISTSP145-8Governance, Reporting, and Stakeholder Education on Cloud Definition13 targets
BSI-01Account management and provisioning
BSI-02Access enforcement and least privilege
BSI-03Multi-factor authentication requirements
BSI-08Cryptographic protection of data
BSI-15Security categorization
BSI-17Continuous monitoring strategy
BSI-18Incident response planning and testing
BSI-20Incident reporting and notification
BSI-21Forensic analysis capabilities
BSI-23Baseline configuration establishment
BSI-24Configuration change control
BSI-26System component inventory
BSI-28Audit event logging and storage

+2 more mappings

Plus AI-powered gap analysis, compliance advisory, PDF exports, and cross-mapping for all 706 frameworks.

Create Free Account →

Free forever — no credit card required

Stop Paying Consultants to Read Spreadsheets

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

$0/forever

Free

  • 706 framework browser
  • Cross-framework mappings (324K+)
  • 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 NIST SP 800-145 and BSI IT-Grundschutz?

NIST SP 800-145 has 8 controls across its framework, while BSI IT-Grundschutz covers 55 controls. Direct mapping analysis identifies 2 overlapping controls (25% coverage). The frameworks diverge most significantly in Deployment Models, where 1 NIST SP 800-145 controls have no direct BSI IT-Grundschutz equivalent.

How many controls map between NIST SP 800-145 and BSI IT-Grundschutz?

Of 8 total NIST SP 800-145 controls, 2 map directly to BSI IT-Grundschutz 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 NIST SP 800-145 to BSI IT-Grundschutz?

6 NIST SP 800-145 controls have no direct equivalent in BSI IT-Grundschutz. The highest concentration of gaps is in Deployment Models 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 NIST SP 800-145 and BSI IT-Grundschutz?

The domain with the highest gap count is Deployment Models (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.