Security testing, done in the open

I am Nick Bean, an independent security tester based in Alabama. I do authorized, scoped security work and I document it. Every engagement starts with written authorization and a scope, and ends with a report that separates what was observed from what was confirmed.

Status, stated plainly: This practice is new. The business entity (A Bean Consult, LLC, Alabama, registered July 2024) was dormant until now and has no clients yet. I hold no offensive-security certifications yet; I am preparing for them. I am not yet accepting paid client engagements. Early engagements are by invitation, with written authorization.

What I can help with

How an engagement works

  1. Scope and authorization — a written letter from someone with authority over the systems, exact targets, time window, and a stop list.
  2. Rules of engagement — request limits, allowed methods, a contact for emergencies.
  3. Testing — only inside the written scope; evidence is captured and secrets are redacted.
  4. Report — findings with reproduction steps, impact, and remediation; observations are kept separate from confirmed vulnerabilities.
  5. Retest — a follow-up check after fixes.

What I will not do

Evidence, not claims

See the lab write-up, the redacted sample report from a self-assessment of this very site, and the research log. Vulnerability reports about my own systems are welcome under the disclosure policy.

weneedthebeans is a brand of A Bean Consult, LLC, an Alabama limited liability company.

Last updated: November 20, 2026 · Nick Bean · [email protected]