According to the Department of Homeland Security (DHS) and the Cybersecurity and Infrastructure Security Agency (CISA), K-12 school divisions are “particularly lucrative targets due to the amount of sensitive student data accessible through school systems.”
Incident Response is a Team Sport, is an event that will provide participants with an experience demonstrating how a cybersecurity incident can unfold and how to respond to one using an Incident Response Plan (IRP). K-12 division-level leadership including superintendents, assistant superintendents, technology directors, network admins, and other critical staff who would be involved in making high-level cybersecurity incident decisions should attend. The objective for the day is for schools to leave with a draft of an IRP if they do not already have one, or to augment or enhance the one they already have as a result of interacting with cybersecurity and legal experts during the day. Division-level teams are preferred. Lunch will be provided.
This event will take place on two different dates; March 14th at Richard Bland College of William and Mary in South Prince George, and again on March 30th at the New College Institute in Martinsville.
The morning sessions will feature experts in the field of cybersecurity presenting topics and current themes relevant to the K-12 school communities regarding the real threats and critical responses to those situations. Registering your division team will be crucial to your participation in the Table Top exercise that will focus on a team-based approach to enhancing your awareness and knowledge and ultimately in the development of your division's IRP. The afternoon sessions will provide smaller group breakout sessions geared toward the specific operational, legal, communications, and technical concerns of those in the crucial division-level leadership roles mentioned above.
Register your team for the Richard Bland College event on March 14th or the New College Institute event on March 30th by pointing your browser to bit.ly/incident-response-23.
