Personal tools
You are here: Home Department IT Security Technical Staff Incident Handling
Document Actions

Incident Handling

Up one level

The Rutgers University Computing Incident Response Team (RU CIRT) serves the Rutgers computing community. The RU CIRT handles incidents in which Rutgers hosts cause problems. The contact email address is: abuse@rutgers.edu

What is a computer abuse incident? — last modified 2007-07-27 11:28
Typical computer abuse incidents and incidents for which action can be taken by the Rutgers University Computing Incident Response Team (RU CIRT).
Reporting a computer abuse incident — last modified 2007-11-19 09:32
The computer staff in your department can assist you in reviewing and reporting computer abuse incidents, as well as the Help Desks in the Campus Computing Divisions.
Responding to computer abuse incidents — last modified 2007-07-27 11:28
Rutgers University employs a distributed security model. The RU CIRT reviews incident reports and dispatches them to the appropriate departmental computing staff for resolution. In other words, notification and data collection are centralized while execution and resolution are decentralized.
Incident Handling Process — last modified 2008-03-07 08:36
Here is information about the operations involved in incident handling by the Rutgers University Computing Incident Response Team (RU CIRT) and how they are carried out.
Advice for specific incidents — last modified 2007-07-27 11:28
Information and advice tailored to the Rutgers University environment. These are the Incident Types used in abuse reports distributed by the Rutgers University Computing Incident Response Team (RU CIRT). Other commonly used designations are included for clarity. Click on the topic to navigate to the detailed information.
Compromise of Confidential or Sensitive Data — last modified 2008-02-25 17:23
There are essential procedures common to a data breach, although a data breach can occur in many ways. The data loss is discovered in the investigation of an incident that initially presents as theft or loss of equipment, system intrusion or hacking, malware and unintended posting to a web page. Once it has been established that a data compromise has taken place, the loss of data becomes the overriding consideration in the response.
Online References for Incident Handling — last modified 2007-07-27 11:28
A vast number of security web sites are available. A collection of favorites is gathered here with short descriptions.
Removing Information from Search Engines — last modified 2007-08-28 14:09
Clearing or removing a web page from the local host is the first step. However, some search engines cache web pages-- copies of entire web pages or portions of them.
IPET — last modified 2007-07-27 11:28
Documents for IPET incident handling.
MS ISAC Operations Center Digital Dashboard — last modified 2007-10-01 18:38
The Digital Dashboard was developed by the Multi-States Information Sharing and Analysis Center (MS-ISAC) to provide a quick overview of the current cyberthreat picture.

Powered by Plone CMS, the Open Source Content Management System

This site conforms to the following standards: