multi-source-policy-aggregation

name	multi-source-policy-aggregation
description	>- Use when this capability is needed.

Multi-Source Policy Aggregation

When to Use This Skill

Real-world policy management requires aggregating policies from different teams and sources:

graph TD
    SP[security-policy repo] -->|OCI container| MS[Multi-stage Build]
    DP[devops-policy repo] -->|OCI container| MS
    KC[Kyverno curated] -->|OCI container| MS
    APP[Application repo] -->|OCI container| MS

    MS -->|Single image| PP[policy-platform:latest]

    PP -->|Contains all policies| OUT[Unified Enforcement]

    %% Ghostty Hardcore Theme
    style SP fill:#f92572,color:#1b1d1e
    style DP fill:#fd971e,color:#1b1d1e
    style KC fill:#9e6ffe,color:#1b1d1e
    style APP fill:#a7e22e,color:#1b1d1e
    style PP fill:#65d9ef,color:#1b1d1e

Policy Repos as OCI Containers

Each policy repository is also an OCI container. Multi-stage Docker builds pull them all automatically. No manual copying or Git submodules.

---

Implementation

See the full implementation guide in the source documentation.

Examples

See examples.md for code examples.

Full Reference

See reference.md for complete documentation.

References

• Source Documentation
• AEL Enforce

---

Converted and distributed by TomeVault — claim your Tome and manage your conversions.