Attention A T users. To access the menus on this page please perform the following steps. 1. Please switch auto forms mode to off. 2. Hit enter to expand a main menu option (Health, Benefits, etc). 3. To enter and activate the submenu links, hit the down arrow. You will now be able to tab or arrow up or down through the submenu options to access/activate the submenu links.
Attention A T users. To access the combo box on this page please perform the following steps. 1. Press the alt key and then the down arrow. 2. Use the up and down arrows to navigate this combo box. 3. Press enter on the item you wish to view. This will take you to the page listed.
Veterans Crisis Line Badge
My healthevet badge

Vulnerability Disclosure Policy
Department of Veterans Affairs



The Department of Veterans Affairs (VA) is charged with providing health care and benefits to support Veterans and members of their families.

VA is committed to ensuring the integrity of its information by securing its information systems. A vulnerability is a “weakness in an information system, system security procedures, internal controls, or implementation that could be exploited or triggered by a threat source.” This Vulnerability Disclosure Policy (VDP) is meant to address some of the possible apprehensions and explain what research would be authorized under this VDP. Good faith research that conforms to these guidelines is considered authorized research. The Department will focus on quickly working to resolve the vulnerability you have identified and is not interested in pursuing legal action when there is authorized research under this policy.

This policy describes what systems and types of research are covered under this policy, how to report the vulnerability, how long VA asks security researchers to wait before publicly disclosing vulnerabilities and what communication or response to expect from the Department.

The Department encourages security researchers to contact us to report potential vulnerabilities in VA systems.


The Department welcomes the chance to hear from good faith security researchers, who are conducting or conduct security research under these VDP guidelines. This VDP is meant to address some of the possible apprehensions and explain that working within this VDP is the best way to ensure the research will be authorized. Good faith research is not considered a security breach if it follows the guidelines below. Once VA sees it is authorized research, the Department wants to focus on quickly working to resolve the vulnerability you have identified and is not interested in pursuing legal action. Should legal action be initiated by a third party against you for activities that were conducted in accordance with this policy, VA will make this authorization known.

These Guidelines Require that You/a Researcher:

  • Access a VA information system in a way that follows this VDP.
  • If you discovered a vulnerability, reported it by following the instructions in this VDP.
  • Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction or manipulation of data.
  • Limit the use of discovered exploits to the extent necessary to confirm a vulnerability’s presence.
  • Do not use an exploit to compromise or exfiltrate data, establish command line access and/or persistence, or use the exploit to pivot to other systems.
  • Provide VA a reasonable amount of time to resolve the issue before you disclose it publicly.
  • Do not submit a high volume of low-quality vulnerability reports.

If you established that a vulnerability or security weakness exists or encounter any sensitive data or data belonging to individuals with their financial information, medical information, contract information or proprietary information which might be a trade secret, you must stop your test, notify VA immediately, and not disclose this data to anyone else.

Test Methods

The following test methods are not authorized or considered good faith/authorized research:

  • Network denial of service (DoS or DDoS) tests or other tests that impair access to or damage a system or data
  • Physical testing (e.g. office access, open doors, tailgating), social engineering (e.g. phishing, vishing), or any other non-technical vulnerability testing


This policy applies to the following systems and services:

Any service not expressly listed above, such as any connected services, are excluded from scope and are not authorized for testing. Additionally, vulnerabilities found in systems from VA vendors fall outside of this policy’s scope and should be reported directly to the vendor according to their disclosure policy (if any). If you aren’t sure whether a system is in scope or not, contact the VA at before starting your research.

Though VA develops and maintains other internet-accessible systems or services, we ask that active research and testing only be conducted on the systems and services covered by the scope of this document. If there is a system not in scope that you think merits testing, please contact the VA to discuss it first. VA will increase the scope of this policy over time.

Reporting a Vulnerability

  • Information submitted under this policy will be used for defensive purposes only – to mitigate or remediate vulnerabilities. If your findings include newly discovered vulnerabilities that affect all users of a product or service and not solely Department of Veterans Affairs, we may share your report with the Cybersecurity and Infrastructure Security Agency (CISA), where it will be handled under their coordinated vulnerability disclosure process. VA will not share your name or contact information without express permission.
  • The VA accepts vulnerability reports at
  • Reports may be submitted anonymously. If you share contact information, we will acknowledge receipt of your report within 3 business days.
  • VA will not offer payment or compensation for good faith research.

What VA would like to see from you

In order to help us triage and prioritize submissions, we recommend that your reports:

  • Describe the location the vulnerability was discovered and the potential impact of exploitation.
  • Offer a detailed description of the steps needed to reproduce the vulnerability (proof of concept scripts or screenshots are helpful).
  • Be in English, if possible.

What you can expect from VA

When you choose to share your contact information with us, we commit to coordinating with you as openly and as quickly as possible.

  • Within 3 business days, we will acknowledge that your report has been received.
  • We will maintain an open dialogue to discuss issues.


Questions regarding this policy may be sent to We also invite you to contact us with suggestions for improving this policy.

For broader questions regarding the requirement for this policy or specific definitions, please see the “Frequently Asked Questions” section of this link at the Department of Homeland Security: - Binding Operational Directive 20-01