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

monitors a user-specified set of regular files for successful attempts to open a file with write or
truncate permission, to delete the file, to rename the file, or to truncate the file.
This template does not monitor changes in file ownership or permissions. The template also does
not monitor for the creation of a new file. Finally, this template does not determine that a file’s
contents were changed, only that a change might have been made. It does not watch the content
of the files, only that a file was opened with permission other than append. Instead of monitoring
write(2) calls that modify files, successful opens to write to the file to provide early detection of
processes that might potentially modify critical files by some means other than appending.
How this template is configured
Table A-11 lists the configurable properties this template supports.
Table A-12 Template Properties
Default ValueTypeName
^/var/adm/btmp$ | ^/var/adm/wtmp$ |
^/var/adm/messages$ | ^/var/adm/syslog/mail log $ |
^/var/adm/syslog/sysloġlog$ | ^/var/adm/pacct$ |
^/var/adm/sulog$
I
pathnames_to_watch
<empty>I
pathnames_to_not_watch
<empty>II
pathnames_X
<empty>II
programs_X
Properties
A brief description about the configurable properties are listed below:
pathnames_to_watch
Path names of files to be monitored for modification other
than appending.
pathnames_to_not_watch
Path names of files that can be safely ignored for
modification, regardless of which program modifies them.
pathnames_X, programs_X
Use these properties to filter out alerts generated when a
particular program modifies a particular file other than
appending. See “Type II: Path Names/Programs Pairs”
(page 116) for a detailed description of these property pairs.
Alerts generated by this template
Append-Only File Being Modified
Table A-13 lists the alert properties this template generates and forwards to a response program
when a file is modified in a way other than being appended to.
Table A-13 Append-Only File Being Modified Alert Properties
DescriptionAlert Value/FormatAlert Field TypeAlert FieldResponse
Program
Argument
Unique code assigned to
template
3IntegerTemplate codeargv[1]
Template version<version>IntegerVersionargv[2]
Alert Severity2IntegerSeverityargv[3]
UTC time in number of
seconds since the epoch
when file was modified
<secs>IntegerUTC timeargv[4]
Changes to Log File Template 135