NewsAugust 4, 2017 @ 6:30 AM

DOJ Issues Framework for Vulnerability Disclosure Programs

To help reduce civil and criminal violations of the Computer Fraud and Abuse Act (CFAA), the U.S. Department of Justice (DOJ) Criminal Division’s Cybersecurity Unit released a framework to help organizations fulfill their legal obligation to disclose vulnerabilities and establish formal vulnerability disclosure programs.

Titled, “A Framework for a Vulnerability Disclosure Program for Online Systems,” the guidelines are designed to show how relevant information could be legally obtained — without breaking existing laws and accessing a protected computer without authorization.

Inside the Framework

Version 1.0 of the document did not concern itself with the particular shape or the objectives of a disclosure program. Instead, it concentrated on authorized discovery and disclosure conduct as it applies to the CFAA, according to SecurityWeek.

Designing the program is the first step, according to the framework. This means figuring out what network components and data to include, as well as the types of vulnerabilities and security practices that will be involved. If third-party components or data are to be part of the program, the organization can determine whether it should request additional authorization for them.

There are other things to consider. For example, an organization that handles sensitive information must weigh the risks and consequences of exposing data that it has a legal duty to protect. Depending on the nature of the information, legal counsel may need to be involved.

The SecurityWeek article also noted that the DOJ “advises organizations to consult the 18F vulnerability disclosure playbook, the NTIA’s work on vulnerabilities and their disclosure, and International Standards Organization (ISO) guidance on this topic during the design phase.”

Managing Vulnerability Disclosure Programs

Managing the program comes next. This involves mostly procedural tasks, such as defining a point of contact for reporting and how to handle out-of-bounds situations.

The final step is defining intent policies. As part of this phase, companies must outline authorized and unauthorized conduct, the systems and data that will be covered by the program and the data access restrictions. The framework wraps up with implementation, which means making the policy available and encouraging its use.

These new framework guidelines will aid security personnel in creating a valuable security program without running afoul of existing laws. Since a bug bounty program can be of great use in reducing attack surfaces, it pays to build one the right way.

Share this Article:
Larry Loeb

Principal, PBC Enterprises

Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek. He wrote for IBM's DeveloperWorks site for seven years and has written a book on the Secure Electronic Transaction Internet protocol. His latest book has the commercially obligatory title of Hack Proofing XML. He's been online since uucp "bang" addressing (where the world existed relative to !decvax), serving as editor of the Macintosh Exchange on BIX and the VARBusiness Exchange.