Safeguard Administrator's Manual (G06.24+, H06.03+)
Table Of Contents
- What’s New in This Manual
- About This Manual
- 1 Introduction
- 2 Controlling User Access
- Introduction
- Using SAFECOM to Establish a Local User Community
- Using SAFECOM to Manage User Access to Your System
- Changing the Owner of a User Authentication Record
- Granting a User Temporary Access to Your System
- Requiring Users to Change Their Passwords
- Granting a Grace Period for Changing an Expired Password
- Forcing Immediate Expiration of a User’s Password
- Freezing a User's Ability to Access the System
- Specifying Auditing for a User ID
- Deleting Users
- Deleting Administrative Groups
- Using SAFECOM to Establish a Network of Users
- Using Safeguard With Nodes With Standard Security
- Identifying Network Users
- Granting a Network User Access to Objects on Your System
- Establishing a Community of Network Users
- Changes to the PAID During a User’s Session
- Additional Considerations for Aliases and Groups
- Additional Considerations for ACCESS with Network Specific Subject IDs
- Establishing Default Protection for a User's Disk Files
- Specifying a Default Command Interpreter for a User
- Establishing Guardian Defaults
- Assigning an Alias to a User
- 3 Managing User Groups
- 4 Securing Volumes and Devices
- 5 OBJECTTYPE Control
- 6 Managing Security Groups
- 7 Securing Terminals
- 8 Warning Mode
- 9 Configuration
- Safeguard Attributes
- Configuring User Authentication
- Configuring Password Control
- Configuring Device Control
- Configuring Process Control
- Configuring Disk-File Control
- Configuring Safeguard Auditing
- Configuring a Default Command Interpreter
- Configuring Communication With $CMON
- Configuring Logon Dialog
- Configuring Exclusive Access at Safeguard Terminals
- Configuring Warning Mode
- Configuring Persistence
- Configuring Attributes for Node Specific Subjects in ACLs
- 10 Installation and Management
- Safeguard Components
- Process Considerations for the SMP and SAFECOM
- Safeguard Subsystem Management Commands
- General Installation Procedure
- Installing the Safeguard Software
- Starting the SMP
- Converting to the Safeguard Subsystem
- Updating the Safeguard Software
- Guidelines for Securing the Safeguard Subsystem
- Monitoring the Safeguard Subsystem
- A SAFECOM Command Syntax
- Index
Controlling User Access
Safeguard Administrator’s Manual—523317-013
2-18
Granting a User Temporary Access to Your System
Check the status of the SOFTWARE.GEORGE user authentication record with an
INFO USER command:
=INFO USER software.george, DETAIL
The general INFO USER report shows that the user's ability to access the system
expires at midnight on December 18, 2005.
The ALTER USER command can be used to change a USER-EXPIRES date. For
example, if the contract for SOFTWARE.GEORGE is extended one month, the
manager of the SOFTWARE group can change that user's USER-EXPIRES date with
this command:
=ALTER USER software.george, USER-EXPIRES Jan 19 2006
GROUP.USER USER-ID OWNER LAST-MODIFIED LAST-LOGON STATUS WARNING-MODE
SOFTWARE.GEORGE 4,21 4,255 27JUN05, 14:37 * NONE * THAWED OFF
ID = 1045
USER-EXPIRES = 19DEC05, 0:00
PASSWORD-EXPIRES = * NONE *
PASSWORD-MAY-CHANGE = * NONE *
PASSWORD-MUST-CHANGE EVERY = * NONE *
PASSWORD-EXPIRY-GRACE = * NONE *
LAST-LOGON = * NONE *
LAST-UNSUCESSFUL-ATTEMPT = * NONE *
LAST-MODIFIED = 27JUN05, 14:37
FROZEN/THAWED = THAWED
STATIC FAILED LOGON COUNT = 0
GUARDIAN DEFAULT SECURITY = OOOO
GUARDIAN DEFAULT VOLUME = $SYSTEM.NOSUBVOL
AUDIT-AUTHENTICATE-PASS = NONE AUDIT-MANAGE-PASS = NONE
AUDIT-AUTHENTICATE-FAIL = NONE AUDIT-MANAGE-FAIL = NONE
AUDIT-USER-ACTION-PASS = NONE
AUDIT-USER-ACTION-FAIL = NONE
TEXT-DESCRIPTION =
BINARY-DESCRIPTION-LENGTH = 0
CI-PROG = * NONE *
CI-LIB = * NONE *
CI-NAME = * NONE *
CI-SWAP = * NONE *
CI-CPU = * NONE *
CI-PRI = * NONE *
CI-PARAM-TEXT =
INITIAL-PROGTYPE = PROGRAM
INITIAL-PROGRAM =
INITIAL-DIRECTORY =
PRIMARY-GROUP = SOFTWARE
GROUP = SOFTWARE
SUBJECT DEFAULT-PROTECTION SECTION UNDEFINED!
SUBJECT OWNER-LIST SECTION UNDEFINED!