Before purchasing software, review the central software licensing list provided by CU Software, a service collaboration between Cornell Information Technologies, Cornell Store’s Technology Connection, and Procurement and Payment Services that provides software to faculty, staff, and students to Cornell and affiliates worldwide.
If a title you’re looking for is not offered, talk to your local IT support representative or see the instructions on the Software Licensing page for information on software selection criteria and requesting new titles.
Before purchasing cloud services or software to be used on a Cornell-owned device, you are required to submit a Technology Risk Assessment (TRA) form, even if you have completed the IT Governance process.
After you submit a TRA request, the IT Security Office (ITSO) will assess whether additional processes or reviews will be required (e.g., review of export control terms, web accessibility compliance, GDPR terms, contract or a full technology risk assessment). Generally, the ITSO review will be completed within 1-2 business days after submission. If a full review is necessary, the average turnaround time is 2-4 weeks.
More information on IT's Security Assessment.
After completing the TRA form and receiving approval to proceed from the ITSO, you may proceed with purchasing cloud services, software as a service (SaaS), or software.
In all instances, the ITSO approval email must be attached to the transaction e-doc (i.e., I Want document, requisition, or procurement card receipt submission).
Submit a Statement of Need to IT Governance for any administrative IT application and related service.
A Statement of Need is required for any administrative IT application or related service that would require internal or external IT expertise or effort, or products, tools, or resources to develop, purchase, alter, upgrade, decommission, etc., an IT application or service, regardless of source of funds or availability of staff time. This includes IT applications or related services that are planned for use within a single department, center, college, or unit if the application requires expertise beyond that which a non-IT functional end user could provide.