Risk Management Policy
Policy Owner: Luacs
Effective Date: 01.03.2025
Purpose
To define actions to address Tekai information security risks and opportunities. To define a plan for the achievement of information security and privacy objectives.
Scope
Risk Management Statement
Inadequate IT risk management exposes Tekai to risks including compromise of Tekai or customer network systems, services and information, cyber-attacks, contractual, or legal issues. Tekai will ensure that risk management plays an integral part in the governance and management of the organization at a strategic and operational level. The purpose of a risk management policy is designed to ensure that it achieves its stated business plan aims and objectives.
Risk Management Strategy
Tekai has developed processes to identify those risks that will hinder the achievement of its strategic and operational objectives. Tekai will therefore ensure that it has in place the means to identify, analyze, control and monitor the strategic and operational risks it faces using this risk management policy based on best practices.
Tekai will ensure the risk management strategy and policy are reviewed regularly and that internal audit functions are responsible for ensuring:
Practical Application of Risk Management
Tekai has adopted a standard format for use in the identification of risks, their classification, and evaluation.
The format is based on the following NIST and ISO standards and frameworks:
Risks are assessed and ranked according to their impact and their likelihood of occurrence. A formal Risk Assessment, and network penetration tests, will be performed at least annually and shall take into consideration the results of any technical vulnerability management activities performed in accordance with the Operations Security Policy.
Risk Categories
Some risks are within the control of Tekai whilst others may be only to a lesser degree. Tekai will therefore take an approach that will identify those risks and classify the risks according to the following categories:
Each risk will be assessed as to its likelihood and impact. Both impact and likelihood are assessed on a scale of 1-5. Impact can range from 1 ("Very low impact") to 5 ("Very high impact") and likelihood can range from 1 ("Very unlikely") to 5 ("Very likely").
Risk Criteria
The criteria for determining risk is the combined likelihood and impact of an event adversely affecting the confidentiality, availability, integrity, or privacy of organizational and customer information, personally identifiable information (PII), or business information systems.
For all risk inputs such as risk assessments, vulnerability scans, penetration test, bug bounty programs, etc., Tekai management shall reserve the right to modify risk rankings based on its assessment of the nature and criticality of the system processing, as well as the nature, criticality and exploitability (or other relevant factors and considerations) of the identified vulnerability.
Risk Response, Treatment, and Tracking
Risk will be prioritized and maintained in a risk register where they will be prioritized and mapped using the approach contained in this policy. The following responses to risk should be employed:
Where Tekai chooses a risk response other than "Accept" or "Avoid" it shall develop a Risk Treatment Plan
Risk Management Procedures
The procedure for managing risk will meet the following criteria:
Roles and Responsibilities
The following table outlines the specific risk management activities and responsibilities associated with each role.
Role | Responsibility |
CEO | Ultimately responsible for the acceptance and/or treatment of any risks to the organization. |
PrincipalEngineer | Can approve the avoidance, remediation, transference, or acceptance of any risk cited in the Risk Register. |
ITManager | Shall be responsible for the identification and treatment plan development of all Information Security related risks. This person shall be responsible for communicating risks to top management and adopting risk treatments in accordance with executive direction. |
Other Resources
04-ISMS Risk Assessment and Treatment Policy
For current Risk Register, see https://app.vanta.com/risk-management/risk-register
ISO 27001 / 27701 Coverage
ISO 27001 6.1; 6.2
Version | Date | Description | Author | Approved by |
1.0 | 01.03.2025 | Initial Implementation | Lucas |
APPENDIX A - Risk Assessment Process
The following is a high-level overview of the process used by Tekai to assess and manage information security related risks.
The process discussed below is based on NIST 800-30 and provides guidance to Tekai on how to:
The risk assessment process is comprised of the following steps:
Step 1: Prepare for the Assessment
In this step, the objective is to establish context for the risk assessment. This can be accomplished by performing the following:
Step 2: Conduct the Assessment
In this step, the objective is to produce a list of information security related risks that can be prioritized by risk level and used to inform risk response decisions. This can be accomplished by performing the following:
Step 3: Communicate and Share the Risk Assessment Results
In this step, the objective is to ensure that decision makers across the Tekai and executive leadership have the appropriate risk-related information needed to inform and guide risk decisions.
Step 4: Maintain the Assessment
In this step, the objective is to keep current, the specific knowledge related to the risks that Tekai incurs. The results of the assessments inform, and drive risk based decisions and guide ongoing risk responses efforts.
APPENDIX B - Risk Assessment Matrix and
Description Key
RISK= LIKELIHOOD * IMPACT | LIKELIHOOD |
|
|
|
|
IMPACT | Very unlikely: 1 | Unlikely:2 | Somewhat likely: 3 | Likely:4 | Very likely: 5 |
Very high impact: 5 | 5 | 10 | 15 | 20 | 25 |
High impact: 4 | 4 | 8 | 12 | 16 | 20 |
Medium impact: 3 | 3 | 6 | 9 | 12 | 15 |
Low impact: 2 | 2 | 4 | 6 | 8 | 10 |
Very low impact: 1 | 1 | 2 | 3 | 4 | 5 |
RISK LEVEL | RISK DESCRIPTION |
Low (1- 4) | A threat event could be expected to have a limited adverse effect on organizational operations, mission capabilities, assets, individuals, customers, or other organizations. |
Medium (5-12) | A threat event could be expected to have a serious adverse effect on organizational operations, mission capabilities, assets, individuals, customers, or other organizations |
High (15-25) | A threat event could be expected to have a severe adverse effect on organizational operations, mission capabilities, assets, individuals, customers, or other organizations. |
LIKELIHOODLEVEL | LIKELIHOOD DESCRIPTION | RATING (NUMERICAL) |
Very unlikely (1) | A threat event is so unlikely that it can be assumed that its occurrence may not be experienced.A threat source is not motivated or has no capability, or controls are in place to prevent or significantly impede the vulnerability from being exploited.Probability of Occurrence: < 5% in a 5-10 year period | 1 |
Unlikely (2) | A threat event is unlikely, but there is a slight possibility that its occurrence may be experienced.A threat source lacks sufficient motivation or capability, or controls are in place to prevent or impede the vulnerability from being exploited.Probability of Occurrence: 6% to 20% in a 2-5 year period | 2 |
Somewhat likely (3) | A threat event is likely, and it can be assumed that its occurrence may be experienced.A threat source is motivated or poses the capability, but controls are in place that may significantly reduce or impeded the successful exploitation of the vulnerability.Probability of Occurrence: 21% to 50% in a 1-2 year period | 3 |
Likely (4) | A threat event is likely, and it can be assumed that its occurrence will be experienced.A threat source is highly motivated or poses sufficient capability and resources, but some controls are in place that may reduce or impede the successful exploitation of the vulnerability.Probability of Occurrence: 51% to 80% in a 1 year period | 4 |
Very likely (5) | A threat event is highly likely, and it can be assumed that its occurrence will be experienced.A threat source is highly motivated or poses sufficient capability or resources, but no controls are in place or controls that are in place are ineffective and do not prevent or impede the successful exploitation of the vulnerability.Probability of Occurrence: > 80% in a 1 year period or less | 5 |
IMPACTLEVEL | IMPACT DESCRIPTION | RATING (NUMERICAL) |
Very low impact (1) | A threat event could be expected to have almost no adverse effect on organizational operations, mission capabilities, assets, individuals, customers other or organizations | 1 |
Low impact (2) | A threat event could be expected to have a limited adverse effect, meaning: degradation of mission capability yet primary functions can still be performed; minor damage; minor financial loss; or range of effects is limited to some cyber resources but no critical resources. | 2 |
Medium impact (3) | A threat event could be expected to have a serious adverse effect, meaning: significant degradation of mission capability yet primary functions can still be performed at a reduced capacity; minor damage; minor financial loss; or range of effects is significant to some cyber resources and some critical resources. | 3 |
High impact (4) | A threat event could be expected to have a severe or catastrophic adverse effect, meaning: severe degradation or loss of mission capability and one or more primary functions cannot be performed; major damage; major financial loss; or range of effects is extensive to most cyber resources and most critical resources. | 4 |
Very high impact (5) | A threat event could be expected to have multiple severe or catastrophic adverse effects on organizational operations, assets, individuals, other organizations, or the Nation. Range of effects is sweeping, involving almost all cyber resources. | 5 |