4 ms·
I really like Jacob's suggestion to set up the "restore a copy of the production database to staging" script to use an allow-list of columns, rather than a deny
by simonw 5y ago
I really like Jacob's suggestion to set up the "restore a copy of the production database to staging" script to use an allow-list of columns, rather than a deny-list.
It's so, so easy for PII and other sensitive data to end up copied to a staging environment, which has a higher chance of shipping a security vulnerability than the production environment does (plus exposes data to staff within an organization).
Strictly allow-listing columns from the start seems like a great way to minimize accidental leaks.
- deleted 5y ago[deleted]
- donatj 5y agoI’m not sure if it would work for everyone, but we keep all our sensitive data in an entirely separate schema, and everything is to be built to assume the sensitive rows can suddenly not exist at any time. This way we only need to restore the insensitive schema to staging areas, and have different backup policies, keeping the insensitive far longer.