Cyber threats are becoming more sophisticated, and research systems and research information are not immune to cyber-attacks. A Security Threat and Risk Assessment, or STRA, is an effective tool that is used to assess the security posture of a research environment. It also identifies compliance gaps and provides recommendations to improve cybersecurity. Below, we provide information about the UBC Research STRA process and what to expect before, during and after an STRA.
What is a STRA
A Security Threat and Risk Assessment (STRA) analyzes the security posture of a research project or service. For UBC research, it includes reviewing how information is collected, processed, and stored with a focus on cybersecurity and compliance with UBC Information Security requirements. The assessment identifies potential threats, gaps, and associated risks.
Why is it important
At UBC, researchers are responsible for securing research information against unauthorized access, disclosure, modification, or deletion. An STRA helps identify significant security gaps, supports compliance with UBC policies, and can help prevent cybersecurity incidents.
When is it required?
STRAs may be required to meet institutional policies, regulations, funding agency requirements, ethics board expectations, or contractual obligations. Not sure if you need one? Check the use cases here under "Are research project treated differently" or contact us for help.
Want to learn more about the STRA process?
Continue reading this page for more information about ARC's Research STRA process and how to prepare for it.
Not sure if you need an STRA?
We can help! Contact us at arc.support@ubc.ca, provide information about your initiative, and one of our subject matter expert will be in touch.
What to Expect Before, During and After a UBC Research STRA

Planning for an STRA
Planning for an STRA is essential to ensure a smooth and efficient process. With proper planning, you can organize and streamline information collection, you can quickly and accurately complete the STRA intake form, and address technical questions proactively. Planning for an STRA also allow you to anticipate potential roadblocks early, reduce delays and enable a more effective and timely STRA outcome.
Reach out early
Going through an STRA allows you to determine gaps within the solution you intend to use or develop. Request an STRA as soon as you know what solution you would like to use or a high-level architecture of the solution you wish to develop.
Allocate time
Depending on project complexity, a research STRA requires some time to complete since it assesses the architecture and processes relevant to your research environment. In simple environments, an STRA can be completed in as little as a few hours. In complex environments, the entire assessment process can take on the order of months. It is important that you allocate sufficient time for an STRA prior to beginning your project or launching your service.
To expedite the process:
- Familiarize yourself with UBC information Security Standards;
- Have potential solution providers or developers complete the ARC Security Compliance checklist to verify their suitability with UBC requirements;
- Ensure that the solution provider or development team can answer technical questions about the architecture and the security of the solution.
Do you have a technical resource available?
An STRA is a technical cybersecurity assessment. Someone with technical knowledge of the solution will need to provide information throughout the process (i.e.: Solution developer or provider).
Completing the Intake
During the STRA process, you’ll start by completing an intake form that captures key details about your initiative. The information you provide helps us determine the appropriate level of assessment for your research project or service—Levels 0, 1, or 2, which are defined in the next section. Completing the form can be challenging, so it’s important to set aside sufficient time. The more accurate and thorough your responses are, the better we can assess the security posture of your project/service, and ensure the process runs smoothly.

