Security Management Guide (G06.24+, H06.03+)

Glossary
Security Management Guide—522283-008
Glossary-8
segregation of duties
passwords. A file receives an initial security string from the default security string of the
process that created the file. The security string can later be changed through FUP or
a system procedure call. See also default security string and logon default security
string.
segregation of duties. The practice of separating roles within an organization, especially
with regard to information processing. For example, the duties of systems development
personnel and operations personnel should not overlap.
sensitive data. Data that is confidential, proprietary, or for restricted distribution, or data that
is publicly known but must be protected from arbitrary change.
server. A process that acts on the behalf of requesters to examine and modify databases in
a controlled way.
spoofing. The actions taken by an intruder to disguise his or her true identity from a user to
gain system access. For example, a spoofing program might appear to a user to be the
system logon program, and thus obtain a user’s user ID and password. See also
Trojan horse.
subject. In the Guardian environment and the Safeguard software, a user ID distinguishable
for authorization checks.
super ID. The reserved user ID (255,255). The main purpose of the super ID is to handle
emergencies. It is also required to perform certain sensitive operations. For information
on the super ID, see Managing the Super ID on page 2-18.
super-group user. Any user whose administrative group ID is 255. User IDs within the
super group have implicit authorizations, primarily related to system operations, that
are not available to other users.
SYSnn subvolume. A subvolume, located on the $SYSTEM volume, containing a version
of the operating system. The nn portion of the subvolume can be any two-digit octal
number.
system console. A NonStop system peripheral used for maintenance and some operations
in the NonStop system. See also RMI.
system load. To bring a NonStop system from an initial power-on state to the basic
operational state.
system manager. The person (or persons) responsible for the orderly operation of the
computer system.
system programmer. The person (or persons) responsible for site-dependent, operations-
related programming, such as setting up OBEY command files, writing custom report
generators, and performing maintenance tasks.