MSAMM
Back to course

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

What you are actually holding

Lesson 152 of 184 · 3 min

Payroll, bank details, personal data and THE ABILITY TO CHANGE ANY OF IT WITHOUT ANYONE NOTICING. Where that leaves your own accountability. An Apps DBA holds more access than almost anybody else in the organisation, and the second half of that sentence is the part worth sitting with. THE DATA IS THE OBVIOUS HALF. Every salary, every bank account the company pays into, every supplier's details, every customer's. A finance director can see the payroll for their own division; you can see all of it, and read it directly without any application recording that you did. AND THE ABILITY TO CHANGE IT IS THE HALF PEOPLE DO NOT THINK ABOUT. Application-level auditing records what users do through the application. A change made at the database level leaves no application audit entry — so the controls the business relies on to know who approved a payment do not see a change

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.

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
What you are actually holding — Oracle Apps DBA: Keeping E-Business Suite Alive — MSAMM