elasticsearch-security-troubleshooting

Fail

Audited by Runlayer on Mar 14, 2026

Risk Level: HIGH
Scan Summary
Max Score
92%
Files
2
Flagged
1
Chunks
4
Flagged Files (1)
elasticsearch-security-troubleshooting/SKILL.mdHIGH
91.8%

Risky tool definition detected

```bash curl <auth_flags> "${ELASTICSEARCH_URL}/_xpack" ``` Confirms whether security is enabled (`features.security.enabled`). If security is disabled, all security APIs return errors. ```bash curl -X POST "${ELASTICSEARCH_URL}/_security/user/_has_privileges" \ <auth_flags> \ -H "Content-Type: application/json" \ -d '{ "index": [ { "names": ["'"${INDEX_PATTERN}"'"], "privileges": ["read"] } ] }' ``` Tests whether the authenticated user holds specific privileges without requiring `manage_securit

### Users locked out after license expired **Symptom:** "Nobody can log in to Kibana. We use SAML." 1. Check license: ```bash curl -u "admin:${PASSWORD}" "${ELASTICSEARCH_URL}/_license" ``` Response shows `"status": "expired"`, `"type": "platinum"`.

Passed Files (1)Click to expand
elasticsearch-security-troubleshooting/references/api-reference.mdOK
20.3%

Tool passed security scan

Audit Metadata
Max File Score
92%
Classification
UNKNOWN_SERVER
Files Scanned
2
Files Flagged
1
Chunks Analyzed
4
Analyzed
Mar 14, 2026, 08:13 PM
Security Audit — runlayer — elasticsearch-security-troubleshooting