Attachment J.2a Judiciary IDAM Requirements Checklist Amend 0003.pdf
PDF 75 KB Posted
- Attached to
- Enterprise Training Software BPA
- Solicitation number
- USCA25Q0045
- Issued by
-
Administrative Office of the U.S. Courts
About this file
This document contains Identity, Credential, and Access Management (ICAM) requirements for a federal contract opportunity with the Judiciary. The requirements specify that any proposed application or Software-as-a-Service (SaaS) solution must integrate with at least one of three enterprise identity providers: IBM Security Verify Governance (ISVG) and/or IBM Security Verify Access (ISVA), Microsoft Active Directory, or Microsoft Entra ID with Microsoft Active Directory Federation Services (AD FS). The solution must support federated identity with user account provisioning and Single Sign-On (SSO) using standards-based identity protocols.
The solution must support industry-standard identity and access management protocols including SAML 2.0, OAuth 2.0, OpenID Connect, and SCIM as applicable to authentication, authorization, and provisioning. Additional requirements include configurable identity attribute mapping and synchronization for exchanging identity and entitlement attributes; selection, mapping, and customization of unique user identifiers such as User Principal Name (UPN); group-based and role-based access control (RBAC/ABAC) using federated identity attributes; modern, FIPS-compliant cryptographic mechanisms to protect identity data in transit and at rest; and audit trails of login activity or product usage. The vendor must demonstrate experience in federal or enterprise environments.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| USCA25Q0045 0004.pdf | ||
| Attachment J.2 Requirements Questionnaire Amend 0003.xlsx | XLSX spreadsheet | |
| Attachment J.1 SOW Amend 0003.pdf | ||
| USCA25Q0045 Amend 0003.pdf | ||
| USCA25Q0045 Enterprise Training BPA Q and A Updated 10-3.xlsx | XLSX spreadsheet | |
| USCA25Q0045 Enterprise Training BPA Q and A Updated.xlsx | XLSX spreadsheet | |
| USCA25Q0045 Enterprise Training BPA Q and A.xlsx | XLSX spreadsheet | |
| Attachment J.3 Training Platform Price Workbook Amd 0002.xlsx | XLSX spreadsheet | |
| USCA25Q0045 Amd 0002.pdf | ||
| Attachment J.2 Requirements Questionnaire Amd 0002.xlsx | XLSX spreadsheet | |
| Attachment J.1 SOW Amd 0002.pdf | ||
| USCA25Q0045 0001 Due Date Extension.pdf | ||
| RFQ USCA25Q0045.pdf | ||
| Attachment J.1 SOW.pdf | ||
| Attachment J.2 Requirements Questionnaire.xlsx | XLSX spreadsheet | |
| Attachment J.3 Training Platform Price Workbook.xlsx | XLSX spreadsheet | |
| Attachment J.2a Judiciary IDAM Requirements Checklist.pdf |
Show all 17
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
ICAM requirements:
To ensure interoperability with the Judiciary’s Identity, Credential, and Access Management (ICAM) infrastructure, the application or Software-as-a-Service (SaaS) solution shall comply with the following requirements.
1. The application or SaaS solution shall support federated identity, including user account provisioning and Single Sign-On (SSO), using standards-based identity protocols. The solution must integrate with at least one of the following enterprise identity providers (IdPs):
1. IBM Security Verify Governance (ISVG) and/or IBM Security Verify Access (ISVA)
2. Microsoft Active Directory
3. Microsoft Entra ID as the authoritative provisioning source with Microsoft Active
Directory Federation Services (AD FS) as the authentication source
2. The solution shall support industry-standard identity and access management protocols commonly used in ICAM architectures (e.g., SAML 2.0, OAuth 2.0, OpenID Connect, SCIM), as applicable to authentication, authorization, and provisioning.
3. The solution shall support configurable identity attribute mapping and synchronization to enable the exchange of identity, credential, and entitlement attributes required for authorization and access control decisions.
4. The solution shall support selection, mapping, and customization of unique user identifiers, including User Principal Name (UPN), during federation and provisioning configuration.
5. The solution shall support group-based and/or role-based access control (RBAC/ABAC as applicable) using federated identity attributes to enforce authorization policies.
6. The solution shall employ modern, FIPS-compliant cryptographic mechanisms to protect identity data in transit and at rest, consistent with federal security standards.
7. The vendor shall provide audit trails of login activity or product usage with demonstrated experience in a federal or enterprise environments.
File details come from the government source that posted it. Updated .