Select Page

Project Planning Team

Executive Sponsor: Anne Milkovich, CIO

Project Sponsor: Anne Milkovich, CIO

Project Managers: Victor Alatorre, Mark Clements, Laura Knaapen

Technical Team Members: Dan Petersen, Christian Beck, Eamon Bauman, Michael Brunn, Michelle Loker, Ricky Johnson, Michelle Loker

 Contact IT

  Phone: (920) 424-3020
  Email: helpdesk@uwosh.edu

Status: 11/9/18

  • Admin rights exception and removal of access processes shared with campus.
  • Exception requests are being processed.
  • Project planning is continues for multi-factor authentication for PeopleSoft, ImageNow and Canvas.

Information Security Compliance

UW System has provided all UW campuses with five Administrative Policies and three Procedures on Information Security. These policies and procedures are mandatory for all UW campuses. The five policies and three procedures are listed on the IT Policies web page.

During the Spring semester IT completed the Authentication procedures regarding password requirements for the university NetID account. As part of the Legislative Bureau audit, several small projects were identified for IT to work on. The projects are listed below in priority order. Additional projects may be required based on the new UW System two-year Info Security plan.

Project/PolicyProject ManagerSemester to Start WorkStatusRecentNext
Enforce mandatory security training.Richard MontanoSpring 2018OperationalEmployees out of compliance will have their accounts lockedImprove system automation by connecting to Canvas
Student employees cannot use generic, shared accounts.Laura KnaapenSummer 2018OperationalAccount creation semi-automated.
Immediate access removal upon employee separation from university or role.Laura KnaapenSummer 2018OperationalProcess maps are set.Verify process is working appropriately.
Remove administrative rights from desktop computers.Laura KnaapenFall 2018In ProgressExceptions being accepted and reviewed.Admin rights will be turned off on January 15, 2019.
Bring Gmail into compliance for password policiesVictor AlatorreSummer 2019No longer neededPlan migration to Office 365
Auditing desktop computers for high risk data.Mark ClementsFall 2018In ProgressTechnical requirements have been metCommunicate rollout of service to campus
Move all high risk data to encrypted storage.Victor Alatorre and Mark ClementsFall 2018ConceptResearching encryption optionsO365 is the current recommendation for storing high risk data that must be shared.
Communicate with past emeriti to verify relationship with campus and need for accountsLaura KnaapenSpring 2019Not Started
No longer allow physical, wired attachment of non-university devices.Laura KnaapenSpring 2019Not Started
Require multi-factor authentication to access high risk data.Mark Clements and Victor AlatorreSpring 2019PlanningProject kickoff meeting held. Planning implementation.Work through technical issues with PeopleSoft and ImageNow.
Teach use of account delegation so email passwords are no longer being sharedLaura KnaapenSpring 2019In ProgressKnowledgeBase article created. Testing with IT Classroom Tech email accountReview test results.
Rollout to campus.
Review all enterprise applications to document security and dependenciesMark ClementsSpring 2019In Progress
Increase offering of security awareness education.Richard MontanoSummer 2019In ProgressSecurity is included in employee orientations.Move from Lawroom to Canvas
Auditing employee data access through formal approval and renewal procedures.Mark ClementsFall 2019Not Started
Desupporting local hard drive storage.Victor AlatorreFall
2019
Not Started
Shift all full-time employees who maintained their student account to the employee account scheme.Victor AlatorreFall 2019Not Started
Provide student accounts to employees taking classesVictor AlatorreFall 2019Not Started

Recent:

  • Admin Rights Exception email sent to campus and placed on web.
  • Exception requests are being processed.
  • Attending college meetings to inform them of Duo and other upcoming projects.

Next:

  • Turn off Admin Rights on January 15, 2019.
  • Begin Duo implementation January 2, 2019.
  • Plan for other audit responses.