904.10 Confidentiality of Security and Emergency Preparedness Information

The District adopts, maintains and revises procedures, plans, and information concerning security procedures and emergency preparedness information for the protection of District employees, visitors to the District, students and other persons in the care, custody, or under the control of the District, and for the protection of property under the jurisdiction of the District, the disclosure of which could reasonably be expected to jeopardize such employees, visitors, persons, or property. The District shall keep information related to the security procedures, emergency preparedness, and vulnerability assessments confidential to the full extent permitted by law.


Without limiting the generality of preceding paragraph, it is the policy of the District to effectuate its security and preparedness measures by maintaining as confidential the following information, records and classes of records:

  • Information directly related to vulnerability assessments;
  • Information contained in records relating to security measures, such as security and operational response plans,
  • radio protocols, security codes and combinations, passwords, restricted area passes, keys, and security or response procedures;
  • Emergency response protocols;
  • Computer and computer network information which, if disclosed, would assist persons to gain unauthorized access to confidential materials described in this policy;
  • Records or information regarding routines, practices and procedures of security personnel, security contractors or other persons responsible for the protection of persons and property of the district; and,
  • Information contained in records that, if disclosed, would significantly increase the vulnerability of critical physical systems or infrastructures of the district to attack.
  • Continuity of Operations and other Long-Term Recovery plans that, if divulged, could be used to deploy secondary devices and secondary attacks.

 

Approved:

February 15, 2010
 

Reviewed:

December 16, 2009
October 19, 2015 
 
Revised:
October 19, 2015