Bitdefender surveyed 250 US IT decision makers who concluded that about “34 percent of companies were breached in the past 12 months, while 74 percent of IT decision makers don’t know how the company was breached” and “Two-thirds of companies would pay an average of $124k to avoid public shaming scandals after a breach. Some 14 percent would pay more than $500k.” The Bitdefender report entitled “Virtualization makes CIOs role key (A survey on US IT decision makers)” included this recommendation about #3 “Be mindful of geographical jurisdiction and data handling storing laws”:
When choosing a cloud service provider, it’s vital that the datacenter physically reside in a region or country in which data handling and storing legislation is favorable to your company’s business interests. Any datacenter, regardless of the data it stores, falls under the data privacy and protection laws of the country it’s built in. Consequently, it’s vital that any company that plans to use a cloud service provider that has datacenters outsider its borders read and abide by the local data protection laws. Otherwise, the organization may risk judicial repercussions that could involve both financial and reputational damages.
Here are all 10 recommendations:
- Define the criteria on which you store on-premise or in-the-cloud data. Perform risk management.
- Keep your cloud private.
- Be mindful of geographical jurisdiction and data handling storing laws
- Perform due diligence on the cloud service provider and stipulate damages.
- Encrypt data both locally and in transit
- Backup cloud data
- Use secure and multiple authentication mechanisms
- Limited number of employees that can access sensitive data
- Prevent DDoS attacks
- Create, define and implement fast security response procedures
Good advice from the IT leaders, but how many companies will follow this advice?
This blog is made available by Foley & Lardner LLP (“Foley” or “the Firm”) for informational purposes only. It is not meant to convey the Firm’s legal position on behalf of any client, nor is it intended to convey specific legal advice. Any opinions expressed in this article do not necessarily reflect the views of Foley & Lardner LLP, its partners, or its clients. Accordingly, do not act upon this information without seeking counsel from a licensed attorney.
This blog is not intended to create, and receipt of it does not constitute, an attorney-client relationship. Communicating with Foley through this website by email, blog post, or otherwise, does not create an attorney-client relationship for any legal matter. Therefore, any communication or material you transmit to Foley through this blog, whether by email, blog post or any other manner, will not be treated as confidential or proprietary.
The information on this blog is published “AS IS” and is not guaranteed to be complete, accurate, and or up-to-date. Foley makes no representations or warranties of any kind, express or implied, as to the operation or content of the site. Foley expressly disclaims all other guarantees, warranties, conditions and representations of any kind, either express or implied, whether arising under any statute, law, commercial use or otherwise, including implied warranties of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Foley or any of its partners, officers, employees, agents or affiliates be liable, directly or indirectly, under any theory of law (contract, tort, negligence or otherwise), to you or anyone else, for any claims, losses or damages, direct, indirect special, incidental, punitive or consequential, resulting from or occasioned by the creation, use of or reliance on this site (including information and other content) or any third party websites or the information, resources or material accessed through any such websites.
In some jurisdictions, the contents of this blog may be considered Attorney Advertising. If applicable, please note that prior results do not guarantee a similar outcome. Photographs are for dramatization purposes only and may include models. Likenesses do not necessarily imply current client, partnership or employee status.