ARTICLE / CLIENT ALERT
CMA Blocks Microsoft’s Acquisition of Activision Blizzard; ‘Game Over’ for Behavioral Remedies?
May 8, 2023
Read time: 10 min
On April 26, 2023, the Competition and Markets Authority (CMA) blocked what would otherwise have been the largest deal in the gaming industry to date. The decision highlights several important trends, such as:
- In dynamic markets, regulators are focusing in on whether a deal harms or could harm future competition (i.e., innovation based on predications raising significant uncertainties). The CMA speculated that the deal would “alter the future of the fast-growing cloud gaming market” and preferred to maintain the status quo with the block.
- Regulators are focusing more and more on non-horizontal relationships and supply chain is-sues, particularly if one party is vertically integrated. Whereas in the past, concerns could often be remedied via behavioral commitments, more and more deals with a vertical component are now being outright prohibited.
- While the industry expects the European Commission (Commission) to accept the behavioral remedy (license package) offered by Microsoft, this case shows once again that the CMA and the Commission can reach different conclusions when reviewing the same trans-action.
BACKGROUND
Gaming is the United Kingdom’s largest entertainment sector in terms of revenue. In early 2022, Microsoft announced its plans to acquire Activision Blizzard (Activision) for nearly $69 billion, making it the biggest deal ever in the gaming industry.
While Microsoft is best known for its Windows operating system (OS), it is also active in gaming through its Xbox console and 24 game development studios, several of which it acquired in recent years. Through the Xbox console, Microsoft competes most closely with Sony’s PlayStation and to a lesser degree with Nintendo’s Switch.
Importantly, with Xbox Cloud Gaming and Azure, Microsoft also has a global cloud computing infrastructure.
Cloud gaming is a relatively new alternative to consoles and PCs. Whereas the more traditional methods of gaming require users to download and run games locally on their devices, cloud gaming services dispense with the need for powerful (and often expensive) hardware. These games run on remote servers and can be streamed directly to any device with a stable high-speed internet connection and a display (e.g., a smart TV).
Activision, on the other hand, has no cloud gaming infrastructure. Rather, it is a leading video games publisher whose most popular titles include Call of Duty, World of Warcraft and Candy Crush. These games run on PCs and consoles, as well as on mobile devices.
Therefore, while there are actual horizontal overlaps between Activision and Microsoft (with both developing and selling games), the CMA investigation focused on the vertical effects of the proposed transaction in console gaming and in cloud gaming services.
THE CMA’S DECISION
Console Gaming
The first theory of harm considered a scenario where Microsoft would make the game Call of Duty either exclusive to Xbox or only available to its rival PlayStation on worse terms. The concerns that the CMA expressed in its provisional findings have in the meantime been dismissed after revisiting the evidence submitted by Microsoft and Activision. The CMA therefore held, in unanticipated addendum provisional findings (nearly two months after the provisional findings were issued), that Microsoft had no incentive to implement a (partial) foreclosure strategy by either offering PlayStation games, in particular Call of Duty, with lesser quality, at a higher price or not at all (i.e., making Activision’s games exclusive to Microsoft).
As a result, the CMA concluded that the deal would not result in a substantial lessening of competition (SLC) in console gaming services in the United Kingdom.
Cloud Gaming
The second theory of harm considered the ability, incentive and potential impact of Microsoft harming its cloud gaming rivals by making Activision games exclusive to its own cloud gaming offering.
Against the backdrop of robust growth projections due to lower hardware requirements and thereby lower costs, the CMA found cloud gaming to be “transformative” and an “important disruptive force” in the gaming industry, with the potential to replace expensive consoles and gaming PCs altogether for at least some users.
Microsoft was deemed to hold a strong position not only in the gaming industry more generally (with its “gaming ecosystem,” including the Xbox console, its Game Pass and development studios, as well as the Windows OS for which the majority of PC games are designed), but also in cloud gaming services more specifically (with 60% to 70% market share). The CMA inferred from this that Microsoft could stream games via Xbox Cloud Gaming and Azure from Windows servers without having to pay its Windows licensing fee or adapt games designed for Windows to an alternative OS—and without having to pay a third-party cloud platform fee. Microsoft would therefore have the ability to make games exclusive to its cloud gaming offering and thereby slow the development of the fast-paced cloud gaming market.
The CMA also found that Microsoft would have an incentive to make Activision’s games, which were deemed to be important for the growing cloud gaming market, exclusive to Xbox Cloud Gaming and Azure. The CMA explained that the cloud gaming market was characterized by elements of direct and/or indirect network effects and that Microsoft could try to gain market power by offering exclusive games on its cloud gaming service. Importantly, the CMA considered that without the deal, Activision would make its games available to all cloud gaming service providers on its own terms.
The fact that Microsoft had signed agreements with cloud gaming providers NVIDIA, Boosteroid, Ubitus and Nware (the latter post-prohibition) to make games available on their platforms could not resolve the CMA’s concerns regarding the effects of the merger. The CMA explicitly relied on paragraph 7.15 of its Merger Assessment Guidelines and criticized that the agreements applied only to a few providers and that there was “material uncertainty” around their scope, terms and enforceability. In the CMA’s view, the market is characterized by few emerging rivals (none of which are as well-positioned as Microsoft) and significant barriers to entry and expansion. The CMA found that, absent the merger, Activision’s games were likely to become available on and would be a particularly important input to cloud gaming services and any alternatives were likely not sufficient enough to offset the loss incurred to cloud gaming rivals by the foreclosure of Activision content.
For similar reasons, the CMA did not accept the behavioral remedies proposed by Microsoft to allay the concerns. Microsoft committed to licensing Activision games royalty-free to certain cloud gaming providers for a period of 10 years. Moreover, Microsoft would have given any consumer who acquired an Activision game from it online the right to stream that game in the cloud gaming services that were covered by the remedy. Importantly, Microsoft also offered to appoint a monitoring trustee to monitor and ensure compliance with the remedy, as well as a fast-track dispute resolution mechanism.
The CMA saw two significant limitations with the proposed remedy. First, it criticized that gamers would have to purchase a game first in order to stream it on certain cloud gaming services and that the latter would thus be precluded from accessing Activision’s games through other strategies, such as multigame subscription services. Second, the CMA pointed out that the remedy did not include PC OSs other than Windows. It argued that since cloud gaming services wishing to stream Activision’s games would have to be compatible with the Windows OS version of those games, non-Windows-based cloud gaming services would be put at a disadvantage. The CMA also found the duration of 10 years to be insufficient and expressed doubts as to the feasibility of monitoring and enforcing the remedy.
For the above-mentioned reasons, the CMA expected the merger to result in an SLC in cloud gaming services in the United Kingdom because of vertical effects in the form of input foreclosure, which would ultimately harm current and future gamers.
COMMENTARY
This decision underscores the CMA’s position—since Brexit—as a global antitrust authority reviewing the largest deals alongside the Commission and US authorities.
Microsoft has already said that it will appeal the CMA’s decision before the Commission Appeals Tribunal (CAT). The appeal itself will not focus on the substance (i.e., Microsoft will apply for judicial review of the CMA’s decision). If Microsoft is successful in arguing that the CMA acted illegally, irrationally or improperly, the CAT could require the CMA to reassess its approach in concluding on the theory of harm concerning cloud gaming services.
Several countries have unconditionally cleared the deal, including Japan, South Africa and—only one day after the CMA’s prohibition—Ukraine. Alongside the appeal before the CAT, Microsoft still awaits regulatory approval in other jurisdictions, most notably the European Union (where the Commission has until May 22, 2023, to decide on the remedies) and the United States (where a private plaintiffs’ challenge is to be heard on May 12, 2023, and an administrative trial at the Federal Trade Commission’s internal court is set to start August 2, 2023). If the deal does not receive clearance from all authorities by July 18, 2023, Microsoft will potentially have to pay a break fee of $3 billion to Activision, unless the parties agree to extend the long stop date in the meantime.
Although the CMA has blocked the deal on the grounds of what looks like a well-established foreclosure theory of harm (cf. ICE/Trayport), its decision is also the expression of more novel and overall, rather vague concerns over the strengthening of a digital ecosystem. More importantly, however, the case reveals a worrisome stance on behavioral remedies, which have traditionally played an important role in removing vertical concerns.
In its press release, the CMA voiced its general skepticism towards behavioral remedies, which in its words would necessitate an “ongoing regulation of the sector, replacing market forces in a growing and dynamic market with mandated regulatory obligations ultimately overseen, and enforced by, the CMA – in this case at a global level.” The CMA has not accepted any behavioral remedies in the past three years during in-depth investigations. It famously rejected behavioral remedies in its review of the acquisitions of Farelogix by Sabre and Giphy by Meta (formerly Facebook) and instead prohibited these deals. By blocking Microsoft’s proposed takeover of Activision, the CMA reinforces this trend.
The Commission thus far seems to have taken a different approach. In its Google/Fitbit clearance, the Commission demonstrated its willingness to accept more complex behavioral remedies, including the possibility of an extension of the initial duration and the appointment of a monitoring trustee. In a similar vein, it has accepted behavioral access remedies to remove its concerns over vertical input foreclosure in Meta/Kustomer, whereas the CMA cleared that same deal unconditionally. It remains to be seen whether the two agencies’ approaches will continue to diverge in the future.

