Infisical is the open-source platform for securing secrets, certificates, access, and AI Agents.
TypeScript acmeagentsai-agentscertificate-managementdevsecopsenvironment-variableskubernetesopen-sourcepampkipostgresprivate-caprivileged-access-managementsecret-managementsecret-managersecretssecrets-managementsecuritysecurity-toolsvault
remove references from doc
Matheus Nogueira4d53161d8a0e
diff --git a/docs/documentation/getting-started/choose-a-product/secret-scanning.mdx b/docs/documentation/getting-started/choose-a-product/secret-scanning.mdxindex ed0db53f24..135750bf1c 100644--- a/docs/documentation/getting-started/choose-a-product/secret-scanning.mdx+++ b/docs/documentation/getting-started/choose-a-product/secret-scanning.mdx@@ -7,7 +7,7 @@ description: "Identify credentials that have been stored in source code or develInfisical Secrets Scanning detects credentials that have been placed in locations where they shouldn't be stored, such as source code repositories, configuration files, and helper scripts. Scanning can be performed against connected cloud-hosted repositories or against local files on a developer's machine.<Card title="Secrets Scanning docs" icon="radar" href="/documentation/platform/secret-scanning/overview">- Data sources, scan modes, findings and lifecycle, custom rules, and CLI usage.+ Data sources, scan modes, findings and lifecycle, ignore rules, and CLI usage.</Card>## Use cases@@ -41,4 +41,4 @@ Infisical Secrets Scanning runs in two environments.- **Connected repositories.** [GitHub](/documentation/platform/secret-scanning/github), [GitLab](/documentation/platform/secret-scanning/gitlab), and [Bitbucket](/documentation/platform/secret-scanning/bitbucket) repositories can be monitored continuously. Each new commit is scanned. When a credential is detected, Infisical records a finding that includes the file path, line number, commit hash, and the detection rule that matched.- **Local environments.** The [`infisical scan`](/cli/commands/scan) CLI command scans a working directory, Git history, or staged changes in a CI pipeline before the changes are pushed to a shared branch.-The detection engine uses pattern matching, entropy analysis, and user-defined rules to identify credentials. Findings can be resolved, ignored, or marked as false positives, and each scan is recorded in an audit log. To reduce the number of false positives, users can define custom detection patterns, ignore rules through `infisical-scan:ignore` and `.infisicalignore`, adjust the entropy threshold, and exclude specific file paths from scanning.+The detection engine uses pattern matching and entropy analysis to identify credentials. Findings can be resolved, ignored, or marked as false positives, and each scan is recorded in an audit log. To reduce the number of false positives, users can skip known secrets with `infisical-scan:ignore` comments or a `.infisicalignore` file.diff --git a/docs/documentation/platform/secret-scanning/concepts/secret-scanning.mdx b/docs/documentation/platform/secret-scanning/concepts/secret-scanning.mdxindex 54630ca984..8638fdd9b9 100644--- a/docs/documentation/platform/secret-scanning/concepts/secret-scanning.mdx+++ b/docs/documentation/platform/secret-scanning/concepts/secret-scanning.mdx@@ -15,6 +15,6 @@ A secret scanning solution helps teams proactively identify and respond to theseInfisical Secret Scanning continuously monitors your source code and connected systems for exposed credentials. It integrates with platforms like [GitHub](/documentation/platform/secret-scanning/github), [GitLab](/documentation/platform/secret-scanning/gitlab), and [Bitbucket](/documentation/platform/secret-scanning/bitbucket) to scan codebases in real-time, detecting leaks as they happen and notifying administrators when action is needed.-Findings are surfaced with detailed context — including file location, commit metadata, and rule match — and can be tracked through their lifecycle using status labels like `Resolved`, `False Positive`, or `Ignored`. Teams can configure rules, exclusions, and thresholds to reduce noise and tailor detection to their environment.+Findings are surfaced with detailed context — including file location, commit metadata, and rule match — and can be tracked through their lifecycle using status labels like `Resolved`, `False Positive`, or `Ignored`. To reduce noise, teams can [ignore known secrets](/documentation/platform/secret-scanning/usage#ignoring-known-secrets) in their code.In addition to real-time monitoring, Infisical supports both full repository scans and lightweight diff scans, as well as local pre-commit scanning via the [Infisical CLI](/cli/commands/scan). This allows teams to prevent secret leaks before they ever reach production.diff --git a/docs/documentation/platform/secret-scanning/overview.mdx b/docs/documentation/platform/secret-scanning/overview.mdxindex 1cb2898dd7..778df616f8 100644--- a/docs/documentation/platform/secret-scanning/overview.mdx+++ b/docs/documentation/platform/secret-scanning/overview.mdx@@ -12,7 +12,7 @@ Secret Scanning works across both cloud-connected repositories and local developCore capabilities include:- Integrated Scanning Across Environments: Monitor secrets in real time across connected repositories like GitHub, GitLab, and Bitbucket, or scan locally using the infisical scan CLI.-- Detection Engine: Identify potential secrets using pattern matching, entropy analysis, and custom rules tailored to your codebase and workflows.+- Detection Engine: Identify potential secrets using pattern matching and entropy analysis.- Flexible Scan Modes: Run full scans manually or configure automatic diff scans triggered by new commits. CLI scans support Git history, file directories, or staged changes in CI pipelines.- Findings and Lifecycle Management: Track detected secrets with context like file path, commit hash, and scanning rule. Findings can be resolved, ignored, or marked as false positives — with full visibility into scan results over time.-- Custom Configuration and Noise Reduction: Fine-tune scanning behavior with custom patterns, ignore rules (infisical-scan:ignore, .infisicalignore), entropy thresholds, and excluded paths to reduce false positives.+- Noise Reduction: [Skip known secrets](/documentation/platform/secret-scanning/usage#ignoring-known-secrets) with `infisical-scan:ignore` comments or a `.infisicalignore` file to reduce false positives.diff --git a/docs/documentation/platform/secret-scanning/usage.mdx b/docs/documentation/platform/secret-scanning/usage.mdxindex c1d4dab7d6..637098f73c 100644--- a/docs/documentation/platform/secret-scanning/usage.mdx+++ b/docs/documentation/platform/secret-scanning/usage.mdx@@ -25,7 +25,6 @@ Secret Scanning consists of several components that enable you to quickly respon- **Alert System**: Notifies organization admins via email when secrets are detected- **Risk Management**: Allows tracking and managing detected secrets with different status options- **Data Sources**: Integrates with various data sources and version control systems-- **Ignore Rules**: Supports ignore patterns to reduce false positivesThese components work together to provide comprehensive secret detection and incident response capabilities.