-
Notifications
You must be signed in to change notification settings - Fork 232
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
Mapping azure_sentinel UDI connector #710
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #710 +/- ##
===========================================
- Coverage 63.32% 63.30% -0.02%
===========================================
Files 425 425
Lines 36805 36834 +29
===========================================
+ Hits 23306 23318 +12
- Misses 13499 13516 +17
Continue to review full report at Codecov.
|
}, | ||
"cloudAppStates": { | ||
"destinationServiceName": { | ||
"key": "x-msazure-sentinel-alert.cloudAppStates.destinationServiceName", | ||
"object": "alert" | ||
"key": "x-ibm-finding.dst_application_ref.name", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any reference mappings in the to-stix file should point to the actual object. Using a sourceip
mapping as an example:
"sourceip": [
{
"key": "ipv4-addr.value",
"object": "src_ip"
},
{
"key": "network-traffic.src_ref",
"object": "nt",
"references": "src_ip"
},
So destinationServiceName
should be creating a software:name
entry and a reference to the software object from the x-ibm-finding
object.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
stix-shifter/stix_shifter_modules/azure_sentinel/stix_translation/json/to_stix_map.json
Line 48 in 39666c3
"destinationServiceName": [ |
I added this
"destinationServiceName": [
{
"key":"software.name",
"object":"software"
},
{
"key":"x-ibm-finding.dst_application_ref",
"object":"finding",
"references":"software"
}
],
does that make sense?
"object": "finding" | ||
}, | ||
{ | ||
"key": "x-oca-event.outcome", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
would outcome and category be the same value in x-oca-event?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I removed x-oca-event.outcome
stix_shifter_modules/azure_sentinel/stix_translation/json/from_stix_map.json
Show resolved
Hide resolved
stix_shifter_modules/azure_sentinel/stix_translation/json/from_stix_map.json
Show resolved
Hide resolved
stix_shifter_modules/azure_sentinel/stix_translation/json/from_stix_map.json
Show resolved
Hide resolved
stix_shifter_modules/azure_sentinel/stix_translation/json/from_stix_map.json
Show resolved
Hide resolved
"key": "x-msazure-sentinel-alert.closedDateTime", | ||
"object": "alert" | ||
"key": "x-ibm-finding.closedDateTime", | ||
"object": "finding" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think closedDateTime
should be mapped to last_observed
"closedDateTime": {
"key": "last_observed",
"cybox": false
}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also remove last_observed
from eventDateTime
field and make it like this-
"eventDateTime": {
"key": "first_observed",
"cybox": false
}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed, see
stix-shifter/stix_shifter_modules/azure_sentinel/stix_translation/json/to_stix_map.json
Line 39 in 59997e2
"closedDateTime":{ |
stix-shifter/stix_shifter_modules/azure_sentinel/stix_translation/json/to_stix_map.json
Line 2 in 59997e2
"eventDateTime": [ |
"key": "x-msazure-sentinel-alert.closedDateTime", | ||
"object": "alert" | ||
"key": "x-ibm-finding.closedDateTime", | ||
"object": "finding" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also remove last_observed
from eventDateTime
field and make it like this-
"eventDateTime": {
"key": "first_observed",
"cybox": false
}
stix_shifter_modules/azure_sentinel/stix_translation/json/to_stix_map.json
Show resolved
Hide resolved
@JingqiuDu can you please resolve the conflicts? |
stix_shifter_modules/azure_sentinel/stix_translation/json/from_stix_map.json
Outdated
Show resolved
Hide resolved
stix_shifter_modules/azure_sentinel/stix_translation/json/from_stix_map.json
Outdated
Show resolved
Hide resolved
"key": "x-oca-event.category", | ||
"object": "event" | ||
} | ||
], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks redundant to map category
to both x-ibm-finding and x-oca-event object
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, it should be removed from the finding object and left with the event object.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
59997e2
to
bd9b787
Compare
conficts resovled |
stix_shifter_modules/azure_sentinel/stix_translation/json/to_stix_map.json
Outdated
Show resolved
Hide resolved
9c9b507
to
c6ef67a
Compare
No description provided.