User Interaction - Cisco IDS-4230-FE - Intrusion Detection Sys Fast Ethernet Sensor Installation And Configuration Manual

Appendix A Intrusion Detection System Architecture

User Interaction

Cisco Intrusion Detection System Appliance and Module Installation and Configuration Guide Version 4.1
78-15597-02
Sensor up-time is 20 days.
Using 214319104 out of 921522176 bytes of available memory (23% usage)
Using 596M out of 15G bytes of available disk space (5% usage)
MainApp 2003_Oct_10_11.16 (Release)
AnalysisEngine 2003_Oct_10_11.16 (Release)
Authentication 2003_Oct_10_11.16 (Release)
Logger 2003_Oct_10_11.16 (Release)
NetworkAccess 2003_Oct_10_11.16 (Release)
TransactionSource 2003_Oct_10_11.16 (Release)
WebServer 2003_Oct_10_11.16 (Release)
CLI 2003_Oct_10_11.16 (Release)
Upgrade History:
* IDS-K9-min-4.1-1-S47
IDS-K9-sp-4.1-3-S61.rpm.pkg
Recovery Partition Version 1.2 - 4.1(1)S47
You can configure IDS through the CLI, the IDM, the IDS MC, or another
application using RDEP.
You can interact with IDS software in the following ways:
• Configure sensor parameters.
You generate the initial configuration for the IDS—setting network
parameters, time, and allowed hosts—by using the setup command in the
CLI. You usually have to do this only once with a new sensor.
Configure blocking and interfaces.
•
• Tune the configuration.
You will want to make modifications to the default configuration, primarily
the sensing engine (SensorApp), which is the portion of the application that
monitors network traffic. After initially installing the IDS on the network,
you can tune it until it is operating efficiently and only producing information
you think is useful.
2003-10-10T11:01:13-0500 Running
2003-10-10T11:01:13-0500 Running
2003-10-10T11:01:13-0500 Running
2003-10-10T11:01:13-0500 Running
2003-10-10T11:01:13-0500 Running
2003-10-10T11:01:13-0500 Running
2003-10-10T11:01:13-0500 Running
2003-10-10T11:01:13-0500
12:00:00 UTC Thu Jun 30 2005
14:14:55 UTC Fri Feb 20 2004
System Overview
A-5