Incident Handling
Charlotte Russell reported on Incident Handling procedures involving UNT vs. non-UNT computers.  Some incidents can result in escalation to other administrative departments on campus for disciplinary or legal action (i.e. Center for Student Rights and Responsibilities, UNT General Counsel, UNT Police department, etc.).  Attempts should be made to handling security incidents administratively, i.e. without the involvement of legal entities, where possible.  Security Incident Handling Procedures will be made available on the Information Security website, http://www.unt.edu/security. In the case of incidents involving non-UNT computers, computing staff should not attempt to confiscate the computer, or detain an individual responsible for the computer against their will.  Initial efforts to contact individuals responsible for security incidents related non-UNT computers may need the additional involvement of department heads or designees for identification purposes.

Wireless Implementation
Rory Rivoire reported on the wireless network implementation.  There are several concerns about the project:

• wireless security policies, procedures, and sanctions
• acceptable locations for wireless access points
• authentication problems for non-UNT users who will not have accounts in the euid system 
• standards for unique devices, operating systems, wireless cameras, handheld devices, etc.
• security vs. functionality (ease of use)
• implementing bandwidth limitations
• building a network that can be used while under expansion

Rory will work with the Information Security team on security implications and would like feedback from DCSMT regarding the types of devices currently in use in each area, wireless needs for each area, and the names of those who would like to be on the network.  He would like for DCSMT to test the access points that are currently in place.  Rory will post updates on the network managers list.   Ideas for a Wireless Technology group as well as a portable testing center (using laptops, handheld devices, etc.) were considered but have not been finalized. 

Old Business

SPSS Contract
Philip reported that the SPSS enterprise license purchase is moving forward and may solve a number of problems that have been addressed.

New Business
Chris Strauss reported that we are thirty days away from the estimated move date to Remedy 5.1 (December 16, 2002).  Any issues with technology could possibly postpone or delay the implementation.  When Remedy 5.1 is rolled out, clients installs should be updated to 5.1.  The system will be integrated with ldap and authentication will take place on the authentication servers (with euid and eaglemail password).  Passwords will not will be stored in Remedy.  Password changes can be made locally and they will pass over to the authentication server.  The web interface is browser and java specific.  There are many issues with the browser.  Chris will post notices on the progress of the project to the network managers list. 

Status Reports
Travis Brown reported that the new Iatro is up behind web director.  Istats should be up by the end of the day.

Kirk Kelly reported that he is studying the implications of a power outage on the west side of campus during Spring Break of 2003.  The outage is scheduled to last 3-5 days to create infrastructure for a new residence hall.

Rory Rivoire reported that power outages can shut down communications on the network.

Wil Clark reported that he is investigating a telephone system upgrade.

Elizabeth Hinkle-Turner reported that general access lab managers have begun their portion of the student computing survey.

The meeting adjourned at 11:25 am.