A NetWorld+Interop treat for you
|
|
|||
|
|
Many of you already plan to attend the NetWorld+Interop conference next month in Las Vegas, but if you're on the fence about going I hope this convinces you to head out to sun city.
With the help of the show's organizers, I've pulled together a special plenary session on security - a topic that has rocketed to the top of your list of "things that keep me up at night."
We've got an all-star group of speakers who will explore the most dangerous threats to our networks, the new tools that will help us deal with those threats and the issues that will shape security.
The session is called "Cyberland defense: Rethinking network security for a dangerous world." It will be held at 5 p.m. on May 8.
Joining me on stage will be:
Our focus will be on defining where our public and private networks are most vulnerable, and exploring what corporations and government agencies need to do to shore up these critical infrastructure resources. We'll also discuss some innovative technologies that could - maybe - finally help us get ahead of the thugs, crooks, nuts and others who want to disrupt our e-business and personal communications.
This session builds upon the special Webcast we conducted in March, featuring Howard Schmidt, the government's top infrastructure protection guru. You can view that Webcast by clicking here.
I could use your help to make this N+I session a success. What questions do you want me to ask these experts? Which issues are most pressing for you? Please drop me an e-mail with your ideas and thoughts. I'll try to ensure that they get answered.
Thanks, and I hope to see you there.
- John Gallant
Editorial director
RELATED LINKS
Error 404--Not Found |
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:10.4.5 404 Not FoundThe server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent. If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address. |

