Purpose of the Template
An infrastructure migration can inadvertently change who can access a system. In the DigiCert incident, an internal business archive was moved from a VPN-restricted network segment to a different availability zone in February 2025, making the system externally accessible. A self-registration feature meant for other applications was exposed, and a permissions flaw allowed accounts with no assigned roles to have default read-only access to archived customer files. This issue persisted for over 16 months before the company implemented an authorization fix and confirmed unauthorized access to archived data.
This situation didn't require a sophisticated attack. It needed a migration review that asked two critical questions: who can now access this system, and what can an unauthenticated or role-less account do once they arrive?
This template is a pre- and post-migration access review you can integrate into your change management process. It supports your obligation under Article 32 GDPR to maintain appropriate technical and organizational measures, and it provides evidence for a supervisory authority if a personal data breach occurs and you need to demonstrate the controls in place.
Prerequisites
Before using the template, ensure you have:
- A current data inventory for the system being migrated, including whether it holds identity documents or other high-risk records.
- A named system owner and a named reviewer who isn't the engineer performing the migration.
- Access to your network and cloud configuration, plus the ability to test from outside your corporate network.
- Logging enabled on the system, with a known retention period, so you can reconstruct access if something goes wrong.
- A DPO contact (if appointed) who can advise if the review surfaces a potential personal data breach.
The Template
Copy this into your change ticket. Every line needs an answer, an owner, and a date.
SECTION 1: System Profile
- System name and owner:
- Categories of personal data held (contact data, identity documents, financial, other):
- Highest-risk record type present:
- Documented retention period for each category:
- Reason this system is being migrated:
SECTION 2: Pre-Migration Baseline
- Current network location (segment, VPN restriction, firewall rules):
- Current authentication method for all users, including MFA requirements:
- Current list of enabled features, including any registration or sign-up functions:
- Current role and permission model, including the default permission for an account with no assigned role:
SECTION 3: Post-Migration Verification
Complete within 24 hours of the change, before the ticket closes.
- Is the system reachable from the public internet? Test from an external network. Result:
- Does the network location match the approved design? Result:
- Are all features that existed pre-migration still restricted as before? List any that changed:
- Has any feature intended for a different application been exposed? Result:
- Does MFA still apply to every account type that can authenticate? Result:
SECTION 4: Permission Tests
- Create a new account. What can it see? Result:
- Use an account with no assigned role. What can it see? Result:
- Request file and record endpoints directly, bypassing the user interface. Result:
- Attempt to retrieve a record belonging to another user or customer. Result:
- Confirm default permission for unassigned accounts is deny. Result:
SECTION 5: Monitoring and Alerting
- Alert configured for creation of accounts outside approved domains or processes:
- Alert configured for unusual file-access volume:
- Log retention confirmed for the period needed to investigate:
- Named person who reviews these alerts and how often:
SECTION 6: Sign-Off
- Reviewer name, date, and result (pass / pass with actions / fail):
- Open actions and deadlines:
- DPO consulted if sensitive records are in scope (yes / no / not applicable):
Customizing the Template
Section 1 assesses risk. Identifying the highest-risk record type helps prioritize the review. Exposed identity documents have more severe consequences than exposed business contact details. If your system holds such documents, require a second reviewer and shorten the post-migration verification window.
Section 3 is often overlooked. Adapt the external reachability test to your environment. Check cloud security groups or web application firewalls. A restricted user interface doesn't ensure underlying records are protected, so include direct requests to file endpoints.
Section 4 should match your role model. The DigiCert flaw was due to a default setting: accounts with no assigned application role still had read-only access. Replace generic wording with your role names, and always include the unassigned-account test. Add tests for any self-service features your platform includes.
Section 5 needs a real owner. An alert nobody reads isn't a control. In the DigiCert case, non-company accounts were noticed but treated as an account-creation issue rather than a data-access event. Add a triage question to your alert runbook: could this account have accessed stored records? If the answer isn't a documented no, treat it as a potential personal data breach and start your assessment.
Add a retention line to every migration. A migration is a good time to ask whether the data should still exist. Archived identity documents with no deletion process are a standing liability. If the retention period has lapsed, delete before you move, not after.
Validation Steps
Once you've adopted the template, ensure it works:
- Run it retrospectively on one migration completed in the last year. Treat any system you can't confidently answer Section 3 for as a priority review.
- Run a deliberate failure test. In a non-production environment, move a test system without applying the restrictions and confirm your Section 3 checks catch it.
- Confirm the reviewer is independent. If the person who performed the migration also signs off the review, the control is weaker than it appears.
- Check your escalation path. If a review finds that personal data was reachable by unauthorized parties, assess whether Article 33 notification to the supervisory authority is required, typically within 72 hours of becoming aware. Ensure your team knows who makes that call.
- Preserve evidence. Keep completed templates, test results, and logs together. If you ever need to show what you did and when, this record is the answer.
A migration ticket that says "complete" tells you the system moved. This template tells you whether it moved safely.





