Skip to content
This repository has been archived by the owner on Nov 16, 2023. It is now read-only.

Added AH query, identify accounts logged on to endpoints affected by cobalt strike #145

Merged
merged 7 commits into from
Jun 14, 2020

Conversation

martyav
Copy link
Contributor

@martyav martyav commented May 14, 2020

I'm an internal contributor, tasked with adding AH queries from TA reports.

Before I get too far in, I wanted to get a review.

This file covers a query that identifies accounts logged on to endpoints affected by cobalt strike

identify accounts logged on to endpoints affected by cobalt strike
@martyav martyav changed the title first example Added AH query, identify accounts logged on to endpoints affected by cobalt strike May 14, 2020
Copy link
Collaborator

@tali-ash tali-ash left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for contributing !

Currently this query will run on MDATP only(DeviceAlertEvents exist only in MDATP), can you please adjust it to work on MTP as well using the tables: AlertInfo and AlertEvidence?

Can you please add time limit to the query? for example | where Timestamp > ago(7d)

In addition, can you please put it in the folder of Credential access, which I saw this is the technique it represents :)

@martyav
Copy link
Contributor Author

martyav commented May 27, 2020

@tali-ash Thanks for the review. I was out for a week, so didn't see until today. I just pushed a commit that should address the changes requested.

@lomayor
Copy link
Contributor

lomayor commented May 27, 2020

@endisphotic, @tali-ash, Marty is helping add the threat analytics queries to this repo, but might need your help adjust the queries as necessary.

Copy link
Collaborator

@tali-ash tali-ash left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @martyav , I made some changes to the query, updated the file itself, this is how it should be written as I understand, please review it before I am inserting into master.

Copy link
Contributor Author

@martyav martyav left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the review. It looks good -- other queries in the older docs I am drawing upon will probably need similar updates

@martyav
Copy link
Contributor Author

martyav commented Jun 4, 2020

@lomayor I updated the file to replace "Ploty" with "Cosipor"

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants