Changes between Version 3 and Version 4 of UAInCPOP.html


Ignore:
Timestamp:
06/21/11 10:32:26 (13 years ago)
Author:
dabantz@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • UAInCPOP.html

    v3 v4  
    1919 
    2020 
    21 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. 
     21!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. 
    2222 
    2323=== 1.  Federation Participant Information === 
    … …  
    4848 Name                   ''David Bantz'' 
    4949 
    50  Title or role         ''Chief Information Architect'' 
    51  
    52  Email address   ''Q@alaska.edu'' 
     50 Title or role         ''Chief Information Architect; Manager, Identity & Access Management'' 
     51 
     52 Email address   mailto:IAM@alaska.edu  ''IAM@alaska.edu'' 
    5353 
    5454 Phone                  ''+1 907 450 8314''                                                                  
    … …  
    7171''Non-terminated employees and students registered in the current term. '' 
    7272 
    73 ''Non-terminated employees include some who do not have a current assignment (for example, faculty on sabbatical or other leave).  While some calendar days on the University calendar are not in any term, for purposes of determining whether a student is registered “in the current term”, a date between terms designates the change from one term to the next.  For some purposes, such as maintaining access to email and portal accounts, we allow students to authenticate and maintain access to accounts up to three terms after their last registration; we would consider using this extended subset for “member of community” for specific services or resources. ''                   
     73''Non-terminated employees include some who do not have a current assignment (for example, faculty on sabbatical or other leave).  For purposes of determining whether a student is registered “in the current term”, a date between terms designates the change from one term to the next.  For some purposes, such as maintaining access to email and portal accounts, we allow students to authenticate and maintain access to accounts up to three terms after their last registration; we would consider using this extended subset for “member of community” for specific services or resources. ''                   
    7474 
    7575'''''Electronic Identity Credentials'''''[[br]] 
    76762.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.” 
    7777 
    78 ''As described in 2.1, current employees (faculty and staff) and students in our HR and Student information system of record (Banner) are automatically provisioned identities (currently via a once/day extract, but potentially more frequent data exports or database triggers).  Employee records are entered only by the institutions’ offices of human resources.  Students may register in person through registrars, or entirely online; payment is required to complete registration.  Unlike employees and students, identities of guests are typically not vetted; in addition to being designated a sponsored person with a responsible official sponsoring department in our IdM, their username and id are prefixed with the string “uaguest_”.   '' 
     78''As described in 2.1, current employees (faculty and staff) and students in our HR and Student information system of record (Banner) are automatically provisioned identities.  Employee records are entered only by the institutions’ offices of human resources.  Students may register in person through registrars, or entirely online; payment is required to complete registration.  Unlike employees and students, identities of guests are typically not vetted; in addition to being designated a sponsored person with a responsible official sponsoring department in our IdM, their username and id are assigned in name spaces that do not overlap the namespace used for employees and students. 
    7979 
    80802.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? 
    8181 
    82 ''Entities in the IdM have passwords that are stored in MIT Kerberos KDC, which is the backend credential store of the UA Enterprise LDAP directory; we use the Duke University Kerberos plug-in for using the external KDC.  Prior to October 2008 passwords were stored in the internal LDAP database; as these passwords are reset by users, their accounts are “kerberized.”  All active accounts should be kerberized by the end of CY2009.''                                                                              
     82''Entities in the IdM have passwords that are stored in the UA Enterprise LDAP directory and in one or more Windows Domains maintained by the UA System and campuses.  Passwords are created by users in a UA-in-house developed interface that enforces password entropy designed to meet NIST LoA 2 (that is, will have that entropy level if the LDAP directory and Domain accounts are locked appropriately after a number of failed attempts), with restrictions on the use of recorded PII, dictionary words, or prior passwords, and syntax constraint requiring characters from each of four character classes.  ''                                                                              
    8383 
    84842.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: 
    8585 
    86 ''We require connections to our LDAP and IdM web interfaces to use encrypted (https) sessions, so clear text passwords are not sent for LDAP authentication, for our CAS-like web central authentication service, nor, obviously, to the Kerberos KDC.  We expect applications using LDAP or our web authentication service to receive and send passwords using encrypted communications only, but realistically cannot guarantee compliance. ''                                                               
    87  
    88 ''Contact UA OIT Chief Information Security Officer Kerry Digou, sxkmd@email.alaska.edu or UA OIT Chief Information Architect David Bantz, Q@alaska.edu'' 
     86''We require connections to our LDAP, IdP, and in-house password reset application to use encrypted (ldaps or https) sessions, so clear text passwords are not sent for authentication via LDAP, CAS, or internally-developed central authentication service.''                                                               
     87 
     88''Contacts:[[br]] 
     89 UA OIT Chief Information Security Officer Kerry Digou, kerry.digou@alaska.edu [[br]] 
     90 UA OIT Chief Information Architect David Bantz, Q@alaska.edu'' 
    8991 
    90922.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.  
    9193 
    92 ''UA’s central authentication service for web-based applications is not strictly speaking an SSO service; each application requests authentication.  However, it is possible to authenticate to the service itself and then launch multiple subscribing services without explicitly re-authenticating.  This SSO-like function will not be used for or available to !InCommon Service Providers. Session time-outs are not in place.  Sessions are terminated with close of browser window(s) for that service.   ''        
     94''UA's Shibboleth IdP runs on servers maintained in our System Office Machine Room, staffed 24x7; access to this room is by approved staff only and requires a key card; all entries are logged.  Network access is protected by both hardware and software firewall rules.  Administrative access to the servers is limited to technical staff in infrastructure/servers and in identity and access management.'' 
     95 
     96 
     97''UA’s Shibboleth IdP enforces a session time-out of 8 hours.  Sessions are of course also terminated when users quit the browser used for web SSO.'' 
    9398 
    94992.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? 
    95100 
    96 ''Locally assigned identifiers and used within UA’s IdM are intended and controlled to be unique for all time to the individual to whom assigned.  (We do have legacy identifiers in use on some systems that have in the past been re-issued, but these are not used as unique identifiers within UA’s IdM.)  UA assigns a name-based “UA Username” and a number-like string “UA ID#” and a UID meaningful only internal to the IdM.  Kerberos principals are UAID#@ALASKA.EDU.  Sponsored accounts (guests) receive UA Username and UA ID# prefixed with the string “uaguest_”.'' 
     101''Locally assigned identifiers and used within UA’s IdM are intended and controlled to be unique for all time to the individual to whom assigned.  (We do have legacy identifiers in use on some systems that have in the past been re-issued, but these are not used as unique identifiers within UA’s IdM.)  UA assigns a name-based “UA Username” and a number-like string “UA ID#” and a UID meaningful only internal to the IdM.  Kerberos principals are UAID#@ALASKA.EDU.  Sponsored accounts (guests) receive similarly formatted UA Username and UA ID#, but in a different namespace to prevent collisions. Sponsored or guest identities are not recycled either. 
    97102 
    98103''UA Usernames may be changed if the person’s legal name changes, but the old UA Username is not available for re-issue.  UA ID# is intended and controlled to be permanent (does not change regardless of status of the person).     ''                                                                                      
    … …  
    1011062.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? 
    102107 
    103 ''For employees and students: A person’s legal name, preferred first name, student registration data (campus and program of each course, declared major and minor, credit hours), employment information (home department, employee type), assigned UA Username and UA ID# originate in and are updated from Banner only.  These data in Banner may generally be edited only by UA’s HR offices (for employees) and Registrar’s offices (for students.  Some employee data may be updated by the employee’s departmental administration.  Students may register and change registration on line. 
    104  
    105 Information about email accounts assigned to an individual may be entered and updated by other individuals with the IdM role of email administrator.  Email administrators are responsible for entering assigned email account information (address, authentication method, protocols supported) and may edit the mailRoutingAddress and advertised email address (each of which may have a different value). 
    106  
    107 Data not actively maintained in Banner HR or Banner SIS may be entered and updated by individual users; this includes: employee working title, secretary, office location, phone, advertised email address, URL, USPS mailing address.  In addition, individuals may edit their mailRoutingAddress, assign themselves vanity email addresses routed to their mailRoutingAddress, and edit the email addresses advertised in the public directory.        ''                                                                    
     108''For employees and students: A person’s legal name, preferred first name, student registration data (campus and program of each course, declared major and minor, credit hours), employment information (home department, employee type), assigned UA Username and UA ID# originate in and are updated from University systems of record (HRIS, SIS components of SunGardHE's Banner) only.  These data may generally be edited only by UA’s HR offices (for employees) and Registrar’s offices (for students).  Some employee data may be updated by the employee’s departmental administration.  Students may register and change registration on line. 'eduPersonAffiliation is maintained in the Directory based on the data in theses systems of record.'' 
     109 
     110''Information about email accounts assigned to an individual may be entered and updated by other individuals with the UA IdM role of email administrator.  Email administrators are responsible for entering assigned email account information (address, authentication method, protocols supported) and may edit the mailRoutingAddress and advertised email address (each of which may have a different value). 
     111 
     112''Data not actively maintained in Banner HR or Banner SIS may be entered and updated by individual users; this includes: employee working title, secretary, office location, phone, advertised email address, URL, USPS mailing address.  In addition, individuals may edit their mailRoutingAddress, assign themselves vanity email addresses routed to their mailRoutingAddress, and edit the email addresses advertised in the public directory.''                                                                  
    108113 
    1091142.9  What information in this database is considered “public information” and would be provided to any interested party? 
    … …  
    111116''For students who elect confidentiality of their records under FERPA: no data is public information; not even the existence of the record is public or would be confirmed even if an inquirer provides a identifier. 
    112117 
    113 For other students: UA has designated “directory information” that includes name, campus, major or program of study, email address; this is the data that would be provided and is available via our public electronic directory. 
    114  
    115 For employees: name, home and other departments or units with which affiliated, working title, email, campus (office) location(s), phone(s), mailing address, administrative contact (“secretary” attribute).  Note that not all this data is automatically populated so may not be present for some employees.       '' 
     118''For other students: UA has designated “directory information” that includes name, campus, major or program of study, email address; this is the data that would be provided and is available via our public electronic directory. 
     119 
     120''For employees: name, home and other departments or units with which affiliated, working title, email, campus (office) location(s), phone(s), mailing address, administrative contact (“secretary” attribute).  Note that not all this data is automatically populated so may not be present for some employees.       '' 
    116121 
    117122'''Uses of Your Electronic Identity Credential System''' [[br]] 
    1181232.10  Please identify typical classes of applications for which your electronic identity credentials are used within your own organization.  
    119124 
    120  ''web applications, including MyUA portal 
    121  
    122  ''Blackboard Course Management System 
    123  
    124  ''Online Directory (“phonebook”) also used to publish printed directories 
    125  
    126  ''Wireless network access (currently not used, but has been and may again) 
    127  
    128  ''Document imaging and management system 
    129  
    130  ''Help Desk (Service Center) incident tracking 
    131  
    132  ''Student Health Service application 
    133  
    134  ''Google Apps for Education     ''                                                                                                
    135  
     125  ''in-house web applications requiring authentication''[[br]] 
     126  ''Blackboard Course Management System''[[br]] 
     127  ''Online Directory (“phonebook”) also used to publish printed directories''[[br]] 
     128  ''Wireless network access'' [[br]] 
     129  ''Document imaging and management system''[[br]] 
     130  ''Help Desk (Service Center) incident tracking''[[br]] 
     131  ''Student Health Service application''[[br]] 
     132  ''Google Apps for Education     ''      [[br]]                                                                                          
    136133'''Attribute Assertions''' [[br]] 
    137134Attributes 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.  
    … …  
    143140[X] enable access to personal information such as student loan status?[[br]][[br]] 
    144141'''Privacy Policy'''[[br]] 
    145 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. 
     142Federation Participants must respect the legal and organizational privacy constraints on attribute information provided by other Participants and use it only for its intended purposes.[[br]] 
     143 
    1461442.13  What restrictions do you place on the use of attribute information that you might provide to other Federation participants? 
    147145 
    … …  
    1501482.14  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? 
    151149 
    152 ''Non-public information could be released only under explicit agreements reviewed and approved by appropriate UA executive authority; such agreements would spell out restrictions on use.  Member of…, current student, current employee, and departmental affiliations are public information.  However, we could not release the name or other uniquely identifying attributes of students electing to retain complete confidentiality of their educational record under FERPA.              '' 
     150''Non-public information could be released only under explicit agreements reviewed and approved by appropriate UA executive authority; such agreements would spell out restrictions on use.  Member of…, current student, current employee, and departmental affiliations are public information.  '' 
    153151 
    154152