Dean Shareski at
Ideas and Thoughts talks about the challenges of allowing personnally owned technology to the district network.
The idea raises many questions. Few of the solutions are clear.
When a student or staff asks to connect to the district network the following questions come to mind:
1. Can you guarantee with 100% certainty that your computer is virus and spyware free?
Most answer yes to that question. We most certainly cannot afford the quarantine methods used by colleges.
1.5 Can you guarantee with 100% certainty that your computer is/will not run any program that will negatively impact District network operations?
2. Are you willing to hold the district harmless if your computer becomes infected while using the District network?
3. Are you willing to be held liable if your computer infects the district computers with a virus or spyware either intentionally or accidentally? My technology department is bare bones and short staffed as it is. Cleaning up infections from personnally owned computers is WAY out of our range of services.
4. Are you willing to provide the district with administrative access to your computer to check for inappropriate content? I’m really not interested in accessing the computer but should an incident happen…
A staff member, after considering these questions once asked if there was ANY way he/she could get connected. I said, “SURE. Just donate your computer to the District. We’ll get it cleaned up, certify the software, and issue it back to you with our network (and security) settings in place.”
There is one element that I worry about that I’m sure is coming our way. Wireless broadband cards. Suppose a student or staff member has a laptop with wireless broadband (Verizon, Sprint, Cingular all offer them.)
We certainly can’t comply with CIPA, COPPA, FERPA under those conditions.
Get your policy committee ready because it’s coming.
Great discussion, Dean.