Tune and complete risk/observable matching feature

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
security

Research direction

Start by locating the existing risk message validation code and the beginnings of the risk-event-to-observable matching code. Trace how those paths are exercised and determine the expected matching behavior before making changes. Done means the observable-matching feature is complete alongside risk message validation, but the issue does not define narrower acceptance criteria.

Written by the indexing model from the issue text.

Description

  • Alongside risk message validation we added the beginnings of some code which can match risk events against observables
  • We should complete this feature
Dominant language
Python
Stars
139
Forks
52
Avg merge
1h 16m
Merged PRs (30d)
3

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.

More from splunk/contentctl

All issues in splunk/contentctl

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.