Why does "Kibana exposure" appear in ExposureGrid?

Scanners observe externally visible signals. A finding means our rules matched - validate severity and applicability in your environment.

Could this be a false positive?

Yes, depending on context and coverage limits. Especially for heuristic, partial, or pattern-based checks, corroborate with manual review.

Re-run a scan to confirm the external signal changed, then enable monitoring where your plan supports it.

Kibana exposure: what it means, why it may matter, and how to remediate with external verification using ExposureGrid.

Kibana exposure: Administrative surfaces are high-value targets when exposed broadly on the internet.

Exposure increases brute-force, exploit, and abuse attempts; combine with MFA, network restrictions, and rate limits.

Inventory public admin URLs, compare to intended architecture, verify auth and logging.

Restrict by IP/VPN, enforce MFA, rate limit, disable public API consoles in production, remove dev tooling from prod paths.

Run a scan to verify this fix on your domain

Use the same public scanner as the homepage — results honor your plan tier.

ExposureGrid fingerprints common admin panels and docs where scanners are enabled for the domain.

Why does "Kibana exposure" appear in ExposureGrid?: Scanners observe externally visible signals. A finding means our rules matched - validate severity and applicability in your environment.
Could this be a false positive?: Yes, depending on context and coverage limits. Especially for heuristic, partial, or pattern-based checks, corroborate with manual review.
What should I do after changing configuration?: Re-run a scan to confirm the external signal changed, then enable monitoring where your plan supports it.

ExposureGrid continuously monitors these issues and alerts you before they become exploitable.

Run a private scan

Compare plans