HP-UX Host Intrusion Detection System Version 4.3 administrator guide
Table Of Contents
- HP-UX Host Intrusion Detection System Version 4.3 administrator guide
- Table of Contents
- About This Document
- 1 Introduction
- 2 Configuring HP-UX HIDS
- 3 Getting Started with HP-UX HIDS
- 4 Using the System Manager Screen
- Starting the HP-UX HIDS System Manager
- Stopping the HP-UX HIDS System Manager
- System Manager Components
- Starting HP-UX HIDS Agents
- Getting the Status of Agent Hosts
- Resynchronizing Agent Hosts
- Activating Schedules on Agent Hosts
- Stopping Schedules on Agent Hosts
- Halting HP-UX HIDS Agents
- Accessing Other Screens
- 5 Using the Schedule Manager Screen
- The Schedule Manager
- Configuring Surveillance Schedules
- Configuring Surveillance Groups
- Configuring Detection Templates
- Setting Surveillance Schedule Timetables
- Configuring Alert Aggregation
- Configuring Monitor Failed Attempts
- Configuring Duplicate Alert Suppression
- Viewing Surveillance Schedule Details
- Predefined Surveillance Schedules and Groups
- 6 Using the Host Manager Screen
- 7 Using the Network Node Screen
- 8 Using the Preferences Screen
- A Templates and Alerts
- Alert Summary
- UNIX Regular Expressions
- Limitations
- Template Property Types
- Buffer Overflow Template
- Race Condition Template
- Modification of files/directories Template
- Changes to Log File Template
- Creation and Modification of setuid/setgid File Template
- Creation of World-Writable File Template
- Modification of Another User’s File Template
- Login/Logout Template
- Repeated Failed Logins Template
- Repeated Failed su Commands Template
- Log File Monitoring Template
- B Automated Response for Alerts
- C Tuning Schedules and Generating Alert Reports
- D The Agent Configuration File
- E The Surveillance Schedule Text File
- F Error Messages
- G Troubleshooting
- Troubleshooting
- Agent and System Manager cannot communicate with each other
- Agent complains that idds has not been enabled, yet lsdev shows /dev/idds is present
- Agent does not start on system boot
- Agent halts abnormally, leaving ids_* files and message queues
- Agent host appears to hang and/or you see message disk full
- Agent needs further troubleshooting
- Agent does not start after installation
- Agents appear to be stuck in polling status
- Agent displays error if hostname to IP mapping is not registered in name service
- Aggregated alerts targets or details field are truncated and the same aggregated alert has several entries logged in the IDS_ALERTFILE
- Alert date/time sort seems inconsistent
- Alerts are not being displayed in the alert browser
- Buffer overflow triggers false positives
- Duplicate alerts appear in System Manager
- Getting several aggregated alerts for the same process
- GUI runs out of memory after receiving around 19,000 alerts
- The idsadmin Command needs installed agent certificates
- The idsadmin Command notifies of bad certificate when pinging a remote agent
- IDS_checkInstall fails with a kmtune error
- IDS_genAdminKeys or IDS_genAgentCerts does not complete successfully
- IDS_genAdminKeys or idsgui quits early
- Large files in /var/opt/ids
- Log files are filling up
- No Agent Available
- Normal operation of an application generates heavy volume of alerts
- Reflection X rlogin produces multiple login and logout alerts
- Schedule Manager timetable screen appears to hang
- SSH does not perform a clean exit after idsagent is started
- System Manager appears to hang
- System Manager does not let you save files to specific directories
- System Manager does not start after idsgui is started
- System Manager starts with no borders or title bar in X client programs on Windows
- System Manager times out on agent functions such as Activate and Status Poll
- UNKNOWN program and arguments in certain alert messages
- Using HP-UX HIDS with IPFilter and SecureShell
- Unable to Generate Administrator Keys and Agent Certificates on PA–RISC 1.1 Systems
- Troubleshooting
- H HP Software License

NOTE: See Table B-1 (page 161) for the definition of additional arguments that can be used to
access specific alert information (for example, pid and ppid) without having to parse the string
alert fields above.
Limitations
The Changes to Log File template has the following limitation:
• The template cannot distinguish whether a file is created or truncated when creat(2) is
invoked.
Creation and Modification of setuid/setgid File Template
The vulnerability addressed by this template
The concept of setuid and setgid files means that if you have the setuid or setgid bit
turned on on a file, anybody executing that executable (file) inherits the permissions of the
individual or group that owns the file.
One of the frequent back doors that an intruder installs on a system is the creation of a copy of
the /bin/sh program that is setuid root. This file enables any command to be executed as a
superuser.
How this template addresses the vulnerability
The setuid/setgid template detects the creation and modification of files with setuid and
setgid privileges by monitoring the following:
• Modifying file permissions to enable the setuid or/and setgid bit on a file owned by a
privileged user or privileged group.
• Changing the owner of a setuid or a setgid file to be owned by a privileged user or
privileged group.
• Creating or modifying a file that has the setuid or setgid bit set, and that is owned by a
privileged user or privileged group.
By detecting the creation and modification of a setuid or setgid file as soon as it occurs, the
setuid/setgid template can provide a timely security report to an administrator regarding a
potential security intrusion. There are no known mechanisms in existence for the HP-UX operating
system that can provide a near real-time report of the creation or modification of setuid and
setgid files.
How this template is configured
Table A-15 lists the configurable properties the setuid/setgid template supports.
Table A-15 Setuid File Template Properties
Default ValueTypeName
0 | 1| 2 | 3 | 4 | 5 | 9 | 11III
priv_user_list
0 | 1 | 2 | 3 | 4 | 5 | 6 | 10 | 11III
priv_group_list
<empty>II
pathnames_X
<empty>II
programs_X
Properties
The configurable properties are listed as follows:
priv_user_list A list of system-level user IDs or user names.
This list contains those users who have elevated access to
the system. Removing any of these users means that the
138 Templates and Alerts