Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    cobit risk analysis

    1

    Managing IT risk without a structured framework often leads to subjective decisions and missed threats.

    $10

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    cobit risk analysis

    cobit risk analysis

    Example session with this skill installed

    Perform a COBIT-based risk analysis for a regional bank's mobile banking app. The goal is 99.9% uptime. Recent incidents include one 2-hour DDoS last month. I have a Low risk tolerance.

    • Read your context and instructions
    • Compiled the cobit risk analysis

    I have processed the request for the regional bank's mobile banking app using the COBIT 5 for Risk methodology. I have identified evidence from your input as E1 (Uptime goal) and E2 (DDoS incident).

    COBIT Risk Analysis — Regional Bank Mobile App, 2024-05-24

    1. Version, scope and sources

    This analysis follows the COBIT 5 for Risk approach. Note that COBIT 2019 has superseded COBIT 5.

    • Scope: Mobile banking application uptime and availability.
    • Sources: E1 (User goal statement), E2 (Incident history).

    2. Governance preparation

    Preparation itemStatusEvidence
    Appetite and tolerancePartialE1 (User stated "Low")
    Risk governance bodyUnknownInformation gap — organizational validation required
    Asset inventoryPartialE1 (Mobile App)

    3. Goals and assets

    Enterprise goalIT-related goalAssetCIAEvidence
    Financial Stability99.9% Service AvailabilityMobile App DBHHHE1
    Customer TrustReal-time transaction accessAPI GatewayMHHE1

    4. Risk scenarios

    IDScenario (hazard, vulnerability, damage)Goal pairAssetOwnerEvidence
    Z1(DDoS, Insufficient bandwidth, Service outage)Financial Stability / AvailabilityAPI GatewayIT OpsE2

    5. Risk factors and estimates

    IDHazard prob.Vuln. presentExploit prob.Est. damageMax damageResilienceUtilityBasis
    Z10.801.000.800.700.900.300.50E2, Analytical estimate

    6. Risk indices and tolerance comparison

    IDEstimatedMaximumToleratedResidualRatioBand
    Z10.560.900.200.391.95High

    Arithmetic for Z1:
    Estimated Risk = Hazard (0.80) * Damage (0.70) = 0.56
    Residual Risk = Estimated (0.56) * (1 - Resilience 0.30) = 0.39
    Ratio = Residual (0.39) / Tolerated (0.20) = 1.95

    7. Risk response and accountability

    IDResponseRationale and trade-offAccountable roleLevelDecision
    Z1MitigateRatio 1.95 exceeds tolerance. Implement scrubbing.CISOManagementManagement decision required

    8. Risk profile and monitoring indicators

    RankIDResidual ratioIndicatorSourceOwnerFrequencyTargetThreshold
    1Z11.95PPS CountNetwork LogsSOCDaily<10k50k

    9. Gaps, review and next steps

    • Gaps: Lack of formal risk governance body identification.
    • Review: Validate the 0.80 hazard probability with the SOC team.

    Next steps

    1. Validate the analytical estimates for Z1 with the scenario owner.
    2. Formally define the risk governance body to oversee these findings.
    3. Review the proposed mitigation funding for DDoS scrubbing services.

    This analysis supports, and does not replace, management's risk decision and professional judgment.
    Legend:

    Analytical estimate — validation required |

    Information gap — organizational validation required |

    Management decision required

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Managing IT risk without a structured framework often leads to subjective decisions and missed threats. This skill provides a rigorous IT risk analysis following the COBIT 5 for Risk methodology to link technical hazards directly to enterprise goals.

    What it does

    • Governance preparation validates risk appetite, tolerance, and accountability structures before analysis begins.
    • Scenario registration builds a detailed register of hazards, vulnerabilities, and damage linked to specific IT-related goals.
    • Factor estimation applies 0.01 to 0.99 scales to hazard probability, vulnerability presence, and estimated damage.
    • Index calculation computes estimated, maximum, and residual risk indices using defined COBIT formulas.
    • Tolerance comparison calculates risk-to-tolerance ratios and classifies them into bands for prioritized action.
    • Response planning suggests avoid, mitigate, transfer, or accept strategies with assigned accountability levels.

    How it works

    1. Intake where the user provides organization scope, enterprise goals, asset inventory, and known incidents.
    2. Evidence mapping numbers every source to separate documented facts from analytical estimates.
    3. Analysis execution covering the goals cascade, asset CIA ratings, and scenario variable population.
    4. Validation reporting where the agent marks gaps or estimates requiring management approval.

    Frameworks & tools

    This skill is strictly grounded in the COBIT 5 for Risk framework (EDM03 and APO12 processes) as taught by Marc-André Léger. It utilizes standardized risk index formulas and indicator structures to maintain framework integrity.

    Why this beats prompting it yourself

    Generic prompts often fail to maintain the strict separation between governance and management required by COBIT. This skill enforces the evidence markers and mathematical formulas needed for an audit-ready risk register that won't hallucinate compliance or security guarantees.

    Use cases

    • Build a formal IT risk scenario register for board-level reporting.
    • Identify scenarios where residual risk exceeds tolerated levels.
    • Propose Key Risk Indicators (KRIs) for ongoing monitoring of IT assets.
    • Prepare for an IT governance review by documenting the goals cascade and accountability.

    Known limitations

    Does not assess process maturity or audit conformity. It cannot decide on risk appetite or funding. Values are risk indices, not absolute probabilities.

    Cannot decide risk appetite or funding. Does not assess COBIT process maturity. Values are indices, not absolute probabilities. Analysis is decision support only.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 5 days ago

    Permissions

    Read Files
    Listed5 days ago

    What's inside

    Frequently Asked Questions

    This skill uses the COBIT 5 framework to link technical IT hazards directly to enterprise goals, transforming subjective guesses into a mathematical risk index that is ready for board-level reporting.

    No, it is designed for any Large Language Model (LLM) that supports custom instructions or system prompts, making it compatible with ChatGPT, Claude, and specialized enterprise AI agents.

    You receive the proprietary system prompt, a structured template for evidence mapping, and a guidebook on how to input your organizational scope and asset inventory for the best results.

    While it provides the analytical framework and index calculations, it cannot set your organization's risk appetite or approve budgets; those decisions must remain with your internal governance stakeholders.

    The skill is grounded in the EDM03 and APO12 processes of COBIT 5 for Risk, ensuring every analysis follows the rigorous standards taught by industry experts like Marc-André Léger.

    The results are provided as a structured IT risk scenario register, including calculated risk-to-tolerance ratios and suggested response strategies that can be easily exported to spreadsheets or GRC tools.