Common Software Vulnerabilities and Countermeasures
The course is part of this learning path
This course covers section one of CSSLP Domain Four: Common Software Vulnerabilities and Countermeasures. You'll learn the elements, ideas, concepts, and principles about what issues must be considered before embarking on a building program of secure software.
- Understand programming fundamentals
- Become familiar with different development methodologies
- Learn about common software attacks and the means of exploitation
This course is intended for anyone looking to develop secure software as well as those studying for the CSSLP certification.
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.
We will continue to build on the essentials of those elements, ideas, concepts, and principles about what issues must be considered when embarking, that is, before embarking on a building program of secure software. We'll discuss the active employment of those essentials and making the optimal use of them through better building. It is less important whether you are working in an Agile Scrum shop, a classic waterfall operation, or a DevsSecOps continuum than it is to ensure that the building of resilient, resistant, recoverable software incorporates structures and features that will make the final product effectively secure.
Every type of practice model can be, and must be able to do this if the final product of secure software will live up to the performance and reliability expectations. What we cover in this module will have a critical impact on the process and the final product produced by your project. In fact, it is more than likely that the impact will be significantly negative if they're not used to inform the functional and detailed design decisions reached in this phase. In this module, we will cover making the best use of these concepts.
So onward. So here we have our domain objectives. We're going to first attempt to understand programming fundamentals, we're going to become familiar with different development methodologies, we're going to know common software attacks and the means of exploitation, we're going to understand defensive coding principles and protection techniques, we're going to, when we're complete, know how to implement safeguards and countermeasures, and then how to conduct code peer reviews.
So here we have section one, common software vulnerabilities and countermeasures. In this, we're going to cover vulnerability information sources, common vulnerabilities in the countermeasures, input validation failures, general programming failures, enumerations, and then other common attack forms.
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.