Alle Artikel
Getting Started
Was ist CICDoo Erste Schritte: der Onboarding-Assistent Das Dashboard und die InfrastrukturkarteConcepts
Produktions-, Staging- und Development-Stages Domains, Subdomains und SSL Odoo-Versionen und -Editionen (Community vs. Enterprise) Workspaces und TeamzusammenarbeitServers
Einen Server hinzufügen Server-Domains und DNS Einen Load Balancer verwenden Über einen Jump-Server verbinden Server-Aktionen: Deploy, Logs und Diagramme Deleting a serverProjects & Git
Ein Projekt erstellen GitHub verbinden Project GitHub settings and webhook GitLab verbinden Branches und Instanzen Projekte mit Tags versehen und filtern Hochverfügbarkeit mit App-Knoten Project environments, extensions and deletionInstances & Console
Eine Instanz erstellen Eine Instanz neu starten, stoppen und entfernen Branches zwischen Stages mergen Web-IDE und Fernzugriff SSH access to instances Instanzeinstellungen erklärt E-Mails deiner Instanzen (Tab E-Mails und ausgehende E-Mails) Deployments und die Job-WarteschlangeAgent Tasks
Was Agent-Aufgaben sind Agent-Aufgaben einrichten Eine Aufgabe ausführen und das Ergebnis prüfen Agent-Zeit und Aufstockungen Agent insights and task filtersMonitoring & Backups
Deine Instanz überwachen Backups und Wiederherstellung S3 storage, uploads and bulk backup actions Warnbenachrichtigungen (E-Mail und SMS)Workspaces & Permissions
Workspace-Mitglieder einladen Mitgliederberechtigungen und Ressourcenzugriff Ein Mitglied kann eine Ressource nicht sehen oder nutzen Audit log and server activityAccount & Security
Zwei-Faktor-Authentifizierung (2FA) Profil- und Integrationseinstellungen Passwörter und Kontowiederherstellung Instance security score and checks Server security scan, vulnerabilities and security updates The Security page: every instance and member at a glanceBilling & Plans
Tarife und Preise Dein Abonnement upgraden und verwalten Wenn ein Projekt-Abonnement unbezahlt bleibt Das Channel-Partner-Programm Onboarding a client as a partnerSupport & Tickets
Ein Support-Ticket eröffnen Hilfe vom CICDoo-Team erhaltenTroubleshooting
Fehlerbehebung: Server kann nicht verbunden werden Fehlerbehebung: ein Deployment ist fehlgeschlagen Fehlerbehebung: git push schlägt mit 403 fehl nach Verschieben eines Repositorys Fehlerbehebung: meine Instanz ist ausgefallen oder langsam Fehlerbehebung: Domain- oder SSL-ProblemeKonto & Sicherheit
Server security scan, vulnerabilities and security updates
How to read a server's Security tab: the software inventory (OS, kernel, nginx, Docker, OpenSSL, OpenSSH), known vulnerabilities matched against OSV.dev, what each check means, what Apply security updates does (with or without a reboot), and Reboot server.
What the server Security tab shows
Every server has a Security tab on its page (Servers, then click the server). It tells you what software the server runs, which known vulnerabilities affect it, and what to do about them. Like the instance Security tab, it rates the server from 0 to 100 with a letter grade (A to F) and lists every check, failing ones first.
The tab has four parts:
- Server security: the score, how many checks fail at each severity, when the server was last scanned and when it was last checked against known vulnerabilities, and the Scan now, Apply security updates and Reboot server buttons.
- Software: the operating system and the date its free security updates end, the running kernel (and a newer one waiting for a reboot, if any), and the versions of nginx, Docker, containerd, runc, Docker Compose, OpenSSL, OpenSSH, PostgreSQL and Python on the server itself. It also shows how many packages are installed and how many updates are pending, security and other.
- Checks: every check with a severity, a sentence on the risk and a fix.
- Known vulnerabilities: each installed package with a known vulnerability, its version, the severity, and the advisories (CVE numbers link to their OSV.dev page) with the version that fixes each one.
After a security update has run, a Last security update card shows what it changed.
Where the software comes from
Next to each version on the Software card, a badge says who maintains it:
- Ubuntu, Debian or Ubuntu Pro (grey): the distribution's own package. The distribution backports security fixes into it without changing the main version number, so an older-looking version such as nginx 1.24.0 on Ubuntu 24.04 can be fully patched. These packages are checked for known vulnerabilities and updated by Apply security updates.
- Docker repository, nginx.org repository and other named publishers (blue): the publisher's own repository. Docker from Docker's repository is how the platform installs it. Updates come from that publisher, not the distribution's security team, so Apply security updates does not install them.
- PPA, Third-party or backports (amber): a personal or third-party repository, or the distribution's backports, which get fewer security fixes.
- Installed by hand or Not from a package (red): a package file installed manually, or a program built or copied onto the server. Nothing updates it, and it cannot be checked for known vulnerabilities.
When the repository has a newer version than the one installed, the card says so ("29.10.0 available in its repository"). Hover a badge to see the package name and the repository it came from.
Packages that do not come from the distribution are left out of the vulnerability check, because the distribution's advisories do not describe them; the Known vulnerabilities card says how many there are and lists them. Docker, containerd and runc from Docker's repository are still checked, against Docker's own advisories.
Who can see and use it
- The tab shows for everyone who can open the server (the View servers permission and access to that server).
- Scan now needs Edit server settings.
- Apply security updates and Reboot server need Deploy servers.
See Member permissions and resource access.
When the scan runs
The server scans itself once a day, and whenever you click Scan now (it starts within about a minute and takes a few seconds). It also scans right after Apply security updates finishes. The scan only reads: it never installs, removes or changes anything.
Matching against known vulnerabilities happens on the platform shortly after each scan, and again every day, because new advisories are published even when the server does not change.
If the last scan is more than 3 days old, the checks show as Not checked yet. That usually means the server is offline.
Where the vulnerability data comes from
Installed packages are matched against OSV.dev, an open vulnerability database that carries the Ubuntu and Debian security trackers and the advisories for Docker's components. Matching uses your distribution's own version numbers, so a fix that Ubuntu or Debian backported into an older version number counts as fixed. Only package names and versions are sent; nothing that identifies the server or you.
Vulnerability matching covers Ubuntu and Debian servers. On other distributions the inventory and the other checks still work.
The kernel is not listed package by package: every kernel version has hundreds of open advisories, almost all still being assessed. The kernel is covered by Reboot pending and by pending security updates instead.
What is checked
- Operating system support (critical once ended, high within 6 months): the release no longer gets, or will soon stop getting, free security updates from the distribution.
- Critical vulnerabilities with a fix available (critical), High-severity vulnerabilities with a fix available (high), Other vulnerabilities with a fix available (medium): installed packages with a known vulnerability for which the distribution already ships a fixed version. Show details lists the package, the installed and fixed versions and the CVE.
- Fixes available only with Ubuntu Pro (medium when one is high or critical, otherwise low): vulnerabilities fixed only in Ubuntu Pro (Expanded Security Maintenance), which the server does not receive. Attach the server to Ubuntu Pro, or move to a release that still gets free fixes.
- Vulnerabilities without a fix yet (advice): known vulnerabilities with no fix from the distribution yet. Nothing to install; they move up once a fix ships.
- Docker engine vulnerabilities (medium, high when one is critical): known vulnerabilities in the installed Docker, containerd or runc version.
- Docker version support (medium): Docker is older than the oldest release still getting fixes.
- Reboot pending (high when a newer kernel is installed but not running, medium for updated system libraries): security fixes in a new kernel only take effect after a reboot. Use Reboot server.
- Pending security updates (medium, low when vulnerability matching is on, since the vulnerability checks already count them): security updates the server knows about and has not installed.
- Package lists (low): the server has not refreshed its package lists for more than 7 days, so newer updates are missing from the counts.
- Automatic security updates (medium): unattended-upgrades is missing, disabled, or its daily timer is off, so fixes wait for someone to install them.
- Root login with a password (high): SSH lets root sign in with a password.
- SSH password logins (medium): SSH accepts passwords, so the server can be attacked by guessing them.
- Software from outside your distribution (medium when nginx, OpenSSH or OpenSSL is installed by hand or not from a package; low for a PPA, another third-party repository or backports; advice for a publisher's own repository such as nginx.org): key software that the distribution does not maintain. Docker from Docker's repository is expected and passes.
- Host firewall (advice): nothing on the server filters incoming traffic. Fine if your hosting provider's firewall does it.
Apply security updates
Apply security updates installs the security updates for the server's own operating system packages. The confirmation asks what to do if an update needs a reboot:
- Do not reboot (the default): the updates are installed and the server keeps running. If a reboot is needed, the result says so and Reboot pending fails until you reboot with Reboot server.
- Reboot right after the updates, only if one of them needs it: when a new kernel or system library was installed, the server reboots about a minute after the updates finish. If nothing needs a reboot, it does not reboot.
After you confirm:
- Within about a minute the server picks up the request. The button shows Updates queued, then Applying updates.
- The server refreshes its package lists. If another installation is running, it waits up to 15 minutes for it; it never interrupts one.
- It installs only the packages whose new version comes from the distribution's security updates. Your configuration files are kept.
- It reports what changed. Without a reboot it scans again straight away; with one, the server scans on its first pass after it comes back. The page refreshes by itself.
What it never does:
- It never reboots unless you chose to, and then only when an update needs it.
- It never updates Docker (docker-ce, containerd, runc). Updating Docker restarts every instance on the server, so those packages are held back and listed as held. Update them in a maintenance window.
- It never restarts services on its own. Only a service whose own package is updated restarts, for example nginx, for a second or two.
The button is unavailable while the server is offline, while an update or reboot is already running, and before the first scan. Every use is recorded in the server's Activity tab, including whether a reboot was allowed.
Reboot server
Reboot server restarts the server without installing anything, for example to activate a kernel that Reboot pending reports. Its icon turns amber when a reboot is pending.
- Click Reboot server and type
rebootto confirm. - Within about a minute the server picks up the request and restarts a minute later. The button shows Reboot queued, then Rebooting.
- Every instance on the server is offline during the reboot, usually for a few minutes. They start again on their own.
- When the server is back it scans itself, and the page refreshes with the new results.
While the server is rebooting, neither button can be used. Every reboot is recorded in the server's Activity tab.
The workspace Security page
The workspace Security page lists every server you can open in a Servers section, worst score first, with the number of failing checks at each severity. Click a server to open its Security tab. See The Security page: every instance and member at a glance.
Betreibe das mit CICDoo auf deinen eigenen Servern
Verbinde einen Server und verknüpfe dein Repository. Deployments, Backups und Monitoring sind eingerichtet, und Odoo-Ingenieure sind nur eine Nachricht entfernt.
Kommst du nicht weiter? Erstelle ein Ticket in der App oder sprich mit einem Techniker.