Fix broken links and add missing file

Author: cwatson-cat

.openpublishing.redirection.sentinel.json

@@ -1207,7 +1207,7 @@
         },
         {
             "source_path_from_root": "/articles/sentinel/data-connectors/zero-networks-segment-audit-function-using-azure-functions.md",
-            "redirect_url": "/azure/sentinel/data-connectors/zero-networks-segment-audit-function",
+            "redirect_url": "/azure/sentinel/data-connectors/zero-networks-segment-audit",
             "redirect_document_id": true
         },
 {

articles/sentinel/TOC.yml

@@ -418,8 +418,6 @@
       href: data-connectors/box.md
     - name: Cisco Application Centric Infrastructure
       href: data-connectors/cisco-application-centric-infrastructure.md
-    - name: Cisco ASA via Legacy Agent
-      href: data-connectors/cisco-asa-via-legacy-agent.md
     - name: Cisco ASA/FTD via AMA (Preview)
       href: data-connectors/cisco-asa-ftd-via-ama.md
     - name: Cisco Duo Security (using Azure Functions)

articles/sentinel/data-connectors-reference.md

@@ -130,7 +130,6 @@ Data connectors are available as part of the following offerings:
 ## Cisco
 
 - [Cisco Application Centric Infrastructure](data-connectors/cisco-application-centric-infrastructure.md)
-- [Cisco ASA via Legacy Agent](data-connectors/cisco-asa-via-legacy-agent.md)
 - [Cisco ASA/FTD via AMA (Preview)](data-connectors/cisco-asa-ftd-via-ama.md)
 - [Cisco Duo Security (using Azure Functions)](data-connectors/cisco-duo-security.md)
 - [Cisco Identity Services Engine](data-connectors/cisco-identity-services-engine.md)

articles/sentinel/data-connectors/cyberarkaudit.md

@@ -0,0 +1,138 @@
+---
+title: "CyberArkAudit (using Azure Functions) connector for Microsoft Sentinel"
+description: "Learn how to install the connector CyberArkAudit (using Azure Functions) to connect your data source to Microsoft Sentinel."
+author: cwatson-cat
+ms.topic: how-to
+ms.date: 04/25/2024
+ms.service: microsoft-sentinel
+ms.author: cwatson
+---
+
+# CyberArkAudit (using Azure Functions) connector for Microsoft Sentinel
+
+The [CyberArk Audit](https://docs.cyberark.com/Audit/Latest/en/Content/Resources/_TopNav/cc_Home.htm) data connector provides the capability to retrieve security event logs of the CyberArk Audit service and more events into Microsoft Sentinel through the REST API. The connector provides ability to get events which helps to examine potential security risks, analyze your team's use of collaboration, diagnose configuration problems and more.
+
+This is autogenerated content. For changes, contact the solution provider.
+
+## Connector attributes
+
+| Connector attribute | Description |
+| --- | --- |
+| **Application settings** | CyberArkAuditUsername<br/>CyberArkAuditPassword<br/>CyberArkAuditServerURL<br/>WorkspaceID<br/>WorkspaceKey<br/>logAnalyticsUri (optional) |
+| **Azure function app code** | https://aka.ms/sentinel-CyberArkAudit-functionapp |
+| **Log Analytics table(s)** | CyberArk_AuditEvents_CL<br/> |
+| **Data collection rules support** | Not currently supported |
+| **Supported by** | [CyberArk Support](https://www.cyberark.com/services-support/technical-support-contact/) |
+
+## Query samples
+
+**CyberArk Audit Events - All Activities.**
+
+   ```kusto
+CyberArkAudit
+ 
+   | sort by TimeGenerated desc
+   ```
+
+
+
+## Prerequisites
+
+To integrate with CyberArkAudit (using Azure Functions) make sure you have: 
+
+- **Microsoft.Web/sites permissions**: Read and write permissions to Azure Functions to create a Function App is required. [See the documentation to learn more about Azure Functions](/azure/azure-functions/).
+- **Audit REST API Connections details and Credentials**: **OauthUsername**, **OauthPassword**, **WebAppID**, **AuditApiKey**, **IdentityEndpoint** and **AuditApiBaseUrl** are required for making API calls.
+
+
+## Vendor installation instructions
+
+
+> [!NOTE]
+   >  This connector uses Azure Functions to connect to the Azure Blob Storage API to pull logs into Microsoft Sentinel. This might result in additional costs for data ingestion and for storing data in Azure Blob Storage costs. Check the [Azure Functions pricing page](https://azure.microsoft.com/pricing/details/functions/) and [Azure Blob Storage pricing page](https://azure.microsoft.com/pricing/details/storage/blobs/) for details.
+
+
+> [!NOTE]
+   >  API authorization key(s) or token(s) are securely stored in Azure Key Vault. Azure Key Vault provides a secure mechanism to store and retrieve key values.
+
+
+**STEP 1 - Configuration steps for the CyberArk Audit SIEM Integration**
+
+ Follow the instructions to obtain connection details and credentials.
+
+1. Use Username and Password for your CyberArk Audit account.
+
+
+**STEP 2 - Choose ONE from the following two deployment options to deploy the connector and the associated Azure Function**
+
+>**IMPORTANT:** Before deploying the CyberArk Audit data connector, have the Workspace Name and Workspace Location (can be copied from the following).
+
+   Workspace Name
+
+   Workspace Location
+
+Option 1 - Azure Resource Manager (ARM) Template
+
+Use this method for automated deployment of the CyberArk Audit data connector using an ARM Template.
+
+1. Click the **Deploy to Azure** button below. 
+
+	[![Deploy To Azure](https://aka.ms/deploytoazurebutton)](https://aka.ms/sentinel-CyberArkAuditAPI-azuredeploy)
+2. Select the preferred **Subscription**, **Resource Group** and **Location**. 
+> **NOTE:** Within the same resource group, you can't mix Windows and Linux apps in the same region. Select existing resource group without Windows apps in it or create new resource group.
+3. Enter the **CyberArkAuditUsername**, **CyberArkAuditPassword**, **CyberArkAuditServerURL**  and deploy. 
+4. Mark the checkbox labeled **I agree to the terms and conditions stated above**. 
+5. Click **Purchase** to deploy.
+
+Option 2 - Manual Deployment of Azure Functions
+
+Use the following step-by-step instructions to deploy the CyberArk Audit data connector manually with Azure Functions (Deployment via Visual Studio Code).
+
+
+**1. Deploy a Function App**
+
+> **NOTE:** You will need to [prepare VS code](/azure/azure-functions/functions-create-first-function-python#prerequisites) for Azure function development.
+
+1. Download the [Azure Function App](https://aka.ms/sentinel-CyberArkAudit-functionapp) file. Extract archive to your local development computer.
+2. Start VS Code. Choose File in the main menu and select Open Folder.
+3. Select the top level folder from extracted files.
+4. Choose the Azure icon in the Activity bar, then in the **Azure: Functions** area, choose the **Deploy to function app** button.
+If you aren't already signed in, choose the Azure icon in the Activity bar, then in the **Azure: Functions** area, choose **Sign in to Azure**
+If you're already signed in, go to the next step.
+5. Provide the following information at the prompts:
+
+	a. **Select folder:** Choose a folder from your workspace or browse to one that contains your function app.
+
+	b. **Select Subscription:** Choose the subscription to use.
+
+	c. Select **Create new Function App in Azure** (Don't choose the Advanced option)
+
+	d. **Enter a globally unique name for the function app:** Type a name that is valid in a URL path. The name you type is validated to make sure that it's unique in Azure Functions. (e.g. CyberArkXXXXX).
+
+	e. **Select a runtime:** Choose Python 3.8.
+
+	f. Select a location for new resources. For better performance and lower costs choose the same [region](https://azure.microsoft.com/regions/) where Microsoft Sentinel is located.
+
+6. Deployment will begin. A notification is displayed after your function app is created and the deployment package is applied.
+7. Go to Azure Portal for the Function App configuration.
+
+
+**2. Configure the Function App**
+
+1. In the Function App, select the Function App Name and select **Configuration**.
+2. In the **Application settings** tab, select ** New application setting**.
+3. Add each of the following application settings individually, with their respective string values (case-sensitive): 
+	- CyberArkAuditUsername
+	- CyberArkAuditPassword
+	- CyberArkAuditServerURL
+	- WorkspaceID
+	- WorkspaceKey
+	- logAnalyticsUri (optional)
+   
+    Use logAnalyticsUri to override the log analytics API endpoint for dedicated cloud. For example, for public cloud, leave the value empty; for Azure GovUS cloud environment, specify the value in the following format: `https://<CustomerId>.ods.opinsights.azure.us`.
+4. Once all application settings have been entered, click **Save**.
+
+
+
+## Next steps
+
+For more information, go to the [related solution](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/cyberark.cyberark_audit_sentinel?tab=Overview) in the Azure Marketplace.