Administration

IT Risk Prioritisation Agent

Almost everything is rated high. Management still wants to hear three names.

Prioritises by actual exposure rather than protection requirement and delivers the top risks for management.

Open agent
Public administration

Four processes that take up the most time today

Developed in Germany · Hosted in the EU

Developed in Germany · Hosted in the EU or on-premises

Delivered together with

STACKIT Sovereign hosting in Germany, single-tenant from the first user.
Rödl Legal, tax and compliance expertise for legally sound deployment.
4P Consulting Advisory and implementation for the public sector, starting with the AI readiness assessment.

A single scan finding passes through three processes before anyone has assessed it.

The scanner reports a vulnerability on a specialist application server and rates it high. Then someone asks about reachability, about protection requirement, about ownership, and the answers come from three different directions.

1scan findingA finding comes out of the vulnerability scanner marked high.
2assessmentsThe protection requirement is in the asset register; the exposure follows from the network.
3queriesThe specialist application team, operations and the service provider each answer separately.
4working daysThat is how long the finding sits on the work list until the answers are in and the order is settled.

A single finding takes two assessments, three queries and four working days before the order is settled, and because the agent brings protection requirement and reachability together in one pass, that is 50% less time to prioritisation.

The 50% comes from the agent's data record and refers to the time from the list of findings to an agreed order. It is a figure from practical experience, not a series of measurements.

Three steps through the process.

After every scan run the agent sets reachability and protection requirement side by side and proposes an order; the head of department ultimately owns the risk itself.

Assess exposure

The agent pulls the findings from the vulnerability scanner and matches them against the asset register. For every finding it notes whether the system is reachable from the internet, who operates it and which specialist application depends on it.

Findings export from the scan run, 3 systems without network assignment

Select top risks

The agent sorts the findings by exposure and protection requirement and explains for the top ten why they rank where they do. Findings of equal rank are merged into one item.

Top 10 table under file reference ISB-RIS/2026/084

Produce the management report

The agent writes a summary for the head of department: three risks, one sentence each on impact, one sentence each on the next step. The full list is attached as an annex.

Leitungsvorlage_Risikolage_KW34.docx, 2 pages, list of findings as an annex

What the agent does not do.

It does not decide whether a risk is accepted, mitigated or transferred.

That rests with the head of department and the information security officer. The agent delivers the order and the reasoning behind it.

It cannot say whether a vulnerability is actually exploitable in your own network.

Operations clarifies that with the service provider on the specific system. The agent works with the scanner's rating and the protection requirement from the register.

It gives no reachability rating to a system that the network plan does not assign to a zone.

The agent reads exposure from the network plan. For the three systems listed there without an assignment, it gives only the protection requirement from the asset register and records reachability as open.

Connected systems

  • Vulnerability scanner
  • asset register
  • GRC tool

Operations

  • Deployment modelEU cloud, private cloud or on-premises
  • Data processingGDPR-compliant, no model training on your data
  • Responsible teamsInformation Security, Management, IT Governance

The questions that come up before the first meeting.

How quickly is the IT Risk Prioritisation Agent ready to use?

A pilot typically runs on your own data within 4 to 6 weeks. The agent connects to your existing systems rather than running as a separate, parallel environment.

Where is the data processed?

EU cloud, private cloud or on-premises. Processing is GDPR-compliant and models are never trained on your data. Details in the Trust Center.

Where does the figure “50% faster prioritisation” come from?

It is based on experience from comparable projects and process benchmarks, not a commitment. We work out the realistic effect for your organisation during the assessment before the pilot.

Related agents.

Intake review, case 2026/04711

Skip to content

Page footer