---
title: 'Explain risk analysis through a departmental application'
url: 'https://ctg.gmbh/en/wissen/informationssicherheit/risikoanalyse-praxisbeispiel'
markdown: 'https://ctg.gmbh/en/wissen/informationssicherheit/risikoanalyse-praxisbeispiel.md'
lang: en
date: '2026-11-14'
description: 'Separate causes, possible events and concrete consequences. A fictional reporting example shows how a protection weakness becomes an assessable risk scenario.'
taxonomy:
  category:
    - Practice
---

# Explain risk analysis through a departmental application

Risk analysis starts with the task that needs to work reliably. Our explicitly fictional example is an application producing a monthly receivables report. The department needs an accurate, timely overview to follow up overdue payments. Missing items or the wrong ordering could delay legitimate collection activity.

## Describe a specific scenario

Assume that a source export is accepted without an independent control total. An employee might accidentally select the previous month's export. The application could produce a plausible but outdated report, causing staff to follow up newly overdue receivables too late. This describes a possible effect on a named business process. Both the event and the scale of its consequence remain uncertain.

A suitable risk title is “Outdated source export delays receivables follow-up”. The missing control total describes an assumed weakness. Selecting the wrong export is a possible trigger. Delayed processing and its concrete business effects form the consequence. A missing document alone would not yet describe a risk scenario.

## Distinguish current protection from planned treatment

Initially, our example contains no evidenced protection against this mix-up. A planned reporting-period check must not reduce the current assessment. Its actual effect can be considered after implementation shows that the wrong month is rejected. Record the application release, input, expected rejection and observed result.

Assess the scenario with the business owner. That person needs to understand how the mix-up might occur and which deadlines, amounts or activities would be affected. An invented probability or arbitrary matrix cannot replace this discussion.

## Turn the scenario into a decision

One treatment option checks the reporting period and input completeness before processing begins. Then decide whether the remaining uncertainty is acceptable for the process. Record the responsible person and the next review trigger. Reconsider the scenario when the data source changes.

This worked method does not claim that the example application conforms to a standard. The [BSI risk analysis article](https://ctg.gmbh/en/wissen/informationssicherheit/bsi-risikoanalyse) explains its methodological context. [Grassroot IT](https://grassroot.it/en) addresses developing and operating departmental applications, while the [framework comparison](https://ctg.gmbh/en/wissen/standards/iso-27001-it-grundschutz-nist-csf) explains the wider management context.

---

## Navigation

- Parent: [Information security](https://ctg.gmbh/en/wissen/informationssicherheit.md)
- Previous: [BSI 200-3: assess risks transparently](https://ctg.gmbh/en/wissen/informationssicherheit/bsi-risikoanalyse.md)
