Skip to content

Releases: splunk/contentctl

v5.5.9

09 Oct 21:53
093d75b

Choose a tag to compare

What's Changed

Full Changelog: v5.5.8...v5.5.9

v5.5.8

30 Jul 19:12
7ea8ffb

Choose a tag to compare

With these changes, integration testing can run much faster!
This also fixes a "bug" related to capitalization of datasources in the escu analytic onboarding assistant.
We also update our ruff configs and some dependencies.

What's Changed

Full Changelog: v5.5.7...v5.5.8

v5.5.7

07 Jul 16:33
52647b7

Choose a tag to compare

Minor update to Playbooks type

What's Changed

  • Add additional use cases and missing D3FEND techniques by @ccl0utier in #418

New Contributors

Full Changelog: v5.5.6...v5.5.7

v5.5.6

20 Jun 18:13
2df94ae

Choose a tag to compare

Generate MITRE Attack Output layer.
Fix a bug intrdocued in tyro v0.0.9.23 where if an extremely large number of files (greater than 530 or so) are passed to mode:selected --mode.files ..., the command line parser crashes.

What's Changed

Full Changelog: v5.5.5...v5.5.6

v5.5.5

13 Jun 16:00
06d84c1

Choose a tag to compare

Added some "allowed macros" to validation because they exist in Enterprise Security.

What's Changed

Full Changelog: v5.5.4...v5.5.5

v5.5.4

10 Jun 17:05
b6b7fcd

Choose a tag to compare

contentctl report has been updated to output MITRE Attack Navigator in the 5.1.0 format.

What's Changed

Full Changelog: v5.5.3...v5.5.4

v5.5.3

19 May 20:48
8877ca0

Choose a tag to compare

What's Changed

  • Catch duplicate analytic stories and other mapped content by @pyth0n1c in #410

Full Changelog: v5.5.2...v5.5.3

v5.5.2

15 May 23:00
226c7f8

Choose a tag to compare

This just bumps the names of the objects generated in dist/api to end in _v2. This is because the detection schema changed slightly, so we want to differentiate them from the old objects.

What's Changed

Full Changelog: v5.5.1...v5.5.2

v5.5.1

06 May 19:41
646f489

Choose a tag to compare

Minor typing changes to a field from str to int

What's Changed

Full Changelog: v5.5.0...v5.5.1

v5.5.0

02 May 22:08
2b633b6

Choose a tag to compare

Most notably, this PR adds support for a cached version of the attack_data repo that is usable during validate and test operations.
This offers a number of distinct advantages in terms of runtime performance and up-front error checking:

  • If attack_data links were incorrect (for example, they link to http/s files that do not exist), then testing could fail at test runtime rather than validation time.
  • Downloading files sometimes fails due to rate limiting from GitHub
  • Attack Data files may be very large (hundreds of MB) and the https://media.githubusercontent endpoint does not compress these files (as it assumes they are media and, thus, already highly compressed)
  • The same attack data file is often downloaded multiple times if it is used by multiple detections

A cache of the https://github.com/splunk/attack_data repo is now hosted and available, compressed with zstd at https://attack-range-attack-data.s3.us-west-2.amazonaws.com/attack_data.tar.zstd. This cache is updated whenever new attack data is merged into the master branch.
This archive includes all of the data in the attack_data/datasets for and is only ~215MB. This makes it a significant improvement over the uncompressed size of all attack data today (about 10GB).

To begin using this data during validation or testing, check out the helptext here:
https://github.com/splunk/contentctl/blob/2b633b6207d028f40908b8d7a618544aaa3876ce/contentctl/objects/config.py#L283-L293

Note that running contentctl validate/build/test with the --verbose flag (such as contentctl validate --verbose) enables even more extended validations of your test data during the validation phase, further reducing chances of a failure to find attack data at runtime.

What's Changed

  • detection_Type and _entities conf file updates by @pyth0n1c in #404
  • Enable Attack Data Download before Test by @pyth0n1c in #392

Full Changelog: v5.4.1...v5.5.0