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

Correlator Process Configuration
The correlator section is bracketed by the [Correlator] ... [END] keywords. Only the parameters
in Table E-2 may be edited.
Table D-2 Correlator Configuration Variables
Default ValueName
““
CMDLINEARGS
“not set”
AGGREGATION
CMDLINEARGS Used to pass command line options to the idscor process. To measure the
average system call event rate on a host for the system calls monitored by HIDS, while running
a particular set of detection templates, set the value to -t <number> where <number> is the
number of events over which the rate is calculated.
For example, -t 100000 calculates the event rate for every 100,000 events. For more information,
see the “HP-UX HIDS Sizing and Tuning Primer”.
After setting the -t option with a value of 100,000, restart the schedule and look for lines like the
following in the agent’s error log:
Event# 100000: 2799.17 events/sec
Event# 200000: 1742.62 events/sec
Event# 300000: 1395.02 events/sec
The agent’s error log is defined by the IDS_ERRORFILE configuration variable described in
Table D-1 (page 192) (the default is /var/opt/ids/error.log).
If event rates do not start appearing in the agent’s error log after about a minute, the rate of
events generated on the system is probably low, so decrease the value of the -t argument to 10,000
or 1,000 in order to calculate the rate more often (that is, for every 10,000 or 1,000 system call
events instead of for every 100,000).
On the other hand, if there are continous large spikes in the event rate, the event rate is not being
calculated over a large enough sample. For example, the following output shows that the event
rate spikes constantly when calculated for every 1,000 events:
Event# 1000: 155933.27 events/sec
Event# 2000: 199.40 events/sec
Event# 3000: 152975.38 events/sec
Event# 4000: 199.41 events/sec
Event# 5000: 199.42 events/sec
Event# 6000: 156421.08 events/sec
Event# 7000: 199.38 events/sec
Event# 8000: 157505.12 events/sec
Event# 9000: 199.40 events/sec
Event# 10000: 141723.36 events/sec
The spikes are due to idscor receiving bursts of events and is probably a function of when
HIDS processes such as idskerndsp or idscor are scheduled to run.
For this example, using a sample rate of 10,000 (that is, -t 10000) results in a stable average
reading of the actual event rate:
Event# 10000: 331.02 events/sec
Event# 20000: 331.84 events/sec
NOTE: No intrusion detection is performed when the -t option is set. Make sure to remove the
-t option from CMDLINEARGS when deploying HIDS.
AGGREGATION
Used to override the schedule alert aggregation property value that specifies whether alert
aggregation is enabled or disabled. Set to 0 to disable alert aggregation. Set to 1 to enable alert
aggregation.
Correlator Process Configuration 193