You are here CertificationEC-Council Certified Secure Programmer
Friday, July 30, 2010
Secure Programming
About 95% of software bugs come from common, well-understood programming mistakes. Today's developers ... oftentimes don't have the academic discipline of secure software engineering and secure software development and training around what characteristics would create flaws in the program or lead to bugs. 
 
One of the problems is that the educational establishment generally doesn't teach secure programming at the undergradute, or even graduate level. 
EC-Council Certifications
Enquiry
Buy Official ECSP Courseware
View ECSP Course Outline

View CSAD Certification Path

Attend ECSP Training at iClass
Attend Training at iClass
View ECSP Certification Path

ECSP Exam Information

EC-Council Certified Secure Programmer
EC-Council’s Certified Secure Programmer and Certified Secure Application Developer are being offered to provide the essential and fundamental skills to programmers and application developers in secure programming.  The most prevalent reason behind buggy code and vulnerabilities being exploited by hackers and malicious code is the lack of adoption of secure coding practices. 
The Certified Secure Programmer and Certified Secure Application Developer  programs will ensure that programmers and developers are exposed to the inherent security drawbacks in various programming languages or architectures. They will be further trained  to exercise secure programming practices to overcome these inherent drawbacks in order to pre-empt bugs from the code
Certified Secure Programmer lays the basic foundation required by all application developers and development organizations to produce applications with greater stability and posing lesser security risks to the consumer. The Certified Secure Application Developer standardizes the knowledge base for application development by incorporating the best practices followed by experienced experts in the various domains. 
The distinguishing aspect of ECSP and CSAD is that unlike vendor or domain specific certifications, it exposes the aspirant to various programming languages from a security perspective. This drives greater appreciation for the platform / architecture / language one specializes on as well as an overview on related ones. 
 
Requirements
ECSP
  • To achieve EC-Council Certified Secure Programmer (ECSP), pass EC-Council’s Certified Secure Programmer  312-92 exam.
CSAD
  • To achieve EC-Council Certified Secure Application Developer (CSAD), achieve  an application development certification from any of the following vendors and pass EC-Council’s Certified Secure Programmer  312-92 exam.
  • For Linux: LCE / LCA / RHCE / LPI certification
  • For Microsoft: MCAD / MCSD / MCTS / MCPD certification
  • Technology Specialist: .NET Framework 2.0 Web Applications
  • Technology Specialist: .NET Framework 2.0 Windows Applications
  • Technology Specialist: .NET Framework 2.0 Distributed Applications
  • Professional Developer: Web Developer
  • Professional Developer: Windows Developer
  • Professional Developer: Enterprise Applications Developer
  • For Sun:  SCJD / SCEA certification
  • For Oracle: OCP certification ( DBA)
  • For IBM: Websphere certification
 
 
Benefits
  1. Exposure to a wide range of programming languages and train on well endorsed secure coding practices
  2. Improve your employability in development organizations
  3. Exposure to application development across platforms
  4. Enhance skills on writing better code and improve efficiency
  5. Build secure applications
 
Target Audience

The ECSP certification is intended for programmers who are responsible for designing and building secure Windows/Web based applications with .NET/Java Framework. It is designed for developers who have C#, C++ and Java development skills.

ECSP Training

Training for the certified secure programmer certification is available at EC-Council Accredited Training Centers across the world. Please contact us for locating a training center close to you.

 

 

 

 

Copyright 2010 by EC-CouncilPrivacy StatementTerms Of Use