← AI resource directorydata-knowledge-infrastructure

data-knowledge-infrastructure · prepared

Redis Open Source data boundary

Official-source trusted-network, ACL, authentication, command/key, read/write, persistence, and exposure boundaries for Redis deployments.

version 1.0.0freshness currentobserved 2026-08-27T01:40:00Z

resource.infrastructure.redis-open-source
sha256:8c0360d58a3087c2cd619fdc9eb7943320069aa1eadbf2a78e3d1db4d1bb31b4

Open canonical machine JSON →

Evidence-backed facts

  1. Redis documents a trusted-client and trusted-environment security model and warns against directly exposing its service to untrusted networks. informative
  2. ACL users can be restricted by commands and keys, so successful authentication must not be treated as unrestricted read access. informative
  3. Write and administrative commands require separate least-privilege ACL decisions; dangerous configuration and destructive commands must not be exposed by default. informative
  4. Authentication, protected mode, persistence, replication, backup, and encryption are separate controls; a reachable endpoint is not evidence that any is correctly enabled. informative