Alle Artikel

Getting Started

Was ist CICDoo Erste Schritte: der Onboarding-Assistent Das Dashboard und die Infrastrukturkarte

Concepts

Produktions-, Staging- und Development-Stages Domains, Subdomains und SSL Odoo-Versionen und -Editionen (Community vs. Enterprise) Workspaces und Teamzusammenarbeit

Servers

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 server

Projects & 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 deletion

Instances & 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 Deployments und die Job-Warteschlange

Agent 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 filters

Monitoring & 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 activity

Account & Security

Zwei-Faktor-Authentifizierung (2FA) Profil- und Integrationseinstellungen Passwörter und Kontowiederherstellung Instance security score and checks The Security page: every instance and member at a glance

Billing & Plans

Tarife und Preise Dein Abonnement upgraden und verwalten Wenn ein Projekt-Abonnement unbezahlt bleibt Das Channel-Partner-Programm Onboarding a client as a partner

Support & Tickets

Ein Support-Ticket eröffnen Hilfe vom CICDoo-Team erhalten

Troubleshooting

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-Probleme

Konto & Sicherheit

The Security page: every instance and member at a glance

How to use the workspace Security page to compare every instance's security grade, run scans, and review your team's 2FA, SSH keys, API tokens and sign-in history, plus security ratings on cluster pages.

What the Security page shows

The Security page brings the security of the whole workspace onto one page: the grade of every Odoo instance, and how well the people who manage them are protected. It has four parts:

  • Instances: every instance you can see, with its score and grade, worst first.
  • People and access: two-factor authentication, SSH keys and API tokens of the people in the workspace.
  • Sign-ins, last 30 days: who signed in to CICDoo, how, and from where.
  • Connect As, last 30 days: who opened Odoo sessions through Connect As, and how often.

For what each instance check means, see Instance security score and checks.

Who can see it

  • The workspace owner and admins always see it.
  • Other members need View the audit log. Without it, Security does not appear in the menu. See Member permissions and resource access.
  • The Instances list only shows instances on which the member also holds Instance settings.

Open the Security page

  1. Click Security in the left menu.
  2. In Instances, each row shows the project, its stage, the branch, the grade and how many checks fail at each severity. Instances with the lowest score come first.
  3. Click a row to open that instance's Security tab with every check and its fix.
  4. If there are many instances, use the page controls at the bottom.

A row may also show:

  • Database not scanned yet: the instance has not been scanned, so its database checks are unknown and the grade may be too high.
  • Scan queued: a scan was requested and is waiting for the server to pick it up, usually within a minute or two.
  • Scanning: the scan is running.

Run a scan now

Scans run daily and after every restart and upgrade. To scan on demand:

  1. To scan one instance, click the round arrow button at the end of its row (Run security scan).
  2. To scan every instance on the page, click Scan all at the top of the Instances card.
  3. The rows show Scan queued, then Scanning. Reload the page after a few minutes to see the new results.

A scan only reads the database. It does not restart the instance or change anything.

People and access

This card has its own grade and three checks:

  • Members without two-factor authentication (high): people with access to the workspace who sign in to CICDoo with a password alone. Each person turns it on under Settings, Security in their own account. See Two-factor authentication (2FA).
  • SSH keys without an expiry date (low): keys that never expire. Re-add long-lived keys with an expiry date under Settings, Security.
  • API tokens (low): tokens that never expire, or that have not been used for 90 days. Revoke unused ones under Settings, Security.

Below the checks, a table lists every member, whether two-factor authentication is On or Off, and when they last signed in.

Sign-in history

Sign-ins, last 30 days lists every sign-in to CICDoo by people in the workspace:

  • When it happened and which Member it was.
  • Result: green for a successful sign-in, with the method (Password, Google, GitHub or Email link), and red for a failed one (Wrong password or Wrong 2FA code).
  • IP address, partly masked. New IP marks a successful sign-in from an address that person had not used in the previous 30 days.

The card header shows how many sign-ins failed in the period. A burst of failures for one person, or a New IP nobody expected, is worth a question to that member.

Security on a cluster page

On a high-availability cluster's page, the Nodes card shows a security grade for each node and a rating for the whole cluster. The cluster's rating is the grade of its weakest node, because every node is a way in. Click it to open that node's Security tab. Not fully scanned means some node has not been scanned yet, so the rating may be too high. Click Scan cluster to scan every node at once. See High availability with app nodes.

Related: Instance security score and checks, Audit log and server activity, Two-factor authentication (2FA), Member permissions and resource access.

If you get stuck, open a support ticket from the Tickets page or the chat widget.

Zurück Instance security score and checks Weiter Was Agent-Aufgaben sind

Kommst du nicht weiter? Erstelle ein Ticket in der App oder sprich mit einem Techniker.