Ju

TrustFun

TrustFun Detail

Overview

Detail

Every object in the list view has rights to the analyzed file for some reason and that reason is can easily be determined using the listview. The following table shows how to interpret some of the lines in a listview:

Description

TrustFun Example

AADP.acct.la.acme is security equivalent to AELRTT.acct.atlanta.acme, which has RF rights to the file beign analyzed, SYS:\DSC\EXERCISE.NLM

TrustFun Example

AASSEY.acct.la.acme is a member of the group badabing.la.acme, which has Supervisor rights to the Acme Organization Object.

TrustFun Example

AASSEY.acct.la.acme is a member of the group badabing.la.acme, which has explicit WRITE rights to the ACL attribute of the root of the tree. There is no user icon since the preceeding line is for the same object. This helps in visually locating duplicate trustee assignments.

TrustFun Example

.BOB.seattle.acme is security equivalent to the DSCS1.yescert.acme server. Because the server has Supervisor rights to itself (and all its volumes) and BOB.seattle.acme is equivalent to it, he has Supervisor rights to all volumes and therefore the file being analyzed.

TrustFun Example

The DALLAS.acme container has a DIRECT trustee assignment to the root of the SYS volume. All users in the DALLAS.acme container have WCEF rights to the root of the volume. The TrustFun filter icon indicates that these users would have had additional rights if they were not blocked by an IRF. See the Filter map to determine where in the file system the Filter was applied.

TrustFun Example

SUB.acct.departments.mgt.acme is an occupant of the role.brainshare.acme Organizational Role, which has Supervisor rights to the yescert.acme container.

You may click on any row in the listview to get detailed information on that object as well as the trustee assignment.

TrustFun Details