Zero-Trust Access

Overview

Zero-Trust Access changes how staff reach sensitive systems: instead of trusting anyone inside the office network, every sign-in and every device is checked before access is granted. Access is scoped to what a role needs, and it is re-checked when something about the sign-in looks different.

The Information Services team is running the approach as a pilot with a small group of applications and teams before extending it across the General Conference.

What the project delivers

• Verified sign-ins: multi-factor authentication and sign-in risk checks for the applications in scope.

• Known devices: only enrolled, up-to-date devices can open sensitive systems.

• Least privilege: access tied to roles, reviewed on a schedule, removed when it is no longer needed.

Timeline

1. Design: choose the policies and the first applications to protect. Complete.

2. Pilot: enrol the pilot teams and devices and tune the policies. In progress.

3. Expand: bring the remaining sensitive systems under the same policies. Planned.

4. Operate: hand the policies to day-to-day operations with regular access reviews. Planned.

What staff will notice

Staff in the pilot sign in with a second factor and keep their devices enrolled and updated. Everyone else sees no change until their team is scheduled.

Questions

Use the contact form to reach the Information Services team about this project.