A A Email Print Share

InCommon Participant Operational Practices (POP)

Federation Participant Information


1.1 The InCommon Participant Operational Practices information below is for:
InCommon Participant organization name: Duquesne University
The information below is accurate as of this date: April 28, 2017


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).
URL(s): http://www.duq.edu/cts/policies http://www.duq.edu/cts/accounts


1.3 Contact information
The following person or office can answer questions about the Participant's identity management system or resource access management policy or practice.
Name: Tom Dugas
Title or role: Director, Information Security/New Initiatives
Email address: dugast@duq.edu
Phone 412.396.6574 FAX 412.396.5144



Identity Provider Information


The most critical responsibility that an Identity Provider 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?
Students, faculty, staff, retirees, affiliates and special patrons are subject to the Duquesne University policies and receive a userID. Authorized personnel in sponsoring departments are required to submit requests for affiliates and special patrons to Human Resources for access approval.


2.2 "Member of Community" 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?
Anyone identified as current faculty, staff, student, retiree, affiliate, or special patron


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."
The Enrollment Management Group for students and the Office of Human Resources for faculty and staff.


The process for the establishment of electronic identity occurs for students at the time a deposit is recorded in our ERP and the student offer is accepted.
For employees it when their complete employment information is entered into our ERP system Banner.


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?
LDAP is used as the principal store for usernames/passwords. Secondarily, usernames are synced with Active Directory and ADFS.


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:
Passwords are not transmitted unencrypted.


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 provide SSO by virtue of the Shibboleth/IDP sign-on process. The standard IDP timeout mechanisms are enforced. User-initiated timeouts only exist by closing out the browser. We also have various application session timeouts and Active Directory timeouts for endpoints based on the role and areas of responsibilities.


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?
All electronic identifiers are unique to the individual and are never reassigned.


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?
The information is acquired and updated by the offices listed in 2.3 through manual and automated scripts populating the University's enterprise systems. Individuals cannot update their information online directly.


2.9 What information in this database is considered "public information" and would be provided to any interested party?
Information categorized as "directory information" is considered to be public 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.
Business Management Systems, Academic Management Systems, Library Systems, Network and IT systems, and Emergency/Security Systems.


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:
[YES] control access to on-line information databases licensed to your organization?
[YES] be used to purchase goods or services for your organization?
[YES] 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 information that we provide may only be used for the agreed upon business purpose. In may not be shared with other parties in detail or in aggregate without our expressed written consent.
Attribute information that we provide may only be used for the agreed upon business purpose. It may not be shared with other parties in detail or in aggregate without our expressed written consent.


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?
Some information is restricted by FERPA, HIPAA and other laws as well as University policies govern the release of attribute information which Duquesne University might release to Federation Participants.


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 resource ProviderID that you have registered.
Duquesne University is not currently a service provider.


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.?
N/A


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?
N/A


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?
N/A


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


4. 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.
IDP version 3.2.1


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?
In the case of a local identity breach, the Computing and Technology Services Information Security Team will work with Legal Affairs to notify those impacted. If outside organizations need to report a breach to Duquesne University, please use help@duq.edu and our team will handle the local coordination.