Home > Articles > Security > Network Security

Software [In]security: Measuring Software Security

  • Print
  • + Share This
Clearly demonstrating the business value of an ongoing software security initiative, especially in troubled economic times, is difficult at best. Gary McGraw, author of Software Security: Building Security In, and Jim Routh, Chief Information Security Officer for KPMG US, describe the business positioning of a successful software security initiative instituted at a large financial services firm.
Like this article? We recommend

How a Large Financial Services Firm Builds Better Software at a Lower Cost

The biggest challenge software security faces is not a technical challenge, it is a business challenge — namely, how to describe the value proposition of building secure software in concrete, positive terms. Every major software security methodology, from Microsoft's SDL through the Cigital Touchpoints to OWASP CLASP, teaches the integration of security controls into the SDLC. Maturity models, including the BSIMM, extol the virtues of metrics and measurement. Yet clearly demonstrating business value of an ongoing software security initiative is a nontrivial undertaking. Doing so in the middle of a recession makes things even harder. In this short article we describe the business positioning of a successful software security initiative instituted at a large financial services firm (referred to for the remainder of the article simply as "the Firm").

Begin with the End in Mind

Barry Boehm's seminal work in SDLC measurement has taught two generations of programmers and software engineers a simple fact — finding and eradicating software defects early is cost-effective and economically sane. In fact, Barry's work shows that the cost of removing a software defect grows exponentially for each downstream phase of the development lifecycle in which it remains undiscovered. Boehm's TRW case study from the '70s is probably the most cited article on software measurement (especially by Marketing types). Figure 1 shows a typical slide created from the TRW data.

So why not rely on these data to justify software security controls? Any experienced business person will tell you that hackneyed old data may make for pretty PowerPoint, but (unless you are TRW) it is far too easy to object that any particular business is different in fundamental ways from TRW; different enough that defect cost measurements from TRW do not apply. Too many security controls might slow a software project down so much that the cure is worse than the disease.

To get past this classic show stopper of an argument, executives at the Firm set out to measure the impact of their own software security initiative using their own real numbers. By determining the actual costs of defect remediation at various SDLC stages, they can compute a real return on investment table. As an example of early lifecycle savings, the Firm's numbers show that fixing a defect post-production takes on average 32 hours of development time. By contrast, fixing a defect in development takes on average 3.2 hours of development time. This factor of ten adds up quickly. The resulting cost/benefit table (displayed as Figure 2) makes the value of finding and removing software security defects early crystal clear to any business person.

By relying on defect cost data computed from their actual code base, the Firm shows a productivity savings in year 4 of $15.6 million on a sustained investment of $200K. The resulting productivity gain is 12%.

Contrast this view of the impact of software security from a business perspective against more typical technical measurements such as defect count. Showing that a defect count is trending down (as in Figure 3) is an excellent technical result. But Figure 3 is much less useful to a business executive who wants to know how much it costs to accomplish this downward trend. Is it worth the effort? In business, the ends rarely justify the means on purely technical grounds; they must make financial sense too.

The Firm's software security initiative can state with confidence that according to the Figure 2 data, just over 12% of every dollar spent on software development is returned for a productivity gain and can thus be reinvested in high value activities. By spending wisely on software security, they save enough money to reinvest in activities other than costly rework.

Software Security Savings Require Investment

Business success with software security does not come easy. Integrating controls and best practices into an existing SDLC (or, more likely, a set of diverse SDLCs) involves instituting a cultural change in software development. The BSIMM model describes a number of software security activities divided into twelve practices, and includes data observed in the Firm's initiative.

Essential practices adopted by the Firm include: adopting and adapting a software security methodology (CLASP in this case), identifying and empowering business stakeholders, performing architectural risk analysis, leveraging standardized security architectures, carrying out code review with static analysis tools, and building and delivering an extensive training curriculum for developers.

By focusing as much attention on the business situation as on technical concerns, the Firm was able to achieve measurable business results in three years. One tactic involved identifying the most competent and highly respected developers and convincing their management team leaders to nominate them for a special program to teach them about security. Developers who participated and passed screening tests were then recognized as part of a newly established community of top developers (gaining them explicit and accepted responsibility to teach their peers about security).

Another tactic involved implementing a transparent and detailed reporting framework in which key performance metrics (like those shown in Figure 3) were shared with team leaders, their managers, and the CIO on a monthly basis. Over time, development leaders focused on issues that were negatively impacting their scores, and an internal competition developed. An arms race for the common good ensued, encouraged and closely monitored by the CIO.

In 2005, the Firm faced a dilemma now facing hundreds of companies. What is the best approach to securing software? By focusing on policy, process, training and automation, and by carefully measuring business impact while accounting for corporate culture, they built a mature, world-class software security initiative.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

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

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about 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.

Surveys

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.

Newsletters

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.

Security


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

Children


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

Marketing


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.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. 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.informit.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.

Links


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