| Author | TrackMe Limited, U.K. |
|---|---|
| Tags | cloud |
| Version | 2.3.2 |
| Hash | aa45f7d962840ed843e11bf2f70ace5b |
| AppInspect Request ID | 47edf330-bc02-423f-b8f4-ea9175cee30f |
| Run Time | 2025-12-11T11:37:10.414980 |
| Execution Time | 324 |
| Field | Value |
|---|---|
| AppInspect Version | 4.1.2 |
| Name | Version | Is Latest |
|---|---|---|
| dynamic-checks | 1.44.2 | True |
| retire-js | 1.1.1 | True |
| static-checks | 4.1.2 | True |
| Status | Count |
|---|---|
|
Successes
|
136 |
|
Failures
|
0 |
|
Errors
|
0 |
|
Warnings
|
16 |
|
Not Applicable
|
72 |
|
Skipped
|
1 |
The app works for MS Windows platform because lib/3rdparty/windows/_rl_renderPM.cp39-win_amd64.pyd exists, which is PE32+ executable (DLL) (GUI) x86-64, for MS Windows. It is only valid at MS Windows platform.
The app works for MS Windows platform because lib/3rdparty/windows/lxml/html/diff.cp39-win_amd64.pyd exists, which is PE32+ executable (DLL) (GUI) x86-64, for MS Windows. It is only valid at MS Windows platform.
The app works for MS Windows platform because lib/3rdparty/windows/lxml/objectify.cp39-win_amd64.pyd exists, which is PE32+ executable (DLL) (GUI) x86-64, for MS Windows. It is only valid at MS Windows platform.
The app works for MS Windows platform because lib/3rdparty/windows/lxml/sax.cp39-win_amd64.pyd exists, which is PE32+ executable (DLL) (GUI) x86-64, for MS Windows. It is only valid at MS Windows platform.
The app works for MS Windows platform because lib/3rdparty/windows/lxml/_elementpath.cp39-win_amd64.pyd exists, which is PE32+ executable (DLL) (GUI) x86-64, for MS Windows. It is only valid at MS Windows platform.
The app works for MS Windows platform because lib/3rdparty/windows/lxml/etree.cp39-win_amd64.pyd exists, which is PE32+ executable (DLL) (GUI) x86-64, for MS Windows. It is only valid at MS Windows platform.
The app works for MS Windows platform because lib/3rdparty/windows/PIL/_imagingcms.cp39-win_amd64.pyd exists, which is PE32+ executable (DLL) (GUI) x86-64, for MS Windows. It is only valid at MS Windows platform.
The app works for MS Windows platform because lib/3rdparty/windows/PIL/_imagingtk.cp39-win_amd64.pyd exists, which is PE32+ executable (DLL) (GUI) x86-64, for MS Windows. It is only valid at MS Windows platform.
The app works for MS Windows platform because lib/3rdparty/windows/lxml/builder.cp39-win_amd64.pyd exists, which is PE32+ executable (DLL) (GUI) x86-64, for MS Windows. It is only valid at MS Windows platform.
The app works for MS Windows platform because lib/3rdparty/windows/PIL/_webp.cp39-win_amd64.pyd exists, which is PE32+ executable (DLL) (GUI) x86-64, for MS Windows. It is only valid at MS Windows platform.
The app works for MS Windows platform because lib/3rdparty/windows/PIL/_imagingmorph.cp39-win_amd64.pyd exists, which is PE32+ executable (DLL) (GUI) x86-64, for MS Windows. It is only valid at MS Windows platform.
The app works for MS Windows platform because lib/3rdparty/windows/PIL/_imagingmath.cp39-win_amd64.pyd exists, which is PE32+ executable (DLL) (GUI) x86-64, for MS Windows. It is only valid at MS Windows platform.
The app works for MS Windows platform because lib/3rdparty/windows/PIL/_imagingft.cp39-win_amd64.pyd exists, which is PE32+ executable (DLL) (GUI) x86-64, for MS Windows. It is only valid at MS Windows platform.
The app works for MS Windows platform because lib/3rdparty/windows/PIL/_imaging.cp39-win_amd64.pyd exists, which is PE32+ executable (DLL) (GUI) x86-64, for MS Windows. It is only valid at MS Windows platform.
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
196Splunk 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
267Splunk 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
656Splunk 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
1094Splunk 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
267As of Splunk 6.5, this functionality is deprecated and should be removed in futureapp versions. Match: splunkjs/mvc/headerview.
1060 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.
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
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
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
105The '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
95The '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
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
102The '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
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
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
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
89The '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
86The '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
35Splunk SDK for Python detected (version 2.1.1). No action required at this time.
319Found usage of `mmap.mmap` which might not work on every operating system.
319Found 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.
574Found usage of `mmap.mmap` which might not work on every operating system.
471The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion.
878The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion.
223The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion.
159The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion.
349The following line contains subprocess.Popen.communicate usage. Use threading and multiprocessing with discretion.
361The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion.
346The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion.
52The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion.
166The following line contains questionable usage `threading.Thread.start` in loop. Use threading and multiprocessing with discretion.
187The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion.
889The 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.
182The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion.
139The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion.
253The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion.
187The following line contains subprocess.Popen.communicate usage. Use threading and multiprocessing with discretion.
223The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion.
177The following line contains subprocess.call usage. Use threading and multiprocessing with discretion.
139The following line contains subprocess.Popen.communicate usage. Use threading and multiprocessing with discretion.
289The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion.
271The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion.
197The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion.
861The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion.
369The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion.
878The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion.
861The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion.
98The following line contains subprocess.call usage. Use threading and multiprocessing with discretion.
371The following line contains questionable usage `threading.Thread.start` in loop. Use threading and multiprocessing with discretion.
61The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion.
253The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion.
271The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion.
2607The following line contains questionable usage `threading.Thread.start` in loop. Use threading and multiprocessing with discretion.
180The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion.
889The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion.
321The 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.
2362The following line contains questionable usage `threading.Thread.start` in loop. Use threading and multiprocessing with discretion.
321The 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.
471The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion.
177The following line contains subprocess.call usage. Use threading and multiprocessing with discretion.
49The following line contains subprocess.call usage. Use threading and multiprocessing with discretion.
98The following line contains subprocess.call usage. Use threading and multiprocessing with discretion.
886The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion.
886The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion.
159The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion.
146The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion.
49The following line contains subprocess.call usage. Use threading and multiprocessing with discretion.
146The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion.
289The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion.
180The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion.
70PUBLIC IP 5.5.5.5 is found in lib/PySocks-1.7.1.dist-info/METADATA:70
25495PUBLIC IP 6.7.8.5 is found in lib/3rdparty/linux_with_deps/lxml/objectify.cpython-39-x86_64-linux-gnu.so:25495
54096PUBLIC IP 6.7.8.5 is found in lib/3rdparty/windows/lxml/etree.cp39-win_amd64.pyd:54096
2PUBLIC IP 12.21.1.11 is found in appserver/static/pages/VirtualTenants.js:2
5PUBLIC IP 4.2.1.1 is found in lib/reportlab/platypus/tableofcontents.py:5
23232PUBLIC IP 6.7.8.5 is found in lib/3rdparty/windows/lxml/objectify.cp39-win_amd64.pyd:23232
196PUBLIC IP 12.21.1.11 is found in appserver/static/pages/TenantHome.js:196
52805PUBLIC IP 6.7.8.5 is found in lib/3rdparty/linux_with_deps/lxml/etree.cpython-39-x86_64-linux-gnu.so:52805
Detected use of a third-party Mako template, which poses a critical security risk by allowing arbitrary Python code execution. Remove custom Mako templates.
Detected use of a third-party Mako template, which poses a critical security risk by allowing arbitrary Python code execution. Remove custom Mako templates.
Detected use of a third-party Mako template, which poses a critical security risk by allowing arbitrary Python code execution. Remove custom Mako templates.
Detected use of a third-party Mako template, which poses a critical security risk by allowing arbitrary Python code execution. Remove custom Mako templates.
Detected use of a third-party Mako template, which poses a critical security risk by allowing arbitrary Python code execution. Remove custom Mako templates.
Detected use of a third-party Mako template, which poses a critical security risk by allowing arbitrary Python code execution. Remove custom Mako templates.
Detected use of a third-party Mako template, which poses a critical security risk by allowing arbitrary Python code execution. Remove custom Mako templates.
Detected use of a third-party Mako template, which poses a critical security risk by allowing arbitrary Python code execution. Remove custom Mako templates.
279Insecure HTTP Connection found Match: requests.get Positional arguments, ["search_results"]; Keyword arguments, {}
259Insecure HTTP Connection found Match: requests.get Positional arguments, ["error_messages", "?"]; Keyword arguments, {}
718Insecure HTTP Connection found Match: requests.post Positional arguments, ["/services/trackme/v2/maintenance_kdb/admin/maintenance_kdb_add_record"]; Keyword arguments, {"data": "?", "headers": "?", "verify": "?", "timeout": "?"}
1640Insecure HTTP Connection found Match: requests.get Positional arguments, ["trackme_metric_idx"]; Keyword arguments, {}
817Insecure HTTP Connection found Match: requests.get Positional arguments, ["app"]; Keyword arguments, {}
3532Insecure HTTP Connection found Match: requests.get Positional arguments, ["acl", "?"]; Keyword arguments, {}
1191Insecure HTTP Connection found Match: requests.Session.get Positional arguments, ["data_sampling_obfuscation"]; Keyword arguments, {}
975Insecure HTTP Connection found Match: requests.Session.get Positional arguments, ["sampling"]; Keyword arguments, {}
1309Insecure HTTP Connection found Match: requests.get Positional arguments, ["is_elastic", "?"]; Keyword arguments, {}
819Insecure HTTP Connection found Match: requests.get Positional arguments, ["orphan"]; Keyword arguments, {}
907Insecure HTTP Connection found Match: requests.get Positional arguments, ["workload_pool"]; Keyword arguments, {}
2325Insecure HTTP Connection found Match: requests.get Positional arguments, ["status", "Unknown status"]; Keyword arguments, {}
185Insecure HTTP Connection found Match: requests.get Positional arguments, ["splk_outliers_static_lower_threshold", "?"]; Keyword arguments, {}
1284Insecure HTTP Connection found Match: requests.get Positional arguments, ["definition"]; Keyword arguments, {}
6084Insecure HTTP Connection found Match: requests.get Positional arguments, ["archive_base64"]; Keyword arguments, {}
238Insecure HTTP Connection found Match: requests.get Positional arguments, ["action", "failure"]; Keyword arguments, {}
102Insecure HTTP Connection found Match: requests.get Positional arguments, ["ack_state", "inactive"]; Keyword arguments, {}
851Insecure HTTP Connection found Match: requests.Session.get Positional arguments, ["adaptive_delay", "?"]; Keyword arguments, {}
1083Insecure HTTP Connection found Match: requests.get Positional arguments, ["account"]; Keyword arguments, {}
2710Insecure HTTP Connection found Match: requests.get Positional arguments, ["ack_mtime", "?"]; Keyword arguments, {}
188Insecure HTTP Connection found Match: requests.get Positional arguments, ["splk_outliers_static_upper_threshold", "?"]; Keyword arguments, {}
1310Insecure HTTP Connection found Match: requests.get Positional arguments, ["collection"]; Keyword arguments, {}
269Insecure HTTP Connection found Match: requests.get Positional arguments, ["trackme_metric_idx"]; Keyword arguments, {}
1163Insecure HTTP Connection found Match: requests.get Positional arguments, ["vtenant_account"]; Keyword arguments, {}
1263Insecure HTTP Connection found Match: requests.get Positional arguments, ["type"]; Keyword arguments, {}
1133Insecure HTTP Connection found Match: requests.get Positional arguments, ["?", ""]; Keyword arguments, {}
901Insecure HTTP Connection found Match: requests.get Positional arguments, ["description"]; Keyword arguments, {}
6017Insecure HTTP Connection found Match: requests.get Positional arguments, ["download_token"]; Keyword arguments, {}
182Insecure HTTP Connection found Match: requests.get Positional arguments, ["splk_outliers_apply_extra_parameters", "?"]; Keyword arguments, {}
344Insecure HTTP Connection found Match: requests.get Positional arguments, ["trackme_general", "?"]; Keyword arguments, {}
975Insecure HTTP Connection found Match: requests.get Positional arguments, ["sampling"]; Keyword arguments, {}
1269Insecure HTTP Connection found Match: requests.get Positional arguments, ["properties", "?"]; Keyword arguments, {}
1311Insecure HTTP Connection found Match: requests.get Positional arguments, ["fields_list"]; Keyword arguments, {}
344Insecure HTTP Connection found Match: requests.get Positional arguments, ["icons_state_mode", "emoji"]; Keyword arguments, {}
Suppressed 81 warning messages
1071Insecure HTTP Connection found Match: requests.get Positional arguments, ["splk_dsm_sampling_search", "?"]; Keyword arguments, {}
308Insecure HTTP Connection found Match: requests.get Positional arguments, ["model_exists"]; Keyword arguments, {}
3187Insecure HTTP Connection found Match: requests.get Positional arguments, ["archive_base64"]; Keyword arguments, {}
1302Insecure HTTP Connection found Match: requests.get Positional arguments, ["splk_dsm_sampling_search", "?"]; Keyword arguments, {}
159Insecure HTTP Connection found Match: requests.Session.get Positional arguments, ["splk__cmdb_search"]; Keyword arguments, {}
438Insecure HTTP Connection found Match: requests.get Positional arguments, ["response"]; Keyword arguments, {}
842Insecure HTTP Connection found Match: requests.get Positional arguments, ["trackme_audit_idx", "trackme_audit"]; Keyword arguments, {}
1191Insecure HTTP Connection found Match: requests.get Positional arguments, ["data_sampling_obfuscation"]; Keyword arguments, {}
368Insecure HTTP Connection found Match: requests.get Positional arguments, ["response"]; Keyword arguments, {}
103Insecure HTTP Connection found Match: requests.get Positional arguments, ["ack_mtime", "?"]; Keyword arguments, {}
244Insecure HTTP Connection found Match: requests.get Positional arguments, ["response"]; Keyword arguments, {}
1960Insecure HTTP Connection found Match: requests.Session.get Positional arguments, ["splk_feeds_auto_disablement_period"]; Keyword arguments, {}
1444Insecure HTTP Connection found Match: requests.Session.post Positional arguments, ["/services/trackme/v2/backup_and_restore/backup"]; Keyword arguments, {"data": "?", "verify": "?", "timeout": "?"}
275Insecure HTTP Connection found Match: requests.get Positional arguments, ["description", ""]; Keyword arguments, {}
900Insecure HTTP Connection found Match: requests.get Positional arguments, ["cron_schedule"]; Keyword arguments, {}
1303Insecure HTTP Connection found Match: requests.get Positional arguments, ["definition"]; Keyword arguments, {}
902Insecure HTTP Connection found Match: requests.get Positional arguments, ["disabled"]; Keyword arguments, {}
2709Insecure HTTP Connection found Match: requests.get Positional arguments, ["ack_state", "inactive"]; Keyword arguments, {}
818Insecure HTTP Connection found Match: requests.get Positional arguments, ["sharing"]; Keyword arguments, {}
276Insecure HTTP Connection found Match: requests.get Positional arguments, ["alias", "?"]; Keyword arguments, {}
951Insecure HTTP Connection found Match: requests.get Positional arguments, ["?", ""]; Keyword arguments, {}
2320Insecure HTTP Connection found Match: requests.get Positional arguments, ["trackme_metric_idx"]; Keyword arguments, {}
159Insecure HTTP Connection found Match: requests.get Positional arguments, ["splk__cmdb_search"]; Keyword arguments, {}
903Insecure HTTP Connection found Match: requests.get Positional arguments, ["is_scheduled"]; Keyword arguments, {}
2474Insecure HTTP Connection found Match: requests.get Positional arguments, [""]; Keyword arguments, {"headers": "?", "verify": "?", "timeout": "?", "params": "?"}
213Insecure HTTP Connection found Match: requests.post Positional arguments, ["/services/trackme/v2/splk_logical_groups/write/logical_groups_del_grp"]; Keyword arguments, {"headers": "?", "data": "?", "verify": "?", "timeout": "?"}
2633Insecure HTTP Connection found Match: requests.get Positional arguments, ["allowed_email_domains", "?"]; Keyword arguments, {}
1266Insecure HTTP Connection found Match: requests.get Positional arguments, ["title"]; Keyword arguments, {}
2061Insecure HTTP Connection found Match: requests.get Positional arguments, ["success_count"]; Keyword arguments, {}
842Insecure HTTP Connection found Match: requests.Session.get Positional arguments, ["trackme_audit_idx", "trackme_audit"]; Keyword arguments, {}
2061Insecure HTTP Connection found Match: requests.Session.get Positional arguments, ["success_count"]; Keyword arguments, {}
911Insecure HTTP Connection found Match: requests.get Positional arguments, ["dispatch.latest_time"]; Keyword arguments, {}
140Insecure HTTP Connection found Match: requests.post Positional arguments, ["/services/trackme/v2/splk_logical_groups/write/logical_groups_update_group_list"]; Keyword arguments, {"headers": "?", "data": "?", "verify": "?", "timeout": "?"}
908Insecure HTTP Connection found Match: requests.get Positional arguments, ["dispatch.earliest_time"]; Keyword arguments, {}
179Insecure HTTP Connection found Match: requests.get Positional arguments, ["splk_outliers_fit_extra_parameters", "?"]; Keyword arguments, {}
2690Insecure HTTP Connection found Match: requests.post Positional arguments, ["/services/trackme/v2/ack/get_ack_for_object"]; Keyword arguments, {"headers": "?", "data": "?", "verify": "?", "timeout": "?"}
907Insecure HTTP Connection found Match: requests.post Positional arguments, ["/services/trackme/v2/maintenance_kdb/admin/maintenance_kdb_manage_record"]; Keyword arguments, {"data": "?", "headers": "?", "verify": "?", "timeout": "?"}
1444Insecure HTTP Connection found Match: requests.post Positional arguments, ["/services/trackme/v2/backup_and_restore/backup"]; Keyword arguments, {"data": "?", "verify": "?", "timeout": "?"}
3509Insecure HTTP Connection found Match: requests.get Positional arguments, ["email_format", "html"]; Keyword arguments, {}
179Insecure HTTP Connection found Match: requests.post Positional arguments, ["/services/trackme/v2/splk_logical_groups/write/logical_groups_remove_object_from_groups"]; Keyword arguments, {"headers": "?", "data": "?", "verify": "?", "timeout": "?"}
1291Insecure HTTP Connection found Match: requests.get Positional arguments, ["definition"]; Keyword arguments, {}
6018Insecure HTTP Connection found Match: requests.get Positional arguments, ["filename", "?"]; Keyword arguments, {}
729Insecure HTTP Connection found Match: requests.get Positional arguments, ["record_id"]; Keyword arguments, {}
172Insecure HTTP Connection found Match: requests.get Positional arguments, ["splk_outliers_mltk_algorithms_default", "DensityFunction"]; Keyword arguments, {}
269Insecure HTTP Connection found Match: requests.Session.get Positional arguments, ["trackme_metric_idx"]; Keyword arguments, {}
944Insecure HTTP Connection found Match: requests.get Positional arguments, ["?", ""]; Keyword arguments, {}
195Insecure HTTP Connection found Match: requests.get Positional arguments, ["response"]; Keyword arguments, {}
175Insecure HTTP Connection found Match: requests.get Positional arguments, ["splk_outliers_boundaries_extraction_macro_default", "splk_outliers_extract_boundaries"]; Keyword arguments, {}
2320Insecure HTTP Connection found Match: requests.Session.get Positional arguments, ["trackme_metric_idx"]; Keyword arguments, {}
2328Insecure HTTP Connection found Match: requests.get Positional arguments, ["files_purged", "?"]; Keyword arguments, {}
221Insecure HTTP Connection found Match: requests.post Positional arguments, ["/services/trackme/v2/maintenance_kdb/admin/maintenance_kdb_manage_record"]; Keyword arguments, {"data": "?", "headers": "?", "verify": "?", "timeout": "?"}
342Insecure HTTP Connection found Match: requests.get Positional arguments, ["success_count"]; Keyword arguments, {}
292Insecure HTTP Connection found Match: requests.get Positional arguments, ["response"]; Keyword arguments, {}
1310Insecure HTTP Connection found Match: requests.get Positional arguments, ["search_mode", "unknown"]; Keyword arguments, {}
1071Insecure HTTP Connection found Match: requests.get Positional arguments, ["trackme_version", "unknown"]; Keyword arguments, {}
1294Insecure HTTP Connection found Match: requests.get Positional arguments, ["alert_properties"]; Keyword arguments, {}
1960Insecure HTTP Connection found Match: requests.get Positional arguments, ["splk_feeds_auto_disablement_period"]; Keyword arguments, {}
203Insecure HTTP Connection found Match: requests.get Positional arguments, ["alias", "?"]; Keyword arguments, {}
1116Insecure HTTP Connection found Match: requests.get Positional arguments, ["?", ""]; Keyword arguments, {}
904Insecure HTTP Connection found Match: requests.get Positional arguments, ["schedule_window"]; Keyword arguments, {}
816Insecure HTTP Connection found Match: requests.get Positional arguments, ["owner"]; Keyword arguments, {}
83Insecure HTTP Connection found Match: requests.post Positional arguments, ["/services/trackme/v2/ack/get_ack_for_object"]; Keyword arguments, {"headers": "?", "data": "?", "verify": "?", "timeout": "?"}
851Insecure HTTP Connection found Match: requests.get Positional arguments, ["adaptive_delay", "?"]; Keyword arguments, {}
6061Insecure HTTP Connection found Match: requests.get Positional arguments, ["archive_base64"]; Keyword arguments, {}
1395Insecure HTTP Connection found Match: requests.get Positional arguments, ["_raw"]; Keyword arguments, {}
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.
5631Ensure 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.
224Ensure 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.
1692Ensure 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.
1940Ensure 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.
2182Ensure 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.
2418Ensure 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.
340Ensure 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.
2393Ensure 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.
339Ensure 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.
155Ensure 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.
162Ensure 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.
58Ensure 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.
1378Ensure 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.
228Ensure 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.
140Ensure 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.
3174Ensure 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.
180Ensure 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.
3859Ensure 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.
943Ensure 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.
1811Ensure 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.
208Ensure 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.
2220Ensure 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 218 warning messages
2181Ensure 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.
1998Ensure 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.
2474Ensure 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.
847Ensure 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.
604Ensure 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.
946Ensure 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.
3108Ensure 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.
153Ensure 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.
2270Ensure 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.
1237Ensure 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.
107Ensure 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.
286Ensure 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.
179Ensure 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.
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.
646Ensure 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.
1388Ensure 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.
322Ensure 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.
2325Ensure 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.
497Ensure 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.
2435Ensure 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.
161Ensure 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.
83Ensure 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.
2293Ensure 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.
6026Ensure 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.
1628Ensure 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.
1769Ensure 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.
296Ensure 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.
213Ensure 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.
907Ensure 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.
1877Ensure 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.
2383Ensure 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.
159Ensure 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.
321Ensure 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.
2098Ensure 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.
179Ensure 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.
2450Ensure 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.
221Ensure 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.
353Ensure 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.
173Ensure 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.
516Ensure 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.
602Ensure 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.
3231Ensure 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.
773Ensure 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.
1298Ensure 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.
2552Ensure 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.
265Ensure 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.
2617Ensure 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.
221Ensure 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.
206Ensure 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.
225Ensure 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.
1153Ensure 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.
188Ensure 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.
1713Ensure 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.
260Ensure 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.
228Ensure 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.
2502Ensure 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.
2351Ensure 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.
173Ensure 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.
1435Ensure 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.
6000Ensure 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.
94Ensure 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.
718Ensure 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.
259Ensure 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.
480Ensure 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.
273Ensure 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.
2690Ensure 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.
390Ensure 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.
179Ensure 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.
1647Ensure 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.
1048Ensure 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.
721Ensure 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.
3453Ensure 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.
132Ensure 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.
17Detected splunktaucclib (version 8.0.0). No action required.
59Detected solnlib (version 7.0.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 exist
authentication.conf does not exist
authentication.conf does not exist
Didn't find any flash files.
inputs.conf does not exist
inputs.conf does not exist
`inputs.conf` does not exist.
inputs.conf does not exist
authentication.conf does not exist
audit.conf does not exist
bookmarks.conf does not exist
datatypesbnf.conf does not exist
default-mode.conf does not exist
deploymentclient.conf does not exist
deployment.conf does not exist
inputs.conf.conf does not exist
health.conf does not exist
inputs.conf.conf does not exist
inputs.conf does not exist
inputs.conf does not exist
inputs.conf does not exist
inputs.conf.conf does not exist
inputs.conf does not exist
inputs.conf does not exist
inputs.conf.conf does not exist
inputs.conf does not exist
instance.cfg.conf does not exist
crawl.conf does not exist
literals.conf does not exist
messages.conf does not exist
No `inputs.conf.spec` was detected.
passwords.conf does not exist
pubsub.conf does not exist
segmenters.conf does not exist
serverclass.conf does not exist
serverclass.seed.xml.conf does not exist
source-classifier.conf does not exist
sourcetypes.conf does not exist
splunk-launch.conf does not exist
telemetry.conf does not exist
The app works for MS Windows platform because lib/3rdparty/windows/_rl_renderPM.cp39-win_amd64.pyd exists, which is PE32+ executable (DLL) (GUI) x86-64, for MS Windows. It is only valid at MS Windows platform.
The app works for MS Windows platform because lib/3rdparty/windows/lxml/html/diff.cp39-win_amd64.pyd exists, which is PE32+ executable (DLL) (GUI) x86-64, for MS Windows. It is only valid at MS Windows platform.
The app works for MS Windows platform because lib/3rdparty/windows/lxml/objectify.cp39-win_amd64.pyd exists, which is PE32+ executable (DLL) (GUI) x86-64, for MS Windows. It is only valid at MS Windows platform.
The app works for MS Windows platform because lib/3rdparty/windows/lxml/sax.cp39-win_amd64.pyd exists, which is PE32+ executable (DLL) (GUI) x86-64, for MS Windows. It is only valid at MS Windows platform.
The app works for MS Windows platform because lib/3rdparty/windows/lxml/_elementpath.cp39-win_amd64.pyd exists, which is PE32+ executable (DLL) (GUI) x86-64, for MS Windows. It is only valid at MS Windows platform.
The app works for MS Windows platform because lib/3rdparty/windows/lxml/etree.cp39-win_amd64.pyd exists, which is PE32+ executable (DLL) (GUI) x86-64, for MS Windows. It is only valid at MS Windows platform.
The app works for MS Windows platform because lib/3rdparty/windows/PIL/_imagingcms.cp39-win_amd64.pyd exists, which is PE32+ executable (DLL) (GUI) x86-64, for MS Windows. It is only valid at MS Windows platform.
The app works for MS Windows platform because lib/3rdparty/windows/PIL/_imagingtk.cp39-win_amd64.pyd exists, which is PE32+ executable (DLL) (GUI) x86-64, for MS Windows. It is only valid at MS Windows platform.
The app works for MS Windows platform because lib/3rdparty/windows/lxml/builder.cp39-win_amd64.pyd exists, which is PE32+ executable (DLL) (GUI) x86-64, for MS Windows. It is only valid at MS Windows platform.
The app works for MS Windows platform because lib/3rdparty/windows/PIL/_webp.cp39-win_amd64.pyd exists, which is PE32+ executable (DLL) (GUI) x86-64, for MS Windows. It is only valid at MS Windows platform.
The app works for MS Windows platform because lib/3rdparty/windows/PIL/_imagingmorph.cp39-win_amd64.pyd exists, which is PE32+ executable (DLL) (GUI) x86-64, for MS Windows. It is only valid at MS Windows platform.
The app works for MS Windows platform because lib/3rdparty/windows/PIL/_imagingmath.cp39-win_amd64.pyd exists, which is PE32+ executable (DLL) (GUI) x86-64, for MS Windows. It is only valid at MS Windows platform.
The app works for MS Windows platform because lib/3rdparty/windows/PIL/_imagingft.cp39-win_amd64.pyd exists, which is PE32+ executable (DLL) (GUI) x86-64, for MS Windows. It is only valid at MS Windows platform.
The app works for MS Windows platform because lib/3rdparty/windows/PIL/_imaging.cp39-win_amd64.pyd exists, which is PE32+ executable (DLL) (GUI) x86-64, for MS Windows. It is only valid at MS Windows platform.
user-seed.conf does not exist
wmi.conf does not exist
workload_pools.conf does not exist
workload_rules.conf does not exist
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
196Splunk 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
267Splunk 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
656Splunk 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
1094Splunk 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
Splunk SDK for JavaScript not found.
limits.conf does not exist
outputs.conf does not exist
data/spl2 does not exist
No invocations of bundled NodeJS binary found.
No `inputs.conf.spec` file exists.
inputs.conf does not exist
eventtypes.conf does not exist
crawl.conf does not exist
viewstates.conf does not exist
outputs.conf does not exist
literals.conf does not exist
1060 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.
README/inputs.conf.spec does not exist.
inputs.conf does not exist
No `inputs.conf.spec` file exists.
4default 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.
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
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
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
105The '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
95The '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
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
102The '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
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
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
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
89The '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
86The '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 exist
datamodels.conf does not exist
No forbidden python files were found.
35Splunk SDK for Python detected (version 2.1.1). No action required at this time.
319Found usage of `mmap.mmap` which might not work on every operating system.
319Found 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.
574Found usage of `mmap.mmap` which might not work on every operating system.
471The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion.
878The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion.
223The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion.
159The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion.
349The following line contains subprocess.Popen.communicate usage. Use threading and multiprocessing with discretion.
361The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion.
346The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion.
52The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion.
166The following line contains questionable usage `threading.Thread.start` in loop. Use threading and multiprocessing with discretion.
187The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion.
889The 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.
182The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion.
139The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion.
253The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion.
187The following line contains subprocess.Popen.communicate usage. Use threading and multiprocessing with discretion.
223The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion.
177The following line contains subprocess.call usage. Use threading and multiprocessing with discretion.
139The following line contains subprocess.Popen.communicate usage. Use threading and multiprocessing with discretion.
289The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion.
271The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion.
197The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion.
861The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion.
369The following line contains subprocess.check_output usage. Use threading and multiprocessing with discretion.
878The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion.
861The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion.
98The following line contains subprocess.call usage. Use threading and multiprocessing with discretion.
371The following line contains questionable usage `threading.Thread.start` in loop. Use threading and multiprocessing with discretion.
61The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion.
253The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion.
271The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion.
2607The following line contains questionable usage `threading.Thread.start` in loop. Use threading and multiprocessing with discretion.
180The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion.
889The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion.
321The 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.
2362The following line contains questionable usage `threading.Thread.start` in loop. Use threading and multiprocessing with discretion.
321The 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.
471The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion.
177The following line contains subprocess.call usage. Use threading and multiprocessing with discretion.
49The following line contains subprocess.call usage. Use threading and multiprocessing with discretion.
98The following line contains subprocess.call usage. Use threading and multiprocessing with discretion.
886The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion.
886The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion.
159The following line contains subprocess.check_call usage. Use threading and multiprocessing with discretion.
146The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion.
49The following line contains subprocess.call usage. Use threading and multiprocessing with discretion.
146The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion.
289The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion.
180The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion.
Python httplib2 library not found.
addon_builder.conf does not exist
70PUBLIC IP 5.5.5.5 is found in lib/PySocks-1.7.1.dist-info/METADATA:70
25495PUBLIC IP 6.7.8.5 is found in lib/3rdparty/linux_with_deps/lxml/objectify.cpython-39-x86_64-linux-gnu.so:25495
54096PUBLIC IP 6.7.8.5 is found in lib/3rdparty/windows/lxml/etree.cp39-win_amd64.pyd:54096
2PUBLIC IP 12.21.1.11 is found in appserver/static/pages/VirtualTenants.js:2
5PUBLIC IP 4.2.1.1 is found in lib/reportlab/platypus/tableofcontents.py:5
23232PUBLIC IP 6.7.8.5 is found in lib/3rdparty/windows/lxml/objectify.cp39-win_amd64.pyd:23232
196PUBLIC IP 12.21.1.11 is found in appserver/static/pages/TenantHome.js:196
52805PUBLIC IP 6.7.8.5 is found in lib/3rdparty/linux_with_deps/lxml/etree.cpython-39-x86_64-linux-gnu.so:52805
No pom.xml, build.gradle or build.gradle.kts file found
Detected use of a third-party Mako template, which poses a critical security risk by allowing arbitrary Python code execution. Remove custom Mako templates.
Detected use of a third-party Mako template, which poses a critical security risk by allowing arbitrary Python code execution. Remove custom Mako templates.
Detected use of a third-party Mako template, which poses a critical security risk by allowing arbitrary Python code execution. Remove custom Mako templates.
Detected use of a third-party Mako template, which poses a critical security risk by allowing arbitrary Python code execution. Remove custom Mako templates.
Detected use of a third-party Mako template, which poses a critical security risk by allowing arbitrary Python code execution. Remove custom Mako templates.
Detected use of a third-party Mako template, which poses a critical security risk by allowing arbitrary Python code execution. Remove custom Mako templates.
Detected use of a third-party Mako template, which poses a critical security risk by allowing arbitrary Python code execution. Remove custom Mako templates.
Detected use of a third-party Mako template, which poses a critical security risk by allowing arbitrary Python code execution. Remove custom Mako templates.
279Insecure HTTP Connection found Match: requests.get Positional arguments, ["search_results"]; Keyword arguments, {}
259Insecure HTTP Connection found Match: requests.get Positional arguments, ["error_messages", "?"]; Keyword arguments, {}
718Insecure HTTP Connection found Match: requests.post Positional arguments, ["/services/trackme/v2/maintenance_kdb/admin/maintenance_kdb_add_record"]; Keyword arguments, {"data": "?", "headers": "?", "verify": "?", "timeout": "?"}
1640Insecure HTTP Connection found Match: requests.get Positional arguments, ["trackme_metric_idx"]; Keyword arguments, {}
817Insecure HTTP Connection found Match: requests.get Positional arguments, ["app"]; Keyword arguments, {}
3532Insecure HTTP Connection found Match: requests.get Positional arguments, ["acl", "?"]; Keyword arguments, {}
1191Insecure HTTP Connection found Match: requests.Session.get Positional arguments, ["data_sampling_obfuscation"]; Keyword arguments, {}
975Insecure HTTP Connection found Match: requests.Session.get Positional arguments, ["sampling"]; Keyword arguments, {}
1309Insecure HTTP Connection found Match: requests.get Positional arguments, ["is_elastic", "?"]; Keyword arguments, {}
819Insecure HTTP Connection found Match: requests.get Positional arguments, ["orphan"]; Keyword arguments, {}
907Insecure HTTP Connection found Match: requests.get Positional arguments, ["workload_pool"]; Keyword arguments, {}
2325Insecure HTTP Connection found Match: requests.get Positional arguments, ["status", "Unknown status"]; Keyword arguments, {}
185Insecure HTTP Connection found Match: requests.get Positional arguments, ["splk_outliers_static_lower_threshold", "?"]; Keyword arguments, {}
1284Insecure HTTP Connection found Match: requests.get Positional arguments, ["definition"]; Keyword arguments, {}
6084Insecure HTTP Connection found Match: requests.get Positional arguments, ["archive_base64"]; Keyword arguments, {}
238Insecure HTTP Connection found Match: requests.get Positional arguments, ["action", "failure"]; Keyword arguments, {}
102Insecure HTTP Connection found Match: requests.get Positional arguments, ["ack_state", "inactive"]; Keyword arguments, {}
851Insecure HTTP Connection found Match: requests.Session.get Positional arguments, ["adaptive_delay", "?"]; Keyword arguments, {}
1083Insecure HTTP Connection found Match: requests.get Positional arguments, ["account"]; Keyword arguments, {}
2710Insecure HTTP Connection found Match: requests.get Positional arguments, ["ack_mtime", "?"]; Keyword arguments, {}
188Insecure HTTP Connection found Match: requests.get Positional arguments, ["splk_outliers_static_upper_threshold", "?"]; Keyword arguments, {}
1310Insecure HTTP Connection found Match: requests.get Positional arguments, ["collection"]; Keyword arguments, {}
269Insecure HTTP Connection found Match: requests.get Positional arguments, ["trackme_metric_idx"]; Keyword arguments, {}
1163Insecure HTTP Connection found Match: requests.get Positional arguments, ["vtenant_account"]; Keyword arguments, {}
1263Insecure HTTP Connection found Match: requests.get Positional arguments, ["type"]; Keyword arguments, {}
1133Insecure HTTP Connection found Match: requests.get Positional arguments, ["?", ""]; Keyword arguments, {}
901Insecure HTTP Connection found Match: requests.get Positional arguments, ["description"]; Keyword arguments, {}
6017Insecure HTTP Connection found Match: requests.get Positional arguments, ["download_token"]; Keyword arguments, {}
182Insecure HTTP Connection found Match: requests.get Positional arguments, ["splk_outliers_apply_extra_parameters", "?"]; Keyword arguments, {}
344Insecure HTTP Connection found Match: requests.get Positional arguments, ["trackme_general", "?"]; Keyword arguments, {}
975Insecure HTTP Connection found Match: requests.get Positional arguments, ["sampling"]; Keyword arguments, {}
1269Insecure HTTP Connection found Match: requests.get Positional arguments, ["properties", "?"]; Keyword arguments, {}
1311Insecure HTTP Connection found Match: requests.get Positional arguments, ["fields_list"]; Keyword arguments, {}
344Insecure HTTP Connection found Match: requests.get Positional arguments, ["icons_state_mode", "emoji"]; Keyword arguments, {}
Suppressed 81 warning messages
1071Insecure HTTP Connection found Match: requests.get Positional arguments, ["splk_dsm_sampling_search", "?"]; Keyword arguments, {}
308Insecure HTTP Connection found Match: requests.get Positional arguments, ["model_exists"]; Keyword arguments, {}
3187Insecure HTTP Connection found Match: requests.get Positional arguments, ["archive_base64"]; Keyword arguments, {}
1302Insecure HTTP Connection found Match: requests.get Positional arguments, ["splk_dsm_sampling_search", "?"]; Keyword arguments, {}
159Insecure HTTP Connection found Match: requests.Session.get Positional arguments, ["splk__cmdb_search"]; Keyword arguments, {}
438Insecure HTTP Connection found Match: requests.get Positional arguments, ["response"]; Keyword arguments, {}
842Insecure HTTP Connection found Match: requests.get Positional arguments, ["trackme_audit_idx", "trackme_audit"]; Keyword arguments, {}
1191Insecure HTTP Connection found Match: requests.get Positional arguments, ["data_sampling_obfuscation"]; Keyword arguments, {}
368Insecure HTTP Connection found Match: requests.get Positional arguments, ["response"]; Keyword arguments, {}
103Insecure HTTP Connection found Match: requests.get Positional arguments, ["ack_mtime", "?"]; Keyword arguments, {}
244Insecure HTTP Connection found Match: requests.get Positional arguments, ["response"]; Keyword arguments, {}
1960Insecure HTTP Connection found Match: requests.Session.get Positional arguments, ["splk_feeds_auto_disablement_period"]; Keyword arguments, {}
1444Insecure HTTP Connection found Match: requests.Session.post Positional arguments, ["/services/trackme/v2/backup_and_restore/backup"]; Keyword arguments, {"data": "?", "verify": "?", "timeout": "?"}
275Insecure HTTP Connection found Match: requests.get Positional arguments, ["description", ""]; Keyword arguments, {}
900Insecure HTTP Connection found Match: requests.get Positional arguments, ["cron_schedule"]; Keyword arguments, {}
1303Insecure HTTP Connection found Match: requests.get Positional arguments, ["definition"]; Keyword arguments, {}
902Insecure HTTP Connection found Match: requests.get Positional arguments, ["disabled"]; Keyword arguments, {}
2709Insecure HTTP Connection found Match: requests.get Positional arguments, ["ack_state", "inactive"]; Keyword arguments, {}
818Insecure HTTP Connection found Match: requests.get Positional arguments, ["sharing"]; Keyword arguments, {}
276Insecure HTTP Connection found Match: requests.get Positional arguments, ["alias", "?"]; Keyword arguments, {}
951Insecure HTTP Connection found Match: requests.get Positional arguments, ["?", ""]; Keyword arguments, {}
2320Insecure HTTP Connection found Match: requests.get Positional arguments, ["trackme_metric_idx"]; Keyword arguments, {}
159Insecure HTTP Connection found Match: requests.get Positional arguments, ["splk__cmdb_search"]; Keyword arguments, {}
903Insecure HTTP Connection found Match: requests.get Positional arguments, ["is_scheduled"]; Keyword arguments, {}
2474Insecure HTTP Connection found Match: requests.get Positional arguments, [""]; Keyword arguments, {"headers": "?", "verify": "?", "timeout": "?", "params": "?"}
213Insecure HTTP Connection found Match: requests.post Positional arguments, ["/services/trackme/v2/splk_logical_groups/write/logical_groups_del_grp"]; Keyword arguments, {"headers": "?", "data": "?", "verify": "?", "timeout": "?"}
2633Insecure HTTP Connection found Match: requests.get Positional arguments, ["allowed_email_domains", "?"]; Keyword arguments, {}
1266Insecure HTTP Connection found Match: requests.get Positional arguments, ["title"]; Keyword arguments, {}
2061Insecure HTTP Connection found Match: requests.get Positional arguments, ["success_count"]; Keyword arguments, {}
842Insecure HTTP Connection found Match: requests.Session.get Positional arguments, ["trackme_audit_idx", "trackme_audit"]; Keyword arguments, {}
2061Insecure HTTP Connection found Match: requests.Session.get Positional arguments, ["success_count"]; Keyword arguments, {}
911Insecure HTTP Connection found Match: requests.get Positional arguments, ["dispatch.latest_time"]; Keyword arguments, {}
140Insecure HTTP Connection found Match: requests.post Positional arguments, ["/services/trackme/v2/splk_logical_groups/write/logical_groups_update_group_list"]; Keyword arguments, {"headers": "?", "data": "?", "verify": "?", "timeout": "?"}
908Insecure HTTP Connection found Match: requests.get Positional arguments, ["dispatch.earliest_time"]; Keyword arguments, {}
179Insecure HTTP Connection found Match: requests.get Positional arguments, ["splk_outliers_fit_extra_parameters", "?"]; Keyword arguments, {}
2690Insecure HTTP Connection found Match: requests.post Positional arguments, ["/services/trackme/v2/ack/get_ack_for_object"]; Keyword arguments, {"headers": "?", "data": "?", "verify": "?", "timeout": "?"}
907Insecure HTTP Connection found Match: requests.post Positional arguments, ["/services/trackme/v2/maintenance_kdb/admin/maintenance_kdb_manage_record"]; Keyword arguments, {"data": "?", "headers": "?", "verify": "?", "timeout": "?"}
1444Insecure HTTP Connection found Match: requests.post Positional arguments, ["/services/trackme/v2/backup_and_restore/backup"]; Keyword arguments, {"data": "?", "verify": "?", "timeout": "?"}
3509Insecure HTTP Connection found Match: requests.get Positional arguments, ["email_format", "html"]; Keyword arguments, {}
179Insecure HTTP Connection found Match: requests.post Positional arguments, ["/services/trackme/v2/splk_logical_groups/write/logical_groups_remove_object_from_groups"]; Keyword arguments, {"headers": "?", "data": "?", "verify": "?", "timeout": "?"}
1291Insecure HTTP Connection found Match: requests.get Positional arguments, ["definition"]; Keyword arguments, {}
6018Insecure HTTP Connection found Match: requests.get Positional arguments, ["filename", "?"]; Keyword arguments, {}
729Insecure HTTP Connection found Match: requests.get Positional arguments, ["record_id"]; Keyword arguments, {}
172Insecure HTTP Connection found Match: requests.get Positional arguments, ["splk_outliers_mltk_algorithms_default", "DensityFunction"]; Keyword arguments, {}
269Insecure HTTP Connection found Match: requests.Session.get Positional arguments, ["trackme_metric_idx"]; Keyword arguments, {}
944Insecure HTTP Connection found Match: requests.get Positional arguments, ["?", ""]; Keyword arguments, {}
195Insecure HTTP Connection found Match: requests.get Positional arguments, ["response"]; Keyword arguments, {}
175Insecure HTTP Connection found Match: requests.get Positional arguments, ["splk_outliers_boundaries_extraction_macro_default", "splk_outliers_extract_boundaries"]; Keyword arguments, {}
2320Insecure HTTP Connection found Match: requests.Session.get Positional arguments, ["trackme_metric_idx"]; Keyword arguments, {}
2328Insecure HTTP Connection found Match: requests.get Positional arguments, ["files_purged", "?"]; Keyword arguments, {}
221Insecure HTTP Connection found Match: requests.post Positional arguments, ["/services/trackme/v2/maintenance_kdb/admin/maintenance_kdb_manage_record"]; Keyword arguments, {"data": "?", "headers": "?", "verify": "?", "timeout": "?"}
342Insecure HTTP Connection found Match: requests.get Positional arguments, ["success_count"]; Keyword arguments, {}
292Insecure HTTP Connection found Match: requests.get Positional arguments, ["response"]; Keyword arguments, {}
1310Insecure HTTP Connection found Match: requests.get Positional arguments, ["search_mode", "unknown"]; Keyword arguments, {}
1071Insecure HTTP Connection found Match: requests.get Positional arguments, ["trackme_version", "unknown"]; Keyword arguments, {}
1294Insecure HTTP Connection found Match: requests.get Positional arguments, ["alert_properties"]; Keyword arguments, {}
1960Insecure HTTP Connection found Match: requests.get Positional arguments, ["splk_feeds_auto_disablement_period"]; Keyword arguments, {}
203Insecure HTTP Connection found Match: requests.get Positional arguments, ["alias", "?"]; Keyword arguments, {}
1116Insecure HTTP Connection found Match: requests.get Positional arguments, ["?", ""]; Keyword arguments, {}
904Insecure HTTP Connection found Match: requests.get Positional arguments, ["schedule_window"]; Keyword arguments, {}
816Insecure HTTP Connection found Match: requests.get Positional arguments, ["owner"]; Keyword arguments, {}
83Insecure HTTP Connection found Match: requests.post Positional arguments, ["/services/trackme/v2/ack/get_ack_for_object"]; Keyword arguments, {"headers": "?", "data": "?", "verify": "?", "timeout": "?"}
851Insecure HTTP Connection found Match: requests.get Positional arguments, ["adaptive_delay", "?"]; Keyword arguments, {}
6061Insecure HTTP Connection found Match: requests.get Positional arguments, ["archive_base64"]; Keyword arguments, {}
1395Insecure HTTP Connection found Match: requests.get Positional arguments, ["_raw"]; Keyword arguments, {}
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.
5631Ensure 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.
224Ensure 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.
1692Ensure 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.
1940Ensure 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.
2182Ensure 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.
2418Ensure 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.
340Ensure 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.
2393Ensure 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.
339Ensure 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.
155Ensure 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.
162Ensure 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.
58Ensure 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.
1378Ensure 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.
228Ensure 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.
140Ensure 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.
3174Ensure 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.
180Ensure 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.
3859Ensure 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.
943Ensure 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.
1811Ensure 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.
208Ensure 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.
2220Ensure 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 218 warning messages
2181Ensure 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.
1998Ensure 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.
2474Ensure 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.
847Ensure 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.
604Ensure 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.
946Ensure 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.
3108Ensure 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.
153Ensure 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.
2270Ensure 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.
1237Ensure 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.
107Ensure 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.
286Ensure 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.
179Ensure 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.
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.
646Ensure 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.
1388Ensure 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.
322Ensure 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.
2325Ensure 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.
497Ensure 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.
2435Ensure 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.
161Ensure 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.
83Ensure 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.
2293Ensure 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.
6026Ensure 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.
1628Ensure 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.
1769Ensure 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.
296Ensure 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.
213Ensure 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.
907Ensure 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.
1877Ensure 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.
2383Ensure 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.
159Ensure 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.
321Ensure 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.
2098Ensure 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.
179Ensure 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.
2450Ensure 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.
221Ensure 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.
353Ensure 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.
173Ensure 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.
516Ensure 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.
602Ensure 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.
3231Ensure 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.
773Ensure 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.
1298Ensure 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.
2552Ensure 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.
265Ensure 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.
2617Ensure 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.
221Ensure 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.
206Ensure 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.
225Ensure 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.
1153Ensure 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.
188Ensure 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.
1713Ensure 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.
260Ensure 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.
228Ensure 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.
2502Ensure 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.
2351Ensure 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.
173Ensure 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.
1435Ensure 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.
6000Ensure 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.
94Ensure 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.
718Ensure 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.
259Ensure 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.
480Ensure 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.
273Ensure 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.
2690Ensure 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.
390Ensure 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.
179Ensure 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.
1647Ensure 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.
1048Ensure 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.
721Ensure 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.
3453Ensure 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.
132Ensure 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.
17Detected splunktaucclib (version 8.0.0). No action required.
59Detected solnlib (version 7.0.0). No action required.