Home > Articles > Security > Software Security

  • Print
  • + Share This
Like this article? We recommend

New Approach

This is going to require a new approach to application development, shifting the focus away from the business-focused requirements. In essence, we must build security into these applications. There are many schools of thought on how to build better software. There are numerous development frameworks, programming standards, and best practices; and a variety of tools used to evaluate code during development, as well as testing the finished product after its been built.

Change in Attitude

I think many would argue that we need to change our attitudes about application development. We need to build secure software, not put walls around it after we build it. This change in mindset is one driving force behind the Rugged Software movement. "Rugged" is not a framework or a development methodology. It's about developing a culture of security.

It strives to bring secure thinking into the development process—whatever framework or methodology you use. The goal is to create "available, survivable, defensible, secure, and resilient software." To this end, they have produced the Rugged Handbook and the Rugged Implementation Guide. Both documents detail steps to help change your software development culture. You can read more at their website and take a moment to read the Rugged Manifesto.

How Did Microsoft Do it?

Changing our mindset and getting us all to focus on security an excellent goal, but we still need to implement secure code. How do we go about that?

Microsoft was criticized for many years about the poor quality of software they produced. Since the platform was widely deployed, it became a primary focus of attack. Yet today Microsoft has successfully changed its process so it's no longer at the top of the list of exploits.

How did Microsoft accomplish this? Part of the answer definitely lies in its Secure Development Lifecycle (SDL). Microsoft has enhanced its development lifecycle, bringing new thinking and tools to bear in an effort to produce more secure applications. I won't go into this in great detail here, but I will highlight what I feel are some key points.

Threat Models

Most experts agree that it's more cost-effective to design and develop secure code than it is to fix broken or unsecure applications after they've been deployed. One way to start thinking about this during the design phase is to use threat modeling, which is a process used to understand security threats to a system, quantify the risks, and try to mitigate those risks in the overall system design.

While historically this has been a white-board exercise, Microsoft has developed the SDL Threat Modeling Tool. This tool focuses on a data-flow diagram representing the basic system design. Then, each component of the system is assigned "threats." The tool constructs threats based on the idea that software comes under a predictable set of threats for each element. These threats are based on the STRIDE Threat Model, and are broken into the following categories:

  • Spoofing identity. An example of identity spoofing is illegally accessing and then using another user's authentication information, such as username and password.
  • Tampering with data. Data tampering involves the malicious modification of data.
  • Repudiation. Repudiation threats are associated with users who deny performing an action without other parties having any way to prove otherwise. Nonrepudiation refers to the capability of a system to counter repudiation threats.
  • Information disclosure. Information disclosure threats involve the exposure of information to individuals who are not supposed to have access to it.
  • Denial of Service. Denial of Service (DoS) attacks deny service to valid users—for example, by making a Web server temporarily unavailable or unusable.
  • Elevation of privilege. In this type of threat, an unprivileged user gains privileged access and thereby has sufficient access to compromise or destroy the entire system.

This tool provides developers with a consistent repeatable process that can be applied to almost any development situation and can be used even in other development environments or frameworks. It doesn't have to be tied to the Microsoft SDL.

Other Frameworks and Methodologies

Clearly, secure application development has a lot of inertia right now. There are many best practice approaches and frameworks available to choose from. While I don't have the space here to cover them all, some examples include these:

Mitre has a number of security efforts, all tied together under their Making Security Measurable website. This is broken down into a number of different interrelated categories, one of which is Software Assurance.

Secure Coding and Code Testing

While we all attempt to write good code, how do we ensure this is happening? First, we need to make sure our developers are properly trained in secure coding techniques. We also need to ensure they understand the capabilities and weaknesses of the coding language or tools they are using. And finally, we need an easy way to review code as it's developed to ensure it is well-formed and avoids common security vulnerabilities and weaknesses.

Training and awareness are the foundation of secure coding, and code review and testing is one way to evaluate the code that is developed. Many integrated development environments (IDEs) provide inline assistance, hints, and context sensitive help while you're writing code.

There are also third-party products that provide for static code analysis, such as HP Fortify Static Code Analyzer, JetBRAINS ReSharper, some products from Veracode and Black Duck Software, to name just a few. Each of these tools has its own strengths and weaknesses, and can be prone to "false positives," but they can be another tool in your kit.

What about Scans?

Let's face it; we've become accustomed to performing ongoing security scans of our environments to provide us with a snapshot of known vulnerabilities and weaknesses. Many of these tools (such as Tenable Nessus or Rapid7's Nexpose) are focused on looking for existing configuration problems and missing patches. They don't look at home-grown applications, but instead focus on known problems with our operating systems and web or database servers.

There are many products now available to perform web-based application vulnerability scans as well. Examples include HP WebInspect and AppDetective, from Application Security; as well as numerous open-source tools. One tool that takes a slightly different approach is the Microsoft Attack Surface Analyzer. The focus of this tool is to examine your environment before deploying your application (as a baseline) and then again after deployment. This then highlights the changes introduced into the environment by the newly installed application.

This footprint is the "Attack Surface" introduced by your application. It shows what new files have been installed and highlights changes to registry keys, services, listening ports and access control lists. The tool enables the following:

  • Developers to view changes in the attack surface resulting from their applications

  • IT professionals to evaluate aggregate attack surface changes by LOB applications

  • IT security auditors to identify risk related to attack surface during threat risk assessments

  • IT security incident responders to better understand the state of securable objects on a system during investigations (if a baseline scan was taken of the system during the deployment phase)

    Again, each of these tools has its own strengths and weaknesses, but they are yet another tool to go in your security arsenal.

    Blend into a "Best of the Best" Approach

    This is a lot of information, and I've barely scratched the surface of what's available. I'm not proposal any single solution—instead I'm attempting to provide a list of resources to get you thinking about how you can improve your development efforts.

    I don't think any one of these approaches will solve all our problems. In fact, many of them won't make sense for your situation. I suggest reviewing the information, looking at the pros and cons; then blending the "best of the best" of each of these approaches into your existing process. If you're already using Agile Development, then I'm not proposing you change everything and switch to the Microsoft SDL approach.

    But perhaps you can employ Threat Models throughout your development process. Maybe one of these code analysis tools can provide you some insight into the capabilities of your development team and the security of the code they're producing. Maybe you have applications already built and deployed but you have no idea what threats they've introduced into your environment. Implementing scans of your web application can provide you with some perspective.

    If you're about to deploy a newly developed application, the Attack Surface Analyzer might show you just how your environment will be affected by this deployment.


    We have a large arsenal of tools available to us that can assist us in providing more secure applications almost immediately. The pressure is on us as application developers, security professionals, and consultants to start providing secure solutions to protect these critical corporate resources.

    I hope you find this information useful in that endeavor.

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


    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