Started tasks (STCs), by default, are not protected by CA Top Secret. To prevent security exposure, it is prudent to protect important started tasks. Security protection for started tasks is provided once they are defined to CA Top Secret.
To define a started task, the STC must be associated with a specific ACID, action, or both. Once an STC is defined, it is listed in the STC Record which maintains a list of defined STC procedures with their designated ACIDs. Consequently, the Security Records associated with this STC, including its resource authorizations and its password, can be referenced whenever it is executed.
First, create the ACID associated with the STC, using the TSS CREATE command function. Next, use the ADD(STC) function to add the associated ACID to the STC Record through the following operation:
TSS ADDTO(STC) PROCNAME(stcname)
ACID(acidname)
[STCACT ]
Is either the STC procedure name or the keyword DEFAULT, which is used to establish default processing for all undefined started tasks.
Is a specified ACID or one of the following keywords used to indicate the designated actions:
Requests that the operator supply an ACID and password to provide operator accountability.
When the STC is defined, an STC entry is created in the CA Top Secret STC Record allowing for security validation.
Note: To issue TSS ADDTO(STC) commands, MISC9(STC) administrative authority is required. This means that the security administrator must have MISC9 specified in the ACID's Security Record by a TSS ADMIN command. MISC9(STC) authorizes the maintenance and listing of the STC Record.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|