huawei-cloud-ucs-policy-governor

• Outcome: Review
• Latest audit: Aug 3, 2026 · 9:21 AM UTC
• Version: 1.0.0

Overview

This appears to be a legitimate Huawei Cloud UCS policy-management skill, but it needs review because some audit and verification steps obtain cluster credentials and change enforcement state without enough guardrails.

Install only if you intend the agent to help with Huawei Cloud UCS policy administration, not just read-only auditing. Use least-privilege or temporary credentials, avoid granting the full governance policy broadly, run mutation examples only on explicitly chosen test or approved production resources, and treat any generated kubeconfig as a sensitive credential that should be protected and removed after use.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Excessive Agency: Unrestricted Tool Access, Autonomous Decision Making, Scope Creep
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (11)

Context-Inappropriate Capability

Medium

• Confidence: 92% confidence
• Finding: The file is scoped as a compliance audit/governance task, but it expands into operational remediation by generating a cluster kubeconfig, running kubectl against the cluster, and toggling policy state. This scope creep increases privilege use and can cause unauthorized or unsafe changes if an agent follows the workflow automatically under the guise of a read-only audit.

Context-Inappropriate Capability

Medium

• Confidence: 87% confidence
• Finding: The compliance audit scenario introduces cluster registration, which is a state-changing administrative action unrelated to reviewing compliance evidence. Including provisioning or onboarding actions in an audit task can mislead agents or operators into performing unexpected infrastructure changes during what should be a low-risk assessment workflow.

Missing User Warnings

Medium

• Confidence: 93% confidence
• Finding: The document enumerates write-capable IAM permissions for creating, updating, deleting, enabling, and disabling UCS policies, but it does not explicitly warn that these actions can change enforcement state, remove governance controls, or disrupt compliance posture. In a governance skill, presenting a broad write policy JSON without prominent destructive-impact guidance increases the chance that users overprovision access and unintentionally grant powerful permissions more widely than necessary.

Missing User Warnings

Medium

• Confidence: 95% confidence
• Finding: The document instructs creation of a kubeconfig file without any warning that it contains cluster access credentials and should be treated as sensitive material. Writing it to a local file can expose administrative access through shell history, workspace leakage, logs, backups, or weak filesystem permissions.

Missing User Warnings

Medium

• Confidence: 90% confidence
• Finding: The remediation workflow disables and re-enables cluster policy without warning about service impact, temporary loss of enforcement, or unintended configuration drift. An operator or agent may execute these steps routinely, creating a compliance blind spot or interrupting protections on production clusters.

Missing User Warnings

Medium

• Confidence: 93% confidence
• Finding: The verification guide includes state-changing governance commands such as enabling, disabling, creating, and updating policy instances in what is framed as routine verification. Even without explicit malice, these actions can alter enforcement behavior across clusters or fleet groups, causing compliance drift, outages, or unexpected policy denial in real environments if copied verbatim.

Credential Access

High

• Category: Privilege Escalation

Content

hcloud UCS ListPolicyJobs --kind=EnablePolicy --cli-region=cn-north-4
hcloud UCS ShowPolicyJob --jobid=<job-id> --cli-region=cn-north-4

# 2. Access the cluster with kubeconfig
hcloud UCS CreateClusterKubeconfig --clusterid=<ucs-cluster-id> --cli-region=cn-north-4 > cluster-kubeconfig.yaml

# 3. Fix violations using kubectl

• Confidence: 93% confidence
• Finding: The workflow explicitly instructs obtaining cluster credentials via CreateClusterKubeconfig in an audit context. This grants direct cluster access beyond governance review and materially increases the risk of credential exposure or misuse by an agent, user, or adjacent tooling.

Credential Access

High

• Category: Privilege Escalation

Content

hcloud UCS ShowPolicyJob --jobid=<job-id> --cli-region=cn-north-4

# 2. Access the cluster with kubeconfig
hcloud UCS CreateClusterKubeconfig --clusterid=<ucs-cluster-id> --cli-region=cn-north-4 > cluster-kubeconfig.yaml

# 3. Fix violations using kubectl
kubectl --kubeconfig=cluster-kubeconfig.yaml apply -f <fix-manifest>

• Confidence: 91% confidence
• Finding: The same kubeconfig creation step is dangerous not just because of file persistence but because it normalizes credential retrieval inside a task presented as compliance auditing. This broadens the task from observation to privileged access, increasing the likelihood that automated execution will overreach user intent.

Credential Access

High

• Category: Privilege Escalation

Content

hcloud UCS ShowPolicyJob --jobid=<job-id> --cli-region=cn-north-4

# 2. Access the cluster with kubeconfig
hcloud UCS CreateClusterKubeconfig --clusterid=<ucs-cluster-id> --cli-region=cn-north-4 > cluster-kubeconfig.yaml

# 3. Fix violations using kubectl
kubectl --kubeconfig=cluster-kubeconfig.yaml apply -f <fix-manifest>

• Confidence: 91% confidence
• Finding: The same kubeconfig creation step is dangerous not just because of file persistence but because it normalizes credential retrieval inside a task presented as compliance auditing. This broadens the task from observation to privileged access, increasing the likelihood that automated execution will overreach user intent.

Credential Access

High

• Category: Privilege Escalation

Content

hcloud UCS CreateClusterKubeconfig --clusterid=<ucs-cluster-id> --cli-region=cn-north-4 > cluster-kubeconfig.yaml

# 3. Fix violations using kubectl
kubectl --kubeconfig=cluster-kubeconfig.yaml apply -f <fix-manifest>

# 4. Re-trigger enforcement
hcloud UCS DisableClusterPolicy --clusterid=<ucs-cluster-id> --cli-region=cn-north-4

• Confidence: 88% confidence
• Finding: The combination of kubeconfig creation and immediate kubectl apply encourages end-to-end credential acquisition and use without any guardrails, review, or cleanup guidance. That pattern can facilitate unauthorized changes, accidental misuse, and lingering credential artifacts in automation environments.

Credential Access

High

• Category: Privilege Escalation

Content

hcloud UCS CreateClusterKubeconfig --clusterid=<ucs-cluster-id> --cli-region=cn-north-4 > cluster-kubeconfig.yaml

# 3. Fix violations using kubectl
kubectl --kubeconfig=cluster-kubeconfig.yaml apply -f <fix-manifest>

# 4. Re-trigger enforcement
hcloud UCS DisableClusterPolicy --clusterid=<ucs-cluster-id> --cli-region=cn-north-4

• Confidence: 88% confidence
• Finding: The combination of kubeconfig creation and immediate kubectl apply encourages end-to-end credential acquisition and use without any guardrails, review, or cleanup guidance. That pattern can facilitate unauthorized changes, accidental misuse, and lingering credential artifacts in automation environments.

VirusTotal

VirusTotal findings are pending for this skill version.

Static analysis

No suspicious patterns detected.