CERT-CSIH: Renewal Process


In the evolving world of technology, innumerable unforeseen cyber-crimes occur every day. Under such circumstances, a Certified Security Incident Handler, or CSIH, plays a pivotal role in ensuring that these incidents are contained in an effective and timely manner. For this to be done effectively, CSIH professionals must actively engage in practices related to computer security incident handling, expand their skill set in risk assessment and participate in training that enhances their professional growth. As a CSIH professional, your role is to work closely with CSIRT in order to receive, review and respond promptly to incidents pertaining to computer security. The point is to solve these cyber-threats before they wreck a business’s IT infrastructure.

The CERT-CSIH certification is valid from the time it was earned to the end of that same month three years later. This means that if you earned your certificate on August 15th, it will be valid until August 31st three years later. The renewal process helps CSIH professionals to keep their certification active. In addition, meeting renewal requirements also ensure that you stay current with the latest incident-response knowledge in the wake of ever-changing technological advances.

In this article, we will examine CERT-CSIH renewal requirements, CERT-CSIH maintenance requirements, renewal activity logs, an audit of renewal activity logs, how long CERT-CSIH certification is good for and how to retake the exam.  

What Are the CERT-CSIH Renewal Requirements?

Once a candidate gets a CERT-CSIH certification, it is valid for a period of three years; after this, it is the responsibility of the CSIH to renew the certification again. The renewal process requires professional to complete 60 PDUs during a three-year life cycle and pay a renewal fee of $150. Additionally, completion of the CSIH certification renewal log is required, along with documentation that supports the PDU (Read more...)

*** This is a Security Bloggers Network syndicated blog from InfoSec Resources authored by Fakhar Imam. Read the original post at: