Vulnerability Disclosure Policy

Vulnerability Disclosure Policy


Idaho Secretary of State’s Office (IDSOS) is committed to ensuring the security of the public by protecting their information. 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.


If you make a good faith effort to comply with this Policy during your security research, we will consider your research to be authorized, we will work with you to understand and resolve the issue quickly, and IDSOS will not recommend or pursue legal action related to your research. Should legal action be initiated by a third party against you for activities that were conducted in accordance with this Policy, we will make this authorization known.


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 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.

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.
  • Degradation of services, network, software, or hardware performance.
  • Disruption of a network, software or hardware services.
  • Any form of manipulation to the integrity of any production or public facing data, information or images.


This policy applies to the following systems and services:

  • **
  • ** (with exception to the provided out-of-scope list)

The following sites subdomains are restricted from active vulnerability discovery, and are considered out-of-scope for the VDP program:


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 our 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 our reporting partner, the Election Infrastructure Information Sharing and Analysis Center (EI-ISAC) at [email protected] before starting your research.

Though we develop and maintain other internet-accessible systems or services, active research and testing must 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, first contact us to discuss it. We aim to 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 IDSOS, we may share your report with the EI-ISAC, which in turn may share it 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 from you.

We accept vulnerability reports via email at [email protected]. Reports may be submitted pseudonymously, with the sender’s email as the only required identifying information.

You may not submit sensitive information via email. If you need to send us sensitive information, indicate this in your report and the EI-ISAC will provide a secure fileshare link. To ease reviewing and responding to your submission, use the submission standard.

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

What We Would Like To See From You

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

  1. Describe the location the vulnerability was discovered and the potential impact of exploitation including URL/software/service(s) affected, and version.
  2. Offer a detailed description of the steps needed to reproduce the vulnerability (proof of concept scripts, illustrations, and screenshots are helpful).
  3. Describe potential attack scenarios and consequences.
  4. Provide any recommended mediation actions.
  5. Be in English.

What You Can Expect From Us

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

Within one business day, the EI-ISAC will acknowledge that your report has been received.

The EI-ISAC will contact you if it requires additional information and, if necessary, provide you with a secure file share link for providing additional information.

Within five business days of having all necessary information, the EI-ISAC will validate the existence of the vulnerability and share it with IDSOS. If the EI-ISAC is unable to confirm the vulnerability, it will work with you to understand why.

Within 120 days, the EI-ISAC will provide an update on the status of remediation. Additionally, the EI-ISAC or IDSOS may contact you regarding issues or challenges regarding remediation.

We will maintain an open dialogue to discuss issues.


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

DO NOT send vulnerability reports to this email address.

System Upgrade In Progress

Campaign Finance, Lobbyist Reporting, and Online Voter Tools are expected to be offline from April 9th at 5:00 p.m. MDT, through April 12th at 8:00 a.m. MDT to complete a system upgrade.

Per Idaho Code 67-6607, campaign finance is reported monthly during a campaign’s election year. The deadline for the March report falls on Saturday, April 10th. Due to the interruption caused by this upgrade, political treasurers will be allowed to file the March report until 11:59 p.m. MDT on Monday, April 12th.

While we do our best to ensure compliance with all deadlines in statute, the timing of this release is critical to ensure minimal (or no) impact to the May election cycle. We are sorry for any inconvenience this may cause.