19:I[57746,["/_next/static/chunks/bce3145d91fff1e7.js","/_next/static/chunks/886d86abc0ed7c44.js","/_next/static/chunks/ebb2f754ee7f66cd.js","/_next/static/chunks/e38fae1733eb6e6f.js","/_next/static/chunks/d404b33fe4cc24aa.js","/_next/static/chunks/6856aedf0793bae7.js","/_next/static/chunks/9152bc2b0076b174.js","/_next/static/chunks/c76bc11d03ac9728.js"],"TagPageClient"] 1a:T4a7,A few weeks ago, a friend from South Africa reached out about a company struggling with their website’s security. We set up a virtual meeting with their management and developer to understand the issue.

I proposed a full Web Application Penetration Test and Vulnerability Assessment, backed by proper documentation. I gave them a 10-working-day timeline—based on my initial review—to deliver a detailed report and Proof of Concept (PoC).

Using the OWASP Top 10, I categorized all findings and delivered the report early. We later had a Zoom session where I broke down the vulnerabilities in plain terms so management could fully understand the risks.

Key lesson:

Devs shouldn’t only focus on payment alerts (“gbagaun”)—your priority should also be protecting users and the company that trusts you.

To Developers:

How do you secure client data in your web/app projects?

To Cyber Pros:

Have you dealt with devs who ignore security? How did you address it?

Let’s share experiences. We all have a role in making the web safer.

1b:T4a7,A few weeks ago, a friend from South Africa reached out about a company struggling with their website’s security. We set up a virtual meeting with their management and developer to understand the issue.