Systematic mapping of the literature on Secure Software Development

Hernan Nina Hanco, José Antonio Pow-Sang, Monica Villavicencio

Research output: Contribution to journalArticle (Contribution to Journal)peer-review

13 Scopus citations


The accelerated growth in exploiting vulnerabilities due to errors or failures in the software development process is a latent concern in the Software Industry. In this sense, this study aims to provide an overview of the Secure Software Development trends to help identify topics that have been extensively studied and those that still need to be. Therefore, in this paper, a systematic mapping review with PICo search strategies was conducted. A total of 867 papers were identified, of which only 528 papers were selected for this review. The main findings correspond to the Software Requirements Security, where the Elicitation and Misuse Cases reported more frequently. In Software Design Security, recurring themes are security in component-based software development, threat model, and security patterns. In the Software Construction Security, the most frequent topics are static code analysis and vulnerability detection. Finally, in Software Testing Security, the most frequent topics are vulnerability scanning and penetration testing. In conclusion, there is a diversity of methodologies, models, and tools with specific objectives in each secure software development stage.
Original languageEnglish
Article number9363884
Pages (from-to)36852-36867
Number of pages16
JournalIEEE Access
StatePublished - 26 Feb 2021


  • Software development
  • construction
  • design
  • requirements
  • security
  • systematic mapping review
  • testing
  • vulnerability


  • Article

OECD Category

  • Ingeniería de sistemas y comunicaciones

Ulima Repository Category

  • Ingeniería de sistemas / Software

Ulima Repository Subject

  • Computer security
  • Desarrollo de software
  • Seguridad informática
  • Software development


Dive into the research topics of 'Systematic mapping of the literature on Secure Software Development'. Together they form a unique fingerprint.

Cite this