Practical security research, engineering notes and technical perspectives from the people building and securing the software organisations depend on.
What these risks actually look like inside point-of-sale systems, APIs and payment integrations — and the first check to run on each one.
Read the articleThe ten risk categories
The ten risk categories, in the order OWASP lists them. Each is assessed against the request path below.
Request path we assess
Payment engineering
M-Pesa done right: transaction verification, reconciliation and idempotent processing — so a retried callback never charges a customer twice.
Read the articleApplication security
The controls we build into business applications from the first commit, and how we verify them before release.
Explore the serviceA study of how an IoT attack vector reaches and affects Windows systems — the implementation, the analysis and the resulting security implications.
DOI 10.5281/zenodo.14886141
View publicationAttack path studied
We assess web applications, APIs and business integrations against the same practical risks we write about — and report the specific checks to make first.
Request a security assessment© Intelisav. All rights reserved.