Modernizing Secure Access

CISCO AnyConnect is Being Retired Effective June 1, 2026​
Introducing the new Ralph Bunche Data Center

Howard University is transitioning away from CISCO AnyConnect and introducing a more secure, scalable, and user-centered framework for accessing University applications off campus. This page explains what’s changing, why it matters, and what you need to do.

Why We’re Retiring Cisco AnyConnect​

Cisco AnyConnect has served as the University's primary remote access solution for many years. However,as our digital environment has grown (and as the ways we work, learn, and collaborate have evolved), thelimitations of traditional VPN architecture have become increasingly apparent.

Rather than routing all traffic through a single, centralized tunnel, modern security principles call forgranular, identity-driven access controls that evaluate every connection on its own merit. This approach —commonly referred to as Zero Trust Network Access (ZTNA) — is the foundation of the new model we areadopting.

What This Means for You

You will no longer need to connect to a VPN before accessing most university applications. Instead, accessis managed per-application, per-user, and per-device — providing a faster, more seamless experiencewhile significantly raising the security baseline for the entire institution.

Inside the VPN Transition Process​

Why We’re Retiring CISCO AnyConnect​

We’re entering a new era of modernization. More information coming soon!

Introducing Private Entra Access​

Private Access is the University's new solution for secure, off-campus application access. Unlike atraditional VPN, Private Access does not route all of your internet traffic through the university network.Instead, it creates secure, policy-driven connections specifically to the applications and resources you areauthorized to use.

This solution validates three factors before granting any connection:

  1. Who you are (your university identity)

  2. What device you're on(whether it is enrolled and meets policy) and

  3. What you need access to (only authorized applications are reachable)

Requesting Access for Private Entra Access

Each building will experience a new era of modernization. More information coming soon!

Requesting Application Access for Private Entra Access​

Not all university applications are automatically available through Private Access at launch. During the initial rollout phase, access tospecific applications must be formally requested by your department or unit, reviewed by the IT Security Office, and provisioned by theNetwork Infrastructure team.

How to Request Application Onboarding

  • Identify the Application and its Data Classification

    • Confirm whether the application handles general, sensitive, or regulated data (see HIPAA/Confidential restrictions)

  • Obtain Departmental Approval

    • Your department head or IT liaison should endorse the request before submission to avoid delays

  • Submit the Application Access Request Form

    • Complete all required fields, including the vendor name, application URL or hostname, intended user group, and businessjustification

  • IT Security Review

    • Enterprise Technology Services (ETS) will evaluate the request against access control policies and notify you of theoutcome

  • Provisioning and Confirmation

    • Upon approval, the application will be added to the Private Access policy and users will be notified

CURRENT ONBOARDING RESTRICTION — HIPAA & CONFIDENTIAL APPLICATIONS

During this initial rollout phase, the University is not able to onboard applications that handle HIPAA-regulated, highly confidential, or similarly restricted data through Private Access. This restriction istemporary and will be lifted once the required security controls, audit logging, and access governanceprocesses have been fully validated.

Applications currently excluded from Private Access onboarding include, but are not limited to:

  • Electronic Health Record (EHR) and clinical data systems

  • Applications subject to HIPAA Business Associate Agreements (BAA)

  • Research data platforms handling regulated human subjects data

  • Any system formally classified as Confidential or Restricted under the University's Data GovernancePolicy

  • If your department relies on one of these applications for remote access, please continue to use the AVD in place or if one is not in place, submit a request for AVD here. 

More information coming soon!​​

Supporting Documentation & Links​

  • GSA Doc

  • Request Private Entra Access

  • Request Application AVD

More information coming soon!