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
against denial-of- service attacks. Despite all the advantages of encryption, it is only part of an
overall security solution.
Security Auditing Tools
A security auditing tool probes systems and networks for potential vulnerabilities that attackers
can exploit, generates a report identifying holes and recommends fixes. Whenever the system
administrator finds the holes, he or she must quickly patch them before they are exploited. If a
security audit tool used is executed or run regularly, it is a valuable tool to handle security threats
or attacks.
Attacks can occur at any point in the day; an attacker can penetrate a system, cover up the tracks,
and install a variety of ways to re-enter the system easily and quickly. Running auditing tools
every hour gives attackers a good opportunity to exploit your system, before you ever detect
them. It is obvious that if some form of continuously running security audit tool is available, it
is easier to monitor systems and make them more secure. An intrusion detection system provides
this type of security.
Intrusion Detection Technology
Intrusion detection can be summarized quite simply: after you have erected the barbed wire
fence, an intrusion detection system is like adding closed circuit TV cameras so that security
guards can monitor the facilities to forestall an attack.
Intrusion detection detects illegal and improper use of computing resources by unauthorized
people, before such misuse results in excessive damage. This detection system constantly monitors
critical systems and data to protect them from attacks.
An intrusion detection system (IDS) monitors user and system activity to detect patterns of
misuse that can correspond to security violations. Monitoring is automatic and constant on all
the systems on which the IDS is deployed. It imposes a low overhead on the systems and network,
so as not to disrupt your business activities. In addition, an IDS can monitor a server machine,
a whole network, or even an application (such as a database or web server).
Before attacking your systems, an attacker needs to identify potential vulnerabilities that can be
exploited to subvert your system’s security. A vulnerability is a feature of the implementation,
or operation of a computer system or network that leaves it open to subversion by an unauthorized
(or authorized) user. Having identified a vulnerability to exploit, the attacker then creates an
attack script, which is often just a shell script or simple program that performs a series of fixed
steps to exploit the vulnerability. Often the script that the attacker needs has already been written
and is available on a website, in which case the attacker’s job is much easier.
Despite the multitude of attacks that are known and reported, there can be small variations on
a theme. In several situations, attackers can use shell scripts used in previous attacks. What
follows is usually a flood of attacks that exhibit common patterns and follow similar steps. Given
a specific attack, you can codify it to express it in terms that an IDS can use. HP-UX HIDS uses
the concept of a detection template to express some fundamental aspect of an attack that makes
it different from legitimate behavior, while permitting detection.
The amount of information that flows through a typical corporate intranet and the level of activity
on most corporate servers make it impossible for any one person to continually monitor them
manually. Traditional network management and system monitoring tools do not address the
issue of helping to ensure that systems are not misused and abused. Nor can they help detect
theft of a company’s critical data from important servers. The potential impact of computer-based
crime is significant to most corporations; their entire intellectual property often resides on servers.
A tool that can detect security-related threats and attacks as they occur significantly eases the
burden that most network administrators face.
22 Introduction