Explore the VRA process, supplier risk considerations, and procurement requirements for new and existing technology.
Action | Description |
IT Consultation | 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:
|
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: |
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: |
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.
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. |
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: Consult with the FOA GRC Team for guidance about risk acceptance decisions. |
Pre-Procurement & | Data and Technology Assessment Form
UC Terms & Conditions For P3 or P4 classifications
If HIPAA data is involved: A Business Associates Agreement (BAA) may be required. |
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:
|