Veritas Velocity™ User's Guide
- Getting to know Velocity
- Setting up Velocity
- How to set up the Velocity Storage Server
- How to set up the Velocity Client
- Setting up the Velocity on-premises management server
- Upgrading Velocity
- Velocity Storage Server
- Users and roles
- Oracle database ingestion using Velocity
- How to use copy preparation to mask or sanitize sensitive data
- Oracle database ingestion using NetBackup CoPilot
- Microsoft SQL Server database ingestion using Velocity
- Database sources and copies
- About scheduling ingestions for a database source
- Retention periods for database sources and copies
- Sandboxes
- Database recovery
- Alerts and logs
- Managing the Velocity physical appliance
- Configuring network address settings on the Velocity physical appliance
- About WAN optimization on the Velocity physical appliance
- About the Veritas Remote Management Console on the Velocity physical appliance
- About Velocity physical appliance storage
- About users on the Velocity physical appliance
- About Velocity physical appliance checkpoints
- About factory reset on the Velocity physical appliance
- Configuring network address settings on the Velocity physical appliance
- Monitoring the Velocity physical appliance
- Velocity physical appliance security
- About Velocity physical appliance user account privileges
- About the Velocity physical appliance intrusion detection system
- About Velocity physical appliance operating system security
- Recommended IPMI settings on the Velocity physical appliance
- Best practices
- Troubleshooting
- Glossary
- Context-sensitive topics
- Section I. Velocity shell menu commands
- Introduction
- Appendix A. Main > Manage > Storage
- Appendix B. Main > Manage > Cloud
- Appendix C. Main > Manage > Software
- Appendix D. Main > Monitor
- Appendix E. Main > Network
- Appendix F. Main > Settings
- Appendix G. Main > Support
How to use copy preparation to mask or sanitize sensitive data
Velocity provides an option that lets you prepare an Oracle database copy for data masking, data sanitizing, or any other data manipulation methods before sandbox users can access the database copies. Masking or sanitizing the data lets you hide the actual data but still provide usable data for test and development purposes. For example, you may want to remove any personal data or sensitive data and insert test data instead.
When you add a database source for ingestion, you can select the
option. Then, after the database is ingested, only the database owner can view it in the list of database copies. The database owner is the person who ran the database ingestion. This restricted view prevents sandbox users from selecting a database copy before you have the opportunity to prepare the data.To change the data in the database copy, create a sandbox for the ingested database on a secure server on which you want to mask or sanitize the data. You can mask or sanitize the data by doing one of the following:
Run your masking script automatically on the database copy when you create the sandbox.
Velocity automatically runs the script when the sandbox is created. After the script runs and the data is masked or sanitized, Velocity runs a snapshot application to make the new database copy with the masked data available to sandbox users, in Sandboxes.
Use your data preparation tools after you create the sandbox.
To change the data in the database copy, create a sandbox for the ingested database on a secure server on which you want to run your data preparation tools. When you have finished preparing the data, Velocity provides a snapshot application for you to run that makes the prepared database copy available for sandbox users.
If you make changes to the database copy in the sandbox, you can run the snapshot application again to make a new copy of the database copy. Sandbox users can then create a sandbox from the prepared database copy that contains the changes.
Sandbox users can create sandboxes only from the prepared database copy. Only the database owner has access to both the original database copy and the prepared database copy.
Note:
Prepared database copies do not expire. You can set a retention date and specify the amount of time to keep the database copy. When the retention period ends, the expired prepared database copy is automatically deleted from the server.
You can disable or enable copy preparation at any time for all of the database copies from a database source, even after the database has been ingested.
All database copies for which copy preparation is enabled are displayed with the following icon:
To mask or sanitize data in a database copy, you must have:
The Velocity administrator role or the Velocity database administrator role.
Root access on the server on which you run the snapshot application if you mask sensitive data manually.
See Masking sensitive data manually in database copies.
See Masking sensitive data in database copies by using a script.
See Masking sensitive data manually in database copies that are already ingested.
See Masking sensitive data by using a script in database copies that are already ingested.