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

5. Edit the System Manager script, as follows:
$ vi /opt/ids/bin/idsgui
6. Set the value of INTERFACE in idsgui to the following:
INTERFACE=127.0.0.1
7. Start the System Manager. For more information, see “Starting the HP-UX HIDS System
Manager” (page 49).
8. On the Host Manager screen, set up the administration system as an agent system, using
127.0.0.1 as its IP address. For more information, see “Adding a New Host Manually”
(page 84) and “Modifying a Host” (page 88).
Configuring Ports
When HP-UX HIDS is first installed on the administration and agent systems, the ports HP-UX
HIDS uses are configured into the /etc/services file on each system as follows:
hpidsadmin 2984/tcp #HP-UX Host IDS admin
hpidsagent 2985/tcp #HP-UX Host IDS agent
NOTE: Comments vary from configuration to configuration.
These are HP standard port numbers, registered with the Internet Assigned Number Authority
(IANA). If, for some reason you need to use different ports, you must change the numbers 2984
and 2985 in all /etc/services files on the administration system and all agent systems. If you
are working with firewalls or NIS systems, you must also make the changes as described in
“Working with NIS” and “Working with Firewalls”.
Working with NIS
If any system is using NIS, you must configure NIS to use the HP-UX HIDS communication
ports. To configure NIS to use the HP-UX HIDS communication ports, follow these steps:
1. Edit /etc/services on the NIS master server to add the two HP-UX HIDS ports described
in “Configuring Ports”.
2. Run /var/yp/ypmake on the NIS master server. For more information, see ypmake( 1M).
Working with Firewalls
If a firewall is positioned between the administration system and an agent system, enable the
ports that are used by HP-UX HIDS on the firewall. Check the values for hpidsadmin and
hpidsagent in the /etc/services file of the administration system. Configure the firewall
system to allow traffic to and from these ports. These values must be the same on all
administration, agent, and firewall systems. For more information, see “Configuring Ports”.
If you use IPFilter as your firewall, see “Using HP-UX HIDS with IPFilter and SecureShell”
(page 223) for useful configuration information for both IPFilter and SecureShell.
Enabling Multiple Agents
If you have more than about 20 agent systems, you may have to modify a kernel parameter and
a network parameter.
Enabling More than 23 Agents (Thread Limits)
You must ensure that the administration system provides enough threads per process to handle
the maximum number of agent systems you will monitor at one time. The thread value is specified
by the tunable kernel parameter max_thread_proc. You can compute its minimum value using
the following formula:
40 Configuring HP-UX HIDS