[INCLUDE THIS DOCUMENT IF CONTRACTOR WILL PROVIDE ELECTRONIC AND INFORMATION RESOURCES AS DEFINED BY SECTION 2054.451, GOVERNMENT CODE: The specifications, representations, warranties and agreements set forth in Proposer’s responses to this document will be incorporated into the Agreement.
University is primarily a [Optional:______________][Optional: Microsoft products] environment.
If the EIR will be hosted by University, please describe the overall environment requirements for the EIR (size the requirements to support the number of concurrent users, the number of licenses and the input/output generated by the application as requested in the application requirements).
Hardware: If Proposer will provide hardware, does the hardware have multiple hard drives utilizing a redundant RAID configuration for fault tolerance? Are redundant servers included as well?
Operating System and Version:
Web Server: Is a web server required? If so, what web application is required (Apache or IIS)? What version? Are add-ins required?
Other Requirements: Are any other hardware or software components required?
Assumptions: List any assumptions made as part of the identification of these environment requirements.
Storage: What are the space/storage requirements of this implementation?
Users: What is the maximum number of users this configuration will support?
Clustering: How does the EIR handle clustering over multiple servers?
Virtual Server Environment: Can the EIR be run in a virtual server environment?
Indicate whether Proposer is willing to allow an audit by University or its representative.
If the user and administrative interfaces for the EIR are web-based, do the interfaces support Firefox on Mac as well as Windows and Safari on the Macintosh?
Manpower Requirements: Who will operate and maintain the EIR? Will additional University full time employees (FTEs) be required? Will special training on the EIR be required by Proposer’s technical staff? What is the estimated cost of required training.
Upgrades and Patches: Describe Proposer’s strategy regarding EIR upgrades and patches for both the server and, if applicable, the client software. Included Proposer’s typical release schedule, recommended processes, estimated outage and plans for next version/major upgrade.
Has the EIR been tested for application security vulnerabilities? For example, has the EIR been evaluated against the Open Web Application Security Project (“OWASP”) Top 10 list that includes flaws like cross site scripting and SQL injection? If so, please provide the scan results and specify the tool used. University will not take final delivery of the EIR if University determines there are serious vulnerabilities within the EIR.
Which party, Proposer or University, will be responsible for maintaining critical EIR application security updates?
If the EIR is hosted, indicate whether Proposer’s will permit University to conduct a penetration test on University’s instance of the EIR.
Is the EIR authentication Security Assertion Markup Language (“SAML”) compliant? Has Proposer ever implemented the EIR with Shibboleth authentication? If not, does the EIR integrate with Active Directory? Does the EIR support SSL connections to this directory service?
Does the EIR rely on Active Directory for group management and authorization or does the EIR maintain a local authorization/group database?
What logging capabilities does the EIR have? If this is a hosted EIR solution, will University have access to implement logging with University’s standard logging and monitoring tools, RSA’s Envision?
Does the EIR have an application programming interface (“API”) that enables us to incorporate it with other applications run by the University? If so, is the API .Net based? Web Services-based? Other?
Will University have access to the EIR source code? If so, will the EIR license permit University to make modifications to the source code? Will University’s modifications be protected in future upgrades?
Will Proposer place the EIR source code in escrow with an escrow agent so that if Proposer is no longer in business or Proposer has discontinued support, the EIR source code will be available to University.
Please complete the Voluntary Product Accessibility Template (“VPAT”) found at http://www.itic.org/index.php?submenu=resources&src=gendocs&ref=vpat&category=resources and submit the VPAT with Proposer’s proposal.]