NORM
“States should create procedurally
transparent frameworks to assess whether
and when to disclose not publicly known
vulnerabilities or flaws they are aware of in
information systems and technologies. The
default presumption should be in favor of
disclosure.”
BACKGROUND
As the complexity of operating systems, critical
software and computer hardware grows, they
increasingly
contain
vulnerabilities.
Those
vulnerabilities can be exploited by state and nonstate actors. States sometimes have conflicting
interests and responsibilities when dealing with
newly discovered vulnerabilities. On the one hand,
they have an obligation to promote the resilience and
integrity of infrastructure essential to the stability of
cyberspace and by helping thwart malicious cyber
activity make the entire digital ecosystem safer for
all users. This would argue for a state to quickly
disclose newly discovered vulnerabilities to vendors
and manufacturers for patching, as well as making
broader public disclosures, where appropriate, to
protect the public. On the other hand, states have an
obligation to protect their citizens from criminals, to
investigate and prosecute cyber crime offenses, and
reserve the right to impose sanctions that act as both
a specific and a general deterrent to future malicious
activity. An essential tool to pursue malicious
actors, and particularly sophisticated actors such as
rogue states, is the exploitation of computer code
vulnerabilities in the digital infrastructure on which
they rely. States therefore often argue that they must
preserve at least some select capabilities, including the
use of undisclosed vulnerabilities, or else extremely
capable malicious actors would go undiscovered and
unchecked.
While states are unlikely to voluntarily disclose every
vulnerability they discover, there has been a recent
move by several states away from a presumption that
all vulnerabilities will be retained, to one where the
presumption is in favor of disclosure in the interests of
greater systemic cybersecurity. A key part of this is the
creation, by states, of a publicly described process for
assessing the pros and cons of disclosure that takes
into account the full range of policy, economic, social
and technical equities. More specifically, that process
should be procedurally transparent and take into
account a full range of views including factors such as:
network security and resiliency; the security of users
and their data; law enforcement and national security
utility; and diplomatic and commercial implications.
The United States has recently promulgated a new
version of such a process and other countries are
considering creating their own Vulnerability Equities
Process (VEP) policies. Given that vulnerability
discovery and disclosure is broader than any one
state, in order to promote network resilience while
at the same time safeguarding national security, it
would be in the interest of the long-term stability of
cyberspace for every state to have such a process
in place. Additionally, states should work towards
compatible and predictable processes. The existence
of such processes can act as a confidence-building
measure between states in that it provides some
assurance that relevant equities and competing
interests are fully considered. Of course, every state
has differing capabilities and unique interagency
structures, however, any effective VEP process should
be designed to take a broad range of perspectives
and equities into account. In addition, though the
actual decisions reached in individual cases may,
out of necessity, remain confidential, there should
be transparency on the general procedures and
framework for reaching such decisions. Finally, this
norm deals only with the establishment of a process
where disclosure decisions are made. If a government
or any other entity decides to make a disclosure, such
disclosure should be made in a responsible manner
that promotes public safety and does not lead to
exploitation of that vulnerability.
GLOBAL COMMISSION
ON THE STABILITY OF CYBERSPACE
NOVEMBER 2018
13
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents