Security Policy & Responsible Disclosure
Stella Ops ships with signed releases, DSSE attestations, and regional crypto hooks. We keep basic access logs for seven days to prevent abuse, then rotate them into hashed form. This page covers responsible disclosure, authenticity guarantees, and the controls already in service. Email our Vulnerability Response Team at Please include: We acknowledge within 72 h and keep you informed until a fix is published. Researchers following this process can be credited in release notes (opt‑in, naturally).Reporting a vulnerability 🔒
security@stella‑ops.org (PGP fingerprint 9BCF 5D1D 6EA9 8F99 24F4 6071 B618 ABAF 7D23 C65D 7A86 77E8 2DE3 7815 6126 F723).Authenticity marks 🔏
9BCF 5D1D 6EA9 8F99 24F4 6071 B618 ABAF 7D23 C65D 7A86 77E8 2DE3 7815 6126 F723.Existing safeguards ✅
Layer Measure Release integrity Cosign-signed artefacts, DSSE replay manifests, and reproducible SBOMs Access logs Stored 7 days, then ip → sha256(ip)JWT quota ledger Stores token‑ID hash + daily counter; no email/IP Soft throttle At 90% daily scan quota the CLI displays a reminder; at 333 scans/day requests slow but never fail Regional crypto Pluggable TLS/signing providers (e.g. SM2/SM3, GOST) with the same DSSE + Cosign trail Container hardening Non‑root UID, cgroup CPU/RAM limits, SELinux/AppArmor Air‑gap ready See Offline Kit Zero‑telemetry promise 📉
Hall of Thanks 🏆