-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Google chrome pack #27619
Merged
Merged
Google chrome pack #27619
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ng convention of the rules files
…correlation rules and the version of the dashboard
…correlation rules and the version of the dashboard
Packs/GoogleChrome/CorrelationRules/GoogleChrome_-_Chrome_Extension_Install_Event.yml
Show resolved
Hide resolved
Packs/GoogleChrome/CorrelationRules/GoogleChrome_-_Chrome_Extension_Install_Event.yml
Show resolved
Hide resolved
@yasta5 Doc review completed. |
…nsion_Install_Event.yml Co-authored-by: ShirleyDenkberg <62508050+ShirleyDenkberg@users.noreply.github.com>
…nsion_Install_Event.yml Co-authored-by: ShirleyDenkberg <62508050+ShirleyDenkberg@users.noreply.github.com>
eepstain
approved these changes
Nov 9, 2023
sapirshuker
pushed a commit
that referenced
this pull request
Dec 21, 2023
* Create pack for google chrome. * New pack for GoogleChrome * Remove author image. * modify googlechrome modeling rule * Adding parsing rule * Added fields to schema * Added readme content * Creating dashboard for google chrome pack, and modifying the schema file * Added correlation rules * Fix correlation rules and fix product in parsing rule. * Added correlation rule. * Updated yml file of parsing rule * Updated dashboard file. * Add from version to dashboard. * Changed rule xif * Changed the from version for modeling and parsing yml * Added fromversion: 6.10.0 to the correlation rules and fixed the naming convention of the rules files * Modified the parsing rules. * Add tags to readme file. * Updated the version of the yml file of the rules, the version of the correlation rules and the version of the dashboard * Updated the version of the yml file of the rules, the version of the correlation rules and the version of the dashboard * updated google chrome dashboard * Update Packs/GoogleChrome/CorrelationRules/GoogleChrome_-_Chrome_Extension_Install_Event.yml Co-authored-by: ShirleyDenkberg <62508050+ShirleyDenkberg@users.noreply.github.com> * Update Packs/GoogleChrome/CorrelationRules/GoogleChrome_-_Chrome_Extension_Install_Event.yml Co-authored-by: ShirleyDenkberg <62508050+ShirleyDenkberg@users.noreply.github.com> * updated google chrome dashboard and reademe. * Modified the correlation rules. * Added fromversion: 8.4.0 to correlation rules * Fixed issue with parsing rule. --------- Co-authored-by: ShirleyDenkberg <62508050+ShirleyDenkberg@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Contributing to Cortex XSOAR Content
Make sure to register your contribution by filling the contribution registration form
The Pull Request will be reviewed only after the contribution registration form is filled.
Status
Related Issues
fixes: link to the issue
Does it break backward compatibility?