Ensure OSS Interface Signature Authentication Is Hardened

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.

# 1. Check the allowlist format (should be "caller1,encrypted_password1;caller2,encrypted_password2") grep '<whitelist' /path/to/tdsql/conf/scheduler.xml # 2. Confirm each upstream system uses an independent caller # e.g., the CAM gateway uses caller=cam_gw, monitoring uses caller=monitor_svc # 3. Verify caller credentials are encrypted (no cleartext should appear)

How it is fixed

Fix method: Guidance or infrastructure patch

<whitelist ip="10.0.1.0/24;10.0.2.100" user_password="cam_gw,<encrypted_token>;monitor_svc,<encrypted_token>;@osssuper, <encrypted_token>" /> For each upstream system: Must have an independent caller. The password is encrypted via crypt_tool -e or tdsql_encrypt -e (see section 2.6). An IP allowlist restricts source addresses. Credentials are rotated periodically (consistent with the 11.8 OSS super user rotation policy).