Security documentation (#2475)

* docs(common): add security docs

* chore(common): secrity docs polishment

* Update security/faq.md

Co-authored-by: Dimo Dimov <961014+dimodi@users.noreply.github.com>

* Update security/faq.md

Co-authored-by: Dimo Dimov <961014+dimodi@users.noreply.github.com>

* Update security/faq.md

Co-authored-by: Dimo Dimov <961014+dimodi@users.noreply.github.com>

* Update security/faq.md

Co-authored-by: Dimo Dimov <961014+dimodi@users.noreply.github.com>

* Update security/faq.md

Co-authored-by: Dimo Dimov <961014+dimodi@users.noreply.github.com>

* Update security/overview.md

Co-authored-by: Dimo Dimov <961014+dimodi@users.noreply.github.com>

* Update security/faq.md

Co-authored-by: Dimo Dimov <961014+dimodi@users.noreply.github.com>

* Update security/overview.md

Co-authored-by: Dimo Dimov <961014+dimodi@users.noreply.github.com>

* Update security/overview.md

Co-authored-by: Dimo Dimov <961014+dimodi@users.noreply.github.com>

* Update security/overview.md

Co-authored-by: Dimo Dimov <961014+dimodi@users.noreply.github.com>

* Update security/overview.md

Co-authored-by: Dimo Dimov <961014+dimodi@users.noreply.github.com>

* Update security/overview.md

Co-authored-by: Dimo Dimov <961014+dimodi@users.noreply.github.com>

* Update security/faq.md

* Update security/faq.md

* Update security/faq.md

* Update security/faq.md

* Update security/faq.md

---------

Co-authored-by: Dimo Dimov <961014+dimodi@users.noreply.github.com>

_config.yml

@@ -42,19 +42,22 @@ navigation:
      "accessibility":
         title: "Accessibility"
         position: 17
+     "security":
+        title: "Security"
+        position: 18       
      "*deployment":
         title: "Deployment"
-        position: 18
+        position: 19
      "upgrade":
         title: "Upgrade"
-        position: 19
+        position: 21
      "upgrade/breaking-changes":
         title: "Breaking Changes"
      "upgrade/rendering-changes":
         title: "Rendering Changes"
      "how-to":
         title: "How To"
-        position: 20
+        position: 23
      "getting-started/vs-integration":
         title: "Visual Studio Integration"
         position: 25

_contentTemplates/editor/general.md

@@ -1,6 +1,6 @@
 #app-must-sanitize-content
 
-The application must sanitize the content before passing it to the editor and, optionally, before saving it to its storage after obtaining it from the editor. It is up to the application to ensure there is no malicious content (such as input sanitization, XSS attack prevention and other security concerns).
+The application must sanitize the content before passing it to the Editor and, optionally, before saving it to its storage after obtaining it from the Editor. It is up to the application to ensure there is no malicious content (such as input sanitization, XSS attack prevention and other security concerns).
 
 #end
 

components/editor/overview.md

@@ -56,7 +56,10 @@ The Blazor HTML Editor interacts with its content (value) like all standard comp
 
 Be aware that [the Editor and the browser treat empty paragraphs differently]({%slug editor-kb-missing-br-tags-in-value%}).
 
->important @[template](/_contentTemplates/editor/general.md#app-must-sanitize-content)
+## Security
+
+@[template](/_contentTemplates/editor/general.md#app-must-sanitize-content)
+
 
 ## Validation
 

security/faq.md

@@ -0,0 +1,71 @@
+---
+title: FAQ
+page_title: FAQ
+description: Find answers to common questions about securing Telerik UI for Blazor components, including how to report vulnerabilities, handle third-party dependencies, and receive security fixes.
+slug: security-faq
+tags: telerik, blazor, security
+published: True
+position: 3
+---
+
+# Frequently Asked Questions (FAQ)
+
+This article provides essential information and resources to help you secure Telerik UI for Blazor components. This FAQ provides guidance on the Progress security processes, no matter if you need to report vulnerabilities, manage third-party dependencies, or understand how security fixes are delivered. Explore best practices and learn how Progress ensures the highest level of security for its products, from vulnerability reporting to compliance with industry standards.
+
+## How can I submit a security vulnerability report?
+
+If you have identified a potential security vulnerability in a Telerik or Kendo UI product, you can report it through the following channels:
+
+- **For Progress Customers**: Submit a security report by opening a support ticket through the [Technical Support Center](https://www.telerik.com/account/support-center). Provide detailed information, including the steps to reproduce the issue and any relevant reports or screenshots.
+
+- **For Security Researchers**: Ethical hackers and security researchers can report vulnerabilities through our [Bugcrowd Vulnerability Disclosure Program](https://bugcrowd.com/engagements/whatsupgold-vdp). This platform ensures that security issues are addressed efficiently and transparently.
+
+We will review the report and follow up in line with our security processes, making every effort to resolve confirmed vulnerabilities in a timely manner.
+
+---
+
+## What if I am using a third-party scanning tool and want Progress' assessment?
+
+As a client, you can open a support ticket through the [Technical Support Center](https://www.telerik.com/account/support-center) for the respective product and submit detailed information, including scan reports (PDF/Word/Excel/Screenshot) triggered against a no-minified version of the scripts and steps to reproduce or evidence of the issue. Our team will review and respond accordingly. We treat Security Vulnerability reports with **highest priority** and we engage with our internal Security Champions for revisions.
+
+>tip We recommend running the scan against the latest product version, as the problem may have already been resolved. 
+
+---
+
+## What is Progress' policy on handling third-party dependencies?
+
+Progress uses leading commercial tools to automatically monitor and update third-party dependencies in our Telerik and Kendo GitHub projects. Alerts are set up for all GitHub-hosted products, and any identified vulnerable dependencies are addressed by the repository owners and our dedicated security team.
+
+Our definition of "done" includes successful builds that are scanned using top security scanning tools, and the resolution of any security alerts.
+
+---
+
+## Is security integrated into the CI pipeline?
+
+Yes, for example, our CI builds use some of the leading security scanning tools to ensure that new code commits do not introduce vulnerabilities or insecure code.
+
+---
+
+## How does Progress prioritize security reports?
+
+We prioritize security vulnerability reports with the highest urgency. When we receive an inquiry or vulnerability report, we analyze the issue to determine whether it's a false positive or a valid concern. If the report is confirmed as valid, we assess its severity using the CVSS (Common Vulnerability Scoring System) and release a patch based on the severity level.
+
+---
+
+## How are security fixes shipped?
+
+Security fixes are typically included in the next product release. Similar to the bugfixes policy, we maintain and commit to support the latest version of the product. That said, if you want to benefit from a security fix, you would need to upgrade to the version where the fix exists.
+
+---
+
+## How am I notified about security fixes?
+
+Once a vulnerability is fixed, we aim to release a patched version of the product. Depending on the severity of the issue, we may notify customers through CVE publications, email, blog posts, KB articles, or Release Notes for the specific product.
+
+---
+
+## Does Progress Telerik have any security certifications or accreditations, such as SOC 2 or other industry-recognized standards?
+
+Yes, Progress and DevTools products perform annual SOC 2 compliance, which validates our commitment to security, confidentiality, and privacy. You can find more information about our compliance on the [Progress Trust Center](https://www.progress.com/trust-center). Additionally, we align our security practices with industry-leading frameworks to maintain and continually improve our high security standards.
+
+      

security/overview.md

@@ -0,0 +1,88 @@
+---
+title: Overview
+page_title: Overview
+description: Learn how to secure Telerik UI for Blazor components and your Web Forms app with best practices, vulnerability reporting, and component-specific security guidelines.
+slug: security-overview
+tags: telerik, blazor, security, xss, owasp, csp
+published: True
+position: 1
+---
+
+# Security
+
+In today's world, security is more critical than ever. At Progress, we prioritize our customers' security, ensuring that our products are built with a strong foundation to safeguard their data and operations. We are committed to identifying and addressing potential vulnerabilities to provide our clients with the highest level of protection and confidence in our products.
+
+## Purpose of this Article
+
+This article covers common security-related questions, best practices, and the tools and processes we use to ensure the security of our products. It also outlines how customers and security researchers can report security issues, including our processes to mitigate risks. We provide guidance for submitting security reports through technical support or Bugcrowd, ensuring a clear pathway for identifying and addressing security concerns.
+
+## Reporting Security Vulnerabilities
+
+Whether you're a customer encountering an issue or a security researcher, we have processes to ensure a swift response and evaluation. Below are the steps for Progress customers and security researchers to report potential security vulnerabilities:
+
+### For Progress Customers
+
+At Progress, we work diligently to identify and fix security vulnerabilities in our products. Customers who believe they have identified a security issue should contact Technical Support for an evaluation. This allows us to document the issue and have our engineering teams confirm and address it as needed. Customers can submit reports through our support center:
+
+- [Technical Support](https://www.telerik.com/account/support-center)
+- [Contact Us](https://www.telerik.com/account/support-center/contact-us/technical-support)
+
+### For Security Researchers
+
+We value the contributions of security researchers and ethical hackers. If a researcher identifies a potential vulnerability, they can submit it via our [Bugcrowd](https://bugcrowd.com/engagements/devtools-vdp) platform. We aim to meet the following response times:
+
+| Type of Response | SLO (in business days) |
+|------------------|------------------------|
+| First Response    | 7 days                 |
+| Time to Triage    | 10 days                |
+| Time to Resolution| Depends on severity    |
+
+For more information, visit:
+
+- [Bugcrowd Vulnerability Disclosure Program](https://bugcrowd.com/engagements/devtools-vdp)
+- [Progress Trust Center](https://www.progress.com/trust-center)
+- [Vulnerability Reporting Policy](https://www.progress.com/trust-center/vulnerability-reporting-policy)
+
+
+## What We Do to Mitigate Risk
+
+Our dedicated security team is comprised of experienced developers and security experts—our "Security Champions". They review all web, desktop, and mobile products technologies for potential vulnerabilities. These vulnerabilities may be internally identified, reported by third-party tools, or flagged externally.
+
+We actively manage the following strategies to mitigate risks:
+
+### Prevention
+
+Our primary goal is to prevent security issues before product delivery. We use the following prevention techniques:
+
+- **Internal Logging**: Every potential security issue is logged, researched, tested, and verified. Issues deemed valid are assessed using a CVSS score, with critical issues prioritized.
+- **Third-Party Static Analysis Testing**: We utilize some of the leading security scanning tools in the market to scan for vulnerabilities in our software code. Regular scans are conducted, and results are reviewed to address vulnerabilities and mitigate false positives.
+
+
+## Third-Party Dependency Handling
+
+We leverage leading commercial tools to automatically monitor and update third-party dependencies in our Telerik and Kendo GitHub projects, ensuring they remain secure and up-to-date. Alerts are enabled for all GitHub-hosted products, and the identified vulnerable dependencies are addressed by the repository code owners and security champions.
+
+>Note: Our definition of "Done" includes successful builds that are scanned using top security scanning tools, and the resolution of any security alerts.
+
+
+## Content Security Compliance
+
+Content Security Policy (CSP) is a critical security measure that helps detect and mitigate the risks of content injection vulnerabilities, such as cross-site scripting (XSS) and data injection attacks. Telerik UI for Blazor components are designed to be CSP-compliant, ensuring secure integration into customer projects.
+
+For more detailed information on CSP compliance, refer to the [Telerik UI for Blazor Content Security Policy]({%slug troubleshooting-csp%}) article.
+
+This resource provides guidelines on how to configure your Blazor application to comply with CSP requirements when using the Telerik UI for Blazor components.
+
+## OWASP Top 10 Alignment
+
+We closely monitor the [OWASP Top 10](https://owasp.org/www-project-top-ten/) list of security risks and align our security practices with these industry-leading standards. Regular updates ensure that our products address evolving security threats and vulnerabilities.
+
+## Telerik UI for Blazor Component-Specific Security Guidelines
+
+The following resources outline best practices and recommendations for securing the corresponding component and mitigating potential risks:
+
+* [Editor - Security Guidelines]({%slug editor-overview%}#security)
+* [Upload - Security Guidelines]({%slug upload-overview%}#security)
+
+For more detailed answers to common security-related questions, please refer to our [Security FAQ page]({%slug security-faq%}).      
+