agentleFS
kaandgnshkaandgnsh/Claude-Blue/skills/business-continuity/critical-service-mapping/SKILL.md

critical-service-mapping

Skill0 starsChanged 15 days agoMITView on GitHub

Map critical business services to their technical dependencies — applications, data stores, identity, network, cloud services, third parties, people — with impact tolerances (RTO/RPO, maximum tolerable downtime) to drive recovery order, security priorities and asset criticality. Use for business impact analysis, ransomware recovery planning, DORA/operational resilience work, or prioritizing protection of crown jewels.

The file

Files
SKILL.md

Critical Service Mapping

Steps

  1. Identify important business services (customer-facing outcomes: "take card payments", "ship orders", "pay employees"), not systems.
  2. Impact tolerances per service from business owners: maximum tolerable downtime, RTO, RPO, peak periods, regulatory/contractual obligations.
  3. Map dependencies (use CMDB, cloud resource graphs, APM/service maps, interviews):
    • Applications and their components
    • Data stores and integrations (queues, APIs, file transfers)
    • Identity (AD, IdP, PKI) — almost everything depends on it
    • Infrastructure (DNS, network, hypervisors, cloud regions/accounts)
    • Third parties (payment gateways, SaaS, MSPs)
    • Key people/roles and manual workarounds
  4. Find single points of failure and shared dependencies (one AD forest, one region, one vendor).
  5. Assign criticality tiers and feed: recovery order (ransomware-recovery), backup requirements (backup-assurance), asset criticality (asset-criticality-tiering), monitoring priorities.
  6. Review annually and on major change.

Record

Service: <name>   Owner: <>   MTD: <h>   RTO: <h>   RPO: <min>
Dependencies:
  App: <> (tier) | Data: <> | Identity: AD/Entra | Infra: <region/cluster> | Third parties: <> | People: <>
Manual workaround: <> (max duration)
SPOFs: <>
Recovery order position: <n>

Dependency discovery tips

  • Identity is a hidden dependency of nearly every service: if AD/Entra/Okta is down or untrusted, list which services still work (local accounts, break-glass) and which do not.
  • Time, DNS and certificates: NTP, internal DNS and PKI outages break authentication and TLS across services.
  • Licensing and SaaS back-ends: on-prem applications that phone home for licences fail in isolated recovery.
  • Data flows: nightly file transfers or message queues that, if missing, silently corrupt downstream processes.
  • Validate maps in exercises (recovery-exercise): turn off a dependency in a test environment and observe what breaks.

Related skills

asset-criticality-tiering, backup-assurance, ransomware-recovery, recovery-exercise

References

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.