C1B3REngage →
Status: available · Q3 engagements

Finding bugs
before attackers do

Independent consultant specializing in web pentesting, QA, AI red teaming, and prompt engineering for teams shipping software people actually trust.

OPERATORC1B3R
EXPERIENCE15+ Years
DISCIPLINESSecurity · QA · AI
BASERemote / EMEA
§ 01 — Services

Five disciplines. One operator.

I work solo or embed with your team. Fixed-scope engagements or retainers.

01

Web Pentesting

Manual testing against the OWASP methodology — reconnaissance, exploitation, and a clear report with remediation steps your team can act on.

  • →Pentest reports
  • →Risk register
  • →Remediation roadmap
02

QA & Security Testing

Functional and security coverage in a single engagement. Manual, API, and end-to-end automation built around how your release pipeline actually works.

  • →Test plans
  • →Automation scaffolds
  • →Release sign-off
03

AI Red Teaming

Adversarial evaluation of LLM-powered systems: jailbreaks, prompt injection, data exfiltration, tool abuse.

  • →Attack catalogue
  • →Severity matrix
  • →Mitigation guidance
04

Prompt Engineering

Production-grade prompts and guardrails — engineered for reliability, cost, and safety under real load.

  • →Prompt libraries
  • →Eval suites
  • →System-prompt audits
05

Bug Bounty

Independent research on public programmes, applying the same rigor as client engagements to find issues that matter.

  • →Vulnerability research
  • →PoC write-ups
  • →Responsible disclosure
§ 02 — Approach

How I work.

[Pentesting & QA]

Functional and security testing, in the same pass.

Most teams run QA and security as separate efforts. I combine them — so a broken flow and an exploitable one get caught by the same person, in the same cycle.
[AI Systems]

Treating LLM features like attack surface, not just a feature.

Prompt injection, jailbreaks, and data leakage rarely show up in a standard QA checklist. I test AI-powered features the way an attacker would try to break them.
[Reporting]

Findings a non-technical stakeholder can act on.

A vulnerability report is only useful if someone can prioritize and fix it. Every finding ships with impact, reproduction steps, and a concrete remediation path.
[Process]

Documentation as I go, not after the fact.

Test plans, coverage, and evidence are tracked throughout the engagement — so there's a clear trail from scope to sign-off, not a rushed report at the end.
§ 03 — About
C

I break things on purpose so production never has to.

For over 15 years I've worked across QA, security testing, and — more recently — AI systems evaluation. That path gave me a habit most pure pentesters or pure QA engineers don't have: I look for what's broken and what's exploitable, in the same pass.

I hold an eJPTv2 certification and a Master's in Cybersecurity & AI, and I'm currently building up independent bug bounty work alongside client engagements.

Tooling & stack
Burp SuiteOWASP ZAPNucleiPostmanPlaywrightSeleniumPyRITGarakpromptfooLangSmith
§ 04 — Engage

Got a system you
think is unbreakable?

Tell me about it. Engagements start with a 30-minute scoping call.

hello@c1b3r.com →View Services