Skip to content

[tenable_ot_security] Add Agentless Deployment Support #19356

Closed

Description

@moxarth-rathod

Description

Add agentless support to the tenable_ot_security.

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. infra-vault-gh-plugin-prod commented on Jun 3, 2026

    @infra-vault-gh-plugin-prod

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

  2. github-actions commented on Jun 3, 2026

    @github-actions
    Contributor

    tl;dr: tenable_ot_security is missing the deployment_modes.agentless policy-template block, and the most reliable path is to mirror the existing Tenable patterns (tenable_io/tenable_sc) with a minor version bump, changelog entry, and agentless doc section.

    Recommendation
    Implement agentless support by adding deployment_modes under packages/tenable_ot_security/manifest.yml policy template, using the same metadata shape used by other security-service-integrations packages. In the same PR, add a changelog entry and agentless documentation text.

    Findings
    1. Target package currently has no agentless declaration

    packages/tenable_ot_security/manifest.yml:30-35

    policy_templates:
      - name: tenable_ot_security_cloud
        title: Tenable OT Security Cloud Events
        description: Collect events from Tenable OT Security Cloud event reporting.
        inputs:
          - type: cel
    1. Direct Tenable precedents already use the exact block needed

    packages/tenable_io/manifest.yml:29-37

    deployment_modes:
      default:
        enabled: true
      agentless:
        enabled: true
        release: beta
        organization: security
        division: engineering
        team: security-service-integrations

    packages/tenable_sc/manifest.yml:29-37 has the same structure.

    1. deployment_modes is valid for this package format
    • packages/tenable_ot_security/manifest.yml:1 uses format_version: 3.3.0.
    • docs/extend/manifest-spec.md:661-664 shows deployment_modes is removed only for versions before 3.1.4.
    • docs/extend/manifest-spec.md:512-513 includes policy_templates[].deployment_modes.
    1. CEL input precedent exists for agentless
    • packages/tenable_io/manifest.yml:38-39 uses CEL and supports agentless.
    1. Docs/changelog gap in target package
    • packages/tenable_ot_security/docs/README.md:15-28 and _dev/build/docs/README.md:15-28 go from requirements directly to logs (no agentless section).
    • packages/tenable_ot_security/changelog.yml:1 latest entry is 2.0.0; no agentless feature note.
    1. Related precedent PRs
    • #15364 ([Tenable SC] Add agentless deployment) shows the expected package-level change set.
    • #18552 established explicit agentless.release usage (beta|ga) across agentless manifests.
    1. Limitation in this triage run
    • The issue body/comments were integrity-filtered in this environment, so this recommendation is based on the issue title plus repository/PR evidence.
    Verification

    I ran a direct repository check for deployment mode declarations:

    git --no-pager grep -n "deployment_modes\|policy_templates\|name: tenable_ot_security\|name: tenable_io\|name: tenable_sc" -- packages/tenable_ot_security/manifest.yml packages/tenable_io/manifest.yml packages/tenable_sc/manifest.yml | head -n 80

    Output:

    packages/tenable_io/manifest.yml:2:name: tenable_io
    packages/tenable_io/manifest.yml:25:policy_templates:
    packages/tenable_io/manifest.yml:26:  - name: tenable_io
    packages/tenable_io/manifest.yml:29:    deployment_modes:
    packages/tenable_ot_security/manifest.yml:2:name: tenable_ot_security
    packages/tenable_ot_security/manifest.yml:30:policy_templates:
    packages/tenable_ot_security/manifest.yml:31:  - name: tenable_ot_security_cloud
    packages/tenable_sc/manifest.yml:2:name: tenable_sc
    packages/tenable_sc/manifest.yml:25:policy_templates:
    packages/tenable_sc/manifest.yml:26:  - name: tenable_sc
    packages/tenable_sc/manifest.yml:29:    deployment_modes:
    
    Detailed Action Plan
    1. Add deployment modes in manifest

      • Edit packages/tenable_ot_security/manifest.yml under policy_templates[0] (after description, before inputs).
      • Add:
      deployment_modes:
        default:
          enabled: true
        agentless:
          enabled: true
          release: beta
          organization: security
          division: engineering
          team: security-service-integrations
    2. Bump package version (minor)

      • Update packages/tenable_ot_security/manifest.yml version from 2.0.0 to next minor, since this is a backward-compatible feature addition (docs/extend/_publish_an_integration.md:23-25).
    3. Add changelog entry

      • Prepend a new top entry in packages/tenable_ot_security/changelog.yml with:
        • type: enhancement
        • description like Enable Agentless deployment.
        • PR link.
    4. Document agentless support

      • Add an agentless section in packages/tenable_ot_security/_dev/build/docs/README.md, following Tenable package precedent (packages/tenable_io/docs/README.md:36-40, packages/tenable_sc/docs/README.md:5-8).
      • Rebuild docs so packages/tenable_ot_security/docs/README.md is updated from template.
    5. Run package checks before merge

      • From package dir: elastic-package check
      • Run package tests used by maintainers (elastic-package test ...) as appropriate.
    Related Items
    Type Link Relevance
    Issue #19356 Requested agentless support for tenable_ot_security
    PR #15364 Tenable precedent adding agentless deployment
    PR #18552 Enforced agentless.release conventions across integrations
    File packages/tenable_ot_security/manifest.yml:30-35 Current gap (no deployment_modes)
    File packages/tenable_io/manifest.yml:29-37 Closest template for required block
    File packages/tenable_sc/manifest.yml:29-37 Additional Tenable template
    File docs/extend/manifest-spec.md:512-513 deployment_modes allowed in policy templates
    File docs/extend/manifest-spec.md:661-664 Version gating confirms support at current format

    Note

    🔒 Integrity filter blocked 40 items

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

    • #19356 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #17973 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • [tenable_ot_security] Add Agentless Deployment Support #19356 issue_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #19356 issue_read: 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".
    • #15364 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #15988 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #17560 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #16985 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #13718 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #12586 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #14306 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #12961 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #14079 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #12893 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #11203 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • ... and 24 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Integration:tenable_ot_securityTenable OT SecurityTeam: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

    ⌂ 换网址