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. On the System Manager screen, in the Monitored Hosts list, select the hosts status you want
to update.
2. Select one of the following options:
• Click the Status button.
• Choose the Actions > Status Poll menu item.
• Press Shift+F7.
• Right-click in the Monitored Hosts area and select Status Poll from the menu.
The System Manager begins polling the selected hosts and returns an updated value in the
Status field. These values are described in Table 4-2 (page 50).
If No Agent Available is shown for a host, the agent may not be not running, or is still
initializing. Recheck the status later. If the agent status does not change, then the following
problems may exist:
• The agent may not be running on the host. For more information, see “Starting HP-UX
HIDS Agents” (page 51).
• The agent host may be down.
• The administration and agent host certificates may not be properly configured. For
more information, see “Setting Up HP-UX HIDS Secure Communications” (page 29).
• The network may be congested.
• The network link to the host may be unavailable.
See also Appendix F (page 203).
Resynchronizing Agent Hosts
The HP-UX HIDS agent program can continue to detect alerts when the HP-UX HIDS System
Manager is not running. During this period, as each agent detects intrusions, it records them in
a log file on the agent host. When you restart the HP-UX HIDS System Manager, the following
events occur:
1. The System Manager locates its own log files for each agent host in the Monitored Host list.
2. If the Automatic Startup Status Poll field is enabled, the monitored hosts are polled for their
status. If the status is either Scheduled or Running, the hosts subsequent alerts and errors
are added to the System Manager log files. For more information, see “General Preferences”
(page 105),
3. If Automatic Startup Alert Resynchronization is enabled, all the alerts in the agent’s log file
that are not updated in the System Manager alert log file are transferred to the System
Manager. If the alert log file for a particular agent is empty, then all alerts are transferred to
the System Manager. For more information, see “General Preferences” (page 105).
TIP: To avoid reloading deleted alerts, retain only the most recent alert message.
The error log files are not resynchronized.
If the Automatic Startup Status Poll field is disabled, you must poll the status of the agent hosts
before you can resynchronize them. See “Getting the Status of Agent Hosts” (page 51).
If Automatic Startup Alert Resynchronization is disabled, use the following procedure to
synchronize the alerts.
1. On the System Manager screen, in the Monitored Hosts list, select the hosts you want to
resynchronize. The status of these hosts must be Available, Scheduled, or Running.
52 Using the System Manager Screen