Overview of TIF Discussion Topics for 2005-06

LATEST IET REPORT
May 2006 IET Report: HTML | PDF

CYBER-SAFETY:
Excerpt from email update from Bob Ono to TIF members dated June 20, 2006:

*Cyber-safety Workgroup Report - The Cyber-safety workgroup report has been completed and is available at http://security.ucdavis.edu/csworkgrouprpt.pdf. A key component of the report is the recommendation for seven new central security initiatives. Developing and maintaining central security measures for campus unit use is, in many cases, more effective and cost efficient than an individual campus unit approach that is duplicated repeatedly throughout the university and not maintained consistently across units. Moreover, a centralized approach for selected security efforts will permit campus units to better focus on the development and support of their unique technology needs. The proposed new central security efforts will be discussed with the CODVC. In addition, we are working with ORMP to identify possible funding sources for the new central security initiatives.

*2006 Cyber-safety Reporting Process - The 2006 cyber-safety compliance report will use a different format than the 2005 report. As recommended by the Cyber-safety Workgroup, the 2006 compliance report will focus on the six highest priority security standards. This attention on the six high priority standards should not be construed as a de-emphasis on campus unit compliance with all 16 security standards. The report will be completed using an online survey. We anticipate the online reporting tool will accept campus unit input from July 3 through September 1. A prototype of the survey is available at http://www.zoomerang.com/recipient/survey-intro.zgi?p=WEB225CR3WVYF5. The survey will be hosted using a secure commercial Web site. As soon as the survey Web site is available, an instructional update will be sent to the TIF-Security listserve.

UC Davis Cyber-Safety Program
Contact: Bob Ono (raono@ucdavis.edu)

VPN REPORT AND RECOMMENDATIONS:
Summary of Workgroup Process & Recommendations
Full Workgroup Report
Contact: Bob Ono (raono@ucdavis.edu)

CAMPUS DATA WAREHOUSE:
Institutional Research Work Group's Final Report (PDF)
Contact: Dave Shelby (drshelby@ucdavis.edu)

EMAIL ARCHITECTURE:
Planning is underway to enhance the campus’ front-end (spam and viruses) and back-end (Web email, email storage, etc.) email services. See Email Architecture Update to access the update provided at the June meeting of the TIF.
Contact: Doug Hartline (jdhartline@ucdavis.edu)

CAMPUS EMERGENCY PLANNING:
In May, Valerie Lucus, Campus Emergency Planner, provided an overview of campus pandemic planning efforts. Lucus explained what a pandemic is and why the campus (like many other organizations and institutions) is taking steps to prepare for a potential avian influenza pandemic. She described the campus emergency operations program, the campus emergency organizational structure, and the various coordination efforts already in place.

By July 1st, the deans, vice chancellors, and vice provosts are expected to submit a business continuity plan for their respective schools, colleges and administrative units. A campuswide plan will be developed from those unit-specific documents. The deadline the provost has set for the campus plan is September 1st.

One of the key scenarios UC Davis is planning for is one in which the campus would be faced with a high rate of absenteeism. Which services would need to continue to operate? How would we keep those basic operations running? A number of campus planning documents are being developed to address issues related to these scenarios (e.g., Draft Telecommunications Options and a comprehensive white paper by IET).

In addition to developing its own business continuity plan, IET will take a close look at the individual plans submitted by the schools, colleges, and administrative units so as to identify and work out unit-driven IT-related gaps and dependencies.

UC Davis Emergency Planning Program
Contact: Valerie Lucus, Campus Emergency Manager (vjlucus@ucdavis.edu)

EFFORT REPORTING PROJECTS:
In May, Mike Allred, Associate Vice Chancellor for Administration, reported on a project involving several UC campuses that are working collaboratively to develop a Web-based effort reporting system (see Effort Reporting Project: Overview and Status Handout).
Deployment for summer 2006 effort reports is expected this fall.

Contact: Mike Allred (jmallred@ucdavis.edu)

myTravel: TRAVEL AND ENTERTAINMENT REPORTING PROJECT
In May, Radhika Prabhu reported on myTravel, the new Web-based system developed by Concur Technologies that will be implemented at the UC Davis campus and the UC Davis Health System in 2006-07 (see MyTravel Update Handout). The primary goals for myTravel are to streamline and improve the efficiency of Travel and Entertainment (T&E) expense reimbursement and reporting processes throughout campus (See handout for a list of system, expense reporting, and approval/audit trail features).

Contact: Radhika Prabhu, Office of Administration (rprabhu@ucdavis.edu)

NEXT PHASE FOR DAFIS TP: KUALI COMMUNITY SOURCE PROJECT
Kuali Project Overview
Kuali Timeline
Kuali Project Web Site

Contact: Mike Allred (jmallred@ucdavis.edu)

BANNER 7 UPGRADE:
IET is working in partnership with several offices in Student Affairs to prepare for the upgrade to Banner 7. The upgrade is scheduled for Labor Day weekend (Sept. 2-4, 2006) and is required by a federal mandate for financial aid. See Banner 7 Upgrade Overview Handoutand the summary of the technical changes Banner 7 will introduce).

Contact: Peter Brinckerhoff, Banner Project Manager (pjbrinckerhoff@ucdavis.edu)

WHITE PAGES:
In January, IET initiated the UC Davis White Pages Project, in collaboration with UC Davis Health System and University Communications. An application is being developed that will centrally manage and function as the system of record for online and printed directory information. This application will be used by departmental contacts to update individual listings as part of the 2006-07 directory update process. Roll-out to campus directory contacts is scheduled to start June 30. See May White Pages Update to TIF
Contact: Tom Arons (tgarons@ucdavis.edu)

BULK GUEST WIRELESS ACCESS:
An application already exists to create individual guest wireless accounts. This summer, the Middleware Team will deploy a Web-based application to allow the upload, review, and/or download of bulk guest wireless access lists.
Contact: Tom Arons (tgarons@ucdavis.edu)

BULK EMAIL WEB APPLICATION:
A project is underway to develop a Web-based application that will facilitate the submission, review, and approval process for bulk email communications, as outlined in campus policy PPM 310-18. Based on the data entered into the system, this new application will determine and then track all necessary components required to accurately distribute a message to its intended recipients.
Contact: Tom Arons (tgarons@ucdavis.edu)

WEB-BASED TEMPORARY AFFILIATE FORM:
IET is developing a new Web-based application for departments to request (and extend) access for guests and visitors to campus network resources. In addition to minimizing time and effort spent processing temporary affiliate approvals, this application will enable sponsors to track the status of their temporary affiliates over time. Development and testing of components—applicant interface, authorized approvers database, and approver database management interface—are underway. Roll-out is expected this summer.
Contact: Tom Arons (tgarons@ucdavis.edu)

CENTRAL AUTHENTICATION SERVICE (CAS):
The Central Authentication Service (CAS) is a centralized, single sign-on authentication service for Web applications. CAS was initially developed at Yale, and is now managed by JA-SIG. It will eventually replace DistAuth on our campus. A pilot is underway and a demo version is being developed. TIF-Infrastructure will continue to be involved in project discussions.
Contact: Tom Arons (tgarons@ucdavis.edu)

RADIUS AUTHENTICATION SERVICE:
IET will be deploying a high availability RADIUS (Remote Authentication Dial In User Service) appliance. The initial application will be 802.1x authentication for wireless. MS-CHAPv2 password hashes will be provisioned in the campus LDAP server. Distributed administration will eventually be rolled out for departmental group management.
Contact: Tom Arons (tgarons@ucdavis.edu)