Security for address spaces started before TSS and not defined in STC Table

Products

• Top Secret

Issue/Introduction

Starting an address space prior to TSS starting  allows the STC to start without an entry in the STC Table. 

 

 

Environment

Release : 16.0

Component : Top Secret for z/OS

Resolution

Starting an address space prior to TSS starting  allows the STC to start without an entry in the STC Table. 

If acid has (+) as the first character, is an indication that this task started before TSS was initialized.
or
Started task not defined to the STC, so it is picking up the default which is bypass.

Once those STCs issue any security check after TSS has been properly initialized then we should rebuild the security
environment according to the acid specified in the STC table.
It should go through normal security checking unless security is being bypassed.

Issue a TSS LIST(STC) and check what the default STC is.
It might be *BYPASS*. This is the default.

example:

TSS LIST(STC)
 ACCESSORID = *STC*     NAME       = STARTED-TASKS
 TYPE       = GLOBAL    SIZE       =      256  BYTES
 
 STC        = *DEF*     ACID       = *BYPASS* <----------------
 STC        = FORSEC*   ACID       = STCACID