Exclude SELECT from DB2 Audit Policy

a { text-decoration: none; color: #464feb; } tr th, tr td { border: 1px solid #e6e6e6; } tr th { background-color: #f5f5f5; }

I recommend voting to exclude the SELECT option from the DB2 audit policy based on the following technical considerations. Auditing SELECT statements can generate an extremely high volume of audit records due to the read‑intensive nature of applications and reporting workloads. This significantly increases audit log size, storage requirements, and archival overhead.

From a performance perspective, enabling SELECT auditing introduces additional I/O and CPU overhead on the DB2 engine, which may impact query response times—especially for high‑frequency or batch read operations. In most environments, SELECT activity does not represent a direct data‑change or privilege‑escalation risk, and the security benefit gained does not justify the operational and performance cost.

Excluding SELECT allows the audit policy to remain focused on higher‑risk events such as INSERT, UPDATE, DELETE, DDL changes, and privilege modifications, ensuring effective compliance monitoring without unnecessary system overhead.

Needed By

Month

Post comment

Guest

Apr 15, 2026

I second this. It’s a top priority for our team

Reply
Hide replies

Guest

Apr 15, 2026

I support this recommendation. This feature is crucial for our operations.

Reply
Hide replies

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.

Please enter your email address

RELATED IDEAS

Exclude SELECT from DB2 Audit Policy