Home > Articles > Security > General Security and Privacy

Software [In]security: Balancing All the Breaking with some Building

Software security should be a balanced approach of offense and defense (white hat and black hat, if you will). Security expert Gary McGraw argues that the balance is off, favoring offense at the expense of defense, and that more proactive defense is needed in the computer security industry.
Like this article? We recommend

Software security involves both building things properly and understanding how things break.  In my view, these two aspects of security should be in balance (and properly feed off each other).  This concept is so central to my approach to security that I created the Yin/Yang cowboy hat icon that adorns the front cover of Software Security and is used to brand other books in the software security series .

The Yin/Yang is the classic Eastern symbol describing the inextricable mixing of standard Western Polemics (black/white, good/evil, Heaven/Hell, create/destroy, et cetera). Eastern philosophies are described as holistic because they teach that reality combines polemics in such a way that one pole cannot be sundered from the other. In the case of software security, two distinct threads—black hat activities and white hat activities (offense/defense, construction/destruction)—intertwine to make up software security. A holistic approach, combining yin and yang (mixing black hat and white hat approaches) is what is required.

The balance is out of whack.  From where I sit, it appears that computer security is spending more time and effort on offense than defense.  Interestingly, this problem is evident in very diverse domains of cyber security, ranging from the hacker crowd that attends conferences such as Blackhat to the military leadership of US Cyber Command.

Simply put, we need more proactive defense in computer security.

Overcoming the NASCAR Effect

One of the problems to overcome is that exploits are sexy and engineering is, well, not so sexy.  I've experienced this first hand with my own books, as the black hat "bad guy" books such as Exploiting Software outsell the white hat "good guy" books by a ratio of 3:1.  I attribute this to the NASCAR effect.

Nobody watches NASCAR racing to see cars driving around in circles; they watch for the crashes. That's human nature. People prefer to see, film, and talk about the crashes rather than talk about how to build safer cars.  There is a reason that there are several NASCAR channels available via satellite TV and zero Volvo car safety channels.

This same phenomenon happens in software. It seems that when it comes to software security, people would rather talk about software exploit, how things break, and the people that carry out attacks than to talk about software security best practices. I suppose that instead of being discouraged by this effect, we need to take advantage of it to get people interested in the software security problem.

In the end, we will need to integrate security into the software development lifecycle (as described in Software Security). But maybe the best way to start is to get a better handle on what attacks really look like. At least then we'll learn more about what deep trouble we're in.

Real Defense is Proactive, Even in Cyber War

War has both defensive and offensive aspects, and understanding this fundamental dynamic is central to understanding cyber war. Overconcentrating on offense can be very dangerous and destabilizing as it encourages actors to attack first and ferociously, before an adversary can since no effective defense is available. On the other hand, when defenses are equal or even superior to offensive forces, actors have less incentive to strike first because the expected advantages of doing so are far less. The United States is supposedly very good at cyber offense today, but from a cyber defense perspective it lives in the same glass house as everyone else. The root of the problem is that the systems we depend on—the lifeblood of the modern world—are not built to be secure.

This notion of offense and defense in cyber security is worth teasing out. In my view, offense involves exploiting systems, penetrating systems with cyber attacks and generally leveraging broken software to compromise entire systems and systems of systems (see, for example Exploiting Software). On the other hand, defense means building secure software, designing and engineering systems to be secure in the first place and creating incentives and rewards for systems that are built to be secure (see, for example, Software Security).

The United States has reportedly developed formidable cyber offenses. Yet America's cyber defenses remain weak. What passes for cyber defense today—actively watching for intrusions, blocking attacks with network technologies such as firewalls, law enforcement activities, and protecting against malicious software with anti-virus technology—is little more than a cardboard shield.  Those kinds of defenses are too reactive, and they happen well after a system is built.

It's worth noting that the kind of defenses usually adopted by Capture the Flag (hacking contest) participants at Defcon and during the international Capture the Flag (iCTF) contest tend to be very much reactive as well.  If the hacker community could figure out a way to include security engineering in the mix during their contests (especially at the software level) I would welcome that evolution.

Case in Point: Charlie Miller's Spectacular Hacking

Besides the NASCAR effect and the intertia against being proactive, there is another problem to overcome as well.  It is far easier to break systems and become famous than it is to build systems properly and become equally famous.  Consider the case of Charlie Miller, whose work hacking apple products has been extensively covered in the media.  Charlie uses a very straigtforward strategy to find problems in popular systems.  He starts with an outside→in fuzzing tool and sifts through the mountains of results. Reportedly, some of his fuzz input generators are incredibly simple five liners that do things like changing an input file one bit at a time, throwing it at the application under test, and keeping track of the results.  (For what it's worth, these kinds of techniques have been around for a long time in computer security.  See, for example, the ancient software testing tome I co-authored with Jeff Voas back in 1997, Software Fault Injection.)  By automating this kind of testing and running it repeatedly (sometimes for several weeks at a time), Charlie is able to uncover enough exploitable flaws to make a name for himself.

This kind of thing raises two basic questions.  The first (and probably most important) is why Apple can't do this kind of testing itself.  It could, and it should.  Charlie says it best when he says that all it takes is patience.  The second question is what kind of software engineering process results in software that can be defeated by automatic fuzzing?!  Apparently, Apple needs to take a closer look at its software security initiative and tighten things up.

Given this example, our challenge as a discipline should be clear: even though the Charlie Millers of the world can break systems automatically and garner spectacular coverage, we need to somehow leverage this into impetus for better software security engineering.  We need better building and less breaking.

A Call for Engineering

Perhaps the Blackhat conference will add a track about security engineering to begin to balance out its over-focus on breaking.  (I've talked to some of the advisors about it.)  Maybe contests like Microsoft's Bluehat Prize—a security engineering challenge—will help.  Maybe the narrative in software security will shift from "what is the best way to find bugs" to "how do we fix these bugs."

One thing is for sure: the demand for people who can practice software security professionally and build more secure systems is growing steadily.  Proactive security—once a pipe dream—is now a reality in many leading firms.  The security engineeting field is progressing apace; now it is time for the rest of security to grow up. 

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