Cloud security seems to baffle people, and it is not surprising why. It seems like no one is quite sure who is in charge of security in the cloud. Is it the company who owns the data stored there or is it the cloud provider? Or should it be some kind of combination of the two?
A combination of the data owner and the cloud provider may be the best option for security, but it has to be up to the data owner to make sure they are doing everything possible to make sure that information is kept secure. Yet, according to a Ponemon Institute study, 36 percent of businesses do not have a centralized cloud security policy in place and 45 percent do not enforce employees’ use of private clouds. This despite the increase of cloud adoption in the workspace.
So what do you need to know about developing a solid cloud security policy? According to Scott Hazdra, principal security consultant for Neohapsis, a security and risk management consulting company specializing in mobile and cloud security services, it is all about thinking of the right questions and understanding your cloud culture and what you are moving into the cloud.
Hazdra provided the following questions a company should ask when writing up a cloud security policy.
Click through for 10 questions a company should ask when writing up a cloud security policy.
What do we want to put in the cloud – data, applications or both? Based on this, you will be able to identify criteria to determine the best cloud provider and service required such as IaaS, PaaS or SaaS.
Do we have a good data classification policy and procedure and what type of data will we allow in the cloud – sensitive corporate data, protected data such as PII, SSNs or HIPAA related, day-to-day operational data? If you don’t have a good data classification policy, create that too so you aren’t inadvertently transmitting and storing data in a cloud that you don’t want there.
What existing policy does our company have that also applies to what we want to do in the cloud?
What have others in our industry done and what can we borrow? Calling up a peer who’s already ventured into the cloud and has experience with the good, the bad and the unexpected can really help you craft your policy. Checking out what a standards body, like ISO, NIST or the CSA, has created is also a great idea for discovering policy areas you may not have considered.
Who within our organization is allowed to enter into agreements with cloud providers? Who has authority to negotiate SLAs? Who can set up an application in or move data to the cloud and with whom should it be approved beforehand?
Where can my data or application be physically located? Where your data lives and where it could be moved to have legal and privacy implications.
What is our exit strategy and policy for removing data or applications from this cloud provider? Having a clear exit strategy before you start prevents you from potentially large operational costs or downtime later.
If we choose to put sensitive or protected data in the cloud, how well does the cloud provider’s security policies and procedures align with our organizations? Ensuring your cloud provider’s security program maturity is as advanced or more advanced than yours is a good sign.
For applications in the cloud, who within our organization is allowed to modify settings on the cloud that affect performance? Define who, when and under what circumstances changes can be made.
How should we manage administrative privileges to the cloud provider? For example, do you allow application developers to make changes to security settings in the cloud to improve performance?