Skip to main content

White Hat Hacker -


"Certified WhiteHat Hacker (CWHH)", a course that will be helpful for a person to get into the Ethical Hacking world. - 

Why CWHH? 
There are totally 5 Lakhs security professional needed in India. People do a general certification course to get into the InfoSec field.  But most of them lack the tech knowledge needed for cyber security.  There are countable number of whitehat hackers who are at cyber security.  CSPF felt that there is need for creating awareness on cybersecurity and Ethical Hacking practices for students in colleges. 

How many levels are in CWHH and can you give more info on that? 
CWHH level-I is subsidized course on Ethical Hacking for college students.  It happens in two ways, most often colleges invite us to do the course in their premises;The second method, we announce the course in common place where students of all colleges can register online and do attend the course.  

CWHH level-II focuses on advanced cybersecurity and provides hands on training.

CWHH level-III and CWHH level-IV are for advanced users. It will be imparted to candidates from corporate who have minimum 2 experience in cybersecurity. We will conduct psychometric test to assess ethics of a person.

CWHH level-V is awarded to white hat hackers who are talented by themselves.  It is mostly given to exploit finders and exploit writers.  It is more given as mark of respect.  CSPF  invites applications from such talented experts.

See more at: http://www.ehackingnews.com/2013/10/certified-whitehat-hacker-training.html#sthash.7fK2qeXY.dpuf

WhiteHat Hacker Level I

 

The Course Contents are:

a)    Introduction.

b)    Information Gathering.

c)    Email Hacking Methodologies.

d)    Password Cracking Techniques.

e)    Sniffing and MITM’s.

f)    Google Hacking.

g)    Facebook Hacking.

h)    Proxies and Anonymity.

i)     Deep Dark Web.

j)     Incapsula Introduction.

k)    Windows Hacking.

l)     Sandboxing and Virtual Machines.

m)  Session Hijacking.

n)    Website Hacking Techniques/Web Application Hacking Techniques.

 o)    Social Engineering.

p)    Hacking Online Games.

q)    Hands on DEMO of various Security Tools.

r)    Credit Card Frauds.

s)    Backtrack Basics.

t)     Steganography.

 

Refer : http://www.meraevents.com/event/39805

Comments

Popular posts from this blog

IPv4 header to requests when a client is using IPv6

  What is Pseudo IPv4? As a stopgap to accelerate the adoption of IPv6, Cloudflare offers Pseudo IPv4 which supports IPv6 addresses in legacy applications expecting IPv4 addresses. The goal is to provide a nearly unique IPv4 address for each IPv6 address, using Class E IPv4 address space, which is designated as experimental and would not normally see traffic. To learn more see  here . Options Add header:  Add additional Cf-Pseudo-IPv4 header only Overwrite headers:  Overwrite the existing Cf-Connecting-IP and X-Forwarded-For headers with a pseudo IPv4 address Cloudflare

IIS 7 Tip # 5 Run a command when Rapid Fail Protection is triggered

Rapid-Fail Protection disables application pools if they crash multiple times within in a specified time period. This prevents the failing application pool from getting into a continuous loop of crashing and restarting. This protects other application pools running on the server as repeated failures can consume lot of system resources. When rapid-fail protection kicks in it stops the application pool that is repeatedly crashing and your clients will start getting a 503 – Service Unavailable error. An administrator will have to manually enable the application pool again. You also have to option to configure an executable to run when ever rapid-fail protection is triggered. For example below I have configured the application pool to restart the IIS service using iisreset.exe … the /rebootonerror will reboot the whole server if iisreset.exe for some reason fails to restart the services. Refer http://blogs.msdn.com/b/vijaysk/archive/2009/03/13/iis-7-tip-5-run-a-command-when-rapid-f...

SSL Certificates without Non-FQDNs- Fully Qualified Domain Name

Over the years, publicly-trusted CAs have issued SSL certificates with domain names of different types. The most common is the Fully Qualified Domain Name (FQDN). This is a certificate that has been issued with a name registered with an entity that manages a top-level domain (TLD), for example server1.domain.com. The differentiating characteristic about an FQDN is that it is unique . There is one controller of domain.com and that controller determines who can have any name under that root, such as server1.domain.com. Along the way, public CAs also issued certificates with non-FQDNs, such as: Server host name only, for example: server1 Server name with non-managed TLD, for example: server1.domain.local (In this example, local is not a TLD per ICANN.) Reserved IP addresses (In this case, the IP address cannot be registered, see IPv4 and IPv6.) Many SSL certificates have been issued that contain non-unique domain identifiers. Correspondingly, there are many security risks w...