skip to main content
10.1145/2095536.2095590acmotherconferencesArticle/Chapter ViewAbstractPublication PagesiiwasConference Proceedingsconference-collections
short-paper

Software security for small development teams: a case study

Published: 05 December 2011 Publication History

Abstract

Microsoft is developing wide-spread software solutions like the Windows operating system and the Office suite. In order to improve security of their products, they have introduced the Microsoft Security Development Lifecycle (MS-SDL). Ample documentation about the MS-SDL is available, thus, allowing other companies to adopt the lifecycle as well. We were wondering whether an adoption of the lifecycle is possible and useful for real small development teams, e.g., for a single developing person. In order to find out, we have done a practical test, i.e., we have used the MS-SDL for the development of a small, but real-world software project. The findings will be presented in this paper.

References

[1]
Sommerville I. 2007. Software Engineering, 8th edition, Addison-Wesley.
[2]
Kent Beck, Cynthia Andres. Extreme Programming Explained: Embrace Change. Addison-Wesley Professional; 2 Edition, 2004.
[3]
Alistair Cockburn. Crystal Clear: A Human-Powered Methodology for Small Teams (Agile Software Development), Addison-Wesley Longman, Amsterdam, 2004.
[4]
Mike Cohn. Succeeding with Agile: Software Development Using Scrum, Addison-Wesley Signature, Addison-Wesley Longman, Amsterdam, 2009.
[5]
Boehm B. and Turner R. 2004. Balancing Agility and Discipline, Addison-Wesley.
[6]
Swiderski F. and Snyder W., 2004. Threat Modeling, Microsoft Press.
[7]
Microsoft 2011. The Microsoft SDL, www.microsoft.com/security/sdl
[8]
OWASP. 2007. OWASP CLASP v1.2. Comprehensive, Lightweight Application Security Process.
[9]
McGraw G. 2009. Software Security: Building Security In, 5th edition, Addison-Wesley.
[10]
Microsoft 2010. Security Development LifeCycle V. 5.0, Microsoft Press.
[11]
Howard M. Lipner S. 2006. The Security Development Life-cycle, Microsoft Press.
[12]
Curphey M., Scambray J., Olson E. 2003. Improving Web Application Security: Threats and Countermeasures, Microsoft Press.
[13]
Howard M., LeBlanc D. 2003. Writing Secure Code, Microsoft Press.
[14]
Microsoft. Improving Web Application Security: Threats and Countermeasures, http://msdn.microsoft.com/enus/library/ff649874.aspx
[15]
Hernan, S., Lambert, S., Ostwald, T., and Shostack, A. 2006. Uncover Security Design Flaws Using The STRIDE Approach. MSDN Magazine, Nov. 2006, http://msdn.microsoft.com/en-us/magazine/cc163519.aspx

Cited By

View all
  • (2025)Review of Techniques for Integrating Security in Software Development LifecycleComputers, Materials & Continua10.32604/cmc.2024.05758782:1(139-172)Online publication date: 2025
  • (2023)Blockchain-based model for tracking compliance with security requirementsComputer Science and Information Systems10.2298/CSIS210923060M20:1(359-380)Online publication date: 2023
  • (2020)A Maturity Model for Secure Requirements EngineeringComputers & Security10.1016/j.cose.2020.101852(101852)Online publication date: May-2020
  • Show More Cited By

Index Terms

  1. Software security for small development teams: a case study

    Recommendations

    Comments

    Information & Contributors

    Information

    Published In

    cover image ACM Other conferences
    iiWAS '11: Proceedings of the 13th International Conference on Information Integration and Web-based Applications and Services
    December 2011
    572 pages
    ISBN:9781450307840
    DOI:10.1145/2095536
    Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than ACM must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected]

    Publisher

    Association for Computing Machinery

    New York, NY, United States

    Publication History

    Published: 05 December 2011

    Permissions

    Request permissions for this article.

    Check for updates

    Author Tags

    1. security development lifecycle
    2. software development
    3. software lifecycle
    4. software security

    Qualifiers

    • Short-paper

    Conference

    MoMM '11

    Contributors

    Other Metrics

    Bibliometrics & Citations

    Bibliometrics

    Article Metrics

    • Downloads (Last 12 months)6
    • Downloads (Last 6 weeks)0
    Reflects downloads up to 07 Mar 2025

    Other Metrics

    Citations

    Cited By

    View all
    • (2025)Review of Techniques for Integrating Security in Software Development LifecycleComputers, Materials & Continua10.32604/cmc.2024.05758782:1(139-172)Online publication date: 2025
    • (2023)Blockchain-based model for tracking compliance with security requirementsComputer Science and Information Systems10.2298/CSIS210923060M20:1(359-380)Online publication date: 2023
    • (2020)A Maturity Model for Secure Requirements EngineeringComputers & Security10.1016/j.cose.2020.101852(101852)Online publication date: May-2020
    • (2014)Experiences with Threat Modeling on a Prototype Social NetworkInformation Security in Diverse Computing Environments10.4018/978-1-4666-6158-5.ch014(261-279)Online publication date: 2014

    View Options

    Login options

    View options

    PDF

    View or Download as a PDF file.

    PDF

    eReader

    View online with eReader.

    eReader

    Figures

    Tables

    Media

    Share

    Share

    Share this Publication link

    Share on social media