I am Prashant Sharma, a penetration tester based in
Gwalior. I started in 2019 and have spent seven years on
offensive security — more than 300 black box and grey box engagements
across web, mobile, API, network and thick client, for clients in banking,
financial services, energy, retail and enterprise technology.
I have led testing teams and owned delivery end to end: scoping, testing,
reporting, executive debriefs and retest closure. On engagements I regularly
find and exploit SQL injection, cross-site scripting, CSRF, remote code
execution, privilege escalation, authentication bypass and business logic
flaws, then sit with the development team while it gets fixed.
The other half of it is giving back. More than 4,000
people have come through sessions I have run, and I mentor candidates
through CEH, OSCP, CRTP and CREST. Security only improves when more
people can spot the problem, so raising awareness and lending a hand to
whoever is coming up next matters as much to me as the testing does.
That is also why I build tools. Roughly three quarters of an engagement is
not testing — it is evidence, impact, remediation and report. Most
online security tools tell you what is wrong and stop there. Mine
give impact, reproduction steps, remediation and report-ready output,
because that is the part that actually costs time. Where a browser genuinely
cannot do something — enumerating TLS cipher suites, scanning ports
— the tool says so rather than pretending.