[Hardening] F-10: No 2FA Verification Required Before Destructive or Sensitive Operations.

### The required feature described as a wish

**Description:** CloudStack does not require users to re-verify their identity (step-up authentication) before performing high-impact operations such as deleting or expunging resources or resetting and revealing secrets, such as API keys of other user accounts. Once a user is authenticated for a session, all actions are permitted without additional verification.

**Affected Components:** Management UI

**Impact:** If a valid user session is hijacked (e.g., through XSS, session token theft, or an unattended workstation), an attacker can immediately perform irreversible, destructive actions or extract sensitive credentials without any additional authentication barrier. Requiring TOTP verification as a step-up factor would block this attack vector, whereas a Static PIN would not, as it offers no time-bound or replay-resistant protection.

**Steps to Reproduce:**
- Log in to the CloudStack Management UI as a Root Admin.
- Navigate to Compute > Instances > Select any instance > Click on Delete.
- Observe that the action proceeds to a confirmation dialog without any prompt for TOTP verification.

**Recommended Remediation:** Implement step-up authentication for a defined list of sensitive or destructive operations. Require the user to enter their current TOTP code before executing the operation. Log all step-up authentication events for auditing.

先檢視重現步驟中描述的 CloudStack Management UI 流程，從執行個體刪除和現有的確認對話方塊開始。定義所涵蓋的敏感操作和破壞性操作，然後確認在執行前是否需要目前的 TOTP 驗證，以及 step-up 事件是否會被記錄以供稽核。

由索引模型根據 Issue 內容生成。