This section contains the following topics:
TSSUTIL Report Selection Criteria
Sample TSSUTIL Selection Criteria
TSSUTIL provides the CA Top Secret administrator with batch reports and with the ability to extract audit information recorded in the Audit/Tracking File. This information contains detailed security-related activity; thus you can produce violation and/or activity reports based on customized selection criteria.
The following considerations affect TSSUTIL:
The following logging options are required to obtain security information:
LOG(INIT,...) requests logging of all job/session initiations and terminations.
LOG(ACCESS,...) requests logging of all resource access.
Each facility can be separately monitored.
Violations are always logged by default.
All security events would need to be logged via the TSS LOG option in order to use the full range of options available with TSSUTIL. Selection, therefore, is limited to data available as a result of the TSS LOG option. Multiple and different reports may be generated using the same Audit/Tracking File input data and one use of TSSUTIL.
To use TSSUTIL you must have or be given REPORT authority. This administrative authority may be given by anyone who has REPORT authority with the following:
TSS ADMIN(acid) ACID(REPORT) RESOURCES(REPORT)
You can only report on those incidents that are generated for ACIDs within the scope of your authority. The scopes are:
Every event
Every event within the LSCAs scope
Entire zone or all divisions within the zone
Entire division or all departments within the division
Entire department or all ACIDs within the department
The user
Note: When using EVENT(VIOL) or EVENT(AUDIT), LSCAs, ZCAs, VCAs and DCAs can report on incidents that are generated for resources within their scope, whether or not the ACID causing the event is within their scope. VCAs using EVENT(VIOL) or EVENT(AUDIT) and specifying a department get resources within that department's scope. For more details on EVENT, see TSSUTIL Report Selection Criteria.
Reports can also be run against a release 1.1 format Audit File using the //DD control statement. For detailed information on EXEC parameters and the //DD control statement, see the Implementation Guide.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|