TA-trackme-cribl

Cribl API integration for TrackMe

Author TrackMe Limited, U.K.
Tags cloud
Version 1.0.1
Hash 9e2c134cbb8d6dca04261729d47f35fd
AppInspect Request ID 5d4752f2-2a95-4fa3-93c9-5c07b9350c94
Run Time 2023-12-31T09:36:55.386473
Execution Time 138
Run Parameters:
Field Value
AppInspect Version 3.0.3
Analyzers:
Name Version Is Latest
static-checks 3.0.3 True
dynamic-checks 1.27.2 True
retire-js 1.0.2 True
Totals:
Status Count
Failures 0
Warnings 10
Errors 0
Not Applicable 89
Manual Checks 11
Skipped 0
Successes 122

[ Warning Summary ]

Warnings are non-blocking concerns. But they are strongly recommended to be fixed.
check_custom_confs
  • Custom config file lib/splunktalib/setting.conf is detected in this app. By default, it will be partitioned to all instances including Search Head(s), Indexer(s) and Forwarder(s). If that's not what you expect, you can use the `targetWorkloads` attribute in app.manifest to indicate the correct instances. For more details about app.manifest, please refer to https://dev.splunk.com/enterprise/docs/releaseapps/packagingtoolkit/pkgtoolkitref/pkgtoolkitapp#JSON-schema-200. Please also make sure that this custom file is safe to install. File: lib/splunktalib/setting.conf
  • Custom config file default/ta_trackme_cribl_settings.conf is detected in this app. By default, it will be partitioned to all instances including Search Head(s), Indexer(s) and Forwarder(s). If that's not what you expect, you can use the `targetWorkloads` attribute in app.manifest to indicate the correct instances. For more details about app.manifest, please refer to https://dev.splunk.com/enterprise/docs/releaseapps/packagingtoolkit/pkgtoolkitref/pkgtoolkitapp#JSON-schema-200. Please also make sure that this custom file is safe to install. File: default/ta_trackme_cribl_settings.conf
check_for_possible_threading
  • The following line contains subprocess.Popen.communicate usage. Use threading and multiprocessing with discretion. File: lib/solnlib/splunkenv.py Line Number: 280
  • The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion. File: lib/solnlib/splunkenv.py Line Number: 277
check_for_python_script_existence
  • 235 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.
check_for_existence_of_python_code_block_in_mako_template
  • Update Mako templates to be Python 3-compatible. Splunk Web, which Mako templates depend on, will support only Python 3.7. If you've finished your update, please disregard this message. File: appserver/templates/base.html
check_for_splunk_js_header_and_footer_view
  • As of Splunk 6.5, this functionality is deprecated and should be removed in futureapp versions. Match: splunkjs/mvc/headerview File: appserver/static/js/build/entry_page.js Line Number: 2
check_for_splunk_sui
  • Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/react-toast-notifications File: appserver/static/js/build/922.8a8a6f6a2ee3e15c3f16.js.map Line Number: 1
  • Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/themes File: appserver/static/js/build/307.88617895514dfe615b67.js.map Line Number: 1
  • Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/themes File: appserver/static/js/build/188.256235eb68ae7193e7ea.js.map Line Number: 1
  • Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/themes File: appserver/static/js/build/987.6ec28389c3adf57d57c6.js.map Line Number: 1
  • Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/react-ui File: appserver/static/js/build/354.fd7d08274e1955fdbd9d.js.map Line Number: 1
  • Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/react-page File: appserver/static/js/build/entry_page.js.map Line Number: 1
check_for_splunk_js
  • Splunk 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 File: appserver/static/js/build/entry_page.js Line Number: 2
  • Splunk 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 File: appserver/static/js/build/entry_page.js.map Line Number: 1
check_for_splunk_frontend_utility_components
  • Splunk 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/ui-utils File: appserver/static/js/build/987.6ec28389c3adf57d57c6.js.map Line Number: 1
  • Splunk 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/ui-utils File: appserver/static/js/build/922.8a8a6f6a2ee3e15c3f16.js.map Line Number: 1
  • Splunk 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/ui-utils File: appserver/static/js/build/188.256235eb68ae7193e7ea.js.map Line Number: 1
  • Splunk 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/ui-utils File: appserver/static/js/build/entry_page.js.map Line Number: 1
  • Splunk 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/ui-utils File: appserver/static/js/build/307.88617895514dfe615b67.js.map Line Number: 1
check_hostnames_and_ips
  • PUBLIC IP 5.5.5.5 is found in lib/PySocks-1.7.1.dist-info/METADATA:70 File: lib/PySocks-1.7.1.dist-info/METADATA Line Number: 70
