Mar 10, 2026 · 12 min read
OWASP Top 10 in Practice: A Developer's Guide for Sri Lankan Software Teams
How the OWASP Top 10 maps to real Sri Lankan software projects — and what teams should actually do differently in daily development.
CodeLK Engineering

The OWASP Top 10 is not a compliance checklist — it is a map of how real applications fail in production. Sri Lankan software teams working in banking, healthcare, and enterprise software encounter every category on this list regularly. Understanding them as a developer, not just as a security auditor, is what separates teams that prevent vulnerabilities from teams that fix them after disclosure.
The three that matter most for enterprise and fintech
Injection (A03) remains the most destructive in regulated financial applications — not just SQL injection in form fields, but second-order injection in batch processing and stored procedure calls where inputs arrive from trusted but unvalidated upstream systems. ORM-parameterised queries are necessary but not sufficient when stored procedures accept raw string concatenation.
Broken Access Control (A01) is the top OWASP risk for a reason. In multi-tenant SaaS and banking platforms, the gap is often not missing authentication but missing authorisation checks on API endpoints that developers assumed "only the UI would call." Direct object reference exploits — incrementing a loan ID or account number in an API call — bypass UI controls entirely.
Cryptographic Failures (A02) in Sri Lankan enterprise software most commonly manifest as MD5 or SHA-1 password hashing still active in legacy codepaths, self-signed certificates accepted in API integrations for "convenience," and session tokens transmitted over HTTP on internal networks assumed to be safe.
What secure SDLC actually looks like day-to-day
- Static analysis (SAST) tools run in CI on every pull request — not as a gate that blocks all deploys but as a review signal developers learn to act on.
- Secrets scanning in Git pre-commit hooks and repository scans prevents API keys and database passwords from being committed and later exfiltrated.
- Dependency vulnerability scanning (SCA) with tools like Snyk or OWASP Dependency-Check runs on the build pipeline; critical CVEs block release.
- Threat modelling for new features — a 30-minute session asking "who can abuse this, what can they do, and what controls prevent it" — catches design flaws before implementation.
Penetration testing: when and how
Penetration testing should be scoped, not broad. A fintech team shipping every two weeks benefits more from targeted API security reviews aligned to new feature surfaces than from annual black-box tests that produce 80-page PDFs nobody reads before the next release cycle. Work with testers who understand your domain — a banking API tester who knows CBSL reporting endpoints and mobile banking authentication flows will find higher-impact findings.
Embed SAST, secrets scanning, and SCA in your CI pipeline this sprint. That alone addresses the majority of OWASP Top 10 categories at the point where fixing is cheapest: before merge.


