How DORA’s Article 9 Shapes Credential Management for Financial Firms

· Original article ↗

Summary

A sponsored Passwork article explains how DORA Article 9 applies to credential controls, recommending phishing-resistant MFA, least privilege, credential vaulting and continuous monitoring, then promotes Passwork’s self-hosted password manager and audit features.

Key points

  • The article says DORA Article 9(4)(c) requires limiting access to legitimate, approved functions, while Article 9(4)(d) addresses strong authentication and cryptographic key protection.
  • It recommends FIDO2/WebAuthn-based phishing-resistant MFA, particularly for privileged accounts and remote access, rather than SMS or TOTP alone.
  • Other recommended controls include just-in-time privileged access, prompt account deactivation, encrypted credential vaulting and alerts for anomalous logins.
  • The article cites the January 2026 Ficoba registry incident, in which a threat actor reportedly used one civil servant’s credentials to access data on 1.2 million bank accounts.
  • It describes the 2024 Santander incident as involving credentials stolen from Snowflake employees and notes that the accessed accounts lacked MFA.
  • Passwork's claims about self-hosted deployment, MFA, access controls and tamper-evident audit logs are presented in sponsored product material.

Article Details

Defense Focus
Reduce credential-based compromise and support DORA compliance through phishing-resistant authentication, least-privilege access, secure credential storage, continuous monitoring, and auditable records.
Detection Methods
  • Alert on anomalous login behavior, including unusual geolocations and off-hours access.
  • Monitor for lateral-movement patterns.
  • Record and review credential access, permission changes, password resets, and sharing events.
Data Sources
  • Authentication and login activity, including geolocation and access time
  • Credential and access-control audit logs
  • SIEM-integrated activity records
Platforms
  • SIEM systems
Defensive Actions
  • Enforce phishing-resistant MFA, particularly for privileged accounts and remote access.
  • Apply least privilege; use just-in-time elevation and promptly deactivate dormant or offboarded accounts.
  • Store service-account passwords, API keys, and privileged credentials in an encrypted, access-controlled vault.
  • Monitor continuously and configure automated alerts for anomalous logins and lateral-movement patterns.
  • Maintain tamper-evident, exportable audit records for credential and permission activity.
  • Require equivalent authentication standards from critical ICT providers and audit their compliance.

MITRE ATT&CK

Malware

Vendors

Products

Countries

Industries

Related Articles