Abstract

Security breaches are largely caused by the vulnerable software. Since individuals and organizations mostly depend on softwares, it is important to produce in secured manner. The first step towards producing secured software is through gathering security requirements. This paper describes Software Security Requirements Gathering Instrument (SSRGI) that helps gather security requirements from the various stakeholders. This will guide the developers to gather security requirements along with the functional requirements and further incorporate security during other phases of software development. We subsequently present case studies that describe the integration of the SSRGI instrument with Software Requirements Specification (SRS) document as specified in standard IEEE 830-1998. Proposed SSRGI will support the software developers in gathering security requirements in detail during requirements gathering phase.

Highlights

  • Requirements define necessary and desired capabilities of the proposed system

  • We presented Security Requirements Gathering Instrument (SSRGI) that provides a general approach to incorporate security during the requirements gathering phase of the software development process

  • It focuses on different types of security requirement that can be gathered from different roles

Read more

Summary

INTRODUCTION

Requirements define necessary and desired capabilities of the proposed system. requirements’ gathering is the first step towards the development of software. Common requirements are business rules, budgets, interfaces, reports, security, hardware, software etc. These requirements are defined by the stakeholders. It is stated that Common Criteria (CC) allows for the development of security requirements, and is being used on the architectural level of the security requirements. This made the usage of CC more beneficial [9]. We propose a Software Security Requirements Gathering Instrument (SSRGI) which can be used to gather the security requirements.

IEEE STANDARD 830-1998
Security Policy
Security Needs and Objectives
Security Requirements
CASE STUDY
RESULTS AND CONCLUSION

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.