Control who can reach staging
Staging sites often use a public hostname. Require authentication or restrict network access. Do not rely on an unlisted URL as the only control.
Check search indexing settings, but do not treat a noindex instruction as access control. Search engines and visitors should not be able to read private test data.
Remove production secrets and customer data
Use separate database credentials, API keys, email settings and payment credentials. Disable live payments and outgoing customer emails in staging.
Use synthetic or de-identified data where possible. If a production copy is necessary, restrict access and remove it when testing ends.
Retire old copies
Keep an owner and expiry date for every staging site. Remove old subdomains and copies when they are no longer needed.
Check that backups and deployment tools do not restore an old public copy. Include staging domains in the website asset inventory.
