Software Development Methodologies
The course is part of this learning path
This course is the fourth installment of four courses covering Domain 1 of the CSSLP, covering the topic of software development methodologies.
- Learn about the secure development lifecycle and the implications it has on your software
- Understand the various software development methods for keeping your environments secure
- Learn about the software development lifecycle
This course is designed for those looking to take the Certified Secure Software Lifecycle Professional (CSSLP) certification, or for anyone interested in the topics it covers.
Any experience relating to information security would be advantageous, but not essential. All topics discussed are thoroughly explained and presented in a way allowing the information to be absorbed by everyone, regardless of experience within the security field.
If you have thoughts or suggestions for this course, please contact Cloud Academy at firstname.lastname@example.org.
So we have reached the end of Domain 1: Secure Software Concepts. Now in these four modules, what we've covered is some basics. We have achieved an understanding of what underlies secure software. Through this discussion, I hope that you've become familiar with the practice of risk management and how it integrates with software development.
We should be able to apply the security concepts throughout the development life cycle, regardless of which management method we're going to use. We've talked about the various security models and how they may apply, what concepts they may lend to the project. Being familiar with the legal and regulatory factors and their effects on software development. Applying design methods to address these issues of performance and resilience, and understanding how security and assurance integrate into the acquisition process.
In the end, what we're trying to achieve ultimately, is a balance between the design and build, the security and the operations, throughout the life cycle in all phases, and all ways that are appropriate and reasonable to ensure that we produce the best product that conforms to the secure by design, secure by default, holy grail features that I mentioned at the beginning.
Mr. Leo has been in Information System for 38 years, and an Information Security professional for over 36 years. He has worked internationally as a Systems Analyst/Engineer, and as a Security and Privacy Consultant. His past employers include IBM, St. Luke’s Episcopal Hospital, Computer Sciences Corporation, and Rockwell International. A NASA contractor for 22 years, from 1998 to 2002 he was Director of Security Engineering and Chief Security Architect for Mission Control at the Johnson Space Center. From 2002 to 2006 Mr. Leo was the Director of Information Systems, and Chief Information Security Officer for the Managed Care Division of the University of Texas Medical Branch in Galveston, Texas.
Upon attaining his CISSP license in 1997, Mr. Leo joined ISC2 (a professional role) as Chairman of the Curriculum Development Committee, and served in this role until 2004. During this time, he formulated and directed the effort that produced what became and remains the standard curriculum used to train CISSP candidates worldwide. He has maintained his professional standards as a professional educator and has since trained and certified nearly 8500 CISSP candidates since 1998, and nearly 2500 in HIPAA compliance certification since 2004. Mr. leo is an ISC2 Certified Instructor.