The detailed process for Risk Assessment and Management is consists of the following phases as shown in the diagram below.
Communication and Consultation
The objective of this phase is to
- improve the understanding of Information Security (IS) risks and the risk management process.
- ensuring that the interests of the stakeholders are understood and considered and
- securing endorsement and support for a treatment plan
Establishing the context
This phase defines the basic parameters for managing the Information security risk and sets the scope and criteria for the remaining process.
The context includes the organization’s external and internal environment and the purpose of the risk management activity.
This also includes consideration of the interface between the external and internal environments.
Identification of Assets
Once the context is established, the information and information processing assets within Tech Mahindra should be identified so that proper risk assessment and management can provide adequate protection.
- Valuation of Assets
To identify the business impact due to the loss of Confidentiality, Integrity, or Availability of an asset, it is necessary to evaluate each asset in terms of their importance to the business. Based on this business can identify, develop, and implement appropriate procedures for the protection of these assets.
Identification of Threat and Vulnerability pairs
Assets are subject to many kinds of threats that can exploit existing vulnerability of the systems, applications or services used by Tech Mahindra Once the Risk owner populates the Asset Inventory in Risk Assessment Template, the relevant risk description, category of risk and its references based on various threat and vulnerabilities along with possible safeguards will be prepopulated in the Risk Treatment Plan tab for the unique applicable asset blocks.
Asset Impact
The Risk owner needs to ascertain if a threat materializes its impact on the confidentiality, integrity and availability of the asset.
Impact Rating |
Impact Level |
Impact Description |
1 |
Low |
Low or Minor impact to the organization on threat exploiting the vulnerability. Minor incidents are those from which are short term, controllable and should be able to recover. With careful management of the incident and the implementation of appropriate safeguards, the financial loss and public embarrassment can be brought to a low level / minimal cost
|
2 |
Medium |
Medium impact to the organization on threat exploiting the vulnerability. Incidents at this level can be Medium and, with an immediate and appropriate response, the impact can be brought to a control.
|
3 |
High |
Significant impact and may cause considerable system outage and or loss of connected customers or business confidence, Significant potential financial losses, coupled with a public loss of credibility. Might result in compromise of large amount of information or services.
|
4 |
Critical |
Serious or Critical impact - May cause system extended outage or to be permanently closed, causing operation to resume in an alternate location. May result in complete compromise of organizations’ information or services, client confidential information or Personal Data Breach. May cause damage to the reputation of system management, Termination of the contract, penalties for Data Privacy Breach and/or notable loss of confidence in system resources/services, might require expenditure of significant resources to repair.
|
Probability of occurrence rating levels
A rating for the probability or likelihood of occurrence of a potential information security incident involving threat exploiting vulnerability should be given as per the following table:
Rating |
Probability ratings |
Probability range |
Description |
1 |
Low |
01% through 40% |
The probability of these Information Security threat happenings is considered to be very low (may happen in once in 1 - 3 years)
|
2 |
Medium |
41% through 60% |
It is considered a reasonable probability that this Information Security threat will occur. (may happen once a year) |
3 |
High |
61% through 80% |
It is considered to be a high probability that this threat will occur if corrective action is not applied. (may happen more than once a year) |
4 |
Critical |
81% through 99% |
It is considered a Critical probability that this threat will occur if corrective action is not applied. (may happen very frequently once in a month or so ) |
Determination and Analysis of Risk
The next step is the calculation of risk and its rating. Risk Rating, which is a value based on Business Impact (BI) and Probability of Occurrence ratings, which can take values as, per the below table:
Risk Evaluation
The risk evaluation process considers identification and selection of security measures (controls) for the identified high-risk levels for a given asset. The purpose of risk evaluation is to make decisions, based on the outcomes of risk analysis, about which risks need treatment and treatment priorities.
Risk treatment Process
Risk treatment involves identifying the range of options for treating risks, assessing these options and the preparation and implementation of treatment plans. Selecting the most appropriate option involves balancing the costs of implementing each option against the benefits derived from it.
Monitoring and Review
Ongoing monitoring and review of Risk management processes ensures that the management plan is relevant and up to date. Regular reviews to be done minimum once in a year or if there are any major changes in Business, operations, or technology.
The following documents will have to be maintained as a part of this Risk management process.
-
RA / RTP filled updated templates for Building, function, Applications, Event based and project Account / BU levels as applicable.
- Information Security Risk Register to be maintained at ISG level.
Risk Assessment and management Activities
Sr.No |
Input |
Process description |
Out put |
Ownership |
1 |
Establishing the Context Phase |
|
SWOT analysis PEST analysis; Organization Structure /Culture; Internal Stakeholders/ Applicable Data Privacy laws |
Establishing Context |
Understanding of internal / External/ organizational Context |
CISO and Steering committee. |
2 |
Risk Identification |
|
H/w, S/w, Data, People, services, Applications, Personal Data |
Identify Assets and Valuate |
Asset value and Criticality |
BU Head /Function owner / PM / Location CS Head. |
|
Identification of applicability of risks and its categories for the Asset subgroups |
Identify Risks |
Risks exposure analysis |
PM/ Respective Function Heads |
|
Existing controls |
Assess Impact |
Impact Rating |
PM/ Respective Function Heads |
|
Past incidents / Current context |
Likelihood of occurrence |
Probability rating |
PM/ Respective Function Heads |
|
BI rating based on Asset value, probability rating |
Risk Determination |
Risk Rating |
PM/ Respective Function Heads |
3 |
Risk Analysis |
|
Risk Rating and Risk criteria |
Risk Analysis |
Prioritization of Risk |
PM/ Respective Function Heads |
4 |
Risk Evaluation |
|
Legal Regulatory requirements / Prioritized Risk Listing / Existing controls and its effectiveness |
Risk Evaluation |
Risk treatment requirements |
PM/ Respective Function Heads |
5 |
Risk Treatment |
|
Risk Assessment Report, Controls from ISO27001 |
Evaluate Controls recommended |
|
PM/ Respective Function Heads |
|
Cost benefit Analysis / Treatment options |
Select Controls |
|
|
|
Preparation of Risk treatment plans (RTP) |
Implement RTP |
Residual Risk, Controls roll out |
PM/ Respective Function Heads |
6 |
Monitoring and review |
|
Plan Audits / Reviews |
Monitoring and review |
Effectiveness of controls / Security improvement plans / Identification of new risks emerging. |
ISG / CISO |
Information Security RARTP (Risk Assessment and Risk Treatment Plan)
The RARTP populates risks based on the assets entered. The Asset inventory will be filled first by the respective project managers. This input would be used to run the RARTP to populate respective risks and controls. They can be used for assessment and verifying the status of the risk in the project.