Oracle Apps DBA: Keeping E-Business Suite Alive · Module 15 · Security, credentials and audit
Auditing: what to record and what it costs
Lesson 157 of 184 · 3 min
What to capture, where it goes, and THE AUDIT TRAIL THAT GREW UNTIL IT BECAME THE SPACE PROBLEM IN MODULE 12. Auditing is the control that answers Lesson 1's problem, and it is also the control most likely to be switched on completely and then abandoned. THE FAILURE MODE IS AUDITING EVERYTHING. It is easy to configure, it feels thorough, and it produces a volume nobody will ever read. Then it becomes a space problem — Module 12 Lesson 1's fifth item — and somebody switches it off to reclaim the disk, which leaves an estate with no auditing at all and a belief that it was tried. SO CAPTURE WHAT SOMEBODY WOULD ACTUALLY ASK ABOUT. Privileged connections — who connected as APPS or as a schema owner, and when. Structural changes: anything that alters an object. Direct changes to data that the application should be the only writer of.…
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.
In this module: Module 15 · Security, credentials and audit
- 1What you are actually holding
- 2The default accounts
- 3The credential in the context fileFree preview
- 4Changing the passwords that matter
- 5Least privilege for a DBA team
- 6Auditing: what to record and what it costs
- 7Encryption, in transit and at rest
- 8Network exposure
- 9What breaks: four security findings
- 10Lab briefing · Audit an estate you did not build