[Return to Library] [Contents] [Previous Chapter] [Next Section] [Next Chapter] [Index] [Help]


1    Introduction for Users

The Digital UNIX operating system is delivered with an enhanced security optional subset. When this subset is installed and configured, the system is referred to as a trusted system. The Digital UNIX enhanced security features result in a trusted system designed to meet the C2 class of trust, as defined by the Trusted Computer System Evaluation Criteria (TCSEC, also called the Orange Book). The system also meets the F-C2 functional class as defined in the Information Technology Security Evaluation Criteria (ITSEC).

Although many of the requirements for maintaining the security of the trusted Digital UNIX system are the responsibility of your site's administrative staff, you have a responsibility, as a user of the system, to help enforce the discretionary controls provided by the system. This chapter explains system capabilities and user responsibilities.


[Return to Library] [Contents] [Previous Chapter] [Next Section] [Next Chapter] [Index] [Help]


1.1    Enhanced Security Features

The Digital UNIX system without the enhanced security subset installed provides traditional UNIX security, as described in the Digital UNIX manuals. Traditional UNIX security at the user level consists of basic login identification, authentication (password checking) and file permissions (discretionary access controls (DAC)). The following sections describe how enhanced security extends traditional security.


[Return to Library] [Contents] [Previous Chapter] [Previous Section] [Next Section] [Next Chapter] [Index] [Help]


1.1.1    Login Control Enhancements

Enhanced security provides the following features for login control:


[Return to Library] [Contents] [Previous Chapter] [Previous Section] [Next Section] [Next Chapter] [Index] [Help]


1.1.2    Password Enhancements

Enhanced security provides the following features for password control:


[Return to Library] [Contents] [Previous Chapter] [Previous Section] [Next Section] [Next Chapter] [Index] [Help]


1.1.3    Audit Subsystem

One of the most useful features of a trusted Digital UNIX system is that the administrator can use the audit subsystem to hold users accountable for their actions. The audit subsytem records every relevant security event that happens on the system (for example, each file open, file creation, login, and print job submitted).

Each action is also stamped with an immutable audit ID (AUID) of the user who logged on, which allows all actions to be traced directly to a user. Users, by request to the system administrator, can use the audit trail to help recreate past events that affect the security of their accounts and data.

The audit feature is discussed in detail in Chapter 10.


[Return to Library] [Contents] [Previous Chapter] [Previous Section] [Next Section] [Next Chapter] [Index] [Help]


1.2    How to Determine if Enhanced Security Is Installed and Running

If you are not sure if the optional, enhanced-security features are installed on your system, you can check as follows:

ls -l /usr/.smdb./OSFC2SEC4??.lk
-rw-r--r--  1 root  system  0 Nov  8 11:02 \
                                  /usr/.smdb./OSFC2SEC400.lk

The presence of the lock file (OSFC2SEC400.lk) indicates that the enhanced security subset is installed (but not necessarily running) on your system. If the subset is not installed, you will receive a "not found" message.

To determine if the installed enhanced security is running on your system, enter the following command:

/usr/sbin/rcmgr get SECURITY BASE
ENHANCED

If the string "ENHANCED" is returned, enhanced security is running. If the string "BASE" is returned, enhanced security is not running.


[Return to Library] [Contents] [Previous Chapter] [Previous Section] [Next Section] [Next Chapter] [Index] [Help]


1.3    User Accountability

A trusted system holds all users accountable for the actions that they perform on the system. When you log in, the system associates an audit ID (AUID) with your processes; the AUID remains stamped on processes regardless of the program being run. Even if you change your real or effective user ID (for example, by using su to become root or another user), the system still knows which authenticated user caused a specific action based on the identity recorded in the indelible AUID. Once stamped, the AUID cannot be changed.

The system maintains an extensive authentication profile describing the characteristics and capabilities of each user - for example, the particular login restrictions on the user.

It is extremely difficult for an unauthorized user to break into a trusted system because of the extra security features added to the login procedure. In addition, in a trusted system you can more easily detect a penetration or attempted penetration into your account. Note, however, that these additional assurances are useless if you do not protect your password.


[Return to Library] [Contents] [Previous Chapter] [Previous Section] [Next Chapter] [Index] [Help]


1.4    User Responsibilities

As a user of a trusted system, you must help protect the information that is stored and processed on the system. Specifically, you must do the following:

A trusted Digital UNIX system provides tools and mechanisms that help the system maintain the level of trust for which the system was designed. These are described in subsequent chapters.