Start of change

What's new in Db2 11 for z/OS security?

Start of changeDb2 11 for z/OS provides critical enhancements to security and auditing. These enhancements strengthen Db2 security in the z/OS environment.End of change

Db2 enhancements for exit authorization checking

Starting in Db2 11, Db2 provides the ACEE of the package owner for authorization checking when the access control authorization exit is active. Db2 also refreshes the cache entries of the package authorization, the routine authorization, the DDF user authorization, and the dynamic statement when a user profile or resource access is changed in RACF® and the access control authorization exit is active.

If the AUTHEXIT_CHECK subsystem parameter is set to DB2, Db2 provides the ACEE of the package or plan owner to perform authorization checking during the processing of the autobind, BIND, REBIND PACKAGE, and REBIND PLAN commands and, if needed, the execution of the package or plan. Db2 also provides the ACEE of the authorization ID as determined by the DYNAMICRULES option to perform dynamic SQL authorization checking at run time. The access control authorization exit uses the ACEE for XAPLUCHK for authorization checking. The XAPLUCHK authorization ID can be a user or a group in RACF. To ensure successful authorization checks with the owner ACEE, the owner authorization ID in XAPLUCHK must be permitted access to the resources in RACF.

When the AUTHEXIT_CACHEREFRESH system parameter is set to ALL and the access control authorization exit is active, Db2 listens to type 62, type 71, and type 79 ENF signals from RACF for user profile or resource access changes. Then, Db2 refreshes the Db2 cache entries as needed. If you define RACF classes for Db2 objects and administrative authorities without using IBM®-supplied RACF resource classes, you must enable the SIGNAL=YES option for these classes in the RACF Class Descriptor Table.

The RACF access control module (DSNXRXAC) is also enhanced to support the new global variable READ (READAUTH) and WRITE (WRITEAUTH) privileges. In addition, it returns the RACLISTED classes in the new XAPLCLST field at Db2 startup, and supports authorization checking that is associated with autobind requests for user-defined functions.

Db2 enhancements for program authorization

Starting in Db2 11, Db2 provides the capability to check whether an application program is authorized to use a plan.

When program authorization is enabled, it is performed in addition to package authorization.

With package authorization, if you own a plan and do not know in advance which programs or packages use the plan, you must enable the necessary authorization by binding the plan with all collections or packages that are used by any programs that execute the plan. A disadvantage to this approach is that if a user has EXECUTE authority to run the plan, the user can accidentally invoke the wrong program, or can change the program to execute a different set of packages from the intended set.

Program authorization does not have this disadvantage, because it allows a program to run only the plans that you specify.

Program authorization is enabled for a program and its plan if the following conditions are true:

  • The plan is bound with the new PROGAUTH(ENABLE) option for BIND PLAN and REBIND PLAN.
  • Table SYSIBM.DSNPROGAUTH contains a row for the program and the plan.
End of change