-
Notifications
You must be signed in to change notification settings - Fork 83
Update $lib.stix and fix skipped tests #4649
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
base: synapse-3xx
Are you sure you want to change the base?
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## synapse-3xx #4649 +/- ##
===============================================
+ Coverage 96.68% 96.75% +0.07%
===============================================
Files 252 252
Lines 60709 60709
===============================================
+ Hits 58698 58742 +44
+ Misses 2011 1967 -44
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
|
||
| {'type': (None, 'uses', None), 'storm': 'yield $n1node [ +(used)> { yield $n2node } ]'}, | ||
| {'type': (None, 'indicates', None), 'storm': 'yield $n1node [ +(indicates)> { yield $n2node } ]'}, | ||
| {'type': (None, 'indicates', None), 'storm': 'yield $n1node [ +(refs)> { yield $n2node } ]'}, |
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.
Do we want to add an indicates edge from it:sec:stix:indicator to the model or use something else?
| # Should these just be the smallest .min and largest .max values that the tag has on any node? | ||
| # 'first_seen': '+:seen $seen=:seen return($lib.stix.export.timestamp($seen.0))', | ||
| # 'last_seen': '+:seen $seen=:seen return($lib.stix.export.timestamp($seen.1))', |
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.
Does this make sense? Or should this be something like -> risk:tool:software:tag :used.min/:used.max?
No description provided.