TypingMindTypingMindThe best frontend for AI
Ict Risikomanagement logo

Ict Risikomanagement

Community
borghei
ict-risikomanagement

Aufbau eines DORA-konformen IKT-Risikomanagement-Rahmens für Finanzunternehmen – Governance Art. 5, Risikomanagement-Rahmen Art. 6, IKT-Systeme Art. 7, Identifikation Art. 8, Schutz Art. 9, Erkennung Art. 10, Reaktion und Wiederherstellung Art. 11, Lernen Art. 13. Use when ein Finanzunternehmen die DORA-Governance aufsetzt oder eine Gap-Analyse zum bestehenden BAIT/MaRisk-Rahmen durchführt.

Overview

Publisherborghei
RepositoryAI-Skills-German-Law
Skill nameict-risikomanagement
Stars
51
Forks
8
Bundled files
1
Links
Skill sourceRepositoryHomepage
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by borghei on GitHub. Read the source before you install it.

Installation

Install the Ict Risikomanagement AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/borghei/AI-Skills-German-Law/tree/main/dora/skills/ict-risikomanagement
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/borghei/AI-Skills-German-Law.git /tmp/AI-Skills-German-Law
mkdir -p .claude/skills
cp -r /tmp/AI-Skills-German-Law/dora/skills/ict-risikomanagement .claude/skills/ict-risikomanagement
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Ict Risikomanagement in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Ict Risikomanagement on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Ict Risikomanagement is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

/dora:ict-risikomanagement

Zweck

DORA ist die zentrale EU-Cyber-Resilienzverordnung für den Finanzsektor. Bestehende BAIT/MaRisk-Strukturen sind nicht automatisch DORA-konform — die Pflichten reichen tiefer (insb. Drittparteien-Register, TLPT, Incident Reporting). Dieser Skill liefert die Gap-Analyse + Roadmap.

Eingaben

  • Art des Finanzunternehmens (CRR-Institut, Versicherer, KAGB-KVG, Krypto-Dienstleister, Zahlungsinstitut etc.)
  • Größenklassen-Einordnung (Art. 16: Mikrounternehmen vs. größere)
  • Bestehende Rahmenwerke (BAIT, VAIT, KAIT, ZAIT, MaRisk)
  • IKT-Drittparteien-Liste
  • Letzter Penetrationstest

Ablauf

1. Geltungsbereich (Art. 2 DORA)

DORA gilt insbesondere für:

  • Kreditinstitute, Zahlungs- und E-Geld-Institute
  • Wertpapierfirmen, Handelsplätze, Zentralverwahrer
  • Versicherer und Rückversicherer, Versicherungsvermittler
  • KAGB-Kapitalverwaltungsgesellschaften
  • Krypto-Dienstleister (CASP) seit MiCA
  • Crowdfunding-Dienstleister

2. Verhältnis zu BAIT/MaRisk

  • BAIT/VAIT/KAIT/ZAIT bleiben anwendbar, ergänzen DORA.
  • Wo Konflikt: DORA hat Vorrang als unmittelbar geltende EU-VO.
  • BaFin hat DORA-Auslegungshinweise veröffentlicht; nationale Konkretisierung verbleibt.

3. Governance (Art. 5)

  • Leitungsorgan trägt letztverantwortlich für IKT-Risikomanagement.
  • Schulung der Leitung verpflichtend (Art. 5 Abs. 4).
  • Strategie für digitale operationale Resilienz (Art. 6 Abs. 8).

4. IKT-Risikomanagement-Rahmen (Art. 6)

Sechs Säulen:

SäuleArtikelInhalt
Strategie und GovernanceArt. 5–6Top-down, mit Budget
IdentifikationArt. 8Inventar IKT-Vermögenswerte, Funktionsbedeutung
Schutz / PräventionArt. 9Identitäts-/Zugriffsmanagement, Verschlüsselung, Patching, Backup
ErkennungArt. 10Monitoring, Alarmierung, Eskalation
Reaktion & WiederherstellungArt. 11–12Business Continuity Plan, Recovery Time Objective
LernenArt. 13Post-Incident-Reviews, Verbesserungsmaßnahmen

5. IKT-Vorfallsmanagement (Art. 17–23)

  • Klassifizierung nach Schwere (Art. 18) — RTS 2024/1772 definiert Schwellen
  • Frühwarnung binnen Stunden, Erstmeldung, Endbericht
  • Anlaufstelle: BaFin

6. Tests (Art. 24–27)

  • Regelmäßige Tests mindestens jährlich (Art. 24, 25)
  • Threat-Led Penetration Testing (TLPT) nach Art. 26 DORA — für signifikante Institute alle 3 Jahre
  • Tester-Akkreditierung nach Art. 27 DORA

