Resource DB2(DSNR..) Bypassing Reported As OK+A In TSSUTIL Report

Products

• Top Secret

Issue/Introduction

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

Resolution

The 'DSNR.' resources need special code to be handled correctly. The security call comes in as a class of DSNR and 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 Top Secret uses to communicate on internal security calls cannot work properly.

Top Secret is able to determine that the security call is supposed to be written to the audit file, but Top Secret can't determine whether it is supposed to be an OK+A event or an OK+B event. So the event is recorded as OK+A even though access was granted via the NORESCHK attribute.