#Default Policies in Alauda Security Service

Alauda Security Service provides built-in system policies to help you prevent high-risk deployments and respond to runtime incidents in Kubernetes environments. These policies cover common vulnerability, configuration, runtime, and supply chain checks and provide the baseline for day-to-day policy management.

#Overview

Default policies cover the full container lifecycle: build, deploy, and runtime. You can review them from Platform Configuration > Policy Management, clone them, and then tailor the cloned copies for your own environment. Default policies cannot be deleted or edited in place.

The exact policy inventory can vary by release, enabled integrations, and imported content. The tables below summarize the default policies commonly present in supported deployments.

#Viewing Policies

1. Go to Platform Configuration > Policy Management in the portal.
2. Review the Policies table and use filters, search, or categories to narrow the list.
3. Use the row actions or policy details page to view policy logic or clone a default policy.

#Policy Table Structure

• Policy: Policy name
• Description: What the policy detects or enforces
• Status: Enabled or Disabled
• Severity: Critical, High, Medium, or Low
• Lifecycle: Build, Deploy, or Runtime

---

#Critical Severity Policies

---

#High Severity Policies

---

#Medium Severity Policies

---

#Low Severity Policies

---

#Managing Default Policies

• Default policies provide broad security coverage.
• You can view, clone, and edit cloned default policies in the portal.
• Default policies cannot be deleted or directly modified.