Apache Pinot controller and broker require separate authorization reviews

Apache Pinot's controller manages cluster metadata, tables, and segments, while its broker handles SQL queries and returns data, and the two roles carry different exposure risks. Pinot's documentation makes authentication and ACL configuration independent for each component, and authentication is disabled by default, with the default access factory permitting all access. The article recommends explicitly verifying that authentication, authorization, TLS, and internal service credentials are enabled in production deployments. It also advises testing read-only, table-specific, and administrator accounts separately and restricting network exposure of controller and broker endpoints. Search-engine counts of Pinot instances are described as matching assets rather than evidence that access controls are misconfigured.