check_for_bias_language
  • Bias language is found in the app. was not in the method <<<WHITELIST>>>. (Issue #1059) (lib/urllib3-1.26.18.dist-info/METADATA:685) [whitelist]. File: METADATA Line Number: 685
  • Bias language is found in the app. for key in ("apps", "slave-apps", "<<<MASTER>>>-apps"): (lib/splunktaucclib/rest_handler/util.py:85) [master]. File: util.py Line Number: 85
  • Bias language is found in the app. This project is [MIT](https://github.com/Ousret/charset_normalize... (lib/charset_normalizer-3.3.2.dist-info/METADATA:278) [master]. File: METADATA Line Number: 278
  • Bias language is found in the app. :target: https://codecov.io/github/tiran/defusedxml?branch=<<<MAS... (lib/defusedxml-0.7.1.dist-info/METADATA:47) [master]. File: METADATA Line Number: 47
  • Bias language is found in the app. <<<BLACKLIST>>> = _etree._Entity (lib/defusedxml/lxml.py:38) [blacklist]. File: lxml.py Line Number: 38
  • Bias language is found in the app. .. image:: https://codecov.io/github/tiran/defusedxml/coverage.sv... (lib/defusedxml-0.7.1.dist-info/METADATA:46) [master]. File: METADATA Line Number: 46
  • Bias language is found in the app. and release. The <<<MASTER>>> branch received the same fix in Pul... (lib/urllib3-1.26.18.dist-info/METADATA:735) [master]. File: METADATA Line Number: 735
  • Bias language is found in the app. <<<BLACKLIST>>> = self.<<<BLACKLIST>>> (lib/defusedxml/lxml.py:41) [blacklist]. File: lxml.py Line Number: 41
  • Bias language is found in the app. .. _`Requests`: https://requests.readthedocs.io/en/<<<MASTER>>>/ (lib/certifi-2023.11.17.dist-info/METADATA:58) [master]. File: METADATA Line Number: 58
  • Bias language is found in the app. if isinstance(child, <<<BLACKLIST>>>): (lib/defusedxml/lxml.py:43) [blacklist]. File: lxml.py Line Number: 43
  • Bias language is found in the app. {"version":3,"file":"188.256235eb68ae7193e7ea.js","mappings":"0GA... (appserver/static/js/build/188.256235eb68ae7193e7ea.js.map:1) [master]. File: 188.256235eb68ae7193e7ea.js.map Line Number: 1
  • Bias language is found in the app. .. image:: https://ci.appveyor.com/api/projects/status/github/gra... (lib/sortedcontainers-2.4.0.dist-info/METADATA:146) [master]. File: METADATA Line Number: 146
  • Bias language is found in the app. Project-URL: Changelog, https://github.com/kjd/idna/blob/<<<MASTE... (lib/idna-3.6.dist-info/METADATA:29) [master]. File: METADATA Line Number: 29
  • Bias language is found in the app. groups_url = f"/api/v1/<<<MASTER>>>/groups?product=stream" (bin/cribl.py:125) [master]. File: cribl.py Line Number: 125
  • Bias language is found in the app. .. image:: https://travis-ci.org/tiran/defusedxml.svg?branch=<<<M... (lib/defusedxml-0.7.1.dist-info/METADATA:42) [master]. File: METADATA Line Number: 42
  • Bias language is found in the app. # <<<BLACKLIST>>> = (etree._Entity, etree._ProcessingInstruction,... (lib/defusedxml/lxml.py:37) [blacklist]. File: lxml.py Line Number: 37
  • Bias language is found in the app. for key in ("apps", "slave-apps", "<<<MASTER>>>-apps"): (lib/splunktalib/common/util.py:103) [master]. File: util.py Line Number: 103
  • Bias language is found in the app. .. image:: https://api.travis-ci.org/grantjenks/python-sortedcont... (lib/sortedcontainers-2.4.0.dist-info/METADATA:143) [master]. File: METADATA Line Number: 143
  • Bias language is found in the app. {"version":3,"file":"entry_page.js","mappings":";UAAIA,ECCAC,EADA... (appserver/static/js/build/entry_page.js.map:1) [master]. File: entry_page.js.map Line Number: 1

[ Full Report ]

Malware, viruses, malicious content, user security standards (dynamic checks)
[ success ] Check that the app does not include viruses.
Splunk Packaging Toolkit (SLIM) validation This group uses slim to extend the cloud checks for improved auto-vetting.
[ success ] Check that the provided app package is not .zip type for SSAI purpose
[ success ] Check that apps can be validated by SLIM or reject, since invalid apps can't be installed in Classic Splunk Cloud.
[ not_applicable ] Check that inputs.conf does not include scripted inputs that perform management tasks.
  • File: app.manifest was found, skipping this check.
[ success ] Check that nested archives do not exist as they are not valid for self-service install.
[ success ] Check that nested apps do not exist as they are not valid for self-service install.
[ not_applicable ] Check that inputs.conf.spec does not include modular inputs that perform management tasks.
  • File: app.manifest was found, skipping this check.
[ warning ] Find non-standard config files and notify app developers to confirm that 1. those files are safe to install. 2. those files are partitioned to the expected instances.
  • Custom config file lib/splunktalib/setting.conf is detected in this app. By default, it will be partitioned to all instances including Search Head(s), Indexer(s) and Forwarder(s). If that's not what you expect, you can use the `targetWorkloads` attribute in app.manifest to indicate the correct instances. For more details about app.manifest, please refer to https://dev.splunk.com/enterprise/docs/releaseapps/packagingtoolkit/pkgtoolkitref/pkgtoolkitapp#JSON-schema-200. Please also make sure that this custom file is safe to install. File: lib/splunktalib/setting.conf
  • Custom config file default/ta_trackme_cribl_settings.conf is detected in this app. By default, it will be partitioned to all instances including Search Head(s), Indexer(s) and Forwarder(s). If that's not what you expect, you can use the `targetWorkloads` attribute in app.manifest to indicate the correct instances. For more details about app.manifest, please refer to https://dev.splunk.com/enterprise/docs/releaseapps/packagingtoolkit/pkgtoolkitref/pkgtoolkitapp#JSON-schema-200. Please also make sure that this custom file is safe to install. File: default/ta_trackme_cribl_settings.conf
Checks related to JavaScript usage.
[ success ] Detect usage of JavaScript libraries with known vulnerabilities.
XML file standards
[ success ] Check that all XML files are well-formed.
[ success ] Check any XML files that embed JavaScript via CDATA for compliance with Splunk Cloud security policy.
Python file standards
[ success ] Check that there are no .pyc or .pyo files included in the app.
[ manual_check ] Check for builtin functions(open, eval, execfile, file) usages in python files
  • The following line will be inspected during code review. The `__builtin__.open` module/method can be used to manipulate files outside of the app dir. File: lib/splunktaucclib/cim_actions.py Line Number: 539
  • The following line will be inspected during code review. The `__builtin__.open` module/method can be used to manipulate files outside of the app dir. File: lib/splunktaucclib/cim_actions.py Line Number: 187
  • The following line will be inspected during code review. The `__builtin__.open` module/method can be used to manipulate files outside of the app dir. File: lib/splunktaucclib/modinput_wrapper/base_modinput.py Line Number: 185
  • The following line will be inspected during code review. The `__builtin__.open` module/method can be used to manipulate files outside of the app dir. File: lib/charset_normalizer/api.py Line Number: 548
  • The following line will be inspected during code review. The `__builtin__.open` module/method can be used to manipulate files outside of the app dir. File: lib/urllib3/contrib/securetransport.py Line Number: 436
  • The following line will be inspected during code review. The `__builtin__.open` module/method can be used to manipulate files outside of the app dir. File: lib/splunktaucclib/splunk_aoblib/setup_util.py Line Number: 128
  • The following line will be inspected during code review. The `__builtin__.open` module/method can be used to manipulate files outside of the app dir. File: lib/urllib3/contrib/securetransport.py Line Number: 867
  • The following line will be inspected during code review. The `__builtin__.open` module/method can be used to manipulate files outside of the app dir. File: lib/charset_normalizer/cli/__main__.py Line Number: 261
  • The following line will be inspected during code review. The `__builtin__.open` module/method can be used to manipulate files outside of the app dir. File: lib/splunktaucclib/common/__init__.py Line Number: 26
[ success ] Check that the python __import__ method is not used in a way that can be exploited (e.g., import(conf_setting) is at risk of code injection).
[ success ] Check all python files are well formed under python2 and python3 standard
[ not_applicable ] Check that Splunk SDK for Python is up-to-date.
  • Splunk SDK for Python not found.
[ success ] Check for untrusted xml usages in python libraries
[ not_applicable ] Check python httplib2 version.
  • Python httplib2 library not found.
[ success ] Check that all network communications are encrypted
[ success ] Check possible root privilege escalation
[ success ] check if possible reverse shell exist in python code
[ success ] Check if restricted execution exist in current app
[ success ] Check for UDP network communication
[ success ] Check if python runtime services could be used to manipulate system python objects
[ success ] Check if multimedia services module could be used to execute unknown-source multimedia files
[ success ] Check if program frameworks could be used to interface with web part
[ warning ] Check for the use of threading, and multiprocesses. Threading or process must be used with discretion and not negatively affect the Splunk installation as a whole.
  • The following line contains subprocess.Popen.communicate usage. Use threading and multiprocessing with discretion. File: lib/solnlib/splunkenv.py Line Number: 280
  • The following line contains subprocess.Popen usage. Use threading and multiprocessing with discretion. File: lib/solnlib/splunkenv.py Line Number: 277
[ manual_check ] check for plain text credentials disclosure in python files
  • The following lines should be inspected during code review, Possible plain text credentials disclosure here, `self._code = 500` File: lib/splunktaucclib/rest_handler/error_ctl.py Line Number: 82
  • The following lines should be inspected during code review, Possible plain text credentials disclosure here, `CredMgmt.PASSWORD_MASK = ********` File: lib/splunktaucclib/rest_handler/base.py Line Number: 452
  • The following lines should be inspected during code review, Possible plain text credentials disclosure here, `GLOBAL_SETTING_KEY = global_settings` File: lib/splunktaucclib/splunk_aoblib/setup_util.py Line Number: 69
  • The following lines should be inspected during code review, Possible plain text credentials disclosure here, `PROXY_ENABLE_KEY = proxy_enabled` File: lib/splunktaucclib/splunk_aoblib/setup_util.py Line Number: 227
  • The following lines should be inspected during code review, Possible plain text credentials disclosure here, `session_key = session_key` File: lib/splunktaucclib/data_collection/ta_consts.py Line Number: 17
  • The following lines should be inspected during code review, Possible plain text credentials disclosure here, `PROXY_ENABLE_KEY = proxy_enabled` File: lib/splunktaucclib/splunk_aoblib/setup_util.py Line Number: 170
  • The following lines should be inspected during code review, Possible plain text credentials disclosure here, `PROXY_RDNS_KEY = proxy_rdns` File: lib/splunktaucclib/splunk_aoblib/setup_util.py Line Number: 229
  • The following lines should be inspected during code review, Possible plain text credentials disclosure here, `self._code = 500` File: lib/splunktaucclib/rest_handler/error_ctl.py Line Number: 101
  • The following lines should be inspected during code review, Possible plain text credentials disclosure here, `PROXY_RDNS_KEY = proxy_rdns` File: lib/splunktaucclib/splunk_aoblib/setup_util.py Line Number: 86
  • The following lines should be inspected during code review, Possible plain text credentials disclosure here, `self._code = 500` File: lib/splunktaucclib/rest_handler/error_ctl.py Line Number: 100
  • The following lines should be inspected during code review, Possible plain text credentials disclosure here, `LOG_LEVEL_KEY = loglevel` File: lib/splunktaucclib/splunk_aoblib/setup_util.py Line Number: 221
  • The following lines should be inspected during code review, Possible plain text credentials disclosure here, `__author__ = TrackMe Limited` File: bin/cribl.py Line Number: 6
  • The following lines should be inspected during code review, Possible plain text credentials disclosure here, `PROXY_RDNS_KEY = proxy_rdns` File: lib/splunktaucclib/splunk_aoblib/setup_util.py Line Number: 168
  • The following lines should be inspected during code review, Possible plain text credentials disclosure here, `CredMgmt.PASSWORD_MASK = ********` File: lib/splunktaucclib/rest_handler/cred_mgmt.py Line Number: 83
  • The following lines should be inspected during code review, Possible plain text credentials disclosure here, `__author__ = TrackMe Limited` File: lib/cribl_libs.py Line Number: 6
  • The following lines should be inspected during code review, Possible plain text credentials disclosure here, `PROXY_ENABLE_KEY = proxy_enabled` File: lib/splunktaucclib/splunk_aoblib/setup_util.py Line Number: 85
  • The following lines should be inspected during code review, Possible plain text credentials disclosure here, `code = 500` File: lib/splunktaucclib/rest_handler/error_ctl.py Line Number: 71
  • The following lines should be inspected during code review, Possible plain text credentials disclosure here, `SecurityConst.kSSLSessionOptionBreakOnServerAuth = 0` File: lib/urllib3/contrib/securetransport.py Line Number: 540
  • The following lines should be inspected during code review, Possible plain text credentials disclosure here, `PASSWORD = ******` File: lib/splunktaucclib/rest_handler/credentials.py Line Number: 95
  • The following lines should be inspected during code review, Possible plain text credentials disclosure here, `LOG_LEVEL_KEY = loglevel` File: lib/splunktaucclib/splunk_aoblib/setup_util.py Line Number: 87
  • The following lines should be inspected during code review, Possible plain text credentials disclosure here, `code = 500` File: lib/splunktaucclib/rest_handler/error_ctl.py Line Number: 73
  • The following lines should be inspected during code review, Possible plain text credentials disclosure here, `LOG_LEVEL_KEY = loglevel` File: lib/splunktaucclib/splunk_aoblib/setup_util.py Line Number: 247
  • The following lines should be inspected during code review, Possible plain text credentials disclosure here, `divide_key = _divide_key` File: lib/splunktaucclib/data_collection/ta_consts.py Line Number: 49
  • The following lines should be inspected during code review, Possible plain text credentials disclosure here, `PROXY_ENABLE_KEY = proxy_enabled` File: lib/splunktaucclib/splunk_aoblib/setup_util.py Line Number: 167
  • The following lines should be inspected during code review, Possible plain text credentials disclosure here, `GLOBAL_SETTING_KEY = global_settings` File: lib/splunktaucclib/splunk_aoblib/setup_util.py Line Number: 151
  • The following lines should be inspected during code review, Possible plain text credentials disclosure here, `LOG_LEVEL_KEY_ENV = log_level` File: lib/splunktaucclib/splunk_aoblib/setup_util.py Line Number: 88
  • The following lines should be inspected during code review, Possible plain text credentials disclosure here, `c.divide_key = _divide_key` File: lib/splunktaucclib/data_collection/ta_config.py Line Number: 203
  • The following lines should be inspected during code review, Possible plain text credentials disclosure here, `self._code = 500` File: lib/splunktaucclib/rest_handler/error_ctl.py Line Number: 85
  • The following lines should be inspected during code review, Possible plain text credentials disclosure here, `qualified_key_str = ` File: lib/splunktaucclib/data_collection/ta_checkpoint_manager.py Line Number: 70
  • The following lines should be inspected during code review, Possible plain text credentials disclosure here, `PROXY_ENABLE_KEY = proxy_enabled` File: lib/splunktaucclib/splunk_aoblib/setup_util.py Line Number: 226
  • The following lines should be inspected during code review, Possible plain text credentials disclosure here, `LOG_LEVEL_KEY_ENV = log_level` File: lib/splunktaucclib/splunk_aoblib/setup_util.py Line Number: 176
  • The following lines should be inspected during code review, Possible plain text credentials disclosure here, `PROXY_RDNS_KEY = proxy_rdns` File: lib/splunktaucclib/splunk_aoblib/setup_util.py Line Number: 230
  • The following lines should be inspected during code review, Possible plain text credentials disclosure here, `PROXY_ENABLE_KEY = proxy_enabled` File: lib/splunktaucclib/splunk_aoblib/setup_util.py Line Number: 258
  • The following lines should be inspected during code review, Possible plain text credentials disclosure here, `c.session_key = session_key` File: lib/splunktaucclib/data_collection/ta_config.py Line Number: 49
  • The following lines should be inspected during code review, Possible plain text credentials disclosure here, `__author__ = TrackMe Limited U.K` File: bin/cribl_rest_handler.py Line Number: 4
  • The following lines should be inspected during code review, Possible plain text credentials disclosure here, `self.PASSWORD = ******` File: lib/splunktaucclib/rest_handler/handler.py Line Number: 157
  • The following lines should be inspected during code review, Possible plain text credentials disclosure here, `c.session_key = session_key` File: lib/splunktaucclib/data_collection/ta_helper.py Line Number: 84
  • The following lines should be inspected during code review, Possible plain text credentials disclosure here, `PROXY_RDNS_KEY = proxy_rdns` File: lib/splunktaucclib/splunk_aoblib/setup_util.py Line Number: 172
  • The following lines should be inspected during code review, Possible plain text credentials disclosure here, `PROXY_ENABLE_KEY = proxy_enabled` File: lib/splunktaucclib/splunk_aoblib/setup_util.py Line Number: 385
  • The following lines should be inspected during code review, Possible plain text credentials disclosure here, `PASSWORD_MASK = ********` File: lib/splunktaucclib/rest_handler/cred_mgmt.py Line Number: 41
[ success ] Check for operating system features that are available on selected operating systems only.
[ success ] check if networking or file manipulation exist in interprocess modules usage
[ success ] Check for the use of web server classes, they could be used to start a internal server in current app
[ manual_check ] Check Python code for importing modules dynamically.
  • The following lines should be inspected during code review, Python code `importlib.import_module` for dynamically importing module has been detected. File: lib/charset_normalizer/utils.py Line Number: 332
  • The following lines should be inspected during code review, Python code `importlib.import_module` for dynamically importing module has been detected. File: lib/charset_normalizer/utils.py Line Number: 327
  • The following lines should be inspected during code review, Python code `importlib.import_module` for dynamically importing module has been detected. File: lib/charset_normalizer/cd.py Line Number: 32
  • The following lines should be inspected during code review, Python code `importlib.import_module` for dynamically importing module has been detected. File: lib/charset_normalizer/utils.py Line Number: 324
  • The following lines should be inspected during code review, Python code `importlib.import_module` for dynamically importing module has been detected. File: lib/charset_normalizer/cd.py Line Number: 36
  • The following lines should be inspected during code review, Python code `importlib.import_module` for dynamically importing module has been detected. File: lib/charset_normalizer/utils.py Line Number: 331
  • The following lines should be inspected during code review, Python code `importlib.import_module` for dynamically importing module has been detected. File: lib/charset_normalizer/utils.py Line Number: 263
[ success ] Check that there are no hidden python files included in the app.
[ manual_check ] check if generic operating system modules could be used to communicate with outside services, files or systems
  • The following lines should be inspected during code review. `logging.StreamHandler` could be used to receive data from outside or log data to outside. File: lib/charset_normalizer/api.py Line Number: 27
  • The following lines should be inspected during code review. `logging.handlers.RotatingFileHandler` could be used to receive data from outside or log data to outside. File: lib/splunktaucclib/cim_actions.py Line Number: 586
  • The following lines should be inspected during code review. `logging.handlers.RotatingFileHandler` could be used to receive data from outside or log data to outside. File: bin/cribl_rest_handler.py Line Number: 25
  • The following lines should be inspected during code review. `argparse.ArgumentParser.parse_args` could be used to receive data from outside or log data to outside. File: lib/charset_normalizer/cli/__main__.py Line Number: 133
  • The following lines should be inspected during code review. `logging.handlers.RotatingFileHandler` could be used to receive data from outside or log data to outside. File: lib/solnlib/log.py Line Number: 127
  • The following lines should be inspected during code review. `logging.StreamHandler` could be used to receive data from outside or log data to outside. File: lib/charset_normalizer/utils.py Line Number: 363
  • The following lines should be inspected during code review. `logging.handlers.RotatingFileHandler` could be used to receive data from outside or log data to outside. File: lib/solnlib/log.py Line Number: 185
  • The following lines should be inspected during code review. `logging.handlers.RotatingFileHandler` could be used to receive data from outside or log data to outside. File: bin/cribl.py Line Number: 37
  • The following lines should be inspected during code review. `logging.StreamHandler` could be used to receive data from outside or log data to outside. File: lib/splunktaucclib/splunk_aoblib/utility.py Line Number: 30
[ manual_check ] Check for possible file and directory access, they could be used in external file manipulation
  • The following line will be inspected during code review. The `shutil.rmtree` module/method can be used to access file/directory outside of the app dir. Function call arguments: ["?"], keywords: {} File: lib/urllib3/contrib/securetransport.py Line Number: 671
  • The following line will be inspected during code review. The `tempfile.mkdtemp` module/method can be used to access file/directory outside of the app dir. Function call arguments: [], keywords: {} File: lib/splunktaucclib/modinput_wrapper/base_modinput.py Line Number: 538
  • The following line will be inspected during code review. The `os.makedirs` module/method can be used to access file/directory outside of the app dir. Function call arguments: ["?"], keywords: {} File: lib/splunktaucclib/modinput_wrapper/base_modinput.py Line Number: 540
[ success ] Check if debugging library could be used to execute arbitrary commands
[ success ] check for data persistence usage which could be used to invoke marshall function call
[ manual_check ] check if data compression and archiving libraries could be used to read & write files outside of app dir
  • The following lines should be inspected during code review, `gzip.open` could be used to create an archiving object, it can read or write file outside of app dir. File: lib/splunktaucclib/alert_actions_base.py Line Number: 174
  • The following lines should be inspected during code review, `gzip.open` could be used to create an archiving object, it can read or write file outside of app dir. File: lib/splunktaucclib/alert_actions_base.py Line Number: 163
[ success ] Check if custom python interpreters could be used in malicious code execution
Data model files and configurations Data models are defined in a datamodels.conf file in the /default directory of the app. For more, see About data models and datamodels.conf.
[ not_applicable ] Check that the use of accelerated data models do not occur. If data model acceleration is required, developers should provide directions in documentation for how to accelerate data models from within the Splunk Web GUI. data model acceleration
  • datamodels.conf does not exist
REST endpoints and handler standards REST endpoints are defined in a restmap.conf file in the /default and /local directory of the app. For more, see restmap.conf.
[ success ] Check that each stanza in restmap.conf has a matching handler script.if not, throw a warning.
[ success ] Check that python version is python3 for executables in restmap.conf.
[ success ] Check that restmap.conf file exists at default/restmap.conf and local/restmap.conf when using REST endpoints.
Custom workflow actions structure and standards Custom workflow actions are defined in a workflow_actions.conf file in the /default directory of the app. For more, see About lookups and workflow_actions.conf.
Custom search command structure and standards Custom search commands are defined in a commands.conf file in the /default directory of the app. For more, see About writing custom search commands and commands.conf.
[ success ] Check that commands.conf must explicitly define the python.version to be python3 for each python-scripted custom command.
Alert actions structure and standards Custom alert actions are defined in an alert_actions.conf file located in the /default directory of the app. For more, see Custom alert actions overview and alert_actions.conf.
[ success ] Check that each custom alert action's payload format has a value of xml or json.
[ success ] Check whether any custom alert actions have executable arguments.
[ not_applicable ] Check that each custom alert action has a valid executable. If it does, further check if the executable is Python script. If it does, further check it's Python 3 compatible.
  • No `alert_actions.conf` was detected.
Server configuration file standards Ensure that server.conf is well formed and valid. For detailed information about the server configuration file, see server.conf.
[ success ] Check that server.conf in an app is only allowed to contain: 1. conf_replication_include.\<custom_conf_files> in [shclustering] stanza 2. or EXCLUDE-\<class> property in [diag] stanza,
Props Configuration file standards Ensure that all props.conf files located in the default (or local) folder are well formed and valid. props.conf transforms.conf
[ not_applicable ] Check that the props.conf does not contain lookup() usage in INGEST_EVAL options. This feature is not available in Splunk Cloud. For example: [lookup1] INGEST_EVAL= status_detail=lookup("http_status.csv", json_object("status", status), json_array("status_description"))
  • No INGEST_EVAL properties were declared.
[ success ] Check that pretrained sourctypes in props.confhave only 'TRANSFORM-' or 'SEDCMD' settings,and that those transforms only modify the host, source, or sourcetype.
Meta file standards Ensure that all meta files located in the /metadata folder are well formed and valid.
[ success ] Check that knowledge objects with access control restrictions defined in *.meta files are accessible to customers in Splunk Cloud.
Indexes.conf file standards Ensure that the index configuration file located in the /default and /local folder is well formed and valid. For more, see indexes.conf.
[ not_applicable ] Check that no default Splunk indexes are modified by the app.
  • indexes.conf does not exist
[ not_applicable ] Check that all index names consist only of lowercase characters, numbers, underscores and hyphens. They cannot begin with an underscore or hyphen, or contain the word 'kvstore'. If index names have any uppercase characters any attempts to edit the index in the UI will cause a duplicate index stanza creation which will cause many errors in Splunk.
  • indexes.conf does not exist
[ not_applicable ] Check that indexes.conf only contains the required 'homePath' , 'coldPath', and 'thawedPath' properties or the optional 'frozenTimePeriodInSecs', 'disabled', 'datatype' and 'repFactor' properties. All other properties are prohibited. Also, if repFactor property exists, it's value should be 'auto'. This check is cloud only because indexes are not allowed via check_indexes_conf_does_not_exist.
  • indexes.conf does not exist
[ not_applicable ] Check that all the coldToFrozenScript in indexes.conf are explicitly set the python.version to python3.
  • indexes.conf does not exist
Configuration file standards Ensure that all configuration files located in the /default folder are well formed and valid.
[ success ] Check that app does not contain any .conf files that create global definitions using the [default] stanza.
[ success ] Check that app conf files do not point to files outside the app container. Because hard-coded paths won't work in Splunk Cloud, we don't consider to check absolute paths.
[ success ] Check that all config files parse cleanly- no trailing whitespace after continuations, no duplicated stanzas or options.
[ not_applicable ] Check that the field.<name> type in collections.conf does not include boolean.Use bool instead.
  • collections.conf does not exist
Directory structure standards Ensure that the directories and files in the app adhere to hierarchy standards.
[ not_applicable ] Check that local/passwords.conf does not exist. Password files are not transferable between instances.
  • The local directory does not exist.
[ success ] Check that the app name does not start with digits
[ success ] Check that the file 'local.meta' does not exist. All metadata permissions should be set in 'default.meta'.
[ success ] Check that app has no .conf or dashboard filenames that contain spaces. Splunk software does not support such files.
[ success ] Check that the 'local' directory does not exist. All configuration should be in the 'default' directory.
App.conf standards The app.conf file located at default/app.conf provides key application information and branding. For more, see app.conf.
[ not_applicable ] Check in default/app.conf and 'local/app.conf', install_source_local_checksum not be set explicitly.
  • `local/app.conf` does not exist.
[ not_applicable ] Check in default/app.conf and 'local/app.conf', install_source_checksum not be set explicitly.
  • `local/app.conf` does not exist.
[ success ] Check that custom config files have a corresponding reload trigger in app.conf. Without a reload trigger the app will request a restart on any change to the config file, which may be a negative experience for end-users.
[ success ] Check that the default/app.conf or or local/app.cong contains a label key value pair in the [ui] stanza and the length is between 5 and 80 characters inclusive.
[ success ] Check that the [package] stanza in app.conf has a valid id value.See https://docs.splunk.com/Documentation/Splunk/latest/Admin/Appconf for details.
[ success ] Check that default/app.conf or local/app.cong doesn't have a reload.<CONF_FILE>, where CONF_FILE is a non-custom conf. (https://docs.splunk.com/Documentation/Splunk/latest/Admin/Appconf#.5Btriggers.5D)
[ success ] Check that id attribute under the package stanza in app.confdoes not match with the Splunk Default App names
[ success ] Check that custom .conf files have a a matching conf_replication_include.<conf_file_name> value in server.conf, under the [shclustering] stanza, to ensure that configurations are synchronized across Search Head Clusters.
Saved search standards Saved searches are defined in a savedsearches.conf file located in the /default and /local directory of the app. For more, see Save and share your reports and savedsearches.conf.
[ not_applicable ] Check that savedsearch.conf stanza do not contain action.populate_lookup option`.
  • savedsearches.conf does not exist
[ not_applicable ] Check that if a savedsearch.conf stanza contains scheduling optionsit does contain a dispatch.latest_time
  • savedsearches.conf does not exist
[ not_applicable ] Check that if a scheduled saved search in savedsearch.conf contains dispatch.earliest_time option, or if a scheduled saved search with auto summary enabled contains auto_summarize.dispatch.earliest_time option
  • savedsearches.conf does not exist
[ not_applicable ] Check that savedsearch.conf stanzas do not contain action.script.filename option
  • savedsearches.conf does not exist
[ not_applicable ] Check that no real-time pre-index saved searches are being used insavedsearches.conf. Real-time pre-index saved searches are extremelysystem intensive and should be avoided.
  • savedsearches.conf does not exist
[ not_applicable ] check that default/savedsearches.conf searches are cron scheduledreasonably. Less than five asterisks should be used.
  • savedsearches.conf does not exist
Lookup file standards Lookups add fields from an external source to events based on the values of fields that are already present in those events.
[ not_applicable ] Check that no two files/directories under the lookups directory have this naming pattern respectively:xxx and xxx.default - with the only difference in the .default extension.During the installation of an app in Splunk Cloud, a lookup file will be temporarily renamed to append an additional.default extension to it, which will cause error if a namesake file already exists.
  • lookups folder does not exist
JSON file standards
[ success ] Check that all JSON files are well formed.
Modular inputs structure and standards Modular inputs are configured in an inputs.conf.spec file located in the /README directory of the app. For more, see Modular inputs overview, Modular inputs configuration, and Modular inputs basic example.
[ not_applicable ] Check that all the modular inputs defined in inputs.conf.spec are explicitlyset the python.version to python3
  • No `inputs.conf.spec` file exists.
Web.conf File Standards Ensure that web.conf is safe for cloud deployment and that any exposed patterns match endpoints defined by the app - apps should not expose endpoints other than their own. Including web.conf can have adverse impacts for cloud. Allow only [endpoint:*] and [expose:*] stanzas, with expose only containing pattern= and methods= properties. - web.conf
[ success ] Check that web.conf only defines [endpoint:] and [expose:]stanzas, with [expose:*] only containing pattern= and methods=.
Deprecated features from Splunk Enterprise 9.0.1 The following features should not be supported in Splunk 9.0.1 or later. For more, see Deprecated features and Changes for Splunk App developers.
[ success ] Check search v1 deprecated API usages
Deprecated features from Splunk Enterprise 8.0 The following features should not be supported in Splunk 8.0.0 or later. For more, see Deprecated features and Changes for Splunk App developers.
[ success ] Check for the existence of the M2Crypto package usage, which is removed in the Splunk Enterprise 8.0.
[ warning ] Check for the existence of Python scripts, which must be upgraded to be cross-compatible with Python 2 and 3 for Splunk Enterprise 8.0.
  • 235 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.
[ warning ] Check for the existence of Python code block in Mako templates, which must be upgraded to be Python 3-compatible for the Splunk Enterprise 8.0.
  • Update Mako templates to be Python 3-compatible. Splunk Web, which Mako templates depend on, will support only Python 3.7. If you've finished your update, please disregard this message. File: appserver/templates/base.html
[ success ] Check for the existence of custom CherryPy endpoints, which must be upgraded tobe Python 3-compatible for the Splunk Enterprise 8.0.
[ success ] Check that there is no Advanced XML, which was deprecated in Splunk Enterprise 6.3.
Deprecated features from Splunk Enterprise 7.3 The following features should not be supported in Splunk 7.3 or later. For more, see Deprecated features and Changes for Splunk App developers.
[ success ] Check for use of tscollect SPL command in .conf files and SimpleXML.
Deprecated features from Splunk Enterprise 7.2 The following features should not be supported in Splunk 7.2 or later. For more, see Deprecated features and Changes for Splunk App developers.
[ not_applicable ] Check deprecated literals.conf existence.
  • literals.conf does not exist
Deprecated features from Splunk Enterprise 7.1 The following features should not be supported in Splunk 7.1 or later. For more, see Deprecated features and Changes for Splunk App developers.
[ success ] Check for use of input SPL command in .conf files and SimpleXML.
Deprecated or removed features from Splunk Enterprise 6.6 The following features should not be supported in Splunk 6.6 or later. For more, see Deprecated features and Changes for Splunk App developers.
[ success ] Check existence for displayRowNumbers option in simple xml. This option is no longer supported since Splunk 6.6.
[ success ] Check apps/appinstall usages
[ not_applicable ] Check removed support for setting autoLB in outputs.conf
  • outputs.conf does not exist
Deprecated features from Splunk Enterprise 6.5 The following features should not be supported in Splunk 6.5 or later. For more, see Deprecated features and Changes for Splunk App developers.
[ success ] Check Dashboard XML files for <option> element with the deprecated option value "refresh.auto.interval" i.e. <option name="refresh.auto.interval">
Deprecated features from Splunk Enterprise 6.4 The following features should not be supported in Splunk 6.4 or later. For more, see Deprecated features and Changes for Splunk App developers.
[ success ] Checks that views are not importing googlemapsview.
[ success ] Checks that views are not importing d3chartview.
[ success ] Check that web.conf does not use the simple_xml_module_renderproperty.
[ success ] Check that web.conf does not use the simple_xml_force_flash_chartingproperty.
[ success ] Check Simple XML files for <single> panels with deprecated options'additionalClass', 'afterLabel', 'beforeLabel', 'classField', 'linkFields','linkSearch', 'linkView'
[ success ] Check that <option name="height"> uses an integer for the value.Do not use <option name="height">[value]px</option>.
Deprecated features from Splunk Enterprise 6.3 These following features should not be supported in Splunk 6.3 or later. For more, see Deprecated features and Changes for Splunk App developers.
[ success ] Check for the deprecated <seed> option in Simple XML forms. Use the <initialValue> element instead.
[ success ] Check for the deprecated <option name='previewResults'> in Simple XML files.
[ success ] Check for Simple XML <chart> panels with deprecated options charting.axisLabelsY.majorTickSize or charting.axisLabelsY.majorLabelVisibility.
[ success ] Check for use of Django bindings.
[ not_applicable ] Check for use of running a script in alert action
  • savedsearches.conf does not exist
Deprecated features from Splunk Enterprise 6.2 The following features should not be supported in Splunk 6.2 or later. https://docs.splunk.com/Documentation/Splunk/6.2.0/ReleaseNotes/Deprecatedfeatures
[ success ] Check for the deprecated grouping attribute of row node in Simple XML files.Use the <panel> node instead.
[ success ] Check for the deprecated <populatingSearch> and <populatingSavedSearch> elements in dashboard XML files.Use the <search> element instead.
[ success ] Check for the deprecated <earliestTime> and <latestTime> elements in dashboard XML files.As of version 6.2 these elements are replaced by <earliest> and <latest> elements.
[ success ] Check Dashboard XML files for <list> element. <list>was deprecated in Splunk 6.2 and removed in Splunk 6.5.
Deprecated features from Splunk Enterprise 6.1 The following features should not be supported in Splunk 6.1 or later.
[ success ] Check that deprecated datamodel/acceleration is not used. https://docs.splunk.com/Documentation/Splunk/6.2.0/RESTREF/RESTknowledge
Deprecated features from Splunk Enterprise 6.0 The following features should not be supported in Splunk 6.0 or later.
[ not_applicable ] Check that viewstates.conf does not exist at local/viewstates.confor at default/viewstates.conf. in the app.(http://docs.splunk.com/Documentation/Splunk/6.0/AdvancedDev/Migration#Viewstates_are_no_longer_supported_in_simple_XML)
  • viewstates.conf does not exist
[ not_applicable ] Check that app does not contain crawl.conf as it was deprecated & removed in Splunk.
  • crawl.conf does not exist
Deprecated features from Splunk Enterprise 5.0 The following features should not be supported in Splunk 5.0 or later.
[ not_applicable ] Check that saved searches are not used within event types. https://docs.splunk.com/Documentation/Splunk/5.0/ReleaseNotes/Deprecatedfeatures https://docs.splunk.com/Documentation/Splunk/7.2.5/Knowledge/Abouteventtypes
  • eventtypes.conf does not exist
[ success ] Check for use of findtypes SPL command in .conf files and SimpleXML.
Outputs.conf file standards Ensure that the outputs.conf file located in the /default folder of the app is well formed and valid. For more, see outputs.conf.
[ not_applicable ] Check that forwarding enabled in 'outputs.conf' is failed in cloud
  • outputs.conf does not exist
Limits.conf file standards Ensure that /default/limits.conf or local/limits.conf file is omitted. When included in the app, the limits.conf file changes the limits that are placed on the system for hardware use and memory consumption, which is a task that should be handled by Splunk administrators and not by Splunk app developers. For more, see limits.conf.
[ not_applicable ] Check that default/limits.conf or local/limits.conf has not been included.
  • limits.conf does not exist
jQuery vulnerabilities
[ success ] Check that the dashboards in your app have a valid version attribute.
[ success ] Check for HTML dashboards, which are deprecated.
[ success ] Check that the app files are not importing files directly from the search head.
JavaScript file standards
[ success ] Check that app does not use REST endpoint to collect and send telemetry data.
[ success ] Check if any weak encryption in JavaScript
[ success ] Check if the app contains udp communication in JavaScript files.
[ success ] Check for usages of telemetry metrics in JavaScript
[ not_applicable ] Check if possible stored xss in JavaScript
  • `default/setup.xml` does not exist. The stored xss check is not applicable
[ manual_check ] Check if the app contain possible remote code execution in JavaScript files.
  • The following line will be inspected during code review. Match: eval("(".concat(rawStr," File: appserver/static/js/build/307.88617895514dfe615b67.js Line Number: 2
[ success ] Check if possible reflected xss in JavaScript
[ success ] Check if the app contain possible insecure http request in JavaScript files.
[ success ] Check if the app contains possible iframe in JavaScript files, templates or html pages.
[ success ] Check if any sensitive data leakage in console log
Check for git conflict releated issue
[ success ] Check no git merge conflict is present
Checking for Front-end Libraries This check looks for various front-end libraries inside of apps. As of 03/23/2022, we are looking at Splunk UI and it's predecessor, SplunkJS. This is currently an INFORMATIONAL Check. Updated on 04/17/2023 This check now is expanded to look for several other critical front-end libraries. 1. We have expanded the regex matching to be more inline with all of the UDF Packages https://splunkui.splunk.com/Packages/dashboard-docs/?path=%2FFAQ 2. We have added a few other critical packages (@splunk/react-search, @splunk/react-time-range, @splunk/search-job, @splunk/ui-utils, @splunk/splunk-utils, @splunk/moment) 3. We have expanded the regex matching to be more inline with more of the Visualizations packages.
[ success ] Check that @splunk/visualizations is being used.
[ warning ] Check that SUI is being used.
  • Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/react-toast-notifications File: appserver/static/js/build/922.8a8a6f6a2ee3e15c3f16.js.map Line Number: 1
  • Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/themes File: appserver/static/js/build/307.88617895514dfe615b67.js.map Line Number: 1
  • Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/themes File: appserver/static/js/build/188.256235eb68ae7193e7ea.js.map Line Number: 1
  • Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/themes File: appserver/static/js/build/987.6ec28389c3adf57d57c6.js.map Line Number: 1
  • Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/react-ui File: appserver/static/js/build/354.fd7d08274e1955fdbd9d.js.map Line Number: 1
  • Splunk has begun gathering telemetry on apps submitted to appinspect, that utilize Splunk UI. Please ignore this warning as it has no impact to your Splunk app. Match: @splunk/react-page File: appserver/static/js/build/entry_page.js.map Line Number: 1
[ warning ] Check that SplunkJS is being used.
  • Splunk 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 File: appserver/static/js/build/entry_page.js Line Number: 2
  • Splunk 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 File: appserver/static/js/build/entry_page.js.map Line Number: 1
[ warning ] Check for usage of utility components.
  • Splunk 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/ui-utils File: appserver/static/js/build/987.6ec28389c3adf57d57c6.js.map Line Number: 1
  • Splunk 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/ui-utils File: appserver/static/js/build/922.8a8a6f6a2ee3e15c3f16.js.map Line Number: 1
  • Splunk 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/ui-utils File: appserver/static/js/build/188.256235eb68ae7193e7ea.js.map Line Number: 1
  • Splunk 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/ui-utils File: appserver/static/js/build/entry_page.js.map Line Number: 1
  • Splunk 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/ui-utils File: appserver/static/js/build/307.88617895514dfe615b67.js.map Line Number: 1
[ success ] Check that @splunk/dashboard-core is being used.
Cloud operations simple application check This group serves to help validate simple applications in an effort to try and automate the validation process for cloud operations.
[ not_applicable ] Check that the app does not create workload_rules.
  • workload_rules.conf does not exist
[ not_applicable ] Check that the app does not create workload_pools.
  • workload_pools.conf does not exist
[ not_applicable ] Check that the app does not create wmi.
  • wmi.conf does not exist
[ not_applicable ] Check that the app does not create user-seed.
  • user-seed.conf does not exist
[ success ] Check that transforms.conf does not contain any transforms with non-python malicious command scripts specified by external_cmd=<string> attribute.
[ not_applicable ] Check that transforms.conf does not contain any transforms with malicious command scripts specified by external_cmd=<string> attribute.
  • `default/transforms.conf` does not exist.
[ success ] Check that the app does not contain configurations of default source type in props.conf, which will overwrite the configurations in system/default/props.conf and may affect other apps.
[ success ] Check that the app contains MS Windows specific components, which will not function correctly in Splunk Cloud whose OS should be Linux x64.
[ not_applicable ] Check that the app does not create telemetry.
  • telemetry.conf does not exist
[ not_applicable ] Check that the app does not create splunk-launch.
  • splunk-launch.conf does not exist
[ not_applicable ] Check that the app does not create sourcetypes.
  • sourcetypes.conf does not exist
[ not_applicable ] Check that the app does not create source-classifier.
  • source-classifier.conf does not exist
[ not_applicable ] Check that the app does not create serverclass.seed.xml.
  • serverclass.seed.xml.conf does not exist
[ not_applicable ] Check that the app does not create serverclass.
  • serverclass.conf does not exist
[ not_applicable ] Check that app does not contain segmenters.conf with Splunk-defined stanza.
  • segmenters.conf does not exist
[ not_applicable ] Check the cmd path pattern of scripted input defined in inputs.conf.
  • `inputs.conf` does not exist.
[ not_applicable ] Check that the app does not create pubsub.
  • pubsub.conf does not exist
[ not_applicable ] Check that the app does not create passwords.
  • passwords.conf does not exist
[ not_applicable ] Check that there is a script file in bin/ for each modular input defined in README/inputs.conf.spec.
  • No `inputs.conf.spec` was detected.
[ not_applicable ] Check that the app does not create messages.
  • messages.conf does not exist
[ not_applicable ] Check that the app does not create literals.
  • literals.conf does not exist
[ success ] Check that Splunk SDK for Java is up-to-date.
[ not_applicable ] Check that the app does not create crawl.
  • crawl.conf does not exist
[ not_applicable ] Check that the app does not create instance.cfg.
  • instance.cfg.conf does not exist
[ not_applicable ] Check that inputs.conf does not have any UDP inputs.
  • inputs.conf does not exist
[ not_applicable ] Check that default/inputs.conf or local/inputs.conf does not contain any tcp:// stanzas.
  • inputs.conf.conf does not exist
[ not_applicable ] Check that inputs.conf does not have any SSL inputs.
  • inputs.conf does not exist
[ not_applicable ] Check that inputs.conf does not contain a splunktcptoken stanza.
  • inputs.conf does not exist
[ not_applicable ] Check that default/inputs.conf or local/inputs.conf does not contain any splunktcp:// stanzas.
  • inputs.conf.conf does not exist
[ not_applicable ] Check that inputs.conf does not have any remote_queue inputs.
  • inputs.conf does not exist
[ not_applicable ] Apps cannot ship a configured HEC token in inputs.conf. HEC tokens must be created by stack admins via ACS. Refer: https://docs.splunk.com/Documentation/Splunk/9.1.0/Data/UsetheHTTPEventCollectorRemove [http://] stanza from inputs.conf.
  • inputs.conf does not exist
[ not_applicable ] Check that inputs.conf does not contain a [http] stanza
  • inputs.conf does not exist
[ not_applicable ] Check that default/inputs.conf or local/inputs.conf does not contain any fschange:// stanzas.
  • inputs.conf.conf does not exist
[ not_applicable ] Check that the app does not create health.
  • health.conf does not exist
[ success ] Check whether the app contains shell files. Shell files will be manually inspected for compliance with Splunk Cloud security policy.
[ not_applicable ] Check if the app contains Perl scripts. Perl scripts will be inspected for compliance with Splunk Cloud security policy.
  • No Perl scripts found in app.
[ not_applicable ] Check whether the app contains java files. Java files will be inspected for compliance with Splunk Cloud security policy.
  • No java files found in app.
[ not_applicable ] Check that default/inputs.conf or local/inputs.conf does not contain any fifo:// stanzas.
  • inputs.conf.conf does not exist
[ not_applicable ] Check that indexes.conf does not declare volumes.
  • indexes.conf.conf does not exist
[ manual_check ] Check that all executable binary files have matching source code. For any binary files, there should be a source code provided with the same name. Or, there should be a decalaration of what the binary file is all about in the app's REAMDE. Details for passing this check will be returned if you fail it.
  • Please ensure the binary files are safe. Related info might be included in App README. Binary   Format: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=70e32f6b4c4800da2508b2effef36317496b3985, not stripped  README: README.txt File: lib/charset_normalizer/md.cpython-310-x86_64-linux-gnu.so
  • Please ensure the binary files are safe. Related info might be included in App README. Binary   Format: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=0821021ce29a35048ca32e86130d2c3424dd2d65, not stripped  README: README.txt File: lib/charset_normalizer/md__mypyc.cpython-310-x86_64-linux-gnu.so
[ not_applicable ] Check that the app does not create deployment.
  • deployment.conf does not exist
[ not_applicable ] Check that the app does not create deploymentclient.
  • deploymentclient.conf does not exist
[ not_applicable ] Check that the app does not create default-mode.
  • default-mode.conf does not exist
[ not_applicable ] Check that the app does not create datatypesbnf.
  • datatypesbnf.conf does not exist
[ success ] Check that custom search commands have an executable or script per stanza.
[ not_applicable ] Check that the app does not create bookmarks.
  • bookmarks.conf does not exist
[ success ] Check that authorize.conf does not contain a [tokens_auth] stanza
[ not_applicable ] Check that the app does not create audit.
  • audit.conf does not exist
[ success ] Check that the static/ directory does not contains any subdirectoriesand contains only known file types.Ensure malicious files are not passed off as metadata files.
[ not_applicable ] Check that only role-mapping stanza is allowed in authenticaiton.conf as long as it doesn't map users to a cloud-internal role.
  • authentication.conf does not exist
[ success ] Check that setup.xml does not exist in the app default or local folders.
[ not_applicable ] Check that python version is python3 for scripted inputs defined in inputs.conf.
  • inputs.conf does not exist
[ success ] Check that the metadata/ directory does not contains any subdirectoriesand only contains .meta files. Ensure malicious files are not passed off as metadata files.
[ not_applicable ] Check that lookups/ contains only approved file types (.csv, .csv.default, .csv.gz, .csv.tgz, .kmz) or files formatted as valid csv. Ensure malicious files are not passed off as lookup files.
  • The `lookups` directory does not exist.
[ not_applicable ] Check that batch input accesses files in a permitted way. To be permissible, the batch input must meet the following criteria: 1) The file path needs to match a file in the directory "$SPLUNK_HOME/var/spool/splunk/" 2) The file name needs to be application specific "$SPLUNK_HOME/etc/apps/" 3) The file name should not end with "stash" or "stash_new"
  • inputs.conf does not exist
[ not_applicable ] Check that batch input has required attributes. The following key/value pairs are required for batch inputs: move_policy = sinkhole
  • inputs.conf does not exist
[ not_applicable ] Check that indexes defined in indexes.conf use relative paths starting with $SPLUNK_DB
  • indexes.conf does not exist
[ not_applicable ] Check if concerningReplicatedFileSize in distsearch.conf is larger than 50 MB.
  • distsearch.conf does not exist
[ not_applicable ] Check that directories under data/ui contain only allowed files. Identify for manual review items that might cause passwords to be stored in plaintext.
  • data/ui/manager does not exist
[ success ] Check that directories under data/ui contain only allowed files. Ensure unnecessary, unwanted files are not bundled in the app inappropriately.
[ success ] Check that authorize.conf does not grant excessive administrative permissions to the user. Prevent roles from gaining unauthorized permissions.
[ not_applicable ] Check that commands referenced in the alert.execute.cmd property of all alert actions are checked for compliance with Splunk Cloud security policy. Prevent alert_actions.conf from being used to execute malicious commands.
  • alert_actions.conf does not exist
Source code and binaries standards
[ manual_check ] Check that files outside of the bin/ directory do not appear to be executable according to the Unix file command. From man file: files have a ``magic number'' stored in a particular place near the beginning of the file that tells the UNIX operating system that the file is a binary executable.
  • The executable will be inspected during code review: File: lib/defusedxml/cElementTree.py
  • The executable will be inspected during code review: File: lib/idna/core.py
  • The executable will be inspected during code review: File: lib/defusedxml/sax.py
  • The executable will be inspected during code review: File: lib/idna/codec.py
  • The executable will be inspected during code review: File: lib/sockshandler.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/rest_handler/admin_external.py
  • The executable will be inspected during code review: File: lib/idna/intranges.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/data_collection/ta_data_loader.py
  • The executable will be inspected during code review: File: lib/splunktalib/schedule/scheduler.py
  • The executable will be inspected during code review: File: lib/splunktalib/splunk_cluster.py
  • The executable will be inspected during code review: File: lib/defusedxml/common.py
  • The executable will be inspected during code review: File: lib/certifi/__main__.py
  • The executable will be inspected during code review: File: lib/solnlib/server_info.py
  • The executable will be inspected during code review: File: lib/splunktalib/event_writer.py
  • The executable will be inspected during code review: File: lib/splunktalib/state_store.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/rest_handler/util.py
  • The executable will be inspected during code review: File: lib/defusedxml/pulldom.py
  • The executable will be inspected during code review: File: lib/splunktalib/splunk_platform.py
  • The executable will be inspected during code review: File: lib/solnlib/conf_manager.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/splunk_aoblib/rest_migration.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/rest_handler/cred_mgmt.py
  • The executable will be inspected during code review: File: lib/solnlib/file_monitor.py
  • The executable will be inspected during code review: File: lib/splunktalib/schedule/job.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/rest_handler/eai.py
  • The executable will be inspected during code review: File: lib/splunktalib/timer_queue.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/rest_handler/base.py
  • The executable will be inspected during code review: File: lib/splunktalib/timer.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/common/__init__.py
  • The executable will be inspected during code review: File: lib/splunktalib/common/util.py
  • The executable will be inspected during code review: File: lib/solnlib/time_parser.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/data_collection/ta_data_collector.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/config.py
  • The executable will be inspected during code review: File: lib/cribl_libs.py
  • The executable will be inspected during code review: File: lib/splunktalib/kv_client.py
  • The executable will be inspected during code review: File: lib/idna/uts46data.py
  • The executable will be inspected during code review: File: lib/defusedxml/expatreader.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/rest_handler/endpoint/converter.py
  • The executable will be inspected during code review: File: lib/certifi/core.py
  • The executable will be inspected during code review: File: lib/splunktalib/conf_manager/request.py
  • The executable will be inspected during code review: File: lib/splunktalib/concurrent/thread_pool.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/data_collection/ta_mod_input.py
  • The executable will be inspected during code review: File: lib/splunktalib/common/pattern.py
  • The executable will be inspected during code review: File: lib/idna/__init__.py
  • The executable will be inspected during code review: File: lib/splunktalib/orphan_process_monitor.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/global_config/__init__.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/rest_handler/normaliser.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/rest_handler/schema.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/rest_handler/entity.py
  • The executable will be inspected during code review: File: lib/splunktalib/modinput.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/rest_handler/error.py
  • The executable will be inspected during code review: File: lib/splunktalib/credentials.py
  • The executable will be inspected during code review: File: lib/splunktalib/conf_manager/data_input_endpoints.py
  • The executable will be inspected during code review: File: lib/splunktalib/rest.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/data_collection/ta_helper.py
  • Suppressed 109 manual_check messages
  • The executable will be inspected during code review: File: lib/defusedxml/xmlrpc.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/rest_handler/datainput.py
  • The executable will be inspected during code review: File: lib/certifi/__init__.py
  • The executable will be inspected during code review: File: lib/socks.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/rest_handler/credentials.py
  • The executable will be inspected during code review: File: lib/solnlib/log.py
  • The executable will be inspected during code review: File: lib/solnlib/net_utils.py
  • The executable will be inspected during code review: File: lib/defusedxml/expatbuilder.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/data_collection/ta_config.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/rest_handler/endpoint/__init__.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/global_config/schema.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/global_config/configuration.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/rest_handler/endpoint/validator.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/rest_handler/poster.py
  • The executable will be inspected during code review: File: lib/splunktalib/common/xml_dom_parser.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/rest_handler/multimodel.py
  • The executable will be inspected during code review: File: lib/splunktalib/file_monitor.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/rest_handler/teardown.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/rest_handler/handler.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/rest_handler/endpoint/field.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/data_collection/ta_checkpoint_manager.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/rest_handler/base_hook_mixin.py
  • The executable will be inspected during code review: File: lib/splunktalib/concurrent/process_pool.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/common/log.py
  • The executable will be inspected during code review: File: lib/splunktalib/common/log.py
  • The executable will be inspected during code review: File: lib/splunktalib/conf_manager/conf_manager.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/splunk_aoblib/rest_helper.py
  • The executable will be inspected during code review: File: lib/idna/compat.py
  • The executable will be inspected during code review: File: lib/defusedxml/minidom.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/splunk_aoblib/setup_util.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/rest_handler/error_ctl.py
  • The executable will be inspected during code review: File: lib/defusedxml/ElementTree.py
  • The executable will be inspected during code review: File: lib/splunktalib/concurrent/concurrent_executor.py
  • The executable will be inspected during code review: File: lib/defusedxml/__init__.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/data_collection/ta_data_client.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/modinput_wrapper/base_modinput.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/alert_actions_base.py
  • The executable will be inspected during code review: File: lib/solnlib/splunk_rest_client.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/cim_actions.py
  • The executable will be inspected during code review: File: lib/defusedxml/lxml.py
  • The executable will be inspected during code review: File: lib/splunktalib/conf_manager/property_endpoints.py
  • The executable will be inspected during code review: File: lib/splunktalib/conf_manager/conf_endpoints.py
  • The executable will be inspected during code review: File: lib/splunktaucclib/rest_handler/validator.py
  • The executable will be inspected during code review: File: lib/splunktalib/conf_manager/ta_conf_manager.py
  • The executable will be inspected during code review: File: lib/rest_handler.py
[ success ] Check that files outside of the bin/ and appserver/controllers directory do not have execute permissions. Splunk Cloud is a Linux-based platform, Splunk recommends 644 for all app files outside of the bin/ directory, 644 for scripts within the bin/ directory that are invoked using an interpreter (e.g. python my_script.py or sh my_script.sh), and 755 for scripts within the bin/ directory that are invoked directly (e.g. ./my_script.sh or ./my_script).
Security vulnerabilities
[ success ] Check that all outgoing connections use TLS in accordance to Splunk Cloud Platform policy.
[ success ] Check for sensitive information being exposed in transit via URL query string parameters
[ manual_check ] Check for passwords and secrets.
  • The following line will be inspected during code review.Possible secret disclosure found. Match:                 this.isSingleOauth = authType.includes('oauth');\n File: appserver/static/js/build/307.88617895514dfe615b67.js.map Line Number: 1
  • The following line will be inspected during code review.Possible secret disclosure found. Match: in.org/basic-auth/user/pass', auth=('user', File: lib/requests-2.31.0.dist-info/METADATA Line Number: 49
  • The following line will be inspected during code review.Possible secret disclosure found. Match: pFullName, secret) {\n    if (secret === File: appserver/static/js/build/entry_page.js.map Line Number: 1
  • The following line will be inspected during code review.Possible secret disclosure found. Match: passSystemAuth        = true File: default/restmap.conf Line Number: 34
  • The following line will be inspected during code review.Possible secret disclosure found. Match: ...auth... File: appserver/static/js/build/307.88617895514dfe615b67.js Line Number: 2
[ success ] Check for insecure HTTP calls in Python.
[ manual_check ] Check for environment variable manipulation and attempts to monitor sensitive environment variables.
  • Environment variable being used in lib/solnlib/splunkenv.py:194: os.environ. File: lib/solnlib/splunkenv.py Line Number: 194
  • Environment variable being used in lib/splunktaucclib/rest_handler/admin_external.py:74: os.environ.get. File: lib/splunktaucclib/rest_handler/admin_external.py Line Number: 74
  • Environment variable being used in lib/splunktaucclib/rest_handler/admin_external.py:78: os.environ. File: lib/splunktaucclib/rest_handler/admin_external.py Line Number: 78
  • Environment variable being used in lib/solnlib/splunkenv.py:193: os.environ. File: lib/solnlib/splunkenv.py Line Number: 193
  • Environment variable being used in lib/splunktaucclib/rest_handler/util.py:97: os.environ. File: lib/splunktaucclib/rest_handler/util.py Line Number: 97
  • Environment variable being used in lib/splunktaucclib/splunk_aoblib/setup_util.py:151: os.environ.get. File: lib/splunktaucclib/splunk_aoblib/setup_util.py Line Number: 151
  • Environment variable being used in lib/solnlib/splunkenv.py:208: os.environ.get. File: lib/solnlib/splunkenv.py Line Number: 208
  • Environment variable being used in lib/solnlib/splunkenv.py:60: os.environ. File: lib/solnlib/splunkenv.py Line Number: 60
  • Environment variable being used in lib/splunktaucclib/modinput_wrapper/base_modinput.py:164: os.environ.get. File: lib/splunktaucclib/modinput_wrapper/base_modinput.py Line Number: 164
  • Environment variable being used in lib/solnlib/splunkenv.py:55: os.environ. File: lib/solnlib/splunkenv.py Line Number: 55
  • Environment variable being used in lib/splunktaucclib/modinput_wrapper/base_modinput.py:222: os.environ.get. File: lib/splunktaucclib/modinput_wrapper/base_modinput.py Line Number: 222
  • Environment variable being used in lib/splunktaucclib/rest_handler/util.py:100: os.environ. File: lib/splunktaucclib/rest_handler/util.py Line Number: 100
  • Environment variable being used in bin/cribl.py:34: os.environ. File: bin/cribl.py Line Number: 34
  • Environment variable being used in lib/splunktaucclib/rest_handler/util.py:98: os.environ. File: lib/splunktaucclib/rest_handler/util.py Line Number: 98
  • Environment variable being used in lib/splunktaucclib/splunk_aoblib/setup_util.py:149: os.environ.get. File: lib/splunktaucclib/splunk_aoblib/setup_util.py Line Number: 149
  • Environment variable being used in lib/solnlib/splunkenv.py:209: os.environ. File: lib/solnlib/splunkenv.py Line Number: 209
  • Environment variable being used in lib/cribl_libs.py:32: os.environ. File: lib/cribl_libs.py Line Number: 32
  • Environment variable being used in lib/splunktaucclib/rest_handler/util.py:99: os.environ. File: lib/splunktaucclib/rest_handler/util.py Line Number: 99
  • Environment variable being used in bin/cribl_rest_handler.py:21: os.environ. File: bin/cribl_rest_handler.py Line Number: 21
  • Environment variable being used in lib/splunktaucclib/modinput_wrapper/base_modinput.py:537: os.environ. File: lib/splunktaucclib/modinput_wrapper/base_modinput.py Line Number: 537
  • Environment variable being used in lib/solnlib/splunkenv.py:271: os.environ. File: lib/solnlib/splunkenv.py Line Number: 271
  • Environment variable being used in lib/splunktaucclib/rest_handler/admin_external.py:75: os.environ. File: lib/splunktaucclib/rest_handler/admin_external.py Line Number: 75
Operating system standards
[ success ] Check for the use of malicious shell commands in configuration files or shell scripts to corrupt the OS or Splunk instance. Other scripting languages are covered by other checks.
Malware, viruses, malicious content, user security standards (static checks)
[ warning ] Check that no sensitive hostnames/IPs are stored in the app.
  • PUBLIC IP 5.5.5.5 is found in lib/PySocks-1.7.1.dist-info/METADATA:70 File: lib/PySocks-1.7.1.dist-info/METADATA Line Number: 70
Bias language (static checks)
[ warning ] Check that the app does not include any bias words.
  • Bias language is found in the app. was not in the method <<<WHITELIST>>>. (Issue #1059) (lib/urllib3-1.26.18.dist-info/METADATA:685) [whitelist]. File: METADATA Line Number: 685
  • Bias language is found in the app. for key in ("apps", "slave-apps", "<<<MASTER>>>-apps"): (lib/splunktaucclib/rest_handler/util.py:85) [master]. File: util.py Line Number: 85
  • Bias language is found in the app. This project is [MIT](https://github.com/Ousret/charset_normalize... (lib/charset_normalizer-3.3.2.dist-info/METADATA:278) [master]. File: METADATA Line Number: 278
  • Bias language is found in the app. :target: https://codecov.io/github/tiran/defusedxml?branch=<<<MAS... (lib/defusedxml-0.7.1.dist-info/METADATA:47) [master]. File: METADATA Line Number: 47
  • Bias language is found in the app. <<<BLACKLIST>>> = _etree._Entity (lib/defusedxml/lxml.py:38) [blacklist]. File: lxml.py Line Number: 38
  • Bias language is found in the app. .. image:: https://codecov.io/github/tiran/defusedxml/coverage.sv... (lib/defusedxml-0.7.1.dist-info/METADATA:46) [master]. File: METADATA Line Number: 46
  • Bias language is found in the app. and release. The <<<MASTER>>> branch received the same fix in Pul... (lib/urllib3-1.26.18.dist-info/METADATA:735) [master]. File: METADATA Line Number: 735
  • Bias language is found in the app. <<<BLACKLIST>>> = self.<<<BLACKLIST>>> (lib/defusedxml/lxml.py:41) [blacklist]. File: lxml.py Line Number: 41
  • Bias language is found in the app. .. _`Requests`: https://requests.readthedocs.io/en/<<<MASTER>>>/ (lib/certifi-2023.11.17.dist-info/METADATA:58) [master]. File: METADATA Line Number: 58
  • Bias language is found in the app. if isinstance(child, <<<BLACKLIST>>>): (lib/defusedxml/lxml.py:43) [blacklist]. File: lxml.py Line Number: 43
  • Bias language is found in the app. {"version":3,"file":"188.256235eb68ae7193e7ea.js","mappings":"0GA... (appserver/static/js/build/188.256235eb68ae7193e7ea.js.map:1) [master]. File: 188.256235eb68ae7193e7ea.js.map Line Number: 1
  • Bias language is found in the app. .. image:: https://ci.appveyor.com/api/projects/status/github/gra... (lib/sortedcontainers-2.4.0.dist-info/METADATA:146) [master]. File: METADATA Line Number: 146
  • Bias language is found in the app. Project-URL: Changelog, https://github.com/kjd/idna/blob/<<<MASTE... (lib/idna-3.6.dist-info/METADATA:29) [master]. File: METADATA Line Number: 29
  • Bias language is found in the app. groups_url = f"/api/v1/<<<MASTER>>>/groups?product=stream" (bin/cribl.py:125) [master]. File: cribl.py Line Number: 125
  • Bias language is found in the app. .. image:: https://travis-ci.org/tiran/defusedxml.svg?branch=<<<M... (lib/defusedxml-0.7.1.dist-info/METADATA:42) [master]. File: METADATA Line Number: 42
  • Bias language is found in the app. # <<<BLACKLIST>>> = (etree._Entity, etree._ProcessingInstruction,... (lib/defusedxml/lxml.py:37) [blacklist]. File: lxml.py Line Number: 37
  • Bias language is found in the app. for key in ("apps", "slave-apps", "<<<MASTER>>>-apps"): (lib/splunktalib/common/util.py:103) [master]. File: util.py Line Number: 103
  • Bias language is found in the app. .. image:: https://api.travis-ci.org/grantjenks/python-sortedcont... (lib/sortedcontainers-2.4.0.dist-info/METADATA:143) [master]. File: METADATA Line Number: 143
  • Bias language is found in the app. {"version":3,"file":"entry_page.js","mappings":";UAAIA,ECCAC,EADA... (appserver/static/js/build/entry_page.js.map:1) [master]. File: entry_page.js.map Line Number: 1
addon_builder.conf standards The addon_builder.conf file located at default/addon_builder.conf provides the information about the add on builder associated with the Splunk App
[ not_applicable ] Check that the addon_builder.conf contains an builder version number between 4.1.3 and 4.1.4 in the [base] stanza. Ensure that apps built with Add-on Builder are maintained with an up-to-date version of Add-on Builder.
  • addon_builder.conf does not exist
Binary file standards
[ success ] Checks that binaries that are distributed to the IDX tier of a distributed Splunk platform deployment are compatible with aarch64.
Authorize.conf file standards Ensure that the authorize configuration file located in the /default folder is well formed and valid. For more, see authorize.conf.
[ success ] Check that authorize.conf does not contain any modified capabilities.
Authentication.conf file standards Ensure that bindDNpassword is not specified. For more, see authentication.conf.
[ not_applicable ] Check that all the scripted authentications defined in authentication.conf are explicitly set the python.version to python3.
  • authentication.conf does not exist
[ not_applicable ] Check that saml-* stanzas in authentication.conf do not turn off signedAssertion property.
  • authentication.conf does not exist
Splunk app packaging standards These checks validate that a Splunk app has been correctly packaged, and can be provided safely for package validation.
[ not_applicable ] Check that the Splunk App package with a .dependencies directory also contains an app folder with an app.manifest.
  • No ../.dependencies folder found. Please add a .dependencies directory that contains an app folder with an app.manifest.
[ success ] Check that the extracted Splunk App does not contains only app.conf
[ not_applicable ] Check that the app does not use Adobe Flash files.
  • Didn't find any flash files.
[ success ] Check that the extracted Splunk App contains a default/app.conf file that contains an [id] or [launcher] stanza with a version property that is formatted as Major.Minor.Revision.
[ not_applicable ] Check that the Splunk App package with a .dependencies directory also contains exactly one valid app folder.
  • No ../.dependencies folder found. Please add a .dependencies directory with an valid app folder.
[ success ] Check that the Splunk app provided a valid compressed file.
[ success ] Check that the Splunk app provided does not start with a . character.
[ not_applicable ] Check that the Splunk App package contains only valid dependencies. Dependencies are valid if a .dependencies directory contains only valid app packages inside.
  • No ../.dependencies folder found. Please check that the Splunk App package contains only valid dependencies.
[ success ] Check that the Splunk app provided does not contain incorrect permissions. Packages must have the owner's read permission set to r (400).
[ success ] Check that the compressed artifact extracts to a directory that does not start with a . character.
[ success ] Check that the Splunk App package does not contain any non-app files. Files within a valid app folder or valid dependencies within a .dependencies folder are permitted, all other files are not.
[ success ] Check that the extracted Splunk App does not contain any directories or files that start with a ., or directories that start with __MACOSX.
[ success ] Check that the extracted Splunk App does not contain any directories with incorrect permissions. Directories and subdirectories must have the owner's permissions set to r/w/x (700).
[ success ] Check that the extracted Splunk App does not contain any files with incorrect permissions. Files must have the owner's permissions include read and write (600).
[ success ] Check that the extracted Splunk App contains a default/app.conf file.