What's included in the intake form?
The ARC Research STRA intake form is comprised of questions related to:
- your research project/service;
- the research information involved;
- security controls and architecture of the solution/s and/or devices used in the project/service.
Some of the questions ask about compliance with the UBC Information Security Standards.
As you answer the questions in the form, think about your entire project lifecycle – think about what information is being collected, accessed, processed and stored and what solutions and devices are used during the entire process.
Please Note: If you are unsure about a response, you have the ability to choose the “I don’t know” option. While this may be an easy option to select, please be aware that forms with many “I don’t know” responses may require further review by a Research Cybersecurity and Compliance Specialist which impacts how quickly you will receive the STRA Report.
The intake form has been designed to limit the technical expertise required to complete the form as much as possible. However, due to the nature of STRAs, some required information is technical in nature. It is strongly recommended that you consult with a technical resource when completing the form. If you need assistance with the STRA Intake Form or need help interpreting the UBC policies and standards, contact the ARC Research Cybersecurity and Compliance team for help at arc.support@ubc.ca
What information is needed?
Research Information
You are asked to describe the research information involved in both free text and multi-choice fields. For the multi-choice fields, you are given sets of information types with examples, and you select those that most closely match the research information involved in your project/service.
Solution/s
You are asked to specify the solution/s involved for processing and storing research information in both free text and multi-choice fields. You are asked where the solution/s is/are hosted; the response to this question may be found in the solution provider’s privacy policy, security statement and/or terms of use/service, or you may need to ask the solution provider for this information.
Architecture
In a multi-choice field question, you are asked about architectural components existing in the solution/s you are using. Some examples of components are Webserver, Database server, VPN, Containers, APIs. These questions may best be responded to by the developer that built or configured the solution, or a technical resources for your initiative.
Security Controls
The STRA Intake Form has multi-choice field questions related to security controls. These questions may best be responded to by the developer that built or configured the solution, or a technical resources for your initiative.
The form asks about security controls applied to:
- The solutions used in the project/service
- computer and mobile devices
- Instruments
- Internet of Things
- Custom components
- Servers
- Data centres
Security controls covered in the form include:
- Information management and security (including encryption and backups)
- Physical security
- Systems and endpoints security
- User management and access controls
- Authentication and key management
- Network security
- Logging and Monitoring
How long does it takes to complete the intake?
The STRA Intake form takes about 30 mins to 1 hour to complete depending on the technical information available at the time of completion. When applicable, connect with the technical experts, developers, or solution providers involved in the configuration and management of the solution to assist with the technical questions within the form. Having the assistance of your technical experts or developers not only can decrease your completion time, but it also may decrease the number of “I don’t know” responses.
Need more time to find the necessary information?
No problem! Simply select "Save & Retrurn Later” option at the bottom of the form, note your unique return code and the link to your form. You can pick up where you left off once you have all the necessary information.]

Timeline, Expectations & Report
After you have completed the intake, our system will perform an initial assessment of your project/service and assign an STRA level. UBC Advanced Research Computing offers Research STRAs in 3 Levels that are defined below. The level required for an initiative is defined based on a number of elements including information classification, architecture design, security controls in place and potential risks associated with the initiative.
Level 0
A Level 0 STRA provides an automated assessment of a UBC research project or service against selected controls from the UBC Information Systems Policy (SC14) and associated standards. It is designed for low-risk initiatives and helps identify basic compliance issues and high-level cybersecurity risks.
Analysis Method: Fully automated (no expert input)
Additional information needed after intake is submitted: No
Timeline: Should your project/service qualify for L0, you will receive the STRA report within 10 minutes of the intake form submission.
Level 1
Building on the Level 0 assessment, Level 1 includes a brief review by a Research Cybersecurity and Compliance Specialist. Suitable for research projects or services with a medium-to-high risk profile, this level may require additional information to provide a more tailored and accurate assessment.
Analysis Method: Semi-Automated (includes a high-level expert review)
Additional information needed after intake is submitted: Yes
Timeline: Depending on workloads, you should expect to be contacted by one of our subject matter experts within 1 week after submitting the STRA intake form. Once we have all the necessary information, we strive to deliver the L1 STRA report within 2 weeks.
Level 2
In addition to the compliance assessment provided by the STRA Level 0, a Level 2 STRA offers a thorough analysis of the security posture of a research project or service, including a detailed technical assessment, an in-depth analysis of the project's/service's associated components, as well as a governance and research data management review. It is intended for high-to-very-high risk projects or services. Participation from developers or solution providers is strongly recommended, and technical familiarity with the solution is required.
Analysis Method: Manual (Expert-led, in-depth analysis)
Additional information needed after intake is submitted: Yes
Timeline: While every effort is made to complete the assessment in a timely manner, its completion timeline is often measured in months due to the complexity of the assessment. Depending on workloads, you should expect to be contacted by one of our subject matter experts within 1 week after submitting the STRA Intake Form to initiate the L2 process.
How can I expedite an L2 STRA?
Below are required L2 STRA supplementary documentation that expedite the information gathering process:
Researchers
Data Flow diagram: Think about your entire project’s data flow and not just the data flow within the primary solution.
Roles and Responsibilities: Think about the different roles that each member has in your team and their responsibilities. For example, if access to the solution or information is required, who will grant access to individuals and who will approve this access? Who will be responsible for removing access to the solution or information when access is no longer required?
Contract/Agreements: Agreements between you and the solutions provider or other groups are reviewed as part of the STRA.
Solution providers
Architecture Diagram: A complete and detailed architecture diagram is necessary for the STRA. A complete architecture diagram will have ALL the computer systems, components and security controls illustrated. This includes network segmentation, perimeter protection, IP addresses and ports, tunnels/VPNs and encrypted connections, and IDS/IPS.
Architecture Description List: This document completes the architecture diagram. It should include all components represented in the diagram, a description of each of the components, what each component contains, how each component interacts with other components in the architecture.
It is important to note that having documentation and information that is incomplete, inconsistent or unclear leads to a lengthier information collection and assessment time and impacts the production and completion of the STRA L2 report.
STRA Review and Risk Mitigation
Receiving the STRA report is not the end of the process. The report typically includes findings and compliance requirements that must be addressed. Acting on these findings is essential to ensure your initiative meets institutional and regulatory security and privacy requirements. Implementing the recommended mitigation plans promptly will help reduce risks and maintain compliance, thus ensuring your research is adequately protected.

