Back to Projects

Secured Software Systems

2026

Secure Banking Authentication

A secure sign-in system for a fintech portal, taken from threat modelling and risk assessment to a secure design, working code built to the OWASP ASVS standard, and security testing.

  • Team of 4

Project Files 2

What I learned

The challenge

Making sign-in hard to attack without making it hard to use: each control, from input validation and salted password hashing to two-step verification and rate limiting, had to answer a specific threat from our risk analysis.

The experience

I led a team of four through a full secure development cycle, from threat modelling to working code and security testing.

Skills I developed

  • Threat modelling (STRIDE)
  • Risk assessment
  • OWASP ASVS
  • Secure coding
  • Security testing
  • Team leadership

01The problem

Banking and fintech systems hold highly sensitive personal, biometric and financial data, which makes them prime targets for attackers.

The challenge in the second assignment was to keep sign-in and access control secure without making them hard to use.

02What the team built

  • Assignment 1: a cyber security threat assessment of a proposed mobile banking app with biometric authentication, covering its assets, trust boundaries, data flows and stakeholders
  • Assignment 2: the secure development of the user authentication and authorization component of a fintech customer portal, from threat modelling to security testing

03Software engineering process

  1. Security

    Threats identified with the STRIDE framework (12 major threats, such as account takeover), rated for likelihood and impact, and prioritised in a risk assessment matrix with mitigation strategies.

  2. Design

    A secure architecture applying security design principles such as fail-safe defaults, complete mediation and separation of duties, with separate services for authentication, MFA, sessions and audit logging.

  3. Implementation

    Working source code with a Git commit history, implementing security requirements from the OWASP ASVS 5.0 standard.

  4. Testing

    A security test plan combining static and dynamic security testing (SAST and DAST), functional testing and abuse-case testing, with recorded evidence.