New York State Enacts Filing Requirement for Physician Practice Management and Physician Practice Transactions
ARTICLE / CLIENT ALERT
New York State Enacts Filing Requirement for Physician Practice Management and Physician Practice Transactions
May 3, 2023
Read time: 7 min
On May 3, 2023, New York State enacted legislation that will require physician practice management services organizations (MSOs) and physician practices to submit a comprehensive filing to the New York State Department of Health (DOH) at least 30 days before closing certain merger, acquisition and affiliation transactions. The legislation does not require MSOs and physician practices to obtain DOH’s approval before closing a transaction, but the filing may extend the timeline to close a transaction, require additional resources to prepare the materials for submission, and bring greater regulatory awareness to the transaction. Significantly, DOH will publicly post a summary of each transaction, resulting in disclosure of transactional information previously unavailable to the public.
The notice requirement will become effective in 90 days (August 1, 2023), giving DOH little time to operationalize the application process and healthcare entities little time to prepare.
The Filing Requirement, Generally
The legislation will require healthcare entities to submit to DOH written notice, with supporting documentation, at least 30 days prior to closing a material transaction. Under the legislation, a healthcare entity includes but is not limited to the following:
- A physician practice, group, or MSO or similar entity providing all or substantially all of the administrative or management services under contract with one or more physician practices.
- A provider-sponsored organization.
- A health insurance plan.
- Any other kind of healthcare facility, organization or plan providing healthcare services in New York State.
The following entities are excluded from the definition of a healthcare entity and do not need to submit filings for transactions with a non-healthcare entity:
- An insurer authorized to do business in New York
- A pharmacy benefit manager (PBM) registered or licensed in New York State.
Under the legislation, a material transaction includes any of the following, occurring during a single transaction or in a series of related transactions within a rolling 12-month period:
- A merger with a healthcare entity
- An acquisition of one or more healthcare entities, including but not limited to the assignment, sale or other conveyance of assets, voting securities, membership or partnership interest or the transfer of control (direct or indirect ownership, control or power to vote 10% or more of the voting securities of the healthcare entity)
- An affiliation agreement or contract formed between a healthcare entity and another person
- The formation of a partnership, joint venture, accountable care organization (ACO), parent organization or MSO for the purpose of administering contracts with health plans, third-party administrators, PBMs or healthcare providers.
The following transactions are excluded from the definition of a material transaction:
- Transactions that are already subject to review under the following articles of the New York Public Health Law:
- Article 28 (Hospitals, including Diagnostic and Treatment Centers/Ambulatory Surgery Centers)
- Article 30 (Emergency Medical Services)
- Article 36 (Home Care Services)
- Article 40 (Hospices)
- Article 44 (Health Maintenance Organizations)
- Article 46 (Continuing Care Retirement Communities)
- Article 46-A (Fee-for-Service Continuing Care Retirement Communities Demonstration Program)
- Article 46-B (Assisted Living)
- Transactions or series of related transactions that result in a healthcare entity increasing its total gross in-state revenues by less than $25 million
- Clinical affiliations of healthcare entities formed to collaborate on clinical trials or graduate medical education programs.
The filing requirement will become effective 90 days following enactment of the legislation. Failure to submit the notice will result in civil penalties of up to $5,000 per day.
The Required Filings
At least 30 days prior to closing a material transaction, a healthcare entity must submit the following to DOH:
- The names of the parties to the material transaction and their current addresses
- Copies of any definitive agreements governing the terms of the material transaction, including pre- and post-closing conditions
- Identification of all locations where healthcare services are currently provided by each party and the revenue generated in the state from such locations
- Any plans to reduce or eliminate services and/or participation in specific plan networks
- The closing date of the proposed material transaction
- A brief description of the nature and purpose of the proposed material transaction, including the following:
- The material transaction’s anticipated impact on cost, quality, access, health equity and competition in the affected markets, which may be supported by data and a formal market impact analysis
- Any commitments by the healthcare entity to address anticipated impacts.
The supporting documentation submitted to DOH will not be subject to disclosure under the New York Freedom of Information Law (FOIL). The legislation does not protect the information submitted in the notice from public disclosure under FOIL, however.
The Review
Immediately upon receipt of the filing, DOH will share the filing with the antitrust, healthcare and charities bureaus of the New York Attorney General’s office. DOH will post the following on its website:
- A summary of the proposed transaction
- An explanation of the groups or individuals likely to be impacted by the transaction
- Information about services currently provided by the healthcare entity, commitments by the healthcare entity to continue such services, and any services that will be reduced or eliminated
- Details about how to submit comments.
Analysis and Takeaways
In a material deviation from Governor Hochul’s initial proposal, the enacted legislation does not require healthcare entities to obtain DOH approval prior to consummating a material transaction. It is possible that DOH or another New York governmental agency could try to intervene if it believed the transaction would violate antitrust or other laws. Since the enacted legislation does not create a specific pathway for this type of action, however, such intervention would need to be based on separate legal authority.
The legislation likely will have several material effects on New York physician practice management and physician practice transactions. A few key considerations include the following:
- Resource and Timing Considerations. The 30-day pre-closing notice will create an additional filing burden and timing consideration for physician practices and MSOs engaging in material transactions in New York State. Healthcare entities will now need to develop analyses relating to the transaction’s anticipated impact on cost, quality, access, health equity and competition in the impacted markets. Some healthcare entities may choose to engage consultants to assist with these analyses.
- Transparency. The legislation will also result in the disclosure of historically confidential information to both state regulators and the public prior to consummation of a transaction. This disclosure will give competitors some level of insight into physician practice management growth strategy and may result in further regulatory scrutiny of transactions.
- DOH Guidance. The notice requirement becomes effective on August 1, 2023, so any healthcare entities involved in a transaction occurring on August 1, 2023, will be required to submit the filing by July 2, 2023. DOH will need to quickly release guidance for the application process to ensure that healthcare entities can complete the filing in a timely manner to close on August 1, 2023. DOH’s guidance may also address ambiguities in the text of the legislation, such as the following:
- What is meant by a “plan,” for purposes of explaining in the filing any intentions to reduce or eliminate participation in specific plan networks
- Whether a “brief description” of various transaction impacts will be acceptable, or whether more significant or expert analyses will be required
- De Minimis Exception. The exception for transactions resulting in a healthcare entity increasing its total gross in-state revenues by less than $25 million leaves room for interpretation. The legislation does not specify what type(s) of revenues should be included in the calculation (e.g., purchase price revenue, annual revenue) or how those revenues should be calculated. It is also unclear how the exception would apply to a sponsor-to-sponsor parent level transaction that does not result in any new physician practice revenue in New York.
Healthcare entities should monitor DOH guidance in the coming days, weeks and months, to understand how and when the filing requirement will be operationalized. Parties to transactions with anticipated closings after August 1, 2023, should begin preparing information and documentation as set forth in the legislation based on a reasonable legal interpretation for prompt submission once the application guidance is released.

