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

D The Agent Configuration File
This appendix describes the user-configurable options that can be modified in the HP-UX HIDS
agent configuration file, which is located in /etc/opt/ids/ids.cf. This appendix addresses
the following topics:
• “The Agent Configuration File” (page 191)
• “Forcing Active Agent to Reread Configuration File” (page 191)
• “Log File Rotation” (page 191)
• “Global Configuration” (page 192)
• “Data Source Process Configuration” (page 194)
• “Remote Communication Configuration” (page 195)
The Agent Configuration File
The HP-UX HIDS agent requires a configuration file named ids.cf, located in the directory
/etc/opt/ids. See ids.cf(4) for details. There is usually no need to modify the configuration
file; any modifications should be made with caution after reading the ids.cf man page. However,
it may be useful to understand some of the parameters and settings to aid debugging and
installation.
The configuration file contains four sections:
1. Global Configuration: Parameters that define the overall product structure. The logging and
interface parameters may be edited by the administrator. See “Global Configuration”
(page 192).
2. Correlator Configuration: Parameters related to the correlator. A parameter can be configured
to take measurements of the system call event rate. See “Correlator Process Configuration”
(page 193).
3. Data Source Process (DSP) Configuration: A section per-DSP that defines the system files
to monitor and level of kernel blocking. See “Data Source Process Configuration” (page 194).
4. Remote Communication Section: Parameters required for network communications. See
“Remote Communication Configuration” (page 195).
Forcing Active Agent to Reread Configuration File
If you make changes to the agent configuration file located in ids.cf, you must instruct the
agent process idsagent to reread the configuration information. On the system that is running
the agent:
1. Become user ids:
$ su - ids
2. Send the hangup signal to the agent process ID:
$ kill -HUP $(cat /var/opt/ids/idsagent.pid)
The idsagent process rereads the configuration file and reactivates the current surveillance
schedule, if any.
Log File Rotation
Both the IDS_ERRORFILE file and the IDS_ALERTFILE file, described in “Global Configuration”
(page 192), are designed to support log rotation. If the file names are changed on the system while
the HP-UX HIDS agent software is running, the agent software will recreate the files as defined
in Table D-1 and continue to log to the newly created files. Log rotation permits periodic archiving
of alerts or errors.
To rotate a log file, use the mv command. For example:
% mv /var/opt/ids/alert.log /home/ids/alert.log_Jan_06
The Agent Configuration File 191