1. Home
  2. Training Library
  3. Security
  4. Security Courses
  5. CSSLP Domain 4:3 - Secure Coding Operations

Build Environment

Contents

keyboard_tab
Secure Coding Operations
2
Code Analysis
PREVIEW2m 36s
3
Code/Peer Review
PREVIEW1m 37s

The course is part of this learning path

Start course
Overview
Difficulty
Beginner
Duration
16m
Students
68
Ratings
5/5
starstarstarstarstar
Description

This course covers section three of CSSLP Domain Four: Secure Coding Operations. You'll learn about code analysis, code reviews, secure build environments, anti-tampering techniques, and version management.

Learning Objectives

  • Learn how to analyze code and review it
  • Understand how to ensure that build environments are secure
  • Understand the importance of anti-tampering techniques and version control when building software

Intended Audience

This course is intended for anyone looking to develop secure software as well as those studying for the CSSLP certification.

Prerequisites

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.

Transcript

We have of course, to make sure that the building of our secure software takes place in an environment that has itself been built to be secure. Not exactly a clean room, but an environment that we have taken great pains to ensure will not adversely affect what is being built within it. Now the execution process to achieve the goals of security and performance and reliability and the balance amongst them must create an environment that will assure these conditions and the methods are possible and can attain them.

Now, the environment that we build is of course, going to be a clear model and provide a process for a secure software development life-cycle. It should be independent of object-oriented development or waterfall or iterative or DevSecOps methods to ensure that it has no hard-coded elements that inherently limit its adaptability based in the kind of model that you use in which to build it. So regardless of method it must be fully integrated to ensure optimal product and integrity through the highly evolved team workflow. There is of course, the IDE the Integrated Development Environment.

Now this is a congealed environment that brings together a variety of tools, methods checkers, compilers, code examiners, fuzzers and others to enable multifaceted design, build and test of the software that we're seeking to construct as secure. It will allow for syntax highlighting to show structures, keywords and syntax errors. It allows for code completion, sort of like an auto-complete intended to speed up programming and tooling intelligent code completion as it learns.

We have to have version control and this automates the process by providing integrated version configuration management. It brings tools to do debugging, compilation, fuzzing and other methods, and it will do workflow tracking. Now examples include of course, things like Microsoft Studio, Eclipse and Android Studio, to bring all of these tools to bear in the integrated environment. But we go back to producing a clean and secure build environment in which to use them.

About the Author
Students
6965
Courses
75
Learning Paths
17

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.