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
IDS_checkInstall fails with a kmtune error
IDS_checkInstall reports that a kmtune file write operation fails and the idds driver is not
configured:
# /opt/ids/bin/IDS_checkInstall
kmtune: Cannot write file -- /stand/.kmsystune_lock
WARNING: The idds driver is not configured into the
kernel.
□ If patch PHCO_24112 is not installed on your system, please contact HP Support.
IDS_genAdminKeys or IDS_genAgentCerts does not complete successfully
□ The normal completion is shown in the steps in “Setting Up HP-UX HIDS Secure
Communications” (page 29).
□ Check the messages in the error log file /var/opt/ids/certs.log for correctable errors.
□ Contact HP Support.
IDS_genAdminKeys or idsgui quits early
On occasion, apparently due to a swlist timeout, the IDS_genAdminKeys and idsgui
commands may quit early. (The swlist command is used to verify that the correct version of
Java is available.)
• The IDS_genAdminKeys command may quit before it finishes making the keys. The
symptom is that the final banner is not displayed. The banner is shown in Chapter 2:
“Configuring HP-UX HIDS” (page 29).
• The idsgui command may quit before it launches the System Manager. The symptom is
that the prompt returns and the following message is not displayed.
Starting the HP-UX HIDS System Manager in the
background
Please wait....
In either case, you can try running the command again.
The solution is to apply the latest Software Distributor (SD) Cumulative Patch. For 11i and 11i
version 1.6, install PHCO_25887 or a superseding patch, if any.
Large files in /var/opt/ids
□ The communication between idskerndsp and idscor uses a memory-mapped file, which
normally only exists (in the /var/opt/ids directory) when a surveillance schedule is
running. The files are named ids_n, where n is incremented from 1001 for each activated
schedule.
□ If idsagent has a problem, the files may not be deleted normally. If no schedule is running
on the agent, there should be no ids_n files. You can safely delete them with the rm
command.
220 Troubleshooting