MSAMM
Back to course

Administering Cloud EPM: The Platform Beneath the Business Processes · Module 9 · Securing the Perimeter

Network perimeter

Lesson 100 of 201 · 14 min

What network perimeter does — restricting where the estate can be reached from. Configure a perimeter at identity domain level, add allowed ranges, ADD YOUR OWN CURRENT ADDRESS BEFORE ACTIVATING, activate and test, test from a disallowed address and show the block, then show the effect on client components and automation. ADD YOUR OWN ADDRESS FIRST. THEN CHECK IT. THEN ACTIVATE. A network perimeter that excludes the administrator configuring it is a support call, and a slightly humiliating one. AUTOMATION RUNS FROM SOMEWHERE. If EPM Automate runs on a scheduled server, that server's address must be allowed. Build the list from Module 11 BEFORE you activate. Perimeter is a DOMAIN-LEVEL control, which means it applies across every environment in that domain. Consider that in the Module 3 design.

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.

See the course and enrol9 free lessons

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 9 · Securing the Perimeter

  1. 1Defence in depth for an EPM estate
  2. 2Network perimeter
  3. 3Migrating from per-environment IP allowlists
  4. 4Sign-on policies
  5. 5Break Glass: managed provider access
  6. 6Approving access requests
  7. 7Customer-managed keys: the concepts
  8. 8Configuring customer-managed keys
  9. 9Compliance reports and the security capability set
  10. 10Answering a security questionnaireFree preview
  11. 11What breaks
  12. 12Lab: proportionate security, and ten questionnaire answers