Monday Sep 25

Posts Tagged ‘Wireless’

Feb
21/11
5 Classes of Wireless by Mission [Mgmt’s Guide to Wireless]
Last Updated on Tuesday, 31 January 2012 12:53
Written by jj
Monday, February 21st, 2011
Share

Wireless can be broken down into five primary classifications, based on its mission. These are classifications I’ve defined for use in discussing wireless goals with customers. (more…)

Tags: ,   |  Posted under Wireless  |  Comments  1 Comment
Aug
28/09
Listen to our PCI Wireless Podcast
Last Updated on Tuesday, 31 January 2012 04:52
Written by jj
Friday, August 28th, 2009
Share

Immediately after landing in Las Vegas for Black Hat and Defcon, I (literally) gathered my luggage and ran to the hotel to check in and hop on the StillSecureAfterAllTheseYears (SSAATY) Podcast with some of my favorite trouble-making colleagues for throw my two cents in on the PCI Wireless Podcast. (more…)

Tags: , , , , ,   |  Posted under Wireless  |  Comments  No Comments
Aug
19/08
ProCurve + Colubris… What to Expect
Last Updated on Tuesday, 31 January 2012 05:18
Written by jj
Tuesday, August 19th, 2008
Share

With 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…)

Tags: , , ,   |  Posted under Industry Insider, Wireless  |  Comments  No Comments
Aug
18/08
WEP Sucks, so Why are You Using It?
Last Updated on Tuesday, 31 January 2012 04:47
Written by jj
Monday, August 18th, 2008
Share

We all know it… we all talk about… we all say how ‘bad’ it is. Yes, we know WEP SUCKS – so why are you still using it?

Yes- I’m talking to YOU! (more…)

Tags: , , , ,   |  Posted under Wireless  |  Comments  No Comments
Jun
30/08
Feature Request #1: Stable Code
Last Updated on Monday, 21 July 2008 11:36
Written by JJ
Monday, June 30th, 2008
Share

         I have a note to all network hardware vendors…

Dear network vendor,

As someone that is forced to configure and implement security on your hardware, I would greatly appreciate stable code and properly functioning features. Unfortunately, I cannot always choose the hardware my customers are using in their infrastructure. However, if you would like for me to recommend they continue purchasing and using it, then the product must demonstrate to me that it is: capable, reliable, predictable and well-documented. If your product is not meeting these requirements, I’m forced to recommend other solutions to your (current) customer.

Stable Code. If I have to spend 2-6 hours per implementation working through your product’s bugs, and then must either spend time on a support call or spend time getting packet captures to prove to you it’s not working, I am not a happy camper because you’re slowing down my progress. Your customer is not happy because they’re paying for that time and I’m not cheap.

Features. Don’t publish in technical documentation that your product, or code can do something, only for me to find out later that it cannot. On-site in the middle of an implementation is not the time to architect Plan B. Let me know before, either through technical docs, white papers, best practices or release notes. I do read those. If you want to bend the truth, do it the marketing fluff, not my technical documents.

Documentation. If your product does do what you say it does, then please do document and explain the concepts and procedures. Examples are good, but explanations are mandatory. A correct CLI reference is always lovely as well. If there are got’chas or tricks, please also document those. Again, white papers or release notes are fine. Having to track down the one security engineer from your company that holds the magic key is not practical, nor scalable. Plus, he may be on vacation during my install, which would make me irate.

Support. If your product is not functioning or performing as expected, do NOT expect your customers to have a current maintenance contract to address a known issue or bug (or an un-known issue or bug for that matter). If they found a bug for you, you should probably give them a maintenance contract for a year… or two. If you don’t let us call support, I will find one of your pre-sales engineers and we will use him or her for post-sales support, which is not what you want them to do. But that’s your problem, not mine.

I believe that sums up the major issues. Specifically, I am interested in security, RADIUS, SSH, SNMP, DHCP and 802.1X functions. Before you add another bell or tweak another whistle, please make what you have works… consistently. That should be first, so it’s my Feature Request #1.

Respectfully,

jj

# # #

Tags: , , ,   |  Posted under Industry Insider  |  Comments  1 Comment

More Content

Find more of my content at
- Low Tech Hacking book
- Dark Reading
- Network Computing
- IANS
- SearchSecurity
- TechTarget

Get Social

RSSFacebookLinkedinYoutube

Subscribe

Enter your email address:

Delivered by FeedBurner

NetworkedBlogs