INCOMMON FEDERATION: PARTICIPANT
OPERATIONAL PRACTICES

Participation in the InCommon Federation (“Federation”) enables a federation participating organization ("Participant") to use Shibboleth identity attribute sharing technologies to manage access to on-line resources that can be made available to the InCommon community.  One goal of the Federation is to develop, over time, community standards for such cooperating organizations to ensure that shared attribute assertions are sufficiently robust and trustworthy to manage access to important protected resources.  As the community of trust evolves, the Federation expects that participants eventually should be able to trust each other's identity management systems and resource access management systems as they trust their own. 

A fundamental expectation of Participants is that they provide authoritative and accurate attribute assertions to other Participants, and that Participants receiving an attribute assertion protect it and respect privacy constraints placed on it by the Federation or the source of that information.  In furtherance of this goal, InCommon requires that each Participant make available to other Participants certain basic information about any identity management system, including the identity attributes that are supported, or resource access management system registered for use within the Federation.

Two criteria for trustworthy attribute assertions by Identity Providers are: (1) that the identity management system fall under the purview of the organization’s executive or business management, and (2) the system for issuing end-user credentials (e.g., PKI certificates, userids/passwords, Kerberos principals, etc.) specifically have in place appropriate risk management measures (e.g., authentication and authorization standards, security practices, risk assessment, change management controls, audit trails, etc.).

InCommon expects that Service Providers, who receive attribute assertions from another Participant, respect the other Participant's policies, rules, and standards regarding the protection and use of that data.  Furthermore, such information should be used only for the purposes for which it was provided.  InCommon strongly discourages the sharing of that data with third parties, or aggregation of it for marketing purposes without the explicit permission[1] of the identity information providing Participant. 

InCommon requires Participants to make available to all other Participants answers to the questions below.[2]  Additional information to help answer each question is available in the next section of this document.  There is also a glossary at the end of this document that defines terms shown in italics.

1. Federation Participant Information

1.1 The InCommon Participant Operational Practices information below is for:

InCommon Participant organization name: Oregon State University     

The information below is accurate as of this date: 04/21/2014               

1.2 Identity Management and/or Privacy information

Additional information about the Participant’s identity management practices and/or privacy policy regarding personal information can be found on-line at the following location(s).

http://fa.oregonstate.edu/infosec-manual

http://fa.oregonstate.edu/gen-manual

1.3       Contact information

The following person or office can answer questions about the Participant’sidentity management system or resource access management policy or practice.

Name: Oregon State University, Information Services, Identity and Access Management

Email Address: IAMTeam@oregonstate.edu

2. Identity Provider Information

The most critical responsibility that an IdentityProvider Participant has to the Federation is to provide trustworthy and accurate identity assertions.[3]  It is important for a Service Provider to know how your electronic identity credentials are issued and how reliable the information associated with a given credential (or person) is.

Community

2.1 If you are an Identity Provider, how do you define the set of people who are eligible to receive an electronic identity?  If exceptions to this definition are allowed, who must approve such an exception?

We provide electronic identities to employees, students, emeriti, adjunct, courtesy faculty and other official associates.   Associate eligibility requirements can be found on the Business Affairs website.

2.2 “Member of Community”[4] is an assertion that might be offered to enable access to resources made available to individuals who participate in the primary mission of the university or organization.  For example, this assertion might apply to anyone whose affiliation is “current student, faculty, or staff.” 

What subset of persons registered in your identity management system would you identify as a “Member of Community” in Shibboleth identity assertions to other InCommon Participants?

All employees, students, and emeritus faculty.

Electronic Identity Credentials

2.3 Please describe in general terms the administrative process used to establish an electronic identity that results in a record for that person being created in your electronic identity database?  Please identify the office(s) of record for this purpose.  For example, “Registrar’s Office for students; HR for faculty and staff.”

Students are issued an account upon successful admission to the university. Student identity is verified using SSN when provided and via transcripts. The office of record for student information is the OSU Registrar’s Office. Employees are issued an account when hired. Employee identity is verified using SSN. The office of record for employee information is OSU Human Resources.

2.4 What technologies are used for your electronic identity credentials (e.g., Kerberos, userID/password, PKI, ...) that are relevant to Federation activities?  If more than one type of electronic credential is issued, how is it determined who receives which type?  If multiple credentials are linked, how is this managed (e.g., anyone with a Kerberos credential also can acquire a PKI credential) and recorded?

Electronic credentials in use today include username/password

2.5 If your electronic identity credentials require the use of a secret password or PIN, and there are circumstances in which that secret would be transmitted across a network without being protected by encryption (i.e., “clear text passwords” are used when accessing campus services), please identify who in your organization can discuss with any other Participant concerns that this might raise for them:

