THE CIRCL SERVICE FOR COMPANY TEAMS

See what needs attention.
Know who can act.

Your infrastructure inventory, vulnerability reviews and responsible contacts in one workspace operated by CIRCL. See what needs attention, assign the next step and keep your team reachable.

What the vulnerabilities have to say

Development & pilot stageStart with a contact and one domain. Add inventory at your own pace.

BEARINGS / Infrastructure overview
Bearings infrastructure overview showing open reviews, coverage gaps and a server needing attention in a synthetic company.

Product view · synthetic data

InventoryEvidenceRiskResponse

Operated by CIRCL

CIRCL is Luxembourg’s CERT for the private sector and municipalities. The Law of 5 May 2026 implementing NIS2 designates CIRCL as a CSIRT; Article 9 names CIRCL as the coordinator for coordinated vulnerability disclosure. We scan for vulnerabilities and support voluntary information sharing so organizations can act earlier.

About CIRCL and its missionNIS2 law · 5 May 2026

A practical benefit for your team

Less searching across tools.
A clearer next action.

When an alert arrives, find the systems and versions you have recorded, the evidence to check and the right person to act. Start small and add the information that is useful to your company.

Prioritize

The right systems first

See urgent reviews, unknown versions and overdue actions, then open the evidence behind them.

Reach

The person who can act

Keep accountable owners and emergency contacts together. Periodic confirmation helps keep those details useful.

Reuse

The data you already have

Keep NetBox or review a CSV import. A contact and one domain or network are enough to get started.

Real problems. A little personality.

The vulnerabilities have an opinion.

Playful fictional quotes. Real CVEs. Each example shows why recorded versions and reachable contacts matter.

NGINX2Root

I was hoping your inventory stopped at “web server”. Then you wrote down the NGINX version. Awkward.

CVE-2026-123007 + 4 more CVEsFictional vulnerability quote

The real issue

NGINX2Root groups five NGINX flaws disclosed in November 2026, including CVE-2026-123007. Relevant features and configuration matter.

What your company gains

Find recorded NGINX installations and package versions, check the applicable vendor or distribution advisory, and reach the team that can update them.

Source advisory · Additional source · CIRCL analysis

Java / Java4Shell

“Somewhere there’s probably Java” used to be my favourite inventory entry. Bearings is ruining the mystery.

CVE-2026-114938Fictional vulnerability quote

The real issue

Oracle addressed CVE-2026-114938 in its 17 November 2026 update. CISA urged organizations to identify affected Java runtimes, including bundled ones.

What your company gains

Record the runtime vendor and exact build, connect it to the application and owner, then check the current vendor guidance. “Java installed” is not enough.

Source advisory · Additional source · CIRCL analysis

Cisco Secure FMC

An inventory, a named owner and follow-up? Honestly, terrible working conditions.

CVE-2026-20079Fictional vulnerability quote

The real issue

Authentication bypass in Cisco Secure FMC. Active exploitation reported in 2026; CISA listed it on 9 September.

What your company gains

Find recorded management platforms and versions, review the advisory and give the right team a concrete next step.

Source advisory · Additional source

React Server Components

Five stars for finding the right servers. Zero stars for my career prospects.

CVE-2025-55182Fictional vulnerability quote

The real issue

Unauthenticated remote code execution in React Server Components, disclosed on 3 December 2025.

What your company gains

Record component versions, not just ‘React’. Narrow the review to the installations and owners that need checking.

Source advisory

FortiCloud SSO

I was rather hoping nobody remembered which firmware was running. Bearings had other plans.

CVE-2026-24858Fictional vulnerability quote

The real issue

FortiCloud SSO authentication bypass. CERT-FR relayed active exploitation on 28 January 2026.

What your company gains

Locate recorded appliances and firmware, verify the relevant SSO configuration and reach the responsible contact.

Source advisory

Sources checked 19 November 2026. Historical examples, not a live threat feed. Check whether an installation is affected and how to address it using current vendor guidance.

Two perspectives. A connected workflow.

Useful to the company.
Actionable for CIRCL.
Good for Luxembourg.

For company teams

Which systems need our attention?

A software issue should lead to the systems that may be affected, the supporting evidence and a clear next action. Bearings groups related reviews, keeps priorities visible and records who is responsible.

  • See urgent reviews and overdue actions
  • Keep software versions and contacts current
  • Invite your team with appropriate company roles
Grouped software reviews and next actions for a fictional Luxembourg company.
Product view · synthetic data View full screenshot

For CIRCL analysts

Who may be affected, and who can act?

Explore permitted inventory across participating companies. Research a reported software version before a CVE exists, review prevalence and contact the appropriate responsible team.

  • Research software/version exposure without a CVE
  • View outstanding reviews and company locations
  • Prepare outreach with evidence and recipient review
