splunk / splunk/contentctl

The "User Name" type should map to a "user" risk object and not "other"

Open
#246 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Python
Stars
139
Forks
52
Avg merge
1h 16m
Merged PRs (30d)
3

Description

  • In detection_abstract.py we look for observable of type username
  • In practice, the valid type (see SES_OBSERVABLE_TYPE_MAPPING) is User Name; Username/username is invalid and static validation does not allwo for these values
  • This is causing a handful of detections to create risk objects of type other instead of type user
  • Additionally, device is not a valid observable type per SES_OBSERVABLE_TYPE_MAPPING (used in validation)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review detection_abstract.py alongside SES_OBSERVABLE_TYPE_MAPPING and the static validation that uses it; confirm the accepted observable names for User Name and device. Verify that detections using User Name produce a user risk object rather than other, and that device handling agrees with the valid observable types.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
security
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.