XYGATE Compliance PRO (XSW) Reference Manual

XYGATE
®
Compliance PRO
™
Reference Manual
Chapter 11. Access Analysis Mapping
XYPRO Technology Corporation 196 Proprietary and Confidential
11.8 XAC Access Analysis
Access Mapping for XAC can be performed on any collection from a node that
includes the XAC product. During the load of such a collection, the ACCONF and
ACACL files are expanded and loaded into a database.
Note: A node may contain more than one copy of XAC, so the copy that is chosen to
load is by hierarchy; included in the current XTR configuration, located on
$SYSTEM, currently active, the first configuration located otherwise.
The XAC access queries are intended to examine your ACACL commands and to
determine who can run what XAC Commands.
Each output grid will include some or all of the following commands (shown in
alphabetical order):
Command Name The Name of the Command.
ACLGROUP The name of the ACLGROUP. The individual members of any
ACLGROUP will be expanded as described in section 11.4.1 on
page 187.
ACL_Name The actual name used in the ACL:
Individual or wild-carded userid or alias
ACLGROUP
UNDERLYING: or NETUNDERLYING:
OBJECT_OWNER_GROUP.OBJECT_OWNER_USER
OBJECT_OWNER_GROUP.*
ACL_No The number sequence of the ACL_Name within the COMMAND’s
ACL. If there are 4 entries in the ACL, the sequence numbers will
be 1 to 4.
ACL_Type This column appears in the ACLGROUP output. The ACL_Type
explains how the expanded userids were derived:
A = A specified or expanded Alias
U = A specified or expanded user
S = A placeholder for an expansion such as \*.*,255 or sup*
X = A subordinate ACLGROUP
Alias Name Alias name, if applicable
AllowDeny_All_Procs
Alias_All_Procs
Authenticate_User
Blank_Password
Change_User_To The list of IDs that this particular user can change to
CMD ALLOWCMD or DENYCMD (if not RE_Modifier)
File_Type I = input file, O=obey file
File_Name Input line, filename, or obey file name