2010
DOI: 10.3745/jips.2010.6.1.091
|View full text |Cite
|
Sign up to set email alerts
|

The ISDF Framework: Towards Secure Software Development

Abstract: Abstract-The rapid growth of communication and globalization has changed the software engineering process. Security has become a crucial component of any software system. However, software developers often lack the knowledge and skills needed to develop secure software. Clearly, the creation of secure software requires more than simply mandating the use of a secure software development lifecycle; the components produced by each stage of the lifecycle must be correctly implemented for the resulting system to ac… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
4
1

Citation Types

0
9
0

Year Published

2011
2011
2023
2023

Publication Types

Select...
4
2
1

Relationship

0
7

Authors

Journals

citations
Cited by 11 publications
(9 citation statements)
references
References 24 publications
0
9
0
Order By: Relevance
“…These activities are described generally from a theoretical perspective and have a broader range of scope. The selection of the activities and execution order are left to the practitioner's discretion to make the processes more flexible and efficient [174].…”
Section: Claspmentioning
confidence: 99%
“…These activities are described generally from a theoretical perspective and have a broader range of scope. The selection of the activities and execution order are left to the practitioner's discretion to make the processes more flexible and efficient [174].…”
Section: Claspmentioning
confidence: 99%
“…Traditionally, security in software development is often viewed either as a remedy or patch deployed to solve security breaches or as an enhancement to a wholly developed software package [1]. As further emphasized by Alkussayer and Allen [1], developers only pay attention to security considerations as they approach the end of the development lifecycle, which is why such security solutions often come as add-on mechanisms and techniques before software systems deployment. Therefore, security issues were often reactively addressed when prompted by some undetected vulnerability or when such vulnerability may have even been exploited [1], [2].…”
Section: Introductionmentioning
confidence: 99%
“…Traditionally, security in software development is often viewed either as a remedy or patch deployed to solve security breaches or as an enhancement to a wholly developed software package [1]. As further emphasized by Alkussayer and Allen [1], developers only pay attention to security considerations as they approach the end of the development lifecycle, which is why such security solutions often come as add-on mechanisms and techniques before software systems deployment. Therefore, security issues were often reactively addressed when prompted by some undetected vulnerability or when such vulnerability may have even been exploited [1,2].…”
Section: Introductionmentioning
confidence: 99%
“…As further emphasized by Alkussayer and Allen [1], developers only pay attention to security considerations as they approach the end of the development lifecycle, which is why such security solutions often come as add-on mechanisms and techniques before software systems deployment. Therefore, security issues were often reactively addressed when prompted by some undetected vulnerability or when such vulnerability may have even been exploited [1,2].…”
Section: Introductionmentioning
confidence: 99%
See 1 more Smart Citation