Crogl 2.7.1 Release Notes

Crogl 2.7.1 connects Darktrace, ends a conversation that has stopped making progress instead of leaving it running, and holds memory steady on a deployment left running for a long time.

What's New

• Connect Darktrace

Detailed Changes

Connect Darktrace

Darktrace is now a supported connector. Point Crogl at a Darktrace deployment and its data joins every investigation and hunt, queried in Darktrace's own format alongside your other connected sources.

Bug Fixes

• A conversation that stops making progress now ends with an error instead of running indefinitely. A turn could previously run until Crogl was restarted, which left a scheduled job appearing to work for as long as it went unnoticed.
• Memory use no longer climbs on a deployment left running for a long time.
• An investigation report's timeline now carries the date on every event, so a timeline spanning more than one day reads unambiguously.
• A GCP service-account connector can now be created without filling in its optional advanced fields. Leaving the token endpoint and scopes empty previously failed with an internal error.
• Outstanding dependency vulnerabilities are remediated.