Contents
How can we protect production environment?
10 elements every production environment must have
- Redundancy.
- Disaster recovery capability.
- Secure access.
- SEE: Network security policy (Tech Pro Research)
- Standardized access.
- Minimalism.
- A patching strategy.
- Segregated networks.
What are non-production environments?
A non-production environment is an environment used exclusively for purposes other than production, such as when software application developers develop and test code. Optimize your licensing investments with the Non-production Environments Software Asset Management (SAM) Engagement.
How is production data protected in non-production environments?
The results look something like this: As you can see, the data is masked, ensuring that sensitive production data isn’t exposed from within the application. The masking changes are persisted with the database, so they’ll survive a backup and restore.
How to protect sensitive data outside the production environment?
Grant Fritchey discusses the need to ‘shift left’ the database and associated database testing, while keeping sensitive data secure when it is outside the production environment, and how SQL Provision can help you achieve this.
What makes a code fail in a production environment?
Code fails because it encounters unexpected data values (outside the expected range of values) or unexpected data types, or it performs terribly because the queries it executes were tested on a volume and distribution of data entirely different from what’s present in production.
Why do you need automated production data provisioning?
Finally, you need database and data provisioning to be automated, so that you get all this data quickly, and exactly when you need it during your development and testing cycle. However, the people in charge of production data can’t, won’t, and shouldn’t give you access to that data. What now?