|go to week of Apr 1, 2012||1||2||3||4||5||6||7|
|go to week of Apr 8, 2012||8||9||10||11||12||13||14|
|go to week of Apr 15, 2012||15||16||17||18||19||20||21|
|go to week of Apr 22, 2012||22||23||24||25||26||27||28|
|go to week of Apr 29, 2012||29||30||1||2||3||4||5|
Compartmentalization of operational roles can be your worst enemy when it comes to protecting critical infrastructure. Having done diagnostics for several multimillion-dollar credit card data thefts, Jim will discuss some areas that weren't discovered as risks until it was too late. Most of the losses were because of lax policies and lack of sharing of information between operational units within a business. Simple policy changes can mitigate these risks, though it's been surprising to see how many businesses have these common problems.
Jim Porell is an IBM Distinguished Engineer and Deputy CTO for Federal Sales. In this role, he consults with and for U.S. government agencies to assist them in removing costs, reducing risk, and improving security and resilience, while satisfying new business proposals. Most recently, he directed the Business Development activities for the mainframe. Before that, he was Chief Architect for the System z Software Brand and the chairperson of the System z Software Design council, which includes all IBM mainframe operating systems and middleware and looks at synergy across servers and the evolution of each of IBM's server platforms and operating systems. Jim has been a security consultant to customers and the U.S. government for over ten years and has co-authored several books on security.
Jim has been with IBM for 32 years in a variety of management and technical positions across the test, development, and brand organizations in the Hudson Valley region of New York and now in the District of Columbia.