-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Test #11326
base: test
Are you sure you want to change the base?
Test #11326
Conversation
Updated Entity mappings of analytical rules
There was a bug where if you had already instantiated something named "RecordedFuture-ConnectorV2" then it would use that, instead of asking you to create a new API connection for sandbox.
Update ingestASimSampleData.py and runAsimSchemaAndDataTesters.yaml
…vin/cp_syslog_config To not change SELinux context we should not move the syslog conf file.
…tivityCombine Updated and Combined data connector of Armis Alerts and Armis Activities to ingest activities associated with each alerts.
Update Anomalous Sign-in Activity.yaml
…date Iboss ama boolean update
Fix data connector title.
Solution Skeleton Structure
…tionUpdate Recorded future solution update
Merge MDTI-Actor-Lookup into playbooks folder
…2-more-analytic-rules Added more analytic rules, modified existing queries, changed alerttype
Repackaged for updated in Analytical Rule
@Kingwins007 please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
Hello @Kingwins007, If this is a test PR could you please move it to Draft state |
Moving the PR to draft since this seems to be raised for testing purpose and no action from author from 2 weeks. |
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.