MSAMM
Back to course

Oracle Integration Cloud: Building Integrations That Survive Production · Module 12 · Security: credentials, certificates and network

The service account and least privilege

Lesson 119 of 175 · 2 min

An account whose ROLES are the ceiling on the damage. Why "the integration needs admin" is almost always a shortcut rather than a requirement. Whatever the integration's account can do is what a compromise of that credential can do, and that is the whole of least privilege. An account restricted to reading suppliers and creating invoices is a bounded loss; an administrator account is the entire system. "IT NEEDS ADMIN" USUALLY MEANS "NOBODY WORKED OUT WHICH ROLES IT NEEDS." That is not laziness — it is genuinely harder: the integration fails with a permission error, admin makes it stop failing, and the deadline is today. Every estate has at least one integration running as administrator because it was faster on the day. THE METHOD THAT WORKS IS TO START WITH NOTHING AND ADD. Give the account no roles, run the integration, read the permission error, grant exactly what it names,…

The full lesson is part of the course

The video, the complete written lesson and the module quiz are included in Oracle Integration Cloud: Building Integrations That Survive Production, 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 12 · Security: credentials, certificates and network

  1. 1What an integration actually holds
  2. 2Where credentials liveFree preview
  3. 3The service account and least privilege
  4. 4OAuth, and which grant to use
  5. 5Certificates: trust, identity and expiry
  6. 6Rotation without an outage
  7. 7Network: allowlists and private endpoints
  8. 8What ends up in a log
  9. 9What breaks: four security failures
  10. 10Lab briefing · Audit an integration for exposure