Latest software headlines from Network World:
Kernel developers, Wall Street to come together
Zoho launches e-mail app with offline, mobile access
|
Does Verizon's Voyager stack up to the iPhone? |
|
|
5 IT skills that won't boost your salary
[1,407]
Women 4 times more likely than men to cough up personal info
[589]
Japan's 10 funniest tech-related commercials [Videos]
[407]
Throwing away a promo CD is "unauthorized distribution"?
[1,265]
Adults too quick to dismiss educational video games
[682]
Attack of the iPhone clones [Slideshow]
[578]
10 things IT needs to know about AJAX
[1,258]
This Year's 25 Geekiest 25th Anniversaries [Slideshow]
[409]
|
|
NAC Lessons Learned
Wow, some of these comments are amazing to down right stupid and it’s obvious that either “amazing or stupid” know nothing about NAC. Well, I believe that anybody planning on jumping into this market as a vendor had better decide early on from what angle to approach NAC. Those two angle are CISCO (hardware) or Microsoft which is software based, and the problem being CISCO is very protective of its proprietary technology, even more so than Microsoft, just look at the WiFi standard and why its been so slow to get off the ground. CISCO has a serious strangle hold on their market and they can afford to build NAC into the product or allow some type of OS upgrade for older systems. I wouldn’t say that CISCO is the reason these companies went “tits up” but I will say those companies did not choose their battles properly. I would suggest that any company that is getting into this area of technology should concentrate on the areas that CISCO can’t, the smaller markets, it’s just not profitable for a company the size of CISCO to focus resources in that area. You cannot walk into the room and slap the biggest and meanest person in there, that only works in the movies for Burt Reynolds, in the real world you get squashed… “choose your battles well grasshoppa…”