Healthcare Regulatory Check-up | March 2023
ARTICLE / REPORT
Healthcare Regulatory Check-up | March 2023
May 2023
Read time: 2 min
This issue of McDermott’s Healthcare Regulatory Check-Up highlights significant regulatory activity for March 2023. We discuss several criminal and civil enforcement actions that involve Anti-Kickback Statute (AKS) and beneficiary inducement issues. We also highlight the recent Office of Inspector General (OIG) advisory opinions 23-03, as well as other notable developments, including OIG’s creation of a new FAQ process and revised CMS Self-Referral Disclosure Protocol forms.

Preparing for the End of the COVID-19 Emergency: High-Deductible Health Plans and Health Savings Accounts
ARTICLE / CLIENT ALERT
Preparing for the End of the COVID-19 Emergency: High-Deductible Health Plans and Health Savings Accounts
May 2, 2023
Read time: 4 min
Our April 3, 2023, webinar explored the impacts that the end of the PHE and NE will have on employee benefit plans and what actions employers and benefit plan sponsors should be taking to prepare. Watch the “How Employers Should Prepare for the End of the Covid-19 National and Public Health Emergencies” webinar recording to learn more.
The Biden administration originally announced its intent to end the COVID-19 National Emergency (NE) and the COVID-19 Public Health Emergency (PHE) on May 11, 2023 (read our prior client alert, “Preparing for the end of the COVID-19 emergency: Tri-agencies issue FAQs to assist plans and issuers,” for more information). Although the end date of the NE was subsequently advanced to April 10, 2023, by Congressional resolution, the US Departments of Labor, Health and Human Services, and the Treasury (the Departments) have given no indication that the change will affect employee benefits plans. Plan sponsors should continue to treat May 11 as the end of the NE until the Departments say otherwise.
During the COVID-19 pandemic, certain permissive practices were allowed by high-deductible health plans (HDHPs) and health savings accounts (HSAs). This article explores whether these benefit offerings can be continued at the end of the PHE and NE.
HDHPs AND HSAs
IRS Notice 2020-15 temporarily permits the coverage of COVID-19 testing with no cost-sharing for HDHPs. It provides that an HDHP will not fail to be an HDHP merely because the plan covers expenses related to COVID-19 testing and treatment prior to satisfying the applicable minimum deductible. This guidance was not directly tied to the NE or the PHE, meaning that it will eventually lapse. The eighth question/answer of the FAQs indicates that individuals covered by an HDHP who have purchased items related to COVID-19 testing or treatment prior to meeting the applicable minimum deductible can continue to contribute to an HSA until further guidance is issued. The Departments also assured plan sponsors that future changes will generally not require HDHPs to make mid-year changes for covered individuals to remain eligible to contribute to an HSA.
Thus, individuals covered by an HDHP may continue to contribute to an HSA following the end of the PHE. COVID-19 vaccinations also continue to be considered preventive care under Section 223 of the Code for purposes of determining whether a health plan is an HDHP.
ACTION ITEMS
Once the PHE and NE have ended, employers can continue their practice of allowing individuals covered by an HDHP plan to contribute to an HSA. Employers need to also consider whether they will continue to cover COVID-19 tests as required by a doctor or OTC without cost-sharing. Employers should strategize what effect this might have on the HDHP. This might also require an amendment to the health plan or its summary plan description. Employers should continue to watch for further guidance from the Departments on this issue.

