This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-website.git
The following commit(s) were added to refs/heads/main by this push:
new 0259dfbb docs(website): add "Secure out of the box" section to Trust
page (#1680) (#1706)
0259dfbb is described below
commit 0259dfbbc4c3c9c15e2b7c85a32af815cc2a2cf8
Author: Pratyush Adhikari <[email protected]>
AuthorDate: Fri Aug 7 15:42:40 2026 +0530
docs(website): add "Secure out of the box" section to Trust page (#1680)
(#1706)
* docs(website): add 'Secure out of the box' section to Trust page (#1680)
* Apply suggestions from code review
Co-authored-by: Copilot Autofix powered by AI
<[email protected]>
---------
Co-authored-by: Claus Ibsen <[email protected]>
Co-authored-by: Copilot Autofix powered by AI
<[email protected]>
---
content/security/_index.md | 7 +++++++
content/trust/_index.md | 36 ++++++++++++++++++++++++++++++++++++
2 files changed, 43 insertions(+)
diff --git a/content/security/_index.md b/content/security/_index.md
index 210e4d9e..f1e45d58 100644
--- a/content/security/_index.md
+++ b/content/security/_index.md
@@ -26,6 +26,13 @@ Every Camel release since 4.0.3 ships with PGP-signed
CycloneDX SBOMs that list
enabling supply chain risk analysis alongside the CVE advisories below.
See [Generating SBOMs](/manual/sbom.html) for details.
+## Security Policy Enforcement
+
+Camel includes built-in Security Policy Enforcement that validates
security-sensitive configuration
+during startup and can prevent insecure configurations from reaching
production.
+
+See [Security Policy Enforcement](/manual/security-policy.html) for
configuration details.
+
## Reporting new security problems with Apache Camel
The Apache Software Foundation takes a very active stance in eliminating
security problems.
diff --git a/content/trust/_index.md b/content/trust/_index.md
index a3a03793..ecf4043c 100644
--- a/content/trust/_index.md
+++ b/content/trust/_index.md
@@ -17,6 +17,11 @@ keywords:
- apache software foundation
- enterprise integration
- production
+- secure by default
+- security policy enforcement
+- startup validation
+- production mode
+- insecure configuration
---
Apache Camel has been running in production since 2007. Some of the largest
organizations in
@@ -252,6 +257,37 @@ Executive Order 14028, the [SBOM box is already
checked](/blog/2026/06/camel-sbo
{{< div "box" >}}
+<a href="/manual/security-policy.html" class="icon" title="Secure out of the
box — runtime security enforcement">{{< icon "security" "Padlock" >}}</a>
+
+{{< div "content" >}}
+
+## Secure out of the box
+
+Apache Camel doesn't just fix vulnerabilities after they are found — it
actively prevents insecure
+configuration from reaching production. Every option in the Camel component
catalog carries
+machine-readable security metadata that identifies whether it is
security-sensitive and whether
+enabling it introduces a known risk. At startup, Camel uses this metadata to
validate
+configuration before a single message is processed.
+
+Camel validates security-sensitive configuration at startup, covering secrets,
transport security,
+serialization, and production-only settings. Components are designed with
secure defaults so that
+the safest configuration is also the easiest one to use.
+
+In **production mode** (`camel.main.profile = prod`), the global default is
`fail`: the application
+refuses to start with any insecure configuration unless explicitly overridden.
This is a hard
+guardrail, not a warning that can be scrolled past. In the default
(no-profile) mode, violations
+are logged as warnings so existing applications are not broken.
+
+<p>
+<a class="button dark" href="/manual/security-policy.html">Security Policy
Enforcement</a>
+</p>
+
+{{< /div >}}
+
+{{< /div >}}
+
+{{< div "box" >}}
+
<a href="/blog/2026/06/camel-ai-trained/" class="icon" title="AI-ready
integration">{{< icon "sparkle" "Sparkle" >}}</a>
{{< div "content" >}}
