Collaborative intrusion prevention
Intrusion Prevention Systems (IPSs) have long been proposed as a defense against attacks that propagate too fast for any manual response to be useful. While purely-network-based IPSs have the advantage of being easy to install and manage, research have shown that this class of systems are vulnerable...
Main Author: | |
---|---|
Format: | Others |
Language: | English |
Published: |
2010
|
Subjects: | |
Online Access: | http://hdl.handle.net/2152/7581 |
id |
ndltd-UTEXAS-oai-repositories.lib.utexas.edu-2152-7581 |
---|---|
record_format |
oai_dc |
spelling |
ndltd-UTEXAS-oai-repositories.lib.utexas.edu-2152-75812015-09-20T16:53:47ZCollaborative intrusion preventionChung, Pak HoIntrusion Prevention SystemsIPSHoneypotsNetwork-basedHost-basedAttacksNetworksProtected systemsIntrusion Prevention Systems (IPSs) have long been proposed as a defense against attacks that propagate too fast for any manual response to be useful. While purely-network-based IPSs have the advantage of being easy to install and manage, research have shown that this class of systems are vulnerable to evasion [70, 65], and can be tricked into filtering normal traffic and create more harm than good [12, 13]. Based on these researches, we believe information about how the attacked hosts process the malicious input is essential to an effective and reliable IPS. In existing IPSs, honeypots are usually used to collect such information. The collected information will then be analyzed to generate countermeasures against the observed attack. Unfortunately, techniques that allow the honeypots in a network to be identified ([5, 71]) can render these IPSs useless. In particular, attacks can be designed to avoid targeting the identified honeypots. As a result, the IPSs will have no information about the attacks, and thus no countermeasure will ever be generated. The use of honeypots is also creating other practical issues which limit the usefulness/feasibility of many host-based IPSs. We propose to solve these problems by duplicating the detection and analysis capability on every protected system; i.e., turning every host into a honeypot.text2010-06-02T18:29:48Z2010-06-02T18:29:48Z2009-122010-06-02T18:29:48Zelectronichttp://hdl.handle.net/2152/7581engCopyright is held by the author. Presentation of this material on the Libraries' web site by University Libraries, The University of Texas at Austin was made possible under a limited license grant from the author who has retained all copyrights in the works. |
collection |
NDLTD |
language |
English |
format |
Others
|
sources |
NDLTD |
topic |
Intrusion Prevention Systems IPS Honeypots Network-based Host-based Attacks Networks Protected systems |
spellingShingle |
Intrusion Prevention Systems IPS Honeypots Network-based Host-based Attacks Networks Protected systems Chung, Pak Ho Collaborative intrusion prevention |
description |
Intrusion Prevention Systems (IPSs) have long been proposed as a defense against attacks that propagate too fast for any manual response to be useful. While purely-network-based IPSs have the advantage of being easy to install and manage, research have shown that this class of systems are vulnerable to evasion [70, 65], and can be tricked into filtering normal traffic and create more harm than good [12, 13]. Based on these researches, we believe information about how the attacked hosts process the malicious input is essential to an effective and reliable IPS. In existing IPSs, honeypots are usually used to collect such information. The collected information will then be analyzed to generate countermeasures against the observed attack. Unfortunately, techniques that allow the honeypots in a network to be identified ([5, 71]) can render these IPSs useless. In particular, attacks can be designed to avoid targeting the identified honeypots. As a result, the IPSs will have no information about the attacks, and thus no countermeasure will ever be generated. The use of honeypots is also creating other practical issues which limit the usefulness/feasibility of many host-based IPSs. We propose to solve these problems by duplicating the detection and analysis capability on every protected system; i.e., turning every host into a honeypot. === text |
author |
Chung, Pak Ho |
author_facet |
Chung, Pak Ho |
author_sort |
Chung, Pak Ho |
title |
Collaborative intrusion prevention |
title_short |
Collaborative intrusion prevention |
title_full |
Collaborative intrusion prevention |
title_fullStr |
Collaborative intrusion prevention |
title_full_unstemmed |
Collaborative intrusion prevention |
title_sort |
collaborative intrusion prevention |
publishDate |
2010 |
url |
http://hdl.handle.net/2152/7581 |
work_keys_str_mv |
AT chungpakho collaborativeintrusionprevention |
_version_ |
1716820786281447424 |