Federal Government to Wind Down Vaccination Mandates
ARTICLE / CLIENT ALERT
Federal Government to Wind Down Vaccination Mandates
May 2, 2023
Read time: 3 min
On May 1, 2023, the White House announced that the federal government will wind down certain of its remaining COVID-19 vaccination mandates (including those for federal workers, contractors and international air travelers) effective May 11, 2023, which is the end of the COVID-19 public health emergency (PHE). The US Department of Health and Human Services (HHS) will also “start the process” to end the vaccination requirements for Centers for Medicare & Medicaid Services (CMS) certified healthcare facilities. Also on May 1, CMS issued a QSO Memo containing wide-reaching guidance pertaining to the end of the PHE, which indicated that further information regarding the end of the CMS COVID-19 vaccination mandate would be forthcoming after the PHE has expired. As the process and timeline for winding down the CMS vaccination mandate has not yet been released, and it is unclear how quickly it will take effect and how elimination of the mandate will impact the many CMS quality measures tied to COVID-19 vaccinations.
These announcements come on the heels of an updated Frequently Asked Questions (FAQs) that CMS released on April 27, 2023, on preparing for the end of the COVID-19 PHE. The FAQs include 25 questions and answers in four categories (general, Medicare, Medicaid and CHIP, and private insurance). They cover issues such as cost of and reimbursement for vaccines, testing and treatment, as well as more specific topics such as telehealth; reporting requirements for nursing homes, hospitals and critical access hospitals; and the end of Medicaid continuous enrollment. Although we are still reading through the details and comparing this document to previously released information, the FAQs do not appear to include any new information.
CMS continues to maintain and update the COVID-19 resource page, which includes fact sheets on various issues related to the end of the PHE. More FAQs and announcements are likely to be released as we get closer to May 11.
McDermott and McDermott+Consulting are monitoring for further developments and will send out an update as soon as more information is available.

