SaaS Cyber Risk is significant since about 80% of businesses use SaaS!

30 November 2021 Internet, IT & e-Discovery Blog Blog
Authors: Peter Vogel reported that “Software-as-a-Service (SaaS) Infrastructure…may represent 70% to 80% or more of a company's IT these days. Between Microsoft 365, Google Workspace, Salesforce, AWS/Azure, and even software development tools, most of the digital crown jewels of companies today might exist on someone else's infrastructure.”  The November 24, 2021 report entitled “When Will Security Frameworks Catch Up With the New Cybersecurity Normal?” included these comments about SaaS how “…the pandemic has also accelerated the disparity between large cybersecurity frameworks like ISO 27001 and the NIST Cybersecurity Framework”:

…. and the reality of most modern organizations, even ones that haven't gone 100% virtual.

This has been happening for years, but as the gaps widen between the security standards we have to follow and the actual security challenges on the ground, the frameworks are going to have to become more agile or risk becoming standards that cost a lot of money to comply with but have little to no effect on actual security.

Current frameworks either don't even mention SaaS or just lump it in with all third-party access. NIST finally released a Cloud Computing update in 2018 (SP 500-322), but it was already outdated when it came out.

Different approaches and controls are required for this type of infrastructure; encryption is often built in, but it may require special backup services or custom settings within the SaaS setup.

The built-in security features and tools are often impressive but offer limited customization. Frameworks need to adjust for this and update their guidance for these widely used platforms.

Given the use of SaaS this should give almost every business major concerns.

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.