Skip to content

Security: byviz/flexiclaw-platform

Security

SECURITY.md

Security Policy

Reporting a vulnerability

If you find a security issue in Flexiclaw Control Tower, please email ivan.frias@flexiclaw.ai with a description and steps to reproduce. Do not open a public issue for security reports. We aim to acknowledge reports within a few business days.

Security posture

  • Read-only by design. Flexiclaw Control Tower only calls read and monitor APIs on Elasticsearch. There is no code path that writes to cluster settings, ILM, index templates, ingest pipelines, indices or data streams.
  • Least privilege. The recommended API key needs only monitor-class privileges — no manage, no write.
  • Local-first, no API authentication yet. This MVP targets a single operator running the stack on their own machine. The API has no auth layer, so it must stay on localhost or a trusted private network. Do not expose ports 3000 and 8000 to the public internet.
  • Credentials encrypted at rest. Cluster credentials are encrypted with your FLEXICLAW_CREDENTIAL_KEY and are never returned by the API or included in any export. Outside the local environment the key is mandatory.
  • Evidence packs are safe to share. They contain normalized metrics and findings only — no credentials and no raw documents.

Supported versions

This project is an MVP under active development. Security fixes target the latest release on the main branch.

There aren't any published security advisories