MSAMM
Back to course

Oracle Apps DBA: Keeping E-Business Suite Alive · Module 15 · Security, credentials and audit

Least privilege for a DBA team

Lesson 156 of 184 · 3 min

NAMED ACCOUNTS rather than a shared one, and WHAT YOU GIVE UP BY INSISTING ON IT. Worth it, and SAY WHY. Most DBA teams share a login, and the reasons are practical rather than lazy — which is why an argument for named accounts has to acknowledge what it costs. WHAT YOU GIVE UP IS REAL. Scripts and scheduled jobs that connect need an identity, and giving each person their own means someone's departure breaks whatever ran under their name. Provisioning is more work — every new team member needs an account and the right grants, and getting those wrong means somebody cannot do their job at 03:00. And a genuine emergency at an hour when the person with the right access is unreachable is the case everybody has in mind. WHAT YOU GAIN IS ATTRIBUTION, AND LESSON 1 IS WHY THAT MATTERS TO YOU RATHER THAN ONLY TO THE…

The full lesson is part of the course

The video, the complete written lesson and the module quiz are included in Oracle Apps DBA: Keeping E-Business Suite Alive, 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 15 · Security, credentials and audit

  1. 1What you are actually holding
  2. 2The default accounts
  3. 3The credential in the context fileFree preview
  4. 4Changing the passwords that matter
  5. 5Least privilege for a DBA team
  6. 6Auditing: what to record and what it costs
  7. 7Encryption, in transit and at rest
  8. 8Network exposure
  9. 9What breaks: four security findings
  10. 10Lab briefing · Audit an estate you did not build