# Start by role

> Five walkthroughs for AppSec engineers, AI engineers, security leaders, partners, and students.

Source: https://keryn.dev/docs/start/by-role/

Use the sample projects to see a release decision, trace data through an AI agent, or export a report in [Keryn Web](https://keryn.app). The partner path also uses a Keryn Cloud account. The student walkthrough includes a local exercise for readers with access to the Keryn CLI.

- [AppSec engineer](https://keryn.dev/docs/start/appsec-engineer/): Why the release is held, the flow from a prompt to a shell, and SARIF for your code scanning.
- [AI engineer shipping agents](https://keryn.dev/docs/start/ai-engineer/): Every model, SDK and MCP server your agent uses, and where untrusted input can reach them.
- [CISO or buyer](https://keryn.dev/docs/start/security-leader/): The findings mapped to your frameworks, a posture assessment, what is measured and what it costs.
- [Partner or OEM](https://keryn.dev/docs/start/partner/): Results as SARIF and CycloneDX your product reads, and a first trust scan on Keryn Cloud through its API.
- [Student](https://keryn.dev/docs/start/student/): Read a detection rule, check a fix with the CLI, and start the Academy speed run.
