Representative scenarios of vulnerabilities commonly identified by SunuCyberSecurity, illustrating the concrete impact of regular audits.
As part of a periodic security review, a payment platform requested a mapping of its exposure beyond its web infrastructure alone — including public code repositories mentioning its name.
15 public GitHub files mentioning the platform's infrastructure, with names typical of sensitive files (.env, credentials, AWS keys) — likely left by developers in public repositories or poorly cleaned commit history.
A real secret exposed in these files (API key, database credential, cloud token) would give an attacker direct access to production systems, without even needing to probe the web infrastructure — an entry point invisible to tools that only monitor the network perimeter.
Each file was manually reviewed by the security team to confirm or rule out a real risk, and the repositories involved were audited to purge any secret still valid.
Ahead of an investor technical due diligence, a fintech startup launched a full infrastructure audit with SunuCampaign Orchestrator.
The tool discovered 4 active, undocumented subdomains, one of which exposed the server real IP address behind the CDN, bypassing WAF protection.
This exposed IP would have allowed an attacker to scan the infrastructure directly, bypassing the security protections in place.
The technical team masked the IP and closed the unused subdomains before the due diligence, reinforcing investor confidence in the product security maturity.
As part of BCEAO compliance efforts, a financial institution submitted its client portal to an in-depth penetration test.
A Log4Shell vulnerability (CVE-2021-44228) on an outdated Java component of the portal, one of the most critical flaws identified in recent years.
This vulnerability would have allowed remote code execution, opening the door to full access to the bank internal systems.
The component was urgently updated. The institution was able to present a full compliance report to its regulator, with proof of remediation.
A mobile payment provider believed it knew the full extent of its attack surface after an audit with a competing tool, which had found only 2 active subdomains. The same target was run through SunuRecon-OSINT for comparison.
19 active subdomains identified — nearly 10 times more than the competing tool — including several undocumented environments the technical team itself had forgotten about.
Every overlooked subdomain is an unmonitored entry point: an abandoned test environment, a poorly protected admin panel, a misconfigured service. You cannot secure what you don't know exists.
The client immediately acknowledged the scale of the gap and now has a complete, reliable map of its real attack surface — an essential foundation for prioritizing remediation.
As part of a combined security campaign (OSINT, network, and web), a regional bank had its entire internet-facing infrastructure audited, beyond just the web portal.
A MySQL database directly reachable from the Internet on one of the subdomains, software version included — while similar ports on the bank's other subdomains were correctly protected by access control, making this exception easy to miss without a systematic audit.
An attacker discovering this port could have attempted to connect directly to it, entirely bypassing the web application firewall and portal protections to potentially access the financial and customer data stored in the database.
The finding was escalated to the technical team as top priority; its severity was confirmed and remediation was underway without delay.