| Author | TrackMe Limited, U.K. |
|---|---|
| Tags | cloud |
| Version | 2.4.18 |
| Hash | c155f5c35b738968eaebcc9ca2b66639 |
| AppInspect Request ID | 0f48dcb9-789e-494e-86ac-69d2a53b1403 |
| Run Time | 2026-09-24T04:43:53.446211 |
| Execution Time | 1303 |
| Field | Value |
|---|---|
| AppInspect Version | 4.3.1 |
| Name | Version | Is Latest |
|---|---|---|
| dynamic-checks | 1.48.0 | True |
| retire-js | 1.3.0 | True |
| static-checks | 4.3.1 | True |
| Status | Count |
|---|---|
|
Successes
|
147 |
|
Failures
|
0 |
|
Future Failures
|
0 |
|
Errors
|
0 |
|
Warnings
|
17 |
|
Not Applicable
|
86 |
|
Skipped
|
1 |
2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI utility components. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/moment 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI utility components. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/moment 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI utility components. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/moment 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI utility components. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/moment 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI utility components. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/moment 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI utility components. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/moment 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI utility components. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/moment 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI utility components. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/moment 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI utility components. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/moment 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI utility components. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/moment 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI utility components. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/moment 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI utility components. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/moment 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI utility components. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/moment 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI utility components. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/moment 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI utility components. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/moment 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 388Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 4Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 4Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 4Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 4Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 388Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 4Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 4Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 4Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 228Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 4Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 4Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 4Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 388Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 4Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 388Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 1203Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/react-icons 1485Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/react-icons 587Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/react-icons 2As of Splunk 6.5, this functionality is deprecated and should be removed in futureapp versions. Match: splunkjs/mvc/headerview. 2As of Splunk 6.5, this functionality is deprecated and should be removed in futureapp versions. Match: splunkjs/mvc/headerview. 2As of Splunk 6.5, this functionality is deprecated and should be removed in futureapp versions. Match: splunkjs/mvc/headerview. 386As of Splunk 6.5, this functionality is deprecated and should be removed in futureapp versions. Match: splunkjs/mvc/headerview. 2As of Splunk 6.5, this functionality is deprecated and should be removed in futureapp versions. Match: splunkjs/mvc/headerview. 2As of Splunk 6.5, this functionality is deprecated and should be removed in futureapp versions. Match: splunkjs/mvc/headerview. 386As of Splunk 6.5, this functionality is deprecated and should be removed in futureapp versions. Match: splunkjs/mvc/headerview. 386As of Splunk 6.5, this functionality is deprecated and should be removed in futureapp versions. Match: splunkjs/mvc/headerview. 2As of Splunk 6.5, this functionality is deprecated and should be removed in futureapp versions. Match: splunkjs/mvc/headerview. 2As of Splunk 6.5, this functionality is deprecated and should be removed in futureapp versions. Match: splunkjs/mvc/headerview. 2As of Splunk 6.5, this functionality is deprecated and should be removed in futureapp versions. Match: splunkjs/mvc/headerview. 2As of Splunk 6.5, this functionality is deprecated and should be removed in futureapp versions. Match: splunkjs/mvc/headerview. 228As of Splunk 6.5, this functionality is deprecated and should be removed in futureapp versions. Match: splunkjs/mvc/headerview. 2As of Splunk 6.5, this functionality is deprecated and should be removed in futureapp versions. Match: splunkjs/mvc/headerview. 2As of Splunk 6.5, this functionality is deprecated and should be removed in futureapp versions. Match: splunkjs/mvc/headerview. 2As of Splunk 6.5, this functionality is deprecated and should be removed in futureapp versions. Match: splunkjs/mvc/headerview. 2As of Splunk 6.5, this functionality is deprecated and should be removed in futureapp versions. Match: splunkjs/mvc/headerview. 386As of Splunk 6.5, this functionality is deprecated and should be removed in futureapp versions. Match: splunkjs/mvc/headerview. 2As of Splunk 6.5, this functionality is deprecated and should be removed in futureapp versions. Match: splunkjs/mvc/headerview. 11631 Python files found. Update these Python scripts to be cross-compatible with Python 2 and 3 for Splunk Enterprise 8.0. See https://docs.splunk.com/Documentation/Splunk/latest/Python3Migration/AboutMigration for more information. If you've finished your update, please disregard this message.App contains `default/splunk_create.conf` but conf_replication_include.splunk_create setting is not set in server.conf. App contains collections.conf. No action required. 79The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 160The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 54The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 147The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 5The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 92The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 126The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 76The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 73The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 60The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 132The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 120The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 141The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 70The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 144The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 44The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 135The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 57The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 123The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 129The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 157The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 107The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 150The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 138The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 63The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 3Splunk SDK for Python detected (version 3.0.1). No action required at this time. 342Found usage of `mmap.mmap` which might not work on every operating system. 574Found usage of `mmap.mmap` which might not work on every operating system. 320Found usage of `mmap.mmap` which might not work on every operating system. 5737Found usage of `mmap.mmap` which might not work on every operating system. 5865Found usage of `mmap.mmap` which might not work on every operating system. 575Found usage of `mmap.mmap` which might not work on every operating system. 273Found usage of `mmap.mmap` which might not work on every operating system. 273Found usage of `mmap.mmap` which might not work on every operating system. 289Found usage of `mmap.mmap` which might not work on every operating system. 268Found usage of `mmap.mmap` which might not work on every operating system. 27The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 197The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 142The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion. 316The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 165The following line contains questionable usage `threading.Thread.start` in loop. Use threading and multiprocessing with discretion. 27The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 914The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 69The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 858The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 40The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 340The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 232The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion. 221The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion. 62The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 57The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 332The following line contains subprocess.Popen.communicate usage. Use threading and multiprocessing with discretion. 65The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 247The following line contains subprocess.Popen.communicate usage. Use threading and multiprocessing with discretion. 85The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 244The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion. 61The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 88The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 68The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 145The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 312The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 200The following line contains subprocess.Popen.communicate usage. Use threading and multiprocessing with discretion. 126The following line contains subprocess.Popen.kill usage. Use threading and multiprocessing with discretion. 29The following line contains subprocess.getstatusoutput usage. Use threading and multiprocessing with discretion. 596The following line contains questionable usage `threading.Thread.start` in loop. Use threading and multiprocessing with discretion. 239The following line contains subprocess.Popen.communicate usage. Use threading and multiprocessing with discretion. 195The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion. 305The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 248The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion. 37The following line contains subprocess.Popen.communicate usage. Use threading and multiprocessing with discretion. 53The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 237The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 122The following line contains subprocess.Popen.terminate usage. Use threading and multiprocessing with discretion. 89The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion. 329The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion. 107The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 159The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 252The following line contains subprocess.Popen.communicate usage. Use threading and multiprocessing with discretion. 29The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 334The following line contains subprocess.call usage. Use threading and multiprocessing with discretion. 46The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 146The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 369The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 136The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion. 45The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 82The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion. 17The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 69The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 719The following line contains questionable usage `threading.Thread.start` in loop. Use threading and multiprocessing with discretion. 407The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 453The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 45The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 246The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 164The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 61The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 74The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 266The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 64The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 52The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 221The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 653The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 108The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 197The following line contains questionable usage `threading.Thread.start` in loop. Use threading and multiprocessing with discretion. 2090The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 1958The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 81The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 11The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion. 51The following line contains questionable usage `threading.Thread.start` in loop. Use threading and multiprocessing with discretion. 276The following line contains questionable usage `threading.Thread.start` in loop. Use threading and multiprocessing with discretion. 77The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 64The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 471The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 147The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 33The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion. 188The following line contains subprocess.Popen.communicate usage. Use threading and multiprocessing with discretion. 36The following line contains questionable usage `threading.Thread.start` in loop. Use threading and multiprocessing with discretion. 15The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion. 283The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 52The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 243The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 56The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 32The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 145The following line contains subprocess.Popen.communicate usage. Use threading and multiprocessing with discretion. Suppressed 104 warning messages2076The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 197The following line contains questionable usage `threading.Thread.start` in loop. Use threading and multiprocessing with discretion. 153The following line contains questionable usage `threading.Thread.start` in loop. Use threading and multiprocessing with discretion. 18The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 187The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion. 48The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 39The following line contains questionable usage `os.killpg` in loop. Use threading and multiprocessing with discretion. 74The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 348The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 81The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 209The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion. 1953The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 7884PUBLIC IP 3.1.4.1 is found in lib/3rdparty/linux_with_deps_313/pillow.libs/libjpeg-02b4d8cf.so.62.4.0:7884 24PUBLIC IP 2.5.29.33 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:24 144PUBLIC IP 1.3.101.111 is found in lib/3rdparty/linux_with_deps_313/Crypto/PublicKey/_montgomery.py:144 597PRIVATE IP 192.168.1.10 is found in lib/trackme_libs_ai_fqm_advisor.py:597 22PUBLIC IP 2.5.29.31 is found in lib/3rdparty/linux_with_deps_39/cryptography/hazmat/_oid.py:22 12590PUBLIC IP 1.3.101.111 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/bindings/_rust.abi3.so:12590 2498PRIVATE IP 192.168.0.1 is found in lib/3rdparty/linux_with_deps_313/regex/tests/test_regex.py:2498 25PUBLIC IP 2.5.29.35 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:25 29PUBLIC IP 2.5.29.54 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:29 388PUBLIC IP 12.21.1.11 is found in appserver/static/pages/AuditDataSampling.js:388 20PUBLIC IP 2.5.29.19 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:20 61PUBLIC IP 2.5.4.8 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:61 21PUBLIC IP 2.5.29.30 is found in lib/3rdparty/linux_with_deps_39/cryptography/hazmat/_oid.py:21 51PUBLIC IP 1.3.101.112 is found in lib/3rdparty/linux_with_deps_39/Crypto/PublicKey/_edwards.py:51 906PUBLIC IP 12.21.1.11 is found in appserver/static/pages/VirtualTenants.js:906 84PUBLIC IP 2.5.4.16 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:84 388PUBLIC IP 12.21.1.11 is found in appserver/static/pages/AuditAiAdvisor.js:388 35PUBLIC IP 1.2.0.0 is found in lib/3rdparty/linux_with_deps_313/urllib3-2.8.0.dist-info/METADATA:35 18PUBLIC IP 2.5.29.17 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:18 2724PUBLIC IP 64.236.16.20 is found in lib/3rdparty/linux_with_deps_313/regex/tests/test_regex.py:2724 189PUBLIC IP 1.3.101.110 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:189 74PUBLIC IP 2.5.4.65 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:74 51PUBLIC IP 1.3.101.112 is found in lib/3rdparty/linux_with_deps_313/Crypto/PublicKey/_edwards.py:51 779PUBLIC IP 12.21.1.11 is found in appserver/static/pages/TenantHome.js:779 111PUBLIC IP 1.3.101.113 is found in lib/3rdparty/linux_with_deps_39/Crypto/PublicKey/_edwards.py:111 27PUBLIC IP 5.7.1.2 is found in lib/3rdparty/linux_with_deps_39/Crypto/SelfTest/Protocol/test_ecdh.py:27 24PUBLIC IP 2.5.29.33 is found in lib/3rdparty/linux_with_deps_39/cryptography/hazmat/_oid.py:24 388PUBLIC IP 12.21.1.11 is found in appserver/static/pages/AuditTenantsOps.js:388 190PUBLIC IP 1.3.101.111 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:190 11769PUBLIC IP 1.3.101.110 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/bindings/_rust.abi3.so:11769 388PUBLIC IP 12.21.1.11 is found in appserver/static/pages/AuditAiRoutines.js:388 388PUBLIC IP 12.21.1.11 is found in appserver/static/pages/AuditTrackersPerf.js:388 395PUBLIC IP 12.21.1.11 is found in appserver/static/pages/TopologyStudio.js:395 71PUBLIC IP 2.5.4.44 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:71 36PUBLIC IP 2.5.29.27 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:36 19PUBLIC IP 2.5.29.18 is found in lib/3rdparty/linux_with_deps_39/cryptography/hazmat/_oid.py:19 144PUBLIC IP 1.3.101.111 is found in lib/3rdparty/linux_with_deps_39/Crypto/PublicKey/_montgomery.py:144 63PUBLIC IP 2.5.4.97 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:63 53PUBLIC IP 2.5.29.21 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:53 15PUBLIC IP 2.5.29.14 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:15 69PUBLIC IP 2.5.4.12 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:69 65PUBLIC IP 2.5.4.11 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:65 60PUBLIC IP 2.5.4.7 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:60 25347PUBLIC IP 6.7.8.5 is found in lib/3rdparty/linux_with_deps_313/lxml/objectify.cpython-313-x86_64-linux-gnu.so:25347 81432PUBLIC IP 8.11.14.1 is found in lib/3rdparty/linux_with_deps_313/pillow.libs/libavif-0b1c2ae7.so.16.4.1:81432 388PUBLIC IP 12.21.1.11 is found in appserver/static/pages/AuditAiAdvisorScheduled.js:388 18PUBLIC IP 2.5.29.17 is found in lib/3rdparty/linux_with_deps_39/cryptography/hazmat/_oid.py:18 64PUBLIC IP 2.5.4.10 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:64 35PUBLIC IP 2.5.29.20 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:35 30PUBLIC IP 2.5.29.28 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:30 52PUBLIC IP 2.5.29.29 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:52 388PUBLIC IP 12.21.1.11 is found in appserver/static/pages/AuditSla.js:388 59PUBLIC IP 2.5.4.6 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:59 27PUBLIC IP 2.5.29.37 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:27 14PUBLIC IP 2.5.29.9 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:14 54PUBLIC IP 2.5.29.24 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:54 26PUBLIC IP 2.5.29.36 is found in lib/3rdparty/linux_with_deps_39/cryptography/hazmat/_oid.py:26 67PUBLIC IP 2.5.4.4 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:67 73PUBLIC IP 2.5.4.46 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:73 17PUBLIC IP 2.5.29.16 is found in lib/3rdparty/linux_with_deps_39/cryptography/hazmat/_oid.py:17 111PUBLIC IP 1.3.101.113 is found in lib/3rdparty/linux_with_deps_313/Crypto/PublicKey/_edwards.py:111 17PUBLIC IP 2.5.29.16 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:17 772PUBLIC IP 12.21.1.11 is found in appserver/static/pages/RemoteAccountsOverview.js:772 15PUBLIC IP 2.5.29.14 is found in lib/3rdparty/linux_with_deps_39/cryptography/hazmat/_oid.py:15 73PUBLIC IP 1.3.101.110 is found in lib/3rdparty/linux_with_deps_39/Crypto/PublicKey/_montgomery.py:73 19PUBLIC IP 2.5.29.18 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:19 58PUBLIC IP 2.5.4.3 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:58 72PUBLIC IP 2.5.4.45 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:72 28PUBLIC IP 2.5.29.46 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:28 70PUBLIC IP 2.5.4.43 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:70 21PUBLIC IP 2.5.29.30 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:21 12436PUBLIC IP 1.3.101.112 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/bindings/_rust.abi3.so:12436 62PUBLIC IP 2.5.4.9 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:62 23PUBLIC IP 2.5.29.32 is found in lib/3rdparty/linux_with_deps_39/cryptography/hazmat/_oid.py:23 22PUBLIC IP 2.5.29.31 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:22 16PUBLIC IP 2.5.29.15 is found in lib/3rdparty/linux_with_deps_39/cryptography/hazmat/_oid.py:16 26PUBLIC IP 2.5.29.36 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:26 27PUBLIC IP 5.7.1.2 is found in lib/3rdparty/linux_with_deps_313/Crypto/SelfTest/Protocol/test_ecdh.py:27 Suppressed 98 warning messages85PUBLIC IP 2.5.4.17 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:85 5828PUBLIC IP 3.1.4.1 is found in lib/3rdparty/linux_with_deps_313/PIL/_imaging.cpython-313-x86_64-linux-gnu.so:5828 68PUBLIC IP 2.5.4.42 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:68 20PUBLIC IP 2.5.29.19 is found in lib/3rdparty/linux_with_deps_39/cryptography/hazmat/_oid.py:20 388PUBLIC IP 12.21.1.11 is found in appserver/static/pages/AuditSvcUsage.js:388 73PUBLIC IP 1.3.101.110 is found in lib/3rdparty/linux_with_deps_313/Crypto/PublicKey/_montgomery.py:73 25PUBLIC IP 2.5.29.35 is found in lib/3rdparty/linux_with_deps_39/cryptography/hazmat/_oid.py:25 122PUBLIC IP 1.3.101.113 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:122 83PUBLIC IP 2.5.4.15 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:83 49243PUBLIC IP 6.7.8.5 is found in lib/3rdparty/linux_with_deps_313/lxml/etree.cpython-313-x86_64-linux-gnu.so:49243 14PUBLIC IP 2.5.29.9 is found in lib/3rdparty/linux_with_deps_39/cryptography/hazmat/_oid.py:14 12461PUBLIC IP 1.3.101.113 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/bindings/_rust.abi3.so:12461 66PUBLIC IP 2.5.4.5 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:66 2724PUBLIC IP 66.35.250.150 is found in lib/3rdparty/linux_with_deps_313/regex/tests/test_regex.py:2724 388PUBLIC IP 12.21.1.11 is found in appserver/static/pages/AuditAiAssistant.js:388 16PUBLIC IP 2.5.29.15 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:16 388PUBLIC IP 12.21.1.11 is found in appserver/static/pages/AuditAdaptiveDelay.js:388 772PUBLIC IP 12.21.1.11 is found in appserver/static/pages/LogsInspector.js:772 121PUBLIC IP 1.3.101.112 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:121 17PUBLIC IP 3.5.0.1 is found in lib/3rdparty/linux_with_deps_313/urllib3/util/ssl_match_hostname.py:17 23PUBLIC IP 2.5.29.32 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:23 Custom Mako template file 'appserver/templates/AuditSla.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/SupportDiag.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/ManageRemoteAccounts.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/AuditSvcUsage.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/VirtualTenants.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/MaintenanceKdb.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/AuditAiAdvisorScheduled.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/AuditAiRoutines.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/license.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/ConfigurationGuardian.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/MaintenanceMode.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/ManageAiProviders.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/AuditAiAdvisor.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/AuditTenantsOps.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/ManageEmailAccounts.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/ManageS3Accounts.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/ManageSystemSettings.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/RemoteAccountsOverview.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/backuprestore.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/TenantHome.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/LogsInspector.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/base.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/AuditAiAssistant.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/RestApiReference.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/AuditDataSampling.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/AuditTrackersPerf.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/AuditAdaptiveDelay.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/TopologyStudio.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/ManageAiTenants.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/ManageBankHolidays.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/AuditKvstore.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. 3258Insecure HTTP Connection found Match: requests.get Positional arguments, ["message"]; Keyword arguments, {} 3295Insecure HTTP Connection found Match: requests.get Positional arguments, [""]; Keyword arguments, {"headers": "?", "verify": "?", "timeout": "?", "params": "?"} 3693Insecure HTTP Connection found Match: requests.post Positional arguments, ["/services/trackme/v2/ack/get_ack_for_object"]; Keyword arguments, {"headers": "?", "data": "?", "verify": "?", "timeout": "?"} 3536Insecure HTTP Connection found Match: requests.get Positional arguments, ["retry_backoff_multiplier"]; Keyword arguments, {} 359Insecure HTTP Connection found Match: requests.get Positional arguments, ["/services/trackme/v2/topology_views/reference_directory/services/trackme/v2/topology_views/reference_directory"]; Keyword arguments, {"headers": "?", "params": "?", "verify": "?", "timeout": "?"} 987Insecure HTTP Connection found Match: requests.get Positional arguments, ["web_base_url"]; Keyword arguments, {} 341Insecure HTTP Connection found Match: requests.get Positional arguments, ["success_count"]; Keyword arguments, {} 1168Insecure HTTP Connection found Match: requests.get Positional arguments, ["trackme_summary_idx"]; Keyword arguments, {} 12843Insecure HTTP Connection found Match: requests.get Positional arguments, ["tracker_report"]; Keyword arguments, {} 375Insecure HTTP Connection found Match: requests.get Positional arguments, ["trackme_metric_idx", "trackme_metrics"]; Keyword arguments, {} 3534Insecure HTTP Connection found Match: requests.get Positional arguments, ["retry_initial_delay"]; Keyword arguments, {} 627Insecure HTTP Connection found Match: requests.get Positional arguments, ["retry_initial_delay", "2"]; Keyword arguments, {} 3240Insecure HTTP Connection found Match: requests.get Positional arguments, ["payload"]; Keyword arguments, {} 12845Insecure HTTP Connection found Match: requests.get Positional arguments, ["earliest"]; Keyword arguments, {} 177Insecure HTTP Connection found Match: requests.Session.get Positional arguments, ["trackme_metric_idx", "trackme_metrics"]; Keyword arguments, {} 612Insecure HTTP Connection found Match: requests.get Positional arguments, ["timeout_search_check", "?"]; Keyword arguments, {} 2230Insecure HTTP Connection found Match: requests.get Positional arguments, ["owner"]; Keyword arguments, {} 2099Insecure HTTP Connection found Match: requests.get Positional arguments, ["owner"]; Keyword arguments, {} 601Insecure HTTP Connection found Match: requests.Session.get Positional arguments, ["timeout_connect_check", "?"]; Keyword arguments, {} 612Insecure HTTP Connection found Match: requests.Session.get Positional arguments, ["timeout_search_check", "?"]; Keyword arguments, {} 2721Insecure HTTP Connection found Match: requests.get Positional arguments, ["message"]; Keyword arguments, {} 177Insecure HTTP Connection found Match: urllib.request.urlopen Positional arguments, ["utf-8"]; Keyword arguments, {} 3503Insecure HTTP Connection found Match: requests.get Positional arguments, ["allowed_email_domains", "?"]; Keyword arguments, {} 625Insecure HTTP Connection found Match: requests.Session.get Positional arguments, ["retry_enabled", "1"]; Keyword arguments, {} 152Insecure HTTP Connection found Match: requests.post Positional arguments, ["/servicesNS/nobody/trackme/storage/collections/data/kv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenants"]; Keyword arguments, {"headers": "?", "data": "?", "verify": "?", "timeout": "?"} 2052Insecure HTTP Connection found Match: requests.get Positional arguments, ["trackme_version", "unknown"]; Keyword arguments, {} 629Insecure HTTP Connection found Match: requests.get Positional arguments, ["retry_max_attempts", "10"]; Keyword arguments, {} 628Insecure HTTP Connection found Match: requests.get Positional arguments, ["retry_backoff_multiplier", "2.0"]; Keyword arguments, {} 2102Insecure HTTP Connection found Match: requests.get Positional arguments, ["sharing"]; Keyword arguments, {} 601Insecure HTTP Connection found Match: requests.get Positional arguments, ["timeout_connect_check", "?"]; Keyword arguments, {} 3530Insecure HTTP Connection found Match: requests.get Positional arguments, ["retry_enabled"]; Keyword arguments, {} 5072Insecure HTTP Connection found Match: requests.get Positional arguments, ["archive_base64"]; Keyword arguments, {} 625Insecure HTTP Connection found Match: requests.get Positional arguments, ["retry_enabled", "1"]; Keyword arguments, {} 207Insecure HTTP Connection found Match: requests.post Positional arguments, ["/services/trackme/v2/component/write/refresh_shadow/services/trackme/v2/component/write/refresh_shadow"]; Keyword arguments, {"headers": "?", "json": "?", "verify": "?", "timeout": "?"} 626Insecure HTTP Connection found Match: requests.Session.get Positional arguments, ["retry_max_total_time", "30"]; Keyword arguments, {} 2328Insecure HTTP Connection found Match: requests.get Positional arguments, ["collection"]; Keyword arguments, {} 2308Insecure HTTP Connection found Match: requests.get Positional arguments, ["type"]; Keyword arguments, {} 3532Insecure HTTP Connection found Match: requests.get Positional arguments, ["retry_max_total_time"]; Keyword arguments, {} 3518Insecure HTTP Connection found Match: requests.get Positional arguments, ["token"]; Keyword arguments, {} 13266Insecure HTTP Connection found Match: requests.get Positional arguments, ["tracker_name"]; Keyword arguments, {} 3909Insecure HTTP Connection found Match: requests.get Positional arguments, ["files_purged", "?"]; Keyword arguments, {} 626Insecure HTTP Connection found Match: requests.get Positional arguments, ["retry_max_total_time", "30"]; Keyword arguments, {} 561Insecure HTTP Connection found Match: requests.get Positional arguments, ["entities_outliers"]; Keyword arguments, {} Suppressed 300 warning messages2634Insecure HTTP Connection found Match: requests.get Positional arguments, ["token", "?"]; Keyword arguments, {} 232Insecure HTTP Connection found Match: requests.get Positional arguments, ["payload"]; Keyword arguments, {} 3467Insecure HTTP Connection found Match: requests.get Positional arguments, ["email_incident_subject_template", ""]; Keyword arguments, {} 271Insecure HTTP Connection found Match: requests.get Positional arguments, ["num_pages", "?"]; Keyword arguments, {} 2321Insecure HTTP Connection found Match: requests.get Positional arguments, ["definition"]; Keyword arguments, {} 3521Insecure HTTP Connection found Match: requests.get Positional arguments, ["timeout_connect_check", "?"]; Keyword arguments, {} 2325Insecure HTTP Connection found Match: requests.get Positional arguments, ["definition"]; Keyword arguments, {} 2309Insecure HTTP Connection found Match: requests.get Positional arguments, ["title"]; Keyword arguments, {} 248Insecure HTTP Connection found Match: requests.get Positional arguments, ["success_count"]; Keyword arguments, {} 3451Insecure HTTP Connection found Match: requests.get Positional arguments, ["email_static_incident_subject", "?"]; Keyword arguments, {} 2272Insecure HTTP Connection found Match: requests.get Positional arguments, ["owner"]; Keyword arguments, {} 1153Insecure HTTP Connection found Match: requests.Session.get Positional arguments, ["trackme_metric_idx"]; Keyword arguments, {} 168Insecure HTTP Connection found Match: urllib.request.urlopen Positional arguments, ["utf-8"]; Keyword arguments, {} 3255Insecure HTTP Connection found Match: requests.get Positional arguments, ["payload"]; Keyword arguments, {} 3538Insecure HTTP Connection found Match: requests.get Positional arguments, ["retry_max_attempts"]; Keyword arguments, {} 2322Insecure HTTP Connection found Match: requests.get Positional arguments, ["alert_properties"]; Keyword arguments, {} 562Insecure HTTP Connection found Match: requests.get Positional arguments, ["entity_outlier"]; Keyword arguments, {} 3524Insecure HTTP Connection found Match: requests.get Positional arguments, ["timeout_search_check", "?"]; Keyword arguments, {} 2318Insecure HTTP Connection found Match: requests.get Positional arguments, ["definition"]; Keyword arguments, {} 16236Insecure HTTP Connection found Match: requests.get Positional arguments, ["download_token"]; Keyword arguments, {} 3712Insecure HTTP Connection found Match: requests.get Positional arguments, ["ack_mtime", "?"]; Keyword arguments, {} 5394Insecure HTTP Connection found Match: requests.get Positional arguments, ["email_format", "html"]; Keyword arguments, {} 2704Insecure HTTP Connection found Match: requests.get Positional arguments, ["payload"]; Keyword arguments, {} 177Insecure HTTP Connection found Match: requests.get Positional arguments, ["trackme_metric_idx", "trackme_metrics"]; Keyword arguments, {} 2268Insecure HTTP Connection found Match: requests.get Positional arguments, ["vtenant_account"]; Keyword arguments, {} 234Insecure HTTP Connection found Match: requests.get Positional arguments, ["shadow_refresh"]; Keyword arguments, {} 238Insecure HTTP Connection found Match: requests.get Positional arguments, ["/services/server/info"]; Keyword arguments, {"headers": "?", "params": "?", "verify": "?", "timeout": "?"} 1168Insecure HTTP Connection found Match: requests.Session.get Positional arguments, ["trackme_summary_idx"]; Keyword arguments, {} 10003Insecure HTTP Connection found Match: requests.get Positional arguments, ["response"]; Keyword arguments, {} 13265Insecure HTTP Connection found Match: requests.get Positional arguments, ["tracker_report"]; Keyword arguments, {} 661Insecure HTTP Connection found Match: requests.get Positional arguments, ["data_sampling_obfuscation"]; Keyword arguments, {} 16321Insecure HTTP Connection found Match: requests.get Positional arguments, ["archive_base64"]; Keyword arguments, {} 2233Insecure HTTP Connection found Match: requests.get Positional arguments, ["sharing"]; Keyword arguments, {} 5071Insecure HTTP Connection found Match: requests.get Positional arguments, ["download_token"]; Keyword arguments, {} 2329Insecure HTTP Connection found Match: requests.get Positional arguments, ["fields_list"]; Keyword arguments, {} 3519Insecure HTTP Connection found Match: requests.get Positional arguments, ["app_namespace", "search"]; Keyword arguments, {} 375Insecure HTTP Connection found Match: requests.Session.get Positional arguments, ["trackme_metric_idx", "trackme_metrics"]; Keyword arguments, {} 15300Insecure HTTP Connection found Match: requests.get Positional arguments, ["/services/trackme/v2/backup_and_restore/backup"]; Keyword arguments, {"headers": "?", "verify": "?", "timeout": "?"} 2716Insecure HTTP Connection found Match: requests.get Positional arguments, ["payload"]; Keyword arguments, {} 12844Insecure HTTP Connection found Match: requests.get Positional arguments, ["tracker_name"]; Keyword arguments, {} 757Insecure HTTP Connection found Match: requests.get Positional arguments, ["trackme_conf"]; Keyword arguments, {} 13267Insecure HTTP Connection found Match: requests.get Positional arguments, ["earliest"]; Keyword arguments, {} 628Insecure HTTP Connection found Match: requests.Session.get Positional arguments, ["retry_backoff_multiplier", "2.0"]; Keyword arguments, {} 1153Insecure HTTP Connection found Match: requests.get Positional arguments, ["trackme_metric_idx"]; Keyword arguments, {} 629Insecure HTTP Connection found Match: requests.Session.get Positional arguments, ["retry_max_attempts", "10"]; Keyword arguments, {} 16243Insecure HTTP Connection found Match: requests.get Positional arguments, ["filename", ".tgz"]; Keyword arguments, {} 309Insecure HTTP Connection found Match: requests.post Positional arguments, ["/services/trackme/v2/topology_alerts/write/disable_alert"]; Keyword arguments, {"headers": "?", "data": "?", "verify": "?", "timeout": "?"} 3711Insecure HTTP Connection found Match: requests.get Positional arguments, ["ack_state", "inactive"]; Keyword arguments, {} 2313Insecure HTTP Connection found Match: requests.get Positional arguments, ["properties", "?"]; Keyword arguments, {} 3906Insecure HTTP Connection found Match: requests.get Positional arguments, ["status", "Unknown status"]; Keyword arguments, {} 13268Insecure HTTP Connection found Match: requests.get Positional arguments, ["latest"]; Keyword arguments, {} 12846Insecure HTTP Connection found Match: requests.get Positional arguments, ["latest"]; Keyword arguments, {} 170Insecure HTTP Connection found Match: urllib.request.urlopen Positional arguments, ["utf-8"]; Keyword arguments, {} 8635Insecure HTTP Connection found Match: requests.get Positional arguments, ["archives"]; Keyword arguments, {} 627Insecure HTTP Connection found Match: requests.Session.get Positional arguments, ["retry_initial_delay", "2"]; Keyword arguments, {} 16214Insecure HTTP Connection found Match: requests.get Positional arguments, ["payload", "?"]; Keyword arguments, {} 1720Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 458Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 2004Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 2260Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 21077Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 205Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 21238Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 20522Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 2987Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. Suppressed 367 warning messages2921Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 2177Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 15300Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 20836Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 72Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 13209Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 2294Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 2921Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 227Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 419Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 5783Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 3213Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 22569Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 3295Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 3222Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 16249Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 3698Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 3539Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 3193Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 121Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 20936Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 534Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 145Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 1685Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 3493Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 238Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 207Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 2235Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 4931Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 389Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 2843Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 79Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 21331Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 2279Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 152Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 264Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 2670Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 309Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 320Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 1789Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 21489Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 5057Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 12710Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 22338Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 186Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 359Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 813Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 22159Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 21920Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 3085Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 567Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 16203Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 3589Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 9957Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 21848Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 2681Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 239Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 2533Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 22635Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 2078Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 1674Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 30Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 5132Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 2613Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 3693Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 953Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 7852Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 365Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 12787Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 428Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 1848Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 62Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 21582Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 234Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 650Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 20628Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 13132Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 1722Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 20756Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 1964Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 154Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 10228Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 358Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 237Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 8583Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 61Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 3765Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 3214Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 3406Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 3489Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 58Detected solnlib (version 8.1.1). No action required. 17Detected splunktaucclib (version 8.2.0). No action required. No ../.dependencies folder found. Please check that the Splunk App package contains only valid dependencies.No ../.dependencies folder found. Please add a .dependencies directory with an valid app folder.No ../.dependencies folder found. Please add a .dependencies directory that contains an app folder with an app.manifest.authentication.conf does not existauthentication.conf does not existauthentication.conf does not existauthentication.conf does not existDidn't find any flash files.inputs.conf does not existinputs.conf does not exist`inputs.conf` does not exist.inputs.conf does not existauthentication.conf does not existaudit.conf does not existbookmarks.conf does not existdatatypesbnf.conf does not existdefault-mode.conf does not existdeploymentclient.conf does not existdeployment.conf does not existinputs.conf.conf does not existhealth.conf does not existinputs.conf.conf does not existinputs.conf does not existinputs.conf does not existinputs.conf does not existinputs.conf.conf does not existinputs.conf does not existinputs.conf does not existinputs.conf.conf does not existinputs.conf does not existinstance.cfg.conf does not existcrawl.conf does not existliterals.conf does not existmessages.conf does not existNo `inputs.conf.spec` was detected.passwords.conf does not existpubsub.conf does not existsegmenters.conf does not existserverclass.conf does not existserverclass.seed.xml.conf does not existsource-classifier.conf does not existsourcetypes.conf does not existsplunk-launch.conf does not existtelemetry.conf does not existuser-seed.conf does not existwmi.conf does not existworkload_pools.conf does not existworkload_rules.conf does not exist2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI utility components. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/moment 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI utility components. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/moment 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI utility components. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/moment 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI utility components. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/moment 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI utility components. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/moment 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI utility components. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/moment 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI utility components. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/moment 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI utility components. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/moment 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI utility components. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/moment 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI utility components. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/moment 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI utility components. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/moment 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI utility components. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/moment 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI utility components. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/moment 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI utility components. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/moment 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI utility components. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/moment 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 388Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 4Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 4Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 4Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 4Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 388Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 4Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 4Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 4Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 228Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 4Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 4Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 4Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 388Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 4Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 388Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 2Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize SplunkJS. Please ignore this warning as it has no impact to your Splunk app. Match: splunkjs/mvc 1203Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/react-icons 1485Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/react-icons 587Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/react-icons Splunk SDK for JavaScript not found.limits.conf does not existoutputs.conf does not existdata/spl2 does not existNo invocations of bundled NodeJS binary found.No `inputs.conf.spec` file exists.inputs.conf does not existeventtypes.conf does not existcrawl.conf does not existviewstates.conf does not existoutputs.conf does not existliterals.conf does not exist11631 Python files found. Update these Python scripts to be cross-compatible with Python 2 and 3 for Splunk Enterprise 8.0. See https://docs.splunk.com/Documentation/Splunk/latest/Python3Migration/AboutMigration for more information. If you've finished your update, please disregard this message.No static/tool_input_payload_signatures.json file exists.tools.conf does not existtools.conf does not existtools.conf does not existtools.conf does not existtools.conf does not existtools.conf does not existtools.conf does not existtools.conf does not existtools.conf does not existtools.conf does not existREADME/inputs.conf.spec does not exist.inputs.conf does not existNo `inputs.conf.spec` file exists.inputs.conf does not existinputs.conf does not exist4default does not have a search setting App contains `default/splunk_create.conf` but conf_replication_include.splunk_create setting is not set in server.conf. `local/app.conf` does not exist.`local/app.conf` does not exist.The local directory does not exist.App contains collections.conf. No action required. 79The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 160The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 54The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 147The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 5The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 92The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 126The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 76The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 73The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 60The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 132The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 120The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 141The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 70The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 144The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 44The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 135The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 57The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 123The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 129The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 157The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 107The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 150The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 138The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object 63The 'admin' role is not available to Splunk Cloud customers. Please consider also including the 'sc_admin' role if you want Splunk Cloud customer administrators to be able to access this knowledge object No INGEST_EVAL properties were declared.workflow_actions.conf does not existdatamodels.conf does not existNo forbidden python files were found.3Splunk SDK for Python detected (version 3.0.1). No action required at this time. Directory does not contain Splunk SDK for Python.342Found usage of `mmap.mmap` which might not work on every operating system. 574Found usage of `mmap.mmap` which might not work on every operating system. 320Found usage of `mmap.mmap` which might not work on every operating system. 5737Found usage of `mmap.mmap` which might not work on every operating system. 5865Found usage of `mmap.mmap` which might not work on every operating system. 575Found usage of `mmap.mmap` which might not work on every operating system. 273Found usage of `mmap.mmap` which might not work on every operating system. 273Found usage of `mmap.mmap` which might not work on every operating system. 289Found usage of `mmap.mmap` which might not work on every operating system. 268Found usage of `mmap.mmap` which might not work on every operating system. 27The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 197The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 142The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion. 316The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 165The following line contains questionable usage `threading.Thread.start` in loop. Use threading and multiprocessing with discretion. 27The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 914The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 69The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 858The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 40The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 340The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 232The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion. 221The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion. 62The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 57The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 332The following line contains subprocess.Popen.communicate usage. Use threading and multiprocessing with discretion. 65The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 247The following line contains subprocess.Popen.communicate usage. Use threading and multiprocessing with discretion. 85The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 244The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion. 61The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 88The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 68The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 145The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 312The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 200The following line contains subprocess.Popen.communicate usage. Use threading and multiprocessing with discretion. 126The following line contains subprocess.Popen.kill usage. Use threading and multiprocessing with discretion. 29The following line contains subprocess.getstatusoutput usage. Use threading and multiprocessing with discretion. 596The following line contains questionable usage `threading.Thread.start` in loop. Use threading and multiprocessing with discretion. 239The following line contains subprocess.Popen.communicate usage. Use threading and multiprocessing with discretion. 195The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion. 305The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 248The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion. 37The following line contains subprocess.Popen.communicate usage. Use threading and multiprocessing with discretion. 53The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 237The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 122The following line contains subprocess.Popen.terminate usage. Use threading and multiprocessing with discretion. 89The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion. 329The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion. 107The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 159The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 252The following line contains subprocess.Popen.communicate usage. Use threading and multiprocessing with discretion. 29The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 334The following line contains subprocess.call usage. Use threading and multiprocessing with discretion. 46The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 146The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 369The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 136The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion. 45The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 82The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion. 17The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 69The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 719The following line contains questionable usage `threading.Thread.start` in loop. Use threading and multiprocessing with discretion. 407The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 453The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 45The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 246The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 164The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 61The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 74The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 266The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 64The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 52The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 221The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 653The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 108The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 197The following line contains questionable usage `threading.Thread.start` in loop. Use threading and multiprocessing with discretion. 2090The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 1958The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 81The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 11The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion. 51The following line contains questionable usage `threading.Thread.start` in loop. Use threading and multiprocessing with discretion. 276The following line contains questionable usage `threading.Thread.start` in loop. Use threading and multiprocessing with discretion. 77The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 64The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 471The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 147The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 33The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion. 188The following line contains subprocess.Popen.communicate usage. Use threading and multiprocessing with discretion. 36The following line contains questionable usage `threading.Thread.start` in loop. Use threading and multiprocessing with discretion. 15The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion. 283The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 52The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 243The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 56The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 32The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 145The following line contains subprocess.Popen.communicate usage. Use threading and multiprocessing with discretion. Suppressed 104 warning messages2076The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 197The following line contains questionable usage `threading.Thread.start` in loop. Use threading and multiprocessing with discretion. 153The following line contains questionable usage `threading.Thread.start` in loop. Use threading and multiprocessing with discretion. 18The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 187The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion. 48The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 39The following line contains questionable usage `os.killpg` in loop. Use threading and multiprocessing with discretion. 74The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 348The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. 81The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion. 209The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion. 1953The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion. Python httplib2 library not found.addon_builder.conf does not exist7884PUBLIC IP 3.1.4.1 is found in lib/3rdparty/linux_with_deps_313/pillow.libs/libjpeg-02b4d8cf.so.62.4.0:7884 24PUBLIC IP 2.5.29.33 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:24 144PUBLIC IP 1.3.101.111 is found in lib/3rdparty/linux_with_deps_313/Crypto/PublicKey/_montgomery.py:144 597PRIVATE IP 192.168.1.10 is found in lib/trackme_libs_ai_fqm_advisor.py:597 22PUBLIC IP 2.5.29.31 is found in lib/3rdparty/linux_with_deps_39/cryptography/hazmat/_oid.py:22 12590PUBLIC IP 1.3.101.111 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/bindings/_rust.abi3.so:12590 2498PRIVATE IP 192.168.0.1 is found in lib/3rdparty/linux_with_deps_313/regex/tests/test_regex.py:2498 25PUBLIC IP 2.5.29.35 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:25 29PUBLIC IP 2.5.29.54 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:29 388PUBLIC IP 12.21.1.11 is found in appserver/static/pages/AuditDataSampling.js:388 20PUBLIC IP 2.5.29.19 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:20 61PUBLIC IP 2.5.4.8 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:61 21PUBLIC IP 2.5.29.30 is found in lib/3rdparty/linux_with_deps_39/cryptography/hazmat/_oid.py:21 51PUBLIC IP 1.3.101.112 is found in lib/3rdparty/linux_with_deps_39/Crypto/PublicKey/_edwards.py:51 906PUBLIC IP 12.21.1.11 is found in appserver/static/pages/VirtualTenants.js:906 84PUBLIC IP 2.5.4.16 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:84 388PUBLIC IP 12.21.1.11 is found in appserver/static/pages/AuditAiAdvisor.js:388 35PUBLIC IP 1.2.0.0 is found in lib/3rdparty/linux_with_deps_313/urllib3-2.8.0.dist-info/METADATA:35 18PUBLIC IP 2.5.29.17 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:18 2724PUBLIC IP 64.236.16.20 is found in lib/3rdparty/linux_with_deps_313/regex/tests/test_regex.py:2724 189PUBLIC IP 1.3.101.110 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:189 74PUBLIC IP 2.5.4.65 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:74 51PUBLIC IP 1.3.101.112 is found in lib/3rdparty/linux_with_deps_313/Crypto/PublicKey/_edwards.py:51 779PUBLIC IP 12.21.1.11 is found in appserver/static/pages/TenantHome.js:779 111PUBLIC IP 1.3.101.113 is found in lib/3rdparty/linux_with_deps_39/Crypto/PublicKey/_edwards.py:111 27PUBLIC IP 5.7.1.2 is found in lib/3rdparty/linux_with_deps_39/Crypto/SelfTest/Protocol/test_ecdh.py:27 24PUBLIC IP 2.5.29.33 is found in lib/3rdparty/linux_with_deps_39/cryptography/hazmat/_oid.py:24 388PUBLIC IP 12.21.1.11 is found in appserver/static/pages/AuditTenantsOps.js:388 190PUBLIC IP 1.3.101.111 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:190 11769PUBLIC IP 1.3.101.110 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/bindings/_rust.abi3.so:11769 388PUBLIC IP 12.21.1.11 is found in appserver/static/pages/AuditAiRoutines.js:388 388PUBLIC IP 12.21.1.11 is found in appserver/static/pages/AuditTrackersPerf.js:388 395PUBLIC IP 12.21.1.11 is found in appserver/static/pages/TopologyStudio.js:395 71PUBLIC IP 2.5.4.44 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:71 36PUBLIC IP 2.5.29.27 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:36 19PUBLIC IP 2.5.29.18 is found in lib/3rdparty/linux_with_deps_39/cryptography/hazmat/_oid.py:19 144PUBLIC IP 1.3.101.111 is found in lib/3rdparty/linux_with_deps_39/Crypto/PublicKey/_montgomery.py:144 63PUBLIC IP 2.5.4.97 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:63 53PUBLIC IP 2.5.29.21 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:53 15PUBLIC IP 2.5.29.14 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:15 69PUBLIC IP 2.5.4.12 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:69 65PUBLIC IP 2.5.4.11 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:65 60PUBLIC IP 2.5.4.7 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:60 25347PUBLIC IP 6.7.8.5 is found in lib/3rdparty/linux_with_deps_313/lxml/objectify.cpython-313-x86_64-linux-gnu.so:25347 81432PUBLIC IP 8.11.14.1 is found in lib/3rdparty/linux_with_deps_313/pillow.libs/libavif-0b1c2ae7.so.16.4.1:81432 388PUBLIC IP 12.21.1.11 is found in appserver/static/pages/AuditAiAdvisorScheduled.js:388 18PUBLIC IP 2.5.29.17 is found in lib/3rdparty/linux_with_deps_39/cryptography/hazmat/_oid.py:18 64PUBLIC IP 2.5.4.10 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:64 35PUBLIC IP 2.5.29.20 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:35 30PUBLIC IP 2.5.29.28 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:30 52PUBLIC IP 2.5.29.29 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:52 388PUBLIC IP 12.21.1.11 is found in appserver/static/pages/AuditSla.js:388 59PUBLIC IP 2.5.4.6 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:59 27PUBLIC IP 2.5.29.37 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:27 14PUBLIC IP 2.5.29.9 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:14 54PUBLIC IP 2.5.29.24 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:54 26PUBLIC IP 2.5.29.36 is found in lib/3rdparty/linux_with_deps_39/cryptography/hazmat/_oid.py:26 67PUBLIC IP 2.5.4.4 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:67 73PUBLIC IP 2.5.4.46 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:73 17PUBLIC IP 2.5.29.16 is found in lib/3rdparty/linux_with_deps_39/cryptography/hazmat/_oid.py:17 111PUBLIC IP 1.3.101.113 is found in lib/3rdparty/linux_with_deps_313/Crypto/PublicKey/_edwards.py:111 17PUBLIC IP 2.5.29.16 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:17 772PUBLIC IP 12.21.1.11 is found in appserver/static/pages/RemoteAccountsOverview.js:772 15PUBLIC IP 2.5.29.14 is found in lib/3rdparty/linux_with_deps_39/cryptography/hazmat/_oid.py:15 73PUBLIC IP 1.3.101.110 is found in lib/3rdparty/linux_with_deps_39/Crypto/PublicKey/_montgomery.py:73 19PUBLIC IP 2.5.29.18 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:19 58PUBLIC IP 2.5.4.3 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:58 72PUBLIC IP 2.5.4.45 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:72 28PUBLIC IP 2.5.29.46 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:28 70PUBLIC IP 2.5.4.43 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:70 21PUBLIC IP 2.5.29.30 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:21 12436PUBLIC IP 1.3.101.112 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/bindings/_rust.abi3.so:12436 62PUBLIC IP 2.5.4.9 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:62 23PUBLIC IP 2.5.29.32 is found in lib/3rdparty/linux_with_deps_39/cryptography/hazmat/_oid.py:23 22PUBLIC IP 2.5.29.31 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:22 16PUBLIC IP 2.5.29.15 is found in lib/3rdparty/linux_with_deps_39/cryptography/hazmat/_oid.py:16 26PUBLIC IP 2.5.29.36 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:26 27PUBLIC IP 5.7.1.2 is found in lib/3rdparty/linux_with_deps_313/Crypto/SelfTest/Protocol/test_ecdh.py:27 Suppressed 98 warning messages85PUBLIC IP 2.5.4.17 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:85 5828PUBLIC IP 3.1.4.1 is found in lib/3rdparty/linux_with_deps_313/PIL/_imaging.cpython-313-x86_64-linux-gnu.so:5828 68PUBLIC IP 2.5.4.42 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:68 20PUBLIC IP 2.5.29.19 is found in lib/3rdparty/linux_with_deps_39/cryptography/hazmat/_oid.py:20 388PUBLIC IP 12.21.1.11 is found in appserver/static/pages/AuditSvcUsage.js:388 73PUBLIC IP 1.3.101.110 is found in lib/3rdparty/linux_with_deps_313/Crypto/PublicKey/_montgomery.py:73 25PUBLIC IP 2.5.29.35 is found in lib/3rdparty/linux_with_deps_39/cryptography/hazmat/_oid.py:25 122PUBLIC IP 1.3.101.113 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:122 83PUBLIC IP 2.5.4.15 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:83 49243PUBLIC IP 6.7.8.5 is found in lib/3rdparty/linux_with_deps_313/lxml/etree.cpython-313-x86_64-linux-gnu.so:49243 14PUBLIC IP 2.5.29.9 is found in lib/3rdparty/linux_with_deps_39/cryptography/hazmat/_oid.py:14 12461PUBLIC IP 1.3.101.113 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/bindings/_rust.abi3.so:12461 66PUBLIC IP 2.5.4.5 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:66 2724PUBLIC IP 66.35.250.150 is found in lib/3rdparty/linux_with_deps_313/regex/tests/test_regex.py:2724 388PUBLIC IP 12.21.1.11 is found in appserver/static/pages/AuditAiAssistant.js:388 16PUBLIC IP 2.5.29.15 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:16 388PUBLIC IP 12.21.1.11 is found in appserver/static/pages/AuditAdaptiveDelay.js:388 772PUBLIC IP 12.21.1.11 is found in appserver/static/pages/LogsInspector.js:772 121PUBLIC IP 1.3.101.112 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:121 17PUBLIC IP 3.5.0.1 is found in lib/3rdparty/linux_with_deps_313/urllib3/util/ssl_match_hostname.py:17 23PUBLIC IP 2.5.29.32 is found in lib/3rdparty/linux_with_deps_313/cryptography/hazmat/_oid.py:23 No pom.xml, build.gradle or build.gradle.kts file foundCustom Mako template file 'appserver/templates/AuditSla.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/SupportDiag.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/ManageRemoteAccounts.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/AuditSvcUsage.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/VirtualTenants.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/MaintenanceKdb.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/AuditAiAdvisorScheduled.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/AuditAiRoutines.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/license.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/ConfigurationGuardian.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/MaintenanceMode.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/ManageAiProviders.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/AuditAiAdvisor.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/AuditTenantsOps.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/ManageEmailAccounts.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/ManageS3Accounts.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/ManageSystemSettings.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/RemoteAccountsOverview.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/backuprestore.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/TenantHome.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/LogsInspector.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/base.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/AuditAiAssistant.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/RestApiReference.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/AuditDataSampling.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/AuditTrackersPerf.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/AuditAdaptiveDelay.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/TopologyStudio.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/ManageAiTenants.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/ManageBankHolidays.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako template file 'appserver/templates/AuditKvstore.html' is deprecated in Splunk Enterprise 10.4. Future Splunk platform versions will no longer support custom Mako templates. Remove the custom template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with @splunk/create version '11.0.0' or later. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. Custom Mako templates are deprecated in Splunk Enterprise 10.4 and will be removed in a future version of the Splunk platform. Remove the custom Mako template. For UCC-generated apps, regenerate the app with UCC framework version '6.3.0' or later. For apps built using @splunk/create, regenerate the app with a version that uses the new template. See https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.4/deprecated-features/deprecated-and-removed-in-version-10.4. 3258Insecure HTTP Connection found Match: requests.get Positional arguments, ["message"]; Keyword arguments, {} 3295Insecure HTTP Connection found Match: requests.get Positional arguments, [""]; Keyword arguments, {"headers": "?", "verify": "?", "timeout": "?", "params": "?"} 3693Insecure HTTP Connection found Match: requests.post Positional arguments, ["/services/trackme/v2/ack/get_ack_for_object"]; Keyword arguments, {"headers": "?", "data": "?", "verify": "?", "timeout": "?"} 3536Insecure HTTP Connection found Match: requests.get Positional arguments, ["retry_backoff_multiplier"]; Keyword arguments, {} 359Insecure HTTP Connection found Match: requests.get Positional arguments, ["/services/trackme/v2/topology_views/reference_directory/services/trackme/v2/topology_views/reference_directory"]; Keyword arguments, {"headers": "?", "params": "?", "verify": "?", "timeout": "?"} 987Insecure HTTP Connection found Match: requests.get Positional arguments, ["web_base_url"]; Keyword arguments, {} 341Insecure HTTP Connection found Match: requests.get Positional arguments, ["success_count"]; Keyword arguments, {} 1168Insecure HTTP Connection found Match: requests.get Positional arguments, ["trackme_summary_idx"]; Keyword arguments, {} 12843Insecure HTTP Connection found Match: requests.get Positional arguments, ["tracker_report"]; Keyword arguments, {} 375Insecure HTTP Connection found Match: requests.get Positional arguments, ["trackme_metric_idx", "trackme_metrics"]; Keyword arguments, {} 3534Insecure HTTP Connection found Match: requests.get Positional arguments, ["retry_initial_delay"]; Keyword arguments, {} 627Insecure HTTP Connection found Match: requests.get Positional arguments, ["retry_initial_delay", "2"]; Keyword arguments, {} 3240Insecure HTTP Connection found Match: requests.get Positional arguments, ["payload"]; Keyword arguments, {} 12845Insecure HTTP Connection found Match: requests.get Positional arguments, ["earliest"]; Keyword arguments, {} 177Insecure HTTP Connection found Match: requests.Session.get Positional arguments, ["trackme_metric_idx", "trackme_metrics"]; Keyword arguments, {} 612Insecure HTTP Connection found Match: requests.get Positional arguments, ["timeout_search_check", "?"]; Keyword arguments, {} 2230Insecure HTTP Connection found Match: requests.get Positional arguments, ["owner"]; Keyword arguments, {} 2099Insecure HTTP Connection found Match: requests.get Positional arguments, ["owner"]; Keyword arguments, {} 601Insecure HTTP Connection found Match: requests.Session.get Positional arguments, ["timeout_connect_check", "?"]; Keyword arguments, {} 612Insecure HTTP Connection found Match: requests.Session.get Positional arguments, ["timeout_search_check", "?"]; Keyword arguments, {} 2721Insecure HTTP Connection found Match: requests.get Positional arguments, ["message"]; Keyword arguments, {} 177Insecure HTTP Connection found Match: urllib.request.urlopen Positional arguments, ["utf-8"]; Keyword arguments, {} 3503Insecure HTTP Connection found Match: requests.get Positional arguments, ["allowed_email_domains", "?"]; Keyword arguments, {} 625Insecure HTTP Connection found Match: requests.Session.get Positional arguments, ["retry_enabled", "1"]; Keyword arguments, {} 152Insecure HTTP Connection found Match: requests.post Positional arguments, ["/servicesNS/nobody/trackme/storage/collections/data/kv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenantskv_trackme_virtual_tenants"]; Keyword arguments, {"headers": "?", "data": "?", "verify": "?", "timeout": "?"} 2052Insecure HTTP Connection found Match: requests.get Positional arguments, ["trackme_version", "unknown"]; Keyword arguments, {} 629Insecure HTTP Connection found Match: requests.get Positional arguments, ["retry_max_attempts", "10"]; Keyword arguments, {} 628Insecure HTTP Connection found Match: requests.get Positional arguments, ["retry_backoff_multiplier", "2.0"]; Keyword arguments, {} 2102Insecure HTTP Connection found Match: requests.get Positional arguments, ["sharing"]; Keyword arguments, {} 601Insecure HTTP Connection found Match: requests.get Positional arguments, ["timeout_connect_check", "?"]; Keyword arguments, {} 3530Insecure HTTP Connection found Match: requests.get Positional arguments, ["retry_enabled"]; Keyword arguments, {} 5072Insecure HTTP Connection found Match: requests.get Positional arguments, ["archive_base64"]; Keyword arguments, {} 625Insecure HTTP Connection found Match: requests.get Positional arguments, ["retry_enabled", "1"]; Keyword arguments, {} 207Insecure HTTP Connection found Match: requests.post Positional arguments, ["/services/trackme/v2/component/write/refresh_shadow/services/trackme/v2/component/write/refresh_shadow"]; Keyword arguments, {"headers": "?", "json": "?", "verify": "?", "timeout": "?"} 626Insecure HTTP Connection found Match: requests.Session.get Positional arguments, ["retry_max_total_time", "30"]; Keyword arguments, {} 2328Insecure HTTP Connection found Match: requests.get Positional arguments, ["collection"]; Keyword arguments, {} 2308Insecure HTTP Connection found Match: requests.get Positional arguments, ["type"]; Keyword arguments, {} 3532Insecure HTTP Connection found Match: requests.get Positional arguments, ["retry_max_total_time"]; Keyword arguments, {} 3518Insecure HTTP Connection found Match: requests.get Positional arguments, ["token"]; Keyword arguments, {} 13266Insecure HTTP Connection found Match: requests.get Positional arguments, ["tracker_name"]; Keyword arguments, {} 3909Insecure HTTP Connection found Match: requests.get Positional arguments, ["files_purged", "?"]; Keyword arguments, {} 626Insecure HTTP Connection found Match: requests.get Positional arguments, ["retry_max_total_time", "30"]; Keyword arguments, {} 561Insecure HTTP Connection found Match: requests.get Positional arguments, ["entities_outliers"]; Keyword arguments, {} Suppressed 300 warning messages2634Insecure HTTP Connection found Match: requests.get Positional arguments, ["token", "?"]; Keyword arguments, {} 232Insecure HTTP Connection found Match: requests.get Positional arguments, ["payload"]; Keyword arguments, {} 3467Insecure HTTP Connection found Match: requests.get Positional arguments, ["email_incident_subject_template", ""]; Keyword arguments, {} 271Insecure HTTP Connection found Match: requests.get Positional arguments, ["num_pages", "?"]; Keyword arguments, {} 2321Insecure HTTP Connection found Match: requests.get Positional arguments, ["definition"]; Keyword arguments, {} 3521Insecure HTTP Connection found Match: requests.get Positional arguments, ["timeout_connect_check", "?"]; Keyword arguments, {} 2325Insecure HTTP Connection found Match: requests.get Positional arguments, ["definition"]; Keyword arguments, {} 2309Insecure HTTP Connection found Match: requests.get Positional arguments, ["title"]; Keyword arguments, {} 248Insecure HTTP Connection found Match: requests.get Positional arguments, ["success_count"]; Keyword arguments, {} 3451Insecure HTTP Connection found Match: requests.get Positional arguments, ["email_static_incident_subject", "?"]; Keyword arguments, {} 2272Insecure HTTP Connection found Match: requests.get Positional arguments, ["owner"]; Keyword arguments, {} 1153Insecure HTTP Connection found Match: requests.Session.get Positional arguments, ["trackme_metric_idx"]; Keyword arguments, {} 168Insecure HTTP Connection found Match: urllib.request.urlopen Positional arguments, ["utf-8"]; Keyword arguments, {} 3255Insecure HTTP Connection found Match: requests.get Positional arguments, ["payload"]; Keyword arguments, {} 3538Insecure HTTP Connection found Match: requests.get Positional arguments, ["retry_max_attempts"]; Keyword arguments, {} 2322Insecure HTTP Connection found Match: requests.get Positional arguments, ["alert_properties"]; Keyword arguments, {} 562Insecure HTTP Connection found Match: requests.get Positional arguments, ["entity_outlier"]; Keyword arguments, {} 3524Insecure HTTP Connection found Match: requests.get Positional arguments, ["timeout_search_check", "?"]; Keyword arguments, {} 2318Insecure HTTP Connection found Match: requests.get Positional arguments, ["definition"]; Keyword arguments, {} 16236Insecure HTTP Connection found Match: requests.get Positional arguments, ["download_token"]; Keyword arguments, {} 3712Insecure HTTP Connection found Match: requests.get Positional arguments, ["ack_mtime", "?"]; Keyword arguments, {} 5394Insecure HTTP Connection found Match: requests.get Positional arguments, ["email_format", "html"]; Keyword arguments, {} 2704Insecure HTTP Connection found Match: requests.get Positional arguments, ["payload"]; Keyword arguments, {} 177Insecure HTTP Connection found Match: requests.get Positional arguments, ["trackme_metric_idx", "trackme_metrics"]; Keyword arguments, {} 2268Insecure HTTP Connection found Match: requests.get Positional arguments, ["vtenant_account"]; Keyword arguments, {} 234Insecure HTTP Connection found Match: requests.get Positional arguments, ["shadow_refresh"]; Keyword arguments, {} 238Insecure HTTP Connection found Match: requests.get Positional arguments, ["/services/server/info"]; Keyword arguments, {"headers": "?", "params": "?", "verify": "?", "timeout": "?"} 1168Insecure HTTP Connection found Match: requests.Session.get Positional arguments, ["trackme_summary_idx"]; Keyword arguments, {} 10003Insecure HTTP Connection found Match: requests.get Positional arguments, ["response"]; Keyword arguments, {} 13265Insecure HTTP Connection found Match: requests.get Positional arguments, ["tracker_report"]; Keyword arguments, {} 661Insecure HTTP Connection found Match: requests.get Positional arguments, ["data_sampling_obfuscation"]; Keyword arguments, {} 16321Insecure HTTP Connection found Match: requests.get Positional arguments, ["archive_base64"]; Keyword arguments, {} 2233Insecure HTTP Connection found Match: requests.get Positional arguments, ["sharing"]; Keyword arguments, {} 5071Insecure HTTP Connection found Match: requests.get Positional arguments, ["download_token"]; Keyword arguments, {} 2329Insecure HTTP Connection found Match: requests.get Positional arguments, ["fields_list"]; Keyword arguments, {} 3519Insecure HTTP Connection found Match: requests.get Positional arguments, ["app_namespace", "search"]; Keyword arguments, {} 375Insecure HTTP Connection found Match: requests.Session.get Positional arguments, ["trackme_metric_idx", "trackme_metrics"]; Keyword arguments, {} 15300Insecure HTTP Connection found Match: requests.get Positional arguments, ["/services/trackme/v2/backup_and_restore/backup"]; Keyword arguments, {"headers": "?", "verify": "?", "timeout": "?"} 2716Insecure HTTP Connection found Match: requests.get Positional arguments, ["payload"]; Keyword arguments, {} 12844Insecure HTTP Connection found Match: requests.get Positional arguments, ["tracker_name"]; Keyword arguments, {} 757Insecure HTTP Connection found Match: requests.get Positional arguments, ["trackme_conf"]; Keyword arguments, {} 13267Insecure HTTP Connection found Match: requests.get Positional arguments, ["earliest"]; Keyword arguments, {} 628Insecure HTTP Connection found Match: requests.Session.get Positional arguments, ["retry_backoff_multiplier", "2.0"]; Keyword arguments, {} 1153Insecure HTTP Connection found Match: requests.get Positional arguments, ["trackme_metric_idx"]; Keyword arguments, {} 629Insecure HTTP Connection found Match: requests.Session.get Positional arguments, ["retry_max_attempts", "10"]; Keyword arguments, {} 16243Insecure HTTP Connection found Match: requests.get Positional arguments, ["filename", ".tgz"]; Keyword arguments, {} 309Insecure HTTP Connection found Match: requests.post Positional arguments, ["/services/trackme/v2/topology_alerts/write/disable_alert"]; Keyword arguments, {"headers": "?", "data": "?", "verify": "?", "timeout": "?"} 3711Insecure HTTP Connection found Match: requests.get Positional arguments, ["ack_state", "inactive"]; Keyword arguments, {} 2313Insecure HTTP Connection found Match: requests.get Positional arguments, ["properties", "?"]; Keyword arguments, {} 3906Insecure HTTP Connection found Match: requests.get Positional arguments, ["status", "Unknown status"]; Keyword arguments, {} 13268Insecure HTTP Connection found Match: requests.get Positional arguments, ["latest"]; Keyword arguments, {} 12846Insecure HTTP Connection found Match: requests.get Positional arguments, ["latest"]; Keyword arguments, {} 170Insecure HTTP Connection found Match: urllib.request.urlopen Positional arguments, ["utf-8"]; Keyword arguments, {} 8635Insecure HTTP Connection found Match: requests.get Positional arguments, ["archives"]; Keyword arguments, {} 627Insecure HTTP Connection found Match: requests.Session.get Positional arguments, ["retry_initial_delay", "2"]; Keyword arguments, {} 16214Insecure HTTP Connection found Match: requests.get Positional arguments, ["payload", "?"]; Keyword arguments, {} 1720Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 458Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 2004Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 2260Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 21077Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 205Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 21238Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 20522Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 2987Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. Suppressed 367 warning messages2921Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 2177Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 15300Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 20836Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 72Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 13209Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 2294Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 2921Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 227Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 419Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 5783Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 3213Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 22569Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 3295Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 3222Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 16249Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 3698Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 3539Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 3193Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 121Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 20936Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 534Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 145Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 1685Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 3493Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 238Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 207Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 2235Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 4931Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 389Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 2843Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 79Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 21331Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 2279Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 152Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 264Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 2670Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 309Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 320Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 1789Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 21489Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 5057Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 12710Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 22338Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 186Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 359Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 813Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 22159Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 21920Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 3085Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 567Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 16203Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 3589Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 9957Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 21848Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 2681Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 239Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 2533Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 22635Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 2078Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 1674Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 30Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 5132Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 2613Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 3693Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 953Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 7852Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 365Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 12787Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 428Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 1848Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 62Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 21582Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 234Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 650Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 20628Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 13132Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 1722Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 20756Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 1964Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 154Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 10228Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 358Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 237Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 8583Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 61Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 3765Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 3214Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 3406Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 3489Ensure that the SSL certificate validation for communications with outside the Splunk Cloud stack is enabled. This can be done by specifying the relevant parameters (verify, cafile etc) to True or the certificate path. 58Detected solnlib (version 8.1.1). No action required. 17Detected splunktaucclib (version 8.2.0). No action required.