Educause Security Discussion mailing list archives

post breach communications best practices


From: "McCrary, Barbara" <bmccrary () OSRHE EDU>
Date: Fri, 9 May 2014 21:11:14 +0000

In Oklahoma City, we have a need for a person that can speak about 45 minutes on best practices in communication 
following a data breach or vulnerability in the higher ed realm ... e.g. what are the key information points and the 
best methods for informing those who are impacted?  What is the best approach in working with media following an 
incident?  How can a public information officer communicate the situation most effectively and offer sage counsel to 
campus leadership?  Please respond, if you are or know a person with the expertise, that would be willing to perform 
this community service.  Thank you.
Barbara McCrary
Chief Information Security Officer
MCSE, MCSE:Security, +Messaging, CompTia:Security+
bmccrary () osrhe edu<mailto:bmccrary () osrhe edu>

Protecting data is a shared responsibility!

INSTALL antivirus and antispyware software.
USE strong passwords.
KNOW who you are dealing with online.
STORE confidential and sensitive data on encrypted devices only.
SHUT DOWN home computers or disconnect from the Internet when not in use.

Oklahoma State Regents for Higher Education
655 Research Parkway
Suite 200
Oklahoma City, OK  73104
405 225.9316 office
405 234.4321 cell
405 234.4588 fax

Note:  This communication and attachments, if any, are intended solely for the use of the addressee hereof.  In 
addition, this information and attachments, if any, may contain information that is confidential, privileged and exempt 
from disclosure under applicable law, including, but not limited to, the Privacy Act of 1974.  If you are not the 
intended recipient of this information, you are prohibited from reading, disclosing, reproducing, distributing, 
disseminating, or otherwise using this information.  If you have received this message in error, please promptly notify 
the sender and immediately, delete this communication from your system.



Current thread: