Security testing C and C++ applications

CYDCpTst3d
3 days
C
C++

Platform

Linux, Windows

Preparedness

General C/C++ development

Audience

C/C++ developers and testers

Group size

12 participants

Labs

Hands-on

Outline

  • Cyber security basics
  • Buffer overflow
  • Security testing
  • Common software security weaknesses
  • Using vulnerable components
  • Wrap up

Objective list

  • Getting familiar with essential cyber security concepts
  • Understanding security testing methodology and approaches
  • Getting familiar with common security testing techniques and tools
  • Handling security challenges in your C and C++ code
  • Identify vulnerabilities and their consequences
  • Learn the security best practices in C and C++

Description

Your application written in C and C++ is tested functionally, so you are done, right? But did you consider feeding in incorrect values? 16Gbs of data? A null? An apostrophe? Negative numbers, or specifically -232? Because that’s what the bad guys will do – and the list is far from complete.

Testing for security needs a remarkable software security expertise and a healthy level of paranoia, and this is what this course provides: a strong emotional engagement by lots of hands on labs and stories from real life.

A special focus is given to finding all discussed issues during testing, and an overview is provided on security testing methodology, techniques and tools.

So that you are prepared for the forces of the dark side.

So that nothing unexpected happens.

Nothing.

Table of contents

  • Cyber security basics
    • What is security?
    • Threat and risk
    • Cyber security threat types
    • Consequences of insecure software
      • Constraints and the market
      • The dark side
    • Categorization of bugs
      • The Seven Pernicious Kingdoms
      • SEI Cert Secure Coding Guidelines
  • Buffer overflow
    • Assembly basics and calling conventions
      • x64 assembly essentials
      • Registers and addressing
      • Most common instructions
      • Calling conventions on x64
        • Calling convention – what it is all about
        • The stack frame
        • Stacked function calls
    • Memory management vulnerabilities
      • Memory management and security
      • Vulnerabilities in the real world
      • Buffer security issues
      • Buffer overflow on the stack
        • Buffer overflow on the stack – stack smashing
        • Exploitation – Hijacking the control flow
        • Lab – Buffer overflow 101, code reuse
        • Exploitation – Arbitrary code execution
        • Injecting shellcode
        • Lab – Code injection, exploitation with shellcode
      • Pointer manipulation
        • Modification of jump tables
        • Overwriting virtual function tables
    • Best practices and some typical mistakes
      • Unsafe functions
      • Dealing with unsafe functions
      • Lab – Fixing buffer overflow
      • What’s the problem with asctime()?
      • Using std::string in C++
      • Unterminated strings
      • readlink() and string termination
      • Manipulating C-style strings in C++
      • Malicious string termination
      • Lab – String termination confusion
      • String length calculation mistakes
      • Off-by-one errors
      • Allocating nothing
      • Testing for typical mistakes
  • Buffer overflow
  • Security testing
    • Security testing vs functional testing
    • Manual and automated methods
    • Security testing methodology
      • Security testing – goals and methodologies
      • Overview of security testing processes
      • Identifying and rating assets
        • Preparation
        • Identifying assets
        • Identifying the attack surface
        • Assigning security requirements
        • Lab – Identifying and rating assets
      • Threat modeling
        • Attacker profiling
        • SDL threat modeling
        • Mapping STRIDE to DFD
        • DFD example
        • Attack trees
        • Attack tree example
        • Lab – Crafting an attack tree
        • Misuse cases
        • Misuse case examples
        • Risk analysis
        • Lab – Risk analysis
      • Security testing approaches
        • Reporting, recommendations, and review
  • Common software security weaknesses
    • Security features
      • Authentication
        • Authentication basics
        • Authentication weaknesses
        • Case study – PayPal 2FA bypass
        • User interface best practices
      • Password management
        • Inbound password management
          • Storing account passwords
          • Password in transit
          • Lab – Why is just hashing passwords not enough?
          • Dictionary attacks and brute forcing
          • Salting
          • Adaptive hash functions for password storage
          • Password policy
            • NIST authenticator requirements for memorized secrets
            • Password length
            • Password hardening
            • Using passphrases
          • The Ashley Madison data breach
            • The dictionary attack
            • The ultimate crack
            • Exploitation and the lessons learned
          • Password database migration
            • (Mis)handling NULL passwords
            • Testing for password management issues
        • Outbound password management
          • Hard coded passwords
          • Best practices
          • Lab – Hardcoded password
          • Protecting sensitive information in memory
            • Challenges in protecting memory
            • Heap inspection
            • Compiler optimization challenges
            • Sensitive info in non-locked memory
      • Authorization
        • Access control basics
        • File system access control
          • Improper file system access control
          • Ownership
          • chroot jail
          • Using umask()
          • Linux filesystem
          • LDAP
        • Access control in databases
        • Privileges and permissions
          • Permission manipulation
          • Incorrect use of privileged APIs
        • Permission best practices
          • Principle of least privilege
          • Principle of separation of privilege
          • Permission granting and handling
  • Using vulnerable components
    • Assessing the environment
    • Hardening
    • Vulnerability management
      • Patch management
      • Vulnerability databases
      • Lab – Finding vulnerabilities in the used components
  • Common software security weaknesses
    • Input validation
      • Input validation principles
        • Blacklists and whitelists
        • Data validation techniques
        • What to validate – the attack surface
        • Where to validate – defense in depth
        • How to validate – validation vs transformations
        • Output sanitization
        • Encoding challenges
        • Validation with regex
      • Injection
        • Injection principles
        • Injection attacks
        • Code injection
          • OS command injection
            • Lab – Command injection
            • OS command injection best practices
            • Avoiding command injection with the right APIs
            • Lab – Command injection best practices
            • Case study – Shellshock
            • Lab – Shellshock
            • Testing for command injection
          • Process control – library injection
            • DLL hijacking
            • Lab – DLL hijacking
      • Integer handling problems
        • Representing signed numbers
        • Integer visualization
        • Integer promotion
        • Integer overflow
        • Lab – Integer overflow
        • Signed / unsigned confusion
        • Lab – Signed / unsigned confusion
        • Integer truncation
        • Lab – Integer truncation
        • Case study – Wannacry
        • Best practices
          • Upcasting
          • Precondition testing
          • Postcondition testing
          • Using big integer libraries
          • Best practices in C
          • UBSan changes to arithmetics
          • Best practices in C++
          • Lab – Integer handling best practices in C++
      • Other numeric problems
        • Division by zero
        • Working with floating-point numbers
        • Testing for numeric problems
    • Time and state
      • Race conditions
        • Race condition in object data members
        • File race condition
          • Lab – TOCTTOU
          • Insecure temporary file
        • Potential race conditions in C/C++
          • Race condition in signal handling
          • Forking
          • Bit-field access
  • Security testing
    • Security testing techniques and tools
      • Code analysis
        • Security aspects of code review
        • Static Application Security Testing (SAST)
        • Using static analysis tools
      • Dynamic analysis
        • Security testing at runtime
        • Penetration testing
        • Stress testing
        • Dynamic analysis tools
        • Dynamic Application Security Testing (DAST)
        • Fuzzing
        • Fuzzing techniques
        • Fuzzing – Observing the process
  • Wrap up
    • Secure coding principles
      • Principles of robust programming by Matt Bishop
      • Secure design principles of Saltzer and Schröder
    • And now what?
      • Further sources and readings
      • C and C++ resources

Pricing

3 days Session Price

2250 EUR / person

  • Live, instructor led classroom training
  • Discussion and insight into the hacker’s mindset
  • Hands-on practice using case studies based on high-profile hacks and live lab exercises
Customized Course

Tailor a course to your preferences

  • Send us a brief description of your business’s training needs
  • Include your contact information
  • One of our colleagues will be in touch to schedule a free 45 minute pre-training consultation

Inquiry

Interested in the trainings but still have some questions? Curious about how you can customize a training for your team? Send us a message and a team member will be in touch within 24 hours.

This field is required

This field is required

Send us your phone number if you prefer to discuss further on a call

This field is required

This field is required

This field is required

This field is required