Course 17: Digital Banking, Privacy and Financial Security
Status: Published English instructional unit; independent expert review, complete translation, and live accessibility testing pending. The 60-minute core is an introduction, not a university-semester equivalent. Completion documents self-reported learning activities and an automatically scored quiz, not professional competency or identity.
Prerequisites: Basic digital literacy, budgeting and account concepts (Courses 03 and 04 recommended). Learning outcomes: (O1) compare authentication protections and their limits; (O2) analyze phishing, account takeover and recovery scenarios; (O3) evaluate permissions, data sharing and privacy tradeoffs; (O4) construct a jurisdiction-aware incident-response plan.
Core study schedule: Objectives 5 minutes · Instruction 20 minutes · Worked cases 10 minutes · Application 15 minutes · Assessment 10 minutes. Additional reading and written work may take longer.
Stage 1 · Objectives and prerequisites (5 minutes)
Digital banking includes online accounts, mobile applications, cards, payment credentials and financial-data connections. Explain in plain language the difference between verifying identity, authorizing a payment and recovering an account. List two financial accounts or fictional accounts and identify their recovery dependencies without entering any real credentials here.
Stage 2 · Substantive instruction (20 minutes)
1. Security as a chain, not a single password
Authentication establishes that a person or device is permitted to access an account. Authorization determines which action is allowed; transaction monitoring and recovery address failures after access. A strong password alone cannot prevent an authorized customer from being tricked into sending money. A second factor reduces some account-takeover risks, but SMS codes can be exposed through SIM swapping, phishing or device compromise. Passkeys using cryptographic origin binding can resist many fake-site credential attacks; their protection depends on device security, recovery design and service support. Prefer phishing-resistant authentication when supported, unique passwords, protected recovery channels and timely security updates. Avoid claiming that any method eliminates risk.
2. Threat modeling and payment irreversibility
Map assets (balances, personal information, payment authority), actors (customer, institution, attacker), entry points (email, QR codes, phone, app permissions), and consequences. In a phishing example, an attacker impersonates a bank, creates urgency and requests a one-time code. The correct response is not to reply or call the supplied number; instead independently navigate to the institution using a trusted channel. If payment instructions change unexpectedly, independently verify with the recipient using previously established contact information. Some authorized transfers are difficult to reverse; dispute rights differ by payment method and country.
3. Privacy and consent
Financial-data aggregators may access account transactions to power budgeting, lending or payments. Assess what data is requested, purpose, retention, onward sharing, security practices, revocation method and consequences of refusing consent. Revoking an app permission may not delete information already collected; read provider policy and applicable law. Data minimization means giving only necessary access. A legitimate app can still pose excessive privacy risk if it retains sensitive histories unnecessarily. The EU General Data Protection Regulation gives certain data-subject rights in its scope; it does not apply universally. Local banking secrecy, consumer privacy and open-banking frameworks differ.
4. Incident response and recovery
If you suspect compromise, use a known-good device to contact the institution through its independently verified official channel; ask to freeze affected instruments and report unauthorized activity. Change credentials and recovery factors, review recent transactions and connected apps, document times and case numbers, and report relevant identity theft or fraud to competent local authorities. Preserve evidence without sharing credentials. If a phone is lost, revoke sessions and contact the carrier about SIM protection. Reporting deadlines, reimbursement and liability depend on jurisdiction, transaction type and facts; consult current official rules rather than assuming a universal guarantee.
5. Design for access and inclusion
Security controls can exclude people who share devices, have intermittent connectivity, lack government identification or use assistive technologies. Compare offline recovery, accessible support and secure alternatives rather than prescribing a single technology to everyone. A recovery process that depends solely on a lost phone can be a single point of failure. Balance security with feasible access.
Stage 3 · Worked cases (10 minutes)
Case A: Compare hypothetical fraud exposure
A fictional service experiences 40 attempted account compromises per 10,000 accounts annually. Assume 25% succeed without stronger protection and 5% succeed with phishing-resistant authentication. Expected successes: 40 × .25 = 10 versus 40 × .05 = 2 per 10,000, an illustrative difference of eight. These probabilities are assumptions, not measured efficacy or a prediction. Changing the attack mix can change the comparison.
Case B: Data sharing
A budgeting app requests 24 months of transactions for a monthly spending chart. Suppose a household makes 50 transactions monthly: 24 × 50 = 1,200 records exposed versus 3 × 50 = 150 if three months suffice. The reduction is 1,050 records or 87.5%. Record count is not itself a privacy-risk score: sensitivity, retention and onward transfers matter more than volume alone.
Case C: Recovery time and adverse scenario
A customer discovers an unfamiliar transfer at 08:00, reports it at 08:25 and obtains a case reference at 08:40. The detection-to-report interval is 25 minutes. An adverse scenario is loss of the customer's phone and email simultaneously: both SMS and email recovery fail. A resilient plan includes independently stored official contact details and a separate secured recovery method. No example establishes legal reimbursement eligibility.
Stage 4 · Interactive application (15 minutes)
Hypothetical threat-exposure model
This model compares assumed incident counts, not actual security performance. Set attempted incidents per 10,000 accounts and assumed success percentages. Do not enter personal financial data.
Graduated problems and solutions
Problem 1 · Recognize the attack
A caller claiming to be your bank requests a login code to cancel fraud. What is the safest next action?
Answer guidance: End the call and contact the bank independently using an official number or authenticated app; never supply a code to an unsolicited caller.
Problem 2 · Analyze consent
An app needs three months of spending information but requests full account history and indefinite retention. Compare options.
Answer guidance: Request narrower access, inspect retention and revocation terms, or decline. The convenience benefit must be weighed against scope and sensitivity.
Problem 3 · Recovery stress test
Your phone and email are unavailable. Explain how you would contact the institution and prove account control without sharing secrets.
Answer guidance: Use independently stored official contact information, alternative recovery credentials and the institution's identity-verification process; identify where the plan might fail.
Written security-plan project
Write a 400–650-word security and recovery plan for a fictional household using two digital financial services. Provide an asset/threat table, a comparison of authentication options and their limitations, a data-permission decision, a lost-device plus suspicious-transfer incident timeline, and a jurisdiction-specific official reporting route with source date. Include a counterexample where a security measure obstructs accessibility or recovery, and propose an alternative.
Self-assessment rubric (20 points): threat model and mechanism accuracy 0–5; authentication comparison and limitations 0–4; data rights and privacy reasoning 0–4; actionable recovery sequence and official local sources 0–5; accessibility and uncertainty 0–2. This written project is self-assessed; no automatic essay-quality evaluation occurs.
Stage 5 · Assessment (10 minutes)
Ten questions map to outcomes O1–O4. Review explanations and retake as necessary. A minimum 8/10 score plus five stage acknowledgments and self-reported written work enables a locally generated non-accredited completion record. No timer proves learning.
No identity verification, accreditation or independent assessment of written quality.
Sources and annotated reading
NIST SP 800-63B, Authentication and Authenticator Management — technical guidance on authenticator assurance and phishing resistance; US federal framework, not universal consumer law.
CISA Secure Our World — practical security hygiene and phishing guidance; general education, not a reimbursement determination.
US Consumer Financial Protection Bureau, fraud resources — US-specific consumer information; check product and transaction scope before applying a remedy.
European Commission, data-protection rights — authoritative explanation of GDPR rights within scope; not a worldwide privacy regime.
World Bank, financial inclusion — context on access barriers; country implementation and evidence vary. Consult current local banking regulator, privacy authority and institution terms for actual rules.
Optional extension: Compare the incident-reporting and data-access rules of two named jurisdictions, citing each official regulator. The one-hour core is not a full academic course or professional certification.