From 80abf1d35925764a7e8f33332e342b542a0448fa Mon Sep 17 00:00:00 2001 From: Amee Lepcha Date: Tue, 28 Jan 2025 15:44:19 +0530 Subject: [PATCH 01/12] Update F5 BIG-IP Local Traffic Manager --- .../security-threat-detection/f5-big-ip-ltm.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/docs/integrations/security-threat-detection/f5-big-ip-ltm.md b/docs/integrations/security-threat-detection/f5-big-ip-ltm.md index ff3c0a82b9..e62144c52b 100644 --- a/docs/integrations/security-threat-detection/f5-big-ip-ltm.md +++ b/docs/integrations/security-threat-detection/f5-big-ip-ltm.md @@ -112,6 +112,23 @@ Now, using telemetry, we will define a [Sumo Logic sink](https://clouddocs.f5.co ```bash curl -k --user admin: -H "Accept: application/json" -H "Content-Type:application/json" -X POST -d@sumo.json https://:3/mgmt/shared/telemetry/declare | python -m json.tool ``` +:::note +Contact F5 Support if the above cURL commands return an error. +::: + +The logging profiles (LTM and ASM) created by AS3 in step 2 need to be assigned to the BIG-IP virtual server(s). Follow the steps below to begin collecting telemetry: + +**Associate LTM logging profile** + +1. From the BIG-IP console UI, navigate to **Local Traffic** > **Virtual Servers** > **Virtual Server List**.
console UI +1. Select and open the virtual server(s) to update their properties. Change the virtual server configuration setting from **Basic** to **Advanced** to expose the logging properties.
server config +1. Scroll down and assign the previously created LTM logging profile to the virtual server(s).
assign LTM logging profile +1. Scroll down and select **Update** to save the changes. + +**Associate ASM logging profile** + +1. After assigning the LTM logging profile to the virtual server, navigate to the top of the form in the BIG-IP console UI and then select the **Security** tab to access the virtual server’s security policy settings.
security +1. Enable logging and assign the previously created ASM logging profile, and then select **Update** to save the configuration changes.
assign ASM logging profil ## Installing the F5 - BIG-IP LTM app From 15f7856140b4f73abf3120c5bb03422550486823 Mon Sep 17 00:00:00 2001 From: Amee Lepcha Date: Tue, 28 Jan 2025 18:46:34 +0530 Subject: [PATCH 02/12] Update docs/integrations/security-threat-detection/f5-big-ip-ltm.md Co-authored-by: Jagadisha V <129049263+JV0812@users.noreply.github.com> --- docs/integrations/security-threat-detection/f5-big-ip-ltm.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/integrations/security-threat-detection/f5-big-ip-ltm.md b/docs/integrations/security-threat-detection/f5-big-ip-ltm.md index e62144c52b..6f62c95973 100644 --- a/docs/integrations/security-threat-detection/f5-big-ip-ltm.md +++ b/docs/integrations/security-threat-detection/f5-big-ip-ltm.md @@ -113,7 +113,7 @@ Now, using telemetry, we will define a [Sumo Logic sink](https://clouddocs.f5.co curl -k --user admin: -H "Accept: application/json" -H "Content-Type:application/json" -X POST -d@sumo.json https://:3/mgmt/shared/telemetry/declare | python -m json.tool ``` :::note -Contact F5 Support if the above cURL commands return an error. +Contact F5 support team if the above curl commands return an error. ::: The logging profiles (LTM and ASM) created by AS3 in step 2 need to be assigned to the BIG-IP virtual server(s). Follow the steps below to begin collecting telemetry: From d2540ae9d1c31dc92ea277ed6e16c257d7fb11aa Mon Sep 17 00:00:00 2001 From: Amee Lepcha Date: Tue, 28 Jan 2025 18:47:17 +0530 Subject: [PATCH 03/12] Update docs/integrations/security-threat-detection/f5-big-ip-ltm.md Co-authored-by: Jagadisha V <129049263+JV0812@users.noreply.github.com> --- docs/integrations/security-threat-detection/f5-big-ip-ltm.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/integrations/security-threat-detection/f5-big-ip-ltm.md b/docs/integrations/security-threat-detection/f5-big-ip-ltm.md index 6f62c95973..d8257d1edf 100644 --- a/docs/integrations/security-threat-detection/f5-big-ip-ltm.md +++ b/docs/integrations/security-threat-detection/f5-big-ip-ltm.md @@ -116,7 +116,7 @@ curl -k --user admin: -H "Accept: application/json" -H "Content-Type: Contact F5 support team if the above curl commands return an error. ::: -The logging profiles (LTM and ASM) created by AS3 in step 2 need to be assigned to the BIG-IP virtual server(s). Follow the steps below to begin collecting telemetry: +To being collecting telemetry, the logging profiles (LTM and ASM) created by AS3 in step 2 need to be assigned to the BIG-IP virtual server(s). **Associate LTM logging profile** From 021ac87063296d650fa665c63ce9e4fae8ae8f73 Mon Sep 17 00:00:00 2001 From: Amee Lepcha Date: Tue, 28 Jan 2025 18:47:30 +0530 Subject: [PATCH 04/12] Update docs/integrations/security-threat-detection/f5-big-ip-ltm.md Co-authored-by: Jagadisha V <129049263+JV0812@users.noreply.github.com> --- docs/integrations/security-threat-detection/f5-big-ip-ltm.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/integrations/security-threat-detection/f5-big-ip-ltm.md b/docs/integrations/security-threat-detection/f5-big-ip-ltm.md index d8257d1edf..71694f119c 100644 --- a/docs/integrations/security-threat-detection/f5-big-ip-ltm.md +++ b/docs/integrations/security-threat-detection/f5-big-ip-ltm.md @@ -118,7 +118,7 @@ Contact F5 support team if the above curl commands return an error. To being collecting telemetry, the logging profiles (LTM and ASM) created by AS3 in step 2 need to be assigned to the BIG-IP virtual server(s). -**Associate LTM logging profile** +Follow the below steps to associate LTM logging profile: 1. From the BIG-IP console UI, navigate to **Local Traffic** > **Virtual Servers** > **Virtual Server List**.
console UI 1. Select and open the virtual server(s) to update their properties. Change the virtual server configuration setting from **Basic** to **Advanced** to expose the logging properties.
server config From ccae5949113c6dde64874d945ff39fe0159373d1 Mon Sep 17 00:00:00 2001 From: Amee Lepcha Date: Tue, 28 Jan 2025 18:47:39 +0530 Subject: [PATCH 05/12] Update docs/integrations/security-threat-detection/f5-big-ip-ltm.md Co-authored-by: Jagadisha V <129049263+JV0812@users.noreply.github.com> --- docs/integrations/security-threat-detection/f5-big-ip-ltm.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/integrations/security-threat-detection/f5-big-ip-ltm.md b/docs/integrations/security-threat-detection/f5-big-ip-ltm.md index 71694f119c..229b70e2ab 100644 --- a/docs/integrations/security-threat-detection/f5-big-ip-ltm.md +++ b/docs/integrations/security-threat-detection/f5-big-ip-ltm.md @@ -125,7 +125,7 @@ Follow the below steps to associate LTM logging profile: 1. Scroll down and assign the previously created LTM logging profile to the virtual server(s).
assign LTM logging profile 1. Scroll down and select **Update** to save the changes. -**Associate ASM logging profile** +Follow the below steps to associate ASM logging profile: 1. After assigning the LTM logging profile to the virtual server, navigate to the top of the form in the BIG-IP console UI and then select the **Security** tab to access the virtual server’s security policy settings.
security 1. Enable logging and assign the previously created ASM logging profile, and then select **Update** to save the configuration changes.
assign ASM logging profil From 3d9cee358491698d4b5fddbe1201147de4cb43d3 Mon Sep 17 00:00:00 2001 From: Amee Lepcha Date: Tue, 28 Jan 2025 18:48:03 +0530 Subject: [PATCH 06/12] Update docs/integrations/security-threat-detection/f5-big-ip-ltm.md Co-authored-by: Jagadisha V <129049263+JV0812@users.noreply.github.com> --- docs/integrations/security-threat-detection/f5-big-ip-ltm.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/integrations/security-threat-detection/f5-big-ip-ltm.md b/docs/integrations/security-threat-detection/f5-big-ip-ltm.md index 229b70e2ab..997e6a6196 100644 --- a/docs/integrations/security-threat-detection/f5-big-ip-ltm.md +++ b/docs/integrations/security-threat-detection/f5-big-ip-ltm.md @@ -121,7 +121,7 @@ To being collecting telemetry, the logging profiles (LTM and ASM) created by AS3 Follow the below steps to associate LTM logging profile: 1. From the BIG-IP console UI, navigate to **Local Traffic** > **Virtual Servers** > **Virtual Server List**.
console UI -1. Select and open the virtual server(s) to update their properties. Change the virtual server configuration setting from **Basic** to **Advanced** to expose the logging properties.
server config +1. Select and open the virtual server(s) to update their properties. In the **Configuration** dropdown, change the virtual server configuration setting from **Basic** to **Advanced** to expose the logging properties.
server config 1. Scroll down and assign the previously created LTM logging profile to the virtual server(s).
assign LTM logging profile 1. Scroll down and select **Update** to save the changes. From 8085c174947060b243aac3db547a32017828c561 Mon Sep 17 00:00:00 2001 From: Amee Lepcha Date: Tue, 28 Jan 2025 18:48:14 +0530 Subject: [PATCH 07/12] Update docs/integrations/security-threat-detection/f5-big-ip-ltm.md Co-authored-by: Jagadisha V <129049263+JV0812@users.noreply.github.com> --- docs/integrations/security-threat-detection/f5-big-ip-ltm.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/integrations/security-threat-detection/f5-big-ip-ltm.md b/docs/integrations/security-threat-detection/f5-big-ip-ltm.md index 997e6a6196..2d1e9cc8a7 100644 --- a/docs/integrations/security-threat-detection/f5-big-ip-ltm.md +++ b/docs/integrations/security-threat-detection/f5-big-ip-ltm.md @@ -122,7 +122,7 @@ Follow the below steps to associate LTM logging profile: 1. From the BIG-IP console UI, navigate to **Local Traffic** > **Virtual Servers** > **Virtual Server List**.
console UI 1. Select and open the virtual server(s) to update their properties. In the **Configuration** dropdown, change the virtual server configuration setting from **Basic** to **Advanced** to expose the logging properties.
server config -1. Scroll down and assign the previously created LTM logging profile to the virtual server(s).
assign LTM logging profile +1. In the **Request Logging Profile**, select the previously created LTM logging profile to the virtual server(s).
assign LTM logging profile 1. Scroll down and select **Update** to save the changes. Follow the below steps to associate ASM logging profile: From 5a2b5e0545f1d230175cedaf2704a354fc99ad21 Mon Sep 17 00:00:00 2001 From: Amee Lepcha Date: Tue, 28 Jan 2025 18:48:24 +0530 Subject: [PATCH 08/12] Update docs/integrations/security-threat-detection/f5-big-ip-ltm.md Co-authored-by: Jagadisha V <129049263+JV0812@users.noreply.github.com> --- docs/integrations/security-threat-detection/f5-big-ip-ltm.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/integrations/security-threat-detection/f5-big-ip-ltm.md b/docs/integrations/security-threat-detection/f5-big-ip-ltm.md index 2d1e9cc8a7..2b047a4b63 100644 --- a/docs/integrations/security-threat-detection/f5-big-ip-ltm.md +++ b/docs/integrations/security-threat-detection/f5-big-ip-ltm.md @@ -123,7 +123,7 @@ Follow the below steps to associate LTM logging profile: 1. From the BIG-IP console UI, navigate to **Local Traffic** > **Virtual Servers** > **Virtual Server List**.
console UI 1. Select and open the virtual server(s) to update their properties. In the **Configuration** dropdown, change the virtual server configuration setting from **Basic** to **Advanced** to expose the logging properties.
server config 1. In the **Request Logging Profile**, select the previously created LTM logging profile to the virtual server(s).
assign LTM logging profile -1. Scroll down and select **Update** to save the changes. +1. Click **Update** to save the changes. Follow the below steps to associate ASM logging profile: From 881b5eb047eef1041fb0ec0f95d5e8b6813d9cc1 Mon Sep 17 00:00:00 2001 From: Amee Lepcha Date: Tue, 28 Jan 2025 18:48:55 +0530 Subject: [PATCH 09/12] Update docs/integrations/security-threat-detection/f5-big-ip-ltm.md Co-authored-by: Jagadisha V <129049263+JV0812@users.noreply.github.com> --- docs/integrations/security-threat-detection/f5-big-ip-ltm.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/integrations/security-threat-detection/f5-big-ip-ltm.md b/docs/integrations/security-threat-detection/f5-big-ip-ltm.md index 2b047a4b63..a5c99395d1 100644 --- a/docs/integrations/security-threat-detection/f5-big-ip-ltm.md +++ b/docs/integrations/security-threat-detection/f5-big-ip-ltm.md @@ -127,7 +127,7 @@ Follow the below steps to associate LTM logging profile: Follow the below steps to associate ASM logging profile: -1. After assigning the LTM logging profile to the virtual server, navigate to the top of the form in the BIG-IP console UI and then select the **Security** tab to access the virtual server’s security policy settings.
security +1. After assigning the LTM logging profile to the virtual server, navigate to the **Security** tab and select **Policies** to access the virtual server’s security policy settings.
security 1. Enable logging and assign the previously created ASM logging profile, and then select **Update** to save the configuration changes.
assign ASM logging profil ## Installing the F5 - BIG-IP LTM app From 71ae6fdf080252bd5348c6173f30a2d66dfa59aa Mon Sep 17 00:00:00 2001 From: Amee Lepcha Date: Tue, 28 Jan 2025 18:49:16 +0530 Subject: [PATCH 10/12] Update docs/integrations/security-threat-detection/f5-big-ip-ltm.md Co-authored-by: Jagadisha V <129049263+JV0812@users.noreply.github.com> --- docs/integrations/security-threat-detection/f5-big-ip-ltm.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/integrations/security-threat-detection/f5-big-ip-ltm.md b/docs/integrations/security-threat-detection/f5-big-ip-ltm.md index a5c99395d1..817d005c9a 100644 --- a/docs/integrations/security-threat-detection/f5-big-ip-ltm.md +++ b/docs/integrations/security-threat-detection/f5-big-ip-ltm.md @@ -128,7 +128,8 @@ Follow the below steps to associate LTM logging profile: Follow the below steps to associate ASM logging profile: 1. After assigning the LTM logging profile to the virtual server, navigate to the **Security** tab and select **Policies** to access the virtual server’s security policy settings.
security -1. Enable logging and assign the previously created ASM logging profile, and then select **Update** to save the configuration changes.
assign ASM logging profil +1. In the **Log Profile**, enable logging and assign the previously created ASM logging profile.
assign ASM logging profil +1. Click **Update** to save the configuration changes. ## Installing the F5 - BIG-IP LTM app From 8915dd20b82976842670d1c680f3178e26ac0886 Mon Sep 17 00:00:00 2001 From: Amee Lepcha Date: Tue, 28 Jan 2025 18:50:33 +0530 Subject: [PATCH 11/12] Update f5-big-ip-ltm.md --- docs/integrations/security-threat-detection/f5-big-ip-ltm.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/integrations/security-threat-detection/f5-big-ip-ltm.md b/docs/integrations/security-threat-detection/f5-big-ip-ltm.md index 817d005c9a..530f39d81e 100644 --- a/docs/integrations/security-threat-detection/f5-big-ip-ltm.md +++ b/docs/integrations/security-threat-detection/f5-big-ip-ltm.md @@ -116,7 +116,7 @@ curl -k --user admin: -H "Accept: application/json" -H "Content-Type: Contact F5 support team if the above curl commands return an error. ::: -To being collecting telemetry, the logging profiles (LTM and ASM) created by AS3 in step 2 need to be assigned to the BIG-IP virtual server(s). +To begin collecting telemetry, the logging profiles (LTM and ASM) created by AS3 in step 2 need to be assigned to the BIG-IP virtual server(s). Follow the below steps to associate LTM logging profile: @@ -206,4 +206,4 @@ import AppUpdate from '../../reuse/apps/app-update.md'; import AppUninstall from '../../reuse/apps/app-uninstall.md'; - \ No newline at end of file + From 8cfe0cbba48e25f6ca83eddaa9de29f6c10f5523 Mon Sep 17 00:00:00 2001 From: Amee Lepcha Date: Tue, 28 Jan 2025 18:58:24 +0530 Subject: [PATCH 12/12] Update f5-big-ip-ltm.md --- docs/integrations/security-threat-detection/f5-big-ip-ltm.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/integrations/security-threat-detection/f5-big-ip-ltm.md b/docs/integrations/security-threat-detection/f5-big-ip-ltm.md index 530f39d81e..051c7ad589 100644 --- a/docs/integrations/security-threat-detection/f5-big-ip-ltm.md +++ b/docs/integrations/security-threat-detection/f5-big-ip-ltm.md @@ -116,7 +116,7 @@ curl -k --user admin: -H "Accept: application/json" -H "Content-Type: Contact F5 support team if the above curl commands return an error. ::: -To begin collecting telemetry, the logging profiles (LTM and ASM) created by AS3 in step 2 need to be assigned to the BIG-IP virtual server(s). +To begin collecting telemetry, the logging profiles (LTM and ASM) created by AS3 in [step 2](#step-2-use-as3-declarative-language-to-define-a-logging-profile-on-big-ip) need to be assigned to the BIG-IP virtual server(s). Follow the below steps to associate LTM logging profile: