Jump to:
Baseline Expectations 2 Progress
As of April 16, 2021:
| Count | Percent of Total | |
|---|---|---|
| BE2-adhering Organizations | 201 | 26% |
| BE2-adhering IdPs | 163 | 28% |
| BE2-adhering SPs | 1319 | 26% |
| IdP with Error URL | 307 | 53% |
| SIRTFI-compliant IdPs | 209 | 36% |
| SIRTFI-compliant SPs | 1327 | 24% |
Happenings
BE2 Office Hour on April 20, 2021
The next BE2 Office Hour will be held on April 20, 2021 at 10AM PT/1PM ET. Join CTAB members to discuss your questions regarding Baseline Expectations 2.
Event: Baseline Expectations 2 Office Hour
Date and Time: April 20th, 2021 at 10AM PT/1PM ET
Connection Information:
https://internet2.zoom.us/j/98078837359?pwd=dzVYaDNHMDhQR1lNZ0RicmxWaU1JQT09
Meeting ID: 980 7883 7359
Passcode: 520783
One tap mobile
+16699006833,,98078837359# US (San Jose)
+13462487799,,98078837359# US (Houston)
Key Dates
| Date | Milestone |
|---|---|
| November 2, 2020 | Baseline Expectations 2 approved by InCommon Steering |
| November 17, 2020 | Implementation Kick-off, CAMP/ACAMP |
| January '21 - March '21 | CTAB begin contacting non-adhering participants |
| July 19 2021 | Transition: new/updated entities must adhere to BE |
Resources
- HOW TO: Meet Baseline Expectations
- Full Text: Baseline Expectations for Trust in Federation Version 2
- Full Text: Implementation Guidance for Baseline Expectations 2
- REFEDS Security Incident Response Framework (SIRTFI) v1.0
- Baseline Expectations on incommon.org
Archived Content
About Baseline Expectations 2
The second set of Baseline Expectations (BE2) adds three technical requirements aimed at improving security and the user experience. Implementation of BE2 is now under way. The InCommon Federation is expected to officially transition to BE2 on July 19, 2021.
The three BE2 elements are:
- Each Identity Provider and Service Provider must secure its connection endpoints with current and trusted encryption (TLS).
- All Identity Providers and Service Providers must comply with the SIRTFI international security response framework.
- All Identity Providers must include an error URL in metadata.
STATEMENT: All Identity Providers (IdP) and Service Providers (SP) service endpoints must be secured with current and community-trusted transport layer encryption.
When registering an entity (IdP or SP) in InCommon, all connection endpoints of that entity must be an https URL. The applied transport layer security protocol and associated cipher must be current and trusted by the community.
Popular security testing software such as the Qualys SSL Lab Server test offers a convenient way to test your server against these criteria and identify weaknesses. If using the Qualys SSL Lab Server test, an overall rating of A or better is considered meeting the requirements of the InCommon Baseline Expectations.
MORE: Clarification - Encrypt Entity Service Endpoints
STATEMENT: All entities (IdP and SP) meet the requirements of the SIRTFI v1.0 trust framework when handling security incidents involving federation participants
The SIRTFI trust framework v1.0 enables standardized and timely security incident response coordination among federation participants. When signaling and responding to security incidents within the federation, entity operators shall adhere to the process defined in the Sirtfi framework.
MORE: Clarification - Entity Complies with SIRTFI v1.0
STATEMENT: All IdP metadata must include an errorURL; if the condition is appropriate, SPs should use the IdP-supplied errorURL to direct the user to proper support.
IdP entity metadata must include a valid errorURL in its IDPSSODescriptor element.
An errorURL specifies a location to direct a user for problem resolution and additional support in the event a user encounters problems accessing a service. In SAML metadata for an IdP, errorURL is an XML attribute applied to the IDPSSODescriptor element.
When a service provider is unable to process an authentication assertion from an IdP, it may display within its error message a link to this URL to direct the user back to the IdP for additional assistance.