Our policy requires that passwords always be encrypted when transmitted. Concerns about OSU password usage can be addressed to the Chief Information Security Officer, David Nevin, in our Office of Information Security. (See Transmission of Protected Information policy.)

2.6 If you support a “single sign-on” (SSO) or similar campus-wide system to allow a single user authentication action to serve multiple applications, and you will make use of this to authenticate people for InCommon Service Providers, please describe the key security aspects of your SSO system including whether session timeouts are enforced by the system, whether user-initiated session termination is supported, and how use with “public access sites” is protected. 

We use Shibboleth to authenticate our users for InCommon. Our Shibboleth IDP delegates authentication to our existing campus SSO system, CAS (Central Authentication System). CAS Ticket-Granting-Tickets expire after 2 hours of inactivity. Users may manually log out of CAS at any time. Users should log out and close their browser when finished using a public access terminal.

2.7 Are your primary electronic identifiers for people, such as “net ID,” eduPersonPrincipalName, or eduPersonTargetedID considered to be unique for all time to the individual to whom they are assigned?  If not, what is your policy for re-assignment and is there a hiatus between such reuse?

Usernames are not reused.

Electronic Identity Database

2.8 How is information in your electronic identity database acquired and updated?  Are specific offices designated by your administration to perform this function?  Are individuals allowed to update their own information on-line?

Human Resources staff verify and populate legal name, department, title and reporting information for employees. Phone numbers and office location for employees are set by the Telecom department. Employees are allowed to set a preferred email address and home address. Registrar’s Office staff verify and populate legal name for students. Students provide home address and phone number information and can update this themselves. Student email addresses are provisioned for them automatically.

2.9 What information in this database is considered “public information” and would be provided to any interested party?

Release of information to third parties is subject to approval by the appropriate records custodian. For employees this is the HR department. For students this is the Registrar’s Office.

We do have a limited amount of information available in our public directory that can be accessed by anyone. For employees this includes name, job title and department, office address and phone, and email address. For students we publish information designated as Directory Information under FERPA, which includes: name, major and level, home address and phone, and email address. Students may opt out of including all or part of this information in our public directory.

Registrar documentation on information release can be found at the following locations Directory information and Non-Directory information

Uses of Your Electronic Identity Credential System

2.10 Please identify typical classes of applications for which your electronic identity credentials are used within your own organization. 

Learning Management System (Blackboard), email, file share, personal webpages, wireless network access, VPN, SMTP auth, helpdesk access, other web applications.

Attribute Assertions

Attributes are the information data elements in an attribute assertion you might make to another Federation participant concerning the identity of a person in your identity management system. 

2.11 Would you consider your attribute assertions to be reliable enough to:

[X] control access to on-line information databases licensed to your organization?

[ ] be used to purchase goods or services for your organization?

[X] enable access to personal information such as student loan status?

Privacy Policy

Federation Participants must respect the legal and organizational privacy constraints on attribute information provided by other Participants and use it only for its intended purposes.

2.12 What restrictions do you place on the use of attribute information that you might provide to other Federation participants?

Attribute release should only include information required for the specific application. Release of attribute data to third parties must be approved by the appropriate OSU records custodian. In particular, bulk unsolicited mailings are a violation of OSU’s acceptable use policy.

2.13 What policies govern the use of attribute information that you might release to other Federation participants?  For example, is some information subject to FERPA or HIPAA restrictions?

We are subject to FERPA restrictions. We are also subject to various State of Oregon Administrative Rules (OARs) applying to the Oregon University System and Oregon State University. Further information can be found in the Policy Manual

3. Service Provider Information

Service Providers are trusted to ask for only the information necessary to make an appropriate access control decision, and to not misuse information provided to them by Identity Providers.  Service Providers must describe the basis on which access to resources is managed and their practices with respect to attribute information they receive from other Participants.

3.1 What attribute information about an individual do you require in order to manage access to resources you make available to other Participants?  Describe separately for each service ProviderID that you have registered.

In general, we require the following attribute information:  eduPersonPrincipalName, primary affiliation.

3.2 What use do you make of attribute information that you receive in addition to basic access control decisions?  For example, do you aggregate session access records or records of specific information accessed based on attribute information, or make attribute information available to partner organizations, etc.?

We anticipate that some SPs may need to maintain cross-session state and preferences for users.   

We do not make any attribute information that SPs receive from non-Oregon State University IdPs in the InCommon Federation available to non-Oregon State University organizations.

3.3 What human and technical controls are in place on access to and use of attribute information that might refer to only one specific person (i.e., personally identifiable information)?  For example, is this information encrypted?

