Ensure Gateway-Layer Secure SQL Protection Is Enabled

MediumLevel 1Manual reviewtdsql

Description

gateway.security.reject. nowhere 1 Reject DELETE/UPDATE without WHERE gateway.security.reject. nopk 1 Reject CREATE TABLE without a primary key gateway.security.name.re strict 1 Restrict object names to alphanumerics and underscore gateway.security.unsafe_ sysfunc.openflag 1 Intercept unsafe system functions gateway.security.conn.co nn_limit >0 Set a reasonable connection limit Assessed manually here: the benchmark check is environment-specific and cannot be evaluated reliably by a single command.

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.

In the OSS management platform (or the Gateway proxy.json) confirm gateway.security.reject.nowhere = 1, gateway.security.reject.nopk = 1, gateway.security.name.restrict = 1 and gateway.security.unsafe_sysfunc.openflag = 1 for every instance. Any value of 0 is a finding.

How it is fixed

Fix method: Guidance or infrastructure patch

Modify the Gateway parameters via the OSS management platform: Parameter Recomm ended

Properties

Operating systems: Any
Tags: tdsqlgateway
Reference: CIS Tencent TDSQL 10.3.22 Benchmark v1.0.0 - 4.9 Ensure Gateway-Layer Secure SQL Protection Is Enabled