Home > Articles > Security > General Security and Privacy

Software [In]security: BSIMM Begin

  • Print
  • + Share This
Gary McGraw, software security expert and author of Software Security: Building Security In, introduces BSIMM Begin, a Web-based study focused on 40 of the 110 activities covered in the full Building Security In Maturity Model.
Like this article? We recommend

Common Activities for Getting Started with Software Security

The Building Security In Maturity Model (BSIMM) was released in March 2009 with much fanfare. Since March, the BSIMM has evolved and expanded in several ways. Most importantly, the BSIMM study has added data for fourteen companies to the original nine, bringing the study total to twenty-three (with three further efforts underway as this article goes to press). These data indicate the model as originally devised is robust enough to retain its utility well into the future.

The original nine include Adobe, The Depository Trust & Clearing Corporation (DTCC), EMC, Google, Microsoft, QUALCOMM, Wells Fargo and two un-named financial institutions. The new data include a number of companies that are also household names in verticals branching from ISVs and financial services into insurance and pharmaceuticals. Later this year, these data will be released under the Creative Commons as BSIMM II.

BSIMM Europe, which will be systematically covered in a future column, is a study of nine large-scale European software security initiatives. Comparing the European market for software security tools and services to the US market has traditionally involved some guesswork (see, for example, Software Security Comes of Age). Data as gathered and reported in BSIMM Europe will shed plenty of light on the complexities of the real situation.

BSIMM progress in the form of BSIMM II and BSIMM Europe is particularly good news for the observation-based model, which is based directly on hard data observed from the field. The more data we gather, the more we can say with confidence about the state of software security in the world. We're looking forward to the time (coming soon) when our data set reaches a size where statistically significant trends can be measured and reported.

At this point in the study we are interested in increasing the number of observations covering software security initiatives that are just getting started. To do that, we introduce BSIMM Begin, a Web-based study focused on 40 of the 110 activities covered in the full BSIMM.

Even if your organization is just getting started with a software security initiative, we hope that you will participate in the BSIMM Begin study yourself. Not only will you help make the study more thorough, you'll also come away with some idea of how your basic software security activities stack up against those practiced by others. Take the survey yourself at http://bsi-mm.com/begin. In fact, do what you can to get your friends and colleagues in other companies to take it too. The more data we gather the better off we'll all be.

Note that BSIMM Begin does not take the place of a full BSIMM assessment in any way. The full study focuses on activities that can be used to measure and compare fairly mature, large-scale software security initiatives. By contrast, BSIMM Begin focuses on new initiatives that are just getting off the ground. To make this clear, consider that the full BSIMM expects an organization to have a formalized a software security group (SSG) charged with carrying out or directing BSIMM activities. BSIMM Begin does not assume the existence of an SSG. In fact, we're interested in finding out who is carrying out various introductory software security activities without an SSG. The other major difference between the full BSIMM and BSIMM Begin is that BSIMM Begin will gather data in a self-reporting mode. BSIMM Begin data will be segregated in a separate set of results and analyzed accordingly.

Activities "Everybody Does" Updated

In the article originally titled Nine Things Everybody Does: Software security activities from the BSIMM, we laid out nine activities observed in the original BSIMM data that a large majority of the companies studied carried out. Here is a chart showing those common activities in terms of objectives. The "Observed" column shows the number of companies in the original BSIMM study where the activity was observed (of nine) as well as the number of companies in BSIMM II (of twenty-three). Note that one of the two level 2 activities in this list [T2.2] was observed the fewest times of all of these commonly-observed activities (and in fact now falls below our threshold for counting as a common activity). This is worth mentioning because BSIMM Begin will focus its attention primarily on level one activities — those activities that are the easiest to instantiate. Also worth noting is the fact that every company observed in the BSIMM study to date practices good network security. First things first!

Objective Observed Activity
build support throughout organization 8 of 9
15 of 23
[SM1.2] create evangelism role/internal marketing
meet regulatory needs or customer demand with a unified approach 9 of 9
19 of 23
[CP1.3] create policy
promote culture of security throughout the organization 9 of 9
18 of 23
[T1.1] provide awareness training
see yourself in the problem 8 of 9
11 of 23
[T2.2] create/use material specific to company history
create proactive security guidance around security features 9 of 9
22 of 23
[SFD1.1] build/publish security features (authentication, audit/log, crypto, ...)
build internal capability on security architecture 8 of 9
15 of 23
[AA1.3] have SSG lead review efforts
use encapsulated attacker perspective 9 of 9
15 of 23
[ST2.1] integrate black box security tools into the QA process
demonstrate that your organization's code needs help, too 9 of 9
22 of 23
[PT1.1] use external pen testers to find problems
provide a solid host/network foundation for software 9 of 9
23 of 23
[SE1.2] ensure host/network security basics in place

In addition to the original "nine things everybody does," the data suggest a number of other basic activities that are commonly observed. Those activities are shown in the table below. The criterion for inclusion on this list is an "observed" number over fifteen (of twenty-three).

Objective Observed Activity
establish SSDL gates (but do not enforce) 19 of 23 [SM1.4] identify gate locations, gather necessary artifacts
understand compliance drivers (FFIEC, GLBA, OCC, PCI, SOX, SAS 70, HIPAA, etc.) 18 of 23 [CP1.1] know all regulatory pressures and unify approach
promote privacy 19 of 23 [CP1.2] identify PII obligations
meet demand for security features 16 of 23 [SR1.1] create security standards (T: sec features/design)
get started with AA 15 of 23 [AA1.1] perform security feature review
review high-risk applications opportunistically 15 of 23 [CR1.2] have SSG perform ad hoc review
drive efficiency/consistency with automation 16 of 23 [CR2.1] use automated tools along with manual review
execute adversarial tests beyond functional 15 of 23 [ST1.1] ensure QA supports edge/boundary value condition testing
use ops data to change dev behavior 16 of 23 [CMVM1.2] identify software bugs found in ops monitoring and feed back to dev

Of the twelve practices that make up the Software Security Framework, only the Attack Models practice has no commonly observed activities. This is an interesting phenomenon. We believe that the attacker's perspective and activities around the attacker's perspective may require more attention than we are observing in practice. Further, it appears that mature software security initiatives have a much better handle on this practice than new initiatives. As we analyze the BSIMM II data more thoroughly, we'll be able to explain this observation more clearly.

Level One Activities

In addition to probing the three level two activities in the seventeen most common activities outlined above, BSIMM Begin is structured to probe all 37 level one activities. This will provide us some understanding of how common the most basic software security activities are.

Using a Web-based survey, BSIMM Basic allows organizations to self assess. This is a significant shift from the standard data-gathering regimen followed during a full BSIMM analysis. To be perfectly blunt, we are not yet sure how the self-reporting paradigm will work. We designed the survey so that "making stuff up" is a non-trivial proposition, but it remains to be seen what kind of data can be gathered in this exercise.

As always, we intend to publish our data once they have been properly vetted and analyzed. We hope that the BSIMM Begin effort will broaden our understanding of small-, medium-, and large-sized businesses just getting started with software security.

Take the BSIMM Begin survey yourself at http://bsi-mm.com/begin.

  • + 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