CISM Certified Information Security Manager Bundle

by Peter H. Gregory
CISM Certified Information Security Manager Bundle cover

On this page

Highlights

CHAPTER 1 Becoming a CISM

My note: .h1

CHAPTER 2 Information Security Governance

My note: .h1

“Establish and/or maintain an information security governance framework and supporting processes to ensure that the information security strategy is aligned with organizational goals and objectives.”
governance is a process whereby senior management exerts strategic control over business functions through policies, objectives, delegation of authority, and monitoring.
Information security governance typically focuses on several key processes. Those processes include personnel management, sourcing, risk management, configuration management, change management, access management, vulnerability management, incident management, and business continuity planning. Another key component is the establishment of an effective organization structure and clear statements of roles and responsibilities.
Information security governance is a set of activities that are established so that management has a clear understanding of the state of the organization’s security program, its current risks, and its direct activities.
For information security governance to be successful, an organization must also have an effective IT governance program. IT is the enabler and force multiplier that facilitates business processes that fulfill organization objectives. Without effective IT governance, information security governance will not be able to reach its full potential. The result may be that the proverbial IT bus will travel safely but to the wrong destination.
The purpose of security governance is to align the organization’s security program with the needs of the business. The term information security governance refers to a collection of top-down activities intended to control the security organization (and security-related activities in every part of the organization) from a strategic perspective to ensure that information security supports the business.
ISACA defines risk appetite as the level of risk that an organization is willing to accept while in pursuit of its mission, strategy, and objectives, and before action is needed to treat the risk.
Risk capacity is related to risk appetite. ISACA defines risk capacity as the objective amount of loss that an organization can tolerate without its continued existence being called into question.
Principle 5: Board management discussions about cyber risk should include identification of which risks to avoid, which to accept, and which to mitigate or transfer through insurance, as well as specific plans associated with each approach.
Security Steering Committee Many organizations form a security steering committee, consisting of stakeholders from many (if not all) of the organization’s business units, departments, functions, and principal locations. A steering committee may have a variety of responsibilities, including the following:       •    Risk treatment deliberation and recommendation The security steering committee may discuss relevant risks, discuss potential avenues of risk treatment, and develop recommendations for said risk treatment for ratification by executive management.       •    Discussion and coordination of IT and security projects The security steering members may discuss various IT and security projects to resolve any resource or scheduling conflicts. They might also discuss potential conflicts between various projects and initiatives and work out solutions.       •    Review of recent risk assessments The security steering committee may discuss recent risk assessments in order to develop a common understanding of their results, as well as discuss remediation of findings.       •    Discussion of new laws, regulations, and requirements The committee may discuss new laws, regulations, and requirements that may impose changes in the organization’s operations. Committee members can develop high-level strategies that their respective business units or departments can further build out.       •    Review of recent security incidents Steering committee members can discuss recent security incidents and their root causes. Often this can result in changes in processes, procedures, or technology changes to reduce the risk and impact of future incidents.

My note: .h1

•    Risk treatment deliberation and recommendation

My note: .1

•    Discussion and coordination of IT and security projects

My note: .2

Review of recent risk assessments

My note: .3

•    Discussion of new laws, regulations, and requirements

My note: .4

Review of recent security incidents

My note: .5

Reading between the lines, the main mission of a security steering committee is to identify and resolve conflicts and to maximize the effectiveness of the security program, as balanced among other business initiatives and priorities.
The Security Balanced Scorecard The balanced scorecard (BSC) is a management tool that is used to measure the performance and effectiveness of an organization.
BMIS defines culture as “a pattern of behaviors, beliefs, assumptions, attitudes, and ways of doing things.”
“governance is the set of responsibilities and practices exercised by the board and executive management with the goal of providing strategic direction, ensuring that objectives are achieved, ascertaining that risks are managed appropriately and verifying that the enterprise’s resources are used responsibly.”
Business Impact Analysis

My note: .h1

