Germany's Bundestag has passed a major overhaul of its intelligence laws, allowing the BND to act against threats abroad, including hacking foreign systems and disabling servers run by hostile state-backed hackers. The BfV gains new domestic powers, such as blocking or rerouting data traffic. Both agencies can now legally analyze large datasets with AI.
This checklist is for enterprise risk officers whose organizations operate in Germany, route data through it, or depend on German partners. It helps you document your exposure, test your assumptions, and demonstrate to regulators or your board that you've considered the changes.
Prerequisites
Before you start, gather these:
- A current data flow map showing where Personally Identifiable Information and sensitive business data travel, including German telecom and hosting providers.
- Your vendor inventory with country of operation and subcontractor chains.
- Your existing Risk Management Framework documentation and risk register.
- Your Incident Response Plan and the contact list for your German entities.
- Legal counsel familiar with German and EU law.
Checklist
1. Assign an owner and open a risk register entry.
Ensure a named executive owns "German intelligence law change" as a tracked risk with a review date.
Good looks like: The entry cites the legislation, states the hypotheses you are testing, and is reviewed regularly.
2. Map your German footprint.
List every legal entity, data center, network path, and vendor tied to Germany.
Good looks like: The map includes indirect exposure, such as a SaaS provider hosted in Germany that your headquarters never contracted with directly.
3. Identify whether you sit in critical infrastructure supply chains.
Determine if you're a critical operator, a supplier to one, or neither.
Good looks like: A documented determination, aligned with your obligations under the NIS2 Directive where it applies, with the reasoning recorded.
4. Review telecom and hosting contracts for traffic-data clauses.
Check whether your contracts address provider notification, scope, and your right to be informed where lawful.
Good looks like: Contracts state what the provider will disclose to you about preservation orders and who your point of contact is.
5. Reassess data protection assumptions under the General Data Protection Regulation.
Confirm with counsel how the new powers interact with your transfer mechanisms, records of processing, and Data Protection Impact Assessments for German data.
Good looks like: Counsel's written view is on file, and any DPIA touching German traffic or metadata has been updated or consciously left unchanged with a rationale.
6. Confirm encryption coverage and Encryption Key Management for data in transit.
Ensure content protection is prioritized over metadata protection you can't control.
Good looks like: Keys are held under your control, rotation is documented, and you've listed which metadata still leaks despite encryption.
7. Add state-actor disruption scenarios to your Incident Response Plan.
Include a scenario where traffic is rerouted or a hosting provider's infrastructure is affected by an operation targeting a third party.
Good looks like: The scenario names decision rights, customer communication triggers, and a regulator-notification path, and it has been exercised in a Tabletop Exercise.
8. Evaluate collateral-impact risk from operations against shared infrastructure.
Assess whether your workloads could share a provider or network segment with adversaries.
Good looks like: Your top providers have been asked about tenant vetting and takedown notification, and answers are recorded.
9. Reassess third-party and fourth-party concentration.
Check consistency with the Digital Operational Resilience Act on ICT third-party risk.
Good looks like: A register of German-dependent providers with substitution options and exit plans for the critical ones.
10. Update Key Risk Indicators (KRIs).
Add indicators such as the number of critical services dependent on German-hosted infrastructure.
Good looks like: Each KRI has a threshold, an owner, and an escalation action, not just a dashboard tile.
11. Brief the board and document the decision.
Ensure the board or risk committee has received a briefing and minuted its risk appetite stance.
Good looks like: The briefing separates what the law does from what you are assuming, and it records accepted, mitigated, and monitored items.
12. Set a monitoring trigger.
Assign someone to track implementation guidance, oversight decisions, and any court challenges.
Good looks like: A defined trigger for re-running this checklist, such as new regulatory guidance or a publicized operation affecting commercial infrastructure.
Common Mistakes
- Treating this as a German-only issue. Data routing and vendor chains carry exposure into organizations with no German office.
- Assuming the law targets your company. It targets foreign threats. Your risk is mostly indirect: shared infrastructure, traffic handling, and provider obligations.
- Skipping the comparison with other jurisdictions. The law stops well short of some allies' powers. Overreacting to Germany while ignoring those regimes distorts your picture.
- Relying on a legal memo without operational follow-through. A memo that never reaches contracts, runbooks, or KRIs hasn't reduced risk.
- Ignoring oversight developments. Hacking operations and active measures inside Germany require advance approval from the Independent Control Council, now doubled from six to twelve members. How that body behaves will shape real-world impact.
Next Steps
Start with items 2 and 3; they determine how much of the rest applies. Have counsel review items 4 and 5 within your next risk committee cycle, and schedule the Tabletop Exercise in item 7 before the next quarter closes. Then fold the register entry into your standard risk reporting so the topic doesn't sit in a standalone project.
If your team lacks the bandwidth to run this assessment, a Virtual CISO (vCISO) or Fractional CISO can own the review and brief your board without a permanent hire.




