diff --git a/content/k3s/latest/en/security/secrets_encryption/_index.md b/content/k3s/latest/en/security/secrets_encryption/_index.md
index e6f626c7af4..9259e4931a9 100644
--- a/content/k3s/latest/en/security/secrets_encryption/_index.md
+++ b/content/k3s/latest/en/security/secrets_encryption/_index.md
@@ -192,4 +192,46 @@ To re-enable secrets encryption on a HA cluster:
 
     ```
     k3s secrets-encrypt reencrypt --force --skip
-    ```
\ No newline at end of file
+    ```
+
+
+### Secrets Encryption Status
+The secrets-encrypt tool includes a `status` command that displays information about the current status of secrets encryption on the node.
+
+An example of the command on a single-server node:  
+```
+$ k3s secrets-encrypt status
+Encryption Status: Enabled
+Current Rotation Stage: start
+Server Encryption Hashes: All hashes match
+
+Active  Key Type  Name
+------  --------  ----
+ *      AES-CBC   aescbckey
+
+```
+
+Another example on HA cluster, after rotating the keys, but before restarting the servers:  
+```
+$ k3s secrets-encrypt status
+Encryption Status: Enabled
+Current Rotation Stage: rotate
+Server Encryption Hashes: hash does not match between node-1 and node-2
+
+Active  Key Type  Name
+------  --------  ----
+ *      AES-CBC   aescbckey-2021-12-10T22:54:38Z
+        AES-CBC   aescbckey
+
+```
+
+Details on each section are as followed:  
+
+- __Encryption Status__: Displayed whether secrets encryption is disabled or enabled on the node  
+- __Current Rotation Stage__: Indicates the current rotation stage on the node.  
+  Stages are: `start`, `prepare`, `rotate`, `reencrypt_request`, `reencrypt_active`, `reencrypt_finished`  
+- __Server Encryption Hashes__: Useful for HA clusters, this indicates whether all server are on the same stage with their local files. This can be used to identify whether a restart of servers is required before proceeding to the next stage. In the HA example above, node-1 and node-2 different hashes, indicating that they currently do not have the same encryption configuration. Restarting the servers will sync up their configuration.
+- __Key Table__: Summarizes information about the secrets encryption keys found on the node.  
+  * __Active__: The "*" indicates which, if any, of the keys are currently used for secrets encryption. An active key is used by kubernetes to encrypt any new secrets.
+  * __Key Type__: All keys using this tool are `AES-CBC` type. See more info [here.](https://kubernetes.io/docs/tasks/administer-cluster/encrypt-data/#providers)
+  * __Name__: Name of the encryption key.  
\ No newline at end of file