All administrative data access is required to comply with the Information Systems baseline Standards of Care policy

We are subject to FERPA and State of Oregon Administrative Rules (OARs) applying to the Oregon University System and Oregon State University.

3.4 Describe the human and technical controls that are in place on the management of super-user and other privileged accounts that might have the authority to grant access to personally identifiable information?

All administrative data access is required to comply with the Information Systems baseline Standards of Care policy

We are subject to FERPA and State of Oregon Administrative Rules (OARs) applying to the Oregon University System and Oregon State University.

3.5 If personally identifiable information is compromised, what actions do you take to notify potentially affected individuals?

Actions are taken in accordance with our Information Security Policies.  See 502: Incident Response and Escalation policy

Other Information

4.1 Technical Standards, Versions and Interoperability

Identify the version of Internet2 Shibboleth code release that you are using or, if not using the standard Shibboleth code, what version(s) of the SAML and SOAP and any other relevant standards you have implemented for this purpose.

We use Shibboleth IDP version 2.3.8.

4.2 Other Considerations

Are there any other considerations or information that you wish to make known to other Federation participants with whom you might interoperate? For example, are there concerns about the use of clear text passwords or responsibilities in case of a security breach involving identity information you may have provided?

Any security related incidents should be reported to Information.SecurityOffice@oregonstate.edu

Glossary

 

access management system

The collection of systems and or services associated with specific on-line resources and/or services that together derive the decision about whether to allow a given individual to gain access to those resources or make use of those services.

assertion

The identity information provided by an Identity Provider to a Service Provider.

attribute

A single piece of information associated with an electronic identity database record.  Some attributes are general; others are personal.  Some subset of all attributes defines a unique individual.

authentication

The process by which a person verifies or confirms their association with an electronic identifier.  For example, entering a password that is associated with an UserID or account name is assumed to verify that the user is the person to whom the UserID was issued.

authorization

The process of determining whether a specific person should be allowed to gain access to an application or function, or to make use of a resource.  The resource manager then makes the access control decision, which also may take into account other factors such as time of day, location of the user, and/or load on the resource system.

electronic identifier

A string of characters or structured data that may be used to reference an electronic identity.  Examples include an email address, a user account name, a Kerberos principal name, a UC or campus NetID, an employee or student ID, or a PKI certificate.

electronic identity

A set of information that is maintained about an individual, typically in campus electronic identity databases.  May include roles and privileges as well as personal information.  The information must be authoritative to the applications for which it will be used.

electronic identity credential

An electronic identifier and corresponding personal secret associated with an electronic identity.  An electronic identity credential typically is issued to the person who is the subject of the information to enable that person to gain access to applications or other resources that need to control such access.

electronic identity database

A structured collection of information pertaining to a given individual.  Sometimes referred to as an "enterprise directory."  Typically includes name, address, email address, affiliation, and electronic identifier(s).  Many technologies can be used to create an identity database, for example LDAP or a set of linked relational databases.

identity

Identity is the set of information associated with a specific physical person or other entity.  Typically an Identity Provider will be authoritative for only a subset of a person’s identity information.  What identity attributes might be relevant in any situation depend on the context in which it is being questioned.

identity management system

A set of standards, procedures and technologies that provide electronic credentials to individuals and maintain authoritative information about the holders of those credentials.

Identity Provider

A campus or other organization that manages and operates an identity management system and offers information about members of its community to other InCommon participants.

NetID

An electronic identifier created specifically for use with on-line applications. It is often an integer and typically has no other meaning. 

personal secret (also verification token)

Used in the context of this document, is synonymous with password, pass phrase or PIN.  It enables the holder of an electronic identifier to confirm that s/he is the person to whom the identifier was issued.

Service Provider

A campus or other organization that makes on-line resources available to users based in part on information about them that it receives from other InCommon participants.

 

[1] Such permission already might be implied by existing contractual agreements.

[2] Your responses to these questions should be posted in a readily accessible place on your web site, and the URL submitted to InCommon.  If not posted, you should post contact information for an office that can discuss it privately with other InCommon Participants as needed.  If any of the information changes, you must update your on-line statement as soon as possible.

[3] A general note regarding attributes and recommendations within the Federation is available here: http://www.incommonfederation.org/attributes.html

[4] "Member" is one possible value for eduPersonAffiliation as defined in the eduPerson schema.  It is intended to include faculty, staff, student, and other persons with a basic set of privileges that go with membership in the university community (e.g., library privileges).  “Member of Community” could be derived from other values in eduPersonAffiliation or assigned explicitly as “Member” in the electronic identity database.  See http://www.educause.edu/eduperson/