DOJ’s Labor Market Prosecution Against Aerospace Employees Dismissed; Alleged Market Allocation Not Within Per Se Rule
ARTICLE / CLIENT ALERT
DOJ’s Labor Market Prosecution Against Aerospace Employees Dismissed; Alleged Market Allocation Not Within Per Se Rule
May 1, 2023
Read time: 6 min
On April 28, 2023, a US District Court for the District of Connecticut judge dismissed the US Department of Justice’s (DOJ) criminal non-solicitation case against six aerospace industry employees, acquitting all the defendants in U.S. v. Patel, et al. Importantly, the court held that the case, as a matter of law, “does not involve a market allocation under the per se rule.” In reaching this stinging decision, the trial court seized on many of the key arguments, themes and rulings that the defense made in the U.S. v. DaVita, Inc. and [a former senior executive] criminal non-solicitation trial from 2022. In that case, McDermott represented DaVita’s former senior executive, who was acquitted on all counts along with DaVita.
In 2021, DOJ indicted six aerospace industry employees, alleging that they engaged in a hub and spoke conspiracy between a manager at an aerospace firm and executives at five other engineering service providers to that firm. DOJ charged that the defendants allegedly agreed to refrain from hiring engineers and/or other skilled workers from each other relating to projects for an aerospace firm.
The timing of the court’s dismissal under Federal Rule of Criminal Procedure 29—at the conclusion of DOJ’s evidence and before the case reached the jury—is quite rare. Dismissing under Rule 29 requires a court, viewing the evidence in the light most favorable to the government, to determine the evidence that the defendant committed the crime alleged is nonexistent or so insignificant that no reasonable jury could find guilt beyond a reasonable doubt. It is a heavy burden for a defendant to successfully challenge the sufficiency of the evidence—and one that the Patel defendants were able to satisfy. DOJ cannot appeal this Rule 29 order.
In its ruling dismissing the case against the six defendants, the court cited as precedent several of the key arguments and rulings from the DaVita and its former senior executive criminal trial. For example, the Patel court highlighted that—citing DaVita and its former senior executive—workers were still able to switch between different engineering staffing companies and that hiring “among the relevant companies was commonplace throughout the alleged agreement.” In addition, the court found that the “alleged agreement itself had so many exceptions that it could not be said to meaningfully allocate the labor market of engineers.” Given this—and again relying on DaVita and its former senior executive—the court ruled that “no reasonable juror could conclude that there was a ‘cessation of “meaningful competition” in the allocated market.’”
The Patel court’s order dismissing the charges against the defendants was not the only significant ruling in the case. Just prior to trial, the court denied DOJ’s motion to prevent defendants from presenting evidence of the procompetitive justifications for their alleged conduct at trial. The court noted that such evidence was relevant to the defendants’ planned ancillarity defense, writing that “the procompetitive evidence at issue here is relevant because it relates to whether defendants joined the charged conspiracy, whether the conspiracy existed as alleged, and whether defendants had the requisite intent to join such a conspiracy.” This permitted the defendants to introduce evidence that any alleged restrictions were ancillary, or reasonably necessary, to achieving the legitimate and procompetitive purposes of a business collaboration; this is significant because if the restraint is ancillary, the alleged violation would not be per se unlawful but would be subject to the far more lenient rule of reason review. Importantly, the court’s proposed jury instructions demonstrated the importance of this planned defense: “Even if the government proves the three elements beyond a reasonable doubt, if the charged agreement is ancillary to a legitimate business collaboration you must find the defendants not guilty. The government bears the burden of proving the charged agreement is not ancillary.” Finally, the court also denied DOJ’s request to exclude evidence from three experts; this provided the defendants the opportunity to present evidence from experts relating to the lack of harm from the alleged conduct.
TAKEAWAYS
- The Patel decision marks DOJ’s fourth consecutive loss in its alleged labor market collusion trials against companies and individuals. Despite the losses, DOJ has trumpeted its success in its labor market prosecutions because judges have thus far declined to grant motions to dismiss (finding that the government had adequately pled its case) and allowed prosecutions to proceed on a per se or categorically illegal standard. This result is different, and DOJ will not be able to advance its prior assertions of success here. And that is because the court explicitly stated—after DOJ’s evidence had been presented—that the alleged market allocation conduct in the Patel matter did not fall under the per se rule. This reflects a rebuke of DOJ’s arguments in the labor market space and raises questions about the viability of its criminal labor market investigations and prosecutions, particularly as it relates to alleged non-solicitation agreements.
- Of note, the court’s pretrial ruling on ancillarity placed an additional evidentiary burden on DOJ. In other words, the court required DOJ to prove beyond a reasonable doubt that the alleged agreement was not subordinate and collateral to a separate, legitimate business collaboration, and that the alleged agreement was not reasonably necessary to achieving the legitimate and procompetitive purposes of the business collaboration. This additional burden of proof for the government is substantial and reflects a potential shift further away from the traditional per se standard in the labor market context.
- Both the April 28, 2023, dismissal and the pretrial ruling discussed above puts the Patel matter closely in line with ordinary rule of reason litigation (weighing the procompetitive benefits against the anticompetitive harm) that allows defendants to justify their conduct or assert that, on balance, it did not actually harm competition. This is in sharp contrast with DOJ’s assertions that criminal labor market prosecutions are subject to the traditional per se standard and that evidence relating to procompetitive benefits, lack of harm, or the definition of the market is irrelevant.
- Although the losses mount, DOJ has provided no signal that it intends to back off its aggressive posture in labor market investigations. To the contrary, recent statements from Assistant Attorney General Jonathan Kanter indicate that labor market investigations and prosecutions remain a top priority for prosecutors, and he referred to the prosecutions as “righteous.” In response to this approach, companies should remain vigilant and stay current with their antitrust compliance. Moreover, groups and individuals involved in hiring and compensation-related decisions may benefit from antitrust training relating to these issues, and they should ensure that direct and third-party employment agreements and arrangements are made with antitrust laws in mind.

The Legal Industry Reviews (05/2023)
ARTICLE
The Legal Industry Reviews (05/2023)
May 01, 2023
Read time: 2 min
Jana Grieb and Dr. Katharina Hoffmeister in the publication “The Legal Industry Reviews” on current developments and outlooks on EU regulations on medical devices and in vitro diagnostic medical devices.

