Skip to content

[jumpcloud] Add Agentless Deployment Support #19093

Closed
#19205
Closed
[jumpcloud] Add Agentless Deployment Support#19093
#19205
Assignees
mohitjha-elastic
Labels
Integration:jumpcloudJumpCloudTeam:SDE-CrestCrest developers on the Security Integrations team [elastic/sit-crest-contractors]Team:Security-Service IntegrationsSecurity Service Integrations team [elastic/security-service-integrations]enhancementNew feature or request

Description

@mohitjha-elastic
mohitjha-elastic
opened on May 20, 2026

Description

Add agentless support to the jumpcloud.

Requirements

Following the established Phase I pattern, for each integration see the Onboarding Integration Guide.

1. Technical implementation

  • Update integration manifest.yml to enable agentless deployment mode ()
  • Update integration documentation with agentless deployment instructions
  • Update changelog.md

Example reference: #13367

2. Performance documentation

  • Test and document throughput in agentless (requires access to vendor environment and/or sample data)
  • Document specific metrics for each integration. For example/where possible:
    • API response time: Average time for vendor API calls to complete
    • Events processed per minute: How many log entries/events the integration can handle
    • Error rates: Percentage of failed API calls or data processing errors
    • Container resource usage: CPU and memory consumption under typical load
    • Vendor-specific limits: Rate limiting thresholds and API quotas

Example documentation format: "Crowdstrike Falcon Intelligence: 200ms avg API response, 5,000 events/min, 0.1% error rate, 512MB RAM/0.5CPU, 1000 API calls/hour limit"

Dependencies

  • Agentless infrastructure GA readiness (still in beta)
  • Input compatibility: Currently agentless is optimized for httpjson and cel inputs
  • UX enhancement: Add agentless deployment filter/toggle to integrations catalog page for better discoverability

Activity

  1. mohitjha-elastic
    self-assigned this
    on May 20, 2026
  2. mohitjha-elastic
    added a parent issue on May 20, 2026
  3. mohitjha-elastic
    added
    enhancementNew feature or request
    Integration:jumpcloudJumpCloud
    Team:Security-Service IntegrationsSecurity Service Integrations team [elastic/security-service-integrations]
    Team:SDE-CrestCrest developers on the Security Integrations team [elastic/sit-crest-contractors]
    on May 20, 2026

  4. infra-vault-gh-plugin-prod commented on May 20, 2026

    @infra-vault-gh-plugin-prod
    infra-vault-gh-plugin-prodBot
    on May 20, 2026

    Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

  5. github-actions commented on May 20, 2026

    @github-actions
    github-actionsBot
    on May 20, 2026 – with GitHub Actions
    Contributor

    tl;dr: jumpcloud is not yet agentless-enabled in package metadata or docs, and the clean path is a Phase-I PR matching prior Security-Service integrations: add deployment_modes.agentless in manifest, add agentless deployment docs, and add a changelog entry; treat measured throughput metrics as a follow-up that requires a live JumpCloud test environment.

    Recommendation

    Proceed with a single implementation PR for technical enablement (manifest + docs + changelog), and track performance benchmarking/documentation in a follow-up issue unless test infrastructure and vendor data are already available.

    Findings
    • packages/jumpcloud/manifest.yml:25-32 defines policy_templates with inputs (httpjson) but has no deployment_modes block.
    • packages/jumpcloud/docs/README.md:13 states Elastic Agent is a requirement, and :29-37 documents only agent-based onboarding.
    • packages/jumpcloud/changelog.yml:1-12 has no agentless-related entry.
    • JumpCloud input compatibility aligns with issue dependency notes:
      • packages/jumpcloud/manifest.yml:30 → type: httpjson
      • packages/jumpcloud/data_stream/events/manifest.yml:4 → input: httpjson
    • Canonical pattern already exists in this repo:
      • packages/cisa_kevs/manifest.yml:28-35 and packages/aws_securityhub/manifest.yml:33-40 show deployment_modes.default + deployment_modes.agentless with org/division/team metadata.
      • packages/cisa_kevs/docs/README.md:7-10 and packages/aws_securityhub/docs/README.md:50-55 show standard agentless documentation language.
      • packages/cisa_kevs/changelog.yml:2-6 shows expected changelog style (Enable Agentless deployment).
    • Related merged PRs following the same pattern: #13367, #13243, #13173, #13177.
    Verification

    I ran targeted checks to confirm what is and isn’t present today:

    $ grep -RInE "deployment_modes|agentless|type:[[:space:]]*httpjson" \
  packages/jumpcloud/manifest.yml \
  packages/jumpcloud/docs/README.md \
  packages/jumpcloud/changelog.yml \
  packages/jumpcloud/data_stream/events/manifest.yml
