Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update RBA API Output #379

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Update RBA API Output #379

wants to merge 1 commit into from

Conversation

pyth0n1c
Copy link
Contributor

@pyth0n1c pyth0n1c commented Mar 8, 2025

Make sure that relevant/required fields are included in the detections.json API object

of fields in new dumped
rba object json
}
if self.rba is not None:
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since these are encoded in individual risk_objects, I do not believe they should be included at a high-level for the entire RBA section anymore.

@@ -11,6 +11,23 @@
RiskScoreValue_Type = Annotated[int, Field(ge=1, le=100)]


def risk_score_to_severity(num: int) -> RiskSeverity:
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If risk_severity needs to exist both for individual risk_objects AND at a high level for the entire RBA section, then this should be broken out here so it can be re-used.
It is also used in the savedsearches.conf dump logic here:

action.notable.param.severity = {{ detection.rba.severity }}

Is this a required field that MUST still be present in savedsearches.conf?

@@ -39,6 +40,7 @@ def writeDetections(
"id",
"description",
"tags",
"rba",
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Make sure that the RBA field is written when a detection is dumped to JSON.

@pyth0n1c pyth0n1c marked this pull request as draft March 20, 2025 22:02
@pyth0n1c
Copy link
Contributor Author

After discussing with relevant team(s), this PR will likely be closed out in favor of another that implements the relevant changes.
We will keep this open until that point for documentation purposes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant