Abstract
Since the advent and astronomical rise of the Internet and E-business, organizations must secure their computer systems or risk malicious attacks. While there have been several software lifecycle process standards (SLPS) for both military and industrial software development, their activities and deliverables are not yet integrated with security engineering (SE) activities. This lack of integration has created conflicts among the system development stakeholders (e.g. system acquirers and developers) during secure information systems development projects. This paper proposes an integration model that interweaves all the process activities and deliverables of SLPS with SE activities, taking IEEE/EIA 12207 as an example of SLPS. This model provides practical guidelines for the development of secure information systems while informing stakeholders how SLPS is related to the SE activities.
Sign-in/Register to access full text options 
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 callDisclaimer: 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.
