CAMEL-23250: Add security policy enforcement framework

[gnodet]

CAMEL-23250

Summary

Adds a security policy enforcement framework that enables runtime detection and enforcement of security-sensitive configuration options in Apache Camel.

Key changes

• New security attribute on @Metadata, @UriParam, @UriPath with categories: "secret", "insecure:ssl", "insecure:serialization", "insecure:dev"
• New insecureValue attribute to flag the specific value that triggers a security concern
• SecurityConfigurationProperties for policy configuration (camel.security.insecureSslPolicy, etc.)
• SecurityUtils / SecurityViolation in camel-util for violation scanning
• SecurityPolicyResult in camel-main for startup enforcement (fail/warn/allow)
• SecurityPolicyHealthCheck for runtime monitoring via health API
• Profile-aware defaults: dev/test profiles default to warn, prod defaults to fail
• Bidirectional derivation: secret=true implies security="secret" and vice versa
• All metadata generators updated to emit the security field in JSON schemas
• Build-time validation: BaseOptionModel.setSecurity() validates categories at build time — typos cause an immediate IllegalArgumentException
• Design proposal: proposals/security.adoc
• 73 component files annotated with insecure:ssl, insecure:serialization, insecure:dev categories

Follow-up work

1. Camel core — Add security = "secret" to all remaining secret = true parameters (~144 files not yet annotated)
2. Camel Spring Boot — Auto-configuration for camel.security.* properties
3. Camel Quarkus — Integration for camel.security.* properties

Test plan

• MainSecurityPolicyTest — parameterized tests for policy enforcement (fail/warn/allow) across profiles
• MainSecurityPolicyHealthCheckTest — health check reports violations
• SecurityUtilsTest — violation scanning logic
• Verify generated metadata includes security field
• CI build passes

[github-actions]

🌟 Thank you for your contribution to the Apache Camel project! 🌟
🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

• First-time contributors require MANUAL approval for the GitHub Actions to run
• You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot although they are normally detected and executed by CI.
• You can label PRs using build-all, build-dependents, skip-tests and test-dependents to fine-tune the checks executed by this PR.
• Build and test logs are available in the summary page. Only Apache Camel committers have access to the summary.

⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.

[sonarqubecloud]

Quality Gate passed

Issues
11 New issues
0 Accepted issues

Measures
0 Security Hotspots
88.6% Coverage on New Code
2.7% Duplication on New Code

See analysis details on SonarQube Cloud

[davsclaus]

CSB and CEQ would need some kind of integration with this as well - CSB have its own spring boot auto configuration that needs to have these new camel.security.xxx option as well.

All the components with secret = true needs to be analyses what kind they are.

[apupier]

@gnodet there are conflicts, a rebase is required

[gnodet]

Agreed on both points:

1. Components with secret = true: All 144 files with secret = true need to be analyzed and annotated with security = "secret". This PR focused on insecure:ssl, insecure:serialization, and insecure:dev categories — the secret migration will be done in a follow-up PR.

2. CSB and CEQ integration: The new camel.security.xxx configuration namespace needs Spring Boot auto-configuration in CSB and Quarkus integration in CEQ.

Follow-up plan (3 PRs):

• Camel core: Add security = "secret" to all remaining secret = true parameters (~144 files)
• Camel Spring Boot: Auto-configuration for camel.security.* properties
• Camel Quarkus: Integration for camel.security.* properties

Claude Code on behalf of Guillaume Nodet