EH-Net

Ethical Hacking Discussions and Related Certifications => General Certification => Topic started by: BillV on July 20, 2009, 08:34:32 AM



Title: EC-Council ECE System
Post by: BillV on July 20, 2009, 08:34:32 AM
Just received this via email, wanted to pass along for anyone that may not have received it.

Quote
Dear Members,

EC-Council introduced the ECE Delta System to allow our members to record
activities and events connected with the re-certification requirement,
which became effective January 1, 2008. In 2009 the EC-Council Scheme
Committee; a member based network of volunteers that are recognized by
EC-Council and the society as key leaders in the field of information
security was formed to identify changes to our present EC-Council |
Continuing Education (E|CE) system and to ensure that our certifications
remain valuable and up-to-date, and that all EC-Council certified
professionals maintain and widen their knowledge base constantly to avoid
revocation of EC-Council’s certification status.

The comments/suggestions with regard to the existing ECE Delta Credit
System posted by our valuable Certified Members were evaluated by the
Members of the EC-Council Scheme committee. I am glad to announce that
most of the constructive feedback were approved by the Scheme Committee.
Based on the recommendation of the Scheme Committee we have incorporated
the changes to the current ECE Delta Credit System.

Please note that this new ECE Delta Credit System would become active from
September 1, 2009.

There will be a gestation period of 3 months wherein all those Certified
Members who are registered/unregistered and have yet to claim the minimum
credit points required to maintain their EC-Council Certifications have
the LAST chance to retain their EC-Council Certifications.
Certified Members who fail to register at the ECE Delta Portal and earn
the minimum ECE Credits prior to December 31, 2009 will risk having their
EC-Council Certifications revoked and will be subject to appeal to the
appeals committee.

We will try our best to reach out to all our Certified Members around the
globe and inform them about the recent changes to the ECE Delta System. We
humbly request each Certified Member reading this post to help spread the
news about the new ECE Delta Credit System to their peer/professional
network so that those members who have missed the ECE Delta Credit System
news are updated and have a chance to retain their EC-Council
Certification.

With your immense support and enthusiasm I am sure there would be none who
will miss this Final Call.

Thanks

Delta Admin
delta@eccouncil.org


Title: Re: EC-Council ECE System
Post by: Ants on July 20, 2009, 10:02:20 AM
Hi, do you know if they have or will provide details of what the new requirements are?


Title: Re: EC-Council ECE System
Post by: BillV on July 20, 2009, 12:26:22 PM
I'm not quite sure what you mean by requirements.

Does this help?

Quote
  • Education Course: 1 credit/hour
  • Higher Education: 10 credits/quarter hour, 15 credits/semester hour
  • Security Certification: 40 credits
  • Seminar/Conference/Event: 1 credit/hour
  • Speaking: 3 credits/hour (first presentation of material only)
  • Author Article/Chapter/Whitepaper: 10 credits
  • Author Book: 40 credits
  • Author New Open Source Tool: 40 credits
  • Identify New Vulnerability: 40 credits
  • Association Membership: 2 credits/year (charter), 3 credits/year (chapter-based), 1 credit/hour of meeting
  • Book/Article Review/Case Study: 5 credits (max 2/year)


Title: Re: EC-Council ECE System
Post by: geekyone on July 20, 2009, 12:52:15 PM
Quote
The comments/suggestions with regard to the existing ECE Delta Credit
System posted by our valuable Certified Members were evaluated by the
Members of the EC-Council Scheme committee. I am glad to announce that
most of the constructive feedback were approved by the Scheme Committee.
Based on the recommendation of the Scheme Committee we have incorporated
the changes to the current ECE Delta Credit System.


Has anyone been able to find out what "changes" they are making?


Title: Re: EC-Council ECE System
Post by: BillV on July 20, 2009, 12:57:13 PM
Most of the changes are to how credits are earned (posted above).

Other changes will mostly include enforcing some of the already established rules (such as the minimum credits earned per year, credits must be added within timeframe, etc.).


Title: Re: EC-Council ECE System
Post by: Ketchup on July 20, 2009, 02:04:32 PM
Bill,

I noticed they got rid of podcasts as a category.  Would podcasts and webcasts fall under Seminar/Conference/Event: 1 credit/hour?


Title: Re: EC-Council ECE System
Post by: BillV on July 20, 2009, 02:14:44 PM
Yep, that'd be a 1 credit/hour event.


Title: Re: EC-Council ECE System
Post by: geekyone on July 20, 2009, 03:33:07 PM
Sooooo....what if I create an Open Source Tool and let's call it GeekyonePwnsCEH.  For the sake of simplicity we will say this tool is a port scanner and everytime it finds an open port it emails Bill Gates.  When it is done I publish it on the web and include the source code.  Now I have authored a "new" open source tool (40 credits to me!).  Now my buddy comes along, who is also a CEH, and reviews my code and finds that I am a really crappy programmer (which is totally true).  He finds an exploit in my code and reports it to me while we are having beers after work (40 credits to him).  I fix the code.  Rinse and repeat once a year.   ::)  I sense a stirring in the force.


Title: Re: EC-Council ECE System
Post by: BillV on July 21, 2009, 06:30:34 AM
The tool wouldn't get approved because plenty of port scanners already exist. Unless it's doing something useful for the InfoSec community, your tool will be denied :)

Already the possibility exists that you can be audited to prove you have earned the credits you are reporting. Anything that will carry significant weight (e.g., a 40-credit "new" tool) will certainly be audited for uniqueness.


Title: Re: EC-Council ECE System
Post by: UNIX on July 22, 2009, 12:51:12 AM
Thanks for the info, BillV.

In general I really like the idea that one has to do something (continuously learning) in order to maintain the certificate and that nothing must be paid at a later point. I think when someone is really interested in security and take it seriously it is not hard to earn 40 credits/ year.

I wish other certificates would not get invalid after a certain period of time (e.g. three years).