MTU Library Catalogue

Syndetics cover image
Image from Syndetics

Solaris security / Peter H. Gregory.

By: Gregory, Peter H.
Material type: materialTypeLabelBookPublisher: Upper Saddle River, N.J. : Sun Microsystems Press ; Prentice Hall, 2000Description: xlii, 291 p. : ill ; 24 cm. + pbk.ISBN: 0130960535.Subject(s): Solaris (Computer file) | Computer securityDDC classification: 005.8
Contents:
Part One: Introduction -- The Security Problem -- The Security Paradigm -- Part Two: The Standalone System -- The PROM, Openboot and physical security -- The Filesystem -- User accounts and environments -- System startup and shutdown -- cron and at -- System Logs -- Part Three: The Network-Connected system -- Network interfaces and services -- Network/System Architecture -- Electronic Mail -- Printing -- Network Access Control -- Name Services -- NFS and the Automounter -- Part Four: Disaster and Recovery -- System Recovery Preparation.
Holdings
Item type Current library Call number Copy number Status Barcode
General lending MTU Bishopstown Library Lending 005.8 (Browse shelf(Opens below)) 1 Available 00071019
Total holds: 0

Enhanced descriptions from Syndetics:

At last, a security book just for Solaris and UNIX(r) system administrators. Learn the specifics for making your system secure, whether its an organization-wide network or a standalone workstation. Expert author Peter Gregory has managed security for everything from top-secret corporate research facilities to casinos. Take advantage of his experience to build a secure, reliable system of your own. Solaris Security looks at the physical, logical, and human factors that affect security, including: * PROMs, physical security, bootpaths, permissions, auditing tools, system logs, passwords, and more * Secure network interfaces and services for remote and Internet access, intrusion detection, access control, email, and printing * Enhanced security for NIS, NIS+, DNS, and NFS A special section shows you how to plan for the inevitable disasters so you can recover your data quickly and accurately without compromising security. References to books, journals, and online resources will help you keep up with the latest innovations. Every chapter opens with a checklist of key topics and their significance, so you can quickly find the information you need. Whether you are a security manager, Info

Includes bibliographical references (pages 249-254) and index.

Part One: Introduction -- The Security Problem -- The Security Paradigm -- Part Two: The Standalone System -- The PROM, Openboot and physical security -- The Filesystem -- User accounts and environments -- System startup and shutdown -- cron and at -- System Logs -- Part Three: The Network-Connected system -- Network interfaces and services -- Network/System Architecture -- Electronic Mail -- Printing -- Network Access Control -- Name Services -- NFS and the Automounter -- Part Four: Disaster and Recovery -- System Recovery Preparation.

