[claroty_xdome] Remove the recommendations field from vulnerabilities requests

[chrisberkhout]

Proposed commit message

Remove the recommendations field from vulnerabilities requests.

The recommendations field is no longer available. The API responds
with 422 Unprocessable Content and this body:

    {
      "detail": [
        {
          "type": "enum",
          "loc": [
            "body",
            "fields",
            15
          ],
          "msg": "Input should be id, name, vulnerability_type, cve_ids, cvss_v2_score, cvss_v2_exploitability_subscore, cvss_v2_vector_string, cvss_v3_score, cvss_v3_exploitability_subscore, cvss_v3_vector_string, sources, source_name, source_url, description, affected_products, is_known_exploited, affected_devices_count, affected_medical_devices_count, affected_iot_devices_count, affected_it_devices_count, affected_ot_devices_count, published_date, affected_fixed_devices_count, affected_confirmed_devices_count, affected_potentially_relevant_devices_count, affected_irrelevant_devices_count, adjusted_vulnerability_score, adjusted_vulnerability_score_level, exploits_count, vulnerability_labels, vulnerability_assignees, vulnerability_note, vulnerability_priority_group, epss_score or alert_id",
          "input": "recommendations",
          "ctx": {
            "expected": "id, name, vulnerability_type, cve_ids, cvss_v2_score, cvss_v2_exploitability_subscore, cvss_v2_vector_string, cvss_v3_score, cvss_v3_exploitability_subscore, cvss_v3_vector_string, sources, source_name, source_url, description, affected_products, is_known_exploited, affected_devices_count, affected_medical_devices_count, affected_iot_devices_count, affected_it_devices_count, affected_ot_devices_count, published_date, affected_fixed_devices_count, affected_confirmed_devices_count, affected_potentially_relevant_devices_count, affected_irrelevant_devices_count, adjusted_vulnerability_score, adjusted_vulnerability_score_level, exploits_count, vulnerability_labels, vulnerability_assignees, vulnerability_note, vulnerability_priority_group, epss_score or alert_id"
          }
        }
      ]
    }

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

[elasticmachine]

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

[github-actions]

Vale Linting Results

Summary: 4 warnings found

⚠️ Warnings (4)

File	Line	Rule	Message
packages/claroty_xdome/docs/README.md	1432	Elastic.QuotesPunctuation	Place punctuation inside closing quotation marks.
packages/claroty_xdome/docs/README.md	1432	Elastic.QuotesPunctuation	Place punctuation inside closing quotation marks.
packages/claroty_xdome/docs/README.md	1432	Elastic.QuotesPunctuation	Place punctuation inside closing quotation marks.
packages/claroty_xdome/docs/README.md	1433	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'and so on' instead of 'etc'.

---

The Vale linter checks documentation changes against the Elastic Docs style guide.

To use Vale locally or report issues, refer to Elastic style guide for Vale.

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: d221f11

History

• 💚 Build #40013 succeeded bdf6224
• 💔 Build #39972 failed 6abfe27

cc @chrisberkhout

[elastic-vault-github-plugin-prod]

Package claroty_xdome - 1.0.2 containing this change is available at https://epr.elastic.co/package/claroty_xdome/1.0.2/