5 min read · Security Testing · Banking & Financial Services

Network and core-banking VAPT across DC–DR for a century-old Indian bank

Cybersecurity Engineering · Infrastructure & CBS VAPT

  • Burp Suite
  • Nmap
  • Nessus
  • Metasploit
  • CIS
  • OWASP

Engagement

How the work ran.

Client names and implementation details are withheld where they are not approved for publication.

Case study

Challenge

A 100-year-old Indian bank with business worth over ₹1,000 Cr required Network and Core Banking System VAPT across servers, branches and DC–DR sites — meeting RBI directives without disrupting production.

Approach

On-site and remote assessments covered internal/external networks and CBS against CIS Benchmarks and OWASP-10, with manual verification of firewalls, routers and switches alongside Burp Suite, Nmap, Nessus and Metasploit.

Engagement model

Cybersecurity Engineering · Infrastructure & CBS VAPT

Technology

Burp Suite, Nmap, Nessus, Metasploit, CIS Benchmarks, OWASP-10

Outcome

Security posture improved across DC–DR, VPN, network gear and CBS with RBI-aligned recommendations.

Industry

Banking & Financial Services

Practice

Cybersecurity Engineering

Value delivered

  • Scope included 22 DC–DR servers, 4 VPNs/firewalls, 12 routers/switches, 180 endpoints, 33 VMware hosts and the CBS application.
  • Secure VPN configuration guidance for branch connectivity.
  • Custom CBS and virtual-server checks in non-production before production hardening.
  • Technical findings mapped to RBI compliance and corporate policy.

Share

LinkedInXEmail

Related practice

Security engineered into how software is built and run.

Cybersecurity Engineering — Assessment, secure development, cloud and identity security, and response — integrated with engineering rather than bolted on.

This engagement sits inside our Cybersecurity Engineering practice. Explore the full scope, outcomes and how we usually start.

Explore Cybersecurity Engineering →

Next step

Have a similar problem — or need more clarity?

If this challenge looks like yours, book a short discovery call. If the problem is still fuzzy, we will help you name the constraint before anyone builds a large plan.

Start a conversation

Tell us whether you need software built, a release assured, or operations taken on.

Start with a 2–8 week advisory if the problem is still a choice — then a project, a named engineering team, or managed operations.