Plugin settings
Setup settings
The Setup plugin is configured through settings in opensearch.yml. All settings use the plugins.setup prefix.
plugins.setup.timeout(Integer, default30) — timeout in seconds for index and search operations.plugins.setup.backoff(Integer, default15) — delay in seconds for the retry mechanism involving initialization tasks.plugins.setup.settings_update.enabled(Boolean, defaulttrue) — whenfalse, the settings update endpoint (PUT /_plugins/_setup/settings) returns403 Forbiddenfor every caller, regardless of role. See Protecting sensitive configuration for the full disable-endpoint pattern shared with Content Manager.
Content Manager settings
The Content Manager plugin is configured through settings in opensearch.yml. All settings use the plugins.content_manager prefix.
plugins.content_manager.cti.api(String, defaulthttps://api.pre.cloud.wazuh.com/api/v1) — base URL for the Wazuh CTI API.plugins.content_manager.catalog.sync_interval(Integer, default60, range 10–1440) — sync interval in minutes.plugins.content_manager.setup_wait.max_retries(Integer, default4, range 0–10) — number of retries the catalog sync job performs while waiting for the Setup plugin to report readiness on startup, before giving up until the next scheduled sync.plugins.content_manager.setup_wait.backoff_base_seconds(Integer, default20, range 1–120) — base delay, in seconds, for the exponential backoff between those retries (delay for retrynisbase * 2^n; with the defaults, 20s/40s/80s/160s = 300s / 5 min worst case).plugins.content_manager.max_items_per_bulk(Integer, default999, range 10–999) — maximum documents per bulk indexing request.plugins.content_manager.max_concurrent_bulks(Integer, default5, range 1–5) — maximum concurrent bulk operations.plugins.content_manager.max_bulk_bytes(Long, default5242880/ 5 MB, range 1048576–104857600 / 1–100 MB) — maximum request body size, in bytes, for a single bulk indexing request.plugins.content_manager.client.timeout(Long, default10, range 10–50) — HTTP client timeout in seconds for CTI API requests.plugins.content_manager.client.max_retries(Integer, default3, range 0–10) — number of times a CTI API request is retried after an HTTP 429 (Too Many Requests) response, before the 429 is returned to the caller.plugins.content_manager.client.retry_backoff_base_seconds(Integer, default30, range 1–300) — base delay, in seconds, for the exponential backoff used between 429 retries when the response carries no usableRetry-Afterheader (delay for retrynisbase * 2^n).plugins.content_manager.pit_keepalive(Long, default120, range 60–600) — point-in-time keepalive in seconds used during paginated index scans.plugins.content_manager.engine.mock(Boolean, defaultfalse) — bypasses real Engine socket calls, returning mocked responses instead. Intended for testing only.plugins.content_manager.catalog.update_on_start(Boolean, defaulttrue) — trigger content sync when the plugin starts.plugins.content_manager.catalog.update_on_schedule(Boolean, defaulttrue) — enable the periodic sync job.plugins.content_manager.catalog.ruleset(String, default"") — full CTI consumer URL for ruleset content.plugins.content_manager.catalog.iocs(String, default"") — full CTI consumer URL for IoC content.plugins.content_manager.catalog.vulnerabilities(String, default"") — full CTI consumer URL for vulnerabilities content.plugins.content_manager.catalog.create_detectors(Boolean, defaulttrue) — automatically create Security Analytics detectors from CTI content.plugins.content_manager.telemetry.enabled(Boolean, defaulttrue, dynamic) — enable or disable the daily Update check service ping.plugins.content_manager.catalog.update_on_demand(Boolean, defaulttrue) — whenfalse, on-demand content updates (POST /update) return403 Forbiddenfor every caller, regardless of role.plugins.content_manager.catalog.policy_update.enabled(Boolean, defaulttrue) — whenfalse, policy updates (PUT /policy/{space}) return403 Forbiddenfor every caller, regardless of role.plugins.content_manager.max_integrations(Integer, default100, minimum0, no upper bound, dynamic) — maximum number of integrations that can be created. Requests that would exceed this limit are rejected with HTTP 400.plugins.content_manager.max_decoders(Integer, default200, minimum0, no upper bound, dynamic) — maximum number of decoders that can be created. Requests that would exceed this limit are rejected with HTTP 400.plugins.content_manager.max_rules(Integer, default200, minimum0, no upper bound, dynamic) — maximum number of rules that can be created. Requests that would exceed this limit are rejected with HTTP 400.plugins.content_manager.max_kvdbs(Integer, default100, minimum0, no upper bound, dynamic) — maximum number of KVDBs that can be created. Requests that would exceed this limit are rejected with HTTP 400.plugins.content_manager.max_filters(Integer, default100, minimum0, no upper bound, dynamic) — maximum number of filters that can be created per space. Requests that would exceed this limit are rejected with HTTP 400.
Security Analytics settings
The Security Analytics plugin is configured through settings in opensearch.yml. All node-scope settings use the plugins.security_analytics prefix. Almost every setting is dynamic and can be changed at runtime via the Cluster Settings API.
plugins.security_analytics.alert_finding_enabled(Boolean, defaultfalse) — enable rollover and retention management for the finding history indices.plugins.security_analytics.alert_finding_max_docs(Long, default1000, minimum0) — Deprecated. Maximum document count for a finding history index before rollover.plugins.security_analytics.alert_finding_rollover_period(Time, default12h) — how often the finding history rollover job runs.plugins.security_analytics.alert_history_enabled(Boolean, defaultfalse) — enable rollover and retention management for the alert history indices.plugins.security_analytics.alert_history_max_age(Time, default30d) — maximum age of an alert history index before rollover.plugins.security_analytics.alert_history_max_docs(Long, default1000, minimum0) — maximum document count for an alert history index before rollover.plugins.security_analytics.alert_history_retention_period(Time, default60d) — retention period after which alert history indices are deleted.plugins.security_analytics.alert_history_rollover_period(Time, default12h) — how often the alert history rollover job runs.plugins.security_analytics.auto_correlations_enabled(Boolean, defaultfalse) — automatically generate correlation rules from new findings.plugins.security_analytics.correlation.detector_cache_ttl(Time, default5m) — TTL for the in-memory monitor-id to detector cache. Set to0sto disable the cache.plugins.security_analytics.correlation.events_backpressure.enabled(Boolean, defaulttrue) — write-block the events indices when the correlation backlog fills, so ingestion pauses and the backlog drains instead of the node running out of memory.plugins.security_analytics.correlation.events_backpressure.high_watermark_percent(Integer, default100, range 1–100) — backlog level, as a percent ofcorrelation.max_pending_findings, at or above which the events indices are write-blocked.plugins.security_analytics.correlation.events_backpressure.low_watermark_percent(Integer, default60, range 0–99) — backlog level, as a percent ofcorrelation.max_pending_findings, at or below which the events-index write block is lifted.plugins.security_analytics.correlation.max_in_flight_findings(Integer, default50, range 1–1000) — maximum number of correlation pipelines running concurrently.plugins.security_analytics.correlation.max_pending_findings(Integer, default10000, range 1–1000000) — maximum findings waiting for a free correlation slot. When the backlog is full, new findings are shed (correlation and enrichment skipped) so the node does not run out of memory under overload.plugins.security_analytics.correlation.metadata_cache_ttl(Time, default5m) — TTL for the in-memory caches of log-type list and correlation rules by detector type. Set to0sto disable both caches.plugins.security_analytics.correlation_history_max_age(Time, default30d) — maximum age of a correlation history index before rollover.plugins.security_analytics.correlation_history_max_docs(Long, default1000, minimum0) — maximum document count for a correlation history index before rollover.plugins.security_analytics.correlation_history_retention_period(Time, default60d) — retention period after which correlation history indices are deleted.plugins.security_analytics.correlation_history_rollover_period(Time, default12h) — how often the correlation history rollover job runs.plugins.security_analytics.correlation_time_window(Time, default5m) — time window used to group findings into correlations.plugins.security_analytics.enable_detectors_with_dedicated_query_indices(Boolean, defaulttrue) — create dedicated query indices for new detectors.plugins.security_analytics.enable_workflow_usage(Boolean, defaulttrue) — use Alerting composite workflows when running detectors.plugins.security_analytics.enriched_findings_bulk_size(Integer, default100, range 10–1000) — number of enriched findings accumulated before a bulk index request is fired.plugins.security_analytics.enriched_findings_enrich_batch_size(Integer, default100, range 1–1000) — maximum number of findings drained from the queue per in-flight permit, fetched via a single combined MultiGet.plugins.security_analytics.enriched_findings_flush_interval(Integer, default5, range 1–60) — interval in seconds at which pending enriched findings are flushed regardless of batch size.plugins.security_analytics.enriched_findings_index_enabled(Boolean, defaulttrue) — toggle the enriched findings pipeline (see Architecture).plugins.security_analytics.enriched_findings_max_in_flight(Integer, default5, range 1–10) — maximum number of concurrent async enrichment chains.plugins.security_analytics.enriched_findings_rule_cache_max_size(Integer, default10000, minimum0, static — requires a node restart to change) — maximum number of rule-metadata entries cached in memory. Least-recently-used entries are evicted past this size.plugins.security_analytics.filter_by_backend_roles(Boolean, defaultfalse) — restrict access to detectors, rules, and findings based on the requester’s backend roles.plugins.security_analytics.finding_history_max_age(Time, default30d) — maximum age of a finding history index before rollover.plugins.security_analytics.finding_history_retention_period(Time, default60d) — retention period after which finding history indices are deleted.plugins.security_analytics.index_timeout(Time, default60s) — timeout for Security Analytics index operations.plugins.security_analytics.max_case_management_bulk_size(Integer, default10, range 0–100, dynamic) — maximum number of findings that can be updated in a single request to the update findings endpoint. Setting it to0disables the endpoint entirely.plugins.security_analytics.max_detectors(Integer, default10, minimum0, no upper bound, dynamic) — maximum number of user-created detectors (Content Manager detectors do not count).plugins.security_analytics.max_rules_per_detector(Integer, default50, minimum0, no upper bound, dynamic) — maximum number of rules (custom or pre-packaged) allowed in a single detector input. Requests that would exceed this limit are rejected with HTTP 400.plugins.security_analytics.mappings.default_schema(String, defaultecs) — default field-mapping schema used to resolve a Sigma rule’s raw field names to Wazuh Common Schema fields when a log type does not declare its own schema.