RFI - Identity Access Management System (IAMS)

Request for Information (RFI)

Identity Access Management System (IAMS)
SUNY Fredonia
11/13/2024

Introduction

SUNY Fredonia is seeking information from qualified vendors for an Identity Access Management System (IAMS) that that is aligned with a framework of policies, processes, and technologies that permits the University to effectively manage digital identities and control user access to institutional resources. The IAMS should integrates seamlessly with our existing infrastructure, including Microsoft services, Ellucian Banner, Google Workspace Gmail, Brightspace, and Jaggaer. This RFI aims to gather insights on available solutions, including their functionalities, compatibility, and support. Open source solutions with commercial support will be considered.

Objectives

The primary goals of implementing an IAMS are to:

1. Assess current environment, develop and implement an IAM program

1. Implement a robust identity management system to meet IAM program requirements

1. Enhance access governance, governance, authentication & assurance

1. Enhance security and regulatory compliance through effective user management.

1. Streamline access to applications and resources.

1. Simplify user provisioning and de-provisioning processes.

1. Improve user experience across various platforms.

Current Environment

• Directory Services: Microsoft Active Directory

• Email Services: Gmail (Google Workspace)

• Learning Management System: Brightspace

• Procurement System: Jaggaer

• HRMS: Home Grown system utilizing SQL & Oracle tables, Asp.Net webforms, and classic ASP web solutions.

Required Components

Vendors should provide information on the following components and functionalities of their IAMS solutions:

1. User Provisioning and De-provisioning

• Automated workflows for onboarding and offboarding users.

• Role-based access control (RBAC) capabilities. Access Governance should be addressed with entitlements, Role Based Access Control (RBAC), Attribute Based Access Control (ABAC), group management, request/approval processes, and (re) certification.

• Self-service user management options.

2. Authentication and Single Sign-On (SSO)

• Support for SSO across Microsoft services, Gmail, Brightspace of Desire2Learn, and Jaggaer (Procurement Solutions).

• Multi-factor authentication (MFA) options and configurations.

• Authentication and Assurance should be addressed with Single Sign-On, Multifactor Authentication, Federation, Social Identity, ID Proofing & Level of Assurance.

• Support for various authentication protocols (SAML, OAuth, OpenID Connect).

3. Identity Governance and Administration

• Tools for managing user roles, permissions, and policies.

• Audit trails and reporting capabilities for compliance.

• Periodic access reviews and attestation processes.

4. Integration Capabilities

• Pre-built connectors for Microsoft Active Directory, Gmail, Brightspace of Desire2Learn, and Jaggaer.

• APIs for custom integration needs.

• Support for integration with additional applications in the future.

5. User Experience

• Intuitive user interface for both administrators and end-users.

• Mobile compatibility for user access.

• Customizable dashboards for monitoring and management.

6. Security Features

• Encryption of data at rest and in transit.

• Advanced threat detection and response capabilities.

• Support for regulatory compliance (e.g., GLBA, FERPA, GDPR).

7. Support and Training

• Documentation and training resources for administrators and users.

• Ongoing technical support options.

• Availability of community or user groups for knowledge sharing.

Submission Guidelines

Interested vendors should provide the following:

1. Company Overview

• Brief history, mission, and relevant experience in providing IAMS solutions for educational institutions.

2. Product Information

• Detailed description of the proposed IAMS solution, including features and functionalities.

3. Integration Experience

• Case studies or examples of successful integrations with Microsoft, Gmail, Brightspace, and Jaggaer.

4. Pricing Structure

• General pricing information, including licensing models and additional costs (e.g., implementation, support).

5. Implementation Timeline

• Estimated timeline for deployment and key milestones.

6. References

• Contact information for at least three educational institutions currently using the proposed solution.

Deadline

Please submit your response to this RFI by 12/5/2024 at 3:00pm

Contact Information & Questions

All questions and answers will be updated daily on the Questions file in the Documents tab. For any questions or clarifications regarding this RFI, please contact:

Janet Mayer
Director of Contracts
Janet.Mayer@fredonia.edu