sail
starsforks
How to install sail?
pillar-labs/sail-skill/sail
$npx -y skills add pillar-labs/sail-skill --skill sailApply the SAIL (Secure AI Lifecycle) V2 framework by Pillar Security to secure AI applications and agents. Use this skill whenever the user asks about AI or agent security — assessing an AI system or agent architecture for risks, building an AI security roadmap or maturity assess
SKILL.md
| 1 | # SAIL V2 — Secure AI Lifecycle Framework |
| 2 | |
| 3 | SAIL is Pillar Security's framework for building, deploying, and operating AI systems and agents securely. It is a working tool, not a reading exercise: users bring real systems, policies, and compliance obligations, and expect concrete, catalog-grounded answers. Whether they are writing their first AI policy or already operating hundreds of agents, SAIL is used to: |
| 4 | |
| 5 | 1. **Build an AI security roadmap** — walk the seven phases in order, assess coverage at each; the gaps, sequenced by phase, become the roadmap. |
| 6 | 2. **Assess AI security maturity** — score each relevant risk (unaddressed / partially mitigated / mitigated with evidence) into a per-phase maturity profile trendable over time. |
| 7 | 3. **Generate a compliance checklist** — filter the catalog by the framework the user is accountable to (ISO/IEC 42001, EU AI Act, OWASP, DASF, AIUC-1). |
| 8 | 4. **Prioritize controls** — focus on risks that intersect the user's zones, assets, and weakest phase; autonomy tiers (SAIL 1.11) set control intensity per agent. |
| 9 | 5. **Run vendor assessments and RFPs** — turn the catalog into a general RFP questionnaire (for security vendors or platform vendors), with questions mapped back to SAIL risk clusters. |
| 10 | 6. **Align security, legal, compliance, and engineering** — SAIL IDs give all four teams one shared vocabulary for design reviews, risk registers, and exception requests. |
| 11 | |
| 12 | Each has a workflow below. |
| 13 | |
| 14 | ## Core structure (memorize this, cite it constantly) |
| 15 | |
| 16 | **Three zones** define *where* agentic risk materializes (drawn by where the risk lands, not where the process runs): |
| 17 | |
| 18 | - **Zone 1 — AI Assets in Code & Pipeline**: models, datasets, prompts, agent configs, AI-generated code as artifacts in repos and CI/CD. Static surface; a poisoned artifact propagates into every build. |
| 19 | - **Zone 2 — Cloud Agents**: agents executing inside managed platforms (Copilot Studio, Agentforce, Bedrock AgentCore, etc.) under platform-issued identities. |
| 20 | - **Zone 3 — Endpoint Agents**: agents running on user devices with user credentials (Claude Code, Cursor, browser agents). |
| 21 | |
| 22 | **Seven lifecycle phases** define *when* controls apply. Each phase has a numbered risk catalog — 91 risks total, each with an ID like `SAIL 3.4`: |
| 23 | |
| 24 | | Phase | Name | Lifecycle stage | Risk IDs | |
| 25 | | :-- | :-- | :-- | :-- | |
| 26 | | 1 | AI Policy | Plan | SAIL 1.x | |
| 27 | | 2 | AI Discovery | Code/No Code | SAIL 2.x | |
| 28 | | 3 | Agentic Posture Management | Build | SAIL 3.x | |
| 29 | | 4 | Agentic Red Teaming | Test | SAIL 4.x | |
| 30 | | 5 | Runtime Controls | Deploy | SAIL 5.x | |
| 31 | | 6 | Sandbox | Operate | SAIL 6.x | |
| 32 | | 7 | Govern | Monitor & Retire | SAIL 7.x | |
| 33 | |
| 34 | Every risk row in the catalog carries: description, concrete example, assets affected, mitigations, and standards mappings (ISO/IEC 42001, EU AI Act, OWASP LLM Top 10, OWASP Agentic, DASF, AIUC-1). SAIL IDs are the shared vocabulary — always cite them (e.g., "this maps to SAIL 5.17") so security, legal, compliance, and engineering can reference the same rows in risk registers and design reviews. |
| 35 | |
| 36 | ## Ground every answer in the catalog |
| 37 | |
| 38 | Do not answer SAIL questions from general knowledge. The value of this skill is the actual catalog text — the mitigations, examples, and standards mappings the user's auditors and vendors will check against. Before making claims: |
| 39 | |
| 40 | 1. Read `references/risk-index.md` first — all 91 risks in one compact table (ID, name, one-line summary, phase, file). Use it to decide which risks are in scope. |
| 41 | 2. Read the full phase file(s) for every risk you cite, so mitigations and standards mappings are quoted accurately, not paraphrased from memory. |
| 42 | |
| 43 | ## Reference files |
| 44 | |
| 45 | | File | Contents | Read when | |
| 46 | | :-- | :-- | :-- | |
| 47 | | `references/risk-index.md` | All 91 risks: ID, name, summary, phase | Almost always — this is your map | |
| 48 | | `references/framework.md` | Executive summary, Chapter 1 (agentic workforce, the three zones with per-surface risk tables), Chapter 2 (phase overview, agentic stack components, how to use SAIL) | Explaining the framework, scoping zones, writing intros for deliverables | |
| 49 | | `references/phase-1-policy.md` … `phase-7-govern.md` | Full risk catalog per phase: descriptions, examples, as |
People who liked this also viewed
6 picksType
- entra-app-registrationGuides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API perSkillsJul 2026
- azure-complianceRun Azure compliance and security audits with azqr plus Key Vault expiration checks. Covers best-practice assessment, resource review, policy/compliance validation, and security posture checks. WHEN: SkillsJul 2026
- azure-rbacOfficial agent plugin providing skills and MCP server configurations for Azure scenarios.SkillsJul 2026
- better-auth-best-practicesAgent skill from better-auth/skillsSkillsJul 2026
- firebase-security-rules-auditorA skill to evaluate how secure Firestore security rules are. Use this when Firestore security rules are updated to ensure that the generated rules are extremely secure and robust.SkillsJul 2026
- audit-websiteAudit a website with the squirrelscan CLI and fix the findings in code. Runs SEO, performance, security, technical, content, accessibility, and 15 other rule categories (260+ rules), returns an LLM-opSkillsJul 2026
