University of Wisconsin–Madison
Line art image of a shield with a check mark and circuits

Endpoint Management Project

Project Updates

Project timeline

High-level milestones

  1. April, 2018 – Discovery: Tool inventory and requirements elicitation.
  2. July, 2018 – Tool Research: Vendor research, peer bench marking, RFI process.
  3. October, 2018 – Budget model and purchasing: Fiscal year 2019 funding, Fiscal year 2020 budget, Request for proposal.
  4. July, 2019 – Request for proposals complete.
  5. March 2020 – COVID-19: Project on hold.
  6. October 2020 – Implementation begins.
  7. April 2021 – Provisioning: Additional central application content for BigFix, Workspace ONE and Dell Factory Provisioning options.
  8. June 2021 – Unified Catalog, Training, Documentation

FAQs

This is an accordion element with a series of buttons that open and close related content panels.

What's an endpoint?

An endpoint device is an internet-capable computer hardware device on a TCP/IP network. This includes but is not limited to computers, laptops, smartphones, tablets, thin clients, printers, and other specialized hardware such as point-of-sale terminals and smart meters. From a security perspective, a server is also considered an endpoint.

In short, an endpoint is a computing device that communicates back and forth with a network. All endpoints, when connected to a network, are open to a number of vulnerabilities if not properly protected.

What are endpoint management and security tools?

  • Endpoint management tools help keep track of devices used in a system to ensure their software is secure and up-to-date.

    Some of the endpoint management and security software tools in use on campus today include Cisco Advanced Malware Protection, Workspace ONE, Trendmicro, System Center Configuration Manager and IBM BigFix, which support virus protection and operating system and software updates and patches.

What's included in an endpoint management and security program?

Important components of an endpoint management and security program include:

  • Consistent management of university-owned devices including inventory, patching, and vulnerability management
  • Identification of security threats and active mitigation of threats such as malware
  • Protection for mobile devices such as tablets and smartphones

Because many people in the UW–Madison community bring their own devices to campus, the project will also include recommendations for personally-owned and unmanaged devices used throughout the university.

Why does UW–Madison need this project?

An endpoint security system is developed to protect the endpoints and their network from malicious threats. It provides a central method to secure the IT network and give visibility to vulnerabilities and risks over time.

Currently, endpoint management is inconsistent across campus. In addition, license and support contracts for our current security agents are due to end. This project seeks to create a service that provides the ability to centrally manage endpoints and provide security agents for over 80% of the campus computing environment.

What's the scope of this project?

The UW System Information Security Program requires UW–Madison to standardize on tools that will enable a campus-wide inventory of university-owned computing devices, provide the capability to connect to all devices, and enable central logging and activity reporting. In addition, the protection of UW–Madison computing devices or endpoints (e.g., desktops, laptops, servers, mobile devices, etc.) that access University data is critical to reducing the overall security risk to the data these devices encounter.

UW–Madison has selected industry-leading and forward-thinking technology solutions that address disparities in endpoint management and security across organizations, which will help us meet the UW System requirements and our own endpoint management and security needs.

Project Team

This is an accordion element with a series of buttons that open and close related content panels.

Executive Sponsor

David Pagenkopf, Deputy CIO

Implementation Leadership Team

  • Tamara Walker (DoIT)
  • Bob Turner (CISO)
  • Kevin Cherek (AIMS)
  • Chris Spencer (SMPH)
  • Stefan Wahe (CALS)
  • Susan Weier (L&S)
  • Pete Boguszewski (GLS)
  • Lauren Bruce, Communications
  • Mark Treiber, DoIT Project Management Office

Endpoint Implementation Core Team

  • Chris Poser (Co-Chair/Service Lead)
  • Jon Dickenson (Technical Lead)
  • Pat Daley (Technical Lead)
  • Karl Weirauch (Technical Lead)
  • Dave Schroeder (Technical Lead)
  • Oakes Dobson (Technical Lead)
  • Cory Chancellor/Derek Tessman – AIMS
  • Curt Shomberg/Matt Schultz – SMPH
  • Sterling Anderson – L&S
  • Chris Wiswell — Athletics
  • Charlie Maurice – Engineering
  • Drew Gardner – WID
  • Jon May – DoIT Data Center
  • Kerry Tobin – CALS-Biochemistry
  • Will May – Information School
  • Susan Weier – LSS
  • Sara J Nagreen – Mathematics
  • Thomas Hartman (or Sara Lien) – CALS-CALS IT
  • Jen Sutherland (ITIL)
  • Sara Tate-Pederson (IT Policy)

Communication Team

  • Lauren Bruce, DoIT
  • ISCOM
  • Cybersecurity

Procurement

  • Bruce Reilly

Other Advisory Teams

  • CIO Cabinet
  • T&L TAG
  • Research TAG
  • Core Services Advisory Group

Feedback & Documentation

Line art image of a brain with sparks

Share your thoughts

Your ideas about Endpoint Management matter to us.

Send us an email

Line art image of a user with three stars

Contribute your expertise

There’s an Endpoint Management Community of Practice on MS Teams.

Join the CoP

Line art image of a shield with a check mark and circuits

More about Endpoint Management

Service page

KnowledgeBase