Add JumpCloud API Key v2 detector (jca_ prefix format)

[rootranjan]

Please review the Community Note before submitting

Description

JumpCloud has introduced a new API key format with a jca_ prefix. The existing JumpCloud detector only matches generic 40-character alphanumeric strings when the keyword "jumpcloud" is nearby, which can lead to false positives and miss keys that don't have contextual keywords.

The new format is: 40 characters total (jca_ prefix + 36 alphanumeric characters)
Example: jca_aBcDeFgHiJkLmNoPqRsTuVwXyZ123456

Preferred Solution

Add a v2 detector for JumpCloud that:

1. Detects the new jca_ prefixed API key format
2. Uses the same verification endpoint (https://console.jumpcloud.com/api/v2/systemgroups)
3. Implements the Versioner interface alongside the existing v1 detector
4. Includes false positive filtering (only digits/letters, sequential patterns, low entropy)

Key Format

• Total length: 40 characters
• Prefix: jca_ (4 characters)
• Key part: 36 alphanumeric characters
• Pattern: jca_[a-zA-Z0-9]{36}
• Keywords: jca_ (self-identifying, no context needed)

Additional Context

• JumpCloud hosts data (user/device management, IAM)
• Has paid services (enterprise directory platform)
• The jca_ prefix makes the key self-identifying, reducing false positives significantly
• Verification can use the existing API endpoint with x-api-key header

References

• JumpCloud API Docs: https://docs.jumpcloud.com/api/
• JumpCloud API Key Support: https://jumpcloud.com/support/jumpcloud-apis
• Existing detector: `/pkg/detectors/jumpcloud/

[shahzadhaider1]

Hi there!

Thank you for taking the time to open this issue and the PR, we really appreciate your contribution to the project!
We’ll take a look and get back to you as soon as we can.

Thanks again for helping make this project better!

[mangod12]

I've submitted a PR to implement this: #4975