To Disclose or Not To Disclose: Federal Government & Cybersecurity Vulnerabilities
Client Alert | 1 min read | 11.16.17
On November 15, 2017, the White House Cybersecurity Coordinator, Rob Joyce, announced a formative cybersecurity policy entitled “Vulnerabilities Equities Policy and Process for the United States Government.”
According to the policy, the primary focus is to “prioritize the public's interest in cybersecurity and to protect core Internet infrastructure, information systems, critical infrastructure systems, and the U.S. economy through the disclosure of vulnerabilities discovered by the United States Government (USG).” The Vulnerabilities Equities Process (VEP) balances dissemination of vulnerability information (e.g., zero day exploits) to the vendor/supplier in the expectation that it will be patched with temporarily restricting the knowledge of the vulnerability to the USG, and potentially other partners, so that it can be used for national security and law enforcement purposes, such as intelligence collection, military operations, and/or counterintelligence. In striking this balance, the policy aims to increase transparency regarding the process for the public and businesses, and also signals that the US will join with several countries that have announced formal policies in this area regarding management of vulnerabilities. Interestingly, this policy expands the management of vulnerabilities to include a broad array of national security and intelligence agencies.
This policy supersedes the Commercial and Government Information Technology and Industrial Control Product or System Vulnerabilities Equities Policy and Process, dated February 16, 2010.
This policy applies to all USG components and personnel and contractors and includes Government off-the-shelf (GOTS), Commercial off-the-shelf (COTS), or other commercial information systems (to include open-source software), Industrial Control Systems (ICS) or products, and associated systems such as Supervisory Control and Data Acquisition (SCADA) and Distributed Control Systems (DCS).
Businesses and the public will likely be interested in the annual public reporting that is promised, which may include statistics about how many vulnerabilities go through the process and even potentially how long they are withheld from disclosure.
Insights
Client Alert | 2 min read | 07.15.26
CMMC Phase II Suspension Requires Reconsideration of Such Requirements in Solicitations
As discussed in more detail here, the U.S. Department of War (DoW) recently issued a memorandum (Memo 26-P-1023, dated July 13, 2026) directing the immediate suspension of Cybersecurity Maturity Model Certification (CMMC) Phase II requirements (Level I and II self assessments are still permitted). Significantly, the memo directs that “all pending and future CMMC implementation milestones across DoW solicitations and contracts are held in abeyance until further notice.” Moreover, the DoW issued a memorandum on implementing these requirements (available here), directing agencies to issue amendments removing CMMC Level 2 and 3 requirements from active solicitations “as soon as practicable.” Contractors should monitor the government’s compliance with this requirement and should be prepared, if needed, to file a bid protest to protect their rights.
Client Alert | 3 min read | 07.15.26
Client Alert | 3 min read | 07.14.26
Client Alert | 3 min read | 07.13.26
Amici Rally Behind Liberty Global, Urging Tenth Circuit to Rein in Economic Substance Doctrine
