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
user_pairs_to_ignore | root, daemon | 0, bin | root, 3 | 0, 4
In this example, an alert is not triggered if any of the following conditions are met:
- If the file owner’s name is root and the effective user ID of the modifying process corresponds
to the user name daemon.
- If the file owner’s user ID is 0 and the effective user ID of the modifying process corresponds
to the user name bin.
- If the file owner’s user ID corresponds to the user name root and the effective user ID of the
modifying process is 3.
- If the file owner’s user ID is 0 and the effective user ID of the modifying process is 4.
Type V: Network Triplets
Type V property values include network information triplets. The members of a triplet are as
follows:
• IP Address: An IP address. For IPv4, the address must be in standard dot notation; for IPv6,
in colon notation.
• Network Mask: The network mask value qualifies the value in the IP address field to an
individual host address or a network address. The network mask follows the notational
requirements for IP addresses.
Network mask is specified in dotted decimal notation for IPv4 addresses and in prefix
notation for IPv6 addresses. In case of IPv4 addresses, a value of 255.255.255.255 means the
value in the IP address field is a host address, and in case of IPv6 addresses a prefix of /128
means the IP address field is a host address. For example:
ip filters | 2001:DB8::, /32, 0 |
Where,
2001:DB8:: network address
/32 network mask for network address in prefix notation
0 no alerts are generated for hosts in specified network
• Severity Code: An integer representing a severity level (0=no alert, 1 = critical, 2 = severe,
3 = moderate), where a severity level of 0 specifies that no alert is generated for a matching
{IP address, Network Mask, 0} triplet.
The following template configuration illustrates a Type V property value:
ip_filters | 192.168.2.0, 255.255.255.0, 0 |
Where:
192.168.2.0 network address
255.255.255.0 network mask for a network address
0 no alerts are generated for hosts in the specified network
Type VI: Time Strings
The time strings property represents time intervals. Each time string has the following syntax:
integer[units]
The integer component is a positive integer representing a time interval. The units component,
when present, indicates the time units the integer is expressed in. The following units are
supported:
s
Seconds
m
Minutes
h
Hours
d
Days
w
Weeks
When the unit component is not present, the integer component is assumed to be in seconds.
For example, the following lines in the template configuration file contain time strings representing
Template Property Types 119