Why Is RESOURCE DB2(DSNR..) Bypassing Being Reported As OK+A In The TSSUTIL Report?

Document ID : KB000050368
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

Why was the security check for the resource DB2(DSNR...), which was granted access through the NORESCHK bypass attribute being reported as OK+A instead of OK+B in the TSSUTIL report?

Solution:

The 'DSNR.' resources need special code to be handled correctly. The security call comes in as a class of DSNR and CA Top Secret converts it to a class of DB2 with 'DSNR.' being appended to the beginning of the original resource name.

Because of the way the special code was implemented, the normal mechanisms CA Top Secret uses to communicate on internal security calls cannot work properly.

CA Top Secret is able to determine that the security call is supposed to be written to the audit file, but CA Top Secret can't determine whether it is supposed to be an OK+A event or an OK+B event.

The event will be recorded as OK+A even though access was granted through the NORESCHK attribute.