Author
Abstract
Traditionally, computer security incident response teams (CSIRT) are expected to respond to hacking incidents, rogue employees, or virus outbreaks. Recently, they are maturing into a critical tool for maintaining business operations, homeland security, and compliance with new regulations. Alberts et al (2004) define a CSIRT to be “a capability or team that provides services and support to a defined constituency for preventing, handling, and responding to computer security incidents.” Among the most important aims of these CSIRTs is a focus on processes related to incident and security management. A type of CSIRT called, “Coordinating CSIRTs (C-CSIRT) “ facilitate the handling of incidents, vulnerabilities, and general information across a variety of external and internal organizations. These C-CSIRTs play a crucial role in performing security and incident management across multiple organizations. Examples of these C-CSIRTs include AusCERT (Australia Computer Emergency Response Team) and CISCO PSIRT (CISCO Product Security Incident Response Team).The main focus of a C-CSIRT is to get its constituent organizations’ computer related infrastructure back to an operational state as soon as possible (Killcerece, 2003). This is done by concentrating primarily on incident, security and IT management. In our view, a C-CSIRT must include related processes such as communication with the public and media and the investigative processes that help to find the root causes of the attack to prevent not only irreparable harm to the public image and services of a business, but also recurring attacks. In the proposed framework, we integrate issues of communication and investigation into the processes that a C-CSIRT performs to fulfill its basic function of security, IT and incident management.
Suggested Citation
Rahul Bhaskar, 2005.
"A Proposed Integrated Framework for Coordinating Computer Security Incident Response Team,"
Journal of Information Privacy and Security, Taylor & Francis Journals, vol. 1(3), pages 3-17, July.
Handle:
RePEc:taf:uipsxx:v:1:y:2005:i:3:p:3-17
DOI: 10.1080/15536548.2005.10855771
Download full text from publisher
As the access to this document is restricted, you may want to search for a different version of it.
Corrections
All material on this site has been provided by the respective publishers and authors. You can help correct errors and omissions. When requesting a correction, please mention this item's handle: RePEc:taf:uipsxx:v:1:y:2005:i:3:p:3-17. See general information about how to correct material in RePEc.
If you have authored this item and are not yet registered with RePEc, we encourage you to do it here. This allows to link your profile to this item. It also allows you to accept potential citations to this item that we are uncertain about.
We have no bibliographic references for this item. You can help adding them by using this form .
If you know of missing items citing this one, you can help us creating those links by adding the relevant references in the same way as above, for each refering item. If you are a registered author of this item, you may also want to check the "citations" tab in your RePEc Author Service profile, as there may be some citations waiting for confirmation.
For technical questions regarding this item, or to correct its authors, title, abstract, bibliographic or download information, contact: Chris Longhurst (email available below). General contact details of provider: http://www.tandfonline.com/uips .
Please note that corrections may take a couple of weeks to filter through
the various RePEc services.