Framework overlap

Does BSI IT-Grundschutz cover ITU Radio Regulations and Space Security Standards?

You hold BSI IT-Grundschutz and have been told to do ITU Radio Regulations and Space Security Standards. Here is how much overlaps, control by control.

25% of ITU Radio Regulations and Space Security Standards you already have

BSI IT-Grundschutz already covers about 25% of ITU Radio Regulations and Space Security Standards, leaving 6 of 8 controls as genuinely new work.

Already covered 0 Likely covered 2 New work 6

No control in BSI IT-Grundschutz maps directly to one in ITU Radio Regulations and Space Security Standards. Everything counted as covered is covered because both map to the same third standard, which is what a crosswalk is, but it is an inference rather than a lookup.

What is genuinely new work

Nothing in BSI IT-Grundschutz reaches these. This is the list to scope.

ITU-Coordination-Notification-MIFR-Art9-Art11-Art12-Advance-Publication-Master-International-Frequency-Register
ITU Radio Regulations Article 9 Coordination + Article 11 Notification and Recording + Article 12 International Frequency Registration + Advance Publication + Master International
ITU-Cybersecurity-Space-Systems-Coord-ITU-T-X-Series-X.805-X.1500-ITU-D-WSIS-CIRT-Outer-Space-Treaty
ITU Cybersecurity of Space Systems + ITU-T X-Series (X.805 + X.1500 + X.1205) + Sector Coordination + ITU-D Development + WSIS + GCI Global Cybersecurity Index + CIRT National Comp
ITU-Earth-Stations-Licensing-Service-Plans-BSS-FSS-MSS-Plans-Appendix30-30A-30B-Region-Plans
ITU Radio Regulations Earth Station Licensing + Coordination + Appendix 30 BSS Plans + Appendix 30A BSS Feeder Links + Appendix 30B FSS Plans + Service Plans + Region 1 + Region 2
ITU-Frequency-Allocations-Art4-Art5-3-Regions-Service-Categories-Primary-Secondary-Allocation-Table
ITU Radio Regulations Article 4 Assignment and Use + Article 5 Frequency Allocations + 3 ITU Regions + Service Categories + Primary + Secondary Allocations + Frequency Allocation T
ITU-Interference-Prevention-Art15-Art16-Harmful-Interference-International-Monitoring-System-Reporting
ITU Radio Regulations Article 15 Interference Prevention + Article 16 International Monitoring + Harmful Interference Reporting + Resolution Process + RFI Geolocation + Internation
ITU-Space-Debris-Mitigation-IADC-Guidelines-UNCOPUOS-LTS-25Year-Rule-EOL-Disposal-Registration-Convention
ITU + IADC Space Debris Mitigation Guidelines + UNCOPUOS Long-Term Sustainability (LTS) Guidelines + 25-Year Rule + End-of-Life Disposal + Registration Convention + Outer Space Tre
Show the 2 you already have
ITU-Scope-Constitution-Convention-Radio-Regulations-WRC-Quadrennial-Treaty-Art1-Definitions
ITU Constitution + Convention + Radio Regulations Scope + Article 1 Definitions + Article 2 Nomenclature + WRC World Radiocommunication Conference Quadrennial Treaty Process + Memb
ITU-Space-Services-Art21-Art22-Art23-PFD-EPFD-Limits-NGSO-Constellation-Milestones-Bringing-Into-Use
ITU Radio Regulations Article 21 Terrestrial and Space Sharing + Article 22 Space Services + Article 23 Time Signal + PFD Power Flux Density + EPFD Equivalent PFD + NGSO Non-Geosta

How this is calculated

Already covered means a mapping runs from a control in BSI IT-Grundschutz to that control. Likely covered means no direct mapping exists but both frameworks map to the same control in a third standard. New work means neither. We keep those separate rather than adding them into one friendlier number, because blending them would present a two-hop inference as a verified fact.

Coverage is not symmetric. Run it the other way and you will get a different number; both are correct.

From 332,959 cross-framework control mappings across 723 frameworks, 531 of them verified against their source documents. It does not tell you that you are compliant: a mapped control means the two standards ask for the same thing, not that you have done it.

Try another pair ยท Today's edition