DNB Good Practice Information Security
What De Nederlandsche Bank expects of the financial institutions it supervises.
Updated
DNB's good practice sets out a control framework for information security at Dutch banks, insurers, pension funds and payment institutions, and is the basis of its periodic assessments.
It is aligned with the EBA Guidelines on ICT and security risk management and, since DORA applies, with DORA. Institutions are asked to self-assess their maturity against it and to substantiate the scores with evidence.
Who needs it
Banks, insurers, pension funds, payment and e-money institutions, trust offices and other financial institutions under DNB supervision, and the ICT providers whose controls they rely on.
From maturity scores to configuration
DNB scores controls on a maturity scale and expects at least level 3, meaning defined, documented and operating controls, for most of them. For cloud infrastructure the relevant controls are logical access management, network security, cryptography, logging and monitoring, change management, and outsourcing and cloud governance. A score has to be backed by evidence that the control works in your environment.
Cloud outsourcing under DNB
DNB expects institutions to stay in control of outsourced and cloud services: a current overview of what runs where, risk assessments, and the ability to demonstrate that security measures are effective. A continuous review of your cloud accounts with a dated record is exactly that demonstration.
What DNB asks of your cloud
The control areas that map onto infrastructure configuration in AWS, Google Cloud and Azure.
Logical access management
User and privileged access on a need-to-have basis, periodic access reviews, and strong authentication.
Network and infrastructure security
Segmentation, hardened configurations, and controlled connections from untrusted networks.
Cryptography
Encryption of sensitive data at rest and in transit, with managed keys.
Logging and monitoring
Security event logging across systems, retained and monitored, supporting incident detection.
Change management
Changes to infrastructure authorised, tested and traceable.
Outsourcing and cloud
Oversight of cloud and ICT providers, including an overview of services and evidence that their controls are effective.
How AKRIBOS checks DNB
Mapped to your resources
Every DNB control is evaluated against the actual accounts, roles, networks and storage in your estate, with the setting behind each result.
Findings come with the fix
A failing control is shown with the exact change as CLI commands or Terraform. You review and approve; nothing is applied on its own.
Evidence over time
Scheduled reviews and a full audit trail give you a dated record of each control for the whole audit period, not just the day of the audit.
Common issues under DNB
Misconfigurations that fail DNB controls, with the control reference for each.
Storage bucket open to the internet
CriticalObject storage that anyone can list or read, usually from a permissive ACL, bucket policy or account-wide setting that was never switched on.Logical access management; data classification.
Read moreRoot or owner account without MFA
CriticalThe most privileged identity in the account protected by a password alone.Logical access management (privileged access, strong authentication).
Read moreDatabase reachable from the internet
CriticalA managed database with a public address and a firewall that lets the world in.Network security; logical access management.
Read moreSnapshots or machine images shared publicly
CriticalDisk snapshots, database snapshots or machine images that anyone with a cloud account can copy.Data classification; logical access management.
Read moreOver-permissive IAM policies
HighIdentities, often service accounts, that can do anything in the account because a wildcard or a basic role was easier than a scoped policy.Logical access management (need-to-have, periodic reviews).
Read moreSSH or RDP open to 0.0.0.0/0
HighManagement ports reachable from any address on the internet.Network security (controlled connections from untrusted networks).
Read moreAudit logging incomplete
HighGaps in the record of who did what: missing regions, missing data-access events, or logs that can be altered.Logging and monitoring.
Read moreLong-lived or unused credentials
HighAccess keys, service account keys and client secrets that never rotate and are no longer needed.Logical access management (joiner-mover-leaver, credential management).
Read moreInstance metadata without session tokens
HighCompute instances that answer metadata requests, including their temporary credentials, to any process that can reach the local metadata address.Infrastructure security (hardening); vulnerability management.
Read moreTrust policies open to any account
HighRoles or bindings that let identities outside your organisation assume access, often for a vendor integration that was set up too generously.Outsourcing and cloud; logical access management.
Read moreData at rest without the encryption you intended
MediumVolumes, snapshots or databases created without encryption, or without the customer-managed keys your policy requires.Cryptography.
Read moreTransport encryption not enforced
MediumEndpoints that still accept plaintext or outdated TLS, even though an encrypted path exists.Cryptography; network security.
Read moreNetwork flow logs off
MediumNo record of which addresses talked to which, so traffic to and from a compromised host cannot be reconstructed.Logging and monitoring.
Read moreDefault network with permissive rules
MediumWorkloads running in the cloud-created default network, which ships with rules nobody would write deliberately.Network security.
Read moreDNB questions
Is the DNB Good Practice mandatory?
It is guidance rather than law, but DNB uses it as the basis for its assessments and self-assessment requests, and it is aligned with the binding EBA Guidelines and DORA. Treating it as the standard is the practical choice.
Which maturity level does DNB expect?
DNB generally expects at least maturity level 3 on its scale, with documented, implemented and effective controls, and higher for institutions with greater risk.
How does it relate to DORA?
DORA now sets the binding requirements for financial entities; the Good Practice is DNB's operational view of what good looks like and has been aligned with DORA. Evidence for one serves the other.
Other frameworks
CIS Benchmarks
The baseline configuration standard for AWS, Google Cloud and Azure.
Read moreSOC 2
Evidence that your cloud controls work, not just that they exist.
Read moreISO/IEC 27001
The international standard for an information security management system, applied to your cloud.
Read moreDORA
The EU Digital Operational Resilience Act, applied to the cloud behind your financial services.
Read moreNIS2
EU-wide cyber risk-management obligations for essential and important entities.
Read morePCI DSS v4
Requirements for every environment that stores, processes or transmits cardholder data.
Read moreNIST CSF 2.0
The US framework of outcomes: Govern, Identify, Protect, Detect, Respond, Recover.
Read moreBSI C5
Germany's cloud computing compliance criteria catalogue.
Read moreAttackers don't wait for your next audit. Neither does AKRIBOS.
Connect AWS, Google Cloud or Azure and get your first review today.
