[T] Introduction to Autobahn

Autobahn is a web-based tool for having assets managed in it checked with different automated “scanners”, processing the results, making progress measurable/presentable and even assigning tasks. Depending on the intended use, it may not be useful to use all of these features within Autobahn. Especially in the context of this cohort

Janis König
David Fuhr
Colin Murphy
Letztes Update
03.02.2026

Overview

Autobahn is a web-based tool for having assets managed in it checked with different automated “scanners”, processing the results, making progress measurable/presentable and even assigning tasks. Depending on the intended use, it may not be useful to use all of these features within Autobahn. Especially in the context of this cohort, we will focus on scanning (the task of int³), the results and the progress, while task assignment to cohort members is done via internal tools if necessary.

Workouts, Assets & Issues

In the left sidebar, you will find the three levels of Autobahn that we can work with, or rather, that allow us to see our assets and tasks.

The unique feature of Autobahn is the workouts, and we will work primarily with these later. But let's start with the other two first: assets and issues.

Under Assets we find a table of all assets previously imported during onboarding. These may already have been deduplicated (e.g. if a specified domain resolves to an IP that is also listed). Also displayed under Source is whether these assets were independently “found” by Autobahn or manually, when this asset was last scanned, who is responsible for this asset and how the most severe issue that can be assigned to this asset is assessed.

Asset-Overview showing sample data

Let's now move on to the heart Autobahn, the workouts. Workouts combines issues sharing the same solution steps into one. This both streamlines working on issues themselves, due to the sheer reduction of the initial list, but also help actively fix problems. Say:

  1. We have 3 assets A, B and C
  2. Problem X occurs on all assets A, B and C, problem Y on A and B, and problem Z only on C.
    • With individual issues, we would now have 6 problems to address
    • …however, actually these are only 3 distinct problems distributed over 3 systems…
  3. Furthermore, both problems X and Z can be both fixed by updating the web server.
    • So with Workouts, we only have two “tasks”: updating the web server (which resolves problems X and Z on systems A—C), and fixing problem Y on A and B.

Under Setup, we can also see which of the individual Issues on which Assets are being resolved by this Workout.

However, since workouts involve a lot of manual work by Autobahn & intcube, it is possible that there is no workout for all emerging issues. In this case, please contact us directly and we will work with you to find a solution and also work to integrate it into Autobahn.

Testüberschrift

Let's now move on to the heart Autobahn, the workouts. Workouts combines issues sharing the same solution steps into one. This both streamlines working on issues themselves, due to the sheer reduction of the initial list, but also help actively fix problems. Say:

Let's now move on to the heart Autobahn, the workouts. Workouts combines issues sharing the same solution steps into one. This both streamlines working on issues themselves, due to the sheer reduction of the initial list,

H3 Überschrift

Let's now move on to the heart Autobahn, the workouts. Workouts combines issues sharing the same solution steps into one. This both streamlines working on issues themselves, due to the sheer reduction of the initial list, but also help actively fix problems. Say:

However, since workouts involve a lot of manual work by Autobahn & intcube, it is possible that there is no workout for all emerging issues. In this case, please contact us directly and we will work with you to find a solution and also work to integrate it into Autobahn.