Cortex Analyzers Repository
Go to file
2020-06-30 11:29:30 +02:00
.github Update issue templates 2019-02-16 21:56:55 +01:00
analyzers rename Lis_GetReport to LastInfoSec 2020-06-27 10:27:37 +02:00
docs automatically build documentation 2020-06-19 10:43:22 +02:00
images update for Cortex 2 2018-06-07 04:15:59 +02:00
responders Merge pull request #766 from hariomenkel/master 2020-06-26 17:31:41 +02:00
thehive-templates rename Lis_GetReport to LastInfoSec 2020-06-27 10:25:18 +02:00
utils handle and display error output content and messages 2019-04-24 00:28:52 +08:00
.drone.yml #587 test purpose 2020-06-30 11:29:30 +02:00
.gitignore add VSCode file in gitignore 2019-03-17 17:27:49 +01:00
AUTHORS fix authors 2019-06-02 09:59:02 +02:00
CHANGELOG.md add version to Changelog 2020-06-19 11:19:10 +02:00
code_of_conduct.md add code of conduct 2017-06-14 11:40:22 -04:00
COMPONENTS add COMPONENTS file 2017-01-30 19:14:06 +01:00
LICENSE AGPL license 2017-01-30 18:26:07 +01:00
README.md Update links on cortexutils README and setup.py files 2017-12-20 11:12:20 +01:00

The following repository is used by TheHive Project to develop and store Cortex analyzers.

Analyzers can be written in any programming language supported by Linux such as Python, Ruby, Perl, etc. Refer to the How to Write and Submit an Analyzer page for details on how to write and submit one.

To configure analyzers, please read the Cortex Analyzer Requirements Guide.

License

Unless specified otherwise, analyzers are released under the AGPL (Affero General Public License).

If an analyzer is released by its author under a different license, the subfolder corresponding to it will contain a LICENSE file.

Updates

Information, news and updates are regularly posted on TheHive Project Twitter account and on the blog.

Contributing

We welcome your contributions for new analyzers that can take away the load off overworked fellow analysts or improvements to existing ones. Please feel free to fork the code, play with it, make some patches and send us pull requests using issues.

Important: To make it easy for every one, please send one pull request per analyzer. It will help us reviewing the code, and merging as soon as feasible.

We do have a Code of conduct. Make sure to check it out before contributing.

Support

if you encounter an issue with an analyzer or would like to request a new one or an improvement to an existing analyzer, please open an issue on the analyzers' dedicated GitHub repository.

Alternatively, if you need to contact the project team, send an email to support@thehive-project.org.

Community Discussions

We have set up a Google forum at https://groups.google.com/a/thehive-project.org/d/forum/users. To request access, you need a Google account. You may create one using a Gmail address or without one.

Website

https://thehive-project.org/