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
Enable audit logging as an independent capability in disabled mode (plugins.security.disabled: true) without requiring any security features — no TLS, no authentication, no authorization.
Background
With SSL-only mode audit logging merged (#6304, #6321), users running OpenSearch with TLS-only have full audit visibility. However, users running with security completely disabled (common in development, log analytics, and internal observability clusters) still have no audit trail.
Compliance frameworks (SOC2, HIPAA, PCI-DSS, GDPR) require audit logs even when access control is not configured.
This is the second phase of the multi-phase standalone audit effort:
Description
Enable audit logging as an independent capability in disabled mode (
plugins.security.disabled: true) without requiring any security features — no TLS, no authentication, no authorization.Background
With SSL-only mode audit logging merged (#6304, #6321), users running OpenSearch with TLS-only have full audit visibility. However, users running with security completely disabled (common in development, log analytics, and internal observability clusters) still have no audit trail.
Compliance frameworks (SOC2, HIPAA, PCI-DSS, GDPR) require audit logs even when access control is not configured.
This is the second phase of the multi-phase standalone audit effort:
Scope
All features from SSL-only mode now work in disabled mode:
REQUEST_AUDITcategory for all REST/transport actionsTRANSPORT_AUDIT)COMPLIANCE_DOC_WRITE,COMPLIANCE_DOC_READ)PUT _cluster/settingsWhat's different from SSL-only mode
Configuration
Related