Works with the AI Agents you already use
cobit risk analysis
Managing IT risk without a structured framework often leads to subjective decisions and missed threats.
$10
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 item | Status | Evidence |
|---|---|---|
| Appetite and tolerance | Partial | E1 (User stated "Low") |
| Risk governance body | Unknown | Information gap — organizational validation required |
| Asset inventory | Partial | E1 (Mobile App) |
3. Goals and assets
| Enterprise goal | IT-related goal | Asset | C | I | A | Evidence |
|---|---|---|---|---|---|---|
| Financial Stability | 99.9% Service Availability | Mobile App DB | H | H | H | E1 |
| Customer Trust | Real-time transaction access | API Gateway | M | H | H | E1 |
4. Risk scenarios
| ID | Scenario (hazard, vulnerability, damage) | Goal pair | Asset | Owner | Evidence |
|---|---|---|---|---|---|
| Z1 | (DDoS, Insufficient bandwidth, Service outage) | Financial Stability / Availability | API Gateway | IT Ops | E2 |
5. Risk factors and estimates
| ID | Hazard prob. | Vuln. present | Exploit prob. | Est. damage | Max damage | Resilience | Utility | Basis |
|---|---|---|---|---|---|---|---|---|
| Z1 | 0.80 | 1.00 | 0.80 | 0.70 | 0.90 | 0.30 | 0.50 | E2, Analytical estimate |
6. Risk indices and tolerance comparison
| ID | Estimated | Maximum | Tolerated | Residual | Ratio | Band |
|---|---|---|---|---|---|---|
| Z1 | 0.56 | 0.90 | 0.20 | 0.39 | 1.95 | High |
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
| ID | Response | Rationale and trade-off | Accountable role | Level | Decision |
|---|---|---|---|---|---|
| Z1 | Mitigate | Ratio 1.95 exceeds tolerance. Implement scrubbing. | CISO | Management | Management decision required |
8. Risk profile and monitoring indicators
| Rank | ID | Residual ratio | Indicator | Source | Owner | Frequency | Target | Threshold |
|---|---|---|---|---|---|---|---|---|
| 1 | Z1 | 1.95 | PPS Count | Network Logs | SOC | Daily | <10k | 50k |
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
- Validate the analytical estimates for Z1 with the scenario owner.
- Formally define the risk governance body to oversee these findings.
- 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
- Intake where the user provides organization scope, enterprise goals, asset inventory, and known incidents.
- Evidence mapping numbers every source to separate documented facts from analytical estimates.
- Analysis execution covering the goals cascade, asset CIA ratings, and scenario variable population.
- 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.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse All Claude Skills.
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
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
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
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