-
Notifications
You must be signed in to change notification settings - Fork 7
Examples modification v2 #45
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: main
Are you sure you want to change the base?
Examples modification v2 #45
Conversation
Signed-off-by: Micah Pegman <mpegman@octolabs.io> Signed-off-by: Cristian Vasilica <cvasilica@secureworks.com>
replaced tenant_id with tenant.id as per JIRA SECOPS-1646 Signed-off-by: Cristian Vasilica <cvasilica@secureworks.com>
replaced tenant_id with tenant.id as per JIRA SECOPS-1646 Signed-off-by: Cristian Vasilica <cvasilica@secureworks.com>
replaced tenant_id with tenant.id as per JIRA SECOPS-1646 Signed-off-by: Cristian Vasilica <cvasilica@secureworks.com>
Signed-off-by: Cristian Vasilica <cvasilica@secureworks.com>
replaced tenant_id with tenant.id as per JIRA SECOPS-1646 Signed-off-by: Cristian Vasilica <cvasilica@secureworks.com>
c628093 to
fb12436
Compare
mpegman-scwx
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.
@cvasilica tenant_id as a results field from Taegis has not completely gone away. Only Alerts has deprecated this field in favor of a TenantV4 object.
| add_threat_intel, | ||
| correlations=[get_ti_pubs], | ||
| tenant_id=TENANT, | ||
| tenant.id=TENANT, |
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 believe this will still be tenant_id as it is the function parameter and not a parsed column from a result set.
https://github.com/secureworks/taegis-magic/blob/main/taegis_magic/pandas/context.py#L492
| " add_threat_intel,\n", | ||
| " correlations=[get_ti_pubs],\n", | ||
| " tenant_id=TENANT,\n", | ||
| " tenant.id=TENANT,\n", |
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 believe this will still be tenant_id as it is the function parameter and not a parsed column from a result set.
https://github.com/secureworks/taegis-magic/blob/main/taegis_magic/pandas/context.py#L492
| "This pandas pipe function will work when there are the following columns in the DataFrame:\n", | ||
| "- A column name that contains `host_id`\n", | ||
| "- A column name that contains `tenant.id` (or `tenant_id`)\n", | ||
| "- A column name that contains `tenant.id`\n", |
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.
The dual column lookup is still correct. Events still use tenant_id, it was alerts that deprecated the tenant_id string in favor of a Tenant object.
Event schemas can be verified using the following snippet, change the RuleEventType to one of the options here:
from taegis_sdk_python import GraphQLService
from taegis_sdk_python.services.rules.types import RuleEventType
service = GraphQLService()
results = service.rules.query.filter_keys(RuleEventType.PROCESS)
print(results)https://github.com/secureworks/taegis-magic/blob/main/taegis_magic/pandas/assets.py#L124
| "#### Asset Data with Taegis Events\n", | ||
| "\n", | ||
| "- Unlike Alert DataFrames, Taegis Event DataFrames only need the `tenant_id` and `host_id` fields" | ||
| "- Unlike Alert DataFrames, Taegis Event DataFrames only need the `tenant.id` and `host_id` fields" |
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.
Events still use the tenant_id string.
| " 'enrichSummary',\n", | ||
| " 'host_id',\n", | ||
| " 'tenant_id'\n", | ||
| " 'tenant.id'\n", |
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.
Events still use the tenant_id string.
| " add_threat_intel,\n", | ||
| " correlations=[get_ti_pubs],\n", | ||
| " tenant_id=TENANT,\n", | ||
| " tenant.id=TENANT,\n", |
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 believe this will still be tenant_id as it is the function parameter and not a parsed column from a result set.
https://github.com/secureworks/taegis-magic/blob/main/taegis_magic/pandas/context.py#L492
Closes #44