Ctera branch #10889
Closed
Ctera branch #10889
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
|
@microsoft-github-policy-service agree [company="{CTERA}"]
From: microsoft-github-policy-service[bot] ***@***.***>
Sent: July 29, 2024 12:15 PM
To: Azure/Azure-Sentinel ***@***.***>
Cc: Robert Elias ***@***.***>; Mention ***@***.***>
Subject: Re: [Azure/Azure-Sentinel] Ctera branch (PR #10889)
You don't often get email from ***@***.******@***.***>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
@roberteliass<https://github.com/roberteliass> please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]
Options:
* (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
@microsoft-github-policy-service agree
* (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.
@microsoft-github-policy-service agree company="Microsoft"
Contributor License Agreement
Contribution License Agreement
This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your
contributions to Microsoft open source projects. This Agreement is effective as of the latest signature
date below.
1. Definitions.
“Code” means the computer software code, whether in human-readable or machine-executable form,
that is delivered by You to Microsoft under this Agreement.
“Project” means any of the projects owned or managed by Microsoft and offered under a license
approved by the Open Source Initiative (www.opensource.org<http://www.opensource.org/>).
“Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
Project, including but not limited to communication on electronic mailing lists, source code control
systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
discussing and improving that Project, but excluding communication that is conspicuously marked or
otherwise designated in writing by You as “Not a Submission.”
“Submission” means the Code and any other copyrightable material Submitted by You, including any
associated comments and documentation.
2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any
Project. This Agreement covers any and all Submissions that You, now or in the future (except as
described in Section 4 below), Submit to any Project.
3. Originality of Work. You represent that each of Your Submissions is entirely Your original work.
Should You wish to Submit materials that are not Your original work, You may Submit them separately
to the Project if You (a) retain all copyright and license information that was in the materials as You
received them, (b) in the description accompanying Your Submission, include the phrase “Submission
containing materials of a third party:” followed by the names of the third party and any licenses or other
restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
guidelines concerning Submissions.
4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else
for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
Submission is made in the course of Your work for an employer or Your employer has intellectual
property rights in Your Submission by contract or applicable law, You must secure permission from Your
employer to make the Submission before signing this Agreement. In that case, the term “You” in this
Agreement will refer to You and the employer collectively. If You change employers in the future and
desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
and secure permission from the new employer before Submitting those Submissions.
5. Licenses.
* Copyright License. You grant Microsoft, and those who receive the Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
parties.
* Patent License. You grant Microsoft, and those who receive the Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
Your patent claims that are necessarily infringed by the Submission or the combination of the
Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
import or otherwise dispose of the Submission alone or with the Project.
* Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
granted by implication, exhaustion, estoppel or otherwise.
1. Representations and Warranties. You represent that You are legally entitled to grant the above
licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
have disclosed under Section 3). You represent that You have secured permission from Your employer to
make the Submission in cases where Your Submission is made in the course of Your work for Your
employer or Your employer has intellectual property rights in Your Submission by contract or applicable
law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
2. Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
You later become aware that would make Your representations in this Agreement inaccurate in any
respect.
3. Information about Submissions. You agree that contributions to Projects and information about
contributions may be maintained indefinitely and disclosed publicly, including Your name and other
information that You submit with Your Submission.
4. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
defenses of lack of personal jurisdiction and forum non-conveniens.
5. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
supersedes any and all prior agreements, understandings or communications, written or oral, between
the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.
—
Reply to this email directly, view it on GitHub<#10889 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A44VKLZZXY2FYISG6MMZW4LZOYB25AVCNFSM6AAAAABLT3H5F6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJVGQYTIMRXGI>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
|
@microsoft-github-policy-service agree company="CTERA"
From: microsoft-github-policy-service[bot] ***@***.***>
Sent: July 29, 2024 12:23 PM
To: Azure/Azure-Sentinel ***@***.***>
Cc: Robert Elias ***@***.***>; Mention ***@***.***>
Subject: Re: [Azure/Azure-Sentinel] Ctera branch (PR #10889)
You don't often get email from ***@***.******@***.***>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
@roberteliass<https://github.com/roberteliass> the command you issued was incorrect. Please try again.
Examples are:
@microsoft-github-policy-service agree
and
@microsoft-github-policy-service agree company="your company"
—
Reply to this email directly, view it on GitHub<#10889 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A44VKL64TUUKQX73LMFUVCTZOYCXRAVCNFSM6AAAAABLT3H5F6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJVGQZDSNJUHA>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
v-visodadasi
requested changes
Jul 30, 2024
| { | ||
| "Name": "CTERA", | ||
| "Author": "CTERA Networks - [email protected]", | ||
| "Logo": "<img src=\"https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/Solutions/CTERA/Data%20Connectors/Logo/CTERA_Networks_logo.svg\" width=\"75px\" height=\"75px\">", |
There was a problem hiding this comment.
Hello @roberteliass, Logo should be in 'Logos' folder, not 'Solution/Logo'. Please move and update link.
|
Please try to resolve the validation errors from your end. |
|
Hi, responding to each section.
From: ***@***.*** ***@***.***>
Sent: July 30, 2024 12:27 PM
To: Azure/Azure-Sentinel ***@***.***>
Cc: Robert Elias ***@***.***>; Mention ***@***.***>
Subject: Re: [Azure/Azure-Sentinel] Ctera branch (PR #10889)
You don't often get email from ***@***.******@***.***>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
@v-visodadasi requested changes on this pull request.
________________________________
In Solutions/CTERA/Data/Solution_CTERA.json<#10889 (comment)>:
@@ -0,0 +1,26 @@
+{
+ "Name": "CTERA",
+ "Author": "CTERA Networks - ***@***.******@***.***>",
+ "Logo": "<img src=\"https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/Solutions/CTERA/Data%20Connectors/Logo/CTERA_Networks_logo.svg\<https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/Solutions/CTERA/Data%20Connectors/Logo/CTERA_Networks_logo.svg/>" width=\"75px\" height=\"75px\">",
+ "Description": "The CTERA solution allows you to ingest and analyze events from CTERA Edge Filers in Microsoft Sentinel. This solution includes a data connector to collect syslog data from CTERA, analytic rules to detect suspicious activities, hunting queries for threat hunting, and a workbook for data visualization and analysis.\n\n**Data Connectors:** 1, **Analytic Rules:** 2, **Hunting Queries:** 3, **Workbook:** 1\n\n[Learn more about Microsoft Sentinel](https://aka.ms/azuresentinel) | [Learn more about Solutions](https://aka.ms/azuresentinelsolutionsdoc)",
Hello @roberteliass<https://github.com/roberteliass>, Description should not include the list of content.
[RE] – List of content was removed from description
________________________________
In Solutions/CTERA/Data/Solution_CTERA.json<#10889 (comment)>:
+ "Data Connectors/CTERA_Data_Connector.json"
+ ],
+ "Workbooks": [
+ "Workbooks/CTERA_Workbook.json"
+ ],
+ "Analytic Rules": [
+ "Analytic Rules/Ransomware User Blocked.yaml",
+ "Analytic Rules/RansomwareDetected.yaml"
+ ],
+ "Hunting Queries": [
+ "Hunting Queries/MassDeletions.yaml",
+ "Hunting Queries/MassAccessDenied.yaml",
+ "Hunting Queries/MassPermissionChanges.yaml"
+ ],
+ "BasePath": "C:\\GitHub\\Azure-Sentinel\\Solutions\\CTERA",
+ "Version": "1.0.0",
Hello @roberteliass<https://github.com/roberteliass>, Update the version to 3.0.0 (currently listed as 1.0.0)
[RE] – The version was changed to 3.0.0
________________________________
In Solutions/CTERA/Data/Solution_CTERA.json<#10889 (comment)>:
@@ -0,0 +1,26 @@
+{
+ "Name": "CTERA",
+ "Author": "CTERA Networks - ***@***.******@***.***>",
+ "Logo": "<img src=\"https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/Solutions/CTERA/Data%20Connectors/Logo/CTERA_Networks_logo.svg\<https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/Solutions/CTERA/Data%20Connectors/Logo/CTERA_Networks_logo.svg/>" width=\"75px\" height=\"75px\">",
Hello @roberteliass<https://github.com/roberteliass>, Logo should be in 'Logos' folder, not 'Solution/Logo'. Please move and update link.
[RE] – Updated as instructed
________________________________
In Solutions/CTERA/Data Connectors/CTERA_Data_Connector.json<#10889 (comment)>:
+ "query": "Syslog\n| where ProcessName == 'gw-audit'\n| extend\n TenantName = extract(\"(\\\"vportal\\\":\\\"[^\\\"]*\\\")\<file:///%22vportal/%22:/%22%5b%5e/%22%5d*/%22)/>", 1, SyslogMessage),\n UserName = extract(\"(user=[^|]*)\", 1, SyslogMessage)\n| extend Permission = extract(\"(op=[^|]*)\", 1, SyslogMessage)\n| where UserName == 'user=specific_user'\n| summarize Count = count() by Permission"
+ }
+ ],
+ "dataTypes": [
+ {
+ "name": "Syslog",
+ "lastDataReceivedQuery": "Syslog | where Source == 'CTERA' | summarize Time = max(TimeGenerated)"
+ }
+ ],
+ "connectivityCriteria": [
+ {
+ "type": "IsConnectedQuery",
+ "value": "Syslog | where Source == 'CTERA' | summarize LastLogReceived = max(TimeGenerated) | project IsConnected = LastLogReceived > ago(15m)"
+ }
+ ],
+ "availability": {
Hello @roberteliass<https://github.com/roberteliass>, Update availability section to "status" : 1, "isPreview" : false.
[RE] – Changed and added as instructed
________________________________
On Solutions/CTERA/Data Connectors/Logo/CTERA_Networks_logo.svg<#10889 (comment)>:
Kql Validation Checks are failing for this logo, Can you please check and resolve those validations.
Please correct the id it should be in guid format.
[RE] – Updated the file, but not totally sure what does KQL validation check means, please elaborate, and how do you check it.
________________________________
In Solutions/CTERA/Workbooks/CTERA_Workbook.json<#10889 (comment)>:
+ "timeContext": {
+ "durationMs": 2592000000
+ },
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces",
+ "visualization": "timechart"
+ },
+ "name": "query - 2"
+ }
+ ],
+ "fallbackResourceIds": [
+ "/subscriptions/0dfe0fcb-a5a0-4b3b-898d-31c327799113/resourcegroups/product-robert/providers/microsoft.operationalinsights/workspaces/robertsentinel2"
+ ],
+ "fromTemplateId": "sentinel-UserWorkbook",
+ "$schema": "https://github.com/Microsoft/Application-Insights-Workbooks/blob/master/schema/workbook.json"
+}
Please change fromTemplateId, The current value is by default. Please change it. [RE] – updated to GUID format
Also please add workbook metadata to this file https://github.com/Azure/Azure-Sentinel/blob/master/Workbooks/WorkbooksMetadata.json. [RE] – added
Also Share some workbook images with Dark and White background. [RE] – please find two screenshots attached, CTERASMBLogsWorkbookWhite.png and CTERASMBLogsWorkbookBlack.png.
—
Reply to this email directly, view it on GitHub<#10889 (review)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A44VKLZQ3MVB5XB6ZOUJG5DZO5L6TAVCNFSM6AAAAABLT3H5F6VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDEMBUHE4DGMJVGE>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
|
Hi,
I haven’t received any response from you.
Please let me know if there’s any feedback and what are the next steps.
Thanks,
Robert Elias
Product Manager
e. ***@***.******@***.***>
linkedin eliasrobert<http://www.linkedin.com/in/eliasrobert>
***@***.***
From: Robert Elias ***@***.***>
Sent: August 1, 2024 2:06 AM
To: Azure/Azure-Sentinel ***@***.***>; Azure/Azure-Sentinel ***@***.***>
Cc: Mention ***@***.***>
Subject: RE: [Azure/Azure-Sentinel] Ctera branch (PR #10889)
Hi, responding to each section.
From: ***@***.******@***.***> ***@***.******@***.***>>
Sent: July 30, 2024 12:27 PM
To: Azure/Azure-Sentinel ***@***.******@***.***>>
Cc: Robert Elias ***@***.******@***.***>>; Mention ***@***.******@***.***>>
Subject: Re: [Azure/Azure-Sentinel] Ctera branch (PR #10889)
You don't often get email from ***@***.******@***.***>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
@v-visodadasi requested changes on this pull request.
________________________________
In Solutions/CTERA/Data/Solution_CTERA.json<#10889 (comment)>:
@@ -0,0 +1,26 @@
+{
+ "Name": "CTERA",
+ "Author": "CTERA Networks - ***@***.******@***.***>",
+ "Logo": "<img src=\"https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/Solutions/CTERA/Data%20Connectors/Logo/CTERA_Networks_logo.svg\<https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/Solutions/CTERA/Data%20Connectors/Logo/CTERA_Networks_logo.svg/>" width=\"75px\" height=\"75px\">",
+ "Description": "The CTERA solution allows you to ingest and analyze events from CTERA Edge Filers in Microsoft Sentinel. This solution includes a data connector to collect syslog data from CTERA, analytic rules to detect suspicious activities, hunting queries for threat hunting, and a workbook for data visualization and analysis.\n\n**Data Connectors:** 1, **Analytic Rules:** 2, **Hunting Queries:** 3, **Workbook:** 1\n\n[Learn more about Microsoft Sentinel](https://aka.ms/azuresentinel) | [Learn more about Solutions](https://aka.ms/azuresentinelsolutionsdoc)",
Hello @roberteliass<https://github.com/roberteliass>, Description should not include the list of content.
[RE] – List of content was removed from description
________________________________
In Solutions/CTERA/Data/Solution_CTERA.json<#10889 (comment)>:
+ "Data Connectors/CTERA_Data_Connector.json"
+ ],
+ "Workbooks": [
+ "Workbooks/CTERA_Workbook.json"
+ ],
+ "Analytic Rules": [
+ "Analytic Rules/Ransomware User Blocked.yaml",
+ "Analytic Rules/RansomwareDetected.yaml"
+ ],
+ "Hunting Queries": [
+ "Hunting Queries/MassDeletions.yaml",
+ "Hunting Queries/MassAccessDenied.yaml",
+ "Hunting Queries/MassPermissionChanges.yaml"
+ ],
+ "BasePath": "C:\\GitHub\\Azure-Sentinel\\Solutions\\CTERA",
+ "Version": "1.0.0",
Hello @roberteliass<https://github.com/roberteliass>, Update the version to 3.0.0 (currently listed as 1.0.0)
[RE] – The version was changed to 3.0.0
________________________________
In Solutions/CTERA/Data/Solution_CTERA.json<#10889 (comment)>:
@@ -0,0 +1,26 @@
+{
+ "Name": "CTERA",
+ "Author": "CTERA Networks - ***@***.******@***.***>",
+ "Logo": "<img src=\"https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/Solutions/CTERA/Data%20Connectors/Logo/CTERA_Networks_logo.svg\<https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/Solutions/CTERA/Data%20Connectors/Logo/CTERA_Networks_logo.svg/>" width=\"75px\" height=\"75px\">",
Hello @roberteliass<https://github.com/roberteliass>, Logo should be in 'Logos' folder, not 'Solution/Logo'. Please move and update link.
[RE] – Updated as instructed
________________________________
In Solutions/CTERA/Data Connectors/CTERA_Data_Connector.json<#10889 (comment)>:
+ "query": "Syslog\n| where ProcessName == 'gw-audit'\n| extend\n TenantName = extract(\"(\\\"vportal\\\":\\\"[^\\\"]*\\\")\<file:///%22vportal/%22:/%22%5b%5e/%22%5d*/%22)/>", 1, SyslogMessage),\n UserName = extract(\"(user=[^|]*)\", 1, SyslogMessage)\n| extend Permission = extract(\"(op=[^|]*)\", 1, SyslogMessage)\n| where UserName == 'user=specific_user'\n| summarize Count = count() by Permission"
+ }
+ ],
+ "dataTypes": [
+ {
+ "name": "Syslog",
+ "lastDataReceivedQuery": "Syslog | where Source == 'CTERA' | summarize Time = max(TimeGenerated)"
+ }
+ ],
+ "connectivityCriteria": [
+ {
+ "type": "IsConnectedQuery",
+ "value": "Syslog | where Source == 'CTERA' | summarize LastLogReceived = max(TimeGenerated) | project IsConnected = LastLogReceived > ago(15m)"
+ }
+ ],
+ "availability": {
Hello @roberteliass<https://github.com/roberteliass>, Update availability section to "status" : 1, "isPreview" : false.
[RE] – Changed and added as instructed
________________________________
On Solutions/CTERA/Data Connectors/Logo/CTERA_Networks_logo.svg<#10889 (comment)>:
Kql Validation Checks are failing for this logo, Can you please check and resolve those validations.
Please correct the id it should be in guid format.
[RE] – Updated the file, but not totally sure what does KQL validation check means, please elaborate, and how do you check it.
________________________________
In Solutions/CTERA/Workbooks/CTERA_Workbook.json<#10889 (comment)>:
+ "timeContext": {
+ "durationMs": 2592000000
+ },
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces",
+ "visualization": "timechart"
+ },
+ "name": "query - 2"
+ }
+ ],
+ "fallbackResourceIds": [
+ "/subscriptions/0dfe0fcb-a5a0-4b3b-898d-31c327799113/resourcegroups/product-robert/providers/microsoft.operationalinsights/workspaces/robertsentinel2"
+ ],
+ "fromTemplateId": "sentinel-UserWorkbook",
+ "$schema": "https://github.com/Microsoft/Application-Insights-Workbooks/blob/master/schema/workbook.json"
+}
Please change fromTemplateId, The current value is by default. Please change it. [RE] – updated to GUID format
Also please add workbook metadata to this file https://github.com/Azure/Azure-Sentinel/blob/master/Workbooks/WorkbooksMetadata.json. [RE] – added
Also Share some workbook images with Dark and White background. [RE] – please find two screenshots attached, CTERASMBLogsWorkbookWhite.png and CTERASMBLogsWorkbookBlack.png.
—
Reply to this email directly, view it on GitHub<#10889 (review)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A44VKLZQ3MVB5XB6ZOUJG5DZO5L6TAVCNFSM6AAAAABLT3H5F6VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDEMBUHE4DGMJVGE>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
|
Please note that the Solution Metadata file should not be formatted in this manner. For reference, Please see https://github.com/Azure/Azure-Sentinel/blob/master/Solutions/AIShield%20AI%20Security%20Monitoring/SolutionMetadata.json |
|
Please resolve the validation errors |
I can't understand why the validation is failing neither on the logo, nor for the rest of the validations. |
|
I’m not sure I understand why the validation fails, is there a clear way to identify it?
Thanks,
Robert Elias
Product Manager
e. ***@***.******@***.***>
linkedin eliasrobert<http://www.linkedin.com/in/eliasrobert>
***@***.***
From: ***@***.*** ***@***.***>
Sent: August 5, 2024 6:57 AM
To: Azure/Azure-Sentinel ***@***.***>
Cc: Robert Elias ***@***.***>; Mention ***@***.***>
Subject: Re: [Azure/Azure-Sentinel] Ctera branch (PR #10889)
Please resolve the validation errors
—
Reply to this email directly, view it on GitHub<#10889 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A44VKL4SC5OSGOZUCU4PZBDZP3ZXHAVCNFSM6AAAAABLT3H5F6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRYGEZDEOJRGE>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
|
Hello @roberteliass, Can you provide me write access to your branch. You can do this by inviting me as an contributor to your branch. Thanks, |
I provided the access, let me know if you have it. In addition please let me know what is the status on my request to better understand the validation failures. |
| "title": "CTERA Syslog", | ||
| "publisher": "CTERA", | ||
| "description": "Ingest CTERA syslog data into Microsoft Sentinel", | ||
| "additionalRequirementBanner": "None ", |
There was a problem hiding this comment.
Hello @roberteliass, Please add a short description markdown to the data connector.
For ref: https://github.com/Azure/Azure-Sentinel/blob/master/Solutions/Theom/Data%20Connectors/Theom.json
There was a problem hiding this comment.
Updated, will commit shortly
|
Please do share sample data to test the content of the solution |
|
Please find the syslog messages files which were used for testing the solution in this link:
https://cti.ctera.com/invitations/?share=c96e27fca1369ea917d8&dl=1
Thanks,
Robert Elias
Product Manager
e. ***@***.******@***.***>
linkedin eliasrobert<http://www.linkedin.com/in/eliasrobert>
***@***.***
From: v-prasadboke ***@***.******@***.***>>
Sent: August 12, 2024 10:07 AM
To: Azure/Azure-Sentinel ***@***.******@***.***>>
Cc: Robert Elias ***@***.******@***.***>>; Mention ***@***.******@***.***>>
Subject: Re: [Azure/Azure-Sentinel] Ctera branch (PR #10889)
Please do share sample data to test the content of the solution
—
Reply to this email directly, view it on GitHub<#10889 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A44VKL7DKXZ5IXVEGD2N36LZRBNK7AVCNFSM6AAAAABLT3H5F6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBTGI2DKNRRHE>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
roberteliass
force-pushed
the
CTERA-branch
branch
from
4ef54ef to
68bc69d
Compare
|
All arm-ttk issues were addressed, please process this request it's pending for over a week |
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.
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.