7. Drittparteien (Art. 28–30)

  • Register aller IKT-Drittparteienvereinbarungen
  • Kritische Funktionen verlangen Vertragsmindestinhalte (Art. 30)
  • BaFin / EBA-Reporting

8. Information Sharing (Art. 45)

Freiwillige Vereinbarungen über Cyber-Bedrohungsinformationen unter Finanzunternehmen.

Quellen

Statute

Verzahnung

Sekundärliteratur

  • Linke, in: Hellner/Steuer, Bankrecht und Bankpraxis, DORA-Kapitel
  • BeckOK DORA (Online)
  • DORA-Kommentar von Maume/Maute/Fromberger (in Vorbereitung)

Ausgabeformat

DORA IKT-RISIKOMANAGEMENT — Gap-Analyse — <Mandant> — <Datum>

I.    Geltungsbereich (Art. 2)        [Ja — Institutsklasse / Mikro nach Art. 16]
II.   Verhältnis zu BAIT/MaRisk       [bestehend / Gap-Liste]
III.  Säulen-Reife
      Governance Art. 5                [🟢 / 🟡 / 🔴]
      Identifikation Art. 8             [🟢 / 🟡 / 🔴]
      Schutz Art. 9                     [🟢 / 🟡 / 🔴]
      Erkennung Art. 10                 [🟢 / 🟡 / 🔴]
      Reaktion / Wiederherstellung Art. 11–12  [🟢 / 🟡 / 🔴]
      Lernen Art. 13                    [🟢 / 🟡 / 🔴]
IV.   Vorfallsmanagement (Art. 17–23)  [Reifegrad / Lücken]
V.    Tests / TLPT (Art. 24–27)         [Letzter / nächster Test]
VI.   Drittparteien-Register (Art. 28) [vollständig / unvollständig]

Roadmap:
  Q1: <…>
  Q2: <…>

Bußgeldrisiko: Bei wesentlichen Verstößen — bis 1 % des durchschnittlichen Tagesumsatzes pro Tag.

Risiken / typische Fehler

  • BAIT als DORA-Ersatz angesehen — Pflichten gehen über BAIT hinaus.
  • TLPT-Pflicht übersehen — signifikante Institute werden alle 3 Jahre getestet, Akkreditierung der Tester verlangt.
  • Drittparteien-Register unvollständig — alle IKT-Dienstleister, nicht nur kritische.
  • Leitungsorgan-Schulung vernachlässigt — Art. 5 Abs. 4 ist Pflicht.
  • Doppelmeldung NIS2/DSGVO/DORA vergessen — bei IKT-Vorfall mit personenbezogenen Daten greifen ggf. drei Meldepflichten.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Ict Risikomanagement AI skill do?

Aufbau eines DORA-konformen IKT-Risikomanagement-Rahmens für Finanzunternehmen – Governance Art. 5, Risikomanagement-Rahmen Art. 6, IKT-Systeme Art. 7, Identifikation Art. 8, Schutz Art. 9, Erkennung Art. 10, Reaktion und Wiederherstellung Art. 11, Lernen Art. 13. Use when ein Finanzunternehmen die DORA-Governance aufsetzt oder eine Gap-Analyse zum bestehenden BAIT/MaRisk-Rahmen durchführt.

Why use Ict Risikomanagement on TypingMind?

Because you install it once and use it with any model. Ict Risikomanagement is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Ict Risikomanagement in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/borghei/AI-Skills-German-Law/tree/main/dora/skills/ict-risikomanagement. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Ict Risikomanagement?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Ict Risikomanagement?

As many as you like. As long as a model supports skills, you can use Ict Risikomanagement with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Ict Risikomanagement AI skill free?

It is published on GitHub by borghei. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
anthropics logo

Internal Comms

anthropics
OrganizationPopular

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal…

21.8K
184K
4 files
View
anthropics logo

Claude Opus 4 5 Migration

anthropics
OrganizationPopular

Migrate prompts and code from Claude Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5. Use when the user wants to update their codebase, prompts, or API calls to use Opus 4.5. Handles model string…

23.8K
146.3K
2 files
View
vercel logo

Deploy Release Test

vercel
OrganizationPopular

Validate a commit-specific Next.js preview package and manually trigger the entire Next.js deployment test suite through the test_e2e_deploy_release.yml GitHub Actions workflow. Use only when asked to…

34.7K
143.1K
1 files
View
vercel logo

Insight Error Page

vercel
OrganizationPopular

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new `errors/<slug>.mdx` page, auditing an existing one, or checking that a page matches the framework fix…

34.7K
143.1K
Instructions
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