Case Study · VAPT · 2023 · INDITECH Consulting Team

Vulnerability assessment and penetration testing for an insurer

Scoped testing of the policy administration and claims platforms for a mid-market insurer — manual exploitation, evidenced findings, and remediation tracked to closure ahead of a regulatory examination.

For an insurer, the policy administration and claims platforms are where the business keeps its promises. Weaknesses there are not abstract risks: they are exposure to data loss, claim manipulation and service outage. The insurer engaged us to test both platforms properly — scoped, evidenced and repeatable — ahead of a regulatory examination cycle.

We began with a threat-informed scope rather than a scan-everything approach: the customer-facing portal, the policy administration core, the claims workflow and the integrations between them. Rules of engagement were written with the client’s IT and business owners — test windows, escalation contacts, blast-radius limits — so testing never became an incident of its own.

Manual testing, not scanner output

The assessment combined web application testing against the OWASP methodology with infrastructure review: identity and access configurations, patch levels on internet-facing middleware, network segmentation between corporate and production zones, and the service accounts that quietly connect everything. Exploitation was performed manually — chained step by step — because a finding that cannot be reproduced is an opinion, not a finding.

What emerged were the patterns that matter in this class of platform: access-control gaps between policyholder roles, session handling weaknesses on the claims portal, unpatched middleware exposed to the internet, and credentials living in configuration files long after the people who set them had left. Each finding was severity-rated, reproduced with evidence, and written up with the remediation the client’s engineers could act on the same week.

A scanner finds what it is told to look for. A tester finds what the business actually built.

We then stayed through the fix. Every remediation was retested against the original evidence, and the tracking sheet only closed when the weakness was proven gone — not when a ticket changed status. The final report paired the closed findings with a residual risk register, giving the insurer a defensible answer for its regulator and a baseline for the next test cycle.

Key takeaways

  • Threat-informed scope across portal, policy core and claims workflow
  • Rules of engagement agreed with business owners before day one
  • Manual exploitation with evidence for every finding
  • Severity-rated remediation the engineering team could act on
  • Retested to closure and handed over as a regulator-ready report

We are ready to support your business

Discuss a similar engagement