The Ugly Truth about Vulnerabilities

 The Ugly Truth

Photo by Ga on Unsplash

Grey Hat Developer

4 December 2010

The ugly truth that no one wants to admit is this. Wait. Let’s back up. Before proceeding I must clarify who the no one of this ugly truth is. No one currently operating nor the guy and gal next door who are just opening up shop. No one wants to admit the ugly truth about vulnerabilities. The ugly truth is every system has them. Period.

No, not true you say. I beg to differ. In fact, I’m going out on a limb to say you have not only one but multiple vulnerabilities in your system.

Let’s see what NIST’s definition of a vulnerability is. NIST, (the National Institute of Standards and Technology), defines vulnerabilities as weaknesses in information systems, system security procedures, internal controls, or implementations that could be exploited or triggered by a threat source.


“To my hacker friends who try to lift the veil of privacy in order to expose corruption, be careful that your Utopian dreams don’t become a nightmare.” – Matthew William Blake

However, my friend, I only used Target as an example to shed light on another point about vulnerabilities. The Target hack wasn’t a result of Target’s systems themselves being hacked but rather a third-party vendor who Target was working with being hacked. In layman’s terms, Target was hacked through someone they trusted very much. Do you have any partners or third-parties that you work with who you trust very much?

As usual this post was not meant to scare or belittle you, but only to enlighten you. If you gained any insight into vulnerabilities and how they may affect your organization please subscribe here for more, follow us here, and like us here. With that, I am going to leave you how I came…in peace, so, Peace!

Hack on, Ladz and Gentz….