I luv you’z guys and I usually agree with both of you on all matters NAC-ish and 1X-ish, but I have to disagree with today’s flurry of 802.1X-adoption talk.
What exactly am I yapping about? Well, today Tim at Network World posted a nice article on the growing adoption of 802.1X. Shortly after, Alan jumped in with his post on ‘Is 802.1X in Your Future?’. You can see my notes below, and I definitely recommend reading the original articles. (more…)
No CommentsWith HP ProCurve’s acquisition of wireless provider Colubris, what should the industry expect?
Oh, who knows… but people have asked my opinion, so I’ll share my thoughts, musings and speculations with the masses. (more…)
No CommentsPer requests, and as part of the ‘ask JJ’ responses, I’ve been working on a couple of blog post series for you.
I’m juggling blog-moving with blog-posting and trying to find the happy medium. Coming soon though, are two NAC/1X series I hope you’ll enjoy… (more…)
No CommentsWell everyone- there’s something I’ve been wanting to tell you and now, after a year, I can!
Because of non-disclosure and other confidentiality contracts with various partners, vendors and manufacturers, we’ve had sealed lips for almost exactly 12 months. Now that it’s been made public by the media, I can share a little information with you and explain why I think you should be excited. (more…)
7 CommentsA quick update on the DNS vulnerability.Based on posts and Twitters last night from Dan and the snippits of information I gleaned from fellow Security Twits and bloggers… I think we are all aware that the DNS vulnerability is now out in the open.
The team that discovered the vulnerability was due to release details of the exploit at BlackHat (in 2 weeks). However, someone has reverse-engineered the vulnerability and released the details. The contents, or portions of the exploit were accidentally posted on a very prominent security blog yesterday then quickly removed. (Don’t ask, that’s a whole ‘nother story).
If your DNS server has not been patched, you are vulnerable now. More info on Dan’s (discoverer’s) site . You’ll notice his 13 > 0 post... letting us know instead of 13 days you now have 0.
If you haven’t patched your DNS server(s), please see my previous DNS vulnerability post, follow the links included for more information and instructions. Consider yourself now at risk.
# # #
No Comments
