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

Anti-tampering Techniques

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

Throughout all of this, we need to have anti-tampering techniques that are included. Now nearly all software companies providing updates and patches through the internet, these all experience different ways in which their software can be tampered with and we therefore have the necessity to validate a the authenticity of origin and the integrity of the deliverable. And this is more important than ever. Trust no one.

Part of how we try to prevent these code modules from being tampered with without our knowledge is the use of code signing technologies that employ PKI. This helps to ensure a higher levels of trust and assurance that these are not being tampered with and that they contain malware insertions that go otherwise undetected. And this is a frequent tool to ensure that we have higher levels of trust and that the code product has a higher level of integrity.

Now, the process to perform this is nearly identical to the digital signature processing that assures authentication of source, integrity of content, and the non-repudiation of sender. But code signing is not an assurance against buggy software, only assurance of trustworthiness in the proof of its source.

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.