-
Notifications
You must be signed in to change notification settings - Fork 233
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
AWS GuardDuty UDI Connector #1525
AWS GuardDuty UDI Connector #1525
Conversation
SharmilaMS-Hcl
commented
Jul 11, 2023
- Added files for AWS GuardDuty UDI Connector module
- Added the following files related to PR Framework Changes for Handling Nested List of Dictionaries #1516 to avoid CI failures.
- json_to_stix_translator.py
- gcp chronicle Read me, to-stix and unit test case files
- Reaqta unit test case file.
- Updated stix_shifter.py file for handling serialization failure of datetime.datetime object.
1. Added files for AWS GuardDuty UDI Connector module 2. Added the following files related to PR opencybersecurityalliance#1516 to avoid CI failures. 1. json_to_stix_translator.py 2. gcp chronicle Read me, to-stix and unit test case files 3. Reaqta unit test case file. 3. Updated stix_shifter.py file for handling serialization failure of datetime.datetime object.
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## develop #1525 +/- ##
===========================================
+ Coverage 85.32% 85.55% +0.22%
===========================================
Files 672 682 +10
Lines 54088 55564 +1476
===========================================
+ Hits 46152 47536 +1384
- Misses 7936 8028 +92
☔ View full report in Codecov by Sentry. |
}, | ||
"detector_ids": { | ||
"label": "Detector Ids", | ||
"description": "Detector id of the GuardDuty" |
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.
Description needs to be more clear. According to this comment #1516 (comment)
You may have to show an example of how to specify the ids.
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.
Updated the description of the detector id with an example.
Updated file with detailed description for Detector Ids
stix_shifter_modules/aws_guardduty/stix_translation/json/to_stix_map.json
Outdated
Show resolved
Hide resolved
stix_shifter_modules/aws_guardduty/stix_translation/json/to_stix_map.json
Outdated
Show resolved
Hide resolved
stix_shifter_modules/aws_guardduty/stix_translation/json/stix_2_1/to_stix_map.json
Outdated
Show resolved
Hide resolved
stix_shifter_modules/aws_guardduty/stix_translation/json/stix_2_1/to_stix_map.json
Outdated
Show resolved
Hide resolved
}, | ||
"AccountId": [ | ||
{ | ||
"key": "x-aws.account_id", |
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.
all the x-aws
mappings can go under x-aws-resource
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.
Basically, x-aws-resource has been used to map the affected resources in the finding. Since account id and region are related to AWS cloud subscription and common to all findings, these fields are mapped under separate object x-aws. Kindly let us know, your comments in this.
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 its unnecessary to create x-aws
object just for accounts. Account information are basically related to aws resources so I think x-aws-resource
should be the right object unless there are multiple account ids mapped.
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.
Updated the mappings as suggested.
1. Removed Cybox attribute from the to-stix file. 2. Updated supported Stix mappings.
Updated the mapping files, unit test cases, read me and supported stix files by modifying account id and region related details to x-aws-resource.