Germany: separate preservation, data disclosure and response
A preservation request needs its own verification and execution workflow. Germany’s reform provides a case for keeping that workflow separate from data disclosure and response actions.
Lire en portugaisBy Pentesty
Record the legislative stage before designing the process
The Bundestag record reports parliamentary adoption of the intelligence-law reform on November 13, 2026. The government explanation gives December 31 as the intended commencement date, which is still in the future at the time of this analysis. Track adoption, publication and commencement as separate milestones.
Identify who follows official acts and who determines their application to the service operated. Record the document, version, consultation date and accountable reviewer. The powers of state agencies require a contextual assessment before changing a business procedure.
Model preservation before disclosure
The official explanation distinguishes temporarily freezing traffic records at a provider from a later request to obtain those records. That distinction is useful when designing two operational controls: keeping a defined dataset available and authorizing a specific disclosure.
In the proposed internal procedure, an incoming request should identify the records at issue, the relevant period and who will assess its authenticity and scope. The technical team translates the approved scope into systems, identifiers and verifiable time windows. The decision record should make that translation reviewable.
Keep a known verification channel
Plan a simulation in which support receives an apparently official request. Use a fictional sender and test information. The recipient should route the request to the designated owner while confirmation takes place through a previously validated channel. Retain the connection between the initial contact, verification and decision.
Include a follow-up request that extends the period or adds another customer. Observe how the workflow requires a new assessment and how the earlier authorization remains bounded. An approval should be traceable to the request reviewed, the identity making the decision and the resulting execution.
Demonstrate the preserved dataset
In a test database, select records within the authorized period and add neighboring records outside it. Run the agreed preservation procedure. Retain the query used, selected identifiers and integrity evidence appropriate to the system. Also check which records continued through the normal retention cycle.
Acceptance needs to consider what happens during execution. New records may arrive while selection is running, and a deletion job may already be scheduled. Document how the team detects these conditions and communicates a gap. The evidence should explain the outcome, including any part of the dataset that could not be preserved.
Assess disclosure as another operation
When a specific disclosure decision exists, test the export using fictional data. Check the recipient, content, period, transfer method and receipt record. Keep the identity executing the export distinct from the evidence showing who approved its scope. Retain a trail that reconstructs the sequence without placing the underlying data in widely accessible tickets.
To close the exercise, check the review of temporary permissions and the handoff of the preserved copy to the approved retention procedure. Define how subsequent changes to the request will be handled. The conclusion should identify the observed behavior and outstanding work assigned to a named owner.
Connect the decision to security work
For an authorized technical assessment, connect the objective, systems, test identities and stopping conditions. Each conclusion about the workflow should point to evidence, with its scope and limitations.
Our Pall Mall analysis connects procurement, purpose and capability changes. Use these contexts to frame questions and produce independent evidence about the workflow the business operates.
Frequently asked questions
Does preserving records demonstrate that they were disclosed?
They are separate operations in the proposed workflow. Record selection and integrity of the preserved dataset, then assess the authorization and outcome of any export separately.
Should parliamentary adoption be recorded as immediate commencement?
Keep the milestones separate. The official explanation consulted gives December 31, 2026 as the intended commencement date; follow the relevant acts before applying a conclusion to the service.
Which data should the simulation use?
Use fictional records inside and outside the chosen period, with verifiable identifiers. This makes selection and exception handling observable without using real third-party data.
What evidence supports acceptance of the exercise?
Connect the request, decision, execution and result. Record gaps, temporary permissions and owners of outstanding work before acceptance.
Sources and references
- Cyber Security Brazil: editorial news reference
- Bundestag: legislative proceedings and parliamentary adoption
- German government: questions and answers on the reform
Original Pentesty analysis, published November 14, 2026. The proposed scenarios are editorial guidance, with scope and validation to be defined for each environment.