Copilot commented on code in PR #1706:
URL: https://github.com/apache/camel-website/pull/1706#discussion_r3650731136


##########
content/trust/_index.md:
##########
@@ -243,6 +248,34 @@ 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.
+

Review Comment:
   The new paragraph has an unusually long line compared to the rest of this 
file, which is consistently hard-wrapped. Please wrap this text to keep the 
markdown readable and consistent with the existing style.



##########
content/security/_index.md:
##########
@@ -26,6 +26,12 @@ 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.

Review Comment:
   This sentence is significantly longer than surrounding lines in this 
document (which are hard-wrapped). Wrapping it improves readability and keeps 
formatting consistent.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to