-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Sensor SSH Cowrie solution #11155
base: master
Are you sure you want to change the base?
Sensor SSH Cowrie solution #11155
Conversation
As part of Hackathon 2024 a team developed a 1 click deploy solution that will deploy a debain vm, install cowrie, create ama dcr, dce, and association, and create a custom table to collect cowrie events. Solution contains a workbook (under development), 1 parser and 5 detection rules . The goal is make this a framework for others and community to create other 1 click deploy for other types of interactive honeypots. Can be used publicly for TI or privately as a detection tripwire
fixing yaml spacing intial validation tests failed.
added workbook and fixing parser yaml
fixed some kql, data connector, workbook validation errors, still researching the permissions on data connector does not match.
made a change to fix kql validation removing commas after each extend and new line | extend, also removed txt based parser.
added vm ext ama for linux in deployment.
fixing detections validation error SourceIP custom colum name to sentinel recognized field Address
minor fixes to validation errors
minor fix filehash
added algo identifier
created new kql validator for cowrie
added | extend for beinging of query line 25
updated deploy to azure button links and data connector permissions reqs
changes to data connector to pass kql validations
create a custom sample data for Sensor SSH Cowrie solution.
Hi @swiftsolves-msft,
|
[like] Nathan Swift reacted to your message:
…________________________________
From: v-atulyadav ***@***.***>
Sent: Thursday, November 7, 2024 7:12:15 AM
To: Azure/Azure-Sentinel ***@***.***>
Cc: Nathan Swift ***@***.***>; Mention ***@***.***>
Subject: Re: [Azure/Azure-Sentinel] Sensor SSH Cowrie solution (PR #11155)
Hi @swiftsolves-msft<https://github.com/swiftsolves-msft>,
We require a few modifications to the PR before proceeding with packaging.
1. The Name property of the data file is currently set to Cowrie, whereas it should be designated as Sensor SSH Cowrie.
image.png (view on web)<https://github.com/user-attachments/assets/feb2fed6-c8f4-47b6-bacc-9527a7cef7b4>
1. It is also necessary to include workbook metadata in the workbookmetadata.json file
(https://github.com/Azure/Azure-Sentinel/blob/master/Workbooks/WorkbooksMetadata.json)
—
Reply to this email directly, view it on GitHub<#11155 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AHIYRC3ADYI2UEY37KJXE7TZ7MHE7AVCNFSM6AAAAABOQYQ4WKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRRGQ4DANZZGA>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
change solution name to match and added workbook metadata in
update images for preview for workbook
Hi @swiftsolves-msft, |
Hi @swiftsolves-msft, |
Hi @swiftsolves-msft, |
Hi @swiftsolves-msft, |
Many thanks this is ongoing may be working with sreedharande on the packaging tool as noted I was running into errors when using the tool. Working on this week to get updated with new PR once data package tool succeeds. |
Hi @swiftsolves-msft, |
Hi @swiftsolves-msft, |
Hi @swiftsolves-msft, |
Hi @swiftsolves-msft, |
As part of Hackathon 2024 a team developed a 1 click deploy solution that will deploy a debain vm, install cowrie, create ama dcr, dce, and association, and create a custom table to collect cowrie events. Solution contains a workbook (under development), 1 parser and 5 detection rules . The goal is make this a framework for others and community to create other 1 click deploy for other types of interactive honeypots. Can be used publicly for TI or privately as a detection tripwire
Required items, please complete
Change(s):
Reason for Change(s):
Version Updated:
Testing Completed:
Checked that the validations are passing and have addressed any issues that are present:
Guidance <- remove section before submitting
Before submitting this PR please ensure that you have read the following sections and filled out the changes, reason for change and testing complete sections:
Thank you for your contribution to the Microsoft Sentinel Github repo.
Change(s):
Reason for Change(s):
Version updated:
Testing Completed:
Note: If updating a detection, you must update the version field.
Checked that the validations are passing and have addressed any issues that are present:
Note: Let us know if you have tried fixing the validation error and need help.