VAREXIS

VAREXIS-INDEX - Synthetic examples

Material subcontracting change

Our ICT provider proposes a new subcontractor. What must we inspect before accepting the change?

1. Establish the scope

The original /mcp find_evidence_questions searches the frozen 1,003-record population. DORA records are catalogue-only additions. Select a title/question here and retrieve its full free JSON or use get_publication_record on /mcp/catalogue with the returned record_id. No schema or search expansion.

2. Select and retrieve source evidence

Choose a question below; each full record supplies exact MCP arguments, source clauses and limitations. This example as JSON

3. Inspect the synthetic material

SUB-1 - Synthetic signed terms and notice

The contract permits the named storage service to be subcontracted. A reasonable 20-calendar-day notice period was agreed for this fictional service; notice was received 1 November and ends 21 November. This period is not a legal default.

SUB-2 - Synthetic change chronology

Provider proposes implementation on 10 November. There is no approval, the notice period has not ended, and the entity sent a risk-tolerance objection with requested modifications on 8 November.

SUB-3 - Synthetic oversight file

Direct-provider monitoring and reporting duties are allocated. The subcontractor reports to the provider; direct reporting to the financial entity is not agreed. Chain identification and resource/failure-impact assessments are incomplete.

SUB-4 - Synthetic contract annex

An audit-rights clause names only the direct provider. Subcontractor flowdown, service-specific contingency tests and evidence of enforceability are absent.

4. Compare within the evidence boundary

The outcome labels describe only this manual example. They are not engine results, regulatory findings or permissions.

supported - SUB-1

The fictional signed terms expressly permit subcontracting the named service. This documents permission for that scope only.

Source records: DORA: Define services and permitted subcontracting

Missing evidence

  • Verify executed parties, service scope and current version in any actual case.

Permitted reliance: Locate the relevant contract permission; do not approve the proposed subcontractor.

refused - SUB-1, SUB-2

Early implementation without approval is not supported. An objection and requested modifications are recorded; identify contractual remedies and resolve the objection. Silence at the end of a permitted notice period is not evidence of positive approval.

Source records: DORA: Material subcontract changes need the contractual review window; DORA: Preserve remedies for unacceptable subcontract changes

Missing evidence

  • Resolution of objection and modifications
  • Valid approval or applicable no-objection chronology
  • Executed termination-right provisions

Permitted reliance: Flag the unsupported timing. Do not issue approval, implement a change or terminate a service.

conditional - SUB-3

The described reporting allocation can support part of the review; direct subcontractor reporting to the entity is qualified by where agreed. Provider responsibilities do not remove entity monitoring duties or the need to identify the relevant chain.

Source records: DORA: Specify monitoring and reporting along the subcontract chain; DORA: Assess the financial entity's own monitoring capacity; DORA: Provider selection must assess subcontractor visibility

Missing evidence

  • Provider chain identification/notification process
  • Entity resources and failure-impact assessment
  • Service-specific monitoring evidence

Permitted reliance: Record the allocated duties and request the missing assessments.

unbound - SUB-4

Direct-provider clauses alone do not establish exercisable subcontractor rights, continuity or effective supervision throughout the chain.

Source records: DORA: Flow down access, inspection and audit rights; DORA: Flow down contingency and security requirements; DORA: Assess complex subcontracting chains and supervision

Missing evidence

  • Subcontract terms and access-rights comparison
  • Contingency/security scope and test records
  • Obstacles and supervisory assessment

Permitted reliance: List the unresolved evidence; no actual audit access, runtime control or resilience finding.

refused - Applicability negative control

This critical-function subcontracting example cannot impose the same enhanced duties on an unrelated non-critical service without a relevant scope basis, or invent a fixed periodic review frequency.

Source records: DORA: Periodic reassessment of subcontracting risks

Missing evidence

  • Applicable service/function classification and assessment scope

Permitted reliance: Explain conditional applicability; do not generalise or manufacture a review interval.

5. Hand over the gaps

The responsible change owner should obtain the executed chain terms, assessments and a defensible chronology, then take the actual decision under the contract and applicable law. This example grants no authority.

Review dates remain those of the reused records. Recheck current official texts, corrections, applicability and current service/contract evidence before actual reliance.

6. Keep free evidence separate from paid services

All DORA records, sources, hashes, navigation and these manual examples are free. Save the public JSON locally if useful.

Not established. These catalogue-only additions are outside original paid saved retrieval and Evidence Receipt. No DORA-specific product or executable profile exists.

Compare existing offers and their limits