Administering Cloud EPM: The Platform Beneath the Business Processes · Module 9 · Securing the Perimeter
Break Glass: managed provider access
Lesson 103 of 201 · 11 min
Under what circumstances can Oracle's own personnel access your environment's data — and who approves it? Break Glass makes that access explicit, approved and logged, rather than implicit. Why an organization wants it: a regulatory requirement, a contractual commitment to their own customers, or an internal policy about third-party access to sensitive data. THE TRADE-OFF, STATED HONESTLY. Requiring approval for provider access means that when you have a serious support incident, the support engineer cannot begin work until somebody approves. SOMEBODY MUST BE REACHABLE. An organization that enables this without an on-call approval process has made its outages longer. So the operational requirement is: a named approver, a deputy, an out-of-hours route, and a documented expectation of response time. Without those, this control makes things worse. DO NOT ENABLE THIS BECAUSE IT SOUNDS THOROUGH. ENABLE IT BECAUSE A REQUIREMENT SAYS SO — AND ONLY WITH THE APPROVAL PROCESS IN PLACE.…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Administering Cloud EPM: The Platform Beneath the Business Processes, with a certificate on completion and a fourteen-day refund window.
In this module: Module 9 · Securing the Perimeter
- 1Defence in depth for an EPM estate
- 2Network perimeter
- 3Migrating from per-environment IP allowlists
- 4Sign-on policies
- 5Break Glass: managed provider access
- 6Approving access requests
- 7Customer-managed keys: the concepts
- 8Configuring customer-managed keys
- 9Compliance reports and the security capability set
- 10Answering a security questionnaireFree preview
- 11What breaks
- 12Lab: proportionate security, and ten questionnaire answers