If you haven’t determined how server virtualization changes your audit plans, you better get moving. I’m not just talking about a virtualization audit (more on that later), but the audits that you typically do every year or on a multi-year cycle.
For example, if every year you do an audit on all networks, servers, applications, and databases that host your key financial reporting or PHI systems, you’re looking at policies and procedures, configuration management, security (including patching), user access, logging, and so on. But do you first consider whether those assets run on virtualized servers?
Here’s my take on the issues that I found with the following quote from SC Magazine (for more info, see Quote of the Weak (Securing Virtual Servers):
We don’t treat the virtualization servers any different than the physical servers when it comes to security. We treat them the same. Security is security.
I love to “steal” content and blog post ideas from others (usually AuditMonkey), but this time, I slim-fingered from Mister Reiner (check out his computer security and hacking blog at misterreiner.wordpress.com).
All I really stole were the ideas inspired by a comment that I left on his post entitled, Your friends and relatives can go home and jack up their own computer. Reiner wrote that allowing others on your computer might result in an infected PC if your friends and relatives do stupid things like surf porn or open email attachments. To avoid these issues, he suggested you do the following:
Matasano Security has released an upgrade to Flint, a FREE web application that examines firewall configurations. “Flint examines firewalls, quickly computes the effect of all the configuration rules, and then spots problems.”
According to Matasano, once you upload a firewall configuration, Flint:
Filed under Free, Security
Filed under Audit, Security