14.2 A Framework for Managing Information Security RisksInformation security risk management is the ongoing process of identifying and addressing information security risks. This section explores the details of a structured approach for managing risks. Figure 14-4 illustrates the operations required by the information security risk management framework as well as the major tasks completed during each operation. This type of framework is common to risk management approaches in many domains, including information security [GAO 98]. Figure 14-4. Operations and Tasks of the Information Security Risk Management FrameworkAssigning ResponsibilityTo manage your information security risks effectively, you must clearly define roles and responsibilities for all of the operations and tasks in the framework. Effective risk management requires everyone in the organization to know his or her role in managing risks. During OCTAVE, an analysis team was responsible for identifying and analyzing risks and for completing high-level planning tasks. This team may not have a permanent existence in your organization, and new people might be assigned responsibility for managing the risks after the evaluation. As you consider the framework in this section and how it might apply to your organization, remember that you will eventually need to determine the appropriate set of roles and responsibilities and distribute them effectively. The remainder of this section examines each operation in Figure 14-4, starting with "Identify." 14.2.1 IdentifyIdentification is the process of transforming uncertainties and issues related to how well an organization's assets are being protected into distinct (tangible) risks. The objective of this activity is to anticipate risks before they become problems and to incorporate this information into the organization's information security risk management process. Table 14-1 illustrates the types of tasks that are conducted during risk identification and the key results produced by each task.
Overall, when implemented, risk identification should
At the end of identification, you will have documented a set of risks, including information about the organization's critical assets, the threats to those assets, and applicable vulnerabilities (both organizational and technological). You will also have collected sufficient supporting information, providing the overall organizational context for interpreting the organization's risks. In the next operation, you build on this information by setting priorities for addressing risks. 14.2.2 AnalyzeAnalysis is the process of projecting how extensive risks are and using those projections to set priorities. The objective of risk analysis is to gain a better understanding of risks by examining all risk-related data in relation to a set of organizational evaluation criteria. Table 14-2 illustrates the risk analysis tasks. Risk analysis should include techniques for setting priorities based on established evaluation criteria. These criteria define those aspects of impact (and probability, if used) that are most important to the organization's business objectives. The analysis process should
When analyzing the risks to your critical assets, you establish the potential impact on the organization and review all risks in the context of organizational needs and objectives. You then use that information to determine which risks to mitigate actively and, after setting your priorities, to decide what your organization can do to address those risks. 14.2.3 PlanPlanning is the process of determining which actions to take to improve the organization's security posture and protect its critical assets. The objectives of planning are to develop and maintain the following three security enhancements:
Table 14-3 highlights the risk planning tasks.
Remember, during OCTAVE, the analysis team completes all high-level planning tasks (i.e., developing a protection strategy and risk mitigation plans). The task of developing detailed action plans occurs after the evaluation. The planning process should include the following specifications:
During the planning process, you develop a protection strategy and risk mitigation plans. First you want to understand the range of available options and next you develop detailed action plans. This second step initially involves selecting key aspects of the protection strategy and risk mitigation plans to implement, based on a cost-benefit analysis. You then formulate an action plan for each key aspect that includes the following elements:
After you finish planning, you have defined the direction for improving your organization's security posture. In the next operation you execute the action plans as designed. 14.2.4 ImplementImplementation is the process of taking planned action to improve an organization's security posture. The objective of risk implementation is to execute all action plans according to the schedules and success criteria that were defined during risk planning. Implementation is tightly linked to risk monitoring and control, during which you follow and correct implementation progress. Table 14-4 illustrates the risk implementation task. Assign responsibility for implementing action plans during the planning process. People who are assigned responsibility for implementing action plans must follow through by ensuring that those plans are completed according to the plan's defined schedules and success criteria. The implementation process should
As you implement action plans, you also need to monitor them to ensure that they are being implemented according to schedule and are meeting their defined success criteria. 14.2.5 MonitorThe monitoring process tracks action plans to determine their current status and reviews organizational data for indications of new risks or changes to existing risks. The objectives of monitoring risks are to collect accurate, timely, and relevant information about the progress of action plans being implemented and any major changes to the organization's operational environment that could indicate the existence of new risks or significant changes to existing risks. Table 14-5 illustrates the tasks completed as risks are monitored.
Typically, the people who are responsible for implementing action plans also monitor those plans. In addition, everyone in the organization needs to be empowered to look for and report information that might indicate the presence of new risks or significant changes to existing risks. For example, if there are major changes to the organization's operational environment (e.g., corporate reorganization, major redesign of the organization's computing infrastructure), management might decide to conduct another information security risk evaluation. Risk monitoring should provide an organization with an efficient and effective way to track the progress of action plans, indications of new risks, and significant changes to existing risks. The monitoring process should both leverage current project management practices within the organization and enable effective and timely communication of status information and risk indicators. As you monitor risks, you need to interpret the data that you collect. Controlling risks allows you to decide how to proceed with action plans, whether the organization needs to identify new risks, and how to address significant changes to existing risks. 14.2.6 ControlControlling risks is a process whereby designated personnel adjust the course of action plans and determine whether changing organizational conditions indicate the presence of new risks. The objective of controlling risks is to make informed, timely, and effective decisions about corrective measures for action plans and about whether to identify new risks to the organization. Table 14-6 highlights the tasks required to control risks. You can make two types of control decisions. The first type deals with adjusting the course of action plans. Part of the responsibility for making control decisions lies with the person who is monitoring an action plan. If action plans were being implemented according to their schedules and were meeting defined success criteria, the person monitoring the plans would simply continue tracking them. The decision in this case is to continue as planned. On the other hand, if the person monitoring the risk noticed a deviation or anomaly that was causing a delay in a plan's schedule or indicated that success criteria were not being met, that person would make sure that the issue was raised at the appropriate management level. It might be necessary to revise that action plan or execute predefined contingency actions. The second type of control decision focuses on interpreting risk indicators. You are looking for major changes to the organization's operational environment, indicating the possible existence of new risks or significant changes to existing risks. As mentioned during our discussion about monitoring risks, anyone in the organization could look for and report information that might indicate the presence of new risks or changes to existing risks. Whoever believes that changes to the operational environment could significantly change the nature of the organization's information security risks should make sure that those issues are raised at the appropriate management level. If appropriate, new risks could be identified (e.g., by conducting another evaluation) or action plans could be revised based on changes to the underlying risks.
Continuous control of risks should be tightly integrated into the organization's management practices. The control process should
This concludes our presentation of the information security risk management framework. The next section looks at a common implementation of the framework. |