DORA patch management
Under DORA's technical standard, Delegated Regulation (EU) 2024/1774 Article 10, financial entities must "set deadlines for the installation of software and hardware patches" with escalation when missed, and scan assets supporting critical or important functions at least weekly. No day count is fixed. DORA applies from 17 Jan 2025.
4.3 Patch windows
DORA RTS 2024/1774
| Severity | Window3143090180 days |
|---|---|
| All severities | no number set; the financial entity sets its own deadlines |
No selected framework sets a number for these rows: every window above is the site template's suggested default, and the clock starts as this section states.
Framework clauses, read 19 Nov 2026:
- DORA RTS 2024/1774: Article 10(4)(d): no number set; the financial entity sets its own deadlines
Dates and legal basis
DORA, Regulation (EU) 2022/2554, was signed on 14 Dec 2022 and "shall apply from 17 January 2025." The regulatory technical standard that carries the patch detail, Commission Delegated Regulation (EU) 2024/1774, was adopted on 13 Mar 2024 and published in the Official Journal on 25 Jun 2024. Article 10 of the standard is titled Vulnerability and patch management and sits inside the ICT security policies required by Article 9(2) of DORA.
Article 10(3) and 10(4): the patch procedure
Paragraph 3 says financial entities "shall develop, document and implement patch management procedures." Paragraph 4 lists what those procedures shall do:
| Article 10(4) | Verbatim text |
|---|---|
| (a) | "to the extent possible identify and evaluate available software and hardware patches and updates using automated tools" |
| (b) | "identify emergency procedures for the patching and updating of ICT assets" |
| (c) | "test and deploy the software and hardware patches and the updates" referred to in Article 8(2) |
| (d) | "set deadlines for the installation of software and hardware patches and updates and escalation procedures in case those deadlines cannot be met" |
The deadline is the entity's own, but the clause makes an escalation path part of the policy. A policy that sets a window and has no step for when it is missed does not meet (d).
Article 10(2): the vulnerability side
- (b) scanning: automated scans and assessments at a frequency "commensurate to the classification" of the asset and its risk profile, and "on at least a weekly basis" for ICT assets supporting critical or important functions.
- (f) prioritizing: "prioritise the deployment of patches and other mitigation measures", considering "the criticality of the vulnerability, the classification" of the asset and its risk profile.
- (g) and (h): monitor and verify the remediation of vulnerabilities, and record every detected vulnerability and its resolution.
- (c) and (d) third parties: verify that ICT third-party providers handle vulnerabilities and report at least the critical ones in a timely manner, and track the use of third-party and open-source libraries, monitoring their versions and possible updates.
Recital 12 on testing
Recital 12 of the standard says patch management "should be a crucial part of those ICT security policies and procedures that, through testing and deployment in a controlled environment, are to resolve identified vulnerabilities and to prevent disruptions from the installation of patches." So the testing step is part of the duty, not an option that a tight deadline can remove.
What a policy must write
- A patch procedure document that exists as its own procedure, not a line in a general security policy.
- Deadlines per asset class or severity set by the entity, with the rule for choosing each (criticality, asset classification, risk profile).
- An escalation procedure with owners and a time trigger for missed deadlines.
- An emergency patching procedure, stated separately from the routine one.
- Automated identification of patches where possible, and the reason when it is not.
- A weekly scan commitment for assets supporting critical or important functions, and a record of detected vulnerabilities and their resolution.
Evidence
The standard describes documents and records: the documented procedure, the deadlines, the escalation log, the weekly scan results, and the remediation tracking in (g) and (h). The competent authority's own supervisory expectations were not read. A separate emergency step is worked through in the emergency patch clause; the other frameworks sit side by side in the Patch Window Table. For the shared logic of reasonable time, see NIS2; for a fixed bar, see Cyber Essentials.
Sources
- EUR-Lex, Commission Delegated Regulation (EU) 2024/1774, Article 10 and recital 12, read 19 Nov 2026
- EUR-Lex, Regulation (EU) 2022/2554 (DORA), application date, read 19 Nov 2026
Last reviewed 19 Nov 2026