Thank you.
Thanks for the question kc.
Guard has multiple detections relating to content exfiltration as well as post-exploitation, lateral movement and privileged token use. The audit log provides comprehensive and immutable records about token creation and use, as well as data exports (users, actions, IP/location, etc). In the future, we hope to offer even more complete detections and telemetry around attachment operations to give customers highly detailed insights into these granular actions. We're also pursuing opportunities to create both detections and responses related to our automation platform.
We're always curious and eager to hear about specific detection requests that can help our customers solve problems in their organizations. If you have any detections ideas, please feel free to share them with us.
Thanks @Jeremy Galloway for the response. Am trying to piece out the different features of Guard together to address the above list. Wondering if there's any cheat sheets or sort that explains the objectives of the Guard Features and what it is trying to address?
Detection ideas if i may share and the example below from Palo Alto SSPM solution to detect posture risks in the Atlassian instance or misconfigurations.
Concerns and considerations are, the tool requires an api token, generated by an Atlassian Org Admin. If only Guard offer this capability natively it will be great.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.