Cohesity Hardware
You set up cohesity hardware by racking nodes and assigning network addresses. Then you group the nodes into a storage cluster and add roles. Most teams share a few broad admin accounts for initial setup. Later, those same broad roles remain active for daily maintenance tasks. Overly wide permissions let a single mistake wipe out backup snapshots. A clear role plan keeps storage nodes safe during daily work. How cohesity hardware architecture and roles work The platform runs as a distributed
Hardware-Based Attestation: the complete guide
Architecture patterns, implementation strategies, and security best practices. Delivered to your inbox.
You set up cohesity hardware by racking nodes and assigning network addresses. Then you group the nodes into a storage cluster and add roles. Most teams share a few broad admin accounts for initial setup. Later, those same broad roles remain active for daily maintenance tasks. Overly wide permissions let a single mistake wipe out backup snapshots. A clear role plan keeps storage nodes safe during daily work.
How cohesity hardware architecture and roles work
The platform runs as a distributed cluster of storage nodes. Each node brings compute, memory, and disk space to the pool. You do not manage drives on one box at a time. Instead, the cluster software spreads data across all nodes for safety. If one node fails, the remaining nodes keep serving backup data. Teams manage this whole cluster through a web console or interface.
You control who can touch the cluster through role-based rules. Admins link the cluster to an identity provider for user logins. Then they map user groups to built-in or custom cluster roles. A viewer role lets a user read backup job status. An operator role lets a user start or stop protection runs. A full admin role allows node removal, network changes, and deletions. For deeper repair work, engineers also log into node shells.
What native cluster roles solve and where gaps remain
Native cluster roles stop unauthorized users from opening the management console. They let you separate daily backup operators from system admins. You can also restrict which data views a specific team sees. This setup handles basic login checks at the front door well. It proves who a user is before a session starts.
Still, native roles only check identity at the time of login. Once a user enters an admin session, every command runs unchecked. A support engineer with shell access can run destructive disk commands. An API script with an admin key can delete backup views. Native logs show that a session happened, not every command detail. Also, backup mounts often hold raw emails, phone numbers, or card numbers. When engineers inspect mounted files, native storage roles do not rewrite data. You need command checks and field masking to reduce runtime risk.
Hardware-Based Attestation: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
Securing node shell and API maintenance workflows
To reduce risk, teams must tighten how engineers run node tasks. First, disable shared local admin logins across all storage nodes. Force every engineer to log in with a personal identity account. Next, separate routine backup jobs from low-level hardware repair tasks. No engineer should hold permanent root shell rights on storage nodes.
When a node needs repair, grant access for that task only. Review the exact commands the engineer plans to run before approval. Keep a full log of every shell command and API call. If an engineer queries mounted data, mask sensitive fields in results. Rewriting card numbers and national IDs in flight prevents accidental leaks. This approach pairs solid hardware roles with strict controls during sessions.
Check database and API queries on the wire
Identity tools, roles, and network rules decide who opens a session. Setup alone cannot check what each query does or mask sensitive values in a response once a session starts. When workflows touch Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes APIs, SSH, or internal HTTP APIs, hoop.dev sits inline in the wire protocol beside those services as an open-source proxy, a sidecar for your Postgres or API. On every query an AI agent or engineer runs against production, hoop.dev decides to pass, mask, block, or hold it for human review.
Your login details and client tools stay as they are while hoop.dev guardrails refuse bad deletes or drops before they run, and hoop.dev data masking rewrites matched sensitive values in responses in memory. Furthermore, hoop.dev holds SOC 2 Type II, is MIT licensed, and writes every query and decision to an audit trail that generates evidence for HIPAA, GDPR, and PCI DSS. See the source on GitHub.
Frequently asked questions
How do nodes join a storage cluster?
New nodes discover existing cluster members over the local network link. An admin claims the new node and adds its disk space.
Can we restrict shell access on storage nodes?
Yes, admins can lock down support shells in the cluster settings. Teams should keep shell access turned off until a repair happens.
Why are static API keys risky for backup automation?
Static keys do not expire and often carry full admin rights. If a script leaks a key, an attacker controls all backups.