packages/jumpcloud/manifest.yml:30:      - type: httpjson

$ grep -RInE "deployment_modes|agentless|Agentless Enabled Integration|How do I deploy this integration\?|Agentless deployment" \
  packages/cisa_kevs/manifest.yml \
  packages/cisa_kevs/docs/README.md \
  packages/aws_securityhub/manifest.yml \
  packages/aws_securityhub/docs/README.md
packages/cisa_kevs/manifest.yml:28:    deployment_modes:
packages/cisa_kevs/manifest.yml:31:      agentless:
packages/cisa_kevs/docs/README.md:7:## Agentless Enabled Integration
packages/aws_securityhub/manifest.yml:33:    deployment_modes:
packages/aws_securityhub/manifest.yml:36:      agentless:
packages/aws_securityhub/docs/README.md:50:### Agentless deployment
    Detailed Action Plan
    1. Update packages/jumpcloud/manifest.yml under policy_templates[0] (around :25-32) to add:
      • deployment_modes.default.enabled: true
      • deployment_modes.agentless.enabled: true
      • deployment_modes.agentless.organization/division/team using the same values used by Security-Service integrations (security / engineering / security-service-integrations).
    2. Keep existing httpjson input unchanged (packages/jumpcloud/manifest.yml:30, packages/jumpcloud/data_stream/events/manifest.yml:4), since this is already within the Phase-I supported input types noted in the issue.
    3. Update packages/jumpcloud/docs/README.md:
      • Add an Agentless deployment subsection near onboarding (after current enablement steps around :29-37), using existing wording pattern from packages/aws_securityhub/docs/README.md:50-55 or packages/cisa_kevs/docs/README.md:7-10.
      • Keep/clarify beta/SLA caveat and serverless/cloud-only scope.
    4. Add a top entry to packages/jumpcloud/changelog.yml (above 1.19.0) for agentless enablement, consistent with repo style (example: packages/cisa_kevs/changelog.yml:2-6).
    5. For the performance-documentation requirement:
      • Document tunable knobs already visible in package config (event_limit, interval, source_lag_time) with references to packages/jumpcloud/data_stream/events/manifest.yml:41-47, 62-67, 97-104.
      • Record measured metrics (API latency, events/min, error rate, resource usage, vendor limits) only after running in a real JumpCloud-backed environment; track this as a follow-up task if not available now.
    Related Items
    Type Link Relevance
    Issue #19093 Current request
    Issue #17973 Parent issue linked from #19093
    PR #13367 Referenced in issue; canonical agentless pattern
    PR #13243 Same Phase-I enablement approach
    PR #13173 Same Phase-I enablement approach
    PR #13177 Same Phase-I enablement approach
    File packages/jumpcloud/manifest.yml:25-32 Missing deployment_modes.agentless
    File packages/jumpcloud/docs/README.md:13,29-37 Agent-based-only docs currently
    File packages/jumpcloud/changelog.yml:1-12 No agentless changelog entry
    File packages/cisa_kevs/manifest.yml:28-35 Good manifest template for agentless block
    File packages/aws_securityhub/docs/README.md:50-55 Good docs template for agentless section

    Note

    🔒 Integrity filter blocked 42 items

    The following items were blocked because they don't meet the GitHub integrity level.

    • #17973 issue_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #19028 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #18552 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #19090 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #18889 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #18141 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #18516 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #19037 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #19036 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #19062 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #18227 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #18345 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #18777 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #18762 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #19087 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #18991 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • ... and 26 more items

    To allow these resources, lower min-integrity in your GitHub frontmatter:

    tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

    What is this? | From workflow: Issue Triage

    Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

  6. mohitjha-elastic
    closed this as completedin #19205on Jun 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Integration:jumpcloudJumpCloudTeam:SDE-CrestCrest developers on the Security Integrations team [elastic/sit-crest-contractors]Team:Security-Service IntegrationsSecurity Service Integrations team [elastic/security-service-integrations]enhancementNew feature or request

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions