Customer Delivery • Project Ownership • VAPT • Sign-off
Owning customer-facing work from execution through walkthroughs, remediation, and closure.
Building a good platform or running a strong assessment is one thing. Driving it through customer reality, dependencies, and sign-off is a different skill set. I’ve done both.
20+
Banking Engagements
Auditing & securing major BFSI customers.
200+
Cases Managed
Support, implementation, & project cases.
5/5 ★
Bhutan RMA Satisfaction
5-star customer rating from Bhutan's Central Bank.
100%
CSP Audit Attestation
Full compliance from 3rd-party vendors for all banking clients.
4+
Major Indian Banks
Indian Bank, IOB, TMB, City Union Bank.
4+
Customer VAPTs
Reporting, rescans, & walkthrough support.
Delivery Execution
I treat delivery work as a system. The work has a lifecycle: understand scope, align execution, perform technical work, communicate clearly, validate, document, and push toward closure.
CSP Implementation
Coordinating with customer teams to implement secure zone architectures and secure SWIFT payment message environments (e.g. Alliance Access/Gateway). Collecting evidence and driving compliance toward successful 3rd-party vendor sign-offs.
CSP Assessment
End-to-end CSCF control assessments, virtual/secure zone reviews, and evidence gap analysis. Guiding major Indian and Bhutanese banks to identify architecture gaps, support remediation, and ensure audit-ready compliance posture.
Customer VAPT Delivery
Vulnerability assessment, reporting, rescans, and post-fix verification. A VAPT report without remediation clarity is just an expensive PDF. I push for understanding, fixing, and revalidating.
Execution Discipline
200+ Cases Handled
Project delivery is also about consistently handling the long tail of support, follow-ups, scheduling issues, and implementation blockers. Cases, evidence gaps, and coordination delays are where projects either stay healthy or start to collapse. Operational follow-through is not optional.
Customer Walkthroughs
Translating technical work into clear customer-facing discussions. The goal is always the same: reduce confusion, make the next step obvious, and keep the engagement moving.
Delivery Principles I Care About
Own the work beyond the technical task
If I’m attached to an engagement, I care about the outcome, not just my isolated task in the middle of it.
Keep the customer clear on what matters
Findings, gaps, and pending actions should be understandable enough that the customer knows what to do next.
Push work toward closure
Reports, evidence, rescans, follow-up, sign-off, and closure are all part of the job, not administrative extras.
Build repeatable execution
If the same delivery pain keeps recurring, I’d rather build a workflow, template, SOP, or tool around it than keep suffering.
Explore the engineering behind the delivery
The delivery work shown here sits on top of a technical foundation: endpoint telemetry platforms, internal engineering systems, hardening validation, and VAPT.