すべての記事

Getting Started

CICDoo とは はじめに: オンボーディングウィザード ダッシュボードとインフラマップ

Concepts

本番、ステージング、開発の各ステージ ドメイン、サブドメイン、SSL Odoo のバージョンとエディション（Community と Enterprise） ワークスペースとチームでの共同作業

Servers

サーバーの追加 サーバーのドメインと DNS ロードバランサーを使う 踏み台サーバー経由で接続する サーバーの操作: デプロイ、ログ、チャート Deleting a server

Projects & Git

プロジェクトの作成 GitHub の接続 Project GitHub settings and webhook GitLab の接続 ブランチとインスタンス プロジェクトのタグ付けと絞り込み アプリノードによる高可用性 Project environments, extensions and deletion

Instances & Console

インスタンスの作成 インスタンスの再起動、停止、削除 ステージ間でのブランチのマージ Web IDE とリモートアクセス SSH access to instances インスタンス設定の説明 デプロイとジョブキュー

Agent Tasks

エージェントタスクとは エージェントタスクの設定 タスクの実行と結果の確認 エージェント時間と追加購入 Agent insights and task filters

Monitoring & Backups

インスタンスのモニタリング バックアップと復元 S3 storage, uploads and bulk backup actions アラート通知（メールと SMS）

Workspaces & Permissions

ワークスペースメンバーの招待 メンバーの権限とリソースへのアクセス メンバーがリソースを表示または使用できない Audit log and server activity

Account & Security

二要素認証（2FA） プロフィールと連携の設定 パスワードとアカウントの復旧 Instance security score and checks The Security page: every instance and member at a glance

Billing & Plans

プランと料金 アップグレードとサブスクリプションの管理 プロジェクトのサブスクリプションが未払いの場合 チャネルパートナープログラム Onboarding a client as a partner

Support & Tickets

サポートチケットの作成 CICDoo チームのサポートを受ける

Troubleshooting

トラブルシューティング: サーバーを接続できない トラブルシューティング: デプロイが失敗した トラブルシューティング: リポジトリ移動後に git push が 403 で失敗する トラブルシューティング: インスタンスが停止している、または遅い トラブルシューティング: ドメインまたは SSL の問題

アカウントとセキュリティ

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.

前へ Instance security score and checks 次へ エージェントタスクとは

まだ解決しませんか？アプリからチケットを作成するか、エンジニアに相談してください。