STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 1 hour ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to IBM DB2 V10.5 LUW Security Technical Implementation Guide

V-213692

CAT II (Medium)

Database objects (including but not limited to tables, indexes, storage, stored procedures, functions, triggers, links to software external to DB2, etc.) must be owned by database/DBMS principals authorized for ownership.

Rule ID

SV-213692r879586_rule

STIG

IBM DB2 V10.5 LUW Security Technical Implementation Guide

Version

V2R1

CCIs

CCI-001499

Discussion

Within the database, object ownership implies full privileges to the owned object, including the privilege to assign access to the owned objects to other subjects. Database functions and procedures can be coded using definer's rights. This allows anyone who utilizes the object to perform the actions if they were the owner. If not properly managed, this can lead to privileged actions being taken by unauthorized individuals. Conversely, if critical tables or other objects rely on unauthorized owner accounts, these objects may be lost when an account is removed.

Check Content

Get the list of authorized owners from ISSO or DBA.

Use the following catalog views/queries to find the ownership of the various database objects:

Select libname,owner from syscat.libraries
Select modulename,owner from syscat.modules
Select tabname,owner from syscat.nicknames
Select pkgname,owner from syscat.packages
Select routinename,owner from syscat.routines
Select seqname,owner from syscat.sequences
Select constname,owner from syscat.tabconst
Select tabname,owner from syscat.tables
Select tbspace,owner from syscat.tablespaces
Select trigname,owner from syscat.triggers

If any owner is not in the ISSO/DBA provided list, this is a finding.

Fix Text

Use the list identified in check. Drop and create the objects as necessary with the correct ownership.
DB2> DROP
DB2> CREATE

Note: For additional information regarding the DROP statement, select the following link:
http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.sql.ref.doc/doc/r0000945.html?lang=en