decorative image - vra process

VRA Overview for Technology Purchases

Explore the VRA process, supplier risk considerations, and procurement requirements for new and existing technology.

 

Action

Description

IT Consultation
(Optional)

Review the FOA VRA Process Checklist for an overview of the steps and resources needed to navigate the process from initial interest through procurement.

Engage your IT support team early to:

  • Align business needs with the right technology solutions.
  • Explore available tools and options.
  • Understand IT support requirements and responsibilities.
  • Identify security risks and applicable requirements.
  • Determine governance committee involvement and approval requirements.

Schedule a General Support Session with the FOA GRC Team

Classify the Business Use Case

Review the UCOP Protection Level Classification Guide for examples of data elements and their classification to determine the most suitable level for your use case (Protection Level 1 (P1), P2, P3 or P4).

For existing tools and contract renewals: 
Follow the ISO VRA Guidelines for renewal requirements. VRA Renewals provide an updated view of the vendor's security posture and must follow the schedule for the highest Protection Level associated with the use case:
      >> Renewal Schedule: P4 - Annually; P3 - Every 2 years; P2 - Optional; P1 - Not required

Initiate the VRA

Action: The product owner or program manager (primary department contact) is responsible for submitting an Information Security Office (ISO) VRA request form to initiate the campus VRA process.

The ISO reviews the use case details and determine if a VRA is necessary. An ISO analyst may contact you to align on specific details of the use case, data classification requirements, and assessment methodology. 

For existing tools and contract renewals:
If a previous VRA was completed, add a note on your form with the previous VRA ticket number and any changes to your business use case since the last VRA.

Risk Assessment Types

Is P3 or P4 in scope of the business use case?

If yes, the ISO will likely conduct a full assessment where the vendor is asked to provide a list of security documentation and compliance artifacts. The department contact is highly encouraged to prepare the vendor for the ISO's inquiry to gather security information to help reduce wait times. 
      >> Estimated duration: 2-3+ months.

  • Prepare the Vendor:
    Use the email template in the FOA VRA Process Checklist to prepare your vendor for their participation in the process and awareness of Appendix DS and the UC procurement process.

If no, the ISO will likely conduct a light version assessment (Multi-Point Intelligence Search) where the vendor is not contacted. Vendor preparation is not necessary. 
      >> Estimated duration: 2-4+ weeks.

Security Evidence Gathering

An ISO analyst will contact the vendor provided in your ISO VRA request form to request their completion of a new security questionnaire (HECVAT, SIG, CAIQ) or recently completed version, and relevant security documents designed to measure the vendor's security posture and risk for consideration before engaging in business with them. 

If the vendor becomes unresponsive, the ISO analyst may ask for your help to engage them.

VRA Report
An ISO risk assessor reviews the vendor's security documentation, conducts a Public Information search, and uses third-party risk tools to deliver a final report that identifies key risk findings and recommendations about the vendor and product/services in scope of the assessment. 
Report Debriefing
The ISO risk assessor may schedule a debriefing to review the final report, discuss key risks and recommendations, and address any concerns. Use this opportunity to ask questions and clarify findings or next steps related to your use case.
Department Response

Action: The primary department contact is responsible for adding responses and taking follow up actions to address the Department Response. Once final responses have been noted on the document, they are responsible for requesting approval from the Unit Head before proceeding with the purchase, renewal, or business engagement.

Instruction: Department Response Process 

Risk Acceptance: 
Formal Risk Acceptance Request may be necessary If the vendor was evaluated as high risk, could not be assessed, will not accept an Appendix Data Security (DS) or other applicable UC terms. 

Consult with the FOA GRC Team for guidance about risk acceptance decisions.

Pre-Procurement &
Contractual Considerations

Data and Technology Assessment Form
A signed form is required for technology purchases. Once the Unit Head's approval has been confirmed, our team works with the Technical UISL to obtain their signature on the form. 

UC Terms & Conditions For P3 or P4 classifications
Suppliers are required to accept Appendix DS as it establishes baseline protection for the Institution in the event a supplier suffers a security incident or breach, and more.

  • Responsibility for Primary Department Contact:
    Prepare the Appendix DS - Exhibit 1 form with all data types and regulations relevant to the product/service and business use case. Reference the VRA Published folder for a PDF copy of your ISO VRA Request form and review the sections for Use Case, Data Sensitivity, and Impact Assessment. 
    >> For support, contact Zainab Shakoor (Privacy Officer/Campus Counsel) for guidance on the data types and privacy selections.

If HIPAA data is involved: A Business Associates Agreement (BAA) may be required. 
         >> Contact Zainab Shakoor to confirm if a BAA is necessary.

Procurement 

Provide completed forms (signed DATA Form, Appendix DS Exhibit 1) to your Business Partner, Purchasing Team contact or Procurement Analyst/Buyer so they can finalize the procurement.

Additional Resources: