[non-validated] DORA SFS E / SF A: Contractual Enforceability for Critical Functions
Generated catalog draft. No operational assessment or human approval is claimed.
[non-validated] This question has unresolved selected work.
Question
[non-validated] Have ICT service contracts established documented mechanisms ensuring enforceability of core contractual rights and obligations for critical functions as required by repository topic boundaries?
Explanation
[non-validated] Do ICT service contracts include documented mechanisms ensuring legally enforceable rights and obligations for critical functions, as required by repository topic boundaries?
Criterion and evidence
Verify documented contractual provisions establishing binding jurisdiction, dispute resolution procedures, and enforceable remedies for critical ICT functions as required by repository topic boundaries (E-repository-area#keyDescription), with explicit coverage of subcontracting oversight and exit arrangements distinct from baseline contract requirements.
AI assistance prompt
Develop sixteen bounded yes/no factors for DORA: Provider contracts, subcontracting and exit. Maintain enforceable ICT contract controls, subcontracting oversight and tested exit arrangements. Cover contractual rights and obligations, service levels, locations/data access, audit/inspection rights, incident assistance, subcontracting changes and termination/exit strategies. Distinguish additional requirements for critical or important functions from baseline contract requirements. DORA article references: 28, 30. Verify entity-role applicability and current primary sources. Missing evidence stays pending; no compliance or assessment is implied.
Clarifications
What constitutes sufficient evidence for compliance?
Valid evidence requires written contracts specifying jurisdiction, binding dispute resolution procedures (e.g., arbitration), and defined legal remedies for critical function obligations validated during the review period. Non-binding memoranda or generic clauses without critical-function specificity are insufficient per repository topic boundaries (E-repository-area#keyDescription).
References
DORA: Provider contracts, subcontracting and exit