\documentclass[]{article}

\usepackage[nonumberlist]{glossaries}
\usepackage{color}

\makeglossaries

\begin{document}

\newglossaryentry{access management system}
{
name={access management system},
plural={access management systems},
description={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.}
}

\newglossaryentry{assertion}
{
name={assertion},
plural={assertions},
description={
The identity information provided by an Identity Provider to a Service 
Provider.}
}

\newglossaryentry{attribute}
{
name={attribute},
plural={attributes},
description={
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.  }
}

\newglossaryentry{authentication}
{
name={authentication},
description={
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.  }
}

\newglossaryentry{authorization}
{
name={authorization},
description={
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.  }
}

\newglossaryentry{electronic identifier}
{
name={electronic identifier},
plural={electronic identifiers},
description={
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 
\textit{\gls{NetID}}, an employee or student ID, or a PKI certificate.  }
}

\newglossaryentry{electronic identity}
{
name={electronic identity},
description={
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.  }
}

\newglossaryentry{electronic identity credential}
{
name={electronic identity credential},
plural={electronic identity credentias},
description={
An electronic identifier and corresponding
\textit{\gls{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.  }
}

\newglossaryentry{electronic identity database}
{
name={electronic identity database},
description={
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.  }
}

\newglossaryentry{identity}
{
name={identity},
plural={identities},
description={
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 attribute might be relevant in any situation depend on 
the context in which it is being questioned.  }
}

\newglossaryentry{identity management system}
{
name={identity management system},
plural={identity management systems},
description={
A set of standards, procedures and technologies that provide 
electronic credentials to individuals and maintain authoritative 
information about the holders of those credentials.  }
}

\newglossaryentry{Identity Provider}
{
name={Identity Provider},
plural={Identity Providers},
description={
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.  }
}

\newglossaryentry{NetID}
{
name={NetID},
description={
An electronic identifier created specifically for use with on-line 
applications. It is often an integer and typically has no other 
meaning.  }
}

\newglossaryentry{personal secret}
{
name={personal secret},
description={
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.  }
}

\newglossaryentry{Service Provider}
{
name={Service Provider},
plural={Service Providers},
description={
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.}
}


\title{INCOMMON FEDERATION: \\
PARTICIPANT OPERATIONAL PRACTICES\\
LIGO-T1200146-v4}
\date{May 19, 2014}
\maketitle

Participation in the InCommon Federation (``Federation'')
enables a federation participating organization
(``Participant'') to use Shibboleth \textit{\gls{identity}}
\textit{\gls{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 \textit{\gls{attribute}} \textit{\glspl{assertion}} 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 \textit{\glspl{identity management system}} and resource
\textit{\glspl{access management system}} as they trust their own.  

A fundamental expectation of Participants is that they provide
authoritative and accurate \textit{\gls{attribute}} \textit{\glspl{assertion}} to other
Participants, and that Participants receiving an \textit{\gls{attribute}}
\textit{\gls{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 \textit{\gls{identity management
system}}, including the \textit{\gls{identity}} \textit{\glspl{attribute}}
that are supported, or resource access management system
registered for use within the Federation.

Two criteria for trustworthy \textit{\gls{attribute}} \textit{\glspl{assertion}} by Identity
Providers are: (1) that the \textit{\gls{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.,
\textit{\gls{authentication}} and \textit{\gls{authorization}}
standards, security practices, risk assessment, change
management controls, audit trails, etc.). 

InCommon expects that \textit{\glspl{Service Provider}}, who
receive \textit{\gls{attribute}} \textit{\glspl{assertion}}
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\footnote[1]{Such permission
already might be implied by existing contractual agreements.}
of the identity information providing Participant.  

InCommon requires Participants to make available to all other
Participants answers to the questions below.\footnote[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.} 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.


\section{Federation Participant Information}

\subsection{}
The InCommon Participant Operational Practices
information below is for:

\begin{description}
\item[InCommon Participant organization name:] 
\textcolor{blue}{LIGO Scientific Collaboration}
\item[The information below is accurate as of this date:]
\textcolor{blue}{March 21, 2012}
\end{description}

\subsection{Identity Management and/or Privacy information}
Additional information about the Participant's \textit{\gls{identity}}
management practices and/or privacy policy regarding personal
information can be found on-line at the following location(s):

\footnotesize
\textcolor{blue}{
http://dcc.ligo.org/cgi-bin/DocDB/RetrieveFile?docid=89243
}
\normalsize

\subsection{Contact information}
The following person or office can answer questions about the Participant's \textit{\gls{identity}} 
management system or resource access management policy or practice.

\begin{description}
\item[Name:] \textcolor{blue}{Scott Koranda}
\item[Title or role:] \textcolor{blue}{LIGO Identity
Management Project Lead Architect}
\item[Email address:] \textcolor{blue}{scott.koranda@ligo.org}
\item[Phone:] \textcolor{blue}{+1 414 229 5056}
\item[FAX:] \textcolor{blue}{+1 414 229 5589}
\end{description}

\section{Identity Provider Information}

The most critical responsibility that an IdentityProvider
Participant has to the Federation is to provide trustworthy
and accurate \textit{\gls{identity}} \textit{\glspl{assertion}}.\footnote[3]{
A general note regarding \textit{\glspl{attribute}} and recommendations within
the Federation is available here:
http://www.incommonfederation.org/\textit{\glspl{attribute}}.html }
It is important for a \textit{\gls{Service Provider}} to know how your
\textit{\gls{electronic identity}} credentials are issued and how reliable
the information associated with a given credential (or person)
is. 

\subsection*{Community}

\subsection{}
If you are an \textit{\gls{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?

\textcolor{blue}{All staff of the LIGO Laboratory and all members of the LIGO
Scientific Collaboration are eligible to receive a LIGO
electronic \textit{\gls{identity}}. Additionally members of the Virgo project
needing access to LIGO resources are eligible. Certain guests
of LIGO approved by the LIGO Directorate, including NSF
program managers and advisory panel members, are also eligible
to receive an electronic \textit{\gls{identity}}.}

\subsection{}
``Member of Community''\footnote[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 \textit{\gls{electronic
identity database}}.
See http://www.educause.edu/eduperson/}
is an \textit{\gls{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 \textit{\gls{assertion}} might apply to anyone whose
affiliation is ``current student, faculty, or staff.''  
 
What subset of persons registered in your \textit{\gls{identity}} management
system would you identify as a ``Member of Community'' in
Shibboleth \textit{\gls{identity}} \textit{\glspl{assertion}} to other InCommon Participants?

\textcolor{blue}{The subset of persons registered who would be identified as a
``Member of Community'' and asserted to other InCommon
Participants include all LIGO Laboratory staff and LIGO
Scientific Collaboration members. Virgo collaboration members
and other guests of LIGO would not be identified as a ``Member
of Community''.}

\subsection*{Electronic Identity Credentials}

\subsection{}
Please describe in general terms the administrative process
used to establish an \textit{\gls{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.''

\textcolor{blue}{Enrollment in the MyLIGO service results in the
creation of an electronic \textit{\gls{identity}}.  Enrollment for LIGO
Laboratory staff is approved by the LIGO Director or the
Deputy Director. Enrollment for LIGO Scientific Collaboration
members is approved by the principal investigator (PI) of the
group that has signed a MOU with the LIGO Scientific
Collaboration and the LIGO Laboratory.}

\subsection{}
What technologies are used for your \textit{\gls{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?

\textcolor{blue}{Kerberos 5 is used for electronic \textit{\gls{identity}}
credentials.}

\subsection{}
If your \textit{\glspl{electronic identity credential}} 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:

\textcolor{blue}{Clear text passwords are not transmitted.}

\subsection{}
If you support a ``single sign-on'' (SSO) or similar campus-wide
system to allow a single user \textit{\gls{authentication}} action to serve
multiple applications, and you will make use of this to
authenticate people for InCommon \textit{\glspl{Service
Provider}}, 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.  

\textcolor{blue}{LIGO utilizes the Shibboleth IdP and SP implementations for
SSO. Users authenticate to the IdP in one of two ways: (i)
login and password sent by the client using HTTPS as the
transport and then tested via the Kerberos KDC or (ii) via the
SPNEGO mechanism with negotiation to use a previously acquired
Kerberos TGT. The IdP session is 24 hours. SP sessions vary
from a default of 10 minutes to a standard of 24 hours for
services requiring extensive use of HTTP POST actions. In
support of specific use cases a SP session of 72 hours has
been allowed. User-initiated session termination with the SP
is supported.}

\subsection{}
Are your primary \textit{\glspl{electronic identifier}} 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?

\textcolor{blue}{eduPersonPrincipalName is unique for all time to the
individual to whom they are assigned.}

\subsection*{Electronic Identity Database}

\subsection{}
How is information in your \textit{\gls{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?

\textcolor{blue}{Enrollment and management of electronic identity and
associated information is accomplished using the MyLIGO
registry service. The LIGO Identity Management Project, under
the authority of the LIGO Computing Committee and the LIGO
Directorate manages the service in collaboration with LIGO
Laboratory staff. Individual members are allowed to update
some of their information including institutional contact
information, email forwarding, and authorship name.}

\subsection{}
What information in this database is considered ``public
information'' and would be provided to any interested party?

\textcolor{blue}{The LIGO Roster displays public information including name,
email address, institution affiliation, principal investigator
(PI) status, and LSC Council membership status.}

\subsection*{Uses of Your Electronic Identity Credential
System}

\subsection{}
Please identify typical classes of applications for which your
\textit{\gls{electronic identity}} credentials are used within your own
organization.  

\textcolor{blue}{Collaboration wikis, electronic notebooks, data
services}

\subsection*{Attribute Assertions}

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

\subsection{}
Would you consider your \textit{\gls{attribute}} \textit{\glspl{assertion}} to be reliable enough to:

\begin{itemize}
\item control access to on-line information databases licensed to your 
organization? \textcolor{blue}{Yes.}
\item be used to purchase goods or services for your organization?
\textcolor{blue}{Yes.}
\item enable access to personal information such as student loan status?
\textcolor{blue}{Yes.}
\end{itemize}

\subsection*{Privacy Policy}

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

\subsection{}
What restrictions do you place on the use of \textit{\gls{attribute}} information that you 
might provide to other Federation participants?

\textcolor{blue}{The information we provide be used only for the
intended purpose and that asserted attribute information be
handled in accord with any limitations expressed with the
conveyed attribute (e.g., time-to-live type restrictions).
}

\subsection{}
What policies govern the use of \textit{\gls{attribute}} information that you might release to 
other Federation participants?  For example, is some information subject to FERPA 
or HIPAA restrictions?

\textcolor{blue}{
No information is subject to FERPA or HIPAA restrictions.
}

\section{Service Provider Information}

\textit{\glspl{Service Provider}} 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.  \textit{\glspl{Service Provider}} must describe the basis on which
access to resources is managed and their practices with
respect to \textit{\gls{attribute}} information they receive from other
Participants.


\subsection{}
What \textit{\gls{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. 

\begin{itemize}
\item \textcolor{blue}{entityID: \footnotesize https://ligo.org/ligovirgo/cbcnote/shibboleth-sp}
    \begin{itemize}
    \item \textcolor{blue}{SP Information: This SP hosts the
    wiki for the LIGO/Virgo Compact Binary Coalescence (CBC) Data
    Analysis Working Group. All access requires authentication
    and authorization. There is no anonymous access.
    Authorization to non-LIGO/Virgo collaboration members
    is granted only by petition to the chairs of the CBC
    working group.}
    \item \textcolor{blue}{Required information: eduPersonPrincipalName}
    \end{itemize}
\end{itemize}


\subsection{}
What use do you make of \textit{\gls{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
\textit{\gls{attribute}} information, or make attribute
information available to partner organizations, etc.?

\begin{itemize}
\item \textcolor{blue}{entityID: \footnotesize https://ask.ligo.org/shibboleth-sp}
    \begin{itemize}
    \item \textcolor{blue}{eduPersonPrincipalName is displayed
    as an identifier in the application and recorded to identify the
    user that added or edited content. Email is also consumed and
    linked to the identity. Access to
    the web server is recorded using eduPersonPrincipalName
    and the client IP address.}
    \end{itemize}
\item \textcolor{blue}{entityID: \footnotesize https://losc-dev.ligo.org/shibboleth-sp}
    \begin{itemize}
    \item \textcolor{blue}{eduPersonPrincipalName is displayed
    as an identifier in the application and recorded to identify the
    user that added or edited content. 
    Access to
    the web server is recorded using eduPersonPrincipalName
    and the client IP address.}
    \end{itemize}
\item \textcolor{blue}{entityID: \footnotesize https://losc.ligo.org/shibboleth-sp}
    \begin{itemize}
    \item \textcolor{blue}{eduPersonPrincipalName is displayed
    as an identifier in the application and recorded to identify the
    user that added or edited content. 
    Access to
    the web server is recorded using eduPersonPrincipalName
    and the client IP address.}
    \end{itemize}
\item \textcolor{blue}{entityID: \footnotesize https://wiki.ligo.org/shibboleth-sp}
    \begin{itemize}
    \item \textcolor{blue}{eduPersonPrincipalName in a modified form is displayed
    as an identifier in the application and recorded to identify the
    user that added or edited content. 
    Access to
    the web server is recorded using eduPersonPrincipalName
    and the client IP address.}
    \end{itemize}
\item \textcolor{blue}{entityID: \footnotesize https://www.lsc-group.phys.uwm.edu/ligovirgo/cbcnote/shibboleth-sp}
    \begin{itemize}
    \item \textcolor{blue}{eduPersonPrincipalName is displayed
    as an identifier in a wiki and recorded to identify the
    user that added or edited content to the wiki. Access to
    the web server is recorded using eduPersonPrincipalName
    and the client IP address.}
    \end{itemize}
\end{itemize}

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

\begin{itemize}
\item \textcolor{blue}{entityID: \footnotesize https://ask.ligo.org/shibboleth-sp}
    \begin{itemize}
    \item \textcolor{blue}{eduPersonPrincipalName is displayed
    as an identifier in the application and recorded to identify the
    user that added or edited content. Email is also consumed and
    linked to the identity. Access to
    the web server is recorded using eduPersonPrincipalName
    and the client IP address. 
    Access to the web server log files is only
    allowed for approved administrators.}
    \end{itemize}
\item \textcolor{blue}{entityID: \footnotesize https://losc-dev.ligo.org/shibboleth-sp}
    \begin{itemize}
    \item \textcolor{blue}{eduPersonPrincipalName is displayed
    as an identifier in the application and recorded to identify the
    user that added or edited content. 
    Access to
    the web server is recorded using eduPersonPrincipalName
    and the client IP address.
    Access to the web server log files is only
    allowed for approved administrators.}
    \end{itemize}
\item \textcolor{blue}{entityID: \footnotesize https://losc.ligo.org/shibboleth-sp}
    \begin{itemize}
    \item \textcolor{blue}{eduPersonPrincipalName is displayed
    as an identifier in the application and recorded to identify the
    user that added or edited content. 
    Access to
    the web server is recorded using eduPersonPrincipalName
    and the client IP address.
    Access to the web server log files is only
    allowed for approved administrators.}
    \end{itemize}
\item \textcolor{blue}{entityID: \footnotesize https://wiki.ligo.org/shibboleth-sp}
    \begin{itemize}
    \item \textcolor{blue}{eduPersonPrincipalName in a modified form is displayed
    as an identifier in the application and recorded to identify the
    user that added or edited content. 
    Access to
    the web server is recorded using eduPersonPrincipalName
    and the client IP address.
    Access to the web server log files is only
    allowed for approved administrators.}
    \end{itemize}
\item \textcolor{blue}{entityID: \footnotesize https://www.lsc-group.phys.uwm.edu/ligovirgo/cbcnote/shibboleth-sp}
    \begin{itemize}
    \item \textcolor{blue}{eduPersonPrincipalName is displayed
    as an identifier in a wiki and recorded to identify the
    user that added or edited content to the wiki. Access to
    the web server is recorded using eduPersonPrincipalName
    and the client IP address.
    Access to the web server log files is only
    allowed for approved administrators.}
    \end{itemize}
\end{itemize}

\subsection{}
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?

\begin{itemize}
\item \textcolor{blue}{entityID: \footnotesize https://www.lsc-group.phys.uwm.edu/ligovirgo/cbcnote/shibboleth-sp}
    \begin{itemize}
    \item \textcolor{blue}{Only a limited set of system
    administrators have privileged access to the service.}
    \end{itemize} 
\end{itemize}

\subsection{}
If personally identifiable information is compromised, what
actions do you take to notify potentially affected
individuals?

\textcolor{blue}{The LIGO Laboratory Security Officer and the
LSC Security Officer will coordinate incident response and
compromise handling with the InCommon Federation incident
response teams. Incidents can be reported to the LIGO Incident
Response Team at lscirt@ligo.org}

\section{Other Information}

\subsection{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.

\textcolor{blue}{LIGO has deployed the Shibboleth Identity
Provider version 2.3.x and the Shibboleth Service Provider
version 2.4.x. LIGO supports only the SAML2 profiles and
bindings. The registered scope for scoped attributes is
@ligo.org}

\subsection{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 \textit{\gls{identity}} information you may have
provided?



\section*{Additional Notes and Details on the Operational
Practices Questions}

As a community of organizations willing to manage access to
on-line resources cooperatively, and often without formal
contracts in the case of non-commercial resources, it is
essential that each Participant have a good understanding of
the \textit{\gls{identity}} and resource management practices implemented by
other Participants.  The purpose of the questions above is to
establish a base level of common understanding by making this
information available for other Participants to evaluate.

In answering these questions, please consider what you would
want to know about your own operations if you were another
Participant deciding what level of trust to place in
interactions with your on-line systems.  For example:

\begin{itemize}
\item What would you need to know about an
\textit{\gls{Identity Provider}}
in order to make an informed decision whether to accept its
\textit{\glspl{assertion}} to manage access to your on- line resources or
applications?
\item What would you need to know about a \textit{\gls{Service
Provider}} in
order to feel confident providing it information that it might
not otherwise be able to have?
\end{itemize}

It also might help to consider how \textit{\glspl{identity
management system}} within a single institution could be used.

\begin{itemize}
\item What might your central campus IT organization, as a
\textit{\gls{Service Provider}}, ask of a peer campus \textit{\gls{Identity
Provider}} (e.g., Computer Science Department, central Library, or
Medical Center) in order to decide whether to accept its
identity \textit{\glspl{assertion}} for access to resources that the IT
organization controls?

\item What might a campus department ask about the central
campus \textit{\gls{identity management system}} if the department wanted to
leverage it for use with its own applications?
\end{itemize}

The numbered paragraphs below provide additional background to
the numbered questions in the main part of this document.

\begin{itemize}

\item[1.2] InCommon Participants who manage
\textit{\glspl{Identity Provider}}
are strongly encouraged to post on their website the privacy
and information security policies that govern their \textit{\gls{identity}}
management system.  Participants who manage
\textit{\glspl{Service Provider}}
are strongly encouraged to post their policies with respect to
use of personally identifying information.

\item[1.3] Other InCommon Participants may wish to contact
this person or office with further questions about the
information you have provided or if they wish to establish a
more formal relationship with your organization regarding
resource sharing.

\item[2] Many organizations have very informal processes for
issuing electronic credentials.  For example, one campus does
this through its student bookstore.  A \textit{\gls{Service
Provider}} may be
more willing to accept your \textit{\glspl{assertion}} to the extent that this
process can be seen as authoritative.

\item[2.1] It is important for a \textit{\gls{Service
Provider}} to have some
idea of the community whose \textit{\glspl{identity}} you may represent.
This is particularly true for \textit{\glspl{assertion}} such as the eduPerson
``Member of Community.''.  A typical definition might be
``Faculty, staff, and active students'' but it might also
include alumni, prospective students, temporary employees,
visiting scholars, etc.  In addition, there may be formal or
informal mechanisms for making exceptions to this definition,
e.g., to accommodate a former student still finishing a thesis
or an unpaid volunteer.

This question asks to whom you, as an \textit{\gls{Identity
Provider}}, will provide electronic credentials.  This is
typically broadly defined so that the organization can
accommodate a wide variety of applications locally.  The
reason this question is important is to distinguish between
the set of people who might have a credential that you issue
and the subset of those people who fall within your definition
of ``Member of Community'' for the purpose of InCommon
\textit{\gls{attribute}} \textit{\glspl{assertion}}.

\item[2.2] The \textit{\gls{assertion}} of ``Member of Community'' is often
good enough for deciding whether to grant access to basic
on-line resources such as library-like materials or websites.
InCommon encourages participants to use this
\textit{\gls{assertion}} only
for ``Faculty, Staff, and active Students'' but some
organizations may have the need to define this differently.
InCommon \textit{\glspl{Service Provider}} need to know if this has been
defined differently.

\item[2.3] For example, if there is a campus recognized office
of record that issues such electronic credentials and that
office makes use of strong, reliable technology and good
database management practices, those factors might indicate
highly reliable credentials and hence trustworthy \textit{\gls{identity}}
\textit{\glspl{assertion}}.

\item[2.4] Different technologies carry different inherent
risks.  For example, a userID and password can be shared or
``stolen'' rather easily.  A PKI credential or SecureID card is
much harder to share or steal.  For practical reasons, some
campuses use one technology for student credentials and
another for faculty and staff.  In some cases, sensitive
applications will warrant stronger and/or secondary
credentials.

\item[2.5] Sending passwords in ``clear text'' is a significant
risk, and all InCommon Participants are strongly encouraged to
eliminate any such practice.  Unfortunately this may be
difficult, particularly with legacy applications.  For
example, gaining access to a centralized calendar application
via a wireless data connection while you are attending a
conference might reveal your password to many others at that
conference.  If this is also your campus credential password,
it could be used by another person to impersonate you to
InCommon Participants.

\item[2.6] ``Single sign-on'' (SSO) is a method that allows a
user to unlock his or her \textit{\gls{electronic identity}} credential once
and then use it for access to a variety of resources and
applications for some period of time.  This avoids people
having to remember many different identifiers and passwords or
to continually log into and out of systems.  However, it also
may weaken the link between an \textit{\gls{electronic
identity}} and the actual person to whom it refers if someone
else might be able to use the same computer and assume the
former user's \textit{\gls{identity}}.  If there is no limit on the duration
of a SSO session, a Federation \textit{\gls{Service Provider}} may be
concerned about the validity of any \textit{\gls{identity}}
\textit{\glspl{assertion}} you might make.  Therefore it is
important to ask about your use of SSO technologies.

\item[2.7] In some \textit{\glspl{identity management system}}, primary
identifiers for people might be reused, particularly if they
contain common names, e.g. Jim Smith@MYU.edu.  This can create
ambiguity if a \textit{\gls{Service Provider}} requires this primary
identifier to manage access to resources for that person.

\item[2.8] Security of the database that holds information
about a person is at least as critical as the electronic
identity credentials that provide the links to records in that
database.  Appropriate security for the database, as well as
management and audit trails of changes made to that database,
and management of access to that database information are
important.

\item[2.9] Many organizations will make available to anyone
certain, limited ``public information.''  Other information may
be given only to internal organization users or applications,
or may require permission from the subject under FERPA or
HIPAA rules.  A \textit{\gls{Service Provider}} may need to know what
information you are willing to make available as ``public
information'' and what rules might apply to other information
that you might release.

\item[2.10] In order to help a \textit{\gls{Service Provider}} assess how
reliable your \textit{\gls{identity}} \textit{\glspl{assertion}} may be, it is helpful to
know how your organization uses those same \textit{\glspl{assertion}}. The
assumption here is that you are or will use the same \textit{\gls{identity}}
management system for your own applications as you are using
for federated purposes.

\item[2.11] Your answer to this question indicates the degree
of confidence you have in the accuracy of your \textit{\gls{identity}}
\textit{\glspl{assertion}}.

\item[2.12] Even ``public information'' may be constrained in
how it can be used.  For example, creating a marketing email
list by ``harvesting'' email addresses from a campus directory
web site may be considered illicit use of that information.
Please indicate what restrictions you place on information you
make available to others.

\item[2.13] Please indicate what legal or other external
constraints there may be on information you make available to
others.

\item[3.1] Please identify your access management requirements
to help other Participants understand and plan for use of your
resource(s).  You might also or instead provide contact
information for an office or person who could answer
inquiries.

\item[3.2] As a \textit{\gls{Service Provider}}, please declare what use(s)
you would make of \textit{\gls{attribute}} information you receive.

\item[3.3] Personally identifying information can be a wide
variety of things, not merely a name or credit card number.
All information other than large group \textit{\gls{identity}}, e.g., ``member
of community,'' should be protected while resident on your
systems.

\item[3.4] Certain functional positions can have extraordinary
privileges with respect to information on your systems.  What
oversight means are in place to ensure incumbents do not
misuse such privileges?

\item[3.5] Occasionally protections break down and information
is compromised.  Some states have laws requiring notification
of affected individuals.  What legal and/or institutional
policies govern notification of individuals if information you
hold is compromised?

\item[4.1] Most InCommon Participants will use Internet2
Shibboleth technology, but this is not required.  It may be
important for other participants to understand whether you are
using other implementations of the technology standards.

\item[4.2] As an \textit{\gls{Identity Provider}}, you may wish to place
constraints on the kinds of applications that may make use of
your \textit{\glspl{assertion}}.  As a \textit{\gls{Service
Provider}}, you may wish to make
a statement about how User credentials must be managed.  This
question is completely open ended and for your use.

\end{itemize}

\glsaddall

\clearpage

\renewcommand{\glspostdescription}{}

\printglossaries


 
 
 
\end{document} 
