There are a lot of sample information security policies floating around the Internet. If you know which policies...
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
you need, you can even purchase policy templates if you're willing to spend the money. So, what does it mean and what does it take to have a practical set of storage security policies that can work for you in the real world?
For starters, you need to perform a formal risk analysis on your storage systems. This can be done internally or part of a larger information risk assessment performed by an outside expert. If you take this project on yourself, be sure to lean on existing methodologies instead of re-inventing the wheel. The bottom line is that you've got to know which risks are present in your storage systems and which ones would have the greatest impact and likelihood of occurrence before you can implement the appropriate policies and supporting controls.
In order to stay organized and keep things simple, you'll need to have a standard security policy template. This will make policy creation and maintenance so much simpler in the long-term than simply bundling everything into one large and unorganized document. The security template located here works well for all security policies.
Now it's time to create your actual policies. Remember -- create policies based on risks discovered and business needs. However, the following policies should be on your radar as they all relate to storage security in one way or another:
- Access controls -- admin rights, file/share permissions, cryptographic controls, zoning configurations, etc.
- Asset management -- system/data inventory, ownership, acceptable use, etc.
- Authentication controls -- applications, operating systems, databases, storage, etc.
- Business associates -- external contractors, offsite storage companies, contract provisions, etc.
- Business continuity -- disaster recovery and/or business continuity plan requirements
- Change management -- why, when, who, testing requirements, backout procedures, etc.
- Data backup -- what, when, methods used, etc.
- Data retention -- what, why, how long, etc.
- Information classification -- public, internal, confidential, labeling requirements, etc.
- Physical security -- building, data center, servers, storage appliances, etc.
- Removal of property -- servers, storage appliances, drives, tapes, etc.
- Security testing and audits -- what, how, when, who will perform testing, etc.
- Separation of duties -- users, system administrators, security auditors, etc.
- System maintenance -- patching, system purging, cleanups, etc.
- System monitoring and incident response -- real-time monitoring, audit logs, incident response plan requirements, etc.
- User authorization -- granting access -- who, what, when, how long, etc.
Once your policies are documented and implemented, don't let all of your diligent efforts be in vain. Work with management, and ideally an organization-wide security or IT governance committee, to make sure these policies are approved, well-accepted, properly maintained and, most importantly, actually enforced.
For more information:
About the author: Kevin Beaver is an independent information security consultant, author and speaker with Atlanta-based Principle Logic, LLC. He has more than 18 years of experience in IT and specializes in performing information security assessments. Kevin has written five books including Hacking For Dummies (Wiley), Hacking Wireless Networks For Dummies , and The Practical Guide to HIPAA Privacy and Security Compliance (Auerbach). He can be reached at email@example.com.