Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The purpose of the Technology Procurement Process (TPP) is to gather information from purchase requestors prior to purchasing electronic and information technologies (EIT) to be compliant with the SUNY's security, accessibility, and procurement policies. This applies to all information technology and any equipment or interconnected system or subsystem of equipment that is used in the creation, conversion, or duplication of data or information. 

...

ALL new AND existing software, licensing, multi-year contracts/agreements, and hardware (technology) procurements MUST follow the Technology Procurement Process below:

Step 1: Submit a Technology Procurement Request Request - Customer completes the Technology Procurement Request Form and FREDMart Requisition. Upon submitting the TPP form, a Tracker ticket is created to initiate the review of the request. All other contracts and licenses should be sent directly to www.fredonia.edu/contractreview

...

  1. Utilizing the data risk category definitions and examples provided in the Data Risk Classification Policy found here: https://answers.fredonia.edu/x/j4I4, please confirm the risk category for the University data that you are requesting to be used with this solution. 
  2. In accordance with SUNY Procurement Policy, a HECVAT (HECVAT (Higher Education Community Vendor Assessment Tool) report is required. In the event of engaging with any cloud vendor, the HECVAT Lite or Full version must be completed by the vendor. In cases where Category II Private (e.g. Title IV or FERPA) or Category III Restricted data (e.g. PHI, Social Security Numbers, Credit Card Information, etc) are being stored, transmitted, or processed via the vendor, the full HECVAT must be provided by the vendor. If the vendor is supplying software that is designed to run on SUNY Fredonia’s local computing infrastructure (network, database, desktops/laptops, etc…) or is running a purpose-built application (often referred to as an agent) in conjunction with a piece of hardware then a HECVAT On-Premise is required. 
  3. In accordance with SUNY Procurement Policy, a 3rd Party attestation of security practices is required. Currently, the preferred response is that the vendor provides an SSAE16/18 SOC 2 Type 2 report. If a SOC2 Type 2 report is not available a suitable substitute may be provided at the discretion of the SUNY Fredonia Chief Information Officer and Chief Information Security Officer (CISO). At this time, it has been determined that both an ISO 27001 or a FedRAMP certification along with the detailed certificate review findings related to security controls are suitable substitutes for a SOC2 Type 2 report. The primary goal is for the vendor to provide an audit of their security practices from a 3rd party that attests to their overall security practices. 

...

  • All technology procurements or renewals must follow this process regardless of the type of funding (State vs. Non-state, AER etc.). NOTE: All other non-technology contracts and licenses should be sent directly to www.fredonia.edu/contractreview
  • All Research Foundation-funded technology procurements need to utilize the Technology Procurement Form and the above applicable steps will need to be completed.
  • Software or Software as a Service (SaaS) cannot be purchased via a state-issued procurement card and must be purchased via a state-issued Purchase Order.
  • This Technology Procurement Process can take up to 6 months to complete.

Additional Resources:

Fredonia IT Procurement Standards: http://answers.fredonia.edu/display/SC/Procurement+ITS Procurement Standards








Short URL to this page: 

...

Live Search
sizelarge
additionalpage excerpt
placeholderSearch Answers
typepage

...