全部文章

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 告警通知（邮件与短信）

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 下一篇 什么是智能体任务

仍未解决？在应用中提交工单，或与工程师沟通。