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.
Now for software to be secure and resilient against hackers, it must take into account certain foundational concepts of information security. These of course include confidentiality, integrity, availability, authentication, authorization, accountability, and management of sessions, exceptions and errors, and configuration parameters. Now on their face, all of these may seem to be quite commonplace, even to the point of people being complacent about hearing these over and over and over again. And if it were not the case that people feel that way they might actually find their way into the building more often than they apparently do.
So the CSSLP candidate is expected to be familiar with these concepts, and how to apply them while designing and developing software, the topical area of this domain. They must be familiar with the principles of risk management and governance as well, as it applies to software development, perhaps a different perspective than we might have when we're looking at operations. The regulatory, privacy, and compliance requirements that impose the need for secure software and the repercussions of non-compliance must be understood. Trusted computing concepts that can be applied in software that is built in house or purchased are covered here. And it is imperative that the candidate is familiar with their applications.
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.