A business impact analysis (BIA) is used to identify an organization’s business processes, the interdependencies between processes, the resources required for process operation, and the impact on the organization if any business process is incapacitated for a time. A BIA is a cornerstone of a business continuity and disaster recovery (BCDR) program because the BIA indicates which business processes and underlying resources are the most vital to the organization. The most critical processes are those that receive the most attention during the development of disaster recovery and business continuity plans. The BIA is also useful for information security professionals aside from business continuity purposes. Again, the BIA indicates the most critical processes (and underlying resources such as information systems and other IT infrastructure), giving the security strategist a better idea of which business processes and systems warrant the greatest protection. The presence of a BIA provides a strong indication of the organization’s maturity, through its intention to protect its most critical processes from disaster scenarios. Correspondingly, the absence of a BIA suggests that the organization does not consider BCDR as having strategic importance.
The BIA is also useful for information security professionals aside from business continuity purposes. Again, the BIA indicates the most critical processes (and underlying resources such as information systems and other IT infrastructure), giving the security strategist a better idea of which business processes and systems warrant the greatest protection.
The presence of a BIA provides a strong indication of the organization’s maturity, through its intention to protect its most critical processes from disaster scenarios.
Information risk management is the practice of balancing business opportunity with potential information security–related losses.
Information risk management is largely a qualitative effort since it is difficult to know the probability and costs of significant loss events.
Risk management is the fundamental undertaking for any organization that desires to be reasonably aware of risks that, if not identified or monitored, could result in unexpected losses and even threaten the survival of the organization.
The purpose of risk management is the identification of credible threats and the means to decide what to do about those threats. Organizations using effective risk management processes experience fewer security incidents; those that do occur have lower impact, and the organization is better prepared to deal with them.
Risk management is the cornerstone of any information security program.
Risk management provides key information that enables the security manager to prioritize scarce resources in a way that results in the greatest possible risk reduction.
The effectiveness of a risk management program is largely dependent on two factors: support from executive management, and an organization’s culture with respect to security awareness and accountability.
effective risk management program can serve as a catalyst to make subtle but strategic changes to an organization’s culture.
An organization that implements an effective risk management program will have heightened awareness about the business use of technology, as well as how technology can impact the business.
The greatest benefit that an organization will derive is a lower probability for security incidents, and for those incidents that do occur, the organization will be better prepared, and the impact from the incident will be reduced.
An organization with the risk management program will develop a culture of risk-aware planning, thinking, and decision-making. Executives in the organization will be more aware of information risk, resulting in a more realistic view of the risks associated with the use of information technology and the Internet.
Organizations without effective risk management programs often acquire many of these capabilities but do so without first identifying specific, relevant risks to their organizations.
The security solutions portfolio should be based on supporting the business objectives and have defined success criteria, business requirements, and technical requirements prior to the purchase of specific technologies.
There are several risk management frameworks to choose from, and they share common principles, including the concept of risk management being a life-cycle process, periodic assessment, and continuous improvement.
Applying a risk management framework in an organization requires a keen understanding of the organization’s mission, objectives, strategies, cultures, practices, structure, financial condition, risk appetite, and level of executive management support.
Security managers will need to perform one or more gap analyses to better understand the current state so that they can develop adequate plans to define, document, and highlight the desired future state.
The objectives of a risk management strategy are to identify all credible risks and to reduce them to a level that is acceptable to the organization. The acceptable level of risk is generally related to these factors:       •    Executive management’s risk appetite       •    The organization’s ability to absorb losses, as well as its ability to build defenses       •    Regulatory and legal requirements
As the organization establishes its acceptable level of risk (also known as risk tolerance), this will drive the implementation and refinement of controls.
Possibly the most important factor that will enable or constrain security managers as they develop a risk management strategy is the development of key relationships throughout the organization.
When a security manager develops and implements a risk management strategy, the security manager is acting as a change agent in the organization.
This role as a security catalyst is an ongoing journey that will become a way of life as the organization…
Stakeholders need to understand how the risk management program will work and the role they will play in it being an effective…
Successful information risk management requires that the channels of communication be open at all times…
information about risks should be readily available to all board members, executives,…
Similar to security awareness programs, the goal of risk awareness is to ensure that business leaders and decision-makers are aware of the idea that all business decisions have a risk component and that…
Further, they need to be aware of the presence of a formal information risk management program, which includes a process and…
There is some overlap in the content and audience of security awareness and risk awareness programs. Primarily, security awareness applies to an entire organization, whereas risk awareness encompasses senior…
Ideally, security awareness and risk awareness programs are developed side by side, ensuring that all audiences receive useful and…
While this may seem like an ad hoc activity, security managers should treat these mini-consulting engagements as formal service requests, even in the absence of a service request system or formal capability. This includes being mindful of responsiveness and service levels. Here are…
Ability to listen to business…
Ability to assess the information and how it may impact a process or business unit, as well as identify other areas in the…
Have a good understanding of the business, not just the technology…
When building an information risk program, the security manager needs to develop processes and procedures, roles and responsibilities,…
ISO/IEC 27001, “Information technology — Security techniques — Information security management…
Requirements 4 through 10 in this standard describe the structure of an entire information…
ISO/IEC 27005, “Information Technology — Security Techniques — Information…
31010, “Risk management — Risk assessment…
“Guide for Applying the Risk Management Framework to Federal Information Systems: A…
First, they can select the single framework that has the best alignment with the…
security manager can select elements from one or more frameworks to build the organization’s…
Security managers in regulated industries need to understand legal and regulatory requirements so that they might select a framework and build a program that has all the required activities and characteristics.
Second, if an enterprise risk management program is in place within the organization, then the security manager should consult with the ERM team to understand how the frameworks will support each other.
Integration into the Environment

