Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Oracle Enterprise Manager Cloud Control 12c: Managing Data Center Chaos

You're reading from   Oracle Enterprise Manager Cloud Control 12c: Managing Data Center Chaos Take back control of your data center with this practical step-by-step tutorial to using Oracle Enterprise Manager. Real-life examples and case studies help you manage rationally rather than through day-to-day firefighting.

Arrow left icon
Product type Paperback
Published in Dec 2012
Publisher Packt
ISBN-13 9781849684781
Length 394 pages
Edition 1st Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
PORUS HOMI HAVEWALA PORUS HOMI HAVEWALA
Author Profile Icon PORUS HOMI HAVEWALA
PORUS HOMI HAVEWALA
Arrow right icon
View More author details
Toc

Table of Contents (19) Chapters Close

Oracle Enterprise Manager Cloud Control 12: Managing Data Center Chaos
Credits
About the Author
Acknowledgements
About the Reviewers
www.PacktPub.com
Preface
1. Chaos at Data Centers 2. Enter Oracle Cloud Control FREE CHAPTER 3. Ease the Chaos with Performance Management 4. Ease the Chaos with Configuration Management and Security Compliance 5. Ease the Chaos with Automated Provisioning 6. Ease the Chaos with Automated Patching 7. Ease the Chaos with Change Management 8. Ease the Chaos with Test Data Management 9. Ease the Chaos with Data Masking 10. Ease the Chaos with Exadata Management 11. Real-life Examples and Case Studies, and It's a Wrap: The Future is the Cloud Index

Chapter 9. Ease the Chaos with Data Masking

In the day-to-day life of the data center, data is frequently copied from production to non-production databases such as test and development databases, and this is required for volume or functional testing, or for the developers to test out their new programs with realistic data.

However, the copied data may contain confidential information, such as credit card numbers, identification numbers (Social Security Number or passport number), which must be protected as per several regulatory requirements—Sarbanes Oxley (SOX), Payment Card Industry Data Security Standards (PCI DSS), Health Insurance Portability and Accountability Act (HIPPA), and other regulations and laws restricting customer data usage. If the copied data is left as it is in the test or development database, it is possible that external or internal hackers may misuse this data. Therefore, it is incumbent on the database department to somehow de-identify or mask this data before it...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image