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 A-24 Successful su Detected Alert Properties (continued)
DescriptionAlert Value/FormatAlert Field TypeAlert FieldResponse
Program
Argument
Detailed alert
description
User <username_from> switched to
user <username_to> on tty <tty>
StringDetailsargv[8]
The event that triggered
the alert.
Switch-user (su)StringEventargv[9]
Indicates an su alert
versus a login/logout
alert
2IntegerFlagargv[10]
The tty from which a
successful su attempt
was made
<tty>
StringDeviceargv[11]
The name of the user
attempting to use the su
command
<username>
StringFromargv[12]
The target user of the su
command
<username>
StringToargv[13]
Limitations
The Login/Logout template has the following limitations:
• The template only detects logins and logouts that are logged to wtmp:
— The template does not detect successful secure ftp (sftp) logins and logouts because
the ssh daemon logs successful sftp logins and logouts using syslog(3C) instead of
logging them to wtmps on HP–UX 11i v2 and HP-UX 11i v3.
— The template does not detect secure shell (ssh) logins and logouts by ssh daemons that
do not log successful ssh logins and logouts to wtmps on HP–UX 11i v2 and HP-UX 11i
v3. To enable Secure Shell to log failed logins and logouts to wtmp(s) or btmp(s),
you must set the permissions of the wtmp(s) or btmp(s) file to 600.
• Because the login name (ut_user in a utmp structure) is not available for a logout event,
the template retrieves the login name from the wtmp log. If the log has been cleared, the
template creates a logout alert that does not contain the user name, only the device on which
the logout occurred.
• The host address filtering provided by this template is vulnerable to IP spoofing.
Repeated Failed Logins Template
The vulnerability addressed by this template
An attacker can gain access to a system by repeatedly attempting to guess the password of an
account.
How this template addresses the vulnerability
The Repeated Failed Login template monitors for repeated failed attempts to log in to the system.
Specifically, this template monitors btmps on HP-UX 11i v2 and HP-UX 11i v3 for a given number
of failed login attempts within a specified time span.
• Failed remote logins
• Failed ftp logins (for HP-UX 11i v2 and HP-UX 11i v3 only)
It monitors for the following events:
If an unusual number of failed attempts occur, this template generates an alert.
Repeated Failed Logins Template 151