Skip to main content

Sourcefire on Twitter

Since Twitter is the latest bandwagon for the tech industry (as well as everyone else, including CNN) to jump on, not saying we have a bunch of bandwagon followers (I’m certainly one), but at Sourcefire, we have several people who have joined Twitter and post often. (And even more who don’t post very much at all.) So I thought I’d compile a quick list.


These people are all humans, not bots, and they have their own opinions, their opinions may or may not represent Sourcefire as a whole, but they are entitled to their opinions just like you all are. I’d recommend if you need to contact someone from Sourcefire, Twitter is not how you do it. Either through Support (if you are a customer) or via email. I have no idea when anybody checks their Twitter account, if, at all.


I thought I’d throw this together because recently our Marketing department did an email blast out to a bunch of people, recommending they follow several of us on Twitter. However, there were only three people listed. I thought it was cool for Marketing to hand me an extra 60 or so followers, but I thought I would help out everyone else that would like some followers on Twitter too.

Follow at your own risk, there are the people’s own accounts, not work related accounts.


http://twitter.com/mroesch -- Marty Roesch, Creator of Snort and Sourcefire Chief Technical Officer.

http://twitter.com/VRT_Sourcefire -- The Sourcefire Vulnerability Research Team.

http://twitter.com/btpollard -- Sourcefire’s Vice President of IT, also a musician in his spare time, also runs 140-seconds.com

http://twitter.com/kmx2600 -- Matt Wachinski Senior Director of the Vulnerability Research Team

http://twitter.com/pusscat -- Lurene Grenier, Team Lead in the VRT, also author of God-knows-what in Metasploit.

http://twitter.com/awilliams -- Andrew Williams, Team Lead in Product Development

http://twitter.com/leonward -- Leon Ward, Security Engineer over in the UK.

http://twitter.com/vrybdpkt -- Jason Brvenik, Senior Director of Security Engineering

http://twitter.com/ericlhoward -- Eric Howard, Security Engineer in the USA.

http://twitter.com/enhancedx -- JJ Cummings, also the Author of PulledPork, Professional Services (like me)

http://twitter.com/cjacob -- Director of Security Engineering, Eastern Division

http://twitter.com/jnaylor01 -- IT Support Engineer, got me a new MacBook Pro to replace my powerbook. So awesome.

http://twitter.com/tryke -- Ryan Jordan, one of our Software Engineers on Snort

http://twitter.com/dbruzek -- Dina Bruzek, Senior Director of Product Development

http://twitter.com/kpyke -- Matt Olney, one of our Sourcefire VRT Members and great photographer.

http://twitter.com/jamesjtucker -- James Tucker, one of our Security Engineers in Sweden.

http://twitter.com/tedbedwell -- Ted Bedwell, Manager in Product Development

http://twitter.com/kschar -- Ken Schar, Security Engineer in Arizona

http://twitter.com/torontomiller -- Marti Toronto Miller -- One of the (many) awesome people in HR.

http://twitter.com/jjtucker -- Jenn Tucker (I think) -- One of our Engineering Administrators.

http://twitter.com/pieterclaassen -- Pieter Claassen, one of our Security Engineer in like, Norway, or something.

http://twitter.com/evilcazz -- Brian Caswell -- One of our VRT Engineers, as well as one of the Shmoo.

http://twitter.com/allenmale -- International Sales person, Allen Male. Man of Mystery.

http://twitter.com/CelticRaven -- Jason Keller -- One of our Professional Services guys.

http://twitter.com/chriskelley -- Manager of Recruiting -- Chris Kelley. If you want to work for us, this is the guy to suck up to.

http://twitter.com/linuxgeek247 -- I am pretty sure this is Christopher McBee. He’s in IT, he also plays Xbox with the group, therefore, cool.

http://twitter.com/mguiterman -- Mike Guiterman, Marketing guy in charge of Snort.

http://twitter.com/alanptak -- Alan Ptak, Another Professional Services guy.

http://twitter.com/mbrannig -- Matt Brannigan, Principle Engineer in Product Development

http://twitter.com/joelesler -- Me.


Well, that’s pretty much all I can find right now on my list. I know there are more, and to those people I missed, I apologize. I’ll add you if you want.

Comments

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