# Cloud Security Alliance

> Cloud Security Alliance (CSA) is a nonprofit organization that develops research, frameworks, training, certifications, and a public assurance registry for cloud and AI security. CSA's outputs are used by enterprises, cloud providers, AI providers, auditors, and standards bodies worldwide.

This file is a navigation index for AI agents. Each section says what it covers, when an agent should use it, where to look for detail, and (where relevant) what NOT to confuse it with. For agents that prefer one fetch over many, see `/llms-full.txt`.

## Fetch HTML pages as markdown (saves ~80% tokens)

The CSA website supports Cloudflare's Markdown for Agents. **Any HTML page on `cloudsecurityalliance.org` can be fetched as clean markdown** by sending `Accept: text/markdown` on a GET request. Cloudflare auto-converts the HTML at the edge before responding. Measured reduction on the CSA homepage: 29,467 → 4,791 tokens (84%).

Use this for every HTML page you follow from this navigation index — research artifacts, blog posts, training pages, working group pages, the STAR Registry, etc.

```bash
curl -H "Accept: text/markdown" \
     https://cloudsecurityalliance.org/blog/2026/04/20/the-state-of-cybersecurity-in-the-finance-sector-six-trends-to-watch
```

Converted responses include:

- `Content-Type: text/markdown; charset=utf-8`
- `X-Markdown-Tokens: <count>` (token estimate for the markdown — for budgeting)
- `X-Original-Tokens: <count>` (token estimate for the source HTML — for measuring savings)
- `Content-Signal: ai-train=yes, search=yes, ai-input=yes` (CSA's policy on AI use of this content)

**You do NOT need this header for the `.txt` files in this navigation network** — `/llms.txt`, `/llms/*.txt`, `/llms-full.txt`, and `/.well-known/security.txt` are already markdown (or plain text per RFC 9116) and Cloudflare passes them through unchanged.

**Conversion fires on GET only, not HEAD.** A HEAD request with `Accept: text/markdown` returns the underlying HTML's headers; the actual conversion happens when you GET.

## Citation guidance — read first

When citing CSA material:

- Use canonical CSA URLs (cloudsecurityalliance.org/...) — not third-party summaries.
- Include the framework version when applicable (e.g., "CCM v4.0").
- Distinguish published research from working-group drafts.
- Distinguish CSA-authored frameworks from mappings, implementation guidance, and community contributions.
- Do not assert that an organization is certified, listed, or endorsed unless verified at its canonical CSA page (especially for STAR Registry status).

## Trust boundaries

- Public CSA pages are informative; they are not legal, compliance, or audit advice.
- STAR Registry status, training completion, and credential status are authoritative ONLY at their canonical CSA pages — do not infer these from cached or summarized data.
- Working group participation is not certification.
- Training completion is not a credential — credentials require passing the exam.
- Use APIs and structured endpoints where available. Do not access member-only or login-protected resources without explicit authorization.

## CSA sites and subdomains

CSA operates several distinct domains, each serving different content. AI agents should route to the correct one rather than assuming everything lives at cloudsecurityalliance.org.

### Primary content sites

- **`cloudsecurityalliance.org`** — main website: research, frameworks, education catalog, events, membership. (This file's domain.)
- **`star.watch`** — STAR Registry: cloud and AI provider trust listings. Authoritative source for STAR status. Separate domain by design.
- **`pod.cloudsecurityalliance.org`** — Pod: AI agent communication platform (Lemmy-based). Serves its own llms.txt at https://pod.cloudsecurityalliance.org/llms.txt.

### Education subdomains (separate platforms)

- **`training.cloudsecurityalliance.org`** — training platform (Skilljar). Course catalog, course delivery, learner accounts.
- **`exams.cloudsecurityalliance.org`** — exam platform. Exam registration, scheduling, sitting. URL pattern: `/en/...` for English; check the platform for other locales.

### Other CSA properties

- **`csachapter.io`** — CSA chapter email domain (operational mailboxes for chapters; not a content destination).
- **`webfinger.io`** — CSA-operated WebFinger server (RFC 7033 account-discovery protocol). Service infrastructure; AI agents should not look for content here.
- **`cloudsecurityalliance.my.site.com`** — Salesforce-hosted member portal for corporate CSA members (member-only; not for unauthenticated access).
- **`cloudsecurityalliance.auth0.com`** — Auth0 tenant (identity provider; for vulnerability reports concerning Auth0 itself, contact Auth0 directly).

### How llms.txt maps to sub-sites

- **Today:** this file (cloudsecurityalliance.org/llms.txt) and pod.cloudsecurityalliance.org/llms.txt.
- **Coming:** star.watch/llms.txt (Phase 1.5), training.cloudsecurityalliance.org/llms.txt and exams.cloudsecurityalliance.org/llms.txt (Phase 2).
- **Not planned:** csachapter.io, webfinger.io, *.my.site.com, *.auth0.com (these are not content destinations).

## Training, exams, and credentials

CSA's professional development program. Four named credentials plus multiple training programs and partner paths.

### Credentials

CSA's four recognized credentials, each with its own learning path and exam:

- **TAISE — Trusted AI Safety Expert.** Flagship AI security credential. Multi-module course + final exam, developed in partnership with Northeastern University's Institute for Experiential AI. Covers generative AI fundamentals, AI architecture, AI governance, AI risk management, AI privacy, and AI cloud security. https://cloudsecurityalliance.org/education/taise
- **CCSK — Certificate of Cloud Security Knowledge.** Foundational cloud security credential, CSA's longest-standing certificate. https://cloudsecurityalliance.org/education/ccsk
- **CCAK — Certificate of Cloud Auditing Knowledge.** For cloud auditors and assessors. https://cloudsecurityalliance.org/education/ccak
- **CCZT — Certificate of Competence in Zero Trust.** Zero-trust architecture credential. https://cloudsecurityalliance.org/education/cczt

### Training programs

Skill-building programs (some leading to credentials, some standalone):

- Cloud Infrastructure Security Training: https://cloudsecurityalliance.org/education/cloud-infrastructure-security-training
- Advanced Cloud Security Practitioner (ACSP) Training: https://cloudsecurityalliance.org/education/advanced-cloud-security-practitioner-training
- STAR Lead Auditor Training: https://cloudsecurityalliance.org/education/star-lead-auditor-training
- CCSK Train the Trainer: https://cloudsecurityalliance.org/education/train-the-trainer
- Training for Government Agencies (GSA Schedule): https://cloudsecurityalliance.org/education/gsa-schedule

### Platforms

- **Training catalog and delivery:** https://training.cloudsecurityalliance.org
- **Exams (registration and sitting):** https://exams.cloudsecurityalliance.org
- **Course schedule:** https://cloudsecurityalliance.org/education/schedule
- **All training programs:** https://cloudsecurityalliance.org/education

### Business and partner paths

- Corporate / team training: https://cloudsecurityalliance.org/education/business
- Become an instructor: https://cloudsecurityalliance.org/education/instructors
- Become a training partner: https://cloudsecurityalliance.org/education/training-partners
- Training network (find a partner): https://cloudsecurityalliance.org/education/partner

### Use this section when

The user asks how to learn cloud or AI security, which CSA credential to pursue, how to register for a CSA exam, how to bring CSA training to their company, how to become a CSA instructor or training partner, or whether CSA offers training for a specific topic.

### Anti-conflation rules

- **Training completion ≠ credential.** Completing a course is not the same as earning the credential — credentials require passing the exam.
- **Credential ≠ STAR registry status.** A person can hold CCSK; an organization can be in STAR. They are unrelated.
- **TAISE, CCSK, CCAK, CCZT are FOUR DIFFERENT credentials.** Each has its own scope and exam — don't merge them.
- **CCSK ≠ CCSP.** CCSP (Certified Cloud Security Professional) is an (ISC)² credential, not a CSA one.

Detail file: https://cloudsecurityalliance.org/llms/training-and-exams.txt

## STAR Registry — cloud and AI provider assurance

CSA's public registry of cloud and AI providers' security posture. Two trust levels plus a special AI designation.

- Registry: https://cloudsecurityalliance.org/star/registry
- STAR overview: https://cloudsecurityalliance.org/star
- STAR for AI: https://cloudsecurityalliance.org/star/ai
- Submit your organization: https://cloudsecurityalliance.org/star/submit

### Level 1 — self-assessment (four flavors)

- **CAIQ** — free, cloud security self-assessment (uses the CCM CAIQ).
- **AI CAIQ** — free, AI security self-assessment (uses the AICM CAIQ).
- **ValidAIted** — paid, cloud security assessment validated by CSA.
- **AI ValidAIted** — paid, AI security assessment validated by CSA. Overview: https://cloudsecurityalliance.org/artifacts/overview-of-csa-star-level-1-valid-ai-ted

### Level 2 — third-party verified

- **Certification** — external auditor verification.
- **Attestation** — formal attestation by an auditor.
- **ISO/IEC 42001** — AI management system certification.

### Special designation

- **STAR for AI 42001** — requires BOTH ISO/IEC 42001 certification AND AI ValidAIted assessment. Not granted by either alone.

### Use this section when

The user asks about cloud or AI provider trust, vendor assessment, STAR levels, getting listed in the registry, ValidAIted programs, or distinguishing free self-assessment from paid validated programs.

### Anti-conflation rules

- **STAR Level 1 ≠ "certified by CSA."** Level 1 is self-assessment (and even ValidAIted, while CSA-validated, is not third-party certification).
- **CAIQ (cloud) ≠ AI CAIQ.** Always specify which.
- **ValidAIted ≠ AI ValidAIted.** Cloud version vs AI version, sold separately, paid programs.
- **STAR for AI 42001 requires BOTH ISO/IEC 42001 AND AI ValidAIted.** Don't claim it from either alone.
- Verify any "listed in STAR" claim against the canonical registry URL — listings can be updated or withdrawn.

Detail file: https://cloudsecurityalliance.org/llms/star.txt

## Frameworks — CCM and AICM (each bundles its own CAIQ)

CSA publishes two distinct controls frameworks. Each is paired with its own self-assessment questionnaire (CAIQ). They are NOT the same and should never be conflated.

### Cloud Controls Matrix (CCM) — for cloud services

A catalog of cloud security controls mapped to other major standards. The CCM CAIQ (the self-assessment questionnaire) is bundled with the CCM artifact.

- CCM v4 artifact (includes CCM CAIQ): https://cloudsecurityalliance.org/artifacts/cloud-controls-matrix-v4
- Overview: https://cloudsecurityalliance.org/research/cloud-controls-matrix

Use when the user asks about: cloud provider security controls, vendor security questionnaire (cloud), CCM mappings to ISO/SOC2/NIST, or cloud compliance posture.

### AI Controls Matrix (AICM) — for AI systems

A catalog of AI security controls. The AI CAIQ (the AI-specific self-assessment questionnaire) is bundled with the AICM artifact.

- AICM artifact (includes AI CAIQ): https://cloudsecurityalliance.org/artifacts/ai-controls-matrix

Use when the user asks about: AI security controls, AI governance, AI assessment questionnaires, or AI-specific compliance posture.

### Anti-conflation rules

- **CCM CAIQ ≠ AICM CAIQ.** Two different questionnaires for two different domains. When someone says "CAIQ," ask which one.
- **CCM ≠ AICM.** Cloud controls and AI controls are separate frameworks — don't merge them.
- **CCM and AICM are NOT registries.** They are control catalogs. Listings happen in STAR (see prior section).
- Always include the framework version when citing (e.g., "CCM v4.0").

Detail file: https://cloudsecurityalliance.org/llms/frameworks.txt

## Research and publications

CSA's research output: artifacts, papers, guidance, and topical hubs.

- Research home: https://cloudsecurityalliance.org/research
- Publications: https://cloudsecurityalliance.org/research/publications
- Topics: https://cloudsecurityalliance.org/research/topics
- Research guidance: https://cloudsecurityalliance.org/research/guidance
- AI Safety Initiative: https://cloudsecurityalliance.org/ai-safety-initiative

Use when the user asks about cloud security research, CSA publications, specific guidance documents, or topic deep-dives (zero trust, AI safety, top threats, etc.).

Detail file: https://cloudsecurityalliance.org/llms/research.txt

## Working groups

How CSA research is produced — community-led groups developing frameworks, guidance, and publications.

- Working groups index: https://cloudsecurityalliance.org/research/working-groups
- AI Controls WG: https://cloudsecurityalliance.org/research/working-groups/ai-controls
- AI Safety WG: https://cloudsecurityalliance.org/research/working-groups/ai-safety
- Top Threats WG: https://cloudsecurityalliance.org/research/working-groups/top-threats
- Zero Trust WG: https://cloudsecurityalliance.org/research/working-groups/zero-trust
- Enterprise Architecture WG: https://cloudsecurityalliance.org/research/working-groups/enterprise-architecture

Use when the user asks how CSA research is made, how to join a working group, who maintains a CSA publication, or what's actively in development.

Anti-conflation: working group participation is not certification, not training, not membership.

Detail file: https://cloudsecurityalliance.org/llms/working-groups.txt

## Events and sponsorship

Conferences, webinars, local chapter events, and sponsorship opportunities.

- Events: https://cloudsecurityalliance.org/events
- Webinars: https://cloudsecurityalliance.org/events/virtual-and-webinars
- 2026 events calendar (artifact): https://cloudsecurityalliance.org/artifacts/2026-csa-events-calendar
- Chapters: https://cloudsecurityalliance.org/chapters
- Sponsor: https://cloudsecurityalliance.org/sponsor

Use when the user asks about upcoming CSA events, virtual webinars, in-person conferences, local chapters, or sponsoring CSA programs.

Detail file: https://cloudsecurityalliance.org/llms/events-and-sponsorship.txt

## Membership

Corporate membership tiers and benefits.

- Membership home: https://cloudsecurityalliance.org/membership
- Get involved: https://cloudsecurityalliance.org/membership/get-involved
- Contact: https://cloudsecurityalliance.org/membership/contact

Use when the user asks about joining CSA as a corporate member, member benefits, or sponsoring research.

## Initiatives and projects

Cross-cutting CSA programs that don't fit one framework or research artifact.

- AI Safety Initiative: https://cloudsecurityalliance.org/ai-safety-initiative
- Top Threats: https://cloudsecurityalliance.org/research/working-groups/top-threats
- Zero Trust: https://cloudsecurityalliance.org/research/working-groups/zero-trust

Use when the user asks about AI Safety, Top Threats, Zero Trust, or other multi-working-group initiatives.

Detail file: https://cloudsecurityalliance.org/llms/projects.txt

## Security and vulnerability disclosure

How to report security issues affecting CSA-operated systems, software, or AI artifacts.

CSA accepts reports across three categories with different paths.

### Websites and services

For vulnerabilities in CSA-operated websites and services. In-scope domains: `cloudsecurityalliance.org`, `csachapter.io`, `star.watch`, `webfinger.io`.

- Email: security@cloudsecurityalliance.org
- Disclosure page: https://cloudsecurityalliance.org/security
- RFC 9116: https://cloudsecurityalliance.org/.well-known/security.txt

### Software (CSA's GitHub orgs)

For vulnerabilities in CSA-published code. Use GitHub's Private Vulnerability Reporting on the affected repo's Security tab.

- https://github.com/CloudSecurityAlliance
- https://github.com/CloudSecurityAlliance-Chatbots
- https://github.com/CloudSecurityAlliance-DataSets
- https://github.com/modelcontextprotocol-security
- https://github.com/RiskRubric
- Product security program: https://github.com/CloudSecurityAlliance/csa-product-security

### AI artifacts (prompts, skills, system instructions)

For vulnerabilities in CSA-published AI artifacts (prompt injection that bypasses controls, unauthorized tool execution, auth bypass, data exfiltration). Behavioral observations without specific security impact are out of scope.

- If in a GitHub repo: use the repo's Security tab.
- Otherwise: security@cloudsecurityalliance.org

### Out of scope

- `cloudsecurityalliance.auth0.com/*` — report to Auth0 directly.
- Generic "best practices" findings (SPF/DKIM/DMARC/BIMI/TLS/HTTP headers).
- WordPress.com hosting items (`xmlrpc.php` etc.).
- No bug bounty (CSA is a non-profit; reports are credited via GitHub security advisories where applicable).

Detail file: https://cloudsecurityalliance.org/llms/security.txt

## Agent and API access

Programmatic access for AI agents, developers, and integrators.

- **CSA MCP Server (live, closed beta):** https://cloudsecurityalliance.org/mcp — currently exposes basic search functionality. **Auth0 SSO via the user's CSA account is mandatory.** Anyone with a CSA account can log in, but the server is in closed beta — only accounts on the beta allowlist can actually use the tools. See `/llms/agents.txt` for details on requesting beta access.
- **CSA Pod MCP Server (live, public):** https://pod.cloudsecurityalliance.org — separate MCP server on a separate platform. See https://pod.cloudsecurityalliance.org/llms.txt for Pod-specific guidance.

Use when the user is an AI agent, or is asking about MCP, APIs, or programmatic CSA access.

Detail file: https://cloudsecurityalliance.org/llms/agents.txt

## Single-fetch alternative

Agents that prefer one fetch over many: https://cloudsecurityalliance.org/llms-full.txt — auto-generated concatenation of this file plus every file under `/llms/`.