# New Documentation

- [New Documentation (in progress)](https://docs.sealsecurity.io/new-documentation/new-docs.md): The remediation platform for open-source vulnerabilities.
- [What is Seal Security](https://docs.sealsecurity.io/new-documentation/new-docs/what-is-seal.md): What Seal does, what it covers, and how it works alongside your existing tools.
- [What you will find in these docs](https://docs.sealsecurity.io/new-documentation/new-docs/navigating-the-docs.md): The section map, role-based starting points, and key terms.
- [The remediation problem](https://docs.sealsecurity.io/new-documentation/new-docs/remediation-problem.md): Why remediating open-source vulnerabilities is hard, and what the cost of chasing upgrades does to a team.
- [Why remediation is hard](https://docs.sealsecurity.io/new-documentation/new-docs/remediation-problem/why-remediation-is-hard.md): The upgrade cascade, transitive dependencies, hard-versus-trivial upgrades, no-upgrade-path cases, container patching, and EOL components.
- [The cost of chasing upgrades](https://docs.sealsecurity.io/new-documentation/new-docs/remediation-problem/the-cost-of-chasing-upgrades.md): Off-cadence interruptions, the hard-upgrade tail, lost knowledge, code base growth, and the deferred-exception pile.
- [The Seal approach](https://docs.sealsecurity.io/new-documentation/new-docs/seal-approach.md): Drop-in replacements, sealed packages, sealing approaches, and the trust posture that ships with every artifact.
- [Drop-in replacements, not upgrades](https://docs.sealsecurity.io/new-documentation/new-docs/seal-approach/drop-in-replacements.md): A sealed package replaces a vulnerable version without changing your code.
- [What a sealed package is](https://docs.sealsecurity.io/new-documentation/new-docs/seal-approach/sealed-packages.md): How a sealed version is built, the sealed-version suffix, what is covered by default, and what an open vulnerability means.
- [How sealed packages are delivered](https://docs.sealsecurity.io/new-documentation/new-docs/seal-approach/sealing-approaches.md): Build-time dependency sealing versus post-build artifact sealing, and when each applies.
- [Trust by default](https://docs.sealsecurity.io/new-documentation/new-docs/seal-approach/trust-by-default.md): Code diff, attestations, and signing. A short overview.
- [The Seal product family](https://docs.sealsecurity.io/new-documentation/new-docs/product-family.md): Five products covering your stack, all built on the same sealing approach.
- [Seal Apps](https://docs.sealsecurity.io/new-documentation/new-docs/product-family/seal-apps.md): Sealed packages for your application's third-party open-source dependencies.
- [Seal OS](https://docs.sealsecurity.io/new-documentation/new-docs/product-family/seal-os.md): Sealed APK, DEB, and RPM packages for Linux servers and containers, including EOL distributions.
- [Seal Base Images](https://docs.sealsecurity.io/new-documentation/new-docs/product-family/seal-base-images.md): Sealed replacements for the public container base images you build on top of.
- [Seal My Container](https://docs.sealsecurity.io/new-documentation/new-docs/product-family/seal-my-container.md): Container-to-container sealing of your private container images.
- [Seal Vendor Apps](https://docs.sealsecurity.io/new-documentation/new-docs/product-family/seal-vendor-apps.md): Open-source remediation inside containers shipped by your vendors.
- [Architecture overview](https://docs.sealsecurity.io/new-documentation/new-docs/architecture.md): The Seal components, how they fit together, and where your data lives.
- [Components](https://docs.sealsecurity.io/new-documentation/new-docs/architecture/components.md): The seven named components that make up the Seal Platform.
- [How the pieces fit together](https://docs.sealsecurity.io/new-documentation/new-docs/architecture/how-pieces-fit-together.md): One diagram of how the Seal components connect.
- [Where your data lives](https://docs.sealsecurity.io/new-documentation/new-docs/architecture/where-your-data-lives.md): What Seal sees in each package discovery mode, and what it never sees.
- [Your first hour with Seal, by role](https://docs.sealsecurity.io/new-documentation/new-docs/audience-guides.md): Role-based starting points. Pick the page that matches what you do.
- [If you're a security leader](https://docs.sealsecurity.io/new-documentation/new-docs/audience-guides/security-leader.md): How to navigate the Seal docs as a security leader.
- [If you're a DevOps engineer](https://docs.sealsecurity.io/new-documentation/new-docs/audience-guides/devops-engineer.md): How to navigate the Seal docs as a DevOps, DevSecOps, or platform engineer.
- [If you're a developer](https://docs.sealsecurity.io/new-documentation/new-docs/audience-guides/developer.md): How to navigate the Seal docs as a developer.
- [If you're a security analyst](https://docs.sealsecurity.io/new-documentation/new-docs/audience-guides/security-analyst.md): How to navigate the Seal docs as a security analyst.
- [Glossary](https://docs.sealsecurity.io/new-documentation/new-docs/glossary.md): The Seal-specific vocabulary used throughout these docs.
- [Sign up and sign in](https://docs.sealsecurity.io/new-documentation/new-docs/sign-up-and-sign-in.md): Activating your invite, signing in, and switching tenants.
- [The onboarding wizard](https://docs.sealsecurity.io/new-documentation/new-docs/onboarding-wizard.md): A guided three-stage setup that runs the first time anyone signs in to a new tenant.
- [Managing users, roles & SSO](https://docs.sealsecurity.io/new-documentation/new-docs/users-and-sso.md): User roles, inviting team members, and configuring single sign-on.
- [User roles](https://docs.sealsecurity.io/new-documentation/new-docs/users-and-sso/user-roles.md): The four user roles in Seal and the permission matrix.
- [Inviting and managing users](https://docs.sealsecurity.io/new-documentation/new-docs/users-and-sso/inviting-users.md): Inviting team members, changing their roles, and revoking access.
- [SSO and SAML](https://docs.sealsecurity.io/new-documentation/new-docs/users-and-sso/sso-and-saml.md): Connecting your identity provider through Seal's authentication portal.
- [Managing tokens](https://docs.sealsecurity.io/new-documentation/new-docs/tokens.md): Production and development tokens, how to generate them, and how to handle them safely.
- [Token types](https://docs.sealsecurity.io/new-documentation/new-docs/tokens/token-types.md): Production tokens versus development tokens, and when to use each.
- [Generating and revoking tokens](https://docs.sealsecurity.io/new-documentation/new-docs/tokens/generating-tokens.md): Creating a token, copying it during the one-time reveal, and revoking it.
- [Token security best practices](https://docs.sealsecurity.io/new-documentation/new-docs/tokens/best-practices.md): Scoping, rotating, and storing Seal tokens safely.
- [Creating a Seal Project](https://docs.sealsecurity.io/new-documentation/new-docs/creating-a-seal-project.md): Creating, naming, and managing the Seal Projects that represent your codebases and pipelines.
- [Your first Proof of Value](https://docs.sealsecurity.io/new-documentation/new-docs/proof-of-value.md): Validating Seal on a representative component from your environment, with sales engineering support.
- [How Seal discovers your packages](https://docs.sealsecurity.io/new-documentation/new-docs/how-seal-discovers-your-packages.md): The four package discovery modes Seal supports, and the trade-offs each one makes.
- [Package discovery mode](https://docs.sealsecurity.io/new-documentation/new-docs/package-discovery-mode.md): Reference for the four package discovery modes a Seal Project can use.
- [Source code](https://docs.sealsecurity.io/new-documentation/new-docs/package-discovery-mode/source-code.md): Reads your dependency manifests directly through a connected SCM integration.
- [CLI](https://docs.sealsecurity.io/new-documentation/new-docs/package-discovery-mode/cli.md): Runs the Seal CLI in your CI/CD pipeline and reports the manifest it scanned.
- [Artifact server](https://docs.sealsecurity.io/new-documentation/new-docs/package-discovery-mode/artifact-server.md): Learns about your packages by recording what your build pulls from the Seal Artifact Server.
- [Imported manifest](https://docs.sealsecurity.io/new-documentation/new-docs/package-discovery-mode/imported-manifest.md): Parses a single uploaded file as the Seal Project's package picture.
- [Connecting source control](https://docs.sealsecurity.io/new-documentation/new-docs/connecting-source-control.md): How to connect Seal to GitHub, GitLab, or Azure DevOps so it can read your dependency manifests directly.
- [Connecting GitHub](https://docs.sealsecurity.io/new-documentation/new-docs/connecting-source-control/github.md): Install the Seal GitHub App and import GitHub repositories as Seal Projects.
- [Connecting GitLab](https://docs.sealsecurity.io/new-documentation/new-docs/connecting-source-control/gitlab.md): Connect Seal to a GitLab instance using a personal access token.
- [Connecting Azure DevOps](https://docs.sealsecurity.io/new-documentation/new-docs/connecting-source-control/azure-devops.md): Connect Seal to an Azure DevOps organization using a personal access token.
- [Managing source control connections](https://docs.sealsecurity.io/new-documentation/new-docs/connecting-source-control/managing-connections.md): View existing source-control installations, disconnect, or replace credentials.
- [Connecting via the Seal CLI in CI](https://docs.sealsecurity.io/new-documentation/new-docs/cli-in-ci.md): Run the Seal CLI in your CI/CD pipeline so it discovers your packages without source-control access.
- [Configuring the Seal Artifact Server for discovery](https://docs.sealsecurity.io/new-documentation/new-docs/artifact-server-discovery.md): Configure your package manager to pull through the Seal Artifact Server so Seal sees what your build uses.
- [Importing manifests & SBOMs](https://docs.sealsecurity.io/new-documentation/new-docs/importing-manifests.md): One-shot uploads of dependency manifests, SBOMs, and Snyk CSV exports.
- [Uploading a dependency manifest](https://docs.sealsecurity.io/new-documentation/new-docs/importing-manifests/dependency-manifest.md): Upload a dependency manifest like package-lock.json or pom.xml as a one-shot snapshot.
- [Uploading an SBOM](https://docs.sealsecurity.io/new-documentation/new-docs/importing-manifests/sbom.md): Upload a CycloneDX or SPDX SBOM as a one-shot snapshot of an environment.
- [Importing from a Snyk export](https://docs.sealsecurity.io/new-documentation/new-docs/importing-manifests/snyk-export.md): Upload a CSV exported from Snyk to bring its findings into Seal as a one-shot snapshot.
- [The Dashboard](https://docs.sealsecurity.io/new-documentation/new-docs/dashboard.md): A tenant-wide executive view of vulnerability and remediation metrics, refreshed daily.
- [The Protection page](https://docs.sealsecurity.io/new-documentation/new-docs/protection-page.md): The Seal UI surface where you triage vulnerable packages, review what is sealed, manage Sealing Rules, and configure Scanner Exclusions.
- [The Vulnerable packages tab](https://docs.sealsecurity.io/new-documentation/new-docs/protection-page/vulnerable-packages-tab.md): Reference for the columns, filters, and per-row actions on the Vulnerable packages tab.
- [The Sealed packages tab](https://docs.sealsecurity.io/new-documentation/new-docs/protection-page/sealed-packages-tab.md): Reference for the columns, filters, and per-row actions on the Sealed packages tab.
- [The Sealing rules tab](https://docs.sealsecurity.io/new-documentation/new-docs/protection-page/sealing-rules-tab.md): Reference for the list view of remote Sealing Rules.
- [The Scanner exclusions tab](https://docs.sealsecurity.io/new-documentation/new-docs/protection-page/scanner-exclusions-tab.md): Reference for the list view of Scanner Exclusions, the false-positive workaround.
- [Package states](https://docs.sealsecurity.io/new-documentation/new-docs/package-states.md): The six package states a vulnerable package can be in, how they transition, and what to do for each.
- [Triggering Generate fix](https://docs.sealsecurity.io/new-documentation/new-docs/generate-fix.md): Request a sealed version on demand for a vulnerable package in the Generate available state.
- [Vulnerability detail](https://docs.sealsecurity.io/new-documentation/new-docs/vulnerability-detail.md): What the Protection page drawer shows for a discovered package.
- [The Repository page](https://docs.sealsecurity.io/new-documentation/new-docs/repository-page.md): Where to find sealed packages for manual download, get shareable code diffs, and run an assessment of an arbitrary dependency set.
- [Browsing sealed packages](https://docs.sealsecurity.io/new-documentation/new-docs/repository-page/sealed-packages.md): Browse the public catalog of sealed packages, with search, per-package detail, and a shareable code diff.
- [Free assessment](https://docs.sealsecurity.io/new-documentation/new-docs/repository-page/free-assessment.md): Upload a manifest or SBOM at the public URL and see which of its packages have sealed versions.
- [Partial fixes & open vulnerabilities](https://docs.sealsecurity.io/new-documentation/new-docs/partial-fixes.md): Why a sealed package may still carry open vulnerabilities, and what to do about each kind.
- [Private versions](https://docs.sealsecurity.io/new-documentation/new-docs/private-versions.md): Sealed versions whose fix introduces a breaking change, enabled per Seal Project after the customer acknowledges the impact.
- [Choosing your deployment method](https://docs.sealsecurity.io/new-documentation/new-docs/choosing-deployment-method.md): A decision page for the five Seal deployment methods, ordered by what they give you.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sealsecurity.io/new-documentation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.