Merge branch 'main' into PLG-97-rename

Author: antonymartinsumo

docs/platform-services/automation-service/app-central/integrations/azure-ad.md

@@ -6,51 +6,55 @@ import useBaseUrl from '@docusaurus/useBaseUrl';
 
 <img src={useBaseUrl('/img/platform-services/automation-service/app-central/logos/azure-ad.png')} alt="axonius" width="80"/>
 
-***Version: 1.8  
-Updated: Jan 16, 2024***
+***Version: 1.9  
+Updated: Nov 12, 2024***
 
 Azure Active Directory (Azure AD) is Microsoft's cloud-based identity and access management service, which helps your employees sign in and access resources.
 
 ## Actions
 
-* **Create User** *(Enrichment)* - Create a new user.
-* **Delete User** *(Containment)* - Delete a specific user.
-* **List Users** *(Enrichment)* - List all users.
-* **Get User** (Enrichment) - Get details for a specific user.
+* **Add Member To Group** *(Enrichment)* - Add a user to a specific group.
 * **Create Group** *(Enrichment)* - Create a group.
+* **Create User** *(Enrichment)* - Create a new user.
 * **Delete Group** *(Containment)* -Delete a specific group.
-* **Add Member To Group** *(Enrichment)* - Add a user to a specific group.
+* **Delete User** *(Containment)* - Delete a specific user.
+* **Disable User** *(Containment)* - Block user account.
 * **Get Manager** (*Enrichment*) - Get user manager.
+* **Get Member Groups** *(Enrichment)* - Retrieve a Group memberships for the user.
+* **Get User** (Enrichment) - Get details for a specific user.
+* **List Devices** *(Enrichment)* - Retrieve a list of device objects registered in the organization.
 * **List Groups** (*Enrichment*) - List all the groups available in an organization.
