XOS:The final access result of the access request from SUPER.SUPER where Safeguard is configured with SUPER.SUPER UNDENIABLE

If Safeguard is configured with SUPER.SUPER UNDENIABLE, the Safeguard software ignores explicit or implicit denials of access authorities for the super ID.

1. If the setting of the SUPERSUPEROK entry on the OSCONF file is OFF and the XOS ruling result of the super ID, i.e. SUPER.SUPER and its aliases, is NO, then the Safeguard ACL will not be consulted.
The final access ruling result of the super ID is NO. Therefore, the super ID can?t access files even though Safeguard is configured ?SUPER.SUPER is UNDENIABLE?.

2. If the setting of the SUPERSUPEROK entry on the OSCONF file is OFF and the XOS ruling result of the super ID is YES, then the final access ruling result is YES. Therefore, the super ID can access files.

3. If the setting of the SUPERSUPEROK entry on the OSCONF file is OFF and the XOS ruling result of the super ID is NORECORD, then the final access ruling result is YES. Therefore, the super ID can access files.

4. If the setting of the SUPERSUPEROK entry on the OSCONF file is ON, then the XOS and Safeguard ruling result of the super ID is YES. Therefore, the super ID can access files.

Note: The setting of the SUPERSUPEROK entry on the OSCONF file has no effect if Safeguard is configured ?SUPERSUPER is DENIABLE?

Related Articles
XOS: How do I resolve a security violation (error 48) doing XOS_COMPILE as SUPER.SUPER?
To resolve the error 48 disable and enable the XOS SEEP using the steps below: As SUPER.SUPER: XOS_SAFECOM_DISABLE As the XOS Installation Owner: XOS_COMPILE As SUPER.SUPER: XOS_SAFECOM_ENABLE If you are unable to locate the solution needed or if you ...
Is there is a way to temporarily set SAFEGUARD to allow all access to a volume while the XOS exit-process is disabled
Add a volume ACL to allow everybody access for R, W, E, P, C to all files on the volume. By having a VOLUME ACL during a planned interruption in XOS processes will not terminate with an security violation. Prior to disabling XOS make sure that all ...
XOS: NORECORD IGNORED causing frequent audit rollover
If you want to get rid of ?IGNORED?s, set the AUDIT-NORECORD keyword to OFF in the OSCONF. Additionally, depending on whether or not you want NORECORD audits for non-IGNORE entries, just setting AUDIT_NORECORD OFF wouldn't work. You would also need a ...
XOS: Why am I seeing \UNKNOWN in the XOS Audit Report?
Below are two possible reasons "\unknown" is seen in a XOS Audit Report for node name: A. When the EXPLICIT_NODES is OFF and you try to execute a FUP program on \one node to purge a file on another you see \UNKNOWN on the SUBJECT-SYSTEM field as ...
XAC: XAC process terminated if XOS denies access to INITIAL-DIRECTORY
Add (or correct) an OSSGROUP to access INITIAL-DIRECTORY in Safeguard. OSSGROUP example: OSSGROUP oss-exgrp-exusr MASK RE:"^/users/exgrp/exusr.*" ACL \*.EXGRP.EXUSR (*) $EVERYONE (OSS-CHDIR,OSS-OPENDIR,OSS-OPENR) PROCESS_AS_ACL

XOS:The final access result of the access request from SUPER.SUPER where Safeguard is configured with SUPER.SUPER UNDENIABLE

XOS:The final access result of the access request from SUPER.SUPER where Safeguard is configured with SUPER.SUPER UNDENIABLE

Related Articles

XOS: How do I resolve a security violation (error 48) doing XOS_COMPILE as SUPER.SUPER?

Is there is a way to temporarily set SAFEGUARD to allow all access to a volume while the XOS exit-process is disabled

XOS: NORECORD IGNORED causing frequent audit rollover

XOS: Why am I seeing \UNKNOWN in the XOS Audit Report?

XAC: XAC process terminated if XOS denies access to INITIAL-DIRECTORY