-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Create Suspicious_Access_Attempt_to_the_cert Windows_Share_Possible_C… #5073
base: master
Are you sure you want to change the base?
Conversation
…ertipy_Activity.yaml
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.
Welcome @NinnessOtu 👋
It looks like this is your first pull request on the Sigma rules repository!
Please make sure to read the SigmaHQ conventions document to make sure your contribution is adhering to best practices and has all the necessary elements in place for a successful approval.
Thanks again, and welcome to the Sigma community! 😃
Hey @NinnessOtu and thanks for your contribution. Please provide logs evidence for EID 5145 as well as better context for why this is interesting to look for by providing perhaps actually references to blogs or sandboxes that made use of this technique. |
hello @nasbench For example, when running the following command:
The output (from Certipy v4.8.2 by Oliver Lyak) provides details of the connection process:
Here are the logs :
|
This rule detects attempts to access the Windows share IPC with the specific target name "cert," which could indicate unauthorized certificate requests. This behavior has been linked to tools such as Certipy.