Safeguard Reference Manual (G06.29+, H06.08+, J06.03+)

Table Of Contents
Introduction
Safeguard Reference Manual 520618-030
1 - 10
Interaction of Local and Remote Users and
Requests
Remote User
A term used in this manual to refer to either a remotely authenticated user or an
unauthenticated user.
Remotely Authenticated User
A valid network user who has been authenticated by a node other than the local node.
Unauthenticated User
A process that lacks a valid user ID; for example, a user who has failed remote
validation in an attempt to access objects on the local node.
Local Request
A local request originates on the same node in which the process receiving the request
is running.
Remote Request
A remote request made in relation to the process receiving the request. This request
originates on another node in a network.
Interaction of Local and Remote Users and Requests
In determining whether to audit a request, the Safeguard software considers a local
user making a local request to be a local request. Any request from a remote user is
considered a remote request.
Thus, if REMOTE is the value of AUDIT-ACCESS-PASS for a disk file, the Safeguard
software audits any attempt that it authorizes to access the file (that is, any authorized
OPEN requests for READ, WRITE, EXECUTE, or PURGE access) that originate from
a remote system or are sent by a remote user.
The remote user described here is not the same as the network user (defined in
Section
2, Common SAFECOM Language Elements). A network user is a user who
has been added to several systems and has matching remote p
asswords between
those systems. A remote user is simply a process that is not locally authenticated. The
remote user does not necessarily have a matching password definition on the local
system. For more information, see Network Users on page 2-17.
Components of the Safeguard Subsystem
The Safeguard subsystem consists of a number of processes and security database
files. These processes cooperate to manage the contents of the security database, to
authenticate users, and to authorize attempts to access protected objects.