Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 16 · Environment management: P2T, refreshes and what breaks
Data masking and why it is not optional
Lesson 158 of 177 · 2 min
A test environment after a P2T holds real salaries, real bank details and real personal data — and test access is wider than production access, granted more freely, and reviewed less. THAT IS THE WHOLE ARGUMENT AND IT IS NOT A COMPLIANCE ABSTRACTION. A consultant with test access can read every employee's salary. A tester can see every customer's bank details. Nobody granted them that; a refresh did. WHAT MUST BE MASKED: anything identifying a person, anything financial about a person, and anything that can REACH a person — which is the category people forget, and it is Lesson 6's email problem. Salaries, bank accounts, national identifiers, personal addresses, dates of birth, email addresses and phone numbers. WHEN: as part of the refresh, before anybody is let back in. Not "this week", not "before UAT starts". The window between the refresh completing and masking running is a window in which…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Fusion Technical: Reports, Data, Integrations and Extensions, with a certificate on completion and a fourteen-day refund window.
In this module: Module 16 · Environment management: P2T, refreshes and what breaks
- 1The environments, and what each is for
- 2What a P2T actually copies
- 3The checklist before anybody clicksFree preview
- 4Data masking and why it is not optional
- 5Preserving configuration across a refresh
- 6Integrations after a refresh
- 7Scheduling refreshes around a project
- 8What breaks: four refresh failures
- 9Lab briefing · Plan a refresh you could defend