The plan
1: Explore the network by going through documentation, and updating where applicable.  One of the things which I'm going to have to get up to speed on very quickly is what we monitor for, both in practice and what we are allowed by policy.  For instance, some of the 'rent your machine to a spammer' IPs -- do we monitor for activity from them?
2: Have lunch with various SIRT members to get a better feel for areas of responsibility in addition to what is listed (realistically, there is an 'unofficial guru' for something in every office)
3: Explore areas of responsibility between different branches of CCIT (the politics of networking)
4: Prepare for the new year, when new (and often infected!) machines arrive
5: Join HTCIA (High Tech Crime Investigation Association), and possibly work on INCH (Extended Incident Handling) with IETF.
6: After my last email communication with my old boss (ITS director), he suggested that a good course of action would be to keep open lines of communication between Tech and UA.
7: If UA is like Tech, one of the biggest security risks are the undergraduates.  One major problem is communication -- many students tend to ignore public announcements via email, etc.
8: Local Linux mirror -- do we have one already?  I noticed that ESPRI has one, but it only has two flavors (Debian and Gentoo).  Obvious downsides are bandwidth, maintanence, etc.  Upsides are that it encourages people 

6 month goals: