Overview
Overview
Overview
The Lifecycle of an Attack, page 1-2 How Cisco Security Agents Protect Against Attacks, page 1-3 Deployment Overview, page 1-4
Network Architecture, page 1-5 Cisco Security Agent Architecture, page 1-6
Communicating Over Secure Channels, page 1-8 Distributing Policy Updates, page 1-9
1-1
Overview
Network Manifestation
Penetrate
Persist
Propagate
Paralyze
ping server IP addresses run traceroute on IP addresses sniff passwords impersonate mail users email attachments Java applets and ActiveX controls buffer overflows backdoors and trojans weaken security settings install new services email Internet connections IRC FTP infected file shares reformat disks destroy or corrupt data drill security holes crash computers consume work cycles steal confidential data
1-2
78-18652-01
Chapter 1
What resource is being accessed. What operation is being invoked. Which application is invoking the action.
The resources in question may be either system resources or network resources such as mail servers. When any system actions that are controlled by specific rules are attempted and allowed or denied accordingly, a system event is logged and sent to the administrator in the form of a configurable notification such as email, pager, or custom script.
1-3
Overview
Deployment Overview
Management Center for Cisco Security Agents contains two components:
CSA MCinstalls on designated Windows 2003 systems and includes a configuration database server and a web-based user interface. Cisco Security Agent (the agent)installs on server and desktop systems across your enterprise network.
Using CSA MC, you assemble your network machines into specified groups and then attach security policies to those groups. All configuration is done through the web-based user interface and then deployed to the agents. The network example shown in Figure 1-1 illustrates a basic deployment scenario. CSA MC software is installed on a system which maintains all policy and host groups. The administration user interface is accessed securely using SSL (Secure Sockets Layer) from any machine on the network that can connect to the server and run a web browser. Use the web-based interface to deploy your policies from CSA MC to agents across your network.
Figure 1-1 Policy Deployment
1-4
78-18652-01
Chapter 1
Network Architecture
The CSA MC architecture model consists of a central management center which maintains a database of policies and system nodes, all of which have Cisco Security Agent software installed on their desktops and servers. Agents register with CSA MC. CSA MC checks its configuration database for a record of the system. When the system is found and authenticated, CSA MC deploys a configured policy for that particular system or grouping of systems. The Cisco Security Agent software now continually monitors local system activity and polls to the CSA MC at configurable intervals for policy updates. It also sends triggered event alerts to the CSA MCs global event manager. The global event manager examines system event logs and, based on that examination, may trigger an alert notification to the administrator or cause the agent to take a particular action. See Appendix B, System Components for detailed information on product architecture.
Note
1-5
Overview
Figure 1-2
CSA MC Architecture
Report Generator
Database Server
Web Server
SSL
Alerts
1-6
78-18652-01
191453
Chapter 1
Figure 1-3
Internet, Intranet
Data Filter
IIS/Apache
Install
TCP/IP Policies
Rule/Event Correlation Engine Network Traffic Interceptor File Interceptor Registry Interceptor
NIC
Disk
System
191452
1-7
Overview
Figure 1-4
Data Filter
iPlanet/Apache
pkadd
TCP/IP Policies
Rule/Event Correlation Engine Network Traffic Interceptor File Interceptor System Call Interceptor
NIC
Disk
System
191451
1-8
78-18652-01
Chapter 1
1-9
Overview
1-10
78-18652-01