From c66f0c364e0ec4c906d89cad356010ee6ac46ffd Mon Sep 17 00:00:00 2001 From: "hyperlint-ai[bot]" <154288675+hyperlint-ai[bot]@users.noreply.github.com> Date: Tue, 25 Feb 2025 01:05:04 +0000 Subject: [PATCH 1/2] Fix issue: WorkspaceTaskSubType.META_DESCRIPTION --- .../saas-security-overview.mdx | 16 +--------------- 1 file changed, 1 insertion(+), 15 deletions(-) diff --git a/src/content/docs/learning-paths/secure-internet-traffic/secure-saas-applications/saas-security-overview.mdx b/src/content/docs/learning-paths/secure-internet-traffic/secure-saas-applications/saas-security-overview.mdx index 96381cd05867a4..66b37c9cd16721 100644 --- a/src/content/docs/learning-paths/secure-internet-traffic/secure-saas-applications/saas-security-overview.mdx +++ b/src/content/docs/learning-paths/secure-internet-traffic/secure-saas-applications/saas-security-overview.mdx @@ -1,15 +1 @@ ---- -title: SaaS security overview -pcx_content_type: learning-unit -sidebar: - order: 1 - ---- - -The concept of SaaS (software-as-a-service) security is top of mind for many security organizations but is not explicitly defined. When organizations approach Cloudflare for help securing their SaaS apps, it can mean a number of different things with a number of ideal outcomes. Cloudflare distills SaaS security into three key concepts: - -1. Better protection for the front door of your SaaS applications with considerations for both managed and unmanaged endpoint access. -2. Assurances for the ability to apply inline security tooling. In other words, we ensure the ability to apply restrictions on file uploads/downloads, the ability to access administrative targets, and the application of policies to prevent or detect data loss. Managing distinct policies for hundreds (on average) of SaaS apps means inline security will always meaningfully drift. -3. Visibility and control for your critical SaaS applications whether or not users are actively engaging with them (also known as out-of-band). This concept becomes most critical when you have limited ability to apply inline policy using TLS inspection and other methods. - -Cloudflare offers multiple solutions that achieve and sometimes overlap with all three of the defined concepts. Through combinations of Access for SaaS identity proxy, WARP with dedicated IP addresses, Browser Isolation, and CASB API, Cloudflare helps define and address any potential SaaS security goals. +---\ntitle: SaaS security overview\npcx_content_type: learning-unit\ndescription: Understand SaaS security with Cloudflare's three key concepts: front door protection, inline security tooling, and visibility control for critical apps.\nsidebar:\n order: 1\n\n---\n\nThe concept of SaaS (software-as-a-service) security is top of mind for many security organizations but is not explicitly defined. When organizations approach Cloudflare for help securing their SaaS apps, it can mean a number of different things with a number of ideal outcomes. Cloudflare distills SaaS security into three key concepts:\n\n1. Better protection for the front door of your SaaS applications with considerations for both managed and unmanaged endpoint access.\n2. Assurances for the ability to apply inline security tooling. In other words, we ensure the ability to apply restrictions on file uploads/downloads, the ability to access administrative targets, and the application of policies to prevent or detect data loss. Managing distinct policies for hundreds (on average) of SaaS apps means inline security will always meaningfully drift.\n3. Visibility and control for your critical SaaS applications whether or not users are actively engaging with them (also known as out-of-band). This concept becomes most critical when you have limited ability to apply inline policy using TLS inspection and other methods.\n\nCloudflare offers multiple solutions that achieve and sometimes overlap with all three of the defined concepts. Through combinations of Access for SaaS identity proxy, WARP with dedicated IP addresses, Browser Isolation, and CASB API, Cloudflare helps define and address any potential SaaS security goals. From ae6728223b31e593932d537068b4574b31d6e3bc Mon Sep 17 00:00:00 2001 From: "hyperlint-ai[bot]" <154288675+hyperlint-ai[bot]@users.noreply.github.com> Date: Tue, 25 Feb 2025 01:05:05 +0000 Subject: [PATCH 2/2] Fix issue: WorkspaceTaskSubType.META_DESCRIPTION --- .../secure-saas-applications/sso-front-door.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/src/content/docs/learning-paths/secure-internet-traffic/secure-saas-applications/sso-front-door.mdx b/src/content/docs/learning-paths/secure-internet-traffic/secure-saas-applications/sso-front-door.mdx index 1ee7670d8add57..017f39d9f3d4bb 100644 --- a/src/content/docs/learning-paths/secure-internet-traffic/secure-saas-applications/sso-front-door.mdx +++ b/src/content/docs/learning-paths/secure-internet-traffic/secure-saas-applications/sso-front-door.mdx @@ -1,6 +1,7 @@ --- title: Single sign-on front door controls pcx_content_type: learning-unit +description: Implement SSO front door controls with Cloudflare to enhance SaaS app security. Integrate with IdPs, enforce policies, and manage user access efficiently. sidebar: order: 2