Tech & Sourcing @ Morgan Lewis

When we represent customers in outsourcing and managed services transactions, we spend a significant amount of time drafting the exhibits for transition, which is typically a major project in and of itself. In order to help clients think about the major components of transition, we often provide the following checklist of common workstreams to facilitate our discussion.

In a recent Law360 article, Morgan Lewis lawyers Gregory Parks, Kristin Hadgis, and Terese Schireson discussed the recently passed bill in Nevada – Nevada Senate Bill 220 (SB 220) – that will require defined “operators” of websites or online services that are used for commercial purposes and collect personal data of Nevada consumers to comply with a consumer’s request not to sell personal information. SB 220 will be the first law of this scope in the United States that provides consumers with opt-out rights with respect to the sale of their data.

As a follow-up to our recent post on third-party contract due diligence in outsourcing deals, this post focuses on how customers in outsourcing deals handle the disposition of legacy third-party contracts—one of the thorniest and most work-intensive work streams—once diligence has concluded.

The National Institute of Standards and Technology (NIST) recently circulated a draft white paper discussing recommended security practices to be adopted throughout the various phases of software development.

Open source programs are becoming a best practice in the technology, telecom/media, and financial services industries.

Complexity in sourcing transactions relates to the interdependence between the parties executing a program.

Even with the standard independent contractor provision in a Master Services Agreement, when employees of the contractor work at a client's site, there can be a heightened risk for joint employment liability, especially where such employees were hired by the contractor as part of an outsourcing arrangement.