Skip to content
AvalaSecurity

Rules & safe harbor

Research within clear boundaries.

These rules define how to test, handle evidence, and coordinate disclosure. Read them alongside the scope before you begin.

Terms effective October 26, 2026. See changes to this program for how updates apply.

Testing

Research rules.

  1. Monthly bounty pool is capped at $5,000 aggregate while we are seed-stage. Reports past the cap are still triaged and fixed; approved bounties are queued and paid in order received as later pools allow.
  2. Conduct research in good faith and within the scope defined above.
  3. Stop at proof-of-concept. Do not exfiltrate data beyond what is needed to demonstrate impact.
  4. Do not access, modify, or destroy data that is not yours.
  5. Do not degrade availability (no load or DDoS testing).
  6. Do not pivot into internal networks after establishing an initial foothold.
  7. Do not use automated scanners against production without prior written approval.
  8. Report findings within 48 hours of discovery.
  9. Keep every finding confidential until Avala confirms the fix is deployed and a publication date is agreed in your report thread. See the disclosure and payment eligibility terms below.
  10. Do not use social engineering against Avala staff, customers, or contractors.
  11. Do not submit reports generated primarily by automated tools or LLMs without independent validation.

Policy

Safe harbor.

Avala considers security research and vulnerability disclosure activities conducted consistent with this policy to be "authorized" conduct under the Computer Fraud and Abuse Act (CFAA), the DMCA, and applicable anti-hacking laws.

We will not pursue civil action or file a complaint with law enforcement for accidental, good-faith violations of our policy. If legal action is initiated by a third party against someone acting in compliance with our policy, we will take reasonable steps to make it known that the activities were authorized.

You must still comply with all applicable laws. Safe harbor does not extend to activities that exceed the program scope or rules, or to research conducted outside good-faith security testing.

This policy is modeled on the disclose.io open framework. It is not a substitute for legal advice. If you have legal questions, consult counsel before testing.

Publication

Coordinate the disclosure.

Keep the finding confidential until we confirm in your report thread that the fix is deployed and we have agreed a publication date. There is no fixed embargo length, because there is no fixed fix timeline; if a validated report has been open for 90 days without a fix, ask for a date and we will propose one.

Use your report thread to coordinate a publication date and researcher credit. Public recognition is optional; you can choose your attribution preference.

For qualifying issues, we request a CVE on the researcher's behalf through MITRE.

Read published advisories

Eligibility

Disclosure and payment eligibility.

You agree to these terms when you submit a report. They are the condition of every bounty.

  1. Bounties are discretionary rewards for research that follows this program through to resolution. Nothing in this program creates a contractual obligation to pay, and Avala makes the final decision on eligibility and amount.
  2. Keep each finding confidential until Avala confirms in your report thread that the fix is deployed and the two of you have agreed a publication date. This covers public posts, talks, advisories, and sharing with any third party.
  3. Disclosing a finding before that point forfeits payment on that report, on every other report you have open with Avala, and on any report you submit afterwards. It also ends your participation in the program. Using a threat of disclosure to speed up remediation or payment is treated the same way.
  4. If a validated report has been open for 90 days without a deployed fix, you may ask in the report thread for a publication date. We will answer with a proposed date and a short explanation of where the fix stands. Disclosure without an agreed date remains early disclosure.
  5. Avala decides, at its sole discretion and acting in good faith, whether a disclosure occurred and whether forfeiture applies. We will tell you in writing if it does.

How we respond

What to expect from us.

Follow progress in your private report thread. This is how a report moves through the program. We publish no response-time targets: we are a small team, and we would rather tell you that than post a deadline we cannot keep.

Acknowledgment
Every submitted report is confirmed by email and gets a private thread.
Triage
We assess severity and scope on a best-effort basis, in the order reports are received. Severity sets our internal priority; it does not set a deadline.
Updates
We post in your report thread when there is something to report. We do not commit to an update cadence, and silence means the report is still open, not that it has been dropped.
Remediation
We will get to every validated report. We do not commit to a remediation timeline, and we will not publish one we cannot keep.
Bounty decision
Made when the fix is deployed, or when the report is closed as duplicate or not applicable.
Payment
Approved bounties are queued in the order reports were received and paid as the monthly pool allows. Payment timing is not fixed; the program status notice carries the latest update.

Changes

Changes to this program.

Terms effective October 26, 2026.

  1. Avala may change, suspend, or end this program and any of its terms at any time, without notice. The version published on this page, with its effective date, is the one in force.
  2. A change applies to reports submitted on or after its effective date. For a report that is already open when the terms change, the eligibility and payment-process terms in force at the time of the bounty decision govern that decision, and the reward tiers in force when the report was submitted govern the amount.
  3. A researcher who submitted under an earlier version keeps the disclosure obligation they agreed to at submission; Avala may ask for an extension in the report thread, and asks that you treat a validated, unfixed report as confidential until a date is agreed.
  4. If a court finds any part of these terms unenforceable, the rest stay in force.

Changelog

October 26, 2026
Replaced response-time targets with a best-effort process description. Added disclosure and payment eligibility terms, made bounties explicitly discretionary, and added the program-change terms below.
September 15, 2026
Reduced reward tiers; informational and low findings no longer carry a cash reward.
April 18, 2026
Program launched.

Get started

Have a finding to share?