-
Notifications
You must be signed in to change notification settings - Fork 46
Smart descriptions for Vectra #19
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: feat/vectra_smart_descriptions
Are you sure you want to change the base?
Smart descriptions for Vectra #19
Conversation
events/smart-descriptions.json
Outdated
| } | ||
| ], | ||
| { | ||
| "value": "{observer.ip} detected {vectra.detection.name} : {host.name} ({host.ip})", |
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.
| "value": "{observer.ip} detected {vectra.detection.name} : {host.name} ({host.ip})", | |
| "value": "{observer.ip} detected {vectra.detection.name} on {host.name} ({host.ip})", |
events/smart-descriptions.json
Outdated
| "relationships": [{ | ||
| "source": "host.ip", | ||
| "target": "destination.ip", | ||
| "type": "{vectra.detection.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.
Using a field name / template is not supported for type at the moment. I've opened an issue to support it.
events/smart-descriptions.json
Outdated
| }] | ||
| }, | ||
| { | ||
| "value": "{observer.ip} refreshed detection {vectra.detection.last_type} : {host.name} ({host.ip})", |
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.
| "value": "{observer.ip} refreshed detection {vectra.detection.last_type} : {host.name} ({host.ip})", | |
| "value": "{observer.ip} refreshed detection {vectra.detection.last_type} on {host.name} ({host.ip})", |
events/smart-descriptions.json
Outdated
| }] | ||
| }, | ||
| { | ||
| "value": "[HOST SCORING] {host.name} ({host.ip}) : threat = {vectra.risk_score_norm}", |
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.
Smart Descriptions are supposed to abstract complexity as much as possible. Can't we create a sentence here ?
events/smart-descriptions.json
Outdated
| }], | ||
| }, | ||
| { | ||
| "value": "[LOCKDOWN] {user.name} {action.name} {vectra.account.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.
Smart Descriptions are supposed to abstract complexity as much as possible. Can't we create a sentence here ?
events/smart-descriptions.json
Outdated
| }] | ||
| }, | ||
| { | ||
| "value": "[HOST LOCKDOWN] {user.name} {action.name} {host.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.
Smart Descriptions are supposed to abstract complexity as much as possible. Can't we create a sentence here ?
events/smart-descriptions.json
Outdated
| }] | ||
| }, | ||
| { | ||
| "value": "[CAMPAIGN] event : {vectra.detection.reason} from {source.ip} to {vectra.destination.name} ({destination.ip}) ", |
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.
Smart Descriptions are supposed to abstract complexity as much as possible. Can't we create a sentence here ?
events/smart-descriptions.json
Outdated
| "relationships": [{ | ||
| "source": "source.ip", | ||
| "target": "destination.ip", | ||
| "type": "{vectra.detection.reason}" |
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.
can't use a field name / template as relationship type at the moment
gaelmuller
left a comment
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.
Could you also apply a formatter ?
| "relationships": [{ | ||
| "source": "source.ip", | ||
| "target": "destination.ip", | ||
| "type": "campaign" | ||
| }] |
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.
Not convinced this relationship really makes sense. Note that you can now use variables in relationship type
| "relationships": [{ | ||
| "source": "source.ip", | ||
| "target": "destination.ip", | ||
| "type": "campaign" | ||
| }] |
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.
| "relationships": [{ | |
| "source": "source.ip", | |
| "target": "destination.ip", | |
| "type": "campaign" | |
| }] |
copy paste error ?
| "relationships": [{ | ||
| "source": "source.ip", | ||
| "target": "destination.ip", | ||
| "type": "campaign" | ||
| }] |
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.
| "relationships": [{ | |
| "source": "source.ip", | |
| "target": "destination.ip", | |
| "type": "campaign" | |
| }] |
copy paste error ?
Smart descriptions for the vectra cognito detect intake format