Delete support email (demisto#13434)

* deleted the support email

* deleted the support email

* edits

* Update Packs/MicrosoftGraphGroups/ReleaseNotes/1_0_7.md

Co-authored-by: Shai Yaakovi <[email protected]>

Co-authored-by: Shai Yaakovi <[email protected]>

Author: merit-maita

CODE_OF_CONDUCT.md

@@ -34,7 +34,7 @@ This Code of Conduct applies both within project spaces and in public spaces whe
 
 ## Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected]. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
 
 Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
 

Packs/Anomali_ThreatStream/Integrations/integration-AnomaliThreatStream_README.md

@@ -36,7 +36,7 @@
 <strong>API Key |</strong> The API key you copied in the previous procedure. (Required)</li>
 </ul>
 </li>
-<li>Click the <strong>Test</strong> button to verify the the URL and token.<br>A green light means the test was successful. If you experience any issues, contact <a href="mailto:[email protected]">Cortex XSOAR Support</a>.</li>
+<li>Click the <strong>Test</strong> button to verify the the URL and token.<br>A green light means the test was successful.</li>
 </ol>
 <hr>
 <h2>Use Cases</h2>

Packs/ArcSightLogger/Integrations/integration-ArcSightLogger_README.md

@@ -20,7 +20,7 @@
 <strong>Use system proxy settings</strong>: Select whether to communicate via the system proxy server or not.<br><strong>Cortex XSOAR engine</strong>: If relevant, select the engine that acts as a proxy to the server.<br>Engines are used when you need to access a remote network segments and there are network devices such as proxies, firewalls, etc. that prevent the Cortex XSOAR server from accessing the remote networks.<br>For more information on Cortex XSOAR engines see:<br><a href="https://support.demisto.com/hc/en-us/articles/226274727-Settings-Integrations-Engines">https://demisto.zendesk.com/hc/en-us/articles/226274727-Settings-Integrations-Engines</a><br><strong>Require users to enter additional password:</strong> Select whether you’d like an additional step where users are required to authenticate themselves with a password.</div>
 </div>
 </li>
-<li>Press the ‘Test’ button to validate connection.<br>If you are experiencing issues with the service configuration, please contact Cortex XSOAR support at <a href="mailto:[email protected]">[email protected]</a>
+<li>Press the ‘Test’ button to validate connection.
 </li>
 <li>After completing the test successfully, press the ‘Done’ button.</li>
 </ol>

Packs/CarbonBlackProtect/Integrations/CarbonBlackProtect/README.md

@@ -17,7 +17,7 @@
 <p class="wysiwyg-indent4"><strong>Cortex XSOAR engine:</strong> If relevant, select the engine that acts as a proxy to the server.  <br> Engines are used when you need to access a remote network segments and there are network devices such as proxies, firewalls, etc. that prevent the Cortex XSOAR server from accessing the remote networks.<br> <br> For more information on Cortex XSOAR engines see:<br> <a href="https://support.demisto.com/hc/en-us/articles/226274727-Settings-Integrations-Engines">https://demisto.zendesk.com/hc/en-us/articles/226274727-Settings-Integrations-Engines</a></p>
 <p class="wysiwyg-indent4"><strong>Require users to enter additional password:</strong> Select whether you’d like an additional step where users are required to authenticate themselves with a password.</p>
 <ol start="4">
-<li>Press the ‘Test’ button to validate connection.<br> If you are experiencing issues with the service configuration, please contact Cortex XSOAR support at [email protected]</li>
+<li>Press the ‘Test’ button to validate connection.</li>
 <li>After completing the test successfully, press the ‘Done’ button.</li>
 </ol>
 <h3>Commands:</h3>

Packs/DNSDB/Integrations/integration-DNSDB_README.md

@@ -8,7 +8,7 @@
 <li>Locate the DNSDB integration by searching for ‘Farsight DNSDB’ using the search box on the top of the page.</li>
 <li>Click ‘Add instance’ to create and configure a new integration. You should configure the following DNSDB and Cortex XSOAR specific settings:<br> <strong>Name</strong>: A textual name for the integration instance.<br> <strong>API Key</strong>: The API key that user gets from Farsight Security.<br> <strong>DNSDB Service URL</strong>: The service URL for Farsight DNSDB.<br> <strong>Use system proxy settings</strong>: Select whether or not to communicate via the system proxy server.<br> <strong>Cortex XSOAR engine</strong>: If relevant, select the engine that acts as a proxy to the server.<br> Engines are used when you need to access a remote network segments and there are network devices such as proxies, firewalls, etc. that prevent the Cortex XSOAR server from accessing the remote networks.<br> For more information on Cortex XSOAR engines see:<br> <a href="https://support.demisto.com/hc/en-us/articles/226274727-Settings-Integrations-Engines">https://demisto.zendesk.com/hc/en-us/articles/226274727-Settings-Integrations-Engines</a>
 </li>
-<li>Press the ‘Test’ button to validate connection.<br> If you are experiencing issues with the service configuration, please contact Cortex XSOAR support at <a href="mailto:[email protected]">[email protected]</a>.</li>
+<li>Press the ‘Test’ button to validate connection.</li>
 <li>After completing the test successfully, press the ‘Done’ button.</li>
 </ol>
 <p> </p>

Packs/Forcepoint/Integrations/integration-Forcepoint_README.md

@@ -12,7 +12,7 @@
 <li>Locate ‘Forcepoint ’ by searching for it using the search box on the top of the page.</li>
 <li>Click ‘Add instance’ to create and configure a new integration. You should configure the following settings:<br><strong>Name</strong>: A textual name for the integration instance.<br><strong>Server URL</strong>: API Server URL.<br><strong>Username and Password: </strong>The username and password for accessing the integration.<br><strong>Use system proxy settings: </strong>Specify whether to communicate with the integration via the system proxy server or not.<br><strong>Do not validate server certificate: </strong>Select in case you wish to circumvent server certification validation.  You may want to do this in case the server you are connecting to does not have a valid certificate.<strong><br></strong><strong>Cortex XSOAR engine</strong>: If relevant, select the engine that acts as a proxy to the server. Engines are used when you need to access a remote network segments and there are network devices such as proxies, firewalls, etc. that prevent the Cortex XSOAR server from accessing the remote networks.<br>For more information on Cortex XSOAR engines see:<br><a href="https://support.demisto.com/hc/en-us/articles/226274727-Settings-Integrations-Engines">https://demisto.zendesk.com/hc/en-us/articles/226274727-Settings-Integrations-Engines</a>
 </li>
-<li>Press the ‘Test’ button to validate connection.<br>If you are experiencing issues with the service configuration, please contact Cortex XSOAR support at <a href="mailto:[email protected]">[email protected]</a>
+<li>Press the ‘Test’ button to validate connection.
 </li>
 <li>After completing the test successfully, press the ‘Done’ button.</li>
 </ol>

Packs/ICEBRG/Integrations/integration-ICEBRG_README.md

@@ -22,7 +22,7 @@
 <li>Locate ‘ICEBRG’ by searching for it using the search box on the top of the page.</li>
 <li>Click ‘Add instance’ to create and configure a new integration. You should configure the following settings:<br><strong>Name</strong>: A textual name for the integration instance.<br><strong>Server URL for the search API</strong>: The URL appliance.<br><strong>API username</strong>: ICEBRG API token.<br><strong>Server URL for the reports API:</strong> The server used for the reports API.<br><strong>Password</strong>: ICEBRG API password.<br><strong>ICEBRG token:</strong> The token obtained in the steps above.<strong> <br></strong><strong>Fetch incidents</strong>: Select whether to automatically create Cortex XSOAR incidents from <strong>ICEBRG </strong>offenses. <br><strong>Cortex XSOAR engine</strong>: If relevant, select the engine that acts as a proxy to the server. Engines are used when you need to access a remote network segments and there are network devices such as proxies, firewalls, etc. that prevent the Cortex XSOAR server from accessing the remote networks.<br>For more information on Cortex XSOAR engines see:<br><a href="https://support.demisto.com/hc/en-us/articles/226274727-Settings-Integrations-Engines">https://demisto.zendesk.com/hc/en-us/articles/226274727-Settings-Integrations-Engines</a>
 </li>
-<li>Press the ‘Test’ button to validate connection.<br>If you are experiencing issues with the service configuration, please contact Cortex XSOAR support at <a href="mailto:[email protected]">[email protected]</a>
+<li>Press the ‘Test’ button to validate connection.
 </li>
 <li>After completing the test successfully, press the ‘Done’ button.</li>
 </ol>

Packs/MicrosoftGraphGroups/Integrations/MicrosoftGraphGroups/MicrosoftGraphGroups.yml

@@ -112,7 +112,7 @@ script:
         Whether this group is synced from an on-premises directory (true). This group was originally synced from an on-premises directory but is no longer synced (false). Null if this object has never been synced from an on-premises directory (default).
       type: String
     - contextPath: MSGraphGroup.ProxyAddresses
-      description: 'Email addresses for the group that directs to the same group mailbox. For example: ["SMTP: support@demisto.com", "smtp: support@demisto.com"].'
+      description: 'Email addresses for the group that directs to the same group mailbox. For example: ["SMTP: example@demisto.com", "smtp: example@demisto.com"].'
       type: String
     - contextPath: MSGraphGroup.RenewedDateTime
       description: 'Timestamp of when the group was last renewed, which represents the time and date information using ISO 8601 format. Always in UTC time. For example, midnight UTC on Jan 1, 2019 is ''2019-01-01T00:00:00Z''.'
@@ -182,7 +182,7 @@ script:
         Whether the group is synced from an on-premises directory (true). This group was originally synced from an on-premises directory but is no longer synced (false). Null if this object has never been synced from an on-premises directory (default).
       type: String
     - contextPath: MSGraphGroup.ProxyAddresses
-      description: 'Email addresses for the group that directs to the same group mailbox. For example: ["SMTP: support@demisto.com", "smtp: support@demisto.com"].'
+      description: 'Email addresses for the group that directs to the same group mailbox. For example: ["SMTP: example@demisto.com", "smtp: example@demisto.com"].'
       type: String
     - contextPath: MSGraphGroup.RenewedDateTime
       description: 'The timestamp of when the group was last renewed. This cannot be modified directly and is only updated via the renew service action. The Timestamp type represents date and time information using ISO 8601 format in UTC time. For example, midnight UTC on Jan 1, 2019 is ''2019-01-01T00:00:00Z''.'
@@ -275,7 +275,7 @@ script:
         Whether this group is synced from an on-premises directory (true). This group was originally synced from an on-premises directory but is no longer synced (false). Null if this object has never been synced from an on-premises directory (default).
       type: String
     - contextPath: MSGraphGroup.ProxyAddresses
-      description: 'Email addresses for the group that directs to the same group mailbox. For example, ["SMTP: support@demisto.com", "smtp: support@demisto.com"].'
+      description: 'Email addresses for the group that directs to the same group mailbox. For example, ["SMTP: example@demisto.com", "smtp: example@demisto.com"].'
       type: String
     - contextPath: MSGraphGroup.RenewedDateTime
       description: 'Timestamp of when the group was last renewed. This cannot be modified directly and is only updated via the renew service action. The Timestamp type represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 would look like this: ''2014-01-01T00:00:00Z''.'
@@ -408,7 +408,7 @@ script:
     description: Removes a member from a group.
     execution: false
     name: msgraph-groups-remove-member
-  dockerimage: demisto/crypto:1.0.0.11412
+  dockerimage: demisto/crypto:1.0.0.19032
   isfetch: false
   longRunning: false
   longRunningPort: false

Packs/MicrosoftGraphGroups/Integrations/MicrosoftGraphGroups/README.md

@@ -195,7 +195,7 @@ If the collection includes DynamicMembership, the group has dynamic membership;
     <tr>
       <td>MSGraphGroup.ProxyAddresses</td>
       <td>String</td>
-      <td>Email addresses for the group that directs to the same group mailbox. For example: ["SMTP: support@demisto.com", "smtp: support@demisto.com"].</td>
+      <td>Email addresses for the group that directs to the same group mailbox. For example: ["SMTP: example@demisto.com", "smtp: example@demisto.com"].</td>
     </tr>
     <tr>
       <td>MSGraphGroup.RenewedDateTime</td>
@@ -409,7 +409,7 @@ If the collection includes DynamicMembership, the group has dynamic membership;
     <tr>
       <td>MSGraphGroup.ProxyAddresses</td>
       <td>String</td>
-      <td>Email addresses for the group that directs to the same group mailbox. For example: ["SMTP: support@demisto.com", "smtp: support@demisto.com"].</td>
+      <td>Email addresses for the group that directs to the same group mailbox. For example: ["SMTP: example@demisto.com", "smtp: example@demisto.com"].</td>
     </tr>
     <tr>
       <td>MSGraphGroup.RenewedDateTime</td>
@@ -640,7 +640,7 @@ If the group collection includes DynamicMembership, the group has dynamic member
     <tr>
       <td>MSGraphGroup.ProxyAddresses</td>
       <td>String</td>
-      <td>Email addresses for the group that directs to the same group mailbox. For example, ["SMTP: support@demisto.com", "smtp: support@demisto.com"].</td>
+      <td>Email addresses for the group that directs to the same group mailbox. For example, ["SMTP: example@demisto.com", "smtp: example@demisto.com"].</td>
     </tr>
     <tr>
       <td>MSGraphGroup.RenewedDateTime</td>

Packs/MicrosoftGraphGroups/ReleaseNotes/1_0_7.md

@@ -0,0 +1,4 @@
+
+#### Integrations
+##### Microsoft Graph Groups
+- Updated the integration docker image to demisto/crypto:1.0.0.19032

Packs/MicrosoftGraphGroups/pack_metadata.json

@@ -2,7 +2,7 @@
     "name": "Microsoft Graph Groups",
     "description": "Microsoft Graph Groups enables you to create and manage different types of groups and group functionality according to your requirements.",
     "support": "xsoar",
-    "currentVersion": "1.0.6",
+    "currentVersion": "1.0.7",
     "author": "Cortex XSOAR",
     "url": "https://www.paloaltonetworks.com/cortex",
     "email": "",

Packs/OpsGenie/Integrations/integration-OpsGenie_README.md

@@ -24,7 +24,7 @@
 </ol>
 <p class="wysiwyg-indent4">For more information on Cortex XSOAR engines see:<br> <a href="https://support.demisto.com/hc/en-us/articles/226274727-Settings-Integrations-Engines">https://demisto.zendesk.com/hc/en-us/articles/226274727-Settings-Integrations-Engines</a><br> Require users to enter additional password: Select whether you’d like an additional step where users are required to authenticate themselves with a password.</p>
 <ol start="4">
-<li>Press the ‘Test’ button to validate connection.<br> If you are experiencing issues with the service configuration, please contact Cortex XSOAR support at <a href="mailto:[email protected]">[email protected]</a>
+<li>Press the ‘Test’ button to validate connection.
 </li>
 <li>After completing the test successfully, press the ‘Done’ button.</li>
 </ol>

Packs/PhishLabs/Integrations/PhishLabsIOC/README.md

@@ -1057,5 +1057,5 @@
 <h2 id="troubleshooting">Troubleshooting</h2>
 </div>
 <div class="cl-preview-section">
-<p>Retrieving indicators for an incident - if the incident was fetched to Cortex XSOAR but wasn’t found by the command, try running it with a longer duration, for example,<span> </span><code>since=30d</code>.<br> Possible error codes from the API:<br> <code>400 Bad Request</code><span> </span>- Unsupported request format<br> <code>401 Unauthorized</code><span> </span>- Incorrect credentials provided<br> <code>403 Forbidden</code><span> </span>- Insufficient permissions<br> <code>404 Not Found</code><span> </span>- Requested resource was not found<br> For further assistance, contact Cortex XSOAR Customer Success:<span> </span><a href="mailto:[email protected]">[email protected]</a>.</p>
+<p>Retrieving indicators for an incident - if the incident was fetched to Cortex XSOAR but wasn’t found by the command, try running it with a longer duration, for example,<span> </span><code>since=30d</code>.<br> Possible error codes from the API:<br> <code>400 Bad Request</code><span> </span>- Unsupported request format<br> <code>401 Unauthorized</code><span> </span>- Incorrect credentials provided<br> <code>403 Forbidden</code><span> </span>- Insufficient permissions<br> <code>404 Not Found</code><span> </span>- Requested resource was not found<br>.</p>
 </div>

Packs/PrismaCloudCompute/Integrations/PaloAltoNetworks_PrismaCloudCompute/README.md

@@ -72,4 +72,3 @@ If any alerts are missing in Cortex XSOAR, check the status of the integration.
 
 ![image](https://user-images.githubusercontent.com/49071222/72086124-18b0fe00-330f-11ea-894b-6b2f9f0528fd.png)
 
-If you have any questions, contact [Demisto support](mailto:[email protected]) and attach the server logs.

Packs/PrismaCloudCompute/README.md

@@ -69,6 +69,4 @@ At this point, you can add tasks that extend the playbook to check and respond t
 
 If any alerts are missing in Demisto, check the status of the integration:
 
-![image](https://user-images.githubusercontent.com/49071222/72086124-18b0fe00-330f-11ea-894b-6b2f9f0528fd.png)
-
-If you're having further issues, contact [[email protected]](mailto:[email protected]) and attach the server logs.
+![image](https://user-images.githubusercontent.com/49071222/72086124-18b0fe00-330f-11ea-894b-6b2f9f0528fd.png)

Packs/ProtectWise/Integrations/integration-ProtectWise_README.md

@@ -22,7 +22,7 @@
 <p class="wysiwyg-indent8"><strong>Cortex XSOAR engine:</strong> If relevant, select the engine that acts as a proxy to the server.  </p>
 <p class="wysiwyg-indent8">Engines are used when you need to access a remote network segments and there are network devices such as proxies, firewalls, etc. that prevent the Cortex XSOAR server from accessing the remote networks.<br><br>For more information on Cortex XSOAR engines see:<br><a href="https://support.demisto.com/hc/en-us/articles/226274727-Settings-Integrations-Engines">https://demisto.zendesk.com/hc/en-us/articles/226274727-Settings-Integrations-Engines</a></p>
 <ol start="4">
-<li>Press the ‘Test’ button to validate connection.<br>If you are experiencing issues with the service configuration, please contact Cortex XSOAR support at [email protected]</li>
+<li>Press the ‘Test’ button to validate connection.</li>
 <li>After completing the test successfully, press the ‘Done’ button.</li>
 </ol>
 <h3>Commands:</h3>

Packs/ServiceNow/.secrets-ignore

@@ -2,7 +2,6 @@ http://www.demisto.com
 https://company.service-now.com
 https://docs.servicenow.com
 https://user-images.githubusercontent.com
-[email protected]
 https://support.demisto.com
 https://company.-now.com
 docs.now.com

Packs/ServiceNow/Integrations/ServiceNow/README.md

@@ -3209,5 +3209,4 @@
 <p>In the API, fields that are linked to records in a table (e.g., user) return as an object of <code>link</code> and <code>value</code> as the <code>link</code> refers to the link to that record in the API and the <code>value</code> refers to the system ID of the record. By default, the integration retrieves the value of the object - which means its system ID.</p>
 <h2>Troubleshooting</h2>
 <p>If there is an error within ServiceNow, the message is usually indicative, e.g., <code>User Not Authenticated, details: Required to provide Auth information </code>, <code>Invalid table</code> or <code>No Record found, details: Record doesn't exist or ACL restricts the record retrieval</code>.</p>
-<p>However there may be connection issues, e.g., when the ServiceNow server URL is incorrect or is unreachable.</p>
-<p>If you experience any issues, contact <a href="mailto:[email protected]">Cortex XSOAR Support</a>.</p>
+<p>However there may be connection issues, e.g., when the ServiceNow server URL is incorrect or is unreachable.</p>