CISA Self-Attestation Form Brings Clarity to Pending Secure Software Requirements for Government Contractors
ARTICLE / CLIENT ALERT
CISA Self-Attestation Form Brings Clarity to Pending Secure Software Requirements for Government Contractors
May 9, 2023
Read time: 11 min
Producers of software sold to the US government are facing an impending requirement to attest that their software is securely developed. More detail on this requirement emerged on April 27, 2023, when the Cybersecurity and Infrastructure Security Agency (CISA) published a draft Secure Software Self-Attestation Form and Request for Comment. The draft CISA form defines four objectives that would set the security baseline for all US government-procured software products and services, addressing open-source security, software bill of materials (SBOM), vulnerability management and development infrastructure security. Government contractors, including off-the-shelf (GOTS) software producers and upstream third-party developers, should act now to validate their secure development practices, in preparation to make and defend legally binding attestations.
Secure software development attestations have been a focus of the federal government’s cybersecurity strategy plan since President Biden’s May 2021 Executive Order (EO) on Improving the Nation’s Cybersecurity. In response to the EO, the National Institute of Standards and Technology (NIST) issued a software supply chain security guidance and updated the Secure Software Development Framework (SSDF).
However, until recently, there was little insight into how the expansive and ambitious SSDF would translate into concrete obligations for producers and developers of software sold to the government. CISA’s draft Self-Attestation Form (the CISA Form) defines the baseline software security standards for government procurement, distilling the SSDF to four “minimum secure software development requirements a software producer must meet, and attest to meeting.”
Although few, the requirements may still present a significant challenge to government contractors, software producers and upstream developers. The chosen requirements are not widely implemented and are some of the most challenging.
- Open-source security: Take reasonable steps to verify the security of third-party code, including open-source libraries.
- SBOM: Capture provenance information, so that a software bill of materials (SBOM) can be prepared at the request of an agency.
- Vulnerability management: Detect, track and remediate vulnerabilities using automation and enterprise processes, such as DevOps & governance risk and compliance (GRC).
- Infrastructure Security: Implement common enterprise security controls on all hardware, virtual infrastructure and SaaS used in development.
The CISA Form serves as a foundation for companies to meaningfully plan for implementation and assess compliance risk. Companies should act now to determine whether they can meet these secure software development attestation requirements, develop a roadmap or Plan of Action and Milestones (POA&M) for any gaps and prepare to create and archive the documentation necessary to support a challenge to an attestation.
Background
On December 17, 2020, US President-elect Joe Biden, addressing the cyberattacks against users of SolarWinds’ Orion software, announced that improving cybersecurity at every level of the government would be a top priority from the moment his administration takes office. On May 12, 2021, with much of the country still disrupted by the ransomware attack on Colonial Pipeline, President Biden issued Executive Order No. 14028 on Improving the Nation’s Cybersecurity. The executive order sought to improve the integrity and security of the software supply chain by establishing baseline security standards for the development of software sold to the government. Leveraging “the purchasing power of the Federal Government to drive the market to build security into all software from the ground up” represented a fundamental shift in the federal government’s cybersecurity strategy.
The executive order broadly directed NIST to solicit input (from the private sector, academia, government agencies and others) to identify or develop new standards, tools, best practices and other guidelines to enhance software supply chain security. In February 2022, after a series of workshops and other public engagements, NIST issued two guidance documents on software supply chain security. The SSDF was published as NIST SP 800-218 on February 3, 2022, and on February 4, 2022, NIST published its Software Supply Chain Security Guidance.
On September 14, 2022, the US Office of Management and Budget (OMB) issued memorandum M-22-18 directing each federal agency to comply with NIST’s SSDF and Software Supply Chain Security Guidance when “using third-party software on the agency’s information systems or otherwise affecting the agency’s information.” The memo directed agencies to obtain a self-attestation from the software producer before using the software and to obtain software artifacts and software bills of materials (SBoMs) as needed. To that end, OMB tasked CISA with establishing a standard self-attestation “common form,” as well as building a repository of software artifacts and SBoMs. OMB developed a waiver and extension process for agencies where software producers cannot meet attestation requirements, stating that any request must be submitted 30 days before any relevant deadline and be “accompanied by a plan for mitigating any potential risks.”
On January 11, 2023, the Government Services Administration (GSA) revelated its process for collecting, reviewing, retaining and monitoring software security attestations in a memorandum titled Ensuring Only Approved Software is Acquired and Used at GSA. GSA will begin collecting attestation letters as part of pre-award and post-award contract deliverables in mid-June 2023 for all government-procured software.
Software supply chain security has remained a priority for the Biden administration. On October 11, 2022, the White House stated that “requiring security features in all software purchased by the Federal Government” will improve security “for all Americans.” The March 2023 National Cybersecurity Strategy recommends legislation that would shift “liability for software products and services to promote secure development practices.” CISA Director Jen Easterly has stated frequently that software companies, rather than end users, should bear the risks and burdens that result from security vulnerabilities.
CISA Self-Attestation Form
The Form is intended to provide the federal government assurances that software used by agencies is securely developed. The April 27 draft Form for public comment identifies four secure software development requirements that producers must “attest that the software they produce was developed in conformity with.”
- Secure the development environment. Development workstations, test infrastructure, DevOps applications, code repositories and all other development infrastructure must be secured like any other sensitive asset, with risk assessments and standard technical controls such as multifactor authentication, encryption, endpoint protection and access monitoring.
- Establish a trusted source code supply chain. Take “reasonable steps to address the security of third-party components,” including open-source software (OSS) libraries and packages, with automation or comparable DevOps processes.
- Maintain provenance data. All first-party and third-party code incorporated into the software must be inventoried, with record of the origin, development, ownership, location and change history.
- Manage vulnerabilities. Automated processes and DevOps tools must be used to test for security vulnerabilities prior to release; discovered vulnerabilities must be addressed prior to release; and third parties must be able to vulnerabilities in released software must be received, reviewed and remediated.
Each of the four required attestations is “related” to one or more SSDF practices and tasks. They collectively address 17 of the 19 secure development practices defined in the SSDF and 31 of 43 tasks.
The CISA form contemplates that the CEO or designee must attest that their software was developed using practices that satisfy the identified secure software development requirements. They must also promise to “notify all impacted agencies if conformance to any element of this attestation is no longer valid.” The Form allows a software producer to attest to the security of software on a company-wide basis or for specific products, product lines or product versions.
As an alternative to the self-attestation, a producer may engage a certified FedRAMP third-party assessor organization (3PAO) to verify that software was developed in accordance with the relevant NIST guidance.
Producers that cannot attest to all required practices will be required to request an extension or waiver from the agency and develop a plan of actions and milestones (POA&M).
What Software Is Affected? When Will the Self-Attestation Be Required?
The CISA Form is intended to be the common form available to any agency for use with any software that has an attestation requirement under the September 2022 OMB memorandum. The Form can be used with any software, including firmware, operating systems, applications and application services (e.g., cloud-based software), as well as products containing software.
Attestations will be collected first for critical software, which OMB defines as “standalone, on-premise software that performs security-critical functions or poses similar significant potential for harm if compromised.” Examples given include operating systems, endpoint security, network control and protection, security logging and monitoring.
The OMB memorandum directs agencies to collect software attestation forms for critical software, seek an exception from OMB or discontinue use of the software by June 11, 2023. There will not be an approved self-attestation form by the date; however, producers of critical software currently in use by the federal government should be prepared to attest as soon as the Form is made final by CISA.
OMB has directed agencies to collect attestations “for all software subject to the requirements of [the September 2022] memorandum” by September 14, 2023. Although the aggressive timelines set by OMB have not been strictly followed to date, producers of any software used by the federal government should not delay in preparing to make secure software self-attestations.
The self-attestation requirements of the OMB memorandum do not apply to software that is freely acquired or software that is developed by an agency. Software that was developed prior to September 14, 2022, is not continuously developed and has not had a major upgrade since that date will remain exempt from the attestation requirements.
What Are the Risks of Noncompliance?
Software producers that fail to provide a required attestation of secure development or receive an exception face substantial risks to federal sales channel revenue, including for existing federal contracts. In its January 2023 memo, the GSA reminded contractors that when software fails to meet GSA IT Standards and becomes unapproved for use, “any future period of performance (e.g., option year, extension, task order) cannot be exercised or issued and the requirement must be re-procured.” It also directed new contracts for commercial software to require IT Standards Process approval before any performance period can begin. Pending rules by the Federal Acquisition Regulatory Council will make attestations a required part of contracts for commercial software procurement.
Software producers that make inaccurate attestations face significant legal risk. As noted in the CISA Form, “[w]illfully providing false or misleading information may constitute a violation of 18 U.S.C. § 1001, a criminal statute.” The Biden administration has repeatedly signaled its intention to use its authorities under the False Claims Act (FCA) to punish and deter misrepresentation of the cybersecurity of the goods and services sold to the federal government. The DOJ’s Civil Cyber-Fraud Initiative, announced on October 11, 2021, will utilize the FCA to pursue cybersecurity-related fraud by government contractors. Potential liability under the FCA is three times the amount of any fraud, which can be valued at 100% of contract revenue, or higher. The FCA includes a whistleblower provision that allows private parties to file a qui tam action and potentially share in the federal government’s civil recovery.
The indirect risks that could result from inaccurate attestations are numerous. For example, a public company might face legal risk from the US Securities and Exchange Commission (SEC), plaintiffs and whistleblowers for failure to escalate and disclose material risks. For software that is sold to consumers as well as the government, the Federal Trade Commission (FTC), state regulators or consumer plaintiffs might allege that inaccurate security attestations constitute a deceptive trade practice.
What Should Government Contractors Do?
Government contractors, including off-the-shelf (GOTS) software producers and upstream third-party developers, should act now to prepare to make and defend secure software attestations.
In-house counsel can ask their software developers the following questions to help assess their company’s maturity against the secure development requirements of the CISA Form:
- Is our development infrastructure inventoried and protected with standard enterprise security controls, including those listed in the CISA Form?
- Do we perform software composition analysis (SCA) to identify and/or validate the open-source code and other third-party components that are included in our software?
- Can we produce an accurate software bill of materials (SBOM) if requested?
- Do we automatically test the software for vulnerabilities during development and prior to release?
- Do we track and remediate discovered vulnerabilities?
- Do we use the software composition analysis results to identity upstream security vulnerabilities?
- Do we have an established process to accept, review and address vulnerability disclosures from external parties?
- Do we monitor and enforce compliance with these practices?
- Do we automatically create and archive secure software development artifacts?
Companies should consider whether to conduct a readiness assessment at the direction of counsel. A privileged investigation can be an effective way to identify and address compliance gaps and to confirm that the company has the necessary documentation to defend the attestation in the face of a challenge.
The public has until June 26, 2023, to submit its feedback on the draft CISA Form. Companies can submit public comments anonymously through counsel or via an industry association, among other means. Companies can also submit comments directly by visiting regulations.gov.
McDermott’s Privacy and Cybersecurity and Government Contracts teams are continuing to monitor the administration’s implementation of Executive Order 14028, including the pending updates to the FAR and DFARS.

