What’s the message about Cloud Contracts since AWS declined to testify to the Senate about SolarWinds?

03 March 2021 Internet, IT & e-Discovery Blog Blog
Authors: Peter Vogel

Darkreading.com reported that “Conspicuously missing from the panel was Amazon Web Services (AWS), which declined the Senate's invitation to testify -- a snub that appeared to rile several senators on the committee. Sen. Richard Burr, R-N.C., pointed out that the attack was waged inside the US, and some secondary command-and-control nodes were hosted on AWS's infrastructure.”  The February 23, 2021 article entitled “SolarWinds Attackers Lurked for 'Several Months' in FireEye's Network” included these comments:

Top execs from FireEye, SolarWinds, Microsoft, and CrowdStrike testified before the US Senate Intelligence Committee today on the aftermath - and ongoing investigations - into the epic attacks.

The attackers who infiltrated SolarWinds Orion's software build and updates had spent "several months" embedded in FireEye's network before the security firm spotted them, Kevin Mandia, CEO of FireEye, told a congressional committee today.

"The attacker wasn't alive every single day" on our network, Mandia told the US Senate Intelligence Committee in response to a question about the attack time frame on FireEye's network.

"They were on our systems for three hours on one day, a week would go by, and a couple of hours another day. We weren't a full-time job for [them] ... because they had broken into another 60-plus, if not 100, organizations.

There were several days of activity before we detected them."

Maybe you should stop and read your Cloud Contracts to see what responsibility the Cloud provider owes you!

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.

Authors

Insights