Skip to main content

Educating our fellow Humans

I wrote this post in conjunction with my last "Top 10 hints" post, but somehow it disappeared.  So I thought I'd try and write it again, trying to remember the key points I hit.

Many of the people that read this blog are security professionals like me, my peers.  We learned about our profession, mostly on our own.  Self-taught individuals with a penchant for curiosity and the likeness to break things.  There are very few schools and certifications to be "professional" at what we do for a living, and it's because of that, that our community is so small.

Take a look at something like Defcon or Blackhat.  You can throw a stone at one of those conferences and usually hit about 4 people you know on a first name basis, and 10 people that you know by their online name.  Think about it.

Along the growth of our careers we've probably had a few mentors, four or five people during our professional growth that have pushed us in the correct direction.  Gave us hints, wrote blog posts, wrote books, wrote articles, and while you mostly taught yourself how to do this job, there probably are some people that you can point at in your career and say "he helped me by handing me my first copy of 2600".  I clearly remember the first person in my life who handed me my first copy of "2600" and "Blacklisted!411" magazines.  He was and remains to be my best friend and was the best man at my wedding, even though his job has nothing at all to do with computers (ironic, IMO).

As I was saying, the vast majority of the people that read this blog are either Apple people (who read because of my rantings on Apple), Google people (because of the same), or security people.  (God knows why you read my drivel?!  Thanks though.)

However, there is a group of you, especially the friends that I have on Facebook that I've pointed over here to get my content, that are not security people.  There are a group of you that are barely computer people.  You may think that getting on the "Internet" means clicking on the big blue "E" on the desktop.

Those are the people I'd like to make aware with those top 10 articles that I post.  With the Facebook article that I wrote on Saturday while my wife was napping on the couch.  Those are the people that I want to reach out to and help and say "yes, you do need antivirus on your Windows computer", and "Do you know what a firewall is on your computer?  Do you have it on?", and "No!  Don't click on that attachment! Are you crazy!?"

Be aware of what you are doing online.  Don't let one of your security questions be "What is your mother's maiden name?"

To my fellow security professionals:  Help out your fellow Humans.  They may take time, they may take patience, but they need our help.  The bad guys won't stop, the code won't get more secure.  There will always be holes, the bad guys have money, they are most likely, in some way-shape-or form already in your network, and they want what you have.  Help your fellow Humans, they need it.

Comments

Sam Pabon said…
Very dramatic ... But, very True ...
Good post J.
Chandler said…
Right on, well said.
Joel Esler said…
Thanks Chandler
Joel Esler said…
Thanks Sam. It's dramatic because it's sad.

Popular posts from this blog

Offset, Depth, Distance, and Within

Without going off the deep-end here and discussing every single Snort rule keyword, I just wanted to touch on a few modifiers that people sometimes misunderstand.  They aren't difficult, and hopefully after this explanation and a few examples, I can clear some of the air around these five modifiers.

The five modifiers that I am talking about are
OffsetDepthDistanceWithinnocaseThese five modifiers are not keywords of themselves, but rather they apply as modifiers to another keyword.  That keyword is "content". The content keyword is one of the easiest pieces of the Snort rules language as all it does is look for a particular string.  So for instance if I wanted to look for the word "joel" within a packet.  A simple:
content:"joel";Would allow me to do that.  The interesting part comes into play when you want to specify where inside of a particular packet you want the string "joel" to be looked for.  If you are running just a plain content ma…

Writing Snort Rules Correctly

Let me start off by saying I'm not bashing the writer of this article, and I'm trying not to be super critical.  I don't want to discourage this person from writing articles about Snort rules.  It's great when people in the Snort community step up and explain some simple things out there.  There are mistakes, it comes with the territory.  If you choose to be one of the people that tries to write Snort rules, you also choose to be someone who wants to learn how to do it better.  That's why I write this blog post, not to bash the writer, but to teach.

I noticed this post today over at the "Tao of Signature Writing" blog, and to be honest I glanced over most of it figuring it was a rehash of things I've already read or things that have already been written from countless people about "Here's how you write Snort rules!".  I scrolled down quickly skimming, not reading at all really, and noticed this part:
Now, let us look at the second questio…

Safari 5.1.4 now available

Safari 5.1.4 now available, fixes issues and improves performance | TUAW - The Unofficial Apple Weblog:


Improve JavaScript performanceImprove responsiveness when typing into the search field after changing network configurations or with an intermittent network connectionAddress an issue that could cause webpages to flash white when switching between Safari windowsAddress issues that prevented printing U.S. Postal Service shipping labels and embedded PDFsPreserve links in PDFs saved from webpagesFix an issue that could make Flash content appear incomplete after using gesture zoomingFix an issue that could cause the screen to dim while watching HTML5 videoImprove stability, compatibility and startup time when using extensionsAllow cookies set during regular browsing to be available after using Private BrowsingFix an issue that could cause some data to be left behind after pressing the "Remove All Website Data" button