DORA EU Digital Operational Resilience Act for financial entities
- version
- 0.1.0
- GitHub stars
- 436
Install
/plugin install dora@grc-engineering-suiteRun it inside Claude Code after adding the marketplace with /plugin marketplace add GRCEngClub/claude-grc-engineering.
Contents
Discovered from sourceSkills 1
DORA Expert
Deep expertise in Digital Operational Resilience Act (DORA) for EU financial entities and ICT third-party service providers.
Expertise Areas
DORA Regulation Overview
Regulation: EU Regulation 2022/2554 on Digital Operational Resilience for the Financial Sector Publication: December 14, 2022 Effective Date: January 17, 2025 Objective: Harmonize ICT risk management across EU financial sector Enforcement: National competent authorities (NCAs) and European Supervisory Authorities (ESAs)
Key Innovation: First comprehensive EU-wide framework specifically addressing digital operational resilience in financial services
Scope and Applicability
Financial Entities Subject to DORA:
- Credit institutions (banks)
- Payment institutions and e-money institutions
- Investment firms
- Crypto-asset service providers (CASPs) under MiCA
- Central securities depositories (CSDs)
- Central counterparties (CCPs)
- Trading venues (MTFs, OTFs)
- Trade repositories
- Managers of UCITS and AIFs
- Insurance and reinsurance undertakings
- Insurance intermediaries, reinsurance intermediaries, ancillary insurance intermediaries
- Institutions for occupational retirement provision (IORPs)
- Credit rating agencies
- Administrators of critical benchmarks
- Crowdfunding service providers
- Securitization repositories
ICT Third-Party Service Providers:
- Cloud service providers
- Software providers
- Data analytics providers
- Data centers
- Any provider of ICT services supporting critical or important functions
Geographic Scope:
- All EU member states
- Applies to entities operating in EU
- Extraterritorial effect for third-party providers serving EU financial entities
Why DORA Matters
Industry Drivers:
- Increasing cyber threats targeting financial sector
- Growing dependence on ICT and third-party providers
- Cloud concentration risk
- Operational disruptions with systemic impact
- Fragmented national approaches pre-DORA
Regulatory Response:
- Harmonized requirements across EU
- Enhanced oversight of critical third-party providers
- Mandatory incident reporting
- Regular resilience testing
- Board-level accountability
Business Impact:
- Significant compliance investment required
- Contract renegotiations with ICT providers
- Enhanced governance and risk management
- Potential competitive advantage for compliant entities
- Regulatory penalties for non-compliance
DORA's 5 Pillars
Pillar 1: ICT Risk Management (Articles 5-16)
Objective: Establish comprehensive, board-approved ICT risk management framework
Governance Requirements (Article 5)
Management Body Responsibilities:
- Define, approve, and oversee digital operational resilience strategy
- Approve and oversee ICT risk management framework
- Allocate appropriate budget and resources
- Ensure at least one member with sufficient ICT knowledge
- Maintain clear roles and responsibilities
- Establish reporting lines for ICT risks
- Receive regular reporting on ICT risk profile
Documentation:
- ICT strategy document
- ICT risk management policy
- Board minutes approving framework
- Skills and training matrix for board members
ICT Risk Management Framework (Article 6)
Framework Components:
-
Strategies, Policies, Procedures:
- ICT risk management strategy
- ICT security policies
- ICT operations procedures
- Risk assessment methodology
- Risk treatment procedures
-
ICT Risk Management Function:
- Dedicated function with sufficient resources
- Reporting to management body
- Independence from IT operations (where feasible)
- Clearly defined responsibilities
-
Documentation and Reporting:
- Written framework document
- Risk registers
- Risk assessments
- Risk treatment plans
- Management reporting
Proportionality Principle:
- Framework complexity proportionate to entity size
- Smaller entities may adopt simplified approaches
- Risk-based tailoring of requirements
- Supervisory expectations vary by significance
Identification (Article 8)
Asset Management:
- Inventory of all ICT assets
- Hardware, software, network components
- Cloud services and SaaS applications
- ICT-supported business functions
- Data assets and flows
Business Impact Analysis (BIA):
- Identify critical and important functions
- Map ICT dependencies
- Assess impact of disruptions
- Determine recovery time objectives (RTO)
- Determine recovery point objectives (RPO)
Dependency Mapping:
- Internal system interdependencies
- Third-party dependencies
- Data flows (internal and external)
- Critical supply chains
Deliverables:
- ICT asset register
- Business impact analysis report
- Dependency maps
- Data flow diagrams
- Network architecture diagrams
Protection and Prevention (Article 9)
Security Policies:
- Information security policy
- Access control policy
- Cryptography policy
- Secure development policy
- Physical security policy
Technical Controls:
-
Identity and Access Management:
- Multi-factor authentication (MFA)
- Privileged access management (PAM)
- Least privilege principle
- Regular access reviews
- Strong password policies
-
Encryption:
- Data at rest encryption
- Data in transit encryption (TLS 1.2+)
- Key management procedures
- Cryptographic standards compliance
-
Network Security:
- Network segmentation
- Firewalls and DMZs
- Intrusion prevention systems (IPS)
- DDoS protection
- Secure remote access (VPN, zero trust)
-
Endpoint Protection:
- Anti-malware solutions
- Endpoint detection and response (EDR)
- Host-based firewalls
- Device encryption
- Mobile device management (MDM)
-
Patch Management:
- Timely patching of vulnerabilities
- Patch testing procedures
- Emergency patching process
- Asset inventory for patch tracking
-
Data Loss Prevention (DLP):
- DLP tools and policies
- Monitoring of data exfiltration
- USB/removable media controls
- Email and web filtering
Awareness and Training:
- Regular security awareness training for all staff
- Role-based training for IT/security personnel
- Phishing simulations
- Incident response training
- Annual refresher training
Physical and Environmental Security:
- Data center access controls
- Environmental monitoring (temperature, humidity)
- Fire suppression systems
- Uninterruptible power supplies (UPS)
- Physical security monitoring (CCTV)
Detection (Article 10)
Continuous Monitoring:
- 24/7 monitoring of critical systems (for significant entities)
- Security information and event management (SIEM)
- Log aggregation and analysis
- Real-time alerting
- Anomaly detection
Detection Capabilities:
- Intrusion detection systems (IDS)
- Network traffic analysis
- User behavior analytics (UBA)
- Threat intelligence integration
- File integrity monitoring
Logging Requirements:
- Comprehensive logging of security events
- Log retention (typically 6-12 months minimum)
- Secure log storage
- Log review and analysis
- Audit trails for privileged actions
Metrics and KPIs:
- Time to detect (TTD)
- Mean time to detect (MTTD)
- False positive rates
- Alert coverage
- Detection effectiveness
Response and Recovery (Article 11)
Business Continuity Planning:
- Business continuity policy
- Business continuity plans (BCPs) for critical functions
- Disaster recovery plans (DRPs) for ICT systems
- Crisis management procedures
- Communication plans
Recovery Objectives:
- Recovery Time Objective (RTO): Maximum acceptable downtime
- Recovery Point Objective (RPO): Maximum acceptable data loss
- Defined for each critical/important function
- Documented and tested
Incident Response:
- Incident response plan
- Incident response team and roles
- Incident classification procedures
- Escalation procedures
- Containment and eradication procedures
- Recovery procedures
- Post-incident review process
Backup and Restoration:
- Regular backups of critical data and systems
- Backup frequency aligned with RPO
- Offsite backup storage
- Immutable backups (ransomware protection)
- Regular restoration testing
- Backup integrity verification
Testing Requirements:
- Annual testing of BCPs/DRPs (minimum)
- Tabletop exercises
- Simulation exercises
- Full failover tests (where feasible)
- Documentation of test results
- Remediation of gaps identified
Learning and Evolving (Article 12)
Post-Incident Reviews:
- Mandatory for all major incidents
- Recommended for significant non-major incidents
- Root cause analysis
- Timeline reconstruction
- Lessons learned documentation
- Corrective action tracking
Continuous Improvement:
- Regular review of ICT risk framework
- Updates based on lessons learned
- Incorporation of new threats
- Technology evolution
- Regulatory changes
Metrics and KPIs:
- Incident frequency and severity
- Mean time to respond (MTTR)
- Mean time to recover (MTTR)
- Patch compliance rates
- Training completion rates
- Audit findings closure rates
Communication (Article 13)
Internal Communication:
- Clear communication channels during incidents
- Stakeholder notification procedures
- Status update protocols
- Escalation communication
External Communication:
- Client communication during disruptions
- Media relations protocols
- Regulatory communication (incident reporting)
- Third-party provider communication
Crisis Communication:
- Crisis communication team
- Pre-approved messaging templates
- Spokesperson designation
- Media handling procedures
Pillar 2: ICT-Related Incident Management & Reporting (Articles 17-23)
Objective: Detect, manage, classify, and report ICT-related incidents to authorities
Incident Management Process (Article 17)
Detection:
- Continuous monitoring systems
- User reporting mechanisms
- Automated alerting
- Threat intelligence feeds
Management Process:
- Detection and Logging: Incident identified and logged
- Assessment: Initial impact and classification
- Containment: Stop spread of incident
- Investigation: Root cause analysis
- Eradication: Remove cause of incident
- Recovery: Restore services and data
- Post-Incident Review: Lessons learned
- Reporting: To authorities if major incident
Incident Response Plan Elements:
- Roles and responsibilities (incident response team)
- Communication procedures
- Technical response procedures
- Decision-making authority
- Escalation criteria
- Evidence preservation
- Reporting procedures
Major Incident Classification (Article 18)
Classification Criteria:
An incident is major if it meets one or more of these:
-
Impact on Services:
- Critical or important functions significantly impacted
- Large number of clients unable to access services
- Transaction processing severely disrupted
- Duration exceeds established thresholds
-
Geographical Spread:
- Multiple EU member states affected
- Cross-border service disruption
-
Data Loss/Corruption:
- Loss of data critical to service delivery
- Corruption of financial records
- Integrity of transactions compromised
-
Reputational Impact:
- Significant media attention
- Public confidence affected
- Market impact on entity
-
Economic Impact:
- Direct financial losses exceed materiality thresholds
- Significant operational costs
- Client compensation required
Classification Decision:
- Use documented criteria and thresholds
- Involve senior management and risk/compliance
- When in doubt, classify as major (can downgrade later)
- Document classification rationale
- Re-assess if incident evolves
Entity-Specific Thresholds:
- Defined based on entity size, complexity, risk profile
- Approved by management body
- Aligned with business impact analysis
- Reviewed annually
Mandatory Reporting Timeline (Article 19)
| Timeframe | Report | Required Information |
|---|---|---|
| 4 hours | Initial notification | Incident awareness, preliminary classification, affected systems, initial impact |
| 72 hours | Intermediate report | Detailed classification, actual impact, root cause (if known), mitigation actions |
| 1 month | Final report | Comprehensive analysis, definitive root cause, remediation, lessons learned, preventive measures |
Reporting Channels:
- To relevant national competent authority (NCA)
- Via designated single point of contact
- Using standardized templates (technical standards under development)
- Electronic submission (secure portal or encrypted email)
Significant Updates:
- Required when material changes to impact assessment
- Discovery of additional affected systems/data
- Incident evolves or escalates
- Timeline for updates: As soon as reasonably practicable
Cross-Border Incidents:
- Report to home member state NCA
- NCA coordinates with other affected member states
- May require parallel notifications (follow NCA guidance)
Voluntary Notification (Article 20)
Cyber Threats:
- Financial entities may voluntarily report cyber threats
- Significant vulnerabilities discovered
- Attempted attacks (even if unsuccessful)
- Threat intelligence about targeting
Benefits:
- Helps collective defense
- Supports threat landscape understanding
- Liability protection for good faith sharing
Process:
- Report to NCA or designated body
- Share with information-sharing communities
- No penalties for reporting
Centralized Incident Reporting (Article 21-22)
ESA Responsibilities:
- Develop single EU hub for incident reporting
- Anonymize and aggregate incident data
- Analyze trends and patterns
- Identify systemic risks
- Publish annual reports on incidents
Financial Entity Benefit:
- Insights into sector-wide threats
- Benchmarking against peers
- Early warning of emerging risks
Pillar 3: Digital Operational Resilience Testing (Articles 24-27)
Objective: Regular testing to ensure systems withstand ICT disruptions
General Testing Requirements (Article 24)
Mandatory Testing Types:
-
Vulnerability Assessments and Scans:
- Quarterly for critical systems
- Annual minimum for all systems
- Automated and manual testing
- Remediation of findings
-
Open-Source Analysis:
- Software composition analysis
- Identification of known vulnerabilities in dependencies
- License compliance
-
Network Security Assessments:
- Firewall configuration reviews
- Network segmentation validation
- Intrusion detection effectiveness
-
Gap Analyses:
- Against DORA requirements
- Against industry standards (ISO 27001, NIST)
- Control maturity assessments
-
Physical Security Reviews:
- Data center walkthroughs
- Access control testing
- Environmental controls validation
-
Questionnaires and Scanning Software:
- Self-assessments
- Configuration scans
- Compliance checklists
-
Source Code Reviews (where feasible):
- Static application security testing (SAST)
- Manual code reviews
- Secure coding standard compliance
-
Scenario-Based Testing:
- Tabletop exercises
- Simulations (ransomware, DDoS, data breach, etc.)
- Crisis management drills
-
Compatibility Testing:
- Integration testing
- API compatibility
- Cross-system functionality
-
Performance Testing:
- Load testing
- Stress testing
- Capacity validation
-
End-to-End Testing:
- Complete business process flows
- Multi-system transactions
- Data integrity across systems
-
Penetration Testing:
- External and internal networks
- Web and mobile applications
- APIs and interfaces
Testing Frequency:
- Minimum: Annual testing
- Risk-based: More frequent for critical systems
- Triggered: After significant changes, major incidents
Testing Documentation:
- Testing policy and procedures
- Test plans
- Test results and reports
- Remediation tracking
- Evidence of fixes validated
Advanced Testing - TLPT (Articles 26-27)
Threat-Led Penetration Testing (TLPT):
- Sophisticated, intelligence-led red team testing
- Simulates real-world attacks by threat actors
- Based on TIBER-EU framework or equivalent
Applicability:
- Mandatory for significant financial entities
- At least every 3 years
- May be required more frequently based on risk
TIBER-EU Framework:
- Threat Intelligence-Based Ethical Red Teaming
- Developed by European Central Bank (ECB)
- Harmonized approach across EU
- Adopted as DORA standard
TLPT Phases:
Phase 1: Preparation
- Scoping of critical functions and systems
- Threat intelligence gathering
- Scenario development based on real threat actors
- Red team selection (must be external)
- Rules of engagement
- Stakeholder preparation
Phase 2: Testing
- Red team executes attack scenarios
- Uses realistic tactics, techniques, procedures (TTPs)
- Blue team (internal) defends and responds
- White team (coordination) oversees
- Real-time monitoring and safety controls
- No actual harm to production (controlled environment)
Phase 3: Closure
- Debriefing and knowledge sharing
- Red team report with findings
- Blue team response analysis
- Remediation plan development
- Lessons learned
- Regulatory reporting to NCA
TLPT Roles:
-
Red Team: External, independent attackers
- Simulate real adversaries
- Use threat intelligence-based TTPs
- Test people, processes, technology
- Document techniques and findings
-
Blue Team: Internal defenders (unaware of timing)
- Security operations center (SOC)
- Incident response team
- Operate as usual, detect and respond
- Validate defensive capabilities
-
White Team: Coordination and oversight
- Internal staff managing process
- Ensure rules of engagement followed
- Monitor for unintended impacts
- Coordinate between red and blue
- Document process
-
Purple Team: Collaborative learning (post-test)
- Red and blue team collaboration
- Share techniques and defenses
- Identify gaps and improvements
TLPT Scope:
- Critical functions and services (per BIA)
- Crown jewel systems and data
- Key dependencies and integrations
- Third-party connections (if material)
Remediation:
- Address critical findings within 30 days
- High findings within 90 days
- Track and validate remediation
- Report to management and board
- NCA notification if required
Inherited TLPT:
- May leverage cloud provider's TLPT results
- If critical services fully outsourced
- Must verify applicability to entity's use
- Document reliance and scope
Pillar 4: ICT Third-Party Risk Management (Articles 28-30)
Objective: Manage risks from ICT service providers, especially critical providers
ICT Third-Party Risk (Article 28)
Third-Party Register:
- Mandatory register of all ICT third-party service providers
- Updated at least annually
- Submitted to NCA upon request
Register Contents:
- Provider name and contact information
- Description of services provided
- Countries where services are provided
- Data and functions supported
- Contract start and end dates
- Classification (critical vs. non-critical)
Risk Management Process:
-
Pre-Contracting:
- Due diligence on provider
- Security assessment questionnaires
- On-site visits for critical providers
- Financial stability review
- Concentration risk assessment
-
Contracting:
- Ensure DORA-mandated contract clauses
- Negotiate service levels (SLAs)
- Define audit and access rights
- Establish exit strategies
- Subcontracting controls
-
Ongoing Monitoring:
- Regular performance monitoring
- Annual security reviews
- Audit rights exercised
- Incident tracking from provider
- Contract compliance reviews
-
Exit Planning:
- Exit strategies for all critical providers
- Transition plans documented
- Data portability procedures
- Service continuity during transition
- Alternative provider identified
Concentration Risk:
- Assess dependence on single or few providers
- Identify single points of failure
- Consider systemic risk (e.g., cloud provider used by many entities)
- Mitigation strategies (multi-cloud, hybrid, exit readiness)
Key Contractual Provisions (Article 30)
Mandatory Contract Clauses:
-
Service Levels and Objectives:
- Clear SLAs with measurable metrics
- Availability targets
- Performance standards
- Response times for incidents
-
Data Location and Processing:
- Specify data storage locations (country, region)
- Specify data processing locations
- Prohibition on relocation without permission
- Compliance with data protection laws (GDPR)
-
Access and Audit Rights:
- Financial entity has access to data, systems, premises
- Competent authorities have access for inspections
- Auditors appointed by financial entity or NCA have access
- Reasonable prior notice (except emergencies)
- No cost to financial entity for regulatory access
-
Security Requirements:
- Minimum security controls specified
- Encryption standards
- Access control requirements
- Logging and monitoring
- Incident notification obligations (immediate for major incidents)
- Data breach notification (align with GDPR)
-
Termination Rights:
- Financial entity can terminate for cause (security breach, SLA failure, regulatory requirement)
- Notice periods specified
- No lock-in that prevents termination
- Survival clauses for data return/deletion
-
Subcontracting:
- Prior written consent required for subcontracting
- Flow-down of DORA provisions to subcontractors
- Visibility into subcontracting chain
- Liability remains with primary provider
-
Exit and Transition:
- Provider assistance during transition
- Knowledge transfer
- Data return in usable format
- Data deletion certification
- Service continuity until transition complete
-
Liability and Insurance:
- Liability caps reasonable and not overly limiting
- Indemnification for security failures
- Professional indemnity insurance
- Cyber insurance coverage
-
Regulatory Compliance:
- Provider acknowledgment of DORA applicability
- Cooperation with NCAs
- Provision of information for regulatory reporting
- Notification of material changes
-
Governing Law and Jurisdiction:
- EU member state law preferred
- Dispute resolution mechanisms
- Jurisdiction for enforcement
Contract Review and Renegotiation:
- All existing contracts must be updated to include DORA provisions
- Deadline: Typically within 12-24 months of DORA effective date (check regulatory technical standards for specifics)
- Priority: Critical providers first
- Document efforts to renegotiate; if provider refuses, assess alternatives
Critical ICT Third-Party Service Providers
Designation Process:
- Designated by European Supervisory Authorities (ESAs)
- Based on systemic importance criteria:
- Number of financial entities served
- Criticality of services provided
- Degree of substitutability (availability of alternatives)
- Interconnectedness with financial system
Examples of Likely Critical Providers:
- Major cloud service providers (AWS, Azure, Google Cloud)
- Core banking system vendors
- Payment processing platforms
- Critical data center operators
- Widely-used cybersecurity tool providers
Oversight Framework:
- Lead Overseer: One ESA designated as lead
- Oversight Responsibilities:
- On-site and remote inspections
- Request for information and documentation
- General investigations
- Recommendations for remediation
- Enforcement actions (fines, restrictions)
Critical Provider Obligations:
- Register with lead overseer
- Provide information upon request
- Submit to inspections and audits
- Implement recommendations from overseers
- Maintain business continuity and disaster recovery
- Report major incidents affecting financial entities
- Cooperate with oversight activities
Financial Entity Benefit:
- Reduced due diligence burden (ESA oversight provides assurance)
- Access to oversight reports (where permitted)
- Collective bargaining power through regulatory oversight
- Early warning of critical provider issues
Pillar 5: Information Sharing Arrangements (Article 45)
Objective: Enhance collective resilience through threat intelligence sharing
Information Sharing Frameworks
Participation:
- Financial entities encouraged to join information-sharing communities
- Voluntary participation
- No penalties for sharing in good faith
Types of Information Shared:
-
Cyber Threat Intelligence:
- Indicators of Compromise (IOCs): IPs, domains, file hashes
- Tactics, Techniques, Procedures (TTPs) of threat actors
- Malware analysis
- Vulnerability disclosures
-
Incident Information:
- Anonymized incident details
- Attack patterns and trends
- Lessons learned from incidents
- Effective mitigations
-
Defensive Measures:
- Security configurations
- Detection rules
- Response playbooks
- Best practices
Confidentiality and Liability Protection:
- Information shared in good faith is protected
- No liability for sharing threat intelligence
- Confidentiality of shared information maintained
- Antitrust safe harbor for security collaboration
- Exceptions: Law enforcement requests, court orders
Information Sharing Platforms
EU-Level Platforms:
-
Financial Services Information Sharing and Analysis Centre (FS-ISAC):
- Global platform with strong EU presence
- Real-time threat intelligence
- Member-only sharing
- Anonymous and attributed sharing options
-
ENISA Threat Intelligence Platform:
- EU Agency for Cybersecurity
- Sector-agnostic threat intelligence
- Open-source intelligence
- Policy and guidance
-
ESA-Coordinated Sharing:
- Incident data from centralized hub (Article 21)
- Aggregated and anonymized
- Sector-wide trends
- Early warning of systemic risks
National-Level Platforms:
-
National CERTs/CSIRTs:
- Computer Emergency Response Teams
- Incident response coordination
- National threat landscape
- Vulnerability alerts
-
Financial Sector ISACs:
- Country-specific financial sector sharing
- Regulatory coordination
- Trusted peer networks
-
NCA-Facilitated Forums:
- National competent authority roundtables
- Public-private partnerships
- Best practice sharing
Implementing Information Sharing
Steps to Participate:
-
Join Sharing Communities:
- Identify relevant platforms (FS-ISAC, national ISACs)
- Complete membership process
- Designate sharing contacts
- Establish legal agreements (NDAs, terms of use)
-
Establish Internal Processes:
- Define what information can be shared
- Approval processes for sharing
- Sanitization of sensitive data
- Receiving and acting on intelligence
-
Integrate Intelligence:
- Ingest threat feeds into SIEM
- Update firewall/IPS rules with IOCs
- Share intelligence with SOC
- Validate intelligence relevance
-
Contribute Intelligence:
- Share incidents (anonymized if preferred)
- Contribute IOCs from investigations
- Share effective mitigations
- Participate in working groups
Benefits:
- Early warning of threats targeting financial sector
- Collective defense against common adversaries
- Reduced time to detect and respond
- Learning from peers' incidents
- Enhanced situational awareness
Challenges:
- Legal and confidentiality concerns (addressed by DORA protections)
- Resource constraints (automated feeds help)
- Competitive sensitivity (anonymization helps)
- Information overload (curation and prioritization needed)
Compliance Timeline and Roadmap
Pre-Effective Date (Before January 17, 2025)
Months 1-3: Gap Assessment and Planning
- Conduct comprehensive DORA gap assessment
- Map current state to 5 pillars
- Identify critical gaps
- Develop remediation roadmap
- Secure executive commitment and budget
Months 4-6: Governance and Policy
- Establish ICT risk management framework
- Draft/update policies (ICT risk, incident response, third-party risk, testing)
- Board approval of framework and policies
- Identify board member with ICT knowledge (train or recruit)
- Define roles and responsibilities
Months 7-9: ICT Risk Management Implementation
- Complete ICT asset inventory
- Conduct business impact analysis (BIA)
- Create dependency maps and data flow diagrams
- Implement/enhance technical controls (MFA, encryption, monitoring)
- Deploy SIEM or enhance existing
- Establish 24/7 monitoring (for significant entities)
Months 10-12: Incident Management and Third-Party Risk
- Define major incident classification criteria
- Implement incident management system
- Develop incident response playbooks
- Create complete ICT third-party register
- Classify providers (critical vs. non-critical)
- Begin contract renegotiations (DORA clauses)
Months 13-15: Testing Program
- Develop digital resilience testing policy
- Conduct initial vulnerability assessments
- Perform gap analysis against DORA
- Execute scenario-based tests (tabletop exercises)
- Plan TLPT (for significant entities)
Months 16-18: Final Preparation
- Complete critical third-party contract updates
- Finalize incident reporting procedures
- Conduct dry run of major incident reporting
- Join information-sharing communities (FS-ISAC)
- Complete staff training on DORA requirements
- Board briefing on DORA readiness
Post-Effective Date (After January 17, 2025)
Ongoing Compliance:
- Continuous: ICT risk monitoring and reporting
- Immediate: Major incident reporting (4 hours, 72 hours, 1 month)
- Annual:
- General resilience testing
- Third-party register update
- ICT risk framework review
- Board reporting
- NCA submission (if required)
- Every 3 Years: TLPT (for significant entities)
- As Needed: Contract updates, policy updates, control enhancements
Regulatory Technical Standards (RTS) and Implementing Technical Standards (ITS)
ESAs Developing Standards:
- European Banking Authority (EBA)
- European Securities and Markets Authority (ESMA)
- European Insurance and Occupational Pensions Authority (EIOPA)
RTS/ITS Topics (to be finalized):
-
ICT Risk Management Framework (Article 16):
- Detailed requirements for framework
- Governance standards
- Control specifications
-
Major Incident Reporting (Article 19):
- Reporting templates and formats
- Classification thresholds
- Reporting channels
-
Harmonization of Incident Conditions (Article 18):
- Materiality thresholds for major incidents
- Consistent classification across member states
-
Oversight of Critical Providers (Articles 31-39):
- Designation criteria
- Oversight procedures
- Enforcement mechanisms
-
Testing (Article 25):
- Testing methodologies
- TLPT standards (building on TIBER-EU)
- Testing frequency and scope
Timeline:
- Most RTS/ITS expected by mid-2024 to late 2024
- Allow financial entities time to implement before Jan 2025
Monitoring:
- Watch ESA websites for consultations and final standards
- Participate in industry consultations
- Update compliance programs as standards finalized
Penalties and Enforcement
Administrative Fines
Maximum Penalties (Article 50):
- Serious breaches: Up to 1% of annual turnover
- Repeated breaches: Up to 2% of annual turnover
Breach Examples:
- Failure to report major incident
- Inadequate ICT risk management framework
- Non-compliance with testing requirements
- Lack of third-party oversight
- Failure to implement NCAs recommendations
Aggravating Factors:
- Duration of breach
- Intentional vs. negligent
- Previous violations
- Cooperation with authorities
- Impact on financial stability
Mitigating Factors:
- Self-reporting
- Prompt remediation
- Cooperation with investigation
- Good faith efforts to comply
Other Enforcement Actions
- Warnings and reprimands
- Orders to cease practices
- Temporary prohibition of activities
- Public disclosure of violations
- Increased reporting requirements
- Enhanced supervision
Reputational Impact
- Public announcement of penalties
- Loss of customer confidence
- Competitive disadvantage
- Potential loss of business (due to non-compliance)
- Board and executive accountability
Key Success Factors for DORA Compliance
-
Executive and Board Commitment:
- C-suite and board understanding of DORA requirements
- Allocation of sufficient budget and resources
- Board-level ownership of digital resilience strategy
-
Cross-Functional Collaboration:
- IT, security, risk, compliance, legal, business units
- Clear governance structure
- Regular communication and coordination
-
Comprehensive ICT Risk Framework:
- Board-approved and regularly updated
- Risk-based approach
- Proportionate to entity size and complexity
- Embedded in organization culture
-
Robust Incident Response:
- Capability to detect major incidents quickly
- Clear classification criteria
- Ability to meet reporting deadlines (4h, 72h, 1 month)
- Tested and effective response procedures
-
Third-Party Risk Management:
- Complete and current register
- DORA-compliant contracts
- Ongoing monitoring and audits
- Exit strategies for critical providers
-
Regular Testing:
- Risk-based testing program
- TLPT for significant entities
- Remediation tracking
- Continuous improvement
-
Information Sharing:
- Active participation in sharing communities
- Integration of threat intelligence
- Contribution to collective defense
-
Documentation:
- Comprehensive policies and procedures
- Evidence of implementation
- Audit trail for compliance
- Readiness for NCA inspections
-
Training and Awareness:
- All staff aware of DORA requirements
- Role-specific training
- Board training on ICT risks
- Regular refresher training
-
Continuous Monitoring and Improvement:
- Ongoing compliance monitoring
- Lessons learned from incidents and tests
- Adaptation to evolving threats
- Regulatory changes incorporated
Common Pitfalls and How to Avoid Them
Pitfall 1: Underestimating Complexity
Problem: Viewing DORA as just another compliance exercise Solution: Treat DORA as strategic transformation, not checklist compliance
Pitfall 2: Insufficient Budget/Resources
Problem: Underfunding DORA implementation Solution: Conduct thorough cost assessment, build business case, secure executive commitment
Pitfall 3: Lack of Board Engagement
Problem: Board treats DORA as IT issue Solution: Board training, regular reporting, frame as business resilience (not just IT)
Pitfall 4: Incomplete Third-Party Register
Problem: Missing or inaccurate register of ICT providers Solution: Comprehensive discovery process, procurement coordination, regular updates
Pitfall 5: Contract Renegotiation Delays
Problem: Providers slow to agree to DORA clauses Solution: Start early, prioritize critical providers, consider alternatives if provider refuses
Pitfall 6: Inadequate Incident Classification
Problem: Misclassifying incidents (major vs. non-major) Solution: Clear, documented criteria; risk/compliance involvement; err on side of reporting
Pitfall 7: Unrealistic Testing Scope
Problem: Testing program too limited or too ambitious Solution: Risk-based prioritization, phased approach, leverage external expertise
Pitfall 8: Siloed Implementation
Problem: IT/security implementing DORA without business involvement Solution: Cross-functional steering committee, business unit engagement, shared ownership
Pitfall 9: Documentation Gaps
Problem: Controls implemented but not documented Solution: Documentation discipline, centralized repository, regular reviews
Pitfall 10: "Set and Forget" Mentality
Problem: Treating DORA as one-time project Solution: Continuous monitoring, regular updates, embed in BAU processes
DORA and Related Regulations
Interaction with Other EU Regulations
GDPR (General Data Protection Regulation):
- DORA complements GDPR
- GDPR: Data protection and privacy
- DORA: Digital operational resilience
- Overlap: Data breach notification, security controls
- Coordination: DORA incident reporting does not replace GDPR breach notification (both may apply)
NIS2 Directive (Network and Information Security Directive):
- NIS2 applies to broader set of entities (including some financial)
- DORA is lex specialis for financial sector (takes precedence)
- Financial entities under DORA not subject to NIS2
- Similar requirements: Risk management, incident reporting, supply chain security
MiCA (Markets in Crypto-Assets Regulation):
- MiCA regulates crypto-asset service providers (CASPs)
- DORA applies to CASPs
- MiCA has specific requirements for CASPs; DORA adds operational resilience layer
EMIR/SFTR (Derivatives and Securities Financing Transactions):
- DORA complements with operational resilience requirements
- CCPs, trade repositories subject to both EMIR and DORA
Alignment with International Standards
ISO 27001: Information security management
- DORA aligns with ISO 27001 principles
- ISO certification helpful but not sufficient for DORA compliance
NIST Cybersecurity Framework:
- DORA's risk management framework similar to NIST CSF
- Identify, Protect, Detect, Respond, Recover
TIBER-EU:
- DORA explicitly adopts TIBER-EU for TLPT
- Harmonized threat-led testing across EU
SWIFT Customer Security Programme (CSP):
- Banks using SWIFT also subject to CSP
- DORA and SWIFT CSP complementary
- Some overlap in controls (reduce duplication)
Resources and References
Official DORA Regulation:
- Regulation (EU) 2022/2554 (OJ L 333, 27.12.2022)
European Supervisory Authorities:
- European Banking Authority (EBA): eba.europa.eu
- European Securities and Markets Authority (ESMA): esma.europa.eu
- European Insurance and Occupational Pensions Authority (EIOPA): eiopa.europa.eu
European Central Bank:
- TIBER-EU Framework: ecb.europa.eu
National Competent Authorities:
- Varies by member state (e.g., Bundesbank, Banque de France, Bank of Italy)
Industry Associations:
- European Banking Federation (EBF)
- Insurance Europe
- AFME (Association for Financial Markets in Europe)
Threat Intelligence and Information Sharing:
- FS-ISAC (Financial Services Information Sharing and Analysis Center): fsisac.com
- ENISA (EU Agency for Cybersecurity): enisa.europa.eu
Standards and Frameworks:
- ISO 27001:2013 Information Security Management
- NIST Cybersecurity Framework
- TIBER-EU
Capabilities
- DORA compliance assessment and gap analysis
- ICT risk management framework design and implementation
- Major incident classification and reporting procedures
- Incident response plan development and testing
- Digital operational resilience testing program design
- TLPT (threat-led penetration testing) planning and execution support
- Third-party ICT risk management and oversight
- Contract review and DORA clause integration
- Critical provider identification and management
- Information sharing strategy and implementation
- Board and executive training on DORA requirements
- Regulatory technical standards (RTS/ITS) interpretation
- NCA preparation and regulatory liaison
- DORA roadmap and project management
- Cross-regulation alignment (GDPR, NIS2, MiCA)
- TIBER-EU framework implementation
- Business impact analysis (BIA) for ICT dependencies
- ICT asset inventory and dependency mapping
Commands 5
DORA Assessment
Evaluates organizational readiness for Digital Operational Resilience Act (DORA) compliance.
Arguments
$1- Assessment scope (required: full, pillar-specific, entity-type)$2- Entity classification (optional: credit-institution, payment-institution, investment-firm, crypto-asset-provider, ict-provider)
DORA Overview
Regulation: EU Regulation 2022/2554 Effective Date: January 17, 2025 Applicability: EU financial entities and ICT third-party service providers Enforcement: National competent authorities (NCAs)
Entity Types Subject to DORA
| Entity Type | Examples | Key Requirements |
|---|---|---|
| Credit Institutions | Banks, lending institutions | Full DORA compliance, advanced testing |
| Payment Institutions | Payment processors, e-money institutions | Digital resilience testing, incident reporting |
| Investment Firms | Broker-dealers, asset managers | ICT risk management, third-party oversight |
| Crypto-Asset Service Providers | Exchanges, wallet providers | Enhanced monitoring, security controls |
| Insurance/Reinsurance | Insurers, reinsurance undertakings | Business continuity, resilience testing |
| ICT Third-Party Providers | Cloud providers, data centers, critical service providers | Oversight framework, contractual requirements |
DORA's 5 Pillars
Pillar 1: ICT Risk Management (Articles 5-16)
Comprehensive framework for managing ICT risks across the organization.
Key Requirements:
- Governance and control framework
- ICT risk management framework
- Business continuity policy and disaster recovery plans
- Learning and evolving capabilities
- Communication during crises
Pillar 2: ICT-Related Incident Management & Reporting (Articles 17-23)
Detection, management, and reporting of major ICT-related incidents.
Key Requirements:
- Incident detection and management processes
- Classification of incidents (major vs. non-major)
- Reporting to competent authorities (major incidents)
- Voluntary notification mechanism
- Centralized incident reporting to ESAs
Major Incident Criteria:
- Significant impact on financial services
- Client/counterparty impact
- Reputational impact
- Data loss or corruption
- Critical service disruption
Pillar 3: Digital Operational Resilience Testing (Articles 24-27)
Regular testing to ensure systems can withstand cyber threats and operational disruptions.
Key Requirements:
- Risk-based testing programs
- Advanced testing (threat-led penetration testing - TLPT)
- Testing frequency based on risk profile
- Test result remediation
- TLPT for systemically important entities
Testing Types:
- Vulnerability assessments
- Network security assessments
- Gap analyses
- Physical security reviews
- Questionnaires and software solution scanning
- Open-source analyses
- Scenario-based testing
- Compatibility testing
- Performance testing
- End-to-end testing
- Threat-led penetration testing (TLPT)
Pillar 4: ICT Third-Party Risk Management (Articles 28-30)
Oversight of risks from ICT service providers, especially critical providers.
Key Requirements:
- Third-party risk assessment and monitoring
- Contractual arrangements with service providers
- Key contractual provisions mandated by DORA
- Exit strategies and transition planning
- Register of all ICT third-party providers
- Oversight framework for critical providers
Critical ICT Third-Party Providers:
- Designated by ESAs
- Subject to direct oversight
- Must meet stringent requirements
- Lead overseer assigned
Pillar 5: Information Sharing (Articles 45)
Voluntary sharing of cyber threat information and intelligence.
Key Requirements:
- Participation in information-sharing arrangements
- Protection from liability when sharing in good faith
- Trusted information-sharing communities
- Cyber threat intelligence exchange
Assessment Output
-
Overall Readiness Score: Compliance percentage across 5 pillars
-
Pillar-by-Pillar Analysis:
- ICT Risk Management: X% compliant
- Incident Management & Reporting: X% compliant
- Resilience Testing: X% compliant
- Third-Party Risk: X% compliant
- Information Sharing: X% compliant
-
Gap Identification:
- Critical gaps blocking compliance
- High-priority gaps requiring immediate attention
- Medium-priority gaps (address before Jan 2025)
- Low-priority enhancements
-
Entity-Specific Requirements: Tailored to organization type
-
Competent Authority Expectations: NCA-specific guidance
-
Remediation Roadmap: Phased approach to compliance
-
Timeline to Compliance: Based on current state
-
Budget Estimates: Investment needed for compliance
Key Compliance Milestones
| Deadline | Requirement |
|---|---|
| January 17, 2025 | DORA becomes applicable |
| Within 6 months | Initial risk assessment complete |
| Within 12 months | Full ICT risk management framework |
| Ongoing | Incident reporting (within timelines) |
| Annual | Resilience testing (minimum) |
| Every 3 years | TLPT for significant entities |
Critical Success Factors
- Executive Commitment: Board-level ownership and resources
- Cross-Functional Collaboration: IT, risk, compliance, legal
- ICT Risk Framework: Comprehensive and board-approved
- Incident Response Capability: Detection, classification, reporting
- Third-Party Inventory: Complete register with risk ratings
- Testing Program: Risk-based and regularly executed
- Documentation: Policies, procedures, evidence
- Vendor Contracts: DORA-compliant clauses and SLAs
Common Readiness Gaps
Governance & Risk Management
- No ICT risk management framework
- Board not sufficiently involved in ICT risk
- Inadequate business continuity planning
- Lack of ICT asset inventory
Incident Management
- No major incident classification criteria
- Incident reporting process not aligned with DORA timelines
- Missing incident response playbooks
- Lack of crisis communication plans
Testing
- No formal resilience testing program
- Testing not risk-based
- Advanced testing (TLPT) not planned
- Remediation tracking inadequate
Third-Party Risk
- Incomplete third-party inventory
- Contracts lack DORA provisions
- No critical provider oversight
- Exit strategies not documented
Information Sharing
- Not participating in threat intelligence communities
- No framework for sharing incidents
- Legal concerns about information sharing
Regulatory Expectations
European Banking Authority (EBA): Focus on credit institutions European Securities and Markets Authority (ESMA): Investment firms European Insurance and Occupational Pensions Authority (EIOPA): Insurance National Competent Authorities: Country-specific supervision
Inspection Focus Areas:
- ICT risk governance
- Major incident handling
- TLPT execution and findings
- Critical provider dependencies
- Contractual compliance
Examples
# Full DORA readiness assessment
/dora:assess full
# Assessment for credit institution
/dora:assess full credit-institution
# Pillar-specific assessment (Third-Party Risk)
/dora:assess pillar-specific
# Assessment by entity type
/dora:assess entity-type payment-institution
DORA Evidence Checklist
Generates comprehensive evidence collection checklists for EU Digital Operational Resilience Act (DORA) requirements, tailored for financial entities operating in the EU with ICT risk management focus.
Never commit evidence artifacts to source control. The outputs below include real usernames, credential reports, MFA device states, and privileged-account inventories.
.gitignorecoversevidence/by default sogit add -Awill not sweep it up, but durable storage is your responsibility. Use an encrypted, access-controlled evidence locker (encrypted S3 with least-privilege IAM, a GRC platform, or a shared drive with full-disk encryption and MFA-gated access).
Usage
/dora:evidence-checklist <article> [--entity-type <credit|investment|payment>] [--export <format>]
Arguments
<article>: DORA article (e.g., "Article 6", "Article 9", "Article 11") or topic (e.g., "ICT Risk Management", "Incident Reporting", "Testing")--entity-type: Financial entity type (credit,investment,payment,crypto,insurance). Default:credit--export: Export format (json,csv,markdown). Default:markdown
Example: ICT Risk Management Framework Evidence
/dora:evidence-checklist "Article 6" --entity-type credit
Output:
DORA Evidence Checklist
Article: Article 6 - ICT Risk Management Framework
Entity Type: Credit Institution (Bank)
Compliance Deadline: January 17, 2025
Supervision: ECB/National Competent Authority
## Article 6 Requirements
Financial entities shall have a sound, comprehensive and well-documented ICT risk management framework as part of their overall risk management system, which enables them to address ICT risk quickly, efficiently and comprehensively and to ensure a high level of digital operational resilience.
## Key Requirements Summary
1. **ICT Risk Management Framework** documented and approved by management body
2. **ICT Risk Management Strategy** aligned with business strategy
3. **ICT Risk Management Policy** covering all ICT risks
4. **ICT Risk Identification, Classification, Assessment**
5. **ICT Risk Mitigation and Protection**
6. **ICT Risk Detection, Response, Recovery**
7. **ICT Risk Monitoring and Communication**
8. **ICT Risk Testing** (Articles 24-25)
## Evidence Requirements
### Required Documentation (Policy Layer)
□ **ICT Risk Management Framework Document**
- Scope: All ICT systems and third-party ICT service providers
- Required components:
- Governance structure (roles, responsibilities)
- Risk identification methodology
- Risk assessment procedures (likelihood, impact)
- Risk treatment strategies (accept, mitigate, transfer, avoid)
- Monitoring and reporting mechanisms
- Integration with overall risk management
- Update frequency: Annually or when material changes
- Approver: Management Body (Board of Directors)
- Evidence: Board-approved ICT Risk Framework v1.x with minutes
□ **ICT Risk Management Strategy**
- Multi-year ICT strategy (3-5 years)
- Alignment with business strategy and risk appetite
- Digital resilience objectives and KPIs
- Investment plan for ICT resilience
- Evidence: Board-approved ICT Strategy document
□ **ICT Risk Management Policy**
- Detailed risk management procedures
- Risk assessment criteria and methodology
- Risk tolerance thresholds
- Escalation procedures
- Evidence: CISO-approved ICT Risk Policy v1.x
□ **ICT Asset Inventory** (Article 8(2))
- Complete inventory of all ICT assets
- Classification by criticality (critical, important, standard)
- Ownership and dependencies
- Update frequency: Real-time or monthly
- Evidence: ICT asset register with classification
□ **ICT Risk Register**
- Identified ICT risks with ratings (inherent, residual)
- Risk treatment plans
- Risk owners
- Review history (quarterly minimum)
- Evidence: ICT Risk Register (Excel/GRC tool export)
□ **Business Impact Analysis (BIA) for Critical ICT Services**
- Identification of critical business functions
- Maximum tolerable downtime (MTD)
- Recovery time objectives (RTO)
- Recovery point objectives (RPO)
- Evidence: BIA report for all critical services
### Automated Evidence Collection
✓ **ICT Asset Inventory (Cloud Infrastructure)**
```bash
# AWS - Complete infrastructure inventory
aws resourcegroupstaggingapi get-resources \
--output json > evidence/dora-art6-aws-assets-$(date +%Y%m%d).json
# AWS Config - Configuration snapshots
aws configservice describe-configuration-recorders \
--output json > evidence/dora-art6-config-recorders-$(date +%Y%m%d).json
# List all EC2 instances with tags (criticality classification)
aws ec2 describe-instances \
--filters "Name=tag-key,Values=Criticality" \
--query 'Reservations[].Instances[].[InstanceId, Tags[?Key==`Criticality`].Value | [0], State.Name]' \
--output json > evidence/dora-art6-ec2-criticality-$(date +%Y%m%d).json
# RDS databases (critical data assets)
aws rds describe-db-instances --output json \
> evidence/dora-art6-rds-databases-$(date +%Y%m%d).json
# Azure - Resource inventory
az resource list --output json > evidence/dora-art6-azure-assets-$(date +%Y%m%d).json
# GCP - Asset inventory
gcloud asset search-all-resources --format=json \
> evidence/dora-art6-gcp-assets-$(date +%Y%m%d).json
Collection Frequency: Monthly (minimum), real-time preferred Retention: 5 years (DORA requirement) Purpose: Complete ICT asset inventory per Article 8(2)
✓ Configuration Management Evidence
# AWS Config - Configuration compliance
aws configservice describe-compliance-by-config-rule \
--output json > evidence/dora-art6-config-compliance-$(date +%Y%m%d).json
# Get non-compliant resources
aws configservice describe-compliance-by-resource \
--compliance-types NON_COMPLIANT \
--output json > evidence/dora-art6-non-compliant-resources-$(date +%Y%m%d).json
# Azure Policy compliance
az policy state list --resource-type "Microsoft.Compute/virtualMachines" \
--filter "complianceState eq 'NonCompliant'" \
--output json > evidence/dora-art6-azure-policy-violations-$(date +%Y%m%d).json
# GCP Policy Intelligence
gcloud asset search-all-resources \
--asset-types='compute.googleapis.com/Instance' \
--format=json > evidence/dora-art6-gcp-policy-compliance-$(date +%Y%m%d).json
Collection Frequency: Daily Retention: 5 years Purpose: ICT system configuration monitoring
✓ Vulnerability Management Evidence
# AWS Inspector - Vulnerability findings
aws inspector2 list-findings \
--filter-criteria '{"severity":[{"comparison":"EQUALS","value":"CRITICAL"},{"comparison":"EQUALS","value":"HIGH"}]}' \
--output json > evidence/dora-art6-vulnerabilities-$(date +%Y%m%d).json
# AWS Security Hub - Security findings
aws securityhub get-findings \
--filters '{"SeverityLabel":[{"Value":"CRITICAL","Comparison":"EQUALS"},{"Value":"HIGH","Comparison":"EQUALS"}],"RecordState":[{"Value":"ACTIVE","Comparison":"EQUALS"}]}' \
--output json > evidence/dora-art6-security-findings-$(date +%Y%m%d).json
# Azure Security Center - Recommendations
az security assessment list --output json \
> evidence/dora-art6-azure-security-$(date +%Y%m%d).json
# Tenable/Qualys vulnerability scan results (if using third-party)
# Export via API or manual download
# evidence/dora-art6-vulnerability-scan-$(date +%Y%m%d).csv
Collection Frequency: Weekly (scans), Monthly (reports) Retention: 5 years Purpose: ICT vulnerability management per Article 9(4)
✓ Patch Management Evidence
# AWS Systems Manager - Patch compliance
aws ssm describe-instance-patch-states \
--output json > evidence/dora-art6-patch-compliance-$(date +%Y%m%d).json
# Azure Update Management
az vm assess-patches --ids $(az vm list --query '[].id' -o tsv) \
--output json > evidence/dora-art6-azure-patches-$(date +%Y%m%d).json
# List instances with missing critical patches
aws ssm describe-instance-patch-states \
--output json | jq '.InstancePatchStates[] | select(.CriticalNonCompliantCount > 0 or .SecurityNonCompliantCount > 0)' \
> evidence/dora-art6-missing-patches-$(date +%Y%m%d).json
Collection Frequency: Weekly Retention: 5 years Purpose: Patch management process evidence
✓ Backup and Recovery Evidence
# AWS Backup - Backup job status
aws backup list-backup-jobs \
--by-created-after $(date -u -d '30 days ago' +%Y-%m-%dT%H:%M:%S) \
--output json > evidence/dora-art6-backup-jobs-$(date +%Y%m).json
# RDS automated backups
aws rds describe-db-snapshots \
--snapshot-type automated \
--output json > evidence/dora-art6-rds-backups-$(date +%Y%m%d).json
# S3 versioning status (for data recovery)
for bucket in $(aws s3api list-buckets --query 'Buckets[].Name' --output text); do
echo "=== $bucket ===" >> evidence/dora-art6-s3-versioning-$(date +%Y%m%d).txt
aws s3api get-bucket-versioning --bucket "$bucket" >> evidence/dora-art6-s3-versioning-$(date +%Y%m%d).txt
done
# Azure - Recovery Services vaults
az backup vault list --output json > evidence/dora-art6-azure-vaults-$(date +%Y%m%d).json
Collection Frequency: Monthly Retention: 5 years Purpose: Backup and recovery capabilities per Article 11
✓ Monitoring and Logging Evidence
# AWS CloudTrail - Audit trail
aws cloudtrail describe-trails --output json \
> evidence/dora-art6-cloudtrail-config-$(date +%Y%m%d).json
# CloudWatch alarms (monitoring setup)
aws cloudwatch describe-alarms --output json \
> evidence/dora-art6-cloudwatch-alarms-$(date +%Y%m%d).json
# GuardDuty findings (threat detection)
aws guardduty list-findings \
--detector-id $(aws guardduty list-detectors --query 'DetectorIds[0]' --output text) \
--finding-criteria '{"Criterion":{"severity":{"Gte":7}}}' \
--output json > evidence/dora-art6-guardduty-findings-$(date +%Y%m%d).json
# Azure Monitor activity logs
az monitor activity-log list \
--start-time $(date -u -d '30 days ago' +%Y-%m-%dT%H:%M:%S) \
--output json > evidence/dora-art6-azure-activity-$(date +%Y%m).json
Collection Frequency: Daily (critical alerts), Monthly (summaries) Retention: 5 years Purpose: Continuous monitoring per Article 17
Manual Evidence Collection
□ Management Body Approval Evidence
- Board meeting minutes approving ICT Risk Framework
- Board resolution on ICT strategy
- Evidence: Board minutes (sanitized), resolution document
- Frequency: Annual (or when framework updated)
- CRITICAL: DORA requires explicit management body oversight
□ Quarterly ICT Risk Committee Meetings
- ICT Risk Committee charter
- Meeting minutes (quarterly minimum)
- Risk review and approval decisions
- Escalation of critical risks to Board
- Evidence: 4 quarterly meeting minutes per year
- Frequency: Quarterly
□ ICT Risk Assessment Reports (Quarterly)
- Comprehensive ICT risk assessment
- Changes in risk profile since last review
- New risks identified
- Risk mitigation progress
- Evidence: Quarterly risk assessment report signed by CISO
- Frequency: Quarterly (minimum)
□ Annual ICT Risk Management Report to Board
- Summary of ICT risks and mitigations
- Key performance indicators (KPIs) for ICT resilience
- Incidents and near-misses
- Testing results (penetration tests, DR tests)
- Third-party ICT provider risks
- Investment recommendations
- Evidence: Annual report to Board with Board acknowledgment
- Frequency: Annual (minimum)
□ Business Impact Analysis (BIA) Review
- Critical business functions identified
- RTOs/RPOs documented for each critical function
- Dependencies mapped (internal, third-party)
- Annual review and update
- Evidence: BIA report v1.x with sign-off
- Frequency: Annual review
□ Third-Party ICT Risk Assessments (Article 28)
- Risk assessment for each critical ICT third-party provider
- Contractual arrangements review (Articles 29-30)
- Concentration risk analysis
- Evidence: Third-party risk register + assessments
- Frequency: Annual (minimum), before onboarding new providers
□ ICT Incident Log (Article 17)
- All ICT incidents logged (major and non-major)
- Root cause analysis for major incidents
- Lessons learned documentation
- Evidence: Incident register + RCA reports
- Frequency: Ongoing (log all incidents)
□ Business Continuity and Disaster Recovery Plan
- Documented BC/DR procedures
- Recovery strategies for critical ICT services
- Crisis management procedures
- Evidence: BC/DR plan v1.x approved by senior management
- Frequency: Annual update, tested semi-annually
□ DR Test Results (Article 11(6))
- At least annual full DR test
- Test scenarios, results, and lessons learned
- Remediation of gaps identified
- Evidence: DR test report with sign-off
- Frequency: Annual (full test), quarterly (component tests recommended)
DORA Supervisory Expectations
National competent authorities (NCAs) will expect:
Documentation Requirements
✓ ICT Risk Framework formally approved by management body ✓ Framework reviewed and updated annually (at minimum) ✓ Quarterly risk reporting to senior management ✓ Annual comprehensive report to Board ✓ Policies aligned with EBA/ESMA/EIOPA guidelines
Implementation Requirements
✓ All ICT assets inventoried and classified by criticality ✓ Risk assessments cover all ICT systems (including third-party) ✓ Risk treatment plans for all material ICT risks ✓ Continuous monitoring and detection capabilities ✓ Incident response procedures tested ✓ BC/DR plans tested annually
Testing and Validation
✓ Annual DR test (full scenario) ✓ Threat-led penetration testing (TLPT) for significant entities ✓ Vulnerability scanning (at least quarterly) ✓ Patch management procedures enforced ✓ Third-party ICT provider audits/assessments
Reporting to Supervisors
✓ Major ICT incidents reported within 4 hours (initial), 24 hours (intermediate), <1 month (final) ✓ Annual DORA compliance attestation (expected from NCAs) ✓ On-demand reporting for supervisory reviews
Common DORA Assessment Findings
Critical (Non-Compliance)
❌ No documented ICT Risk Framework ❌ Framework not approved by management body ❌ No ICT asset inventory or incomplete inventory ❌ No business impact analysis for critical services ❌ No annual DR testing ❌ Major incidents not reported to NCA within timeframes
Moderate (Gaps requiring remediation)
⚠️ ICT Risk Framework not reviewed annually ⚠️ Quarterly risk reporting to Board incomplete ⚠️ Some ICT assets not classified by criticality ⚠️ Third-party ICT risk assessments incomplete ⚠️ Vulnerability management process gaps ⚠️ Patch SLAs not defined or enforced
Minor (Best practice recommendations)
⚠️ Risk register not updated quarterly ⚠️ Monitoring dashboards incomplete ⚠️ DR test scenarios limited (need more comprehensive tests) ⚠️ Evidence retention <5 years
Remediation Guidance
If No ICT Risk Framework Exists
-
Immediate (Weeks 1-4): Draft ICT Risk Framework
- Use EBA Guidelines on ICT Risk (EBA/GL/2019/04) as template
- Adapt to organization size and complexity
- Include all 7 required components (governance, ID, protect, detect, respond, recover, testing)
-
Weeks 5-8: Board Approval Process
- Present framework to ICT Risk Committee
- Revise based on feedback
- Present to Board for approval
- Document approval in Board minutes
-
Weeks 9-12: Implementation Planning
- Develop detailed policies and procedures
- Assign roles and responsibilities
- Implement risk assessment process
- Launch asset inventory project
Timeline: 3-4 months minimum before DORA deadline
If Asset Inventory Incomplete
- Use automated discovery (AWS Config, Azure Resource Graph, etc.)
- Classify assets by criticality (align with BIA)
- Document asset owners (business + technical owners)
- Implement continuous asset tracking (not one-time snapshot)
Timeline: 4-8 weeks depending on estate size
If DR Testing Not Performed
- Schedule annual DR test (before DORA deadline)
- Define test scenarios (loss of primary data center, ransomware, etc.)
- Involve all critical stakeholders
- Document results and lessons learned
- Remediate gaps within 90 days
Timeline: 2-3 months (planning + execution + remediation)
Cross-References
Related DORA Articles
- Article 5 - Governance and organization
- Article 8 - Identification (asset inventory, dependencies)
- Article 9 - Protection and prevention (ICT security, change management)
- Article 11 - Business continuity (BC/DR, backup)
- Article 17 - Detection (monitoring, logging)
- Article 28-30 - Third-party ICT risk management
Maps to Other Frameworks
- ISO 27001:2022: Annex A (all controls), clause 6 (risk management)
- NIST Cybersecurity Framework: All 5 functions (Identify, Protect, Detect, Respond, Recover)
- NIST 800-53: All families (especially RA, CA, CP, IR, SI)
- SOC 2: CC3 (Risk assessment), CC7 (System monitoring), CC9 (Risk mitigation)
- EBA Guidelines: EBA/GL/2019/04 (ICT Risk), EBA/GL/2019/02 (Outsourcing)
Cost Estimates
ICT Risk Framework Implementation (For Medium Bank)
- Framework development and approval: 200 hours ($20,000)
- Asset inventory and classification: 160 hours ($16,000)
- Risk assessment process: 120 hours ($12,000)
- Policy and procedure documentation: 200 hours ($20,000)
- GRC tool implementation: 160 hours + $50k software ($66,000)
- Total Year 1: ~$134k
Ongoing Compliance (Annual)
- Quarterly risk assessments: 160 hours/year ($16,000)
- Annual Board reporting: 40 hours ($4,000)
- DR testing: 80 hours ($8,000)
- Vulnerability management: 240 hours/year ($24,000)
- Incident management: 120 hours/year ($12,000)
- Total Ongoing: ~$64k/year
Tools/Services
- GRC platform: $50k-$150k/year (medium org)
- Vulnerability scanning: $10k-$30k/year
- SIEM/monitoring: $50k-$200k/year
- Third-party audit (ISO 27001): $30k-$80k
- TLPT testing (significant entities): $100k-$300k (every 3 years)
Evidence Package Structure
evidence/
└── dora-article-6-ict-risk-framework/
├── framework/
│ ├── ict-risk-framework-v1.2-board-approved.pdf
│ ├── board-minutes-approval-2024-03-15.pdf
│ ├── ict-risk-strategy-2024-2027.pdf
│ ├── ict-risk-policy-v1.1.pdf
│ └── governance-structure-diagram.pdf
├── asset-inventory/
│ ├── 2024-Q1/
│ │ ├── aws-assets-20240331.json
│ │ ├── azure-assets-20240331.json
│ │ └── asset-register-criticality-20240331.xlsx
│ ├── 2024-Q2/
│ ├── 2024-Q3/
│ └── 2024-Q4/
├── risk-assessments/
│ ├── Q1-2024-ict-risk-assessment.pdf
│ ├── Q2-2024-ict-risk-assessment.pdf
│ ├── Q3-2024-ict-risk-assessment.pdf
│ ├── Q4-2024-ict-risk-assessment.pdf
│ └── ict-risk-register-master.xlsx
├── bia/
│ ├── business-impact-analysis-2024.pdf
│ ├── critical-services-rto-rpo.xlsx
│ └── dependency-mapping.pdf
├── monitoring/
│ ├── 2024-01/
│ │ ├── vulnerabilities-202401.json
│ │ ├── security-findings-202401.json
│ │ └── patch-compliance-202401.json
│ └── ... (monthly)
├── dr-testing/
│ ├── dr-test-2024-annual.pdf
│ ├── test-scenarios-2024.docx
│ └── remediation-plan-2024.xlsx
├── board-reporting/
│ ├── Q1-2024-board-report.pdf
│ ├── Q2-2024-board-report.pdf
│ ├── Q3-2024-board-report.pdf
│ ├── Q4-2024-board-report.pdf
│ └── annual-ict-risk-report-2024.pdf
└── README.md (evidence index, 5-year retention)
Automation Script
#!/usr/bin/env python3
"""
DORA Article 6 Evidence Collection Automation
Collects ICT risk management evidence for EU financial entities
"""
import boto3
import json
import os
from datetime import datetime, timedelta
class DORAEvidenceCollector:
def __init__(self, output_dir="evidence/dora-article-6"):
self.output_dir = output_dir
self.timestamp = datetime.now().strftime("%Y%m%d")
self.quarter = f"{datetime.now().year}-Q{(datetime.now().month-1)//3+1}"
os.makedirs(f"{output_dir}/asset-inventory/{self.quarter}", exist_ok=True)
os.makedirs(f"{output_dir}/monitoring/{datetime.now().strftime('%Y-%m')}", exist_ok=True)
def collect_asset_inventory(self):
"""Collect complete ICT asset inventory (Article 8 requirement)"""
print("Collecting ICT asset inventory...")
# AWS - All resources
resource_groups = boto3.client('resourcegroupstaggingapi')
paginator = resource_groups.get_paginator('get_resources')
all_resources = []
for page in paginator.paginate():
all_resources.extend(page['ResourceTagMappingList'])
output_file = f"{self.output_dir}/asset-inventory/{self.quarter}/aws-all-resources-{self.timestamp}.json"
with open(output_file, 'w') as f:
json.dump(all_resources, f, indent=2)
# Classify by criticality (based on tags)
critical_assets = [r for r in all_resources if any(t.get('Key') == 'Criticality' and t.get('Value') == 'Critical' for t in r.get('Tags', []))]
print(f"✓ Total assets: {len(all_resources)}")
print(f"✓ Critical assets: {len(critical_assets)}")
return {'total': len(all_resources), 'critical': len(critical_assets)}
def collect_vulnerability_findings(self):
"""Collect vulnerability scan results (Article 9 requirement)"""
print("Collecting vulnerability findings...")
inspector = boto3.client('inspector2')
security_hub = boto3.client('securityhub')
# Inspector findings (critical/high only)
inspector_findings = inspector.list_findings(
filterCriteria={
'severity': [
{'comparison': 'EQUALS', 'value': 'CRITICAL'},
{'comparison': 'EQUALS', 'value': 'HIGH'}
]
},
maxResults=1000
)
month = datetime.now().strftime("%Y-%m")
output_file = f"{self.output_dir}/monitoring/{month}/vulnerabilities-{self.timestamp}.json"
with open(output_file, 'w') as f:
json.dump(inspector_findings, f, indent=2, default=str)
finding_count = len(inspector_findings.get('findings', []))
print(f"✓ Vulnerability findings (Critical/High): {finding_count}")
return finding_count
def collect_backup_evidence(self):
"""Collect backup and recovery evidence (Article 11 requirement)"""
print("Collecting backup evidence...")
backup = boto3.client('backup')
# Backup jobs in last 30 days
start_date = datetime.now() - timedelta(days=30)
backup_jobs = backup.list_backup_jobs(
ByCreatedAfter=start_date
)
month = datetime.now().strftime("%Y-%m")
output_file = f"{self.output_dir}/monitoring/{month}/backup-jobs-{self.timestamp}.json"
with open(output_file, 'w') as f:
json.dump(backup_jobs, f, indent=2, default=str)
# Check backup success rate
total_jobs = len(backup_jobs.get('BackupJobs', []))
completed_jobs = len([j for j in backup_jobs.get('BackupJobs', []) if j.get('State') == 'COMPLETED'])
print(f"✓ Backup jobs (30 days): {total_jobs}")
print(f"✓ Successful backups: {completed_jobs}/{total_jobs} ({completed_jobs/total_jobs*100:.1f}%)")
return {'total': total_jobs, 'completed': completed_jobs}
def generate_quarterly_report(self, asset_data, vuln_count, backup_data):
"""Generate quarterly ICT risk management summary for Board"""
report = f"""
DORA Article 6 - ICT Risk Management Evidence Summary
Quarter: {self.quarter}
Generated: {datetime.now().strftime("%Y-%m-%d")}
ICT ASSET INVENTORY (Article 8)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Total ICT Assets: {asset_data['total']}
Critical ICT Assets: {asset_data['critical']} ({asset_data['critical']/asset_data['total']*100:.1f}%)
VULNERABILITY MANAGEMENT (Article 9)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Critical/High Findings: {vuln_count}
{'✓ GOOD' if vuln_count < 10 else '⚠️ REQUIRES ATTENTION' if vuln_count < 50 else '✗ CRITICAL - IMMEDIATE ACTION REQUIRED'}
BACKUP & RECOVERY (Article 11)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Backup Jobs (30 days): {backup_data['total']}
Success Rate: {backup_data['completed']/backup_data['total']*100:.1f}%
{'✓ COMPLIANT' if backup_data['completed']/backup_data['total'] >= 0.95 else '✗ BELOW TARGET (95%)'}
REQUIRED ACTIONS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
□ Quarterly ICT Risk Committee meeting (present these findings)
□ Update ICT risk register with new/changed risks
□ Escalate critical vulnerabilities to CISO
□ Complete quarterly access review
□ Prepare summary for Board report
NEXT QUARTERLY EVIDENCE COLLECTION: {(datetime.now() + timedelta(days=90)).strftime('%Y-%m-%d')}
Evidence Location: {self.output_dir}/
Retention: 5 years (DORA Article 10(1))
"""
report_file = f"{self.output_dir}/quarterly-summary-{self.quarter}.txt"
with open(report_file, 'w') as f:
f.write(report)
print(f"\n{report}")
print(f"Summary report: {report_file}")
if __name__ == "__main__":
print("DORA Article 6 - ICT Risk Management Evidence Collection")
print("=" * 70)
print(f"Compliance Deadline: January 17, 2025")
print("=" * 70)
collector = DORAEvidenceCollector()
asset_data = collector.collect_asset_inventory()
vuln_count = collector.collect_vulnerability_findings()
backup_data = collector.collect_backup_evidence()
collector.generate_quarterly_report(asset_data, vuln_count, backup_data)
print("\n✓ DORA evidence collection complete")
print("⚠️ REMINDER: Ensure Management Body reviews ICT Risk Framework annually")
DORA Compliance Deadline: January 17, 2025 Supervision: ECB (credit institutions), ESMA (investment firms), EIOPA (insurance) Implementation Priority: 🔴 CRITICAL (EU regulatory requirement) Penalties: Up to 2% of annual worldwide turnover or €10 million (whichever higher) Evidence Retention: 5 years minimum (Article 10)
DORA Incident Reporting
Provides comprehensive guidance on DORA's incident management and reporting requirements for major ICT-related incidents.
Arguments
$1- Incident severity (required: major, non-major, cyber-threat)$2- Reporting stage (optional: initial, intermediate, final, update)
Incident Reporting Overview
Legal Basis: Articles 17-23 of DORA Requirement: Mandatory reporting of major incidents to national competent authorities Timeline: Strict deadlines (4 hours, 72 hours, 1 month) Penalties: Significant fines for non-compliance
Incident Classification
Major Incident Criteria (Article 18)
An ICT-related incident is classified as major if it meets one or more of these criteria:
1. Impact on Financial Services
Threshold Indicators:
- Critical or important functions affected
- Services unavailable or degraded
- Transaction processing disrupted
- Client access to accounts/services blocked
- Payment systems affected
Examples:
- Online banking unavailable for >2 hours
- Payment processing system down
- Trading platform outage during market hours
- ATM network failure affecting multiple locations
2. Client/Counterparty Impact
Threshold Indicators:
- Large number of clients affected (>10,000 for large entities, proportionate for smaller)
- High-value counterparties impacted
- Multiple member states affected
- Impact duration exceeds tolerance levels
Examples:
- Widespread account access issues
- Failed bulk payments affecting thousands
- Trading disruptions affecting multiple clients
- Data breach exposing client information
3. Duration of Impact
Threshold Indicators:
- Service unavailable exceeding RTO (Recovery Time Objective)
- Prolonged degradation of critical services
- Extended recovery time
- Multiple business days affected
Typical Thresholds (entity-specific):
- Critical services: >2-4 hours
- Important services: >4-8 hours
- Supporting services: >24 hours
4. Geographical Spread
Threshold Indicators:
- Incident affects operations in multiple EU member states
- Cross-border service disruption
- International clients impacted
- Widespread system failure
5. Data Loss or Corruption
Threshold Indicators:
- Loss of critical data affecting service delivery
- Data corruption preventing transaction processing
- Integrity of financial records compromised
- Personal data breach requiring GDPR notification
Examples:
- Transaction database corruption
- Customer account data loss
- Financial records integrity issues
- Backup systems compromised
6. Reputational Impact
Threshold Indicators:
- Significant media coverage
- Public confidence affected
- Regulatory scrutiny triggered
- Market impact on share price
Examples:
- Major cybersecurity breach publicized
- Extended service outage reported in media
- Data breach affecting thousands of clients
- Ransomware attack with public demands
7. Economic Impact
Threshold Indicators:
- Direct financial losses exceeding materiality thresholds
- Operational costs of incident response
- Regulatory fines or penalties
- Client compensation required
Typical Thresholds:
- Large institutions: >EUR 100,000
- Medium institutions: >EUR 50,000
- Small institutions: >EUR 10,000
- (Proportionate to entity size and complexity)
Non-Major Incidents
Characteristics:
- Limited impact on services
- Contained to single function/system
- Quick resolution (within tolerance)
- Minimal client impact
- No data loss or corruption
- No reputational damage
Reporting:
- Internal tracking and documentation required
- No mandatory reporting to authorities
- May aggregate for trend analysis
- Report if incident escalates to major
Cyber Threats (Article 20)
Definition:
- Potential cyber attack identified
- Vulnerability discovered that could be exploited
- Threat intelligence indicating targeting
- Reconnaissance or probing detected
Reporting:
- Voluntary notification to authorities
- Can share with other financial entities
- Liability protection for good faith sharing
- Helps collective defense
Incident Reporting Timeline
Initial Notification (4 Hours)
Deadline: Within 4 hours of detection and classification as major incident
Required Information:
- Date and time of incident detection
- Indication that incident is classified as major
- Preliminary description of incident
- Affected systems or services
- Initial assessment of impact
- Status of incident (ongoing, contained, resolved)
Submission Method:
- Via single point of contact to NCA
- Using standardized template (when available)
- Electronic submission preferred
Key Point: This is notification of awareness, not full analysis. Speed is critical.
Intermediate Report (72 Hours)
Deadline: Within 72 hours of initial notification
Required Information:
- Updated incident classification and justification
- Actual number of clients/users affected
- Actual duration of impact to date
- Geographical scope of incident
- Root cause analysis (preliminary or final)
- Technical details of incident:
- Attack vectors (if applicable)
- Vulnerabilities exploited
- Systems/services compromised
- Data affected
- Mitigation actions taken
- Recovery actions initiated
- Expected recovery timeline
- Whether incident is ongoing
- Estimated further impact
Analysis Required:
- More detailed impact assessment
- Initial root cause if identified
- Evidence of mitigation effectiveness
Final Report (1 Month)
Deadline: Within 1 month after initial notification (may be extended in complex cases)
Required Information:
-
Comprehensive Incident Description:
- Full timeline of events
- Complete impact assessment
- Final client/service impact numbers
- Total duration of incident
-
Root Cause Analysis:
- Definitive root cause identification
- Contributing factors
- Why incident occurred
- Why incident was not prevented/detected earlier
-
Remediation Actions:
- Immediate fixes implemented
- System restoration details
- Data recovery efforts
- Compensating controls deployed
-
Lessons Learned:
- What went well
- What needs improvement
- Gaps identified in defenses
- Process failures
-
Preventive Measures:
- Long-term fixes planned/implemented
- Control enhancements
- Process improvements
- Technology upgrades
-
Estimated Costs:
- Direct incident costs
- Recovery costs
- Remediation costs
- Business impact (if calculable)
Quality Expectations:
- Thorough and accurate
- Evidence-based conclusions
- Clear action plan
- Demonstrates learning
Significant Updates (As Needed)
When Required:
- Material change to impact assessment
- Discovery of additional affected systems/data
- Extended recovery timeline
- New information about root cause
- Incident evolves or escalates
- Regulatory inquiry requires response
Timeline: As soon as reasonably practicable after new information emerges
Incident Management Process
1. Detection and Logging
Activities:
- Continuous monitoring detects anomaly
- Alerts triggered via SIEM or monitoring tools
- Incident logged in incident management system
- Initial timestamp recorded
Tools:
- SIEM (Security Information and Event Management)
- IDS/IPS (Intrusion Detection/Prevention Systems)
- Monitoring dashboards
- Anomaly detection systems
2. Initial Assessment
Activities:
- Security/IT team reviews alert
- Validates incident is genuine (not false positive)
- Assesses initial scope and impact
- Determines if incident could be major
Timeframe: Within 30-60 minutes of detection
3. Classification
Activities:
- Apply major incident criteria
- Consult classification matrix/decision tree
- Engage management if borderline
- Document classification decision
Key Decision: Major or Non-Major?
If Major:
- Initiate 4-hour notification clock
- Activate major incident response plan
- Notify senior management and board
If Non-Major:
- Continue internal incident response
- Document in internal register
- Monitor for escalation
4. Containment
Activities:
- Isolate affected systems
- Prevent spread of incident
- Preserve evidence for investigation
- Implement emergency workarounds
Examples:
- Network segmentation
- System isolation
- Account lockdowns
- Service redirects to backup systems
5. Initial Notification (if Major)
Activities:
- Prepare initial notification form
- Submit to NCA within 4 hours
- Copy to internal stakeholders
- Update incident log
Checklist:
- Incident detected and classified
- Senior management notified
- Initial notification form completed
- Submitted to NCA within 4 hours
- Confirmation received from NCA
- Internal stakeholders informed
6. Investigation and Analysis
Activities:
- Forensic investigation
- Root cause analysis
- Impact assessment
- Evidence collection
- Timeline reconstruction
Outputs:
- Incident timeline
- Root cause report
- Impact quantification
- Evidence package
7. Remediation and Recovery
Activities:
- Implement fixes
- Restore services
- Verify integrity
- Test functionality
- Communicate with clients
Validation:
- Services fully restored
- No residual vulnerabilities
- Monitoring confirms stability
- Clients notified of resolution
8. Intermediate Reporting (if Major)
Activities:
- Compile intermediate report
- Include all required elements
- Submit within 72 hours
- Update incident management system
9. Post-Incident Review
Activities:
- Lessons learned session
- Documentation of findings
- Improvement action items
- Update procedures/playbooks
Attendees:
- Incident response team
- Affected business units
- Senior management
- Risk and compliance
10. Final Reporting (if Major)
Activities:
- Compile comprehensive final report
- Complete root cause analysis
- Document all remediation
- Submit within 1 month
- Close incident in system
11. Continuous Improvement
Activities:
- Implement lessons learned
- Update incident response plans
- Enhance monitoring/detection
- Training on new procedures
- Test improvements
Reporting Channels and Contacts
National Competent Authority (NCA)
Identify Your NCA:
- Credit institutions: National banking supervisor (e.g., ECB, national central bank)
- Investment firms: National securities regulator
- Payment institutions: Payment services authority
- Insurance: National insurance regulator
Single Point of Contact:
- Designate internal contact person for NCA
- Provide contact details to NCA in advance
- Ensure 24/7 availability for major incidents
- Maintain backup contacts
Submission Methods:
- Electronic portal (varies by country)
- Secure email (encryption required)
- Dedicated incident reporting system
- Phone notification followed by written report
Internal Escalation
Notification Chain:
- IT/Security Operations Center (SOC)
- Chief Information Security Officer (CISO)
- Chief Information Officer (CIO)
- Chief Risk Officer (CRO)
- Chief Executive Officer (CEO)
- Board of Directors (for major incidents)
Timing:
- Immediate: SOC, CISO, CIO
- Within 1 hour: CRO, CEO (if major)
- Within 4 hours: Board chair (if major and ongoing)
- Next scheduled meeting: Full board briefing
Incident Response Documentation
Incident Log (All Incidents)
Required Fields:
- Incident ID
- Date and time of detection
- Date and time of classification
- Incident type (e.g., cyber attack, system failure, data breach)
- Affected systems and services
- Impact assessment
- Classification (major/non-major)
- Actions taken
- Status (open, contained, resolved, closed)
- Lessons learned
Major Incident File
Additional Documentation:
- Initial notification submission and NCA confirmation
- Intermediate report submission
- Final report submission
- All updates and significant changes
- Evidence collected (logs, forensics, screenshots)
- Root cause analysis
- Post-incident review notes
- Remediation tracking
- Cost tracking
Incident Response Plan
Required Components:
- Incident response team roles and responsibilities
- Classification criteria and decision trees
- Escalation procedures
- Communication templates
- NCA contact information
- Technical response procedures
- Recovery procedures
- Testing and training schedule
Common Reporting Challenges
Challenge 1: Classification Uncertainty
Issue: Unclear if incident meets major criteria Solution:
- Use documented decision tree
- Consult with risk/compliance
- When in doubt, report as major (can downgrade later)
- Document classification rationale
Challenge 2: Timeline Pressure
Issue: 4-hour notification deadline is tight Solution:
- Pre-populate templates
- Automate data collection
- Designate on-call responders
- Conduct incident drills
Challenge 3: Incomplete Information
Issue: Not all details available within deadlines Solution:
- Provide best available information
- Clearly state what is preliminary/estimated
- Commit to updates as information emerges
- Document information gaps
Challenge 4: Cross-Border Incidents
Issue: Incident affects multiple EU countries, unclear which NCA to notify Solution:
- Notify NCA of home member state
- Indicate cross-border nature
- NCA will coordinate with other regulators
- May need to notify multiple NCAs (follow their guidance)
Challenge 5: Third-Party Incidents
Issue: Incident originates from ICT service provider Solution:
- Financial entity still responsible for reporting
- Coordinate with service provider for details
- Ensure service provider contractual obligation to provide incident information
- Report even if incident is provider's fault
Penalties for Non-Compliance
Failure to Report:
- Administrative fines up to 1% of annual turnover
- Reputational damage
- Increased regulatory scrutiny
- Potential license implications
Late Reporting:
- Proportionate penalties based on delay
- Supervisory action
- Remediation requirements
Inaccurate Reporting:
- Penalties for misleading information
- Requirement to resubmit
- Loss of regulatory trust
Best Practices
Preparation
- Maintain up-to-date incident response plan
- Conduct regular incident response drills
- Pre-populate notification templates
- Establish clear communication channels with NCA
- Train all personnel on classification criteria
Detection
- Implement 24/7 monitoring for critical systems
- Deploy automated alerting
- Integrate threat intelligence
- Regular review of detection effectiveness
Response
- Activate incident response team immediately
- Document everything in real-time
- Preserve evidence (logs, forensics)
- Communicate clearly and frequently with stakeholders
Reporting
- Start clock immediately upon classification
- Submit initial notification well before 4-hour deadline
- Provide accurate, complete information
- Flag uncertainties and estimate ranges
- Follow up proactively with updates
Learning
- Conduct thorough post-incident review
- Document lessons learned
- Update procedures and controls
- Share insights with team
- Test improvements
Examples
# Get guidance for reporting a major incident (initial notification)
/dora:incident-reporting major initial
# Prepare intermediate report for major incident
/dora:incident-reporting major intermediate
# Understand non-major incident handling
/dora:incident-reporting non-major
# Guidance on voluntary cyber threat reporting
/dora:incident-reporting cyber-threat
# Prepare final report for major incident
/dora:incident-reporting major final
# Update reporting for evolving incident
/dora:incident-reporting major update
DORA Pillar Guidance
Provides detailed implementation guidance for each of DORA's 5 pillars.
Arguments
$1- Pillar (required: ict-risk, incident-management, resilience-testing, third-party-risk, information-sharing, all)$2- Detail level (optional: overview, implementation, evidence)
Pillar 1: ICT Risk Management (Articles 5-16)
Overview
Establishes comprehensive framework for managing ICT risks across financial entities.
Legal Basis: Articles 5-16 of DORA Applicability: All financial entities Key Principle: Proportionality to size, risk profile, and complexity
Core Requirements
1. ICT Risk Management Framework (Article 6)
Must Include:
- Strategies, policies, procedures, and protocols
- ICT risk management function with sufficient resources
- Documentation of ICT risk management framework
- Board approval and regular review
Implementation:
- Establish ICT risk management policy
- Define roles and responsibilities
- Create risk assessment methodology
- Implement controls and mitigation measures
- Monitor and report on ICT risks
2. Governance and Organization (Article 5)
Board Responsibilities:
- Define, approve, and oversee ICT risk management framework
- Allocate budget and resources
- Approve ICT strategy
- Approve policies for ICT service provision by third parties
- Receive regular reporting on ICT risk
Management Body:
- At least one member with sufficient knowledge and skills in ICT
- Regular training on ICT risks
- Oversight of senior management
3. Identification (Article 8)
Requirements:
- Identify all ICT-supported business functions
- Map dependencies and interdependencies
- Identify all ICT assets and configurations
- Document data flows
- Assess criticality of ICT assets
Deliverables:
- ICT asset inventory
- Business impact analysis (BIA)
- Data flow diagrams
- Network diagrams
- Dependency mapping
4. Protection and Prevention (Article 9)
Requirements:
- Implement security policies and procedures
- Regular ICT security awareness training
- Physical and environmental security
- Access control mechanisms
- Encryption of sensitive data
- Segregation of duties
- Network security controls
Key Controls:
- Multi-factor authentication
- Privileged access management
- Data loss prevention
- Endpoint protection
- Network segmentation
- Vulnerability management
- Patch management
5. Detection (Article 10)
Requirements:
- Continuous monitoring mechanisms
- Detection tools and systems
- Logging and log analysis
- Anomaly detection
- Intrusion detection/prevention systems (IDS/IPS)
- Security information and event management (SIEM)
Capabilities:
- Real-time alerting
- 24/7 monitoring (for significant entities)
- Threat intelligence integration
- Automated detection rules
6. Response and Recovery (Article 11)
Business Continuity:
- Business continuity policy
- Business continuity plans (BCPs)
- Disaster recovery plans (DRPs)
- Regular testing of BCPs/DRPs
- Communication plans during crises
Incident Response:
- Incident response plans
- Predefined incident response procedures
- Crisis management team
- Communication protocols
- Recovery time objectives (RTO)
- Recovery point objectives (RPO)
7. Learning and Evolving (Article 12)
Requirements:
- Post-incident reviews
- Lessons learned documentation
- Continuous improvement process
- Metrics and KPIs for ICT risk
- Regular framework updates
8. Communication (Article 13)
Requirements:
- Internal communication channels
- External communication (clients, authorities)
- Crisis communication plans
- Public relations protocols
- Media handling procedures
9. Backup Policies and Procedures (Article 12)
Requirements:
- Backup strategies and policies
- Regular backups of critical data and systems
- Backup testing and restoration
- Off-site backup storage
- Immutable backups (ransomware protection)
Pillar 2: Incident Management & Reporting (Articles 17-23)
Overview
Comprehensive framework for detecting, managing, classifying, and reporting ICT-related incidents.
Legal Basis: Articles 17-23 Key Innovation: Mandatory reporting of major incidents to authorities Timeline: Strict reporting deadlines
Core Requirements
1. Incident Management Process (Article 17)
Requirements:
- Detection mechanisms
- Incident management procedures
- Incident classification criteria
- Escalation procedures
- Root cause analysis
- Remediation and recovery
Process Steps:
- Detection and logging
- Initial assessment and classification
- Containment
- Investigation and analysis
- Remediation and recovery
- Post-incident review
- Reporting (if major incident)
2. Classification of Incidents (Article 18)
Major Incident Criteria:
- Significant impact on financial services provided
- Large number of clients/counterparties affected
- Geographical spread across multiple member states
- Duration exceeding thresholds
- Reputational impact
- Data loss affecting critical services
- Critical services unavailable
Classification Factors:
- Number of clients affected
- Duration of incident
- Geographical spread
- Economic impact
- Data loss severity
- Service criticality
- Reputational damage
3. Reporting to Authorities (Article 19)
Major Incident Reporting Timeline:
| Timeline | Report Type | Content |
|---|---|---|
| 4 hours | Initial notification | Incident awareness, preliminary assessment |
| 72 hours | Intermediate report | Classification, impact assessment, mitigation actions |
| 1 month | Final report | Root cause, remediation, lessons learned |
Additional Reports:
- Significant updates when incident evolves
- Material changes to impact assessment
- Updates on remediation progress
Reporting Channels:
- To relevant national competent authority (NCA)
- Via single point of contact
- Using standardized templates (RTS to be developed)
4. Voluntary Notification (Article 20)
Cyber Threats:
- Financial entities may voluntarily report cyber threats
- Sharing with other entities
- Reporting to authorities
- No liability for good faith sharing
5. Centralized Hub (Article 21)
ESA Responsibilities:
- European Supervisory Authorities establish incident register
- Analyze incident patterns
- Publish anonymized incident reports
- Identify trends and systemic risks
Pillar 3: Digital Operational Resilience Testing (Articles 24-27)
Overview
Risk-based testing program to ensure systems withstand, respond to, and recover from ICT-related disruptions.
Legal Basis: Articles 24-27 Principle: Proportionate to size, risk profile, and complexity
Core Requirements
1. General Testing Requirements (Article 24)
Mandatory Testing Types:
- Vulnerability assessments and scans
- Open-source analysis
- Network security assessments
- Gap analyses
- Physical security reviews
- Questionnaires and scanning software solutions
- Source code reviews (where feasible)
- Scenario-based testing
- Compatibility testing
- Performance testing
- End-to-end testing
- Penetration testing
Testing Frequency:
- Regular basis (at least annually)
- After significant changes to ICT systems
- Following major incidents
- Based on risk assessment
Testing Scope:
- All critical ICT systems
- Live production environments
- Third-party service providers
- Backup and recovery systems
2. Advanced Testing - TLPT (Articles 26-27)
Threat-Led Penetration Testing (TLPT):
- Simulated real-world cyber attacks
- Uses tactics, techniques, and procedures (TTPs) of threat actors
- Red team vs. blue team exercises
- Covers people, processes, and technology
TLPT Requirements:
- Conducted at least every 3 years
- For entities identified as systemically important
- By qualified testers (internal or external)
- Based on TIBER-EU framework or equivalent
- Covers critical functions and services
TLPT Process:
-
Preparation Phase:
- Scope definition
- Threat intelligence gathering
- Test plan development
- Stakeholder engagement
-
Testing Phase:
- Red team attack simulation
- Blue team defense
- White team oversight
- Real-time monitoring
-
Closure Phase:
- Debriefing
- Test report
- Remediation plan
- Lessons learned
TIBER-EU Alignment:
- Intelligence-led testing
- Bespoke scenarios
- Controlled testing environment
- No disruption to services
- Comprehensive documentation
3. Testing Documentation
Required Documentation:
- Testing policy and procedures
- Test plans and scopes
- Test results and findings
- Remediation plans
- Evidence of fixes implemented
- Management reporting
Pillar 4: Third-Party Risk Management (Articles 28-30)
Overview
Framework for managing risks from ICT third-party service providers, especially critical providers.
Legal Basis: Articles 28-30 Scope: All ICT services provided by third parties Special Focus: Critical ICT third-party service providers
Core Requirements
1. ICT Third-Party Risk (Article 28)
Risk Management Process:
- Maintain register of all ICT third-party service providers
- Risk assessment before contracting
- Ongoing monitoring of service providers
- Due diligence and security assessments
- Regular audits and reviews
- Exit strategies and transition plans
Register Requirements:
- List of all ICT service providers
- Contractual arrangements
- Data and functions involved
- Countries where services provided
- Start/end dates of contracts
- Classification (critical vs. non-critical)
2. Contractual Requirements (Article 30)
Mandatory Contractual Provisions:
-
Service Levels:
- Clear service level agreements (SLAs)
- Performance metrics
- Availability targets
- Response times
-
Locations:
- Data storage locations
- Data processing locations
- Permission requirements for relocations
-
Access and Audit Rights:
- Financial entity access to systems/data
- Competent authority access rights
- Audit rights
- Inspection rights
-
Security Requirements:
- Security measures and controls
- Incident notification obligations
- Data protection requirements
- Encryption standards
-
Termination Rights:
- Clear termination conditions
- Notice periods
- Handover procedures
- Data return/deletion
-
Subcontracting:
- Prior approval for subcontracting
- Subcontractor requirements
- Chain of subcontracting visibility
-
Exit Strategy:
- Transition assistance
- Knowledge transfer
- Data portability
- Service continuity during transition
-
Liability and Indemnity:
- Liability provisions
- Insurance requirements
- Indemnification clauses
3. Critical ICT Third-Party Providers
Designation:
- By European Supervisory Authorities (ESAs)
- Based on systemic importance
- Criteria: number of clients, criticality of services, substitutability
Oversight Framework:
- Direct oversight by ESAs
- Lead overseer appointed
- On-site inspections
- Recommendations and enforcement
- General investigations
Critical Provider Obligations:
- Register with lead overseer
- Provide information to authorities
- Submit to inspections
- Implement recommendations
- Maintain business continuity
Pillar 5: Information Sharing (Article 45)
Overview
Voluntary sharing of cyber threat information and intelligence among financial entities.
Legal Basis: Article 45 Purpose: Enhance collective resilience Protection: Liability protection for good faith sharing
Core Requirements
1. Information Sharing Arrangements
Participation:
- Join information-sharing communities
- Establish trusted sharing relationships
- Participate in sector-specific ISACs
- Engage with national/EU-level sharing platforms
Types of Information Shared:
- Cyber threat intelligence
- Tactics, techniques, and procedures (TTPs)
- Indicators of compromise (IOCs)
- Vulnerabilities and exploits
- Incident trends and patterns
- Mitigation strategies
2. Confidentiality and Liability Protection
Protections:
- No liability for sharing in good faith
- Confidentiality of shared information
- Protection from disclosure requirements (exceptions for law enforcement)
- Antitrust safe harbor
Conditions:
- Information shared in good faith
- Within trusted communities
- For enhancing digital resilience
- Not for competitive advantage
3. Information Sharing Platforms
EU-Level:
- Financial Services Information Sharing and Analysis Centre (FS-ISAC)
- EU Agency for Cybersecurity (ENISA) platforms
- ESA-coordinated sharing mechanisms
National-Level:
- National Computer Emergency Response Teams (CERTs)
- Financial sector ISACs
- NCA-facilitated forums
Implementation Roadmap by Pillar
Pillar 1: ICT Risk Management
Phase 1 (Months 1-3):
- Conduct gap assessment
- Draft ICT risk management framework
- Establish governance structure
- Initial asset inventory
Phase 2 (Months 4-6):
- Implement risk assessment processes
- Deploy monitoring and detection tools
- Develop business continuity plans
- Board approval of framework
Phase 3 (Months 7-12):
- Full framework implementation
- Training and awareness programs
- Continuous improvement processes
- Metrics and reporting
Pillar 2: Incident Management
Phase 1 (Months 1-2):
- Define incident classification criteria
- Establish reporting procedures
- Identify competent authority contact
Phase 2 (Months 3-4):
- Implement incident management system
- Develop incident response playbooks
- Train incident response team
Phase 3 (Months 5-6):
- Test incident reporting process
- Conduct tabletop exercises
- Refine classification criteria
Pillar 3: Resilience Testing
Phase 1 (Months 1-3):
- Define testing policy and scope
- Identify critical systems for testing
- Establish testing schedule
Phase 2 (Months 4-9):
- Conduct vulnerability assessments
- Perform scenario-based tests
- Execute penetration testing
Phase 3 (Months 10-12 and ongoing):
- TLPT planning (if applicable)
- Remediation of findings
- Continuous testing program
Pillar 4: Third-Party Risk
Phase 1 (Months 1-2):
- Create complete third-party register
- Assess criticality of providers
- Gap analysis on current contracts
Phase 2 (Months 3-6):
- Renegotiate contracts with DORA clauses
- Conduct due diligence on critical providers
- Develop exit strategies
Phase 3 (Months 7-12):
- Implement ongoing monitoring
- Annual audits of critical providers
- Regular register updates
Pillar 5: Information Sharing
Phase 1 (Months 1-2):
- Identify relevant sharing communities
- Establish legal framework for sharing
Phase 2 (Months 3-6):
- Join FS-ISAC or similar
- Participate in threat intelligence sharing
- Integrate intelligence into defenses
Examples
# Get guidance on ICT Risk Management pillar
/dora:pillar-guidance ict-risk
# Detailed implementation guide for incident management
/dora:pillar-guidance incident-management implementation
# Evidence requirements for resilience testing
/dora:pillar-guidance resilience-testing evidence
# Overview of all 5 pillars
/dora:pillar-guidance all overview
# Third-party risk management implementation
/dora:pillar-guidance third-party-risk implementation
DORA Resilience Testing
Comprehensive guidance on DORA's digital operational resilience testing requirements, including advanced threat-led penetration testing (TLPT).
Arguments
$1- Testing type (required: general, advanced-tlpt, vulnerability, scenario, all)$2- Entity profile (optional: significant, non-significant)
Testing Framework Overview
Legal Basis: Articles 24-27 of DORA Purpose: Ensure systems can withstand, respond to, and recover from ICT-related disruptions Principle: Risk-based and proportionate approach Frequency: Regular basis with minimum annual testing
Testing Requirements by Entity Type
Significant Financial Entities
Characteristics:
- Systemically important
- Large market share
- Critical infrastructure provider
- Interconnected with financial system
Testing Requirements:
- All general testing (Article 24)
- Advanced testing (TLPT) at least every 3 years (Article 26)
- More rigorous scope and frequency
- External validation required
- TLPT based on TIBER-EU or equivalent
Non-Significant Financial Entities
Characteristics:
- Smaller market footprint
- Limited systemic importance
- Less complex operations
Testing Requirements:
- General testing (Article 24) required
- TLPT optional (but recommended)
- Proportionate scope based on risk profile
- May use simplified methodologies
- Internal testing acceptable with oversight
General Testing Requirements (Article 24)
Mandatory Testing Types
1. Vulnerability Assessments and Scans
Purpose: Identify security weaknesses in systems and applications
Scope:
- Network infrastructure
- Operating systems
- Applications and databases
- Cloud environments
- APIs and interfaces
Frequency:
- Quarterly for critical systems
- At least annually for all systems
- After significant changes
Tools:
- Automated vulnerability scanners (Nessus, Qualys, Rapid7)
- Manual testing for complex systems
- Authenticated scans for deeper analysis
Deliverables:
- Vulnerability scan reports
- Risk-rated findings (Critical, High, Medium, Low)
- Remediation recommendations
- Tracking of fixes
2. Open-Source Analysis
Purpose: Identify vulnerabilities in open-source components
Activities:
- Software composition analysis (SCA)
- Identification of known vulnerabilities (CVEs)
- License compliance review
- Dependency analysis
Tools:
- OWASP Dependency Check
- Snyk
- Black Duck
- WhiteSource
Output:
- Inventory of open-source components
- Known vulnerabilities identified
- Remediation plan for outdated/vulnerable components
3. Network Security Assessments
Purpose: Evaluate security of network infrastructure
Testing Areas:
- Firewall configurations
- Network segmentation
- Intrusion detection/prevention systems
- VPN security
- Wireless network security
- Router and switch configurations
Methods:
- Configuration reviews
- Traffic analysis
- Port scanning
- Packet inspection
Deliverables:
- Network security assessment report
- Configuration weaknesses
- Segmentation gaps
- Remediation roadmap
4. Gap Analyses
Purpose: Compare current state against desired security baseline
Frameworks:
- DORA requirements
- ISO 27001
- NIST Cybersecurity Framework
- Industry best practices
Process:
- Document current controls
- Map to framework requirements
- Identify gaps
- Prioritize remediation
Output:
- Gap analysis report
- Control maturity assessment
- Remediation priorities
- Investment roadmap
5. Physical Security Reviews
Purpose: Assess physical security of facilities and assets
Scope:
- Data center access controls
- Office premises security
- Equipment security
- Visitor management
- Environmental controls (fire, flood, HVAC)
Activities:
- Physical walkthroughs
- Access control testing
- Surveillance review
- Incident log review
Findings:
- Physical vulnerabilities
- Access control gaps
- Environmental risks
- Improvement recommendations
6. Questionnaires and Scanning Software Solutions
Purpose: Self-assessment and automated security checks
Types:
- Security control questionnaires
- Configuration scanning tools
- Compliance checklists
- Third-party risk questionnaires
Examples:
- CAIQ (Consensus Assessments Initiative Questionnaire)
- SIG (Standardized Information Gathering)
- Internal control self-assessments
- Vendor security assessments
7. Source Code Reviews
Purpose: Identify security flaws in application code
Scope (where feasible):
- Custom-developed applications
- Critical business applications
- Applications handling sensitive data
- APIs and integrations
Methods:
- Static application security testing (SAST)
- Manual code review
- Secure coding standard compliance
Tools:
- SonarQube
- Checkmarx
- Veracode
- Fortify
Findings:
- Code vulnerabilities (SQL injection, XSS, etc.)
- Insecure coding practices
- Hardcoded secrets
- Remediation guidance
8. Scenario-Based Testing
Purpose: Test response to specific incident scenarios
Scenarios:
- Ransomware attack
- DDoS (Distributed Denial of Service) attack
- Data breach
- Insider threat
- System failure
- Third-party provider outage
Methods:
- Tabletop exercises
- Simulations
- War games
- Crisis management drills
Participants:
- IT and security teams
- Business continuity team
- Crisis management team
- Senior management
- Communications team
Outputs:
- Scenario test report
- Response effectiveness assessment
- Communication gaps identified
- Plan improvements
9. Compatibility Testing
Purpose: Ensure systems interoperate correctly and securely
Testing Areas:
- System integrations
- API compatibility
- Data format compatibility
- Cross-platform functionality
- Browser/device compatibility
Approach:
- Integration testing
- Interface testing
- Regression testing
- User acceptance testing
10. Performance Testing
Purpose: Validate systems perform under stress and load
Types:
- Load testing: Normal expected load
- Stress testing: Beyond normal capacity
- Spike testing: Sudden load increases
- Endurance testing: Sustained load over time
Metrics:
- Response times
- Throughput
- Resource utilization
- Error rates
- Recovery time
Scenarios:
- Peak transaction volumes
- Market volatility surges
- End-of-day processing
- Batch job performance
11. End-to-End Testing
Purpose: Validate entire business processes and systems
Scope:
- Complete transaction flows
- Multi-system integrations
- User journeys
- Data flows across systems
Examples:
- Account opening to closure
- Trade lifecycle (order to settlement)
- Payment processing end-to-end
- Customer onboarding
Validation:
- Functional correctness
- Data integrity
- Security controls throughout
- Error handling and recovery
12. Penetration Testing
Purpose: Simulate attacks to identify exploitable vulnerabilities
Scope:
- External network perimeter
- Internal network
- Web applications
- Mobile applications
- APIs
- Social engineering (if approved)
Types:
- Black box: No prior knowledge
- Gray box: Partial knowledge
- White box: Full knowledge
Methodology:
- Reconnaissance
- Scanning and enumeration
- Exploitation
- Post-exploitation
- Reporting
Deliverables:
- Penetration test report
- Executive summary
- Detailed findings with proof of concept
- Risk ratings
- Remediation guidance
Testing Frequency and Triggers
Minimum Frequency:
- At least annually for all testing types
- More frequent for high-risk systems (quarterly/semi-annual)
Additional Testing Triggered By:
- Significant changes to ICT systems
- Infrastructure upgrades
- Application deployments
- New system implementations
- Major incidents (post-incident validation)
- Merger/acquisition integration
- Third-party changes affecting critical services
Risk-Based Prioritization:
- Critical systems: Quarterly testing
- Important systems: Semi-annual testing
- Standard systems: Annual testing
- Low-risk systems: Biennial acceptable (with justification)
Advanced Testing - TLPT (Articles 26-27)
Threat-Led Penetration Testing (TLPT) Overview
Definition: Sophisticated, intelligence-led testing simulating real-world attack scenarios by actual threat actors
Applicability:
- Mandatory for significant entities
- At least every 3 years
- May be required more frequently based on risk
Framework: Based on TIBER-EU (Threat Intelligence-Based Ethical Red Teaming) or equivalent national frameworks
TIBER-EU Framework
Developed By: European Central Bank (ECB) Purpose: Harmonized approach to TLPT across EU Adoption: Required for DORA compliance (or equivalent framework)
Key Principles:
- Intelligence-led: Based on real threat actors and TTPs
- Bespoke: Tailored to entity's environment
- Controlled: Managed process with oversight
- Safe: No disruption to live services
- Documented: Comprehensive reporting
TLPT Roles
1. White Team
Role: Coordination and oversight
Responsibilities:
- Manage overall TLPT process
- Coordinate between red and blue teams
- Ensure rules of engagement followed
- Manage escalations
- Document process
- Oversee closure phase
Composition:
- Internal staff from security, risk, compliance
- May include external facilitator
2. Red Team
Role: Simulate adversary attacks
Responsibilities:
- Execute attack scenarios
- Use real-world TTPs (Tactics, Techniques, Procedures)
- Test technical controls
- Test people and processes
- Document findings
- Brief on techniques used
Composition:
- Must be external and independent
- Certified ethical hackers
- Threat intelligence experts
- Social engineering specialists (if in scope)
Requirements:
- Proven expertise in penetration testing
- Knowledge of threat actor TTPs
- Experience with TIBER-EU or similar
- Appropriate certifications (OSCP, CREST, etc.)
- Professional indemnity insurance
3. Blue Team
Role: Detect and respond to attacks
Responsibilities:
- Operate as usual (unaware of timing)
- Detect attack indicators
- Respond to incidents
- Execute defensive procedures
- Document response
Composition:
- Internal security operations team
- Incident response team
- SOC (Security Operations Center)
Critical Point: Blue team should not know when testing occurs (blind testing for realism)
4. Purple Team (Optional)
Role: Collaboration and learning
Activities:
- Post-test review
- Share red team techniques
- Analyze blue team response
- Identify detection gaps
- Enhance defensive capabilities
TLPT Process Phases
Phase 1: Preparation (2-4 months)
Activities:
-
Scoping:
- Define critical functions and services
- Identify in-scope systems
- Determine threat scenarios
- Establish boundaries (what's off-limits)
- Define success criteria
-
Threat Intelligence Gathering:
- Identify relevant threat actors
- Research TTPs used by those actors
- Open-source intelligence (OSINT)
- Dark web reconnaissance
- Sector-specific threats
-
Scenario Development:
- Create realistic attack scenarios
- Map scenarios to threat actors
- Define objectives for each scenario
- Align with critical functions
-
Rules of Engagement:
- Define what red team can/cannot do
- Establish communication protocols
- Define escalation procedures
- Set testing windows
- Emergency stop conditions
-
Red Team Selection:
- Procure external red team
- Verify qualifications and independence
- Contractual agreements
- NDA and confidentiality
-
Stakeholder Preparation:
- Brief management and board
- Prepare white team
- Ensure blue team readiness (but unaware of timing)
- Third-party provider notifications (if applicable)
Deliverables:
- Test plan document
- Threat intelligence report
- Scenario descriptions
- Rules of engagement
- Stakeholder approval
Phase 2: Testing (4-12 weeks)
Activities:
-
Reconnaissance:
- Red team gathers information about target
- OSINT, social engineering (if permitted)
- Network mapping
- Identify vulnerabilities
-
Initial Access:
- Exploit vulnerabilities
- Phishing campaigns (if approved)
- Physical intrusion (if in scope)
- Gain foothold in environment
-
Persistence:
- Establish persistent access
- Deploy backdoors
- Create rogue accounts
- Evade detection
-
Privilege Escalation:
- Elevate privileges
- Compromise credentials
- Exploit misconfigurations
- Lateral movement
-
Achieving Objectives:
- Access target systems/data
- Simulate data exfiltration
- Demonstrate impact
- Test incident response
-
Blue Team Response:
- Detection of attack indicators (or lack thereof)
- Incident response activation
- Containment efforts
- Investigation and analysis
-
White Team Monitoring:
- Track red team activities
- Monitor blue team response
- Document observations
- Manage any issues
Timing:
- Typically 4-8 weeks of active testing
- May be intermittent (not continuous)
- Blue team not told when testing occurs
Safety Measures:
- Red team stays within rules of engagement
- White team monitors for unintended impacts
- Emergency stop procedures if needed
- No actual data exfiltration or destruction
Phase 3: Closure (1-2 months)
Activities:
-
Debriefing:
- Red team reveals activities
- Blue team shares detection/response
- Discussion of gaps and successes
- Collaborative learning (purple team session)
-
Reporting:
- Red team test report
- Blue team response analysis
- White team observations
- Executive summary
-
Remediation Planning:
- Prioritize findings
- Assign remediation owners
- Define timelines
- Allocate resources
-
Lessons Learned:
- What worked well
- What needs improvement
- Process enhancements
- Training needs
-
Regulatory Reporting:
- Report TLPT execution to NCA
- Share high-level findings if requested
- Demonstrate compliance with DORA Article 26
-
Cleanup:
- Remove red team access
- Close backdoors
- Restore configurations
- Verify environment integrity
Deliverables:
- Comprehensive test report
- Remediation plan
- Lessons learned document
- Management/board briefing
- Regulatory submission
TLPT Scope Considerations
Must Include:
- Critical functions and services
- Crown jewel data/systems
- Key dependencies
- Third-party connections (if material)
May Exclude (with justification):
- Low-risk systems
- Recently tested systems (under 3 years)
- Systems covered by inherited TLPT results (e.g., cloud provider)
- Systems being decommissioned
Third-Party Involvement:
- If critical ICT provider, may need to coordinate testing
- Provider may conduct own TLPT that entity can leverage
- Ensure contractual rights to test third-party connections
TLPT Remediation
Remediation Requirements:
- Address critical findings immediately
- Remediate high-risk findings within defined timeline
- Track remediation progress
- Validate fixes effective
- Report to management and board
Typical Timeline:
- Critical: 30 days
- High: 90 days
- Medium: 6 months
- Low: 12 months or next TLPT cycle
Validation:
- Retest critical findings
- Verify controls effective
- Update documentation
- Confirm with NCA if required
Testing Documentation
Testing Policy
Required Elements:
- Testing objectives and scope
- Frequency and triggers
- Roles and responsibilities
- Testing methodologies
- Reporting and escalation
- Remediation processes
- TLPT framework (if applicable)
Test Plans
Required Elements:
- Test scope and objectives
- Systems/applications in scope
- Testing methodology
- Schedule and timeline
- Roles and responsibilities
- Success criteria
- Risks and mitigations
Test Reports
Required Elements:
- Executive summary
- Scope and methodology
- Findings and risk ratings
- Evidence (screenshots, logs)
- Recommendations
- Remediation plan
Remediation Tracking
Required Elements:
- Finding description
- Risk rating
- Assigned owner
- Remediation plan
- Due date
- Status
- Validation evidence
Testing Best Practices
Planning
- Conduct testing at appropriate intervals
- Align testing with risk profile
- Engage qualified testers (internal or external)
- Obtain management approval for testing
- Coordinate with third-party providers if needed
Execution
- Follow documented test plans
- Preserve evidence of testing
- Document findings in real-time
- Minimize impact on live services
- Communicate with stakeholders during testing
Reporting
- Provide clear, actionable findings
- Risk-rate all findings
- Include evidence and proof-of-concept
- Make remediation recommendations
- Brief management on critical findings
Remediation
- Prioritize based on risk
- Assign clear ownership
- Track remediation progress
- Validate fixes effective
- Report completion to stakeholders
Continuous Improvement
- Analyze trends across tests
- Update testing methodologies
- Enhance controls based on findings
- Train staff on lessons learned
- Share insights across organization
Testing Cost Estimates
General Testing (Annual)
- Small Entity: EUR 20K - 50K
- Medium Entity: EUR 50K - 150K
- Large Entity: EUR 150K - 500K+
Costs include tools, external testing services, internal effort
TLPT (Every 3 Years)
- Small Entity: EUR 100K - 200K
- Medium Entity: EUR 200K - 500K
- Large Entity: EUR 500K - 1M+
Costs include red team, threat intelligence, white team facilitation, remediation
Cost Drivers:
- Scope and complexity
- Internal vs. external resources
- Testing frequency
- Remediation effort
- Tools and technology
Examples
# Create comprehensive testing plan
/dora:testing-plan all
# Plan TLPT for significant entity
/dora:testing-plan advanced-tlpt significant
# Guidance on vulnerability assessment program
/dora:testing-plan vulnerability
# Scenario-based testing guidance
/dora:testing-plan scenario
# Testing plan for non-significant entity
/dora:testing-plan general non-significant
Sponsors
Details
- Marketplace
- GRCEngClub/claude-grc-engineering
- Source
- plugins/frameworks/dora
- Category
- Community
More from GRCEngClub/claude-grc-engineering
All 70- drata-inspectorv0.1.0
- essential8v0.1.0
- eu-nis2v0.1.0
- fedramp-20xv0.1.0
- fedramp-rev5v0.1.0
- fedramp-sspv0.1.0
- gcp-docsv0.1.0
- gcp-inspectorv0.1.0
- gcp-secret-metadatav0.1.0
- gdprv0.1.0
- github-inspectorv0.1.0
- glbav0.1.0
- grc-auditorv0.1.0
- grc-diagramsv0.1.0
- grc-engineerv0.1.0
- grc-internalv0.1.0
- grc-loopv0.1.0
- grc-portfoliov0.1.0
- grc-reporterv0.1.0
- grc-tprmv0.1.0
- hitrustv0.1.0
- ind-dpdpav0.1.0
- irapv0.1.0
- ismapv0.1.0