Table of contents provided by Syndetics

  • I Introduction
  • 1 The Security Problem
  • Causes of Security Weaknesses
  • Growth of Network Connectivity
  • Software Vulnerabilities
  • Employees and Contractors
  • Motivated and Resourceful Hackers
  • Site Policies
  • 2 The Security Paradigm
  • Principle 1 The Hacker Who Breaks into Your System Will Probably Be Someone You Know
  • Principle 2 Trust No One, or Be Careful About Whom You Are Required to Trust
  • Principle 2a Dont Trust Yourself, or Verify Everything You Do
  • Principle 3 Make Would-Be Intruders Believe They Will Be Caught
  • Principle 4 Protect in Layers. Principle
  • 5 While Planning Your Security Strategy, Presume the Complete Failure of Any Single Security Layer
  • Principle 6 Make Security a Part of the Initial Design
  • Principle 7 Disable Unneeded Services, Packages, and Features
  • Principle 8 Before Connecting, Understand and Secure
  • Principle 9 Prepare for the Worst. The Nine Principles: A Way of Life
  • II The Standalone System
  • 3 The PROM, OpenBoot, and Physical Security
  • What Is the PROM? What Is OpenBoot? Why Users Must Be Kept Out of OpenBoot
  • Protecting OpenBoot by Setting Security Parameters
  • Procedures for Changing OpenBoot Security Levels
  • All Passwords Lost-Partial Recovery Procedure
  • Boot Device Recommendations
  • Change the OpenBoot Banner
  • Recover a Lost Root Password
  • Physical Security Considerations
  • Theft and Access Prevention
  • Audit PROMs
  • OpenBoot Passwords
  • CD-ROM Drives
  • Backup Media
  • OS Release Media
  • Where to Go for Additional Information
  • 4 The Filesystem
  • What Is the Filesystem? Some Applications Require Open Permissions
  • Understanding File and Directory Permissions
  • Who: User, Group, and Other
  • Permission Summary: Read, Write, Execute, SetUID, SetGID, Sticky Bit
  • Putting It All Together: The Who and the What
  • How to View File and Directory Permissions
  • Permissions: Numeric Form
  • Setting File and Directory Permissions-Numeric
  • Setting File and Directory Permissions-Symbolic
  • umask and How It Works
  • Default File Permissions and umask
  • Root User umask
  • Default Directory Permissions and umask
  • How to Find Files with Specific Permission Settings
  • System Device Access Permissions
  • Filesystem Auditing Tools
  • ASET
  • COPS
  • Tiger
  • Tripwire
  • lsof (list open files)
  • Other Security Tools and Techniques
  • Check /etc Permissions
  • Ensure Proper utmp and utmpx Permissions
  • Use Fix-modes Tool to Enhance Security
  • Use the fuser Command
  • Use the ls Command to Show Hidden Files and Hidden Characters in Filenames
  • Alias the rm Command. Randomize Filesystem Inode Numbers with fsirand
  • Filesystem Quotas
  • Filesystem Access Control Lists
  • Where to Go for Additional Information
  • 5 User Accounts and Environments
  • Introduction
  • User Account Security
  • The Root Account
  • Other Administrative Accounts and Groups
  • User Accounts
  • When Users Need Root Privileges
  • PATH and LD_LIBRARY_PATH
  • The Password, Shadow, and Group Files
  • Password File
  • Shadow File
  • Password Security
  • UNIX Groups
  • The /etc/default/passwd File
  • Root Access
  • Direct Root Login
  • The su Command
  • Shell and Application Security
  • Forced Application Startup
  • Include System Name in Root Shell Prompt
  • Restricted Shell
  • Default Login Environment
  • Writing Directly to the Console
  • Program Buffer Overflow
  • Additional Process Information
  • X-Windows Security
  • X-Windows Screen Lock, Manual
  • X-Windows Screen Lock, Auto
  • X-Windows Display Permissions
  • Auditing Tools
  • COPS
  • Crack
  • Where to Go for Additional Information
  • 6 System Startup and Shutdown
  • System Run Levels
  • Determining Current Run Level
  • System Startup
  • PROM. init
  • Multiuser Mode
  • The rc Mechanism
  • System Shutdown. init. uadmin
  • More Information on rc Files
  • An Example rc File Examined
  • Auditing Startup and Shutdown Mechanisms
  • COPS
  • Tripwire
  • Modifying Startup and Shutdown Mechanisms
  • Adding Startup and Shutdown Scripts
  • Changing Startup and Shutdown Scripts
  • Disabling Startup and Shutdown Scripts
  • More on Linked Startup Files
  • Where to Go for Additional Information
  • 7 cron and at
  • cron
  • What is cron? How cron Works
  • How cron Is Configured
  • cron User Configuration
  • User Access to cron System. at
  • What Is at? How at Works
  • User Access to at System
  • Common Mistakes to Avoid
  • Failure to Adequately Conceal Programs Launched by cron
  • Leaving crontab Files Lying Around for All to See
  • Unsecure PATH Elements in Scripts Launched by cron
  • Indeterminate PATH Elements in Scripts Launched by cron
  • Use of stdin and stdout in cron and at Jobs
  • Auditing Tools
  • Tripwire. COPS
  • Where to Go for Additional Information
  • 8 System Logs
  • What Is a System Log
  • syslog. syslog Facilities and Severity Levels
  • syslog Message Classification Notation
  • syslog Configuration
  • Debugging syslog. loginlog. sulog
  • Last Log
  • Volume Manager Log
  • Install Log
  • sysidtool Log
  • Tools to Help with Logging
  • Logcheck
  • Where to Go for Additional Information
  • III The Network-Connected System
  • 9 Network Interfaces and Services
  • Networks
  • Network Interfaces
  • Network Interface Characteristics
  • Network Interface Configuration. ifconfig. ndd
  • Turn Off IP Forwarding with /etc/notrouter. netstat. /etc/inet/hosts. /etc/inet/netmasks. /etc/defaultrouter. /etc/nodename. /etc/hostname.interface
  • How Adaptors Are Configured. Promiscuous Mode
  • Network Services
  • Unnecessary Services
  • Network Service Numbers
  • Network Service Configuration
  • How Network Services Are Started
  • Daemon Network Services Not Started with inetd
  • Routing
  • Adding Static Routes
  • Adding Dynamic Routes
  • Using snoop
  • Where to Go for Additional Information
  • 10 Network/System Architecture
  • What Is an Architecture? Simple vs Complex Architectures
  • Architecture Principles
  • Principle
  • 1 Minimize the Number of Failure Points (or Shorten the Critical Path)
  • Principle
  • 2 Keep Services Close to Those Being Served
  • Principle
  • 3 Vertically Align Services with Their Applications
  • Principle
  • 4 Prepare for Increasing Network Partitioning
  • 11 Electronic Mail
  • Overview of E-Mail
  • Transport Agent
  • Delivery Agent
  • User Agent
  • Types of E-Mail Security Weaknesses
  • Auth (or Identd) Protocol
  • Message Brokering
  • Message Source Routing
  • Privacy
  • Authenticity
  • Mitigating E-Mail Security Weaknesses
  • Run Sendmail Only on Mail Servers
  • Disconnect Inside Mail Server(s) from the Internet
  • Prevent Message Source Routing
  • Implement Mail Encryption and Digital Signatures
  • Replace Sendmail
  • Remove Unnecessary E-Mail Aliases
  • Implement Smrsh
  • Implement ForwardPath
  • Where to Go for Additional Information
  • 12 Printing
  • Printing Architectures
  • Print Subsystem Directories
  • Auditing Print Subsystem Directories
  • Local Printing
  • Local Print Devices
  • How to Determine Which Device a Specific Printer Uses
  • Print Device Permissions
  • Auditing Print Device Permissions
  • Restricting Access to Printers and Print Servers
  • Direct Access to Network Printers
  • Where to Go for Additional Information
  • 13 Network Access Control
  • Network Access Control Principles
  • Unnecessary Network Access Points Are Security Risks
  • Unguarded Network Access Points Are Security Risks
  • Necessary and Unnecessary Services
  • How to Disable Unnecessary Services
  • Strengthening Network Access Control. inetd Connection Tracing
  • TCP Wrappers
  • Public-Domain rpcbind. .rhosts File-Gateway to the r-Commands. /etc/hosts.equiv File. Auditing .rhosts and hosts.equiv Files 170 Secure Replacement for telnet, rsh, and rlogin. ftp. tftp. X-Windows Is Unsecure. Firewalls. Testing System Accessibility. Satan. ISS. Intrusion Detection. Syn. Klaxon. Courtney. Tocsin. Gabriel. Intrusion Detection: Staying Current
  • Authentication
  • System Authentication
  • DES (Diffie-Hellma

Author notes provided by Syndetics

Peter H. Gregory is Infrastructure Group Manager for a major telecommunications service provider. He developed and implemented system and network security policies for its research facilities, where he has performed the roles of UNIX system administrator, network engineer, Webmaster and network software developer. Before that, he was lead software engineer for a security product developed for use in large casinos.