A Reprise of an Open Letter to WOSC Technology Users on Computer/Technology Security Dated February 11, 2004. This document is as pertinent today as it was then. Your continual vigilance as end users is more important than ever to keep your computing and technology resources safe and in working order.Â I will add a couple items to the 2010 version as there are more schemes and deceptions online than ever.Â Please note the additions are posted in Bold Text Below:
1) Be diligent in upgrading your antivirus and antispyware software
2) Do not open emails in which you donâ€™t know the sender
3) Be cautious in downloading anything from the internet
4) Hesitate before sharing or forwarding emails of unknown or questionable origin.
5) IT/LSS will never ask for your username and password over email.
6) Living in the moment online could have long term implications for your future and potentially your safety.Â Be careful what pictures you post and what things you say online
7) Never, Ever, Ever, Never send a social security number, credit card number or other personal information via email.
An Open Letter to WOSC Technology Users regarding: 1) your diligence in upgrading your antivirus 2) in not opening emails in which you donâ€™t know the recipient 3) in downloading anything from the internet 4) in sharing or forwarding emails of unknown or questionable origin.
As I sit here deep into the a.m. of Wed February 11, 2004 I look back at this week as a microcosm of the last five years of virus security and general network and telecommunications usage. On Monday February 9, 2004. I come into the officeÂ and sat down planning to resolve one of normal everyday frustrations of you the average campus technology user.Â Instead I am greeted by the voice of Ted of outofthisworldhosting.com of Gainsville Tennessee (the names have been changed in case… or maybe because this is a small small small world and this could be your cousin or brother) who is muttering something about them preferring not to take legal action and a system on our end is attempting to overwhelm one of their systems blah, blah, blah.Â I say, â€œso a system with one of our addresses is attacking your systemâ€Â to which he replies, â€œ I didnâ€™t want to use the word attack, but if you mustâ€¦..â€Â He provides me some information from his logs that no normal person is interested in and we â€˜telecommunicativelyâ€™ part ways for the time being with me agreeing to keep him posted.
Since legislation related to many of the digital issues of our modern world is a bit, or byte or packet behind reality IÂ have at that moment no exact picture of the reality ofÂ his ability to pursue legal recourse.Â I simply say unto myself â€œI believe I need to do unto others as I would like him to do unto meâ€ which in this case is help my telecommunications brethren. At this point I contact what some of you the end users refer to as the â€œtechie boysâ€ usually Steve, Brian,Â and /or Joe, in this case all of the above.We meetÂ briefly and the follow up with several emails discussing our strategy for resolving the issue.Â Now they up until this point are merrily working on one of the multitude of projects, which are deemed to be, by you, (the end user) as the most mission critical event of the moment.
Within the first 15 minutes of the first phone call â€œthe techie boysâ€ track down information, which tells us the attacker, is possibly in the dorms and which we hypothesize is most likely from a computer which has become the home of a virus.Â I subsequently take the email from our telecommunications provider, OneNet, notifying us of a â€œnetwork usage abuseâ€ from the party noted above.Â They too areÂ requesting a reply and notification of our receipt of the message and that we need to report how we will resolve the issue or they will â€¦â€¦.. have to â€œshutter our telecommunications window.â€
I do the required notifications and go beyond the call of duty to update and notify outofthisworldhosting.com of our intentions and strategy for resolving the issue.Â I then talk to a couple of our administrators notifying them of a potential problem and of our strategy for resolution.Â At this point we are 2.5 hours into day and guess whatâ€¦â€¦â€¦no other mission critical event of the moment is being worked on by myself â€¦â€¦.or the techie boys.Â I get up head to the cafeteria for my morning jolt of caffeine and am subsequently confronted by at least two hallway notifications that their or somebody elseâ€™s work order has not been completed or acknowledged or that they canâ€™t ever find someone to help with some technical issue.Â I reply I will check into, I get my caffeine and return to the desk.Â I again check with the â€œtechie boysâ€ who are still working on our virus issue and not working on the other various mission critical events of the moment to get an update.Â I actually do one task related something other than the aforementioned virus events and it is time for lunch.Â By the end of the day the â€œtechie boysâ€Â Â Â have still not totally tracked down the culprit but have at least narrowed down the possibilities.Â Again, however it must be noted that at least 4 full time FTE employees have committed at least (7 hours x 4 FTE) 28 clock hours to the task of resolving an unanticipated virus issue.
We return on Tuesday February 10, 2004 with again much of the morningâ€™s time and effort committed to tracking down and locating the issue discussed in the previous text. The issue becomes stickier as it not only involves our campus network, but AOL through a dial up account which is issue which envokes the reworking of our campus network use policy(2010 NOTE: I wish I remembered all of the details here.Â I will have to dig deeper to see what I can find).Â Â Additionally questions arise related to this event that will involve $$$,Â Do we, or can we force them, the dorm user, to purchase antivirus as that is not specifically written into our dorm access policy? Do we provide it for them and up their access fee?Â Do we provide it and not up the access fee?
Then suddenly its time for the Campus Staff All Staff meeting and you know what the issue is still not totally resolved and once again the other various mission critical events of the moment are not resolvedÂ least (13 hours x 4 FTE) 52 clock hours later.
I submit this tale as a reminder to you that the internet in all of its apparent glory is democracy in its purest form, it is the wild west of the modern world it is all of these things and more.Â The tale is not that uncommon in our workday, however I donâ€™t always tell you.Â If we have a major issue that must be addressed and resolved such as Kazaa, Napster or one of the other file sharing programs you may hear about it.Â However, we generally try to let this resource operate behind the scene.Â You see the privilege of the resource, Â you donâ€™t always see the price for making it transparent.
I am again asking for your help in watching your email and web research.Â I am asking you to be careful about the types of resources you look at on the internet.Â I am asking that you ask yourself if what you are doing is work related.
There are some technical issues that come about that you can do nothing about, but again when one of us sends a message about a virus or a telecom issue that you do take notice.
I send this encouraging you to be ever vigilant about these issues to again show that one little virus or security issue can consume the days of 2, 3 or even 4 of our personnel causing those things that are near and dear to you (and productive) to be delayed.Â Some security related issue happens every couple of weeks if not every week.Â Â It has changed our (information services) workload significantly.Â Although we have automated protection process and invested in tools to automate protection we still spend probably 20- 25% of our time addressing issues related to network security and viruses and it does take away from the various other productive mission critical events of the moment.Â Five or six years ago this was a non-issue.