Version 1.0

Purpose

This policy defines the responsibilities of all members of the University community when responding to or reporting information security incidents.

Scope

This IT policy, and all policies referenced herein, shall apply to all members of the University community including faculty, students, administrative officials, staff, alumni, authorized guests, delegates, and independent contractors (the “User(s)” or “you”) who use, access, or otherwise employ, locally or remotely, the University’s IT Resources, whether individually controlled, shared, stand-alone, or networked.

Policy Statement

• Any individual who suspects that a theft, breach, or exposure of Fordham Protected data or Fordham Sensitive data has occurred must immediately provide a description of what happened to the University Information Security Office (UISO) via email sent to infosec@fordham.edu.
• The Computer Security Incident Response Team (CSIRT), per the Computer Security Incident Response Plan (CSIRP), handles the incident response process.
• All members of the CSIRT must participate in the Testing, Training, & Exercise (TT&E) program is to sustain and refine the University’s ability to handle Incidents following the best practices outlined in NIST Special Publication 800-84.
• The CSIRP provides the process for handling different types of Incidents. Regardless of the scenario, incident handling must follow this nine-phase lifecycle.
  • Preparation
  • Identification
  • Notification
  • Initial containment
  • Analysis
  • Post-analysis containment
  • Eradication
  • Recovery
  • Follow-up

Definitions

An Incident is a suspected, attempted, successful, or imminent threat of unauthorized access, use, disclosure, breach, modification, or destruction of IT Resources, interference with IT Resources operations, or violation of policy.

IT Resources include computing, networking, communications, application, and telecommunications systems, infrastructure, hardware, software, data, databases, personnel, procedures, physical facilities, cloud-based vendors, Software as a Service (SaaS) vendors, and any related materials and services.

Related Policies and Procedures

• Computer Security Incident Response Plan (CSIRP)
• Information Security Breach Response

Implementation Information

Revision History

Policy Disclaimer Statement

Deviations from policies, procedures, or guidelines published and approved by the University Information Security Office (UISO) may only be done cooperatively between the UISO and the requesting entity with sufficient time to allow for appropriate risk analysis, documentation, and possible presentation to authorized University representatives. Willful failure to adhere to UISO written policies may be met with University sanctions.