Receiving the STRA report
Due to the confidential nature of the report, a one-time use download link is provided to you. Please download and save the STRA report document in a secure location. STRA reports are considered TLP:Amber which means information can only be shared on a need-to-know basis. You may share this document with stakeholders who require this information, for example the Research Ethics Board, Data Stewards, Funding Agencies, UBC Procurement, and/or your Academic Head of Unit.
Reviewing the STRA Report
Findings are common
Don’t panic if findings, gaps and risks are noted—most STRA includes them.
Involve stakeholders
It is essential that stakeholders, including decision-makers, participate in reviewing the STRA report, as action may be required to address findings and implement necessary mitigation measures.
Not a pass/fail exercise
Although you are encouraged to address all the gaps identified in the STRA report, the STRA is not a pass/fail exercise. The report serves as an informational resource to support decision-makers in prioritizing and addressing gaps based on their risk tolerance. ARC provides recommendations for mitigation but does not grant approval for mitigation actions.
The STRA report is organized into the following sections:
- Summary of the Initiative:
Provides an overview of your project or service, including timelines, supervisory roles, partnerships, and any related assessments such as a PIA, where applicable. - Information Management:
Outlines how information is handled within your initiative, covering classification, applicable requirements, sharing practices, ownership, and custody. - Information Processing:
Details the solutions used to process information, including solution providers, implemented security controls, and user management practices. - Information Storage:
Describes the solutions used for storing information, highlighting solution providers, security measures, and encryption methods. - Endpoint Security:
Focuses on endpoint devices that access, process, or store information related to your initiative. - Security Threat Risk Assessment:
Summarizes identified strengths and gaps, non-compliance with UBC policies and standards, and associated cybersecurity, information, and business risks.
Note: Each section may include additional details beyond the examples listed above, depending on the specifics of your initiative and the applicable STRA level.
Addressing Gaps and Risks
When reviewing the contents of the STRA report, consider the following:
- Compliance with UBC policies and standards is mandatory.
- You may wish to meet with your solution developer/s or provider to address the identified gaps.
- The developer/solution provider’s mitigation plan should be documented along with a timeline for mitigation completion for each gap.
- Administrative control gaps such as those related to SOPs, processes, or training must be addressed by the research team. Contact the Research Cybersecurity and Compliance team at arc.support@ubc.ca for guidance, if required.
- If you still wish to use the solution and some non-compliance items that cannot be mitigated, follow UBC information Security Standard M1 (ISS-M1).
Can I receive technical support from ARC to implement mitigation controls?
ARC does not currently offer technical implementation services. It is recommended to contact the solution or service developer/provider(s) for support with the implementation of mitigation controls.
Updates and Changes
The STRA process looks at a project or service at a point in time. As your project or service evolves, or the use of the system(s) changes, the initial STRA may no longer accurately assess these changes. Consider a revised STRA any time there is a material change to the systems or use of those systems.
Need more help?
We can help! Contact us at arc.support@ubc.ca, provide information about your initiative, and one of our subject matter expert will be in touch.
Do I need Privacy Impact Assessment?
A Privacy Impact Assessment (or PIA) is a risk-based analysis of personal information collection, use and disclosure, based on potential harm that could be caused by its loss, corruption, or disclosure. While research information is generally exempt from BC FIPPA, collection, use, sharing or disclosure for purpose other than research may require a PIA.
Additional Resources
To learn more about UBC security requirements, visit:
To learn more about UBC legal requirements, visit:
To learn more about UBC information privacy and security, visit:
To learn more about UBC information classification, visit:
Can’t find what you are looking for?
Send us an email at arc.support@ubc.ca to talk to one of our subject matter experts.