Home > Articles > Security > General Security and Privacy

Software [In]security: You Really Need a Software Security Group

Gary McGraw, author of Software Security: Building Security In, explains why having a software security group is necessary for a software security initiative.
Like this article? We recommend

BSIMM Data Show an SSG is a Software Security Necessity

Deep in my Powerpoint pile I have a list of 58 major firms with software security initiatives underway that I have collected over the last few years. Just for the record, 31 of the companies on the list are financial services firms like Wells Fargo, nine are Independent Software Vendors like Microsoft, nine are technology firms like Google, five are retailers, and the remaining four firms are in defense and energy with one uncategorizable behemoth…(GE). So far, twenty-six of these firms are captured in the BSIMM study with four more firms under analysis.

There are almost as many ways that these companies have chosen to get started with software security as there are initiatives. Way back in January 2008 I wrote about four particular ways to get started that I had experienced first hand: buy a tool first, train your staff first, create a top down plan first, or start with a portfolio risk assessment. Two years of further experience consulting with ten software security initiatives in combination with careful study of twenty-six real world initiatives in the BSIMM reveals a key insight: having a software security group is necessary for a software security initiative.

Who Should Do Software Security?

Management 101 teaches that in order to get something done in an organization, someone or some group needs to be put in charge. No job does itself.

So why is it that some companies believe this basic fact doesn't apply to software security? In some backwards firms (surely not yours), if you go to the development organization and ask about software security they will immediately refer you to the network security people. "We have a department for that security stuff," they say while ushering you out the door. But when you make your way to the network security department and ask them about software security, they say something like, "Yeah, those developers really should produce code that doesn't suck. Those guys ruin our perfectly configured network with their broken applications."

See the problem? Dev points to security, and security points right back to dev, leaving nobody in the middle. Guess who ends up doing software security in organizations like that? You got it — nobody.

To make perfectly clear that this is a management issue, ask yourself who gets fired when your firm experiences a software security problem? Who gets rewarded when your firm does a good job with software security? If the answer is "nobody," then you have a real problem.

Job one is to fix the "nobody problem." Create an SSG to stand between dev and security for everyone to point to. Empower the SSG with real responsibility and authority for software security, and give them the resources they need to get the job done.

Here's what page five of the BSIMM document has to say about the SSG:

    … Every single one of the nine successful programs we built BSIMM around has a sizeable SSG. Carrying out the activities in the BSIMM successfully without an SSG is very unlikely, so create an SSG before you start working to adopt BSIMM activities. The best SSG members are software security people; but software security people are often impossible to find. If you must create software security types from scratch, start with developers and teach them about security. Do not attempt to start with network security people and teach them about software, compilers, SDLCs, bug tracking and everything else in the software universe. No amount of traditional security knowledge can overcome software cluelessness.

    A good SSG will include both people with deep coding experience and people with architectural chops. As you will see below, software security can't only be about finding specific bugs such as the OWASP Top 10. Code review is a very important best practice, and to perform code review you must actually understand code (not to mention the huge piles of security bugs we all know about). However, the best code reviewers sometimes make very poor software architects, and asking them to perform an Architectural Risk Analysis will only result in blank stares. Make sure you cover architectural capabilities in your SSG as well as you do code. Finally the SSG is often asked to mentor, train, and work directly with hundreds of developers. Communications skills, teaching capability, and good consulting horse sense are must–haves for at least a portion of the SSG staff.

Of course, if the SSG is bigger than one person (see below for guidance on SSG size), you'll need someone to lead it. Of primary interest to successful software security initiatives is identifying and empowering a senior executive to manage operations, garner resources, and provide political cover. Grassroots approaches to software security sparked and led by developers and their direct managers have a poor track record in the real world. Likewise, initiatives spearheaded by resources from an existing network security group often run into serious trouble when it comes time to interface with development groups. By identifying a senior executive and putting him or her in charge of software security directly, you address two basic management 101 concerns: accountability and empowerment. You also create a place in the organization where software security can take root and begin to thrive.

How Big Should Your SSG Be?

Don't tell anybody, but we used to guess what the answer to the SSG size question was. Now we know.

By studying 26 software security initiatives, we observed that in general an SSG is 1% of the size of the development organization. That is, for every 100 developers in a firm, we observe one full time member in the SSG. This is a number that has borne out over the course of the BSIMM study even as the study has tripled in size. (Note that we reported SSG numbers and this same basic ratio from the original nine BSIMM firms in an earlier article.) Over all twenty-six firms currently in the BSIMM, the average SSG size is 1.13% the size of development, with a range in headcount from 0 to 100 and a median of 13. The size of the development group in these firms ranges from 40 to 30,000 with a median of 3000.

Unfortunately, we only have one data point in the BSIMM for firms with less than 100 developers. (If you were wondering about the size 0 SSG above, well that was the firm.) Because of this dearth of data, there is not much we can say about smaller firms at this point. As soon as we analyze the BSIMM Begin data we will revisit the small company question.

In the meantime, the 1% number holds true for larger firms, though the particular structure of the SSG itself is always a matter of corporate culture, and no two SSGs are constructed exactly the same.

How Many Software Security People are There Out There?

If you sum up all of the SSG members in the twenty-six firms that we studied in the BSIMM, the total headcount is 562. That is an impressive number of hard core software security types. Not only is that number large, but those people not directly employed in the SSG but still playing a critical role in a firm's software security initiative (for which we term the satellite) sum to a further 992. If we combine the SSG and the satellite total, we end up with 1554 people working every day in software security as observed in 26 firms. Incidentally, the average satellite size is 2.8% the size of development, with a range of 0 to 300 and a median of 11. (As you can see from the numbers, the existence of a satellite is not as common or as important as the existence of an SSG.)

The average SSG size among our 26 firms was 22, so if we extrapolate to the 58 firms on my list we get 1276 SSG-level people. Factoring in the satellite, where the average size is 40, and extrapolating to 58, we get an additional 2320 people. Of course all 3596 of those people have full time jobs, but these numbers go to show that not only is software security a great career choice, it's also actually possible to both find and employ software security types.

Does your firm have an SSG? It should.

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.


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.


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 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.


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