I've installed the ProofPoint TAP modular Input app. When trying to configure the data source I am receiving the error "Encountered the following error while trying to save: Validation for scheme=proofpoint_tap_siem failed: The script returned with exit status 1."
I've validated the Name, Principal and Secret. Interval is set to 600, Source type is automatic, Host is the Splunk server, Index is the index created for this application. I have also validated connectivity from the Splunk Server to ProofPoint TAP.
,I've installed the app and am configuring the data source and am receiving the following: "Encountered the following error while trying to save: Validation for scheme=proofpoint_tap_siem failed: The script returned with exit status 1.
Name, Principal and Secret have been validated. Interval is set to 600, sourcetype Automatic, Host is the Splunk server and Index is set to "proofpointtap" which is the index created for this app. My first thought was connectivity from the Splunk server to ProofPoint TAP but that has been validated as well.
Managed to figure this out...
Found the following error in the splunkd log in \Program Files\Splunk\var\log\splunk
09-22-2017 12:19:00.003 -0700 ERROR ModularInputs - Argument validation for scheme=proofpoint_tap_siem: validate_arguments/error validating username/password - ([SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:676))
Was able to see from the Splunk server when browsing to *.proofpoint.com that I was being proxied by Triton with SSL inspection (saw the Triton certificate in the browser instead of the ProofPoint certificate). Put in an SSL decryption bypass in Triton to *.proofpoint.com and now it's good to go.
Proofpoint now has a beta app that will allow you report on and visualze your Proofpoint Protection Server and TAP data! Check out the new app here:
https://splunkbase.splunk.com/app/3727/#/details
Be sure to follow the instructions listed in the details to get all the needed TA's etc that the app needs to work correctly.
Managed to figure this out...
Found the following error in the splunkd log in \Program Files\Splunk\var\log\splunk
09-22-2017 12:19:00.003 -0700 ERROR ModularInputs - Argument validation for scheme=proofpoint_tap_siem: validate_arguments/error validating username/password - ([SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:676))
Was able to see from the Splunk server when browsing to *.proofpoint.com that I was being proxied by Triton with SSL inspection (saw the Triton certificate in the browser instead of the ProofPoint certificate). Put in an SSL decryption bypass in Triton to *.proofpoint.com and now it's good to go.