This section describes the possible values for the SERVICE, INCLUDE, and EXCLUDE fields of the TSSOERPT report. These values are case-sensitive.
Note: Additional information that appears on the report when the DETAIL option is specified is a function of the call.
Determines if a user has the requested access (READ, WRITE, EXECUTE, or SEARCH) to the specified file or directory.
Checks if a current process is a superuser or the owner of the specified file. A process could be the owner of a file if the effective UID is equal to the file owner's UID.
Determines whether the current process has the requested access to the interprocess communication (IPC) key or identifier whose IPC security packet (IISP) is passed.
Checks whether the calling process is a superuser or is the owner of the file/directory, or directory/directory entry pair represented by input FSP1 and FSP2. A process is the owner of the file if the processes effective UID is equal to the file's owner UID.
Determines if the calling process is a superuser.
Checks to see if the calling process is the owner of a process being called.
Clears temporary access given to a file or directory. (Resets the S_ISUID, S_ISGID, and S_ISVTX bits in the file's or directory's access permissions to zero. For information, see the IBM z/OS UNIX System Services User's Guide.
Indicates that the user's access to USS terminated.
Indicates that a call was made to determine the GID for a groupname or the groupname for a GID.
Gets the real, effective, and saved UIDs and GIDs, and the supplemental groups from the USP.
Indicates that a call was made to determine the UID for a username or the username for a UID.
Provides an interface for creating and managing security contexts created through the pthread_security_np service.
Indicates initial user access to USS.
Seen when a file or directory is created.
Builds an IISP in the area provided by the caller.
Indicates that a new file system is being initialized in a new PDSE/x data set.
Indicates that file security options were queried to determine the settings.
Indicates that system security options were queried to determine the settings.
Allows applications to pass an CA Top Secret command buffer used to update the CA Top Secret secfile.
A record cut in addition to a security service record. The record supplies additional information about the file being audited.
Indicates a call was made for cache services. A cache is stored in a data space and contains security relevant information. The cache functions are:
Indicates that a file's Audit Options have been changed.
Indicates a file's permissions (mode) have changed.
Changes a file's owning UID and GID to a new value.
Implements OCSF data library support, which provides access to digital certificates connected to a keyring.
Enables an application server to check a user's authority to access a CA Top Secret defined resource. Used only for the USS kernel on behalf of an application server.
Retrieves or sets fields in the DCE USER profile record.
Enables USS DCE to retrieve or set a DCE password (key).
Enables USS DCE to determine the user ID of the client from the string forms of the client's DCE UUID pair.
Changes the effective and saved UID or GID or both.
Indicates a call was made to get the security information for a forked process.
Indicates a call was made to determine what groups the current process or user belongs to.
Indicates that a call was made to determine the groups to which a specific userid belongs.
Performs functions based on a function code.
Retrieves or sets SecureWay Security Server Network Authentication Service fields. The service returns principal or realm information and updates the count of invalid attempts at accessing the SecureWay Security Server Network Authentication Service. The invalid key count is also cleared upon successful access to the service.
Indicates that a check was made to see if a calling process can ptrace a target process it is calling.
Allows applications to request the generation retrieval and administration of V3 X.509 digital certificates.
Allows applications to invoke the LDAP component of the Security Server for z/OS to obtain data which resides in an LDAP directory.
Changes the effective GID to a different GID
Changes the effective UID to a different UID.
Indicates a call was made to create or modify an Access Control List.
Changes the security label in the FSP
Changes the real, effective, and saved GIDs to a different GID.
Changes the real, effective and saved UID to a different UID.
This service enables application servers to parse or extract principal names from a GSS-API context token. This enables an application server to determine the client principal who originated an application-specific request when the request includes a GSS-API context token.
Change of permissions that a program sets in a new file or directory when it creates a new file or directory.
Enables z/OS application servers to determine the application user identity associated with an CA Top Secret acid, or to determine the CA Top Secret acid associated with an application user identity or digital certificate. Currently, the only supported applications are Lotus Notes for z/OS and Novell Directory Services and SecureWay Server Network Authentication Server.
Sets, resets, or queries the setting of the write-down privilege in the ACEE. When MLS is active, the following fields are captured on the TSSOERPT report:
Many log entries show additional information about the request. The information is contained internally as Security Credentials (CRED) and File Security Packets (FSP). This information is common to many calls and can appear in the following fields on the TSSOERPT report if it is available:
Specifies the function attempted for a file or directory, for example OPEN and SEARCH.
Specifies the full pathname of a file or directory, including the file or directory name itself. There could be two pathnames specified if the call involved more than one file or directory.
Specifies the name of a file or directory. In the case of a ck_access, this field names the part of the path currently being validated for access (If the path is aa/bb/cc three separate ck_access calls are seen: the first with filename aa, the second with filename bb, and the third with filename cc ). There can also be two filenames specified if the call involved more than one file or directory.
Specifies the access permissions for the file's owning UID (owner), the file's owning GID (group), and all others attempting access (other).
Specifies the UID of the owner of the file or directory. If the real UID of a user or process attempting access to this file matches the owning UID, access is granted according to the owner file permissions.
Specifies the GID of the owner of the file or directory. If the real GID of a user or process attempting access to this file matches the owning GID, access is granted according to the group file permissions. If the process or user does not have the owning GID as its primary GID, but has a supplemental group that matches the owning GID, access is also determined by the group file permissions.
Note: If the GID or UID do not match the owner's GID or UID, the other file permissions are used to determine access.
Specifies the volume on which the file system that contains the file resides.
In some cases pathname or filename are not indicated in a call. In this occurs, access is validated using the file identifier. To determine the path and filename for this call, find the last previous call with the same file identifier. The pathname and filename for that call are the same as for the call in question.
The file audit options are:
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|