Open System Services Management and Operations Guide (G06.30+, H06.08+, J06.03+)

Figure 21 Major Components and Interfaces for OSS Security Management
See the Security Management Guide for an overview of both Guardian and OSS security. See the
Safeguard Audit Service Manual for a description of the SAFEART program and the information
logged for audited OSS files.
Beginning with the J06.15 and H06.26 RVUs, the OSS name server consults the OSS SEEP for
operations on files in OSS SEEP-protected Version 3 catalog filesets, if the OSS SEEP is running.
For details of OSS SEEP consultation, see the OSS SEEP Programming chapter in the Open System
Services Programmer's Guide.
The commercial text Practical UNIX & Internet Security listed in “OSS Security” (page 33) contains
many suggestions for securing file systems. Those suggestions include which actions to avoid in
best-practice system administration.
Differences Between OSS and UNIX User and User-Group Configuration
You configure a NonStop operating system user for access to the OSS environment through a fully
licensed version of the Safeguard product. Whether you license Safeguard determines the security
and user configuration features available for managing the OSS environment. If you use the optional
Safeguard product, you can:
• Configure a user name with an administrative group name and a member name
• Configure an alias for a user name, for Guardian or OSS environment login and use
• Configure an initial working directory OSS pathname for a user ID when the OSH command
is used to start an OSS shell
• Configure the initial directory and interface when a user accesses the FTP server
• Configure an initial program to execute when access occurs for a specific user definition, if
a server supports that feature
• Define file-sharing user groups for OSS access with group numbers above 255
222 Managing Security