Skip to content
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.

Sign up for GitHub

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

[Microsoft Graph Security] Update msg-update-alert documentation #32983

Merged
merged 6 commits into from
Feb 20, 2024
Merged

[Microsoft Graph Security] Update msg-update-alert documentation #32983

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
0babb6f
update docs
michal-dagan Feb 18, 2024
ae0f13a
update dockers
michal-dagan Feb 18, 2024
0316273
Merge branch 'master' into update-msg-docs-xsup-33542
michal-dagan Feb 18, 2024
425adcc
Merge branch 'master' into update-msg-docs-xsup-33542
michal-dagan Feb 19, 2024
f40d346
Merge remote-tracking branch 'origin/master' into update-msg-docs-xsu…
michal-dagan Feb 19, 2024
40f5614
add "MSG-ediscovery-tpb" to skipped_tests
michal-dagan Feb 19, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 2 additions & 4 deletions Packs/MicrosoftGraphSecurity/Integrations/MicrosoftGraphSecurity/MicrosoftGraphSecurity.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -689,17 +689,15 @@ script:
- unknown
- truePositive
- falsePositive
- benignPositive
- informationalExpectedActivity
- auto: PREDEFINED
description: Relevant only for Alerts v2. Use this field to update the alert's determination.
name: determination
predefined:
- unknown
- apt
- malware
- phishing
- other
- securityPersonnel
- securityTesting
- multiStagedAttack
- maliciousUserActivity
Expand Down Expand Up @@ -2038,7 +2036,7 @@ script:
- contextPath: MSGraphMail.AssessmentRequest.ResultMessage
description: The result message of the assessment request.
type: String
dockerimage: demisto/crypto:1.0.0.82826
dockerimage: demisto/crypto:1.0.0.87358
isfetch: true
runonce: false
script: '-'
Expand Down
26 changes: 13 additions & 13 deletions Packs/MicrosoftGraphSecurity/Integrations/MicrosoftGraphSecurity/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -377,19 +377,19 @@ Update an editable alert property within any integrated solution to keep alert s

#### Input

| **Argument Name** | **Description** | **Required** |
| --- | --- | --- |
| alert_id | The Alert ID. Provider-generated GUID/unique identifier. | Required |
| assigned_to | Name of the analyst the alert is assigned to for triage, investigation, or remediation. | Optional |
| closed_date_time | Relevant only for Legacy Alerts. Time the alert was closed in the string format MM/DD/YYYY. | Optional |
| comments | Relevant only for Legacy Alerts. Analyst comments on the alert (for customer alert management). | Optional |
| feedback | Relevant only for Legacy Alerts. Analyst feedback on the alert. Possible values are: unknown, truePositive, falsePositive, benignPositive. | Optional |
| status | Alert lifecycle status (stage). Possible values are: unknown, newAlert, inProgress, resolved, new. | Optional |
| tags | Relevant only for Legacy Alerts. User-definable labels that can be applied to an alert and can serve as filter conditions, for example "HVA", "SAW). | Optional |
| vendor_information | Relevant only for Legacy Alerts. Details about the security service vendor, for example Microsoft. | Optional |
| provider_information | Relevant only for Legacy Alerts. Details about the security service vendor, for example Windows Defender ATP. | Optional |
| classification | Relevant only for Alerts v2. Use this field to update the alert's classification. Possible values are: unknown, truePositive, falsePositive, benignPositive. | Optional |
| determination | Relevant only for Alerts v2. Use this field to update the alert's determination. Possible values are: unknown, apt, malware, phishing, other, securityPersonnel, securityTesting, multiStagedAttack, maliciousUserActivity, lineOfBusinessApplication, unwantedSoftware. | Optional |
| **Argument Name** | **Description** | **Required** |
|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|
| alert_id | The Alert ID. Provider-generated GUID/unique identifier. | Required |
| assigned_to | Name of the analyst the alert is assigned to for triage, investigation, or remediation. | Optional |
| closed_date_time | Relevant only for Legacy Alerts. Time the alert was closed in the string format MM/DD/YYYY. | Optional |
| comments | Relevant only for Legacy Alerts. Analyst comments on the alert (for customer alert management). | Optional |
| feedback | Relevant only for Legacy Alerts. Analyst feedback on the alert. Possible values are: unknown, truePositive, falsePositive, benignPositive. | Optional |
| status | Alert lifecycle status (stage). Possible values are: unknown, newAlert, inProgress, resolved, new. | Optional |
| tags | Relevant only for Legacy Alerts. User-definable labels that can be applied to an alert and can serve as filter conditions, for example "HVA", "SAW). | Optional |
| vendor_information | Relevant only for Legacy Alerts. Details about the security service vendor, for example Microsoft. | Optional |
| provider_information | Relevant only for Legacy Alerts. Details about the security service vendor, for example Windows Defender ATP. | Optional |
| classification | Relevant only for Alerts v2. Use this field to update the alert's classification. Possible values are: unknown, truePositive, falsePositive, informationalExpectedActivity. | Optional |
| determination | Relevant only for Alerts v2. Use this field to update the alert's determination. Possible values are: unknown, malware, phishing, other, securityTesting, multiStagedAttack, maliciousUserActivity, lineOfBusinessApplication, unwantedSoftware. | Optional |

#### Context Output

Expand Down
6 changes: 6 additions & 0 deletions Packs/MicrosoftGraphSecurity/ReleaseNotes/2_2_8.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@

#### Integrations

##### Microsoft Graph Security
- Updated the documentation for the ***msg-update-alert*** command to include only the determination and classification options supported by Microsoft.
- Updated the Docker image to: *demisto/crypto:1.0.0.87358*.
2 changes: 1 addition & 1 deletion Packs/MicrosoftGraphSecurity/pack_metadata.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
"name": "Microsoft Graph Security",
"description": "Unified gateway to security insights - all from a unified Microsoft Graph\n Security API.",
"support": "xsoar",
"currentVersion": "2.2.7",
"currentVersion": "2.2.8",
"author": "Cortex XSOAR",
"url": "https://www.paloaltonetworks.com/cortex",
"email": "",
Expand Down
3 changes: 2 additions & 1 deletion Tests/conf.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5865,7 +5865,8 @@
"ThreatStream-Test": "Issue CRTX-96526",
"MSG-Threat-Assessment-test": "API limitation",
"BambenekConsultingFeed_Test": "Issue CRTX-99480",
"AWS SNS Listener - Test": "Cant validate mock msg against AWS-SNS in TBP"
"AWS SNS Listener - Test": "Cant validate mock msg against AWS-SNS in TBP",
"MSG-ediscovery-tpb": "Issue CIAC-9763"
},
"skipped_integrations": {
"EWS Mail Sender": "The integration is deprecated",
Expand Down
Loading