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

values of 23 seconds, 10 minutes, 1 hour and 23 seconds; the s component in the last line is
redundant, but can be used for clarity.
fail_interval | 23
warning_interval | 10m
fail_interval | 1h
warning_interval | 23s
NOTE: You cannot specify the time unit value in the Schedule Manager screen.
Type VII: Flags
The Type VII property value is an integer used to enable or disable a flag. A value of 1 means
enabled, and a value of 0 means disabled. For example, the following properties of the
Login/Logout template specify that the monitoring of logins is enabled, and the monitoring of
successful su commands is disabled:
monitor_login_flag | 1
monitor_su_flag | 0
Type VIII: Scalars
The Type VIII property value is a single integer. However, this value can be any integer. For
example, the following property of the Buffer Overflow template specifies that 500 is considered
an unusually long argument length when invoking a priviledged setuid program:
unusual_arg_len | 500
Type IX: Path Names / Integer Pairs
The Type IX property specifies pairs of path names and integers. In each pair, the two members
are separated by a comma and pairs are separated by a pipe. The path name is interpreted as
regular expressions and extended regular expressions. For more information on regular
expressions, see “UNIX Regular Expressions ” (page 114). The integer is interpreted to be of type
Type VI: Time Strings.
Currently, only the global alert aggregation tuples property is of this type. For more information,
see “Surveillance Schedule Text File” (page 198).
Type X: String Patterns
The Type X property value is a list of regular expression string patterns that are separated by
the pipe (|) character and that can be grouped using the ampersand (&) character. Type X
properties are similar to Type I properties. However, Type I properties are regular expressions
for specifying pathnames while Type X properties are regular expressions for specifying string
patterns in general. Type X property values must be enclosed using double quotes to denote the
start and end of the string pattern.
This property type is currently used only in the Log File Modification Template for
specifying log file entries to monitor or ignore.
NOTE: When specifying the template property value in the Schedule Manager window, enter
only string patterns enclosed in double quotes and the ampersand (&) character if grouping 2
or more string patterns.
For example, the following line specifies the Log File Monitoring template property to monitor
log file entries that contain either the string "file system full" or both the string "fail" and
"authentication":
watch | "file system full" | "fail" & "authentication"
For examples of regular expressions, see “UNIX Regular Expressions ” (page 114).
120 Templates and Alerts