Administering Cloud EPM: The Platform Beneath the Business Processes · Module 9 · Securing the Perimeter
What breaks
Lesson 109 of 201 · 2 min
Eight cases, and two of them are the control itself causing the damage. One. "We activated the network perimeter and locked ourselves out." Own address not allowed. Add it, verify it, THEN activate. Two. "Overnight automation stopped after the perimeter change." The automation server's address was not in the list. Three. "Support could not help during an outage." THE CONTROL MADE THE INCIDENT LONGER. Managed access approval with no reachable approver. Four. "We cannot decrypt after a regional failover." Key not replicated. Five. "Nobody can sign in and there are three possible causes." Perimeter, sign-on policy and SSO all in play. Use the diagnostic order. Six. "We claimed a control we had not configured." The questionnaire was answered from the feature list rather than from the configuration. Findable. And damaging. Seven. "The security review found controls with no owner." Decisions made implicitly. The decision log exists for this. Eight. "Perimeter…
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