All Collections
Setting up container scanning
Detecting outdated runtimes using Aikido
Detecting outdated runtimes using Aikido
Willem Delbare avatar
Written by Willem Delbare
Updated over a week ago

Runtimes we monitor

Once you connected your docker registry, Aikido will start monitoring important runtimes.

Examples of monitored runtimes are:

  • Python language runtime

  • Node.js language runtime

  • PHP language runtime

  • Apache webserver

  • Nginx webserver

  • ..

We monitor these specific runtimes because they can have a big impact or are usually exposed to the web.

Status overview of Runtimes

Our Runtime Overview page will give an overview of all runtimes. Different statuses are shown per monitored runtime.

  • Outdated: This status indicates that the runtime has deprecated and is no longer maintained.

  • Almost Out-of-Date: Assigned when a runtime is nearing the deprecation date, specifically when it will expire in 30 days.

  • Up-to-Date: This status confirms that the runtime is current and fully updated.

  • Not Found: This status is given when no runtime is found after Aikido scanning.

You can view the list of monitored runtimes in Aikido by clicking here.

Alerts in the feed

Once we detect a specific package version is no longer maintained by the vendor, Aikido will send an alert to your feed.

The first alert will come 2 months before the deprecation date. As the date grows closer, the severity of the issue will become higher. The following logic is applied.

  • Low Severity: For runtimes expiring in the next 60 days.

  • Medium Severity (60): When the runtime expired within the last 30 days.

  • Lower End - High Severity - (70): If the runtime expired between 30 and 60 days ago.

  • High End - High Severity (89): For runtimes expired more than 60 days ago.

  • High End - High Severity (97): For runtimes expired more 2 years ago.

  • High End - High Severity (99): For runtimes expired more 3 years ago.

Did this answer your question?