CCAP

Government Accountability for the Greater Chattanooga Area



1. Scope: What This Policy Covers

This policy applies to systems directly operated by CCAP:

Out of scope. This policy does not cover:

2. What Researchers May and May Not Do

You may:

You may not:

3. How to Report a Vulnerability

Email security chattaccountability.org. This address is for vulnerability reports only. For anything else, use the contact form.

Subject line: Use something descriptive, such as [Security] Reflected XSS on chattaccountability.org.

Encryption: CCAP does not currently publish a PGP key. If you need to share sensitive proof-of-concept details in an encrypted format, email first and arrangements can be made for a secure transfer.

What to include:

4. Response Commitments

CCAP has no dedicated security team. These are targets, not a guaranteed SLA, and CCAP will tell you if something is going to take longer than expected.

Target response times for security vulnerability reports
Milestone Target
Acknowledge receiptWithin 5 business days
Initial triage (confirm validity, assign severity)Within 10 business days
Status updates, if still openRoughly every 30 days
Fix (critical)Best effort, as fast as availability allows
Fix (high, medium, or low)Varies by severity, with no fixed deadline

Coordinated disclosure: Please give CCAP a reasonable window, typically up to 90 days for non-critical issues, before public disclosure. If more time is needed, that will be communicated, and CCAP will never ask you to stay quiet indefinitely.

5. Safe Harbor

CCAP will not pursue legal action against a security researcher who: follows the rules in Section 2 above; reports the vulnerability through the channel in Section 3; does not access, exfiltrate, modify, or destroy data beyond what's necessary to demonstrate the issue; and acts in good faith to avoid disrupting the site or harming its visitors.

CCAP considers security research conducted in accordance with this policy to be authorized access under the Computer Fraud and Abuse Act (18 U.S.C. § 1030) and comparable Tennessee law. If a third party threatens or brings legal action against a researcher for work that complied with this policy, CCAP will state clearly that the research was authorized.

This safe harbor applies only to chattaccountability.org itself. CCAP can't authorize testing against, or provide safe harbor for, Change.org, DreamHost, or any other third-party service this site links to or relies on. Report issues with those directly to the service in question.

6. Recognition

CCAP does not offer a monetary bug bounty, since there's no budget for one. With your permission, CCAP will credit you by name or handle on the Hall of Thanks page once a reported vulnerability is confirmed and resolved, along with a thank-you. If you'd rather stay anonymous, say so and you won't be named.

Common Questions

What's in scope?

Only chattaccountability.org, this website. Issues with Change.org or other third-party services this site links to or loads resources from should go to those services directly, not to CCAP.

How do I report an issue?

Use the dedicated security address in the "How to Report a Vulnerability" section above, with what you found, where, how to reproduce it, and its likely impact.

Is there a bug bounty?

No. CCAP has no budget for a bug bounty program. If you'd like public credit for a confirmed, resolved report, say so when you report it, and you'll be listed on the Hall of Thanks page.

How fast will I hear back?

As fast as a small, unpaid project can. CCAP aims to acknowledge reports within 5 business days, but there's no formal SLA. See "Response Commitments" above.