Pathlock SSO for PeopleSoft

100%

Status

Completed [Completed]

100% complete, updated on Mon 2/6/23 1:36 PM by Wendy Bentley

Changed Status from In Process to Completed.
Changed Health from Green to None.
Pathlock SSO for PeopleSoft was completed. Had been monitoring changes. Post change cleanup has been completed.

Details

Dates
Mon 5/9/22 - Mon 2/6/23
Acct/Dept
Office of the CIO
Service
Project and Change Management Office / Information Technology Project Request
Type
IT Projects / DoIT Project
Health
None - No health has been set
Portfolio(s)
Classification
Projects *Deactivated*
Created
Thu 5/12/22 1:24 PM
Modified
Mon 2/6/23 1:36 PM
Closed
Mon 2/6/23 1:36 PM

Change Impact

How will you measure the impact of this project?
What are some metrics or KPIs that will be used to measure success? Think about the five metrics to measure: quality, quantity, timeliness, cost, and customer satisfaction.
Removing CAS integration, improved availability for logging of security incidents, and reduction in one-off security roles.
What are the consequences of not doing this project?
For example: direct significant negative consequences to the University, unable to conduct basic services; failure to resolve customer complaints or requests; loss of opportunity for improved service delivery or efficiency. Please explain.
Failure to improve SSO security and reduce associated risks. Loss of opportunity to enforce conditional access rules. Failure to improve logging/review of user actions, role based access, and remote access review. Loss of opportunity to elevate roles in-session and log/alert on it.
How many employees will be impacted by this change?
Select the size of the employee population that will be impacted by this request.
Dozens
How many students will be impacted by this change?
Select the size of the student population that will be impacted by this request.
None

Project Costs

Funding Status
Funding is necessary and has been approved

Project Details

Divisional VP Support
Does your divisional VP support this request?
Yes
What would a successful solution look like?
What outcome will you have at the conclusion of this project? If this proposal is one of a multi-phase project, please explain your plans, goals, and timelines for subsequent phases.
Once Appsian is in place, it would allow us to use SAML instead of the CAS proxy currently in place for SSO to all PS instances both dev and prod. This platform will also allow for much improved logging/review of user actions.
Executive Sponsor Division
The executive sponsor's campus division.
Information Technology
Is there a mandated or requirement driving this request?
Please indicate whether or not this request is mandated or required. If it’s mandated or required, you will be asked to attach supporting documentation.
Required (not mandated) directly from Chico State President or VP
Campus Enduring Commitments & Strategic Goals
For more information about the Campus Enduring Commitments and Strategic Priorities, please go to https://www.csuchico.edu/strategicplan/enduring... and https://www.csuchico.edu/strategicplan/.
Strategic Priority: Resilient and Sustainable Systems

Project Resources & Effort

What resources will this project require?
Identify the department and/or individuals that might need to work on this project and the estimated number of hours required for each individual.
2hrs. time for a PeopleSoft Admin (unidentified as of now) working with the vendor.
2hrs. time with (Greg Coates or his alternate) for configuring connectivity with Fischer.
1.5 hrs. Initial meeting with Appsian project manager.
5hrs. testing functionality
2-4 hrs. Configuring logging to our Splunk instance (or alternative log repository). James Gordon

Greg Coates, Ryan Richter, Joseph Linn-Galan will all be involved, Greg/Joseph as primary for Fischer/SSO, Joseph for SSO decommission away from the current method. Ryan Richter will back up both. James Gordon to be involved in Splunk connectivity.
DoIT Departments Involved
Any Division of IT departments that will be involved in this project.
EAPP (Enterprise Applications)
ISEC (Information Security)
Complexity of Implementation
What is the complexity of the project?
High (significant/complex interfaces/impacts/dependencies)
What is the solution type?
The solution type translates to the level of impact on IT staffing and technology maintenance. Based on consultation with your IT representative, pick the best fit for your proposed solution.
New features in an existing system, wide breadth/depth

Description

Monique would like to move forward with the Appsian Security Platform (ASP) for PeopleSoft. ASP combines sophisticated controls to strengthen authentication, dynamically control user access, limit ‘sensitive’ data exposure, and provide granular visibility. Legacy ERP customers can create a ‘data-centric’ strategy to detect/prevent/respond to risk while proving regulatory compliance. This solution is already utilized at 19 other campuses and would allow our campus to resolve the mobile login issue that currently exists. The goal is to limit the scope to only configuring Single Sign On in our development and production instances, and utilize the improved logging capabilities.

Systems Affected

  1. PeopleSoft CFS

  2. PeopleSoft CS

  3. PeopleSoft HR

Manager

CB
Craig Bentley

Sponsor

MS
Monique Sendze

Stakeholders (1)

CW
Chris Witthans
Information Security Officer
Responsible, Accountable, Consulted, Informed
Information Security / Information Security Officer
Wed 8/24/22 10:58 AM