Filed in archive
risk
by leon on January 25, 2008
Where do security leaks and IT disasters come from? Look no further than the IT department.
According to a recent study by London-based security company Orthus, IT departments are responsible for 30 per cent of all data leaks. Four reasons for the disconnect between what the IT departments are trying to achieve and the problem itself are identified by Forbes: no-one's monitoring the IT department, the repercussions of security breaches are unclear, IT personnel can be a bit too cavalier with the information they have and security issues are more complex and ever-changing.
So how to avoid an IT disaster? Australian law firm Minter Ellison have put together a tongue-in-cheek guide to how to create them. Avoid structure, don't plan, keep things rigid and don't communicate are a good start.
Permalink: How to plan an IT disaster
Trackback: http://publish.creative-weblogging.com/publish/mt-tb.pl/111763
Addthis
Ask
Blinklist
del.icio.us
Digg
Fark
Facebook
Google
Lycos
Ma.gnolia
Mr Wong
Netscape
Netvousz
Newsvine
Reddit
StumbleUpon
Slashdot
Tailrank
Technorati
Wink
Yahoo
Vote for How to plan an IT disaster:
|
Rating: 9.00 out of 1 vote(s) cast.
|
Subscribe
Use the search to look for other interesting posts
| RSS |  See all blog subscribe options |
 What is RSS? | |
| Yahoo! |
|
| Addthis |
|
| Bloglines |
|
| Newsletter | |
| Follow us on Twitter! |
