Jump to:
Meet Baseline Expectations 2 Now
InCommon Participants established the InCommon Baseline Expectations for Trust in Federation in 2018 as a means to increase trust and interoperability among InCommon federation participants and to define what they expect of each other, and of InCommon Operations.
The second iteration of Baseline Expectations (Baseline Expectations 2, or BE2) was ratified by the InCommon Steering Committee in late 2020. BE2 officially went into effect on July 19, 2021. All InCommon Participants are expected to update their registered entities to meet BE2 requirements by December 17, 2021.
Does my organization meet Baseline Expectations?
Visit the Baseline Expectations 2 Adherence by Organization page to see if your organization meets the requirements of Baseline Expectations 2.
If your organization still has entities that do not meet BE2 requirements, we need to hear from you. Please complete this Baseline Expectation 2 Acknowledgement Form to let us know.
Baseline Expectations 2 Progress
The BE2 Progress is updated weekly. The line graph and table below are updated every Monday using the published metadata from the prior Friday.
As of February 25, 2021:
Count | Percent of Total | |
|---|---|---|
BE2-adhering Organizations | 700 | 89% |
BE2-adhering IdPs | 529 | 92% |
BE2-adhering SPs | 5193 | 95% |
IdP with Error URL | 544 | 94% |
SIRTFI-compliant IdPs | 531 | 92% |
SIRTFI-compliant SPs | 5196 | 96% |
How are we doing on endpoint encryptions?
The following graphs illustrate the participants' progress toward strengthening connection endpoints. The graphs compare the data collected across five testing cycles between April 2021 and February 2022.
The encryption test data is updated approximately monthly.
Endpoint Encryption Test Results among InCommon IdPs
Apr 15 2021 | Jun 23 2021 | Jul 22 2021 | Aug 26 2021 | Spt 19 2021 | Oct 30 2021 | Dec 17 2021 | Jan 14 2022 | Feb 17 2022 | |
|---|---|---|---|---|---|---|---|---|---|
A | 186 | 251 | 323 | 370 | 380 | 398 | 412 | 414 | 417 |
B | 344 | 259 | 221 | 181 | 174 | 157 | 152 | 145 | 141 |
C | 10 | 8 | 6 | 2 | 2 | 2 | 2 | 1 | 2 |
F | 2 | 27 | 5 | 2 | 2 | 1 | 0 | 0 | 1 |
n/a | 39 | 37 | 32 | 27 | 21 | 25 | 16 | 17 | 16 |
Endpoint Encryption Test Results among InCommon SPs
Apr 15 2021 | Jun 23 2021 | Jul 22 2021 | Aug 26 2021 | Spt 19 2021 | Oct 30 2021 | Dec 17 2021 | Jan 14 2022 | Feb 17 2022 | |
|---|---|---|---|---|---|---|---|---|---|
A | 3263 | 3288 | 3574 | 3773 | 3823 | 3893 | 4029 | 4046 | 4053 |
B | 1473 | 1220 | 1205 | 1056 | 1049 | 982 | 915 | 907 | 876 |
C | 45 | 47 | 44 | 39 | 36 | 32 | 34 | 26 | 26 |
F | 23 | 270 | 17 | 26 | 35 | 34 | 25 | 23 | 58 |
n/a | 800 | 693 | 554 | 554 | 514 | 525 | 408 | 412 | 427 |
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
- Community Consensus for Baseline Expectations 2
- Consultation on Baseline Expectations 2
- Baseline Expectation 1 wiki archive
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.