TMAegis
More rules for oceanbase

TMA-OCEANBASE-2.2

Use OceanBase Official Signed Installation Packages

MediumLevel 1Manual reviewoceanbase

Description

OceanBase official release packages are signed with a GPG key. Before using the packages, users can verify their integrity by checking the signature, thereby preventing supply chain poisoning attacks caused by tampered or untrusted installation packages.

How it is checked

Audit method: Manual review

This recommendation cannot be checked automatically. A scan lists it with these instructions when you pass --include-manual.

For environments deployed using the OceanBase Cloud Platform (OCP), verify that installation packages are sourced exclusively from official OceanBase channels and that OCP's built-in signature validation mechanism is enabled. Review deployment logs or audit records from OCP to confirm that no unsigned or untrusted packages were installed. The presence of alerts or rejection events related to package signature validation indicates that the control is active.

How it is fixed

Fix method: Guidance or infrastructure patch

Ensure that all OceanBase installation packages used in production environments are obtained directly from official OceanBase distribution channels and bear valid digital signatures issued by OceanBase. Coordinate with authorized OceanBase support or delivery personnel to confirm the authenticity and integrity of software packages prior to deployment.

Properties

Operating systems
Any
Tags
oceanbasesupply-chain
Reference
CIS OceanBase Enterprise Edition V4 Benchmark v1.0.0 - 2.2 Use OceanBase Official Signed Installation Packages