Study guide

11.2 Cluster Security Options: Lockdown, Encryption, and the Recycle Bin

Nutanix Certified Associate NCA

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Nutanix Cloud Platform & HCI Foundations

1.1 Nutanix NCA Exam Overview, Format, and Objectives 1.2 Hyperconverged Infrastructure (HCI) vs. Traditional 3-Tier Architecture 1.3 The Nutanix Enterprise Cloud Portfolio (NCI, NUS, NCM, EUC, NC2)

2 Chapter 2: Platform Architecture & Distributed Core Services

2.1 Hardware Building Blocks: Nodes, Blocks, Clusters, and Quorum 2.2 Controller VM (CVM) Architecture, Datapath, and Autopathing 2.3 Core Distributed Services: Cassandra, Stargate, Curator, Zookeeper, and Genesis

3 Chapter 3: Prism Administration & Cluster Operations

3.1 Prism Element vs. Prism Central Architecture and Interface Navigation 3.2 Entity Management, Categories, and Role-Based Access Control 3.3 Nutanix Licensing Tiers, Add-ons, and Pulse Telemetry

4 Chapter 4: AOS Distributed Storage Fabric & Data Placement

4.1 Storage Pools, Storage Containers, and vDisk Virtual Architecture 4.2 Redundancy Factor (RF2 vs. RF3), Failure Domains, and Fault Tolerance 4.3 Data Locality Mechanics and Intelligent Lifecycle Management (ILM)

5 Chapter 5: Storage Optimization & Business Continuity

5.1 Storage Efficiency: Compression, Deduplication, and Erasure Coding (EC-X) 5.2 Space-Efficient Redirect-on-Write (ROW) Snapshots and Zero-Byte Clones 5.3 Protection Domains, Consistency Groups, and Disaster Recovery Replication

6 Chapter 6: AHV Virtual Machine Lifecycle Management

6.1 AHV VM Provisioning, Resource Allocation (vCPU, vRAM, Disks), and Boot Types 6.2 Nutanix Image Service and Virtual Machine Templates 6.3 Nutanix Guest Tools (NGT) Architecture, Features, and Deployment 6.4 AHV High Availability (HA), Acropolis Dynamic Scheduling (ADS), and Affinity Rules

7 Chapter 7: AHV Networking & Flow Security Fundamentals

7.1 AHV Virtual Networking Architecture, Open vSwitch (OVS), and Bridges 7.2 Host Network Uplinks, Virtual Switch Configuration, and NIC Bonding Modes 7.3 Virtual Networks: Managed vs. Unmanaged Networks and IPAM 7.4 Nutanix Flow Network Security & Microsegmentation Fundamentals

8 Chapter 8: Cluster Maintenance, Health Monitoring & Support

8.1 Nutanix Cluster Health Monitoring, Alerts, and Events Engine 8.2 Nutanix Cluster Check (NCC) Architecture and Execution 8.3 Life Cycle Manager (LCM) and Rolling Non-Disruptive Upgrades 8.4 Nutanix Support Ecosystem: Diagnostics, Log Gathering, and Support Bundles

9 Chapter 9: Recognizing Nutanix Solutions, Hypervisors & the Product Portfolio

9.1 Supported Hypervisors for NCI and Feature Supportability 9.2 NCI Core Components, Configurations, and Common Deployment Scenarios 9.3 Nutanix Unified Storage: Files, Objects, and Volumes Use Cases 9.4 Nutanix Database Service (NDB) and Database Automation 9.5 Nutanix Kubernetes Platform, Enterprise AI, and End-User Computing

10 Chapter 10: Nutanix Tools — Migration, Deployment, and Validation

10.1 Nutanix Move: Cross-Hypervisor and Cloud Migration 10.2 Foundation and Foundation Central: Imaging and Cluster Deployment 10.3 X-Ray, Collector, and the Objective 1.3 Tool Inventory

11 Chapter 11: Cluster Configuration, Security & Hardware Maintenance

11.1 Cluster Services Configuration: DNS, NTP, SMTP, and SNMP 11.2 Cluster Security Options: Lockdown, Encryption, and the Recycle Bin 11.3 Node Maintenance Mode, Host Shutdown, and Cluster Shutdown 11.4 Cluster Expansion: Node Types and In-Node Expansion Capabilities 11.5 Out-of-Band Management and Remote Console Access

12 Chapter 12: Storage, Network, and Software Administration Tasks

12.1 Volume Groups, vDisk Placement, and Live vDisk Migration 12.2 Network Visualizer, Physical Switch Monitoring, and Network Segmentation 12.3 The Software Compatibility Matrix and Upgrade Path Planning 12.4 Taking and Managing VM Snapshots in Prism 12.5 License Operations: State, Assignment, Reclamation, and Expiry

13 Chapter 13: Performance Analysis, Reporting & Support Operations

