Assessment practice
Professional work includes web application and backend API penetration testing across AgriTech, Road Asset, Bridge Management and Employee Management platforms. Testing combines manual validation with structured evidence collection and CVSS-based reporting.
Recurring security themes
- Broken object-level authorization and IDOR.
- Authentication bypass and unauthenticated API exposure.
- JWT signing-secret and token-lifetime weaknesses.
- Misconfiguration and sensitive information disclosure.
- CSRF, CORS and missing rate-limiting controls.
- Exposed infrastructure services and debug endpoints.
Selected verified examples
Reported issues included a publicly exposed Redis instance, Django DEBUG information leakage, hardcoded JWT secrets, a time-of-check/time-of-use authentication bypass, and missing authorization on messaging endpoints. Details that could identify client systems or enable exploitation are intentionally excluded from this public summary.
Reporting workflow
- Confirm written scope and test boundaries.
- Enumerate the application and API attack surface.
- Manually validate suspected vulnerabilities and assess impact.
- Capture reproducible, sanitized evidence.
- Assign CVSS severity and explain business impact.
- Provide remediation guidance and retest fixes.
Across 7+ client projects, 258 vulnerabilities were reported and 1,433 pages of technical reports delivered. Figures are based on the November 2026 resume.