Of Digital Interest Quarterly Roundup | Q1 2023
ARTICLE / REPORT
Of Digital Interest Quarterly Roundup | Q1 2023
April 28, 2023
Read time: 2 min
McDermott’s digital health team continually monitors legal developments affecting all aspects of the remote delivery of care. This inaugural issue of our Of Digital Interest Quarterly Roundup highlights key issues and trends in the first quarter of 2023.
Remote care is an important development in care delivery, but the regulatory patchwork is complicated. Our digital health team works alongside the industry’s leading providers, payors and technology innovators to help them enter new markets, break down barriers to delivering accessible care and mitigate enforcement risk through proactive compliance. Are you working to make healthcare more accessible through telehealth?

IRS Releases Memorandum on the Tax Consequences of a Blockchain Protocol Upgrade
ARTICLE / CLIENT ALERT
IRS Releases Memorandum on the Tax Consequences of a Blockchain Protocol Upgrade
April 27, 2023
Read time: 7 min
On April 21, 2023, the Internal Revenue Service (IRS) released a Chief Counsel Advice memorandum (ILM 202316008), concluding that a protocol upgrade to the consensus mechanism of a cryptocurrency blockchain that did not result in the issuance of new tokens (or coins) did not result in gain, loss or other income to a taxpayer who held cryptocurrency native to that blockchain.
IRS GUIDANCE ON PROTOCOL UPGRADES
On September 15, 2022, Ethereum implemented a protocol upgrade known as “The Merge” whereby Ethereum upgraded from the original proof-of-work (PoW) consensus mechanism to proof-of-stake (PoS). The Merge was one step of Ethereum’s roadmap to better scale itself and adapt to the latest technologies that emerge from research and development. This did not result in any change in ownership for holders of Ether (ETH) tokens, unlike a hard fork, another type of protocol update that may involve the issuance of new tokens (or coins) to preexisting token holders. Ethereum has additional upgrades on its roadmap and just recently completed another protocol update known as the “Shanghai Upgrade,” which involved the final step for Ethereum to move from a PoW to a PoS consensus mechanism.
Ethereum is not the only blockchain to undergo a protocol upgrade. In the same month as The Merge, Algorand announced the implementation of a major protocol upgrade as well. As blockchain technology continues to develop, and as new technologies are created and released, additional protocol updates are anticipated with evolving blockchains (such as Ethereum).
The IRS’s memorandum addressed the federal income tax consequences of a blockchain that underwent a protocol upgrade. While no reference is explicitly made to which blockchain is being referred to, based on the facts provided in the memorandum, it can be inferred that such guidance likely relates to The Merge.
The memorandum considered a simple fact pattern in which a specific blockchain (K) used distributed ledger technology to record transactions involving cryptocurrency based on a particular protocol. The protocol included a consensus mechanism for adding new blocks of transactions to the blockchain, including those involving a particular cryptocurrency (C). A taxpayer purchased 10 units of C and stored the private keys for these units. Later, K changed its consensus mechanism used to select who may validate transactions and add blocks of transactions to the K blockchain from PoW to PoS. The memorandum labeled this change as the “protocol upgrade.” After the protocol upgrade, the K blockchain required that transactions be validated and new blocks be added to the K blockchain exclusively through the new PoS consensus mechanism. The protocol upgrade did not affect or otherwise change the existing transaction history on the K blockchain and new blocks were added to the K blockchain pursuant to the new protocol. Units of the cryptocurrency C remain unchanged, including the 10 units held by the taxpayer. The taxpayer did not receive any cash, services or property as a result of the protocol upgrade.
GAINS, LOSSES AND INCOME TAX GENERALLY
Code Section 1001 provides rules for the computation and recognition of gains and losses related to the sale or other disposition of property. Gains and losses generally arise from the difference between the amount of money (as well as the value of any property) received from selling or otherwise disposing of property and the taxpayer’s tax basis in that property. Treasury Regulations further provide that when property is exchanged for other property differing materially in kind or in extent, gain or loss may be realized and is treated as income or as a loss sustained. However, an exchange of property is only a realization event if the exchange results in the receipt of property that is materially different from the property transferred. Properties must embody legally distinct entitlements to be materially different. Otherwise, the transfer will not result in a realization of gain or loss.
Code Section 61 provides the rules for gross income. Gross income means all income from whatever source derived, including gains from dealings in property. Generally, all gains that are clearly realized by the taxpayer are included in gross income. This includes when a taxpayer receives property or services that have a greater fair market value than what the taxpayer pays for it. Because this calculation is concerned with the value received, income may be realized in many forms, including money, property or services.
TAX CONSEQUENCES OF A PROTOCOL UPDATE
The memorandum’s conclusions on gain or loss treatment and income resulting from the protocol upgrade are straightforward. First, the memorandum concluded that the protocol upgrade did not result in a realization event in which the taxpayer realized gain or loss on the existing 10 units of cryptocurrency C. This is because the existing units of cryptocurrency C were not changed by the protocol upgrade and there was no taxable exchange of units.
Second, the memorandum concluded that the protocol upgrade did not result in the inclusion of income to the taxpayer. This is because there was no accession to wealth resulting from the upgrade; the taxpayer’s 10 units of cryptocurrency C remain unchanged and the taxpayer did not otherwise derive any separable economic benefit from the protocol upgrade, such as cash, services or other property (including other cryptocurrencies).
CONCLUSION
Although the memorandum deals with a fact pattern that involves a protocol upgrade that does not directly result in a hard fork, the memorandum’s guidance is consistent with Situation 1 of Rev. Rul. 2019-24 and Question 22 of the IRS’s FAQs on Virtual Currency Transactions, both of which provide that if a cryptocurrency went through a hard fork but a taxpayer did not receive any new cryptocurrency (whether through an airdrop or some other kind of transfer), the taxpayer does not have any taxable income. Unlike Situation 2 of Rev. Rul. 2019-24 and Question 23 of the IRS’s FAQs where the IRS ruled that a taxpayer does have taxable income if an airdrop was followed by a hard fork, Situation 1 of Rev. Rul. 2019-24 and Question 22 of the IRS’s FAQs haven’t been viewed as controversial guidance that requires further clarification and such guidance can reasonably be extrapolated to a fact pattern that involves a protocol upgrade that is not a hard fork.
Notwithstanding the above, the IRS’s additional guidance regarding a protocol upgrade (without a hard fork) continues to support the fact that absent (1) a change in an existing property, (2) an exchange of property or (3) the receipt of property (or another separable economic benefit) to a taxpayer, a taxpayer may be able to expect that a protocol update (whether in the form of a hard fork without an airdrop, an update to a consensus mechanism or otherwise) does not result in gain, loss or other income to itself.
The memorandum shows the IRS’s view that guidance related to the taxation of cryptocurrency (and related technologies) is important and is being given priority.
