Case study

Case Study: Jyotipunja Phase 1 Technical Audit

Work delivered through Gurkha Technology. Where a number was not published, this page does not invent one.

Catalog: /case-studies/. Hire: packages.

The engagement

What was done

Outcomes (as published)
Written audit and training delivery. No public vulnerability list (that would be irresponsible). No invented “% risk reduction.”
Client
Jyotipunja Savings and Credit Cooperative Ltd. (named).
Industry
Savings and credit cooperative, Nepal
Location
Nepal
Timeline
Phase 1 engagement under the consulting agreement.
Team
Gurkha Technology. Cooperative IT stakeholders.

Problem

Technical operations depended on vendors and APIs. Leadership needed an independent view of SLAs and integration security before further spend — not another Facebook page.

Starting point

Structured consulting agreement for Phase 1 only.

Strategy

Audit before build: vendor SLAs, API integration security, then a training module so the internal team could operate the findings.

Implementation

Phase 1 technical infrastructure audit. SLA review. API security evaluation. Dedicated technical training for staff.

Arjan’s role

Lead consultant: audit, security review, training.

Evidence

Engagement deliverables under NDA-style constraints. Findings stay with the client.

Takeaways

What other businesses can learn

  • Audit before adding tools. Vendor SLAs decide how reliable member-facing services can be.
  • Treat every API integration as part of the security surface, especially where member or payment data flows.
  • Pair the audit with staff training so findings are acted on, not filed.
  • Phase the engagement. A defined Phase 1 lets leadership decide on further spend with evidence.

Next step

Want this for your business?

Consulting · Contact