How we keep PNEC's site safe — and what to do if something looks wrong.
Poway NEC is a 100% volunteer organization, but we treat security like a critical-path concern. The site holds household contact info, neighborhood coordinator rosters, and an emergency-time communications channel. Here's what we do to protect it, and how to reach us if you spot a problem.
Encrypted everywhere
Every connection to PNEC uses TLS 1.2 or 1.3 with HSTS enforcement. Sign-in passwords are hashed with PBKDF2-SHA256 server-side — they're never stored or transmitted in plain text.
256-bit · HSTS enabledAccount lockout
If someone tries to guess your password, after 5 failed attempts in 15 minutes the account is automatically locked for 15 minutes — even if the attacker rotates IPs. The site rate-limits sign-in attempts at 8 per minute per IP on top of that.
15-min lockout · IP rate-limitedBrowser hardening headers
Every API response carries Content-Security-Policy, X-Frame-Options, Referrer-Policy, Permissions-Policy, and Strict-Transport-Security headers — defense-in-depth against XSS, clickjacking, and downgrade attacks.
CSP · HSTS · X-Frame-OptionsReal-time audit log
Every sign-in, registration, account lockout, page edit, and admin action lands in a server-side audit log. Admins see real-time security events on a private dashboard — including suspicious user-agent strings (sqlmap, nmap, etc.) and rate-limit hits.
90-day retention · admin-onlyPrivacy-first data handling
Your account exists to connect you with your block coordinator. We don't sell or share your data, don't run third-party advertising, and don't load tracking pixels. Push notifications (when you opt in) only post to verified push providers — Apple, Google, Mozilla, Microsoft.
No tracking · No ads · No third partiesBuilt & maintained by neighbors
The PNEC site is open-source and maintained by Poway volunteers — not an outsourced agency. All code changes are reviewed, tested, and deployed with version history. Reverting a bad change takes seconds, not days.
Open source · Versioned · Locally runFound a security issue? Tell us.
If you believe you've found a vulnerability — anything from a broken login flow to a way to access another user's data — we want to hear about it before it becomes a problem.
Please:
- Email contact@example.test with "Security" in the subject line.
- Include enough detail for us to reproduce the issue (URL, steps, expected vs. actual).
- Don't post the issue publicly (Nextdoor, social media, GitHub issues) until we've confirmed the fix is live.
- Don't run automated scanners against the production site without coordinating with us first — they trigger our rate-limit + lockout systems and can lock real volunteers out of their accounts.
PNEC is a small volunteer organization, so we don't run a paid bug-bounty program. But we will: respond to legitimate reports within 5 business days, credit you publicly (with permission) once the fix lands, and make sure the issue actually gets fixed.
If this is an active emergency — call 911.
This page is for security questions about the website. For real-world emergencies in Poway, dial 911. For PNEC-specific community support, the email below is monitored by a real volunteer.
Email PNEC
PNEC