TMAegisBeta
Más reglas para oceanbase

OceanBase

TMA-OCEANBASE-2.2

Use OceanBase Official Signed Installation Packages

MediaNivel 1Revisión manualoceanbase

Descripción

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.

Cómo se verifica

Método de auditoría: Revisión manual

Esta recomendación no se puede verificar automáticamente. Un escaneo la lista con estas instrucciones cuando se pasa --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.

Cómo se corrige

Método de corrección: Guía o parche de infraestructura

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.

Propiedades

Sistemas operativos
Cualquiera
Etiquetas
oceanbasesupply-chain
Referencia
CIS OceanBase Enterprise Edition V4 Benchmark v1.0.0 - 2.2 Use OceanBase Official Signed Installation Packages