> For the complete documentation index, see [llms.txt](https://docs.sealsecurity.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealsecurity.io/introduction/navigating-the-docs.md).

# What you will find in these docs

These docs are organized into ten sections, ordered roughly from "what is this?" to "look up the exact flag I need."

## The section map

* [**Introduction**](/welcome-to-seal-security.md) (you are here): what Seal is, how it works, who it is for, and the vocabulary used throughout the docs.
* [**Getting started**](/getting-started/sign-up-and-sign-in.md): sign-in, user management, tokens, your first Seal Project, and an end-to-end Proof of Value walkthrough.
* [**Discovering vulnerabilities**](/discovering/how-seal-discovers-your-packages.md): how Seal finds your packages and how to navigate the platform to triage findings, including the Protection page, package states, and the Repository page.
* [**Using the Seal Platform**](/using-platform/working-with-the-platform.md): the day-to-day operating manual. Sealing Rules, working with each of the five products, the Seal AI Agent, the Seal Engineer, the Notification Center, the Reports Manager, and the Usage page.
* [**Application and OS setup**](/setup-apps-os/choosing-deployment-method.md): day-1 setup guides for Seal Apps and Seal OS, including the Seal CLI in CI/CD, the Seal Artifact Server, and standalone on-prem environments.
* [**Container and image setup**](/setup-containers/seal-base-images.md): day-1 setup guides for Seal Base Images, Seal My Container, and Seal Vendor Apps.
* [**Integrations**](/integrations/internal-scanners.md): connecting Seal to internal SCA scanners, external scanner feeds, JFrog Artifactory, GitHub, and the package renaming feature.
* [**Trust & compliance**](/trust/why-this-matters.md): code diff transparency, attestations, cryptographic signing, the 72-hour SLA, and supported compliance frameworks.
* [**Reference**](/reference/cli.md): CLI commands and flags, Public API, naming and versioning conventions, and network requirements.
* [**FAQ & disclosure**](/faq-and-disclosure/faq.md): frequently asked questions and the vulnerability disclosure policy.

## Find your starting point by role

| Role                 | Focus                                                           | Start here                                                                        |
| -------------------- | --------------------------------------------------------------- | --------------------------------------------------------------------------------- |
| **Security leader**  | Evaluating Seal; reviewing the Dashboard and reports            | [If you're a security leader](/introduction/audience-guides/security-leader.md)   |
| **DevOps engineer**  | Setting up integrations; operating the platform side day to day | [If you're a DevOps engineer](/introduction/audience-guides/devops-engineer.md)   |
| **Developer**        | Integrating the Seal CLI; applying Sealing Rules                | [If you're a developer](/introduction/audience-guides/developer.md)               |
| **Security analyst** | Day-to-day triage, notifications, and reports for leadership    | [If you're a security analyst](/introduction/audience-guides/security-analyst.md) |

The DevOps guide also covers DevSecOps and platform engineers; everyone responsible for the platform side of operating Seal in your organization.

## Key terms

Seal uses a precise vocabulary across these docs. The most common terms you will encounter:

* A **sealed package** is a drop-in replacement for a public package version, with security fixes backported in.
* A **Sealing Rule** tells Seal which package to replace and with which sealed version.
* A **Seal Project** is the entity inside the Seal Platform that represents one of your codebases or build pipelines.
* The **package discovery mode** of a Seal Project determines how Seal sees your packages: source code, CLI, artifact server, or imported manifest.
* A **deployment method** is how Seal is integrated into your environment, for example the Seal CLI in CI/CD, or the Seal Artifact Server as a configured remote.
* The **CLI fix mode** is the mode the Seal CLI runs in: **local** mode (rules from a `.seal-actions.yml` file in your source), **remote** mode (rules from the Seal Platform UI), or **all** mode (every vulnerable package replaced automatically).

The full vocabulary is in the [Glossary](/introduction/glossary.md).