Implementation of Secure Software Design and their impact on Application

Abstract

Vulnerability is associated with the system and it is a big risk for system and result in surplus maintenance cost. It is due to many reasons those are not considered during the stages of System Development Life Cycle (SDLC). During SDLC it may be reduced to minimum level. Millions of dollars waste due to vulnerable application and rescind working. Most of the software are not secure and cause Physical and Financial mutilation. It may not be possible to eliminate vulnerability completely but it might be reduced to the minimum level because it is the ongoing process. A web application using secure design patterns (SDPs) is presented in this paper. Two secure design patterns and their implementation are given. Secure Strategy Design Pattern (SSDP) and Secure Builder Design Pattern (SBDP) are purposed for two different forms SSDP is used for Driver information page and SBDP is used for Route information page. Special codes are used for inquiring whether valid user is using site or not. A class of encryption/decryption technique is added to add security. An encryption/decryption technique named SHA-1 is used. The result shows that SDPs are beneficial to all application developers especially for the developers of critical and sensitive systems. The system suits secure and design pattern makes it simple to understand its functionality. However, any other encryption/decryption techniques may also be applied on it in place of SHA-1. In future we plan to attach this class with other design patterns to make them secure from attackers and eliminate vulnerable points. Many features can be included in web application with the help of different design patterns and can be secured by attaching encryption/decryption class.

The practice of secure software development in SDLC: an investigation through existing model and a case study

“…Vulnerabilities associated with the system may be reduced to a minimum level during the SDLC. It may not be possible to eliminate vulnerability, but it might be reduced to a minimum level if security is treated as an ongoing process . Therefore, this research looks at the software development process as a whole, from the perspective of each development phase (SDLC), and seeks to determine important secure measures that must be employed at each phase to ensure highly secure products.…”

“…In many cases, it is only considered after the design of the system is completed or when a significant issue must be addressed. Currently, no software development processes or practices exist that consistently produce secure software . Therefore, it is recommended that developers adopt practices that can reduce software defects and, as a result, minimize any potential risk because of the lack of security attention during the process.…”

“…In addition, detailed information about the usage of secure software is rarely published. One important area, as noted by Ahmad et al ., , Arbain et al ., , and Devanbu and Stubblebine in more than a decade ago, is that focused on the non‐functional requirements of software security, are not well defined in software security research. The area place emphasizes on effective design and the use of policies and a framework for security requirements, to sufficiently address software security concerns in various software development projects.…”

Design Pattern and Security Influence on Application Development

“…To reduce accidental addition of vulnerability Secure Design Pattern (SDP) are used. Secure Strategy Design Pattern (SSDP) and Secure Builder Design Pattern (SBDP) were introduced and implemented in a web application [2]. SSDP is actually addition in working of Strategy design pattern and SBDP is extension in Builder design pattern.…”

“…Attackers cause problems by exploiting vulnerabilities in code [1]. Vulnerability is also known as a fault in the security of an information system that some time may be known or unknown [2]. Vulnerability is simply a design flaw or an implementation bug that allows a potential attack on the software in some way [1].…”