You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
tl;dr: I recommend enabling agentless deployment for Sysdig at the package level, but documenting it as API/CEL-focused support while keeping Alerts (http_endpoint) as agent-based behavior. This matches existing patterns in this repo for mixed-input integrations.
Recommendation
Enable deployment_modes.agentless in packages/sysdig/manifest.yml (beta metadata included), keep current inputs unchanged, and update Sysdig docs to clearly separate:
Agentless-capable API polling streams (event, cspm, vulnerability via CEL)
Agent-based webhook stream (alerts via http_endpoint)
Findings
packages/sysdig/manifest.yml:41-51 has one policy template with http_endpoint + cel inputs and nodeployment_modes.
packages/sysdig/data_stream/alerts/manifest.yml:4-25 is input: http_endpoint and requires listener settings (listen_address, listen_port) — this is inbound webhook style.
packages/sysdig/data_stream/event/manifest.yml:4-8, packages/sysdig/data_stream/cspm/manifest.yml:4-8, packages/sysdig/data_stream/vulnerability/manifest.yml:4-8 are all input: cel API polling streams.
packages/sysdig/docs/README.md:23-27 currently has only Agent-based installation; :33-39 makes Alerts webhook sound mandatory before API setup.
Repo precedent for agentless metadata:
packages/forgerock/manifest.yml:20-28 (deployment_modes.default + deployment_modes.agentless with release/org/division/team)
packages/darktrace/manifest.yml:27-35 same structure.
Repo precedent for mixed push + polling inputs with agentless enabled:
packages/zscaler_zia/manifest.yml:72-80 enables agentless at policy level,
while still containing tcp/http_endpoint (:82, :129) and cel (:191) inputs.
Docs precedent for agentless language:
packages/forgerock/docs/README.md:5-8 has a standard “Agentless Enabled Integration” section and beta/cloud caveat.
GitHub context limitation: issue/related-item bodies are integrity-filtered in this environment, so this triage is based on repository evidence only.
Verification
I ran workspace commands to verify current package/test layout and local tooling availability:
$ ls -1 packages/sysdig/data_stream/*/_dev/test/system/test-default-config.yml
packages/sysdig/data_stream/alerts/_dev/test/system/test-default-config.yml
packages/sysdig/data_stream/cspm/_dev/test/system/test-default-config.yml
packages/sysdig/data_stream/event/_dev/test/system/test-default-config.yml
packages/sysdig/data_stream/vulnerability/_dev/test/system/test-default-config.yml
$ elastic-package check -C packages/sysdig -v
bash: elastic-package: command not found
Detailed Action Plan
Update packages/sysdig/manifest.yml under policy_templates[0] (:41+) to add:
deployment_modes.default.enabled: true
deployment_modes.agentless.enabled: true
deployment_modes.agentless.release: beta
deployment_modes.agentless.organization/division/team (follow team convention used by forgerock/darktrace).
Bump Sysdig package version (minor bump recommended for capability addition), and add a changelog entry in packages/sysdig/changelog.yml as type: enhancement.
Add agentless section (using established wording/caveats similar to forgerock/docs/README.md:5-8).
Split setup guidance into API/CEL vs Alerts webhook so users don’t assume webhook is required for agentless.
Regenerate docs output so packages/sysdig/docs/README.md stays in sync.
Validate package with standard package checks in an environment with elastic-package available (recommended gate before merge).
Suggested scope decision: keep current mixed-input policy template (least invasive), and make support boundaries explicit in docs rather than restructuring templates in this issue.
Activity
infra-vault-gh-plugin-prod commentedon Jun 3, 2026
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)
github-actions commentedon Jun 3, 2026
tl;dr: I recommend enabling agentless deployment for Sysdig at the package level, but documenting it as API/CEL-focused support while keeping Alerts (
http_endpoint) as agent-based behavior. This matches existing patterns in this repo for mixed-input integrations.Recommendation
Enable
deployment_modes.agentlessinpackages/sysdig/manifest.yml(beta metadata included), keep current inputs unchanged, and update Sysdig docs to clearly separate:event,cspm,vulnerabilityvia CEL)alertsviahttp_endpoint)Findings
packages/sysdig/manifest.yml:41-51has one policy template withhttp_endpoint+celinputs and nodeployment_modes.packages/sysdig/data_stream/alerts/manifest.yml:4-25isinput: http_endpointand requires listener settings (listen_address,listen_port) — this is inbound webhook style.packages/sysdig/data_stream/event/manifest.yml:4-8,packages/sysdig/data_stream/cspm/manifest.yml:4-8,packages/sysdig/data_stream/vulnerability/manifest.yml:4-8are allinput: celAPI polling streams.packages/sysdig/docs/README.md:23-27currently has only Agent-based installation;:33-39makes Alerts webhook sound mandatory before API setup.packages/forgerock/manifest.yml:20-28(deployment_modes.default+deployment_modes.agentlesswithrelease/org/division/team)packages/darktrace/manifest.yml:27-35same structure.packages/zscaler_zia/manifest.yml:72-80enables agentless at policy level,tcp/http_endpoint(:82,:129) andcel(:191) inputs.packages/forgerock/docs/README.md:5-8has a standard “Agentless Enabled Integration” section and beta/cloud caveat.GitHub context limitation: issue/related-item bodies are integrity-filtered in this environment, so this triage is based on repository evidence only.
Verification
I ran workspace commands to verify current package/test layout and local tooling availability:
$ ls -1 packages/sysdig/data_stream/*/_dev/test/system/test-default-config.yml packages/sysdig/data_stream/alerts/_dev/test/system/test-default-config.yml packages/sysdig/data_stream/cspm/_dev/test/system/test-default-config.yml packages/sysdig/data_stream/event/_dev/test/system/test-default-config.yml packages/sysdig/data_stream/vulnerability/_dev/test/system/test-default-config.yml$ elastic-package check -C packages/sysdig -v bash: elastic-package: command not foundDetailed Action Plan
packages/sysdig/manifest.ymlunderpolicy_templates[0](:41+) to add:deployment_modes.default.enabled: truedeployment_modes.agentless.enabled: truedeployment_modes.agentless.release: betadeployment_modes.agentless.organization/division/team(follow team convention used byforgerock/darktrace).packages/sysdig/changelog.ymlastype: enhancement.packages/sysdig/_dev/build/docs/README.md:forgerock/docs/README.md:5-8).packages/sysdig/docs/README.mdstays in sync.elastic-packageavailable (recommended gate before merge).Suggested scope decision: keep current mixed-input policy template (least invasive), and make support boundaries explicit in docs rather than restructuring templates in this issue.
Related Items
packages/sysdig/manifest.yml:41-51deployment_modes; contains mixedhttp_endpoint+celinputspackages/sysdig/data_stream/alerts/manifest.yml:4-25packages/sysdig/data_stream/{event,cspm,vulnerability}/manifest.yml:4-8cel) suitable for agentless modepackages/sysdig/docs/README.md:23-39packages/forgerock/manifest.yml:20-28forgerock/changelog.yml:9-11)packages/zscaler_zia/manifest.yml:72-80,82,129,191Note
🔒 Integrity filter blocked 4 items
The following items were blocked because they don't meet the GitHub integrity level.
search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".issue_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter:What is this? | From workflow: Issue Triage
Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.