Skip to main content

Vulnerability Disclosure Policy


This policy is intended to give security researchers clear guidelines for conducting vulnerability discovery activities and to convey our preferences in how to submit discovered vulnerabilities to us.

This policy describes what systems and types of research are covered under this policy, how to send us vulnerability reports, and how long we ask security researchers to wait before publicly disclosing vulnerabilities.

We encourage you to contact us to report potential vulnerabilities in our systems or if you find information in general about TVA that could pose significant harm if disclosed. 

Vulnerabilities submitted to TVA will be used for defensive purposes to mitigate or remediate vulnerabilities in our network services and those of our vendors.


If you make a good faith effort to comply with this policy during your security research, we will consider that security research to be authorized, we will work with you to understand and resolve the issue quickly, and Tennessee Valley Authority will not recommend legal action related to your security research that is consistent with this policy. You are expected, as always, to comply with all applicable laws.


Under this policy, “research” means activities in which you:

  • Notify us as soon as possible after you discover a real or potential security issue.
  • Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction or manipulation of data.
  • Only use exploits to the extent necessary to confirm a vulnerability’s presence. Do not use an exploit to compromise or exfiltrate data, establish persistent command line access, or use the exploit to pivot to other systems.
  • Provide us a reasonable amount of time (60 - 90 days) to resolve the issue before you disclose it publicly.
  • Do not submit a high volume of low-quality reports.
  • Once you’ve established that a vulnerability exists or encounter any sensitive data (including personally identifiable information, financial information, or proprietary information, or trade secrets of any party), you must stop your test, notify us immediately, and not disclose this data to anyone else.

Unauthorized Test Methods

The following test methods are not authorized:

  • 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
  • Defacing or alteration of websites
  • Intentional compromise to perform data exfiltration of privacy, safety, intellectual property, or Controlled Unclassified Information (CUI) including PII or RPII

Out-Of-Scope Vulnerabilities

The following vulnerabilities are considered Out of Scope:

  • Vulnerabilities that cannot be verified or replicated with detailed instructions
  • Client-side application/browser autocomplete or saved password/credential functions
  • Incomplete or missing SPF/DMARC/DKIM records
  • Submissions related to rate limiting/brute force protections
  • URL/Open Redirection

Scope of Policy

TVA leverages third-party services and managed service providers (MSPs) to provide communications capabilities or externally available services to the general public or its business partners. These third-party services may have their own vulnerability disclosure program or vendor-specific privacy policies. If so, submit vulnerability disclosures through the vendor’s specific VDP requirements.

If it is not possible to obtain the vendor’s authorization, you may not include those systems or services in scope of your policy. Testing of vendor websites outside of this policy is not protected under this disclosure program and may be subject to legal prosecution. 

This policy applies to all TVA-managed systems that are accessible from the internet and are associated to the following systems and services:

  1. * domains
  2. * domains
  3. * domains
  4. * domains
  5. * domains
  6. * domains

This includes any OSINT data gathered that pertains to a TVA digital asset. e.g., compromised passwords, sensitive data stored in public repositories like GitHub, etc.

Any service not expressly listed above, such as any connected services, are excluded from scope and are not authorized for testing. If you aren’t sure whether a system is in scope or not, contact us at before starting your research (or at the security contact for the system’s domain name listed in the .gov WHOIS).

Though we develop and maintain 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 particular system not in scope that you think merits testing, please contact We will add additional sites to the scope as resources permit.

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 Tennessee Valley Authority, we may share your report with the Cybersecurity and Infrastructure Security Agency, where it will be handled under their coordinated vulnerability disclosure process. We will not share your name or contact information without express permission.

Reports may be submitted anonymously. If you share your contact information, we will make our best efforts to acknowledge receipt of your report within 3 business days.

We do not support PGP-encrypted emails.

By submitting a vulnerability, you acknowledge that you have no expectation of payment and that you expressly waive any future pay claims against the U.S. Government related to your submission.

What We Need From You

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

  • Describe the location where 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).

What You Can Expect From Us

When you submit a vulnerability report to this program, we commit to coordinating with you as openly and as quickly as possible.

  • Within 3 business days, we will make our best efforts to acknowledge that your report has been received.
  • To the best of our ability, we will confirm the existence of the vulnerability to you and be as transparent as possible about what steps we are taking during the remediation process, including on issues or challenges that may delay resolution.
  • We will maintain an open dialogue to discuss issues.