[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 の本文から書いたものです。