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

Table B-8 Additional Arguments Passed to Response Programs While Generating Aggregated
Alerts (continued)
DescriptionAlert Value/FormatAlert Field TypeAlert Field
Response Program
Argument
Full hostname of the
remote host from
which attacker logged
in. Set to localhost
if the local host or the
empty string is not
known.
<hostname>
StringFull hostname of
remote host
argv [27]
The IP address of the
remote host from
which the attacker
logged in. Set to
empty string if not
known.
<IP address>
StringIP address of the
remote host
argv [28]
Table B-9 Environment Variables Set for Response Programs
DescriptionValueVariable
Home directory
/opt/idsHOME
Default installation location
/opt/idsIDS_BASE
Configuration file directory
/etc/opt/idsIDS_ETC
Temporary file location
/var/opt/idsIDS_VAR
Tab, newline: separator string
t nIFS
Library path
<empty>LD_PRELOAD
Program path
/usr/bin:/sbin:/usr/sbinPATH
Shell path name
/usr/bin/shSHELL
Terminal type
unknownTERM
Programming Guidelines
This section provide guidelines for writing response scripts.
Perl Versus Shell Response Scripts
Perl is not privileged. However, when a Perl script is run by a privileged user (as it often is), care
must be taken to ensure that the script is secure.
It is far easier to write an insecure script in Perl as compared to a shell (POSIX, Korn, C). This is
similar to the problems with the str* functions. The functions themselves have no security
issues when properly used; however, their usage is almost always insecure, and it is better to
avoid them altogether. Perl, similarly, makes it very easy to write bad scripts when compared
to programming with a shell.
As an example of problems with Perl, consider the Perl statement open INPUT, $FILE when
$FILE is an input from the user that can potentially contain ill-formed data such as
>/etc/passwd. A code reader can assume the $FILE is being opened for read, whereas the
statement opens >/etc/passwd for write, and truncates the file.
The taint check option of Perl, perl -T, is a substitute for a shell in most cases.
Use a current version of Perl. Older versions have known vulnerabilities.
166 Automated Response for Alerts