Certified Application Security Engineer (CASE) . Net

Course overview

The Certified Application Security Engineer (CASE) credential is developed in partnership with large application and software development experts globally. The CASE credential tests the critical security skills and knowledge required throughout a typical software development life cycle (SDLC), focusing on the importance of the implementation of secure methodologies and practices in today’s insecure operating environment.

The CASE certified training program is developed concurrently to prepare software professionals with the necessary capabilities that are expected by employers and academia globally.It is designed to be a hands-on, comprehensive application security course that will help software professionals create secure applications. The training program encompasses security activities involved in all phases of the Software Development Lifecycle (SDLC): planning, creating, testing, and deploying an application.

Course Duration

3 Days

Cost

Audience

Individuals involved in the role of developing, testing, managing, or protecting a wide area of applications or individuals hoping to become application security engineers/analysts/testers.

Prerequisites

  • Be an ECSP (.NET/ Java) member in good standing or
  • Have a minimum of 2 years working experience in InfoSec/ Software domain.

Course Content

Understanding Application Security, Threats and Attacks

  • What is a Secure Application
  • Need for Application Security
  • Most Common Application Level Attacks
  • Why Applications become Vulnerable to Attacks
  • What Consistutes Comprehensive Application Security ?
  • Insecure Application: A Software Development Problem
  • Software Security Standards, Models and Frameworks

Security Requirements Gathering

  • Importance of Gathering Security Requirements
  • Security Requirement Engineering (SRE)
  • Abuse Case and Security Use Case Modeling
  • Abuser and Security Stories
  • Security Quality Requirements Engineering (SQUARE)
  • Operationally Critical Threat, Asset and Vulnerability Evaluation (OCTAVE)

Secure Application Design and Architecture

  • Relative Cost of Fixing Vulnerabilities at Different Phases of SDLC
  • Secure Application Design and Architecture
  • Goal of Secure Design Process
  • Secure Design Actions
  • Secure Design Principles
  • Threat Modeling
  • Decompose Application
  • Secure Application Architecture

Secure Coding Practices for Input Validation

  • Input Validation
  • Why Input Validation ?
  • Input Validation Specification
  • Input Validation Approaches
  • Input Filtering
  • Secure Coding Practices for Input Validation: Web Forms
  • Secure Coding Practices for Input Validation: ASP.NET Core
  • Secure Coding Practices for Input Validation: MVC

Secure Coding Practices for Authentication and Authorization

  • Authentication and Authorization
  • Common Threats on User Authentication and Authorization
  • Authentication and Authorization: Web Forms
  • Authentication and Authorization: ASP .NET Core
  • Authentication and Authorization: MVC
  • Authentication and Authorization Defensive Techniques : Web Forms
  • Authentication and Authorization Defensive Techniques : ASP .NET Core
  • Authentication and Authorization Defensive Techniques : MVC 

Secure Coding Practices for Cryptography

  • Cryptographic
  • Ciphers
  • Block Ciphers Modes
  • Symmetric Encryption Keys
  • Asymmetric Encryption Keys
  • Functions of Cryptography
  • Use of Cryptography to Mitigate Common Application Security Threats
  • Cryptographic Attacks
  • Techniques Attackers Use to Steal Cryptographic Keys
  • What should you do to Secure .Net Applications for Cryptographic Attacks
  • .NET Cryptographic Name Spaces
  • .NET Cryptographic Class Hierarchy
  • Symmetric Encryption
  • Symmetric Encryption: Defensive Coding Techniques
  • Asymmetric Encryption
  • Asymmetric Encryption: Defensive Coding Techniques
  • Hashing
  • Digital Signatures
  • Digital Certificates
  • XML SIgnatures
  • NET Core Specific Secure Cryptography Practices

Secure Coding Practices for Session Management

  • What are Exceptions/Runtime Errors ?
  • Need for Secure Error/Exception Handling
  • Consequences of Detailed Error Message
  • Exposing Detailed Error Messages
  • Considerations: Designing Secure Error Messages
  • Secure Exception Handling
  • Handling Exceptions in an Application
  • Defensive Coding practices against Information Disclosure
  • Defensive Coding practices against Improper Error Handling
  • ASP .NET Core: Secure Error Handling Practices
  • Secure Auditing and Logging
  • Tracing .NET
  • Auditing and Logging Security Checklists

Static and Dynamic Application Security Testing (SAST and DAST)

  • Static Application Security Testing
  • Manual Secure Code Review for Most Common Vulnerabilities
  • Code Review: Check List Approach
  • SAST Finding
  • SAST Report
  • Dynamic Application Security Testing
  • Automated Application Vulnerability Scanning Tools
  • Proxy-based Security Testing Tools
  • Choosing between SAST and DAST

Secure Deployment and Maintenance

  • Secure Deployment
  • Prior Deployment Activity
  • Deployment Activities: Ensuring Security at Various Levels
  • Ensuring Security at Host Level
  • Ensuring Security at Network Level
  • Ensuring Security at Application Level
  • Web Application Firewall (WAF)
  • Ensuring Security at IIS Level
  • Sites and Virtual Directories
  • ISAPI Filters
  • Ensuring Security at .NET Level
  • Ensuring Security at SQL Server Level
  • Security Maintenance and Monitoring

Enroll now

error: Content is protected !!