A Luxembourg company-location heat map using synthetic demonstration data.
Product view · synthetic data View full screenshot

Company locations are approximate and may differ from server locations. The map describes participating inventory, not complete national coverage.

Start small. Build confidence over time.

A practical route into Bearings.

  1. Join or register

    Accept your company admin's invitation, or register a new company and confirm your email. CIRCL sharing is reviewed separately.

  2. Add your first useful details

    Start with a contact and one domain or network. Add inventory manually, review a CSV import or reuse an approved NetBox source.

  3. Review what matters

    Check version and coverage gaps, review vulnerability evidence and assign the next action. A match alone is not confirmed affectedness.

  4. Keep the loop alive

    Confirm data periodically, review contact responsiveness and track actions. Setup saves along the way, so your team can return later.

Create your free company workspace
A Bearings configuration wizard with section progress, a save form and synthetic company information.
Product view · synthetic data View full screenshot

THE OPTIONAL LINUX CLIENT

Your inventory keeps up. Your team gets time back.

Install once on your Linux servers. The Bearings client regularly reports software versions to the CIRCL service, so updates become visible without maintaining package lists by hand.

01

Stay current

Ubuntu, Debian and RPM package versions are collected automatically. Configured checks can also cover software installed outside the package manager.

02

Roll out once

Use a limited rollout code with your existing deployment process. Each host creates its own key and sends signed reports over HTTPS; no files need to be carried back for import.

03

Act on evidence

Bearings compares supported distribution packages with vendor security rules and separates potential issues, unresolved checks and fixes already present in the installed version.

With operator-enabled managed NetBox, hosts can also register in the correct company inventory. VM tags such as LXC, Incus, Proxmox or VMware keep the deployment type visible. Existing read-only inventories remain read-only.

Get started with the free service

Reuse the ecosystem

One place to make sense
of the tools you already use.

NetBox

Inventory

NetBox

Approved, scoped device, VM, IP and prefix imports.

Vulnerability-Lookup

Vulnerability evidence

Vulnerability-Lookup

Public product mappings and CVE evidence for review.

MOSPMONARC

Risk context

MOSP / MONARC

Public scenario definitions and reviewed company-specific business context.

MISP

Your MISP intelligence

MISP

Optional customer-owned keys; separate internal CIRCL research.

AIL

Monitoring configuration

AIL

Keyword and honeytoken export for manual import and analyst review.

FlowIntelRTRTIR

Coordination

FlowIntel · RT / RTIR

Reviewed case/ticket hand-offs with independent native permissions.

Integrations have different maturity and deployment requirements. AIL is a manual export; the MISP cache is a bounded pilot. Core company workflows do not require an account in every connected tool.

Trust comes from explicit boundaries

Clear about what the data means.

Your company's scope

Company roles and separate CIRCL sharing control infrastructure access. Personal MISP views use their owner's upstream permissions.

Known gaps stay visible

Unknown versions, stale sources and incomplete coverage do not become a green assurance badge.

People make the decisions

Risk acceptance, recipient handling and outreach require review. Bearings does not install patches or turn every match into an incident.

A few practical answers

Before you get started.

Read all frequently asked questions
Who operates the Bearings service?

This Bearings installation is operated by CIRCL. CIRCL is Luxembourg’s CERT for the private sector and municipalities. The Law of 5 May 2026 implementing NIS2 designates CIRCL as a CSIRT; Article 9 names CIRCL as the coordinator for coordinated vulnerability disclosure. We scan for vulnerabilities and support voluntary information sharing so organizations can act earlier.

Is Bearings free to use?

Yes. The CIRCL-operated Bearings service is free and will remain free, including continued use after registration. Start with a responsible contact and one domain or network, then add details over time. Colleagues can join by invitation. Optional external tools have their own account and operating requirements.

Do I need a complete inventory to get started?

No. Start with a responsible contact and one domain, IP address or network. Add hardware, software and versions over time. A resumable setup guide and individual editors let you continue later. Unknown or missing data remains visible as a coverage gap.

Does a CVE match mean a server needs a patch?

A match starts a review. A product name or a high CVSS score alone does not prove that a particular installation is affected. Review the version, exposure and evidence, assign responsibility, and record the tested action. Bearings does not install patches or infer successful remediation from an empty issue list.

Is Bearings ready for production?

Bearings is a development and pilot project with automated tests and synthetic reference deployments. Tests with 40,000 companies and 1.2 million assets passed within the documented resource and workload limits. This is not a production approval: sustained testing on the intended deployment, real-service permissions and versions, operational email delivery, monitored jobs, backup/restore, retention and native-account revocation still require validation.

BEARINGS · AGPL-3.0-OR-LATER

Your first step is free. So is every step after.

Register with CIRCL, confirm your email and add a responsible contact plus one domain or network. Your private company workspace opens after confirmation; sharing with CIRCL is reviewed separately.