13.1 Prism Analysis: Metric Charts, Entity Charts, and Custom Reports 13.2 Custom Alert Policies and Behavioural Anomaly Detection 13.3 Interpreting Workload Performance: CPU Contention, CPU Ready, Memory, and I/O Latency 13.4 Creating Support Cases, Required Documentation, and Insights

11.2 Cluster Security Options: Lockdown, Encryption, and the Recycle Bin

Key Takeaways Explain This Topic AI

Cluster lockdown disables password-based SSH access to CVMs and hosts, permitting only key-based authentication after keys have been added and tested.

Nutanix supports software-based data-at-rest encryption using AES-256, with key management either native to the cluster or through an external KMIP-compliant key manager.

The Recycle Bin retains a deleted VM configuration and its vDisks for up to 24 hours, providing a short window to reverse an accidental deletion.

Role-based access control, directory integration, and least-privilege role assignment are the access-side security controls named by Objective 3.1.

Adding SSH keys and validating access with them must come before disabling password login, or the administrator locks themselves out.

Last updated: September 2026

11.2 Cluster Security Options: Lockdown, Encryption, and the Recycle Bin

"Identify security options" is the fourth knowledge statement under Objective 3.1. At NCA level you are asked to recognize what each control does and when it applies — not to design a hardening standard.

Cluster Lockdown and SSH Key Authentication

By default, an administrator can SSH to a CVM with a username and password. Cluster lockdown removes that: password-based SSH authentication is disabled, and only public key authentication is accepted.

Why organizations enable it:

Passwords can be guessed, brute-forced, phished, or shared. Private keys cannot be typed into a phishing page.

Access becomes auditable per key rather than shared through one account password.

Removing a departing administrator is a matter of deleting their public key.

The order of operations matters

This is the part that is genuinely examinable, because getting it wrong is how administrators lock themselves out of their own cluster:

Add the public key or keys to the cluster through Prism.

Test SSH access using those keys and confirm it works.

Only then disable remote login with password — in Prism this is presented as clearing the Enable Remote Login with Password option.

Warning

Disabling password login before validating key-based access leaves nobody able to reach the CVM command line. Add keys, prove they work, then lock down. Never the other way round.

Lockdown can be managed from Prism Element for a cluster and from Prism Central across clusters, which is the scalable option for an estate.

Data-at-Rest Encryption

Data-at-rest encryption protects data on the physical drives, so that a drive removed from a node — failed, replaced, decommissioned, or stolen — is unreadable.

Nutanix offers software-based encryption using AES-256 , which means the capability does not depend on buying self-encrypting drives. Self-encrypting drives (SEDs) remain an option where an organization already standardizes on them.

Key management is the real decision

Encryption is easy; key management is the design choice:

  • Option What it means When it fits
  • Native / local key manager The cluster manages the keys itself Simplest to run; no external dependency

External KMIP key manager Keys held by an external, KMIP-compliant key management server Required where policy mandates separation of keys from data, or where one key manager serves many platforms

The principle to carry into the exam: encryption without key management is not a security control . If the keys sit beside the data with no separation, a policy requiring that separation is not satisfied.

What it does and does not protect

Data-at-rest encryption protects physical media . It does not protect against an authenticated user reading data they have legitimate access to, and it is not a substitute for RBAC, network segmentation, or Flow policy. A question that describes limiting which administrators can see which VMs is an RBAC question, not an encryption question.

Access Control

Covered in depth in section 3.2, and named here because Objective 3.1 counts it among the security options:

Role-based access control assigns permissions through roles rather than to individuals, with built-in roles plus custom roles in Prism Central.

Directory services integration with Active Directory or LDAP means accounts and their lifecycle live in the directory rather than as local users on the cluster.

Local break-glass accounts should exist, be few, and be tightly controlled — they are how you recover when the directory is unreachable.

Least privilege is the assignment principle: give a role the minimum scope the job requires.

The Recycle Bin

The Recycle Bin, available from AOS 5.18 onward, is a safety net for accidental deletion. When a guest VM is deleted, its configuration file and its vDisks are retained for up to 24 hours rather than being destroyed immediately.

What this means in practice:

A VM deleted by mistake can be recovered within that window.

Space consumed by a deleted VM is not reclaimed instantly, which occasionally surprises administrators watching capacity after a bulk cleanup.

Important

The Recycle Bin is not backup . Its retention is a day, and it protects only against deletion — not corruption, not ransomware, not a failure discovered a week later. Snapshots, protection domains, and a backup product remain necessary.

Summary Table

  • Control Protects against Key detail
  • Cluster lockdown Credential attacks on the CVM shell Add and test keys before disabling password login

Data-at-rest encryption Data exposure via physical drives AES-256 software encryption; native or external KMIP key management

RBAC + directory integration Excessive administrative privilege Least privilege; keep a controlled break-glass account

Recycle Bin Accidental VM deletion Up to 24 hours retention; not a backup

Loading diagram... Cluster Security Controls by Threat