Home > Articles > Other IT Certifications > CISSP

Making Sense of Risk Management in the IT Security Field: Risk Management and Security Series, Part II

IT security professionals and CISSP exam candidates find the field of risk management and security metrics tough to navigate. Many security professionals and consulting firms comfort customers by saying that they do not support or sell their services based upon fear, uncertainty, or doubt (FUD). In this second of an ongoing article series related to risk management and security metrics, world-renowned security and CISSP expert Shon Harris discusses the importance of selling services and products based on real and meaningful statistics and metrics.
Like this article? We recommend

Like this article? We recommend

Many security professionals and consulting firms comfort customers by saying that they do not support or sell their services based upon fear, uncertainty, or doubt (FUD). When we look at FUD, what are we really talking about?

Fear is based upon devastating events that can take place from an attack. Uncertainty is based upon the potential or probability that an attack would take place against a specific organization. Doubt is based upon the effectiveness of the organization's current security measures that are put in place to protect against a specific attack.

So basically you can have a fear that the sky may fall. You are uncertain if it will fall upon and squish you. You doubt that the current protection measures that you have protecting you from the sky falling will really help you. So what do you do? Buy something. Buy insurance, a product, or a consultant to direct you on how not to get squished by the falling sky. Are you really protected? Probably not, but you feel more safe so you can now go blissfully along with your day-in-and-day-out activities.

A better approach than selling FUD is selling services and/or products based on real and meaningful statistics and metrics. More formal and structured risk management models that are based upon security measurements are emerging, but they have not yet moved from the purely theoretical phase to the purely practical phase.

We are marching this way, slowly, but many of the consulting services and products in the market are not based upon formal risk management models. The key word here is formal. When we say that a model is formal, it can be proven (usually mathematically) and is repeatable.

Many of the risk management approaches today are not risk-based at all. Many consulting firms and products that are touted to provide risk management really just carry out vulnerability management. This means that they can identify a vulnerability and tell you how to fix it, but do not (or cannot) estimate the probability of a vulnerability being exploited and (more importantly) what the business impact pertaining to that exploitation will be. Vulnerability management works at the micro level, while risk management works at the macro level.

Most security professionals would really like to have an approach to security that is not based upon FUD. As many in the industry know, it is hard to convince an executive to spend money because something bad may happen and it may hurt the organization. Executives and other business-oriented people are used to releasing funds solely based upon sound financial numbers and business scenarios: not "ifs," "maybes," "coulds," and "should."

Most security professionals are left with FUD only because they are not armed with consistent security metrics that illustrate the effectiveness of different security solutions and the resulting ramifications of not implementing them. Where FUD keeps everyone in the dark, solid security metrics provides light to better see and understand the many complex components of information security risk management.

It is very difficult to show progress in management of anything without the ability to measure. A metric should have the points, the measurement, and the reference.

Okay, but a metric means nothing without an objective. You can have an objective to lose 30 pounds. To know how you are doing to meet this objective, you need to have a reference (what you weigh today) and a way to measure the progress of your activities toward that objective (weighing yourself on your scale daily).

At a very basic operational security metric view, you might have the objective of experiencing only two virus infections per year within your enterprise. You have a historical reference point: Your organization experienced eight virus infections last year. You have a way to measure the progress—recording the amount of virus infections you get this year. So this very simplistic metric is made up of a reference point (where we are today) and the way to measure progress (how are we doing) and an end objective (our goal).

What are we really trying to get out of this type of measurement? The effectiveness of a security solution put in place. So if you had eight virus infections last year and your goal is to experience only two or fewer infections in the next 12 months something has to change: You are going to implement a security solution.

Let's say your organization already has antivirus software on all the systems in the network, but even with that you still experienced eight virus infections last year. Now you put in an antivirus solution on your mail server and you need to find out how effective that product is against the threat of virus infiltration. Over the next 12 months, you keep track and your organization has not experienced any virus infections. This solution would be seen as a successful countermeasure against this specific threat.

The previous example is a simplistic operational metric example. It is critical to define meaningful metrics for both an operational and strategic point of view. Operational metrics means "how are we doing down in the weeds?" Strategic metrics means "how are we doing at a business level?" Setting the objectives per metric and overseeing the progress of the processes necessary to obtain the set objectives is in a nutshell what security governance is.

So the entities carrying out security governance in an organization (CSO, CISO) draw the lines in the sand and state "we will meet these objectives in our security efforts". These entities responsible for governance need to be continually updated in how the organizational efforts are moving along to meet the set objectives. How can this information be communicated to the security governance entities without meaningful metrics?

If security metrics are created properly, they should be the language that is used when discussing security within your organization. What is unfortunate is that the industry does and does not have standard metrics that can be used. The industry does have high-level models that contain their own incorporated metrics; CobiT, NIST, and ISO 27000. We have some other models that can also be used to derive metrics from: CMMI, COSO, ITIL, Prince2, and Six Sigma. So the industry does have sets of metrics that can be used, but the industry does not have one set standard of metrics to be used by everyone.

With the lack of security metric standards and the overwhelming amount of items that need to be measured, most security professionals revert to using risk ratings and/or color coding identified risks (red, yellow, green) and call it a day.

I believe that it takes a certain type of person to be able to develop useful security metrics for an organization. This person needs to have one foot in the technical side of security and one foot in the business side of security. This person must be able to understand the detail-oriented level of security, but not get stuck in the weeds. This person needs to understand the company drivers of an organization and understand that most companies are not about technology or being secure—they are in business to make money. This person needs to be able to think "outside the box," but also must know what is inside the box in the first place.

Someone who is going to develop security metrics for an organization should understand what we mean when we say "holistic security." You should not just measure what is there but also be able to identify what is not there that should be.

This may sound intimidating, and you may be saying "I am not that person," but you could be if you set out the course to develop security metrics that would be directly beneficial to your organization. If you put in this time and effort, not only would you hone your skills as a security professional; you could also help tame that thing we call "information security" within your own company.

Please stay tuned for Part III!

For more information visit http://www.logicalsecurity.com.

Pearson IT Certification Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from Pearson IT Certification and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about Pearson IT Certification products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites; develop new products and services; conduct educational research; and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by Adobe Press. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.pearsonitcertification.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020