Conversation
Run CWS and CSPM without the security agent: - DD_RUNTIME_SECURITY_CONFIG_ENABLED=true enables runtime security in system-probe.yaml with direct_send_from_system_probe, and leaves security-agent.yaml alone. - DD_COMPLIANCE_CONFIG_ENABLED=true enables compliance_config with run_in_system_probe in datadog.yaml. An existing security-agent.yaml gets direct_send_from_system_probe so it stops sending CWS events, but it is never created.
lebauce
force-pushed
the
lebauce/no-security-agent
branch
from
September 23, 2026 09:52
50bfd34 to
b6b7b45
Compare
❌ ErrorsYour PR has failed checks. Please review the issues below and take necessary action before merging. 🚦 1 Pipeline job failed
ℹ️ InfoNo other issues found (see more)🧪 All tests passed Useful? React with 👍 / 👎 This comment will be updated automatically if new data arrives.🔗 Commit SHA: b6b7b45 | Docs | View more details | Give us feedback! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Lets CWS and CSPM run in system-probe instead of the security agent.
With
DD_NO_SECURITY_AGENT_INSTALLset:DD_RUNTIME_SECURITY_CONFIG_ENABLED=true→system-probe.yamlgetsruntime_security_config: {enabled: true, direct_send_from_system_probe: true}.DD_COMPLIANCE_CONFIG_ENABLED=true→datadog.yamlgetscompliance_config: {enabled: true, run_in_system_probe: true}.security-agent.yamlis never created. If it already exists, it gets bothruntime_security_config.direct_send_from_system_probeandcompliance_config.run_in_system_probe: thedatadog-agent-securityservice starts as soon as that file exists, so the security agent needs to read those to know it has nothing to do and stop.manage_security_configtakes the new flag as an argument, so both paths stay in one place. Also reported in the install telemetry asno_security_agent.Covered by unit tests and a new
TestInstallNoSecurityAgentSuitee2e suite (picked up by the existing catch-all e2e jobs).