Version 3.1.0

Policies, policies, policies! This is our first feature release since launching the Toolkit onto GitHub. From today, you can describe Prevention and Response policies in your Falcon tenant, export them to JSON, and re-import them again (e.g., to a new tenant). This can help MSSPs who have a 'known good' configuration that they would like to replicate over to another customer.

Let us know how you use it and feel free to open up an issue if you encounter any issues!

We have also bumped up dependencies across the board to bring in fixes in Caracara, FalconPy, and several other libraries that this project uses (and is hugely grateful for!).

What's Changed

• Fix minor typo on README by @lautriv in #24
• Bump pytest from 7.2.0 to 7.2.1 by @dependabot in #28
• Bump pydocstyle from 6.2.2 to 6.3.0 by @dependabot in #26
• Bump pylint from 2.15.9 to 2.15.10 by @dependabot in #27
• Bump cryptography from 39.0.0 to 39.0.1 by @dependabot in #31
• Bump cmd2 from 2.4.2 to 2.4.3 by @dependabot in #29
• Bump pylint from 2.15.10 to 2.16.1 by @dependabot in #30
• Policy Describe/Import/Export by @ChristopherHammond13 in #12

New Contributors

• @lautriv made their first contribution in #24

Full Changelog: v3.0.2...v3.1.0

Version 3.0.2

This patch release of Falcon Toolkit includes fixes for #11 and #20, as well as some better README content. There is also a significant bump in dependency versions to keep up to date with the latest security and feature patches up and down the stack.

We recommend that all users upgrade to this version as soon as possible to get these fixes.

Version 3.0.1

This release contains a minor update to address #5, as well as some fixes in #7 which should improve how the project appears on PyPI.

Version 3.0.0: First Public Release!

This release brings Falcon Toolkit to the world. The public release has been given a major version number bump to ensure that it does not conflict with any other versions of the Toolkit used internally within CrowdStrike, and from this version we will be moving internally to tracking the public repository.

Let us know how this first public release supports your use cases, and we look forward to adding lots more features in the coming months!

- Chris Hammond and the CrowdStrike IR Team