Commentary

George Hulme
 

Black Hat 2008, First Day Sessions

I've been in Las Vegas for a couple of days now, meeting with some old friends in the information security community, and making a few new ones. This year, the annual Black Hat confab will be serving interesting talks on the security implications of virtualization, social networks, and Web 2.0. Should make a good conference that will highlight some of the big security concerns going forward.

I've been in Las Vegas for a couple of days now, meeting with some old friends in the information security community, and making a few new ones. This year, the annual Black Hat confab will be serving interesting talks on the security implications of virtualization, social networks, and Web 2.0. Should make a good conference that will highlight some of the big security concerns going forward.On Wednesday, I'll be attending the keynote, from the Application Security track, of Ian O. Angell, professor of information systems, London School of Economics, called Complexity in Computer Security: a Risky Business. While the name of the presentation doesn't pack much punch, this description pulled me in: The mixture of computers and human activity systems spawns bureaucracy and systemic risk, which can throw up singularities that defy any positivist/statistical analysis. Should be interesting, I'm always up for an economist's take on information security.

Next up, we're jumping over to the networking track for a ride with The Four Horsemen of the Virtualization Security Apocalypse, presented by Christopher Hoff, chief security architect at Unisys. This network presentation will focus on both securing virtualization as well as virtualizing security; from virtualization-enabled chipsets to the hypervisor to the VMs, we'll explore the real issues that exist today as well as those that are coming that aren't being discussed or planned for. There's no doubt virtualizing security, as well as securing virtualized environments, are two topics just getting warmed up.


More Security Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Final session I'll be attending Wednesday will be Xploiting Google Gadgets: Gmalware and Beyond. Couldn't resist this description: This talk will analyze the security history of Google Gadgets and demonstrate ways to exploit Gadgets for nefarious purposes. I guess social-engineering someone to install a gadget so you can scan all of the systems on their subnet will supplement malware-laced USB storage devices used for the same purposes.

I'll be posting my observations from the conference throughout the week. Stay tuned.

Or, you can follow my micro blogs from the event on Twitter.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links