+* **List Users** *(Enrichment)* - List all users.
+* **Reset User Password** *(Containment)* - Reset user password.
 * **Revoke Sign In Sessions** (*Containment*) - Invalidates all the refresh tokens issued to applications for a user (as well as session cookies in a user's browser).
-* **List Devices** *(Enrichment)* - Retrieve a list of device objects registered in the organization.
-* **Disable User** *(Containment)* - Block user account.
-* **Get Member Groups** *(Enrichment)* - Retrieve a Group memberships for the user.
 
 ## Azure Active Directory configuration
 
 The following steps show how to create an Azure AD Application in order to work with Cloud SOAR.
 
 1. Log in to Azure portal with the user that has administrator privileges.
 1. Navigate to **Azure Active Directory** > **App registrations** > **New registration**.<br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/azure-ad/azure-ad-1.png')} style={{border:'1px solid gray'}} alt="azure-ad-1" width="600"/>
-1. In the registration form, choose a name for your application and then click Register.<br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/azure-ad/azure-ad-2.png')} style={{border:'1px solid gray'}} alt="azure-ad-2" width="600"/>
-1. Write down the Application ID and Directory ID, you will need them later for the integration configuration.<br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/azure-ad/azure-ad-3.png')} style={{border:'1px solid gray'}} alt="azure-ad-3" width="600"/>
-1. Configure Azure AD Application permissions: on the left choose API permissions.
-1. Then click the **Add a permission** button.<br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/azure-ad/azure-ad-4.png')} style={{border:'1px solid gray'}} alt="azure-ad-4" width="600"/>
-1. Select your application in App registrations in the Azure portal. 
+1. In the registration form, choose a name for your application and then click **Register**.<br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/azure-ad/azure-ad-2.png')} style={{border:'1px solid gray'}} alt="azure-ad-2" width="600"/>
+1. Write down the Application ID and Directory ID. You will need them later for the integration configuration.<br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/azure-ad/azure-ad-3.png')} style={{border:'1px solid gray'}} alt="azure-ad-3" width="600"/>
+1. To configure Azure AD Application permissions, on the left choose **API permissions**. 
+6. Click the **Add a permission** button.<br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/azure-ad/azure-ad-4.png')} style={{border:'1px solid gray'}} alt="azure-ad-4" width="600"/>
+7. Select your application in App registrations in the Azure portal. 
    * Delegated permissions are selected by default. 
    * Delegated permissions are appropriate for client apps that access an API as the signed-in user, and whose access should be restricted to the permissions you select in the next step. 
    * Application permissions are for service or daemon-type applications that need to access API as themselves, without user interaction for sign-in or consent.<br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/azure-ad/azure-ad-5.png')} style={{border:'1px solid gray'}} alt="azure-ad-5" width="700"/>
 1. Select the following permissions to add:
    * **Delegated (work or school account)**. User.Read, User.ReadWrite, User.ReadBasic.All, User.Read.All, User.ReadWrite.All, Directory.Read.All, Directory.ReadWrite.All, Directory.AccessAsUser.All.
    * **Delegated (personal Microsoft account)**. User.Read, User.ReadWrite.
    * **Application**. User.Read.All, User.ReadWrite.All, Directory.Read.All, Directory.ReadWrite.All. <br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/azure-ad/azure-ad-6.png')} style={{border:'1px solid gray'}} alt="azure-ad-6" width="600"/>
-1. Once API permission are added then Admin must consent to a grant these permissions ([Learn more about permissions and consent](https://docs.microsoft.com/azure/active-directory/develop/v2-permissions-and-consent?WT.mc_id=Portal-Microsoft_AAD_RegisteredApps)). <br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/azure-ad/azure-ad-7.png')} style={{border:'1px solid gray'}} alt="azure-ad-7" width="600"/>
-1. Once Admin Consent is granted, API permissions configuration have been completed. Then we have to add a Client secret that will be used for the authentication, along with Client ID and Directory ID. To add Client secret, go to Certificates and secrets, and click **New client secret**.<br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/azure-ad/azure-ad-8.png')} style={{border:'1px solid gray'}} alt="azure-ad-8" width="600"/> 
-1. Select description and expiry period for the created secret and create it.
+1. Once API permission are added then Admin must consent to a grant these permissions ([Learn more about permissions and consent](https://docs.microsoft.com/azure/active-directory/develop/v2-permissions-and-consent?WT.mc_id=Portal-Microsoft_AAD_RegisteredApps).) <br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/azure-ad/azure-ad-7.png')} style={{border:'1px solid gray'}} alt="azure-ad-7" width="600"/>
+1. Once Admin Consent is granted, API permissions configuration have been completed. Then we have to add a Client secret that will be used for the authentication, along with Client ID and Directory ID. To add Client secret, go to Certificates and secrets, and click **New client secret**.<br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/azure-ad/azure-ad-8.png')} style={{border:'1px solid gray'}} alt="azure-ad-8" width="600"/>
+1. Select description and expiry period for the created secret and create it. 
 1. Once it's created, make sure you save its value, since its only displayed once.<br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/azure-ad/azure-ad-9.png')} style={{border:'1px solid gray'}} alt="azure-ad-9" width="600"/>
 1. Once you do these steps you will need to find the Tenant ID in order to use it on your resources file.<br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/azure-ad/azure-ad-10.png')} style={{border:'1px solid gray'}} alt="azure-ad-10" width="600"/>
 1. Configuration of Azure AD application is completed, you will need application’s Client ID, secret, Tenant ID. 
+1. Assign the app the role of User Administrator. This is required to perform action "Reset User Password".
+    * **Azure Active Directory** > **Roles and administrators** > **User Administrator** > **Add assignments** > **Your app** > **Add**.
+
 
 ## Change Log
 
@@ -69,3 +73,5 @@ The following steps show how to create an Azure AD Application in order to work
 * September 19, 2023 (v1.7) - Versioning
 * January 16, 2024 (v1.8)
 	+ Added New Action: Get Member Groups
+* November 12, 2024 (v1.9)
+    + Added New Action: Reset User Password

docs/platform-services/automation-service/app-central/integrations/microsoft-ews.md

@@ -7,8 +7,8 @@ import useBaseUrl from '@docusaurus/useBaseUrl';
 
 <img src={useBaseUrl('/img/platform-services/automation-service/app-central/logos/microsoft-ews.png')} alt="microsoft-ews" width="100"/>
 
-***Version: 2.3  
-Updated: Mar 4, 2024***
+***Version: 2.4  
+Updated: Nov 12, 2024***
 
 Perform actions on Microsoft EWS mailboxes, accounts, and security settings.
 
@@ -31,7 +31,7 @@ Perform actions on Microsoft EWS mailboxes, accounts, and security settings.
 
 Each application you want the Microsoft identity platform to perform identity and access management (IAM) needs to be registered. Registering it establishes a trust relationship between your application and the identity provider, the Microsoft identity platform.
 
-**Register an application**
+### Register an application
 
 Registering your application establishes a trust relationship between your app and the Microsoft identity platform. The trust is unidirectional: your app trusts the Microsoft identity platform, and not the other way around.
 
@@ -49,14 +49,15 @@ When registration completes, the Azure portal displays the app registration's Ov
 
 The client ID as one aspect in validating the security tokens it receives from the identity platform.<br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/microsoft-ews/microsoft-ews-3.png')} style={{border:'1px solid gray'}} alt="/microsoft-ews" width="800"/>
 
-**Add credentials**
+### Add credentials
 
 Credentials are used by confidential client applications that access an API. Examples of confidential clients are web apps, or service- and daemon-type applications. Credentials allow your application to authenticate as itself, requiring no interaction from a user at runtime.   
 You can add client secrets (a string) as credentials to your confidential client app registration.
 
 <br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/microsoft-ews/microsoft-ews-4.png')} style={{border:'1px solid gray'}} alt="/microsoft-ews" width="800"/>
 
-**Add a client secret**   
+### Add a client secret
+
 The client secret, known also as an application password, is a string value of your app.
 
 1. Select your application in App registrations in the Azure portal.
@@ -66,15 +67,15 @@ The client secret, known also as an application password, is a string value of y
 5. Select **Add**.
 6. Record the secret's value for use in your client application code - it's never displayed again after you leave this page.
 
-**Add permissions to API**
+### Add permissions to API
 
 1. Select your application in App registrations in the Azure portal.
 2. Select **API permissions > Add a permission**.
 3. Delegated permissions are selected by default. Delegated permissions are appropriate for client apps that access an API as the signed-in user, and whose access should be restricted to the permissions you select in the next step.
 4. Application permissions are for service- or daemon-type applications that need to access API as themselves, without user interaction for sign-in or consent. Unless you've defined application roles for your API.
 5. Select Add a permission, and add the following permissions (as we can see from picutre). <br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/microsoft-ews/microsoft-ews-5.png')} style={{border:'1px solid gray'}} alt="/microsoft-ews" width="800"/>
 
-**EWS API need to be configure these permissions**
+#### EWS API to be configured for these permissions
 
 Applications are authorized to call APIs when they are granted permissions by users/admins as part of the consent process. The list of configured permissions should include all the permissions the application needs.
 
@@ -130,6 +131,17 @@ full\_access\_as\_app Use Exchange Web Services with full access to all mailboxe
 
 Once API permission are added then Admin must consent to a grant these permissions, [Learn more about permissions and consent](https://docs.microsoft.com/azure/active-directory/develop/v2-permissions-and-consent?WT.mc_id=Portal-Microsoft_AAD_RegisteredApps).
 
+### Assign the required roles in the Exchange Admin Center
+
+1. Sign in to the [Exchange Admin Center (EAC)](https://admin.exchange.microsoft.com/#/).
+2. In the EAC, navigate to **Roles**.
+3. Click **Admin Roles**.
+4. Search for the role **Discovery Management** and click on it.
+5. Click on the **Assign** tab.
+6. Click **+** and search for the user you want to assign the role to.
+7. Click **Save**.
+
+
 ## Category
 
 Email Gateway
@@ -146,3 +158,6 @@ Email Gateway
 * November 29, 2022 - Added new actions (Send Email and Reply To Email)
 * October 6, 2023 (v2.2) - Integration Updated
 * March 4, 2024 (v2.3) - Updated code for compatibility with Python 3.12
+* November 12, 2024 (v2.4) 
+  * Updated the exchange_lib library to 5.4.2
+  * Updated the action Get Contacts to return the message "No contacts found" if the contacts are not found rather than returning an exception.

docs/platform-services/automation-service/app-central/integrations/netskope-v2.md

@@ -43,7 +43,8 @@ When finished, click **OK**. After being created, tokens can be managed by click
 1. The integration details will appear. Click on the **"+"** button to add new Resource.<br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/netskope-v2/netskope-v2-7.png')} style={{border:'1px solid gray'}} alt="netskope-v2" width="150"/> 
 1. Populate all the required fields (\*) and then click **SAVE**.
    * **Server URL**. URL for API V2 REST API (https://&lt;tenant-name&gt;.goskope.com).
-   * **Token**. The Token you copied earlier.
+   * **Token**. The Token you copied earlier. 
+   * <img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/netskope-v2/netskope-v2-11.png')} style={{border:'1px solid gray'}} alt="netskope-v2" width="400"/>
 1. Additionally, if need you can populate the query daemons.
 1. To make sure the resource is working, hover over the resource and then click the **TEST** that appears on the right.<br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/netskope-v2/netskope-v2-8.png')} style={{border:'1px solid gray'}} alt="netskope-v2" width="200"/> 
 1. You should receive a successful notification in the bottom right corner.<br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/netskope-v2/netskope-v2-10.png')} style={{border:'1px solid gray'}} alt="netskope-v2" width="400"/>