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

1. Determine if the agent system is multihomed. Use the nslookup command to determine
which IP address corresponds to the host name of the system. If more than one IP address
is returned by nslookup, your system is multihomed. If only one IP address is returned,
your system is not multihomed.
NOTE: No modifications are needed for a system that has only one IP address.
2. Select the interface on which you want the HP-UX HIDS agent to communicate with the
administration system.
The choice of address depends on your network topology. The address can be an IP address
in IPv4 dotted decimal notation, (for example, 1.2.3.4) or an IP address in IPv6 colon notation,
(for example, 2001:db8::100) or a host name that resolves to a unique address on the system
where the agent resides.
It is essential that a network route exists between the HP-UX HIDS administration system
and the HP-UX HIDS agent system. On the administration system, enter the
/usr/sbin/ping command or the /usr/contrib/bin/traceroute command to verify
that network traffic can flow between the systems. HP recommends that you select the
address with the shortest transmission speed or fewer hops (exposure).
Later, you must enter the IP address or host name you selected into a configuration screen
in the HP-UX HIDS System Manager. For more information see Chapter 6 (page 83).
NOTE: If the HP-UX HIDS agent system uses an IPv4 address for communication, the
administration system must also use an IPv4 address. This is also applicable for the IPv6
address.
3. On the multihomed agent host, log in as ids, as follows:
$su - ids
4. Edit the configuration file; for example:
$ vi /etc/opt/ids/ids.cf
5. Locate the IDS_LISTEN_IFACE parameter in the Globals section. For more information,
see Appendix D (page 191)
6. Remove the comment symbol (#) from the start of the line, and place the interface address
selected in step 2 after the parameter name. For example, change:
# IDS_LISTEN_IFACE <insert your hostname/IP addr here>
to
IDS_LISTEN_IFACE 192.0.2.4
or
IDS_LISTEN_IFACE 2001:db8::100
7. Save the modified file.
8. If the agent is running, force the agent to reread the configuration file by sending it a HUP
signal. For more information, see “Forcing Active Agent to Reread Configuration File”
(page 191).
If you enter an invalid IDS_LISTEN_IFACE parameter, the HP-UX HIDS software agent reports
an error when you attempt to start it. Repeat steps 1to 8 to correct the setting of
IDS_LISTEN_IFACE, and restart the HP-UX HIDS agent.
Example
The following example illustrates how to configure a multihomed agent system:
36 Configuring HP-UX HIDS