Group 3 · Cloud security and identity

Cloud Computing · Session 14 · IE University

Cloud security and identity in financial services

Group 3

Carlos · Emile · Gabriel · Justin · Nargiz · Paul · Ritesh · Shafira · Teun

Presenting: Ritesh, Paul, Teun and Gabriel

1 · The problem

Six core problems in financial services

$6.3M average breach cost in financial services, against $4.99M across all sectors (IBM, 2026)

2 · Defence in depth

Gaps can open at every layer

3 · Our solution

Our design, piece by piece

Who connects
Identity
What they reach

4 · The choices

Seven decisions, each over a rejected option

5 · Resilience

Keeping the service running

availability of the payment path
possible downtime per year

Replication or backup?

Main databaselive data
Replicaan up-to-date copy
Immutable backuplast night's copy, cannot be changed

Replication supports continuity. Backup supports recovery.

6 · Worked example

Same blueprint, adapted to Coinbase

7 · Honest costs

What we give up, and how we limit it

Remaining risk: a stolen live session or a dishonest employee can still do limited harm, kept to one narrow role and to minutes rather than months.

8 · Over time

Contain in minutes, report on time

    100%phishing-resistant MFA for admins
    0permanent admin accounts
    0passwords stored in code
    < 1 hto contain a stolen account

    Rules behind the clock: DORA (EU, 2025) · GDPR: tell the regulator within 72 hours · PCI DSS 4.0.1: MFA on card data, logs kept 12 months

    References

    Sources

    Follow along step by step, with demos and a quiz, in the Learn section.