My note: .h2

To be efficient and effective, the organization’s risk management program needs to fit neatly and easily into the organization’s existing policies, processes, and systems. The risk management program should complement existing structures instead of building separate structures.
The risk management program should complement existing structures instead of building separate structures.
The principle at work here is one of utilizing existing structures and minimizing impact on the organization. A new or improved risk management program will already be disruptive on an organization in need of such a program—there is no point in making the componentry of a program disruptive as well.
A new or improved risk management program will already be disruptive on an organization in need of such a program—there is no point in making the componentry of a program disruptive as well.
Risk management programs need to integrate into the organization’s culture. To the greatest extent possible, a new or improved risk management program should leverage current thinking, vocabulary, customs, and practices to fit seamlessly into the organization. But as stated previously, an organization’s culture may be in need of minor adjustments with regard to information risk and information security. If so, the new risk management program should be “eased into” the culture as opposed to being haphazardly imposed upon the organization.
The most important part of integrating an information risk program into an existing environment has little to do with the organization’s existing systems or even its processes. Instead, integrating into the organization’s culture is the most important consideration.
When designing and establishing a risk management program, the security manager needs to understand the business context
scope of the program,
entire business environment in which the program will operate, including the organization’s policies, processes, practices, and culture.
Instead, the security manager, together with executive management, needs to define the boundaries within which the risk management program will operate.
A gap analysis is defined as an examination of a process or system to determine differences between its existing state and a desired future state.
This helps the security manager better understand the current state and how it is different from the desired future state.
the gap analysis will reveal what characteristics of the current state can remain, what should be discarded, what should be replaced, and what should be added.
For example, a security manager examines an organization’s existing change control process. All that can be found is a log of changes and e-mail attachments containing management approvals for changes.
The gap analysis reveals the lack of a change request procedure, change advisory board (CAB) calls, and roles and responsibilities.
With this information, the security manager now can undertake (or direct) the work required to get the change control process improvements implemented.
Fortunately, there’s a wealth of information available to security managers, which will help to supplement the knowledge and skills that they already have so that they can proceed with building and running their information risk management program with more confidence and with better assurances of positive outcomes. Here are some of these information sources:
The Risk Management Life Cycle
risk management is formally defined in policy and process documents that define scope, roles and responsibilities, workflow, business rules, and business records.
Information risk management relies upon risk assessments that consider valid threats against the organization’s assets, considering any present vulnerabilities.
The results of risk assessments are placed into a risk register, which is the official business record containing current and historic information risk threats.
Risk treatment is the activity where decisions about risks are made after weighing various risk treatment options. Risk treatment decisions are typically made by a business owner associated with the affected business activity.
The Risk Management Process
Scope definition
geographical
A classification scheme may be used to identify risk and criticality levels.
Asset valuation is a key part of asset management processes, and the value of assets is appropriated for use in the risk management processes.
Risk appetite
Developed outside of the risk management life-cycle process, risk appetite is an expression of the level of risk that an organization is willing to accept.
A risk appetite that is related to information risk is typically expressed in qualitative means; however, organizations in financial services industries often express risk in quantitative terms.
Risk identification
This is the first step in the iterative risk management process. Here,
the organization identifies a risk that comes from one of several sources, including the following:
Risk assessment
Vulnerability assessment
Threat advisory
Risk analysis
Risk analysis
This is the second step in a typical risk management process. After
it is then analyzed to determine several characteristics, including the following:
Probability of event occurrence
likelihood
This is typically expressed in the number of likely events per year.
Impact of event occurrence
Mitigation
Recommendation
Risk treatment
Here, an individual decision-maker or committee makes a decision about a specific risk.
Accept
the organization elects to take no action
Mitigate
reduce the probability
reduce the impact
The actual steps taken may include business process changes, configuration changes, the enactment of a new control, or staff training.
transferring risk is typically achieved through an insurance policy, although other forms are available, including contract assignment.
Avoid
Risk communication
The risk register, sometimes known as a risk ledger,
A risk register is a listing of risks that have been identified. Typically, a risk register contains many items, including a description of the risk, the level and type of risk, and information about risk treatment decisions.
Risk Management Methodologies
NIST Standards
NIST Special Publication 800-30, “Guide for Conducting Risk Assessments,”
NIST Special Publication 800-39, “Managing Information Security Risk: Organization, Mission, and Information, System View,”
NIST SP 800-39
Tier 1: Organization view
Tier 2: Mission/business process view
Tier 3: Information systems view
Step 1: Risk framing
Step 3: Risk response
Step 4: Risk monitoring
(NIST 800-30 has exemplary lists of threats, vulnerabilities, and impact in its appendixes).
Step 2: Conduct assessment
Identify threat sources and events
Identify vulnerabilities and predisposing conditions
Determine likelihood of occurrence
Determine magnitude of impact
Determine risk
Step 3: Communicate results
Step 4: Maintain assessment
NIST Special Publication 800-137, “Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations,”
NIST 800-30 is available at http://csrc.nist.gov/publications/PubsSPs.html.
ISO/IEC 27005
Step 1: Establish context
Scope of the risk assessment
Purpose of the risk assessment
Risk evaluation criteria
Impact criteria
Risk acceptance criteria
Logistical plan
Step 2: Risk assessment
Asset identification
Threat identification
Control identification
Consequences identification
Step 3: Risk evaluation
Step 4: Risk treatment
Risk reduction (sometimes known as risk mitigation)
Risk retention (sometimes known as risk acceptance) Here, the
Risk avoidance
Risk transfer
When an organization transfers risk to another party, there will usually be residual risk that is more difficult to treat.
For example, while an organization may have had reduced costs from a breach because of cyber insurance, the organization may still suffer reputational damage in the form of reduced goodwill.
Decision-makers weigh the costs and benefits associated with each these four options and decide the best course of action for the organization.
For instance, a business application was found to accept weak passwords; the chosen risk treatment was a combination of security awareness training (mitigation) and acceptance (the organization elected not to modify the application as this would have been too expensive).
Often, after risk treatment, some risk—known as residual risk—remains. When analyzing residual risk, the organization may elect to undergo additional risk treatment to reduce the risk further, or it may accept the residual risk as is. Note that residual risk cannot be reduced to zero—there will always be some level of risk.
Step 5: Risk communication
Step 6: Risk monitoring and review
is an analysis method that helps a risk manager understand the factors that contribute to risk, as well as the probability of threat occurrence and an estimation of loss.
FAIR is used to help a risk manager understand the probability of a given threat event and the losses that may occur.
FAIR also focuses on the concept of asset value and liability.
For example, a customer list is an asset because the organization can reach its customers to solicit new business; however, the customer list is also a liability because of the impact on the organization if the customer list is obtained by an unauthorized person.
FAIR guides a risk manager through an analysis of threat agents and the different ways in which a threat agent acts upon an asset.
FAIR is claimed to be complementary to risk management methodologies such as NIST SP 800-30 and ISO/IEC 27005. You can obtain FAIR at www.fairinstitute.org.
Asset Identification and Valuation
Hardware Assets
Value
Location
Asset group
Information Assets
Customer information
Business operations
Virtual assets
Cloud-Based Information Assets
Virtual Assets
Asset Classification
The purpose of asset classification is to determine, for each asset, its level of criticality to the organization.
The best approach to asset classification in most organizations is to first identify and classify information assets and then follow this with system classification.
It should be noted that one area that is often overlooked
data that resides outside of the organization’s approved systems.
Information Classification
Operational criticality
Accuracy or integrity
Sensitivity
the most successful organizations will be those that build a fairly simple information classification scheme.
Secret
Restricted
Confidential
Public
examples of information at each of these levels of classification include the following:
Merger and acquisition plans, user and system account password, and encryption keys
Restricted
Credit card numbers, bank account numbers, Social Security numbers, detailed financial records, detailed system configuration, and vulnerability scan reports
Confidential
System documentation, end-user documentation, internal memos, and network diagrams
Public
Marketing collateral, published financial reports, and press releases
Organizations that develop and implement information classification programs find that personnel will often misclassify information, either because they do not understand the nature of the sensitivity of a particular set of data or because they know that at a higher level of classification, they may feel that they cannot store or transmit the information in a way they feel is needed.
Asset Valuation
A key part of a risk assessment is the identification of the value of an asset.
Qualitative Asset Valuation
The objective of qualitative asset valuation is to establish which assets have more value than others.
Qualitative valuation gives an organization the ability to see which assets have greater value and which have less value. This can be highly useful in an organization with a lot of assets, as this can provide a view of its high-value assets without the “noise” of comingled lower-valued assets.
Quantitative Asset Valuation
Many organizations opt to surpass qualitative asset valuation and assign a dollar (or other currency) valuation to its assets.
This is common in larger or more mature organizations that want to better understand the actual costs that may be associated with loss events.
Replacement cost
If the asset is a database, its cost might be determined to be the operational costs to restore it from backup or the costs to recover it from its source such as a service provider.
This represents the value of an asset in the organization’s financial system, typically the purchase price less depreciation.
Net present value (NPV)
If the asset directly or indirectly generates revenue, this valuation method may be used.
Redeployment cost
If the asset is intellectual property such as software source code, its valuation might be determined to be the effort for developers to re-create it.
Consequential financial cost
If the asset is a database containing sensitive data, its valuation might be measured in the form of financial costs that result from its theft or compromise. While the cost of recovering that database may be relatively low, the consequences of its compromise could cost hundreds of dollars per record. This is a typical cost when measuring the full impact of a breach.
Security managers need to carefully determine the appropriate method for setting the value of each asset.
In many cases, an individual asset will have more than a single valuation category described earlier.
Security managers should document their rationale and method of valuation, particularly for sensitive information assets whose valuations could vary widely depending on the method used.
Better yet, larger and more mature organizations will have guidelines that specify methods and formulas to be used in information asset valuation.
these can include both deliberate and accidental actions; further, it includes those that are man-made and those that are associated with naturally occurring events.
In a risk assessment, it is essential to identify all threats that have a reasonable likelihood of occurrence.
Threats such as meteorites and space debris are rarely included in risk assessments because of the minute chance of occurrence.
“An APT is an adversary that possesses sophisticated levels of expertise and significant resources which allow it to create opportunities to achieve its objectives using multiple attack vectors (e.g., cyber, physical, and deception). These objectives typically include establishing and extending footholds within the IT infrastructure of the targeted organizations for purposes of exfiltrating information, undermining or impeding critical aspects of a mission, program or organization; or positioning itself to carry out these objectives in the future. The advanced persistent threat: (i) pursues its objectives repeatedly over an extended period of time; (ii) adapts to defenders’ efforts to resist it; (iii) is determined to maintain the level of interaction needed to execute its objectives.”
The term APT was developed in the early 2000s to describe a new kind of adversary that worked slowly but effectively to compromise a target organization.
The Risk Register
A risk register is a business record that contains information about business risks and information about their origin, potential impact, affected assets, probability of occurrence, and treatment.
Risk assessment
Vulnerability assessment
Internal audit
Security incident
Threat intelligence
Industry development
New laws and regulations
Consultants
When managing the contents of the risk register, an organization may establish business rules related to the types of content that may be included in the risk register.
However, if in the course of conducting vulnerability scans, the security manager discovers that there are systemic problems with recurring vulnerabilities, this phenomenon may warrant an entry in the risk register. For example, there may be recurring instances of servers that are not being patched or a problem that results in patches being removed. This could be part of a larger problem that incurs significant risk to the organization, deserving of an entry in the risk register.
Risks identified in third parties in the organization’s third-party risk management program should be included in the risk register.
a business case as “documentation of the rationale for making a business investment, used both to support a business decision on whether to proceed with the investment and as an operational tool to support management of the investment through its full economic life cycle.”
Organizations should consider managing information about assets in a fixed-assets application.
Why Asset Management Is Control #1
The well-known control framework known as the Critical Security Controls by the Center for Internet Security (known as the CIS 20) lists hardware asset inventory as the first control. I believe there is a specific purpose to this: an organization cannot protect assets that it does not know about.
The policies, procedures, mechanisms, systems, and other measures designed to reduce risk are known as controls.
An organization develops controls to ensure that its business objectives will be met, risks will be reduced, and errors will be prevented or corrected.
Controls are used in two primary ways in an organization: they are created to ensure desired outcomes, and they are created to avoid unwanted outcomes.
Internal Control Objectives
Control objectives are the foundation for controls. For each control objective, one or more controls will exist to ensure the realization of the control objective.
“Availability of IT Systems”
“Manage information risk to an acceptable level based on risk appetite in order to meet organizational goals and objectives.”
“Develop and maintain an information security program that identifies, manages and protects the organization’s assets while aligning to information security strategy and business goals, thereby supporting an effective security posture.”
“Plan, establish and manage the capability to detect, investigate, respond to and recover from information security incidents to minimize business impact.”

267 highlights, exported from my Kindle via Readwise.

Subscribe to Ishan Girdhar newsletter and stay updated.

Don't miss anything. Get all the latest posts delivered straight to your inbox. It's free!
Great! Check your inbox and click the link to confirm your subscription.
Error! Please enter a valid email address!