Ensure Centralized Audit Log Collection Is Configured

MoyenneNiveau 1Revue manuelletdsql

Description

TDSQL can use managed Filebeat instances to collect logs from compute nodes, data nodes, and Agents and send them to Kafka or Elasticsearch. The destination may be DBbrain full-link audit analysis or an equivalent enterprise SIEM. Central collection must cover all production instances and all security-relevant log sources.

Méthode de vérification

Méthode d'audit: Revue manuelle

Cette recommandation ne peut pas être vérifiée automatiquement. Une analyse la liste avec ces instructions lorsque vous passez --include-manual.

Verify the Filebeat process and management-platform configuration on every production instance: ps aux | grep '[f]ilebeat' # Inspect the effective Filebeat inputs and outputs. grep -E 'type:|paths:|output\.kafka|output\.elasticsearch|hosts:|topic:' \ /path/to/filebeat.yml Confirm that the following required sources are enabled where present: 1. Compute-node interface logs. 2. Compute-node SQL logs. 3. Data-node DB audit logs. 4. Data-node slow query logs. 5. Data-node error logs. 6. Agent sys_log, back_log, and dump_log. 7.

Méthode de correction

Méthode de correction: Recommandation ou correctif d'infrastructure

In the TDSQL management platform, open the instance's Filebeat audit-log settings and enable the required compute-node, data-node, and Agent log inputs. Configure an approved Kafka or Elasticsearch destination and use consistent topics and partition rules for equivalent logs across instances. Where DBbrain high-level analysis is licensed, Kafka output may be connected to DBbrain for full-link analysis. DBbrain is optional;

Propriétés

Systèmes d'exploitation: Tous
Étiquettes: tdsqlloggingaudit
Référence: CIS Tencent TDSQL 10.3.22 Benchmark v1.0.0 - 6.8 Ensure Centralized Audit Log Collection Is Configured