# Panther Analysis Tool
[Panther Analysis Tool](https://github.com/panther-labs/panther_analysis_tool)
is a Python application for testing, packaging, and deploying Panther
Detections.
For further details, see [Quick Start](https://docs.panther.com/quick-start) and
[Panther Documentation](https://docs.panther.com/).
## Installation
### From PyPi
Use pip to install
[panther_analysis_tool package](https://pypi.org/project/panther-analysis-tool/)
from PyPi:
```shell
pip3 install panther_analysis_tool
```
Or without a virtual environment:
```shell
make deps
pip3 install -e .
```
### From source
```shell
make install
pipenv run -- pip3 install -e .
```
## Usage
### Help
Show available commands and their options:
```bash
$ panther_analysis_tool -h
usage: panther_analysis_tool [-h] [--version] [--debug] [--skip-version-check] {release,test,publish,upload,delete,update-custom-schemas,test-lookup-table,validate,zip,check-connection,benchmark,enrich-test-data} ...
Panther Analysis Tool: A command line tool for managing Panther policies and rules.
positional arguments:
{release,test,publish,upload,delete,update-custom-schemas,test-lookup-table,validate,zip,check-connection,benchmark,enrich-test-data}
release Create release assets for repository containing panther detections. Generates a file called panther-analysis-all.zip and optionally generates panther-analysis-all.sig
test Validate analysis specifications and run policy and rule tests.
publish Publishes a new release, generates the release assets, and uploads them. Generates a file called panther-analysis-all.zip and optionally generates panther-analysis-all.sig
upload Upload specified policies and rules to a Panther deployment.
delete Delete policies, rules, or saved queries from a Panther deployment
update-custom-schemas
Update or create custom schemas on a Panther deployment.
test-lookup-table Validate a Lookup Table spec file.
validate Validate your bulk uploads against your panther instance
zip Create an archive of local policies and rules for uploading to Panther.
check-connection Check your Panther API connection
benchmark Performance test one rule against one of its log types. The rule must be the only item in the working directory or specified by --path, --ignore-files, and --filter. This feature is an extension
of Data Replay and is subject to the same limitations.
enrich-test-data Enrich test data with additional enrichments from the Panther API.
optional arguments:
-h, --help show this help message and exit
--version show program's version number and exit
--debug
--skip-version-check
```
### Test
Run tests for a given path:
```bash
$ panther_analysis_tool test --path tests/fixtures/valid_policies/
[INFO]: Testing analysis packs in tests/fixtures/valid_policies/
AWS.IAM.MFAEnabled
[PASS] Root MFA not enabled fails compliance
[PASS] User MFA not enabled fails compliance
```
### Upload
Create packages to upload through the Panther UI:
```bash
$ panther_analysis_tool zip --path tests/fixtures/valid_policies/ --out tmp
[INFO]: Testing analysis packs in tests/fixtures/valid_policies/
AWS.IAM.MFAEnabled
[PASS] Root MFA not enabled fails compliance
[PASS] User MFA not enabled fails compliance
[INFO]: Zipping analysis packs in tests/fixtures/valid_policies/ to tmp
[INFO]: <current working directory>/tmp/panther-analysis-2020-03-23T12-48-18.zip
```
Or upload packages directly into Panther:
```bash
$ panther_analysis_tool upload --path tests/fixtures/valid_policies/ --out tmp
[INFO]: Testing analysis packs in tests/fixtures/valid_policies/
AWS.IAM.MFAEnabled
[PASS] Root MFA not enabled fails compliance
[PASS] User MFA not enabled fails compliance
AWS.IAM.BetaTest
[PASS] Root MFA not enabled fails compliance
[PASS] User MFA not enabled fails compliance
AWS.CloudTrail.MFAEnabled
[PASS] Root MFA not enabled fails compliance
[PASS] User MFA not enabled fails compliance
[INFO]: Zipping analysis packs in tests/fixtures/valid_policies/ to tmp
[INFO]: Found credentials in environment variables.
[INFO]: Uploading pack to Panther
[INFO]: Upload success.
[INFO]: API Response:
{
"modifiedPolicies": 0,
"modifiedRules": 0,
"newPolicies": 2,
"newRules": 1,
"totalPolicies": 2,
"totalRules": 1
}
```
### Filtering
The `test`, `zip`, and `upload` commands all support filtering. Filtering works
by passing the `--filter` argument with a list of filters specified in the
format `KEY=VALUE1,VALUE2`. The keys can be any valid field in a policy or rule.
When using a filter, only anaylsis that matches each filter specified will be
considered. For example, the following command will test only items with the
AnalysisType as `policy` AND severity as `High`:
```bash
$ panther_analysis_tool test --path tests/fixtures/valid_policies --filter AnalysisType=policy Severity=High
[INFO]: Testing analysis packs in tests/fixtures/valid_policies
AWS.IAM.BetaTest
[PASS] Root MFA not enabled fails compliance
[PASS] User MFA not enabled fails compliance
```
Alternately, the following command will test items with the AnalysisType
`policy` OR `rule`, AND the severity `High`:
```bash
$ panther_analysis_tool test --path tests/fixtures/valid_policies --filter AnalysisType=policy,rule Severity=High
[INFO]: Testing analysis packs in tests/fixtures/valid_policies
AWS.IAM.BetaTest
[PASS] Root MFA not enabled fails compliance
[PASS] User MFA not enabled fails compliance
AWS.CloudTrail.MFAEnabled
[PASS] Root MFA not enabled fails compliance
[PASS] User MFA not enabled fails compliance
```
When writing policies or rules that refer to the global analysis types, include
them in the filter. An empty string as a filter value means the filter applies
only if the field exists. The following command returns an error: the policy
imports a global, but the global lacks a severity and thus is excluded by the
filter.
```bash
$ panther_analysis_tool test --path tests/fixtures/valid_policies --filter AnalysisType=policy,global Severity=Critical
[INFO]: Testing analysis packs in tests/fixtures/valid_policies
AWS.IAM.MFAEnabled
[ERROR] Error loading module, skipping
Invalid: tests/fixtures/valid_policies/example_policy.yml
No module named 'panther'
[ERROR]: [('tests/fixtures/valid_policies/example_policy.yml', ModuleNotFoundError("No module named 'panther'"))]
```
For this query to work, allow for the abscence of the severity field:
```bash
$ panther_analysis_tool test --path tests/fixtures/valid_policies --filter AnalysisType=policy,global Severity=Critical,""
[INFO]: Testing analysis packs in tests/fixtures/valid_policies
AWS.IAM.MFAEnabled
[PASS] Root MFA not enabled fails compliance
[PASS] User MFA not enabled fails compliance
```
Filters work for the `zip` and `upload` commands in the exact same way they work
for the `test` command.
In addition to filtering, setting a minimum number of unit tests is possible
with the --minimum-tests flag. Detections lacking the minimum number of tests
are considered failing. If `--minimum-tests` is set to 2 or greater, the
requirement becomes that at least one test must return `True` and another must
return `False`.
```
$ panther_analysis_tool test --path tests/fixtures/valid_policies --minimum-tests 2
% panther_analysis_tool test --path okta_rules --minimum-tests 2
[INFO]: Testing analysis packs in okta_rules
Okta.AdminRoleAssigned
[PASS] Admin Access Assigned
Okta.BruteForceLogins
[PASS] Failed login
Okta.GeographicallyImprobableAccess
[PASS] Non Login
[PASS] Failed Login
--------------------------
Panther CLI Test Summary
Path: okta_rules
Passed: 0
Failed: 3
Invalid: 0
--------------------------
Failed Tests Summary
Okta.AdminRoleAssigned
['Insufficient test coverage, 2 tests required but only 1 found.', 'Insufficient test coverage: expected at least one passing and one failing test.']
Okta.BruteForceLogins
['Insufficient test coverage, 2 tests required but only 1 found.', 'Insufficient test coverage: expected at least one passing and one failing test]
Okta.GeographicallyImprobableAccess
['Insufficient test coverage: expected at least one passing and one failing test.']
```
In this case, even though the rules passed all their tests, they are still
considered failing because they do not have the correct test coverage.
### Delete Rules, Policies, or Saved Queries
```bash
$ panther_analysis_tool delete
usage: panther_analysis_tool delete [-h] [--no-confirm] [--athena-datalake] [--api-token API_TOKEN] [--api-host API_HOST] [--aws-profile AWS_PROFILE] [--analysis-id ANALYSIS_ID [ANALYSIS_ID ...]]
[--query-id QUERY_ID [QUERY_ID ...]]
Delete policies, rules, or saved queries from a Panther deployment
optional arguments:
-h, --help show this help message and exit
--no-confirm Skip manual confirmation of deletion (default: False)
--athena-datalake Instance DataLake is backed by Athena (default: False)
--api-token API_TOKEN
The Panther API token to use. See: https://docs.panther.com/api-beta (default: None)
--api-host API_HOST The Panther API host to use. See: https://docs.panther.com/api-beta (default: None)
--aws-profile AWS_PROFILE
The AWS profile to use when updating the AWS Panther deployment. (default: None)
--analysis-id ANALYSIS_ID [ANALYSIS_ID ...]
Space separated list of Detection IDs (default: [])
--query-id QUERY_ID [QUERY_ID ...]
Space separated list of Saved Queries (default: [])
```
Pass a space-separated list of Analysis IDs (RuleID or PolicyID) or QueryIDs.
Use the --no-confirm flag to bypass confirmation prompts. Rules and their
associated saved queries will be matched and deleted. The default configuration
targets a Snowflake datalake; for an Athena datalake, use the --athena-datalake
flag.
## Configuration File
Panther Analysis Tool will also read options from a configuration file
`.panther_settings.yml` in the current working directory. An example
configuration file is included in this repo,
[example_panther_config.yml](example_panther_config.yml), that contains example
syntax for supported options.
Options in the configuration file take precedence over command-line options. For
instance, if minimum_tests: 2 is set in the configuration file and
--minimum-tests 1 is specified on the command line, the minimum number of tests
will be 2.
## Contributing
All contributions are welcome. Prior to submitting pull requests, consult the
[contributing guidelines](https://github.com/panther-labs/panther-analysis/blob/master/CONTRIBUTING.md).
For steps to open a pull request from a fork, refer to
[GitHub's guide](https://docs.github.com/en/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request).
### Local Development
To develop with the panther_analysis_tool locally, prepare two repositories:
this one and another containing the panther analysis content for PAT testing.
From your [panther_analysis](https://github.com/panther-labs/panther-analysis)
content repository, install as editable (and test, for example):
```bash
pipenv install --editable ../relative/path/to/panther_analysis_tool
pipenv run panther_analysis_tool test
```
## License
This repository is licensed under the AGPL-3.0
[license](https://github.com/panther-labs/panther-analysis/blob/master/LICENSE).
Raw data
{
"_id": null,
"home_page": "https://github.com/panther-labs/panther_analysis_tool",
"name": "panther-analysis-tool",
"maintainer": null,
"docs_url": null,
"requires_python": null,
"maintainer_email": null,
"keywords": "Security, CLI",
"author": "Panther Labs Inc",
"author_email": "pypi@runpanther.io",
"download_url": "https://files.pythonhosted.org/packages/fb/1d/dbde32e4943083582d8ad2ff16a0d68720152002295062470426f9fcf6b4/panther_analysis_tool-0.48.0.tar.gz",
"platform": null,
"description": "# Panther Analysis Tool\n\n[Panther Analysis Tool](https://github.com/panther-labs/panther_analysis_tool)\nis a Python application for testing, packaging, and deploying Panther\nDetections.\n\nFor further details, see [Quick Start](https://docs.panther.com/quick-start) and\n[Panther Documentation](https://docs.panther.com/).\n\n## Installation\n\n### From PyPi\n\nUse pip to install\n[panther_analysis_tool package](https://pypi.org/project/panther-analysis-tool/)\nfrom PyPi:\n\n```shell\npip3 install panther_analysis_tool\n```\n\nOr without a virtual environment:\n\n```shell\nmake deps\npip3 install -e .\n```\n\n### From source\n\n```shell\nmake install\npipenv run -- pip3 install -e .\n```\n\n## Usage\n\n### Help\n\nShow available commands and their options:\n\n```bash\n$ panther_analysis_tool -h\nusage: panther_analysis_tool [-h] [--version] [--debug] [--skip-version-check] {release,test,publish,upload,delete,update-custom-schemas,test-lookup-table,validate,zip,check-connection,benchmark,enrich-test-data} ...\n\nPanther Analysis Tool: A command line tool for managing Panther policies and rules.\n\npositional arguments:\n {release,test,publish,upload,delete,update-custom-schemas,test-lookup-table,validate,zip,check-connection,benchmark,enrich-test-data}\n release Create release assets for repository containing panther detections. Generates a file called panther-analysis-all.zip and optionally generates panther-analysis-all.sig\n test Validate analysis specifications and run policy and rule tests.\n publish Publishes a new release, generates the release assets, and uploads them. Generates a file called panther-analysis-all.zip and optionally generates panther-analysis-all.sig\n upload Upload specified policies and rules to a Panther deployment.\n delete Delete policies, rules, or saved queries from a Panther deployment\n update-custom-schemas\n Update or create custom schemas on a Panther deployment.\n test-lookup-table Validate a Lookup Table spec file.\n validate Validate your bulk uploads against your panther instance\n zip Create an archive of local policies and rules for uploading to Panther.\n check-connection Check your Panther API connection\n benchmark Performance test one rule against one of its log types. The rule must be the only item in the working directory or specified by --path, --ignore-files, and --filter. This feature is an extension\n of Data Replay and is subject to the same limitations.\n enrich-test-data Enrich test data with additional enrichments from the Panther API.\n\noptional arguments:\n -h, --help show this help message and exit\n --version show program's version number and exit\n --debug\n --skip-version-check\n```\n\n### Test\n\nRun tests for a given path:\n\n```bash\n$ panther_analysis_tool test --path tests/fixtures/valid_policies/\n[INFO]: Testing analysis packs in tests/fixtures/valid_policies/\n\nAWS.IAM.MFAEnabled\n [PASS] Root MFA not enabled fails compliance\n [PASS] User MFA not enabled fails compliance\n```\n\n### Upload\n\nCreate packages to upload through the Panther UI:\n\n```bash\n$ panther_analysis_tool zip --path tests/fixtures/valid_policies/ --out tmp\n[INFO]: Testing analysis packs in tests/fixtures/valid_policies/\n\nAWS.IAM.MFAEnabled\n [PASS] Root MFA not enabled fails compliance\n [PASS] User MFA not enabled fails compliance\n\n[INFO]: Zipping analysis packs in tests/fixtures/valid_policies/ to tmp\n[INFO]: <current working directory>/tmp/panther-analysis-2020-03-23T12-48-18.zip\n```\n\nOr upload packages directly into Panther:\n\n```bash\n$ panther_analysis_tool upload --path tests/fixtures/valid_policies/ --out tmp\n[INFO]: Testing analysis packs in tests/fixtures/valid_policies/\n\nAWS.IAM.MFAEnabled\n [PASS] Root MFA not enabled fails compliance\n [PASS] User MFA not enabled fails compliance\n\nAWS.IAM.BetaTest\n [PASS] Root MFA not enabled fails compliance\n [PASS] User MFA not enabled fails compliance\n\nAWS.CloudTrail.MFAEnabled\n [PASS] Root MFA not enabled fails compliance\n [PASS] User MFA not enabled fails compliance\n\n[INFO]: Zipping analysis packs in tests/fixtures/valid_policies/ to tmp\n[INFO]: Found credentials in environment variables.\n[INFO]: Uploading pack to Panther\n[INFO]: Upload success.\n[INFO]: API Response:\n{\n \"modifiedPolicies\": 0,\n \"modifiedRules\": 0,\n \"newPolicies\": 2,\n \"newRules\": 1,\n \"totalPolicies\": 2,\n \"totalRules\": 1\n}\n```\n\n### Filtering\n\nThe `test`, `zip`, and `upload` commands all support filtering. Filtering works\nby passing the `--filter` argument with a list of filters specified in the\nformat `KEY=VALUE1,VALUE2`. The keys can be any valid field in a policy or rule.\nWhen using a filter, only anaylsis that matches each filter specified will be\nconsidered. For example, the following command will test only items with the\nAnalysisType as `policy` AND severity as `High`:\n\n```bash\n$ panther_analysis_tool test --path tests/fixtures/valid_policies --filter AnalysisType=policy Severity=High\n[INFO]: Testing analysis packs in tests/fixtures/valid_policies\n\nAWS.IAM.BetaTest\n [PASS] Root MFA not enabled fails compliance\n [PASS] User MFA not enabled fails compliance\n```\n\nAlternately, the following command will test items with the AnalysisType\n`policy` OR `rule`, AND the severity `High`:\n\n```bash\n$ panther_analysis_tool test --path tests/fixtures/valid_policies --filter AnalysisType=policy,rule Severity=High\n[INFO]: Testing analysis packs in tests/fixtures/valid_policies\n\nAWS.IAM.BetaTest\n [PASS] Root MFA not enabled fails compliance\n [PASS] User MFA not enabled fails compliance\n\nAWS.CloudTrail.MFAEnabled\n [PASS] Root MFA not enabled fails compliance\n [PASS] User MFA not enabled fails compliance\n```\n\nWhen writing policies or rules that refer to the global analysis types, include\nthem in the filter. An empty string as a filter value means the filter applies\nonly if the field exists. The following command returns an error: the policy\nimports a global, but the global lacks a severity and thus is excluded by the\nfilter.\n\n```bash\n$ panther_analysis_tool test --path tests/fixtures/valid_policies --filter AnalysisType=policy,global Severity=Critical\n[INFO]: Testing analysis packs in tests/fixtures/valid_policies\n\nAWS.IAM.MFAEnabled\n [ERROR] Error loading module, skipping\n\nInvalid: tests/fixtures/valid_policies/example_policy.yml\n No module named 'panther'\n\n[ERROR]: [('tests/fixtures/valid_policies/example_policy.yml', ModuleNotFoundError(\"No module named 'panther'\"))]\n```\n\nFor this query to work, allow for the abscence of the severity field:\n\n```bash\n$ panther_analysis_tool test --path tests/fixtures/valid_policies --filter AnalysisType=policy,global Severity=Critical,\"\"\n[INFO]: Testing analysis packs in tests/fixtures/valid_policies\n\nAWS.IAM.MFAEnabled\n [PASS] Root MFA not enabled fails compliance\n [PASS] User MFA not enabled fails compliance\n```\n\nFilters work for the `zip` and `upload` commands in the exact same way they work\nfor the `test` command.\n\nIn addition to filtering, setting a minimum number of unit tests is possible\nwith the --minimum-tests flag. Detections lacking the minimum number of tests\nare considered failing. If `--minimum-tests` is set to 2 or greater, the\nrequirement becomes that at least one test must return `True` and another must\nreturn `False`.\n\n```\n$ panther_analysis_tool test --path tests/fixtures/valid_policies --minimum-tests 2\n% panther_analysis_tool test --path okta_rules --minimum-tests 2\n[INFO]: Testing analysis packs in okta_rules\n\nOkta.AdminRoleAssigned\n [PASS] Admin Access Assigned\n\nOkta.BruteForceLogins\n [PASS] Failed login\n\nOkta.GeographicallyImprobableAccess\n [PASS] Non Login\n [PASS] Failed Login\n\n--------------------------\nPanther CLI Test Summary\n Path: okta_rules\n Passed: 0\n Failed: 3\n Invalid: 0\n\n--------------------------\nFailed Tests Summary\n Okta.AdminRoleAssigned\n ['Insufficient test coverage, 2 tests required but only 1 found.', 'Insufficient test coverage: expected at least one passing and one failing test.']\n\n Okta.BruteForceLogins\n ['Insufficient test coverage, 2 tests required but only 1 found.', 'Insufficient test coverage: expected at least one passing and one failing test]\n\n Okta.GeographicallyImprobableAccess\n ['Insufficient test coverage: expected at least one passing and one failing test.']\n```\n\nIn this case, even though the rules passed all their tests, they are still\nconsidered failing because they do not have the correct test coverage.\n\n### Delete Rules, Policies, or Saved Queries\n\n```bash\n$ panther_analysis_tool delete\n\nusage: panther_analysis_tool delete [-h] [--no-confirm] [--athena-datalake] [--api-token API_TOKEN] [--api-host API_HOST] [--aws-profile AWS_PROFILE] [--analysis-id ANALYSIS_ID [ANALYSIS_ID ...]]\n [--query-id QUERY_ID [QUERY_ID ...]]\n\nDelete policies, rules, or saved queries from a Panther deployment\n\noptional arguments:\n -h, --help show this help message and exit\n --no-confirm Skip manual confirmation of deletion (default: False)\n --athena-datalake Instance DataLake is backed by Athena (default: False)\n --api-token API_TOKEN\n The Panther API token to use. See: https://docs.panther.com/api-beta (default: None)\n --api-host API_HOST The Panther API host to use. See: https://docs.panther.com/api-beta (default: None)\n --aws-profile AWS_PROFILE\n The AWS profile to use when updating the AWS Panther deployment. (default: None)\n --analysis-id ANALYSIS_ID [ANALYSIS_ID ...]\n Space separated list of Detection IDs (default: [])\n --query-id QUERY_ID [QUERY_ID ...]\n Space separated list of Saved Queries (default: [])\n```\n\nPass a space-separated list of Analysis IDs (RuleID or PolicyID) or QueryIDs.\nUse the --no-confirm flag to bypass confirmation prompts. Rules and their\nassociated saved queries will be matched and deleted. The default configuration\ntargets a Snowflake datalake; for an Athena datalake, use the --athena-datalake\nflag.\n\n## Configuration File\n\nPanther Analysis Tool will also read options from a configuration file\n`.panther_settings.yml` in the current working directory. An example\nconfiguration file is included in this repo,\n[example_panther_config.yml](example_panther_config.yml), that contains example\nsyntax for supported options.\n\nOptions in the configuration file take precedence over command-line options. For\ninstance, if minimum_tests: 2 is set in the configuration file and\n--minimum-tests 1 is specified on the command line, the minimum number of tests\nwill be 2.\n\n## Contributing\n\nAll contributions are welcome. Prior to submitting pull requests, consult the\n[contributing guidelines](https://github.com/panther-labs/panther-analysis/blob/master/CONTRIBUTING.md).\nFor steps to open a pull request from a fork, refer to\n[GitHub's guide](https://docs.github.com/en/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request).\n\n### Local Development\n\nTo develop with the panther_analysis_tool locally, prepare two repositories:\nthis one and another containing the panther analysis content for PAT testing.\n\nFrom your [panther_analysis](https://github.com/panther-labs/panther-analysis)\ncontent repository, install as editable (and test, for example):\n\n```bash\npipenv install --editable ../relative/path/to/panther_analysis_tool\npipenv run panther_analysis_tool test\n```\n\n## License\n\nThis repository is licensed under the AGPL-3.0\n[license](https://github.com/panther-labs/panther-analysis/blob/master/LICENSE).\n",
"bugtrack_url": null,
"license": "AGPL-3.0",
"summary": "Panther command line interface for writing, testing, and packaging policies/rules.",
"version": "0.48.0",
"project_urls": {
"Download": "https://github.com/panther-labs/panther_analysis_tool/archive/v0.48.0.tar.gz",
"Homepage": "https://github.com/panther-labs/panther_analysis_tool"
},
"split_keywords": [
"security",
" cli"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "fb1ddbde32e4943083582d8ad2ff16a0d68720152002295062470426f9fcf6b4",
"md5": "1b992c2b3fab2cb87ce064771e0bcedb",
"sha256": "220b9f8dfb7780854f756b4886e62d26ac28f7afb21e745786bdedef7cf6cd2b"
},
"downloads": -1,
"filename": "panther_analysis_tool-0.48.0.tar.gz",
"has_sig": false,
"md5_digest": "1b992c2b3fab2cb87ce064771e0bcedb",
"packagetype": "sdist",
"python_version": "source",
"requires_python": null,
"size": 118973,
"upload_time": "2024-04-30T22:03:43",
"upload_time_iso_8601": "2024-04-30T22:03:43.267772Z",
"url": "https://files.pythonhosted.org/packages/fb/1d/dbde32e4943083582d8ad2ff16a0d68720152002295062470426f9fcf6b4/panther_analysis_tool-0.48.0.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-04-30 22:03:43",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "panther-labs",
"github_project": "panther_analysis_tool",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"requirements": [],
"lcname": "panther-analysis-tool"
}
JSON
