Certification Path

The EC-Council Certified Secure Programmer v2 CSP certification includes only one 312-92 certification exam.

Who should take the 312-92 exam

The EC-Council Certified Secure Programmer v2 312-92 Exam certification is an internationally-recognized validation that identifies persons who earn it as possessing skilled as an EC-Council Certified Secure Programmer v2 CSP. If a candidate wants significant improvement in career growth needs enhanced knowledge, skills, and talents. The EC-Council Certified Secure Programmer v2 312-92 Exam certification provides proof of this advanced knowledge and skill. If a candidate knows associated technologies and skills that are required to pass EC-Council Certified Secure Programmer v2 312-92 Exam then he should take this exam.

EC-Council Certified Secure Programmer v2 312-92 Exam

EC-Council Certified Secure Programmer v2 312-92 Exam is related to EC-Council Certified Secure Programmer v2 CSP certification. This 312-92 exam which is related to Computer Hacking Forensics Investigator version 8 CHFI Certification. This validates the ability to produce applications with greater stability and posing lesser security risks to the consumer, designing and building secure Windows/Web-based applications with .NET framework or JAVA. Software Application Developers and Web Applications Developers usually hold or pursue this certification and you can expect the same job role after completion of this certification.

312-92 Exam topics

Candidates must know the exam topics before they start of preparation. Our 312-92 exam dumps will include the following topics:

• Vulnerability Disclosure Growth
• Impact of Vulnerabilities and Associated Costs
• Security Incidents
• Software Security Failure Costs
• Need for Secure Coding
• Java Security Overview
• Java Security Platform
• Java Virtual Machine (JVM)
• Class Loading
• Bytecode Verifier
• Class Files
• Security Manager
• Java Security Policy
• Java Security Framework
• Why Secured Software Development is needed?
• Why Security Bugs in SDLC?
• Characteristics of a Secured Software
• Security Enhanced Software Development Life Cycle
• Software Security Framework
• Secure Architecture and Design
• Design Principles for Secure Software Development
• Guidelines for Designing Secure Software
• Threat Modeling
• Threat Modeling Approaches
• Web Application Model
• Threat Modeling Process
• SDL Threat Modeling Tool
• Secure Design Considerations
• Secure Java Patterns and Design Strategies
• Secure Java Coding Patterns
• Secure Code Patterns for Java Applications
• Secure Coding Guidelines
• System Quality Requirements Engineering
• System Quality Requirements Engineering Steps
• Software Security Testing
• Secure Code Review
• Step 1: Identify Security Code Review Objectives
• Step 2: Perform Preliminary Scan
• Step 3: Review Code for Security Issues
• Step 4: Review for Security Issues Unique to the Architecture
• Code Review
• Source Code Analysis Tools
• Advantages and Disadvantages of Static Code Analysis
• Advantages and Disadvantages of Dynamic Code Analysis
• LAPSE: Web Application Security Scanner for Java
• FindBugs: Find Bugs in Java Programs
• Coverity Static Analysis
• Coverity Dynamic Analysis
• Veracode Static Analysis Tool
• Source Code Analysis Tools For Java
• Fuzz Testing
• File Input and Output in Java
• The java.io package
• Character and Byte Streams in Java
• Reader and Writer
• Input and Output Streams
• All File creations should Accompany Proper Access Privileges
• Handle File-related Errors cautiously
• All used Temporary Files should be removed before Program Termination
• Release Resources used in Program before its Termination
• Prevent exposing Buffers to Untrusted Code
• Multiple Buffered Wrappers should not be created on a single InputStream
• Capture Return Values from a method that reads a Byte or Character to an Int
• Avoid using write() Method for Integer Outputs ranging from 0 to 255
• Ensure Reading Array is fully filled when using read() Method to Write in another Array
• Raw Binary Data should not be read as Character Data
• Ensure little endian data is represented using read/write methods
• Ensure proper File Cleanup when a Program Terminates
• File Input/Output Best Practices
• File Input and Output Guidelines
• Serialization
• Implementation Methods of Serialization
• Serialization Best Practices
• Secure Coding Guidelines in Serialization
• Percentage of Web Applications Containing Input Validation Vulnerabilities
• Input Validation Pattern
• Validation and Security Issues
• Impact of Invalid Data Input
• Data Validation Techniques
• Whitelisting vs. Blacklisting
• Input Validation using Frameworks and APIs
• Regular Expressions
• Vulnerable and Secure Code for Regular Expressions
• Servlet Filters
• Struts Validator
• Struts Validation and Security
• Data Validation using Struts Validator
• Avoid Duplication of Validation Forms
• Struts Validator Class
• Enable the Struts Validator
• Secure and Insecure Struts Validator Code
• HTML Encoding
• Vulnerable and Secure Code for HTML Encoding
• Vulnerable and Secure Code for Prepared Statement
• CAPTCHA
• Stored Procedures
• Character Encoding
• Input Validation Errors
• Best Practices for Input Validation
• Exception and Error Handling
• Example of an Exception
• Handling Exceptions in Java
• Exception Classes Hierarchy
• Exceptions and Threats
• Erroneous Exceptional Behaviors
• Dos and Donts in Exception Handling
• Best Practices for Handling Exceptions in Java
• Logging in Java
• Example for Logging Exceptions
• Logging Levels
• Log4j and Java Logging API
• Java Logging using Log4j
• Vulnerabilities in Logging
• Logging: Vulnerable Code and Secure Code
• Secured Practices in Logging
• Percentage of Web Applications Containing Authentication Vulnerabilities
• Percentage of Web Applications Containing Authorization Bypass Vulnerabilities
• Introduction to Authentication
• Java Container Authentication
• Authentication Mechanism Implementation
• Declarative v/s Programmatic Authentication
• Declarative Security Implementation
• Programmatic Security Implementation
• Java EE Authentication Implementation Example
• Basic Authentication
• How to Implement Basic Authentication?
• Form-Based Authentication
• Form-Based Authentication Implementation
• Implementing Kerberos Based Authentication
• Secured Kerberos Implementation
• Configuring Tomcat User Authentication Setup
• Client Certificate Authentication in Apache Tomcat
• Client Certificate Authentication
• Certificate Generation with Keytool
• Implementing Encryption and Certificates in Client Application
• Authentication Weaknesses and Prevention
• Introduction to Authorization
• JEE Based Authorization
• Access Control Model
• Discretionary Access Control (DAC)
• Mandatory Access Control (MAC)
• Role-based Access Control (RBAC)
• Servlet Container
• Authorizing users by Servlets
• Securing Java Web Applications
• Session Management in Web Applications
• EJB Authorization Controls
• Common Mistakes
• Java Authentication and Authorization (JAAS)
• JAAS Features
• JAAS Architecture
• Pluggable Authentication Module (PAM) Framework
• JAAS Classes
• JAAS Subject and Principal
• Authentication in JAAS
• Subject Methods doAs() and doAsPrivileged()
• Impersonation in JAAS
• JAAS Permissions
• LoginContext in JAAS
• JAAS Configuration
• Locating JAAS Configuration File
• JAAS CallbackHandler and Callbacks
• Login to Standalone Application
• JAAS Client
• LoginModule Implementation in JAAS
• Phases in Login Process
• Java EE Application Architecture
• Java EE Servers as Code Hosts
• Tomcat Security Configuration
• Best Practices for Securing Tomcat
• Declaring Roles
• HTTP Authentication Schemes
• Securing EJBs
• Percentage of Web Applications Containing a Session Management Vulnerability
• Java Concurrency/ Multithreading
• Concurrency in Java
• Different States of a Thread
• Java Memory Model: Communication between Memory of the Threads and the Main Memory
• Creating a Thread
• Thread Implementation Methods
• Threads Pools with the Executor Framework
• Concurrency Issues
• Do not use Threads Directly
• Avoid calling Thread.run() Method directly
• Use ThreadPool instead of Thread Group
• Use notify all() for Waiting Threads
• Call await() and wait() methods within a Loop
• Avoid using Thread.stop()
• Gracefully Degrade Service using Thread Pools
• Use Exception Handler in Thread Pool
• Avoid Overriding Thread-Safe Methods with the non ThreadSafe Methods
• Use this Reference with caution during Object Construction
• Avoid using Background Threads while Class Initialization
• Avoid Publishing Partially Initialized Objects
• Race Condition
• Secure and Insecure Race Condition Code
• Deadlock
• Avoid Synchronizing high level Concurrency Objects using Intrinsic Locks
• Avoid Synchronizing Collection View if the program can access Backing Collection
• Synchronize Access to Vulnerable Static fields prone to Modifications
• Avoid using an Instance Lock to Protect Shared Static Data
• Avoid multiple threads Request and Release Locks in Different Order
• Release Actively held Locks in Exceptional Conditions
• Ensure Programs do not Block Operations while Holding Lock
• Use appropriate Double Checked Locking Idiom forms
• Class Objects that are Returned by getClass() should not be Synchronized
• Synchronize Classes with private final lock Objects that Interact with Untrusted Code
• Objects that may be Reused should not be Synchronized
• Be Cautious while using Classes on Client Side that do not Stick to their Locking Strategy
• Deadlock Prevention Techniques
• Secured Practices for Handling Threads
• Session Management
• Session Tracking
• Session Tracking Methods
• Types of Session Hijacking Attacks
• Countermeasures for Session Hijacking
• Countermeasures for Session ID Protection
• Guidelines for Secured Session Management
• Percentage of Web Applications Containing Encryption Vulnerabilities
• Need for Java Cryptography
• Java Security with Cryptography
• Java Cryptography Architecture (JCA)
• Java Cryptography Extension (JCE)
• Attack Scenario: Inadequate/Weak Encryption
• Encryption: Symmetric and Asymmetric Key
• Encryption/Decryption Implementation Methods
• SecretKeys and KeyGenerator
• The Cipher Class
• Attack Scenario: Man-in-the-Middle Attack
• Digital Signatures
• The Signature Class
• The SignedObjects
• The SealedObjects
• Insecure and Secure Code for Signed/Sealed Objects
• Digital Signature Tool: DigiSigner
• Secure Socket Layer (SSL)
• Java Secure Socket Extension (JSSE)
• SSL and Security
• JSSE and HTTPS
• Insecure HTTP Server Code
• Secure HTTP Server Code
• Attack Scenario: Poor Key Management
• Keys and Certificates
• Key Management System
• KeyStore
• Implementation Method of KeyStore Class
• KeyStore: Temporary Data Stores
• Secure Practices for Managing Temporary Data Stores
• KeyStore: Persistent Data Stores
• Key Management Tool: KeyTool
• Digital Certificates
• Certification Authorities
• Signing Jars
• Signing JAR Tool: Jarsigner
• Signed Code Sources
• Code Signing Tool: App Signing Tool
• Java Cryptography Tool: JCrypTool
• Java Cryptography Tools
• Dos and Donts in Java Cryptography
• Best Practices for Java Cryptography
• Average Number of Vulnerabilities Identified within a Web Application
• Computers reporting Exploits each quarter in 2011, by Targeted Platform or Technology
• Introduction to Java Application
• Java Application Vulnerabilities
• Cross-Site Scripting (XSS)
• Cross Site Request Forgery (CSRF)
• Directory Traversal
• HTTP Response Splitting
• Parameter Manipulation
• XML Injection
• SQL Injection
• Command Injection
• LDAP Injection
• XPATH Injection
• Injection Attacks Countermeasures