Security events are often triggered by the incoming requests of a specific service account configured within an integration. Mismatched credentials, FIPS mode conflicts, or incorrect RBAC roles can cause repeated authentication failures that manifest as brute-force guessing alerts in security monitors.
Validate the authentication events directly on the NSX-T Manager node to identify the source IP and the specific process calling the service account:
grep "####" /var/log/proxy/reverse-proxy.log
Review the client IP address (appearing alongside the POST or GET request). If the IP belongs to a server other than the expected collector, that server is the true source of the traffic.
grep "ACCESS_CONTROL" /var/log/syslog | grep "failure"
Cross-reference these timestamps with the brute force alert timestamps from the security monitor.
grep "####" /var/log/proton/nsxapi.log
If the issue is confirmed as a false positive due to integration, synchronize the credentials in the source application (e.g., vRNI Data Source settings).
To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on your respective region.