> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/keeperpam/privileged-access-manager/secrets-scanner.md).

# Secrets Scanner

Find exposed credentials, review security findings and move secrets into Keeper Vault.

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2FQHuvSMOrkVSgUH6WQIXq%2FKeeper%20-%20Secrets%20Scanner.jpg?alt=media&amp;token=25835a01-334e-4ced-919c-b6657085206d" alt=""><figcaption></figcaption></figure>

Keeper Secrets Scanner finds credentials that have been left in source code, repository history, configuration files and local environments. Findings include passwords, API keys, service tokens, database connection strings and private-key files. You can review each finding, check whether supported credentials still work, and move credentials into Keeper Vault without leaving the app.

The desktop app brings scanning, review and remediation into one workspace. It also checks selected local access settings, such as passwordless administrator access and risky SSH configuration. For terminal workflows and build pipelines, the command-line scanner provides findings in console, JSON, CSV and SARIF formats.

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2FoQ5pxe5P09HZHrE1wBIo%2Fworkspace-full.jpg?alt=media" alt="Keeper Secrets Scanner workspace with projects on the left, findings in the center and a selected finding on the right."><figcaption><p>The main workspace: select a project or target, review its findings and choose an action.</p></figcaption></figure>

{% hint style="success" %}
You can scan without signing in to Keeper. Connect your Keeper account when you are ready to save a discovered credential to your vault. GitHub, Jira and cloud AI features require their respective connections.
{% endhint %}

### When to use Keeper Secrets Scanner

Use the scanner to review a repository before sharing it, check a developer workstation for credentials left in configuration files, or revisit older commits after an exposure. Security teams can group related repositories and folders into projects, prioritize findings and create Jira tickets for follow-up. Developers can add scanning to a build pipeline or pre-commit workflow and bring findings into the desktop app for review.

Many discovered credentials belong to applications, scripts and services rather than people. Finding these credentials helps you identify secrets that should be stored and managed in Keeper instead of embedded in code or configuration.

The screenshots below use sample projects and findings. Account details and sign-in tokens have been redacted.

### Before you begin

* Install the Keeper Secrets Scanner desktop app for your operating system. The desktop app supports macOS, Windows and Linux.
* Scan only files, repositories and environments that you are authorized to inspect. Your operating system account needs permission to read the selected files.
* To scan GitHub repositories, install the GitHub CLI and sign in through **Settings > Integrations**. The repository picker uses the access available to that GitHub account.
* To save credentials to Keeper, use a Keeper account with permission to create records in the destination folder.
* To use AI assistance, select **Local (on-device)** or configure an approved provider in **Settings > AI**.

### Unlock the app

On first launch, select **Get started** to set up the app. On later launches, unlock the app to access your saved findings and integration credentials.

On supported Macs, the lock screen offers **Unlock with Touch ID**. Follow the operating system prompt, including the device passcode option where available. On other systems, use the unlock option presented by the app.

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2FcegkdwoLToocOISrl9Lc%2Funlock-full.jpg?alt=media" alt="Keeper Secrets Scanner lock screen with an Unlock with Touch ID button."><figcaption><p>The lock screen protects access to scan findings and integration credentials.</p></figcaption></figure>

Locking the app and signing out of Keeper are separate actions. Lock the app when stepping away from your computer. Use **Log out** when you want to disconnect your Keeper account.

### Connect your Keeper account

You can select **Skip for now** during sign-in and continue scanning. To connect later, use the Keeper connection control in the lower-left corner of the workspace or open **Settings > Keeper Vault**.

Enter your Keeper email address, choose the region where your account is hosted and select **Continue**. Complete the prompts for your account. These may include your master password, two-factor authentication, a security key or device approval.

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2FKhiK2Q9xd6ueIvotPM7E%2Fkeeper-sign-in-full.jpg?alt=media" alt="Connect your Keeper Vault screen with email, region, Continue and Skip for now controls."><figcaption><p>Sign in to Keeper when you are ready to save discovered credentials.</p></figcaption></figure>

#### Single sign-on

If your organization uses SSO, complete sign-in in the browser. When prompted, copy the token from the confirmation page into **Token from browser** and select **Complete sign-in**. Use **Reopen SSO sign-in page** if you need to return to the browser flow. Complete any additional approval required by your organization.

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2FhpUHInQjeVZsMNOjTZfz%2Fkeeper-sso-full.jpg?alt=media" alt="Keeper SSO sign-in screen with the browser token redacted and a Complete sign-in button."><figcaption><p>Complete the SSO browser flow, then return to the app.</p></figcaption></figure>

### Create a project

A project groups scan targets that you want to review together. For example, a project can contain the repositories for an application, a set of local folders, or the access checks for a workstation.

Select **New project**, enter a name and choose the first target to add. You can also select **Create the project without a target for now** and add targets later.

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2Fg0RzAmXB26wL0DmlfqvW%2Fnew-project-full.jpg?alt=media" alt="New project dialog showing a project name field and the available first scan targets."><figcaption><p>Name the project and choose where to start scanning.</p></figcaption></figure>

#### Add scan targets

Use the **+** beside a project or select **Add scan target** in an empty project. A project can contain multiple targets and different target types.

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2FkxcGKlkNuPzAiKqXXV42%2Fadd-target-full.jpg?alt=media" alt="Add a scan target dialog listing folders, GitHub repositories, environment variables, common locations and local access checks."><figcaption><p>Add more targets without creating another project.</p></figcaption></figure>

| Target                    | What it reviews                                                                                                     | Typical use                                                                                         |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
| **Folder**                | Readable text files in a local directory. Selecting the root of a Git repository also includes its history.         | Review application code, scripts and configuration files.                                           |
| **GitHub repositories**   | Repositories accessible to your connected GitHub account.                                                           | Review one or several repositories without preparing local clones yourself.                         |
| **Environment variables** | Environment variables available to the running scanner process.                                                     | Check for credentials passed into local applications or shell sessions.                             |
| **Common locations**      | Common credential locations under your home directory, such as AWS configuration, SSH files and cloud CLI settings. | Review credentials stored outside an application repository.                                        |
| **sudoers**               | Selected sudoers configuration and drop-in files.                                                                   | Identify passwordless root access and command grants that can provide broader access than intended. |
| **PAM access.conf**       | Local login access rules.                                                                                           | Identify catch-all rules that override more restrictive rules below them.                           |
| **Local privilege**       | Local users and group memberships.                                                                                  | Review administrator or root-equivalent access and additional accounts with root privileges.        |
| **sshd\_config**          | SSH server configuration.                                                                                           | Review direct root password login and missing user or group restrictions.                           |

Local access checks depend on the operating system, the configuration files present and your read permissions. A configuration finding requires a review of the setting; it is not necessarily a captured secret that can be moved into a vault.

#### Choose GitHub repositories

Select **GitHub repositories** to open the repository picker. Choose your account or an organization, search by repository name and select the repositories to add. You can select several repositories at once. The picker displays repository size and whether a repository is private or archived.

If GitHub is unavailable as a target, check **Settings > Integrations** for GitHub CLI installation and sign-in status. Private repositories require permission from the connected account, including any organization approval required by GitHub.

#### Choose the right local scope

Select the repository root when you want to include Git history. Selecting a subfolder scans that folder's current files rather than the entire enclosing repository's history.

The **Environment variables** target reviews the environment inherited by the scanner, not every running process on the computer. An app launched from the desktop may see a different environment from one launched in a terminal.

### Run a scan and monitor progress

Select **scan** beside an individual target to scan it, or select **Scan all** to scan all targets in the current project. The **Active Scans** panel shows the latest status for each target, including queued, cloning, scanning, verifying, done, failed and canceled states.

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2FoUdeES0DH145X3JNb9MK%2Factive-scans-full.jpg?alt=media" alt="Active Scans panel showing a completed local privilege scan and tabs for Active Scans and Activity."><figcaption><p>Monitor target progress and open a completed scan from the Active Scans panel.</p></figcaption></figure>

Use **cancel** to stop a queued or running scan. Select a completed entry to open its findings. **Clear finished** removes completed entries from this panel; it is not the same as deleting saved scan data.

Open the **Activity** tab to review recorded remediation actions, such as moving a credential to Keeper, removing it from source or undoing a removal.

### Review findings in the workspace

The workspace has three main areas:

* The project tree on the left organizes projects, target types and individual targets. Use **Find a target** to locate an item.
* The findings list in the center shows results for the selected project or target. Selecting a project shows findings across its scanned targets; selecting a target narrows the view.
* The detail panel on the right shows the selected finding's location, supporting information and available actions.

Use **Severity** and **Status** to narrow the list. Search can match a finding's title, file, secret type, value or tags. Where access information is available, the **Privilege** filter helps you focus on administrative, write or read access.

Severity labels help prioritize review. A **Critical** or **High** finding deserves prompt attention, but you should still check the context before making a change. A detected value may be a working credential, test data or an example. A configuration finding may depend on how the system is actually used.

#### Open a finding

Select a finding to review its description and location. Where available, use the location link to open the file or commit in GitHub, copy the path, or reveal a local file in Finder or Explorer.

Expand **Source** to review the surrounding code. Expand **Details** to review the detected value and additional finding information. Secret values are masked by default in Details; use the visibility control only when you need to inspect the value. Hide it again before sharing your screen.

Git history findings also show commit information, such as the author, date and commit message. A credential can remain exposed in an older commit even when it has been removed from the current file.

#### Track review status

Use the **Labels** status control to record the finding's review state:

| Status             | How to use it                                                       |
| ------------------ | ------------------------------------------------------------------- |
| **New**            | The finding has not yet been reviewed.                              |
| **Triaged**        | You have reviewed the finding and established its context.          |
| **To Fix**         | The finding needs follow-up action.                                 |
| **Fixed**          | You have completed and verified the required work.                  |
| **Won't Fix**      | You have reviewed the issue and decided not to change it.           |
| **False Positive** | The detected value or context does not represent the reported risk. |

These labels are review decisions. Marking a finding **Fixed** does not change a file or revoke a credential. Likewise, **In Keeper** confirms that a credential is stored in your vault, not that every copy has been removed or that the provider has revoked the exposed value.

### Check credential liveness

For supported credential types, the **Liveness** section reports whether the credential authenticated successfully. Supported checks include AWS access keys, Google Cloud service account credentials, Azure client secrets and Stripe keys. Not every detected secret type supports a liveness check, and some checks require nearby information such as a matching key or account details.

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2F19SbM3YG2UOZzAl2g2Rr%2Fliveness-full.jpg?alt=media" alt="Finding detail with an example Liveness result and a Re-check liveness control."><figcaption><p>An illustrative liveness result for an AWS finding.</p></figcaption></figure>

| Result                       | Meaning                                                                                                                       |
| ---------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| **Live - key authenticates** | The credential authenticated during the check. Prioritize reviewing and replacing the exposed value.                          |
| **Dead - key rejected**      | The provider rejected the credential during the check. Review and remove the exposure even if the credential no longer works. |
| **Inconclusive**             | The scanner could not establish validity, for example because required context or connectivity was unavailable.               |
| **Not checked**              | A liveness result is not available for this finding yet.                                                                      |

Use **Re-check liveness** to refresh a supported result. For AWS findings, **View in IAM Console** opens the AWS IAM console for further review.

{% hint style="info" %}
Credential verification contacts the relevant provider and requires network access. An inconclusive result does not mean that a credential is safe. A successful check confirms validity at that time; it does not prove that the credential has never been misused.
{% endhint %}

#### Group identity-related findings

When the results contain identity-related findings, the shield control opens **IAM Posture**. This alternate view groups the existing findings by available access level, then by the associated identity or source location. Select a group to expand it and select a finding to use the same detail panel.

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2FaMWSdMLnnMBCzIFItzhO%2Fiam-posture-full.jpg?alt=media" alt="IAM Posture view grouping existing AWS credential findings by an Unknown access level and source file."><figcaption><p>Group identity-related scan results without starting a separate scan.</p></figcaption></figure>

**Unknown** means the findings do not establish an access level. This view organizes information from the completed scan; it should not be treated as a complete inventory of your cloud accounts or their permissions. Select **Back to findings** to return to the standard list.

### Take action on a finding

Select **Take Action** in the finding detail panel. Choose one or more available actions, then select **Execute**.

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2FlIkvMtod8u317XEQ9GmH%2Ftake-action-full.jpg?alt=media" alt="Take Action dialog with Move to Keeper, Also remove from source and Generate Remediation options."><figcaption><p>Choose the actions to perform before selecting Execute.</p></figcaption></figure>

#### Move a credential to Keeper Vault

Choose **Move to Keeper** to save the discovered credential as a Keeper record. Sign in if the app prompts you to connect your vault.

After the action succeeds, the finding displays **In Keeper**. Use **Open in Vault** to open the associated record and verify its contents.

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2FqC1gWyZNN59Kn5HEbVNq%2Faction-complete-full.jpg?alt=media" alt="Completed Take Action dialog showing Move to Keeper and Generate Remediation completed, with an Open in Vault link."><figcaption><p>Review the result of each selected action and open the saved Keeper record.</p></figcaption></figure>

You can choose a destination for new records in **Settings > Keeper Vault > Secret records folder**. Select a folder and select **Save**. This destination is for discovered credentials, not for the files being scanned.

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2FegfT9K7wcLKWHH6jMSyo%2Fvault-destination-full.jpg?alt=media" alt="Secret records folder setting with a folder selector and Save button."><figcaption><p>Choose where credentials moved to Keeper will be stored.</p></figcaption></figure>

#### Remove a credential from a local file

Select **Also remove from source** if you want the app to replace the captured secret in a writable local file. The credential must first be saved to Keeper. The replacement contains a `KEEPER_REMOVED` marker rather than the original value.

For supported removals, an encrypted recovery copy lets you restore the file using **Undo**. Review restored files carefully because undo brings back the original credential.

Automatic removal is not available for every finding. History-only findings, remotely scanned repository files, private key findings and configuration issues may require manual work. If the app reports that a value could not be removed, follow the explanation instead of treating the action as complete.

{% hint style="warning" %}
Saving a credential to Keeper does not revoke it, remove it from Git history or update an application to retrieve it from Keeper. Replacing a hardcoded value can also interrupt an application until you update its configuration. Review the change, replace or revoke exposed credentials with their provider, and test the affected application before marking the issue fixed.
{% endhint %}

#### Generate remediation guidance

Choose **Generate Remediation** to create guidance for the selected finding. The result appears in the detail panel and can include an explanation of the risk, suggested immediate actions and follow-up checks.

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2F3HZyE1qefSYJVShmNDyZ%2Fremediation-guidance-full.jpg?alt=media" alt="AI-generated remediation guidance for an npm access token, with Risk, Do Now and Do Soon sections."><figcaption><p>Use the generated guidance to plan and verify a fix.</p></figcaption></figure>

Generating guidance does not execute the suggested commands or change the affected system. Check the recommendations against your environment and your organization's procedures before acting.

### Work through several findings

Select **Remediate All** to open the bulk-action dialog. It shows how many findings are in scope and provides controls to plan fixes, move credentials to Keeper and remove eligible values from local source files.

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2FQPbLysj54iTp4M7XFach%2Fbulk-remediation-full.jpg?alt=media" alt="Remediate all findings dialog with individual bulk actions and Run all steps."><figcaption><p>Run a specific action in bulk or choose Run all steps after reviewing the scope.</p></figcaption></figure>

You can run an individual step or select **Run all steps**. Source removal only proceeds for eligible findings whose credentials have been saved to Keeper. Configuration findings and values that cannot be removed automatically still need manual review.

Use **Stop** while a bulk operation is running to stop further processing. Stopping does not undo actions that have already completed. Review the updated findings and the **Activity** panel afterward.

### Ask KeeperAI about a finding

Select the KeeperAI control in the workspace to open the chat panel. With a finding selected, you can ask for an explanation, a remediation plan or help assessing the risk. Suggested prompts include **Explain this finding**, **How do I fix this?** and **What's the risk?**

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2FQOh69j6dkof5trggPeNU%2Fkeeperai-full.jpg?alt=media" alt="KeeperAI welcome panel with the active npm access token finding and suggested prompts."><figcaption><p>Start a conversation with the selected finding as context.</p></figcaption></figure>

Type a question and select **Send**. Use **Enter** to send or **Shift+Enter** for a new line. Select **New** to start a fresh conversation. The panel also provides controls to stop a response and save the conversation as an HTML file.

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2F1Dp0OA0iG2ahomrC1Fyj%2Fkeeperai-response-full.jpg?alt=media" alt="KeeperAI response explaining a selected finding and recommending remediation."><figcaption><p>Review the explanation and ask follow-up questions without leaving the findings view.</p></figcaption></figure>

AI responses are guidance, not proof that a finding is genuine or that a fix is complete. The chat panel does not execute a fix because you ask about it. Review the advice and use the product's action controls when you want to make a change.

#### Review potential false positives

The **Weed out the false positives** prompt starts an AI review of eligible findings. Confirm the scope with **Run across all findings**. The review can label findings as **False Positive** when their context suggests test data, placeholders or documentation examples.

The result summarizes how many findings were analyzed and how many were marked. Use the **Status** filter to revisit marked findings and correct any classification you disagree with. This review changes finding labels; it does not remove files or revoke credentials.

### Choose an AI provider

Open **Settings > AI** to select the provider used for AI-assisted features.

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2FikaTnaLq8rEsBhxmXqOC%2Fsettings-ai-full.jpg?alt=media" alt="AI settings with provider and model selection, stored credentials, saved providers and Save &#x26; Activate."><figcaption><p>Configure and activate the AI provider approved for your environment.</p></figcaption></figure>

* **Local (on-device)** runs a supported model on your computer. The app downloads the selected model on first use; once it is available, local AI processing does not send requests to a cloud model. You can also select **Add custom model** to use a supported local model file.
* Cloud options include OpenAI, Anthropic, Google Gemini, Azure OpenAI, AWS Bedrock and Vertex AI. The app also supports Keeper AI Gateway and compatible endpoints. Enter the credentials and connection details requested for your provider.

For a cloud provider, choose the model or deployment, complete the required fields and select **Save & Activate**. You can keep several provider configurations and switch between saved providers. **Deactivate AI** turns off AI assistance without preventing scans.

The model selector beside **Take Action** provides a quick way to switch between available local models and saved cloud providers.

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2Fkfjnc3qmd9Q2d09E2qu4%2Fmodel-switcher-full.jpg?alt=media" alt="Model selector beside Take Action with a local model and a saved cloud provider."><figcaption><p>Switch the active model from the finding detail panel.</p></figcaption></figure>

{% hint style="info" %}
AI provider credentials are stored in the operating system's credential store. With a cloud provider, prompts and finding context are sent to the configured service. The app redacts captured secret values from the finding context it supplies, but your own messages and other context may still contain sensitive information. Follow your organization's AI policy and do not paste credentials into chat.
{% endhint %}

### Connect GitHub and Jira

Open **Settings > Integrations** to review the connection status for GitHub and Jira.

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2FwrvtdoV11PFwLCxND956%2Fsettings-integrations-full.jpg?alt=media" alt="Integrations settings showing Jira and GitHub connection status with account details redacted."><figcaption><p>Manage the connections used for repository access and issue tracking.</p></figcaption></figure>

#### GitHub

When the GitHub CLI is installed but not signed in, select **Sign in**. Copy the one-time code, open the browser link and complete GitHub's authorization flow. Return to the app to confirm that your account is connected, then add repositories to a project.

#### Jira tickets

Select **Connect** for Jira and complete the browser authorization. Use **Reconnect** if the connection needs to be refreshed, or **Disconnect** to remove it from the app.

To create a ticket, open a finding and select **Create Jira ticket**. Choose the Jira project, issue type and priority, then review the summary and description before selecting **Create ticket**. The generated description includes finding context with the secret redacted. After creation, the finding provides a link to the ticket.

If the selected issue type requires fields the app cannot supply, choose a different issue type or create the issue directly in Jira. Creating a ticket records follow-up work; it does not remediate the finding or keep the finding's status automatically synchronized with Jira.

### Create a scan report

Select a scanned project or target and open **Report** using the chart control in the workspace toolbar. A project report summarizes the project's findings; selecting a target produces a report for that target's scan results.

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2FewjucC0BfHgkQQ4q5ypI%2Fscan-report-full.jpg?alt=media" alt="Keeper Secrets Scanner Report viewer with slide navigation, White and Dark themes and Download PDF."><figcaption><p>Review a scan report and export it for a security review or team update.</p></figcaption></figure>

The nine-slide report covers:

* An overview of the scan and unique findings.
* Findings by severity and type.
* The sources and locations where findings appear.
* Scan coverage, including files, repositories and completed scans where available.
* Findings over time when scan history is available.
* Locations to prioritize and a summary of the results.

Use the arrows or numbered slide controls to navigate. Choose **White** or **Dark** for the report's appearance. Select **Download PDF** to save the report, or **Back to scans** to return to the findings workspace.

A report needs completed scan data. The trend view needs more than one scan to show a comparison. Review the report's scope and any sensitive file or project names before sharing it.

### Customize settings

Open **Settings** from the top-left of the workspace. Use the settings search to find a section or option.

#### General

Choose **Light** or **Dark**, select a color preset and adjust **Zoom**. These preferences change the interface without changing scan results.

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2FunaiC0ozLoF1oWNSmZBK%2Fsettings-general-full.jpg?alt=media" alt="General settings showing theme, color presets, zoom and remediation preferences."><figcaption><p>Adjust the workspace appearance and finding-review preferences.</p></figcaption></figure>

**Remove from source by default** preselects **Also remove from source** when you open **Take Action**. It does not remove anything until you execute the action. **Expand Source and Details by default** opens those sections automatically when you select a finding.

#### Security

Set **Auto-lock after inactivity** to control when the app locks. Use **Lock now** in this section or **Lock** in the workspace to lock immediately. The section also shows the unlock method available on your device.

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2FcSPakDVjHdJo8ObXD3xs%2Fsettings-security-full.jpg?alt=media" alt="Security settings with unlock method, auto-lock timeout and Lock now."><figcaption><p>Set an inactivity timeout and lock the app when you leave your workstation.</p></figcaption></figure>

#### Projects

Open **Settings > Projects** to see project names, target counts and creation details. Select **Open** to switch projects. Rename a project from the sidebar tree.

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2FSSTRxMdvuHGxfk0vr7vn%2Fsettings-projects-full.jpg?alt=media" alt="Projects settings listing projects with their target counts and Open and Delete controls."><figcaption><p>Open and manage existing projects from Settings.</p></figcaption></figure>

**Delete** removes a project's definition and targets. Saved scan results remain on disk. This is different from **Reset all scans** in a project's actions menu, which deletes that project's scans and review labels. Read the confirmation before either action and export anything you need to keep.

#### About and detection coverage

Open **Settings > About** to view the installed version, open the documentation or send feedback. The **What we scan for** catalog lists supported secret types by category. Use its filter to search for a provider or type, such as AWS, a database credential or a private key.

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2FDxH4EIbDmBRX7YZsTWWR%2Fdetection-catalog-full.jpg?alt=media" alt="What we scan for catalog with a search filter and expandable secret categories."><figcaption><p>Browse detection coverage in the installed app.</p></figcaption></figure>

### Use the command-line scanner

The command-line scanner is useful for repeatable reviews, build pipelines and pre-commit checks. It can scan local paths, repository history, environment variables and common credential locations. It also provides local SSH, certificate and access-configuration checks.

The examples below use `ss`, the command name on macOS and Windows. On Linux package installations, use `keeper-ss` to avoid a name conflict with the system's socket-statistics utility.

Scan a local folder:

```bash
ss scan /path/to/project
```

Include repository history and produce a SARIF report for a pipeline. With **high** as the threshold, the command returns exit code 1 when High or Critical findings remain:

{% code overflow="wrap" %}

```bash
ss scan /path/to/repository --git-history --severity high --exit-code --output sarif > findings.sarif
```

{% endcode %}

Run without the normal console findings report and request a desktop notification:

```bash
ss scan /path/to/project --silent --notify
```

Silent mode still saves a local run summary; warnings and errors remain visible in the terminal. When a notification is available, open it to review the run in the desktop app. Select **Remediate in app** from the run summary to rescan accessible local paths in the app and work with the normal remediation controls.

JSON, CSV and SARIF outputs redact secret values. They still contain finding metadata, so review the files before sharing them. The pre-commit scanner can check staged changes and block a commit when it detects a secret. Use `ss scan --help` for the options supported by your installed version.

### Verify a fix

{% stepper %}
{% step %}

#### Review the exposure

Confirm the credential, its source and whether other files or historical commits contain it. Check liveness where supported, but do not rely on an inconclusive result to dismiss the finding.
{% endstep %}

{% step %}

#### Store and replace the credential

Save the credential to Keeper where appropriate. Replace or revoke an exposed credential with its provider and update the application to use the replacement securely. Remove the exposed value from writable files or follow the manual cleanup instructions for other sources.
{% endstep %}

{% step %}

#### Test and rescan

Test the affected application, rescan the relevant targets and review any remaining copies. Record follow-up work in Jira if needed. Mark the finding **Fixed** only after you have verified the required changes.
{% endstep %}
{% endstepper %}

### Common questions

#### Do I need a Keeper account to scan?

No. You can scan and review findings without signing in to Keeper. A Keeper account is required to move discovered credentials into Keeper Vault.

#### Does scanning change my files?

Scanning inspects the selected sources. File changes occur when you explicitly execute a supported removal action. Generating AI guidance, setting a review label and creating a Jira ticket do not remove a secret from its source.

#### Does moving a credential to Keeper finish the remediation?

No. It stores the credential in Keeper. You still need to review other copies, replace or revoke exposed values with their provider, update dependent applications and verify the result.

#### Can I work without a cloud AI provider?

Yes. Scanning does not require AI. For AI assistance, select **Local (on-device)** and download a supported model. GitHub access, Keeper sign-in and credential liveness checks still need their respective network connections.

#### Why is a local check empty or unavailable?

The check may not apply to your operating system, the expected file may not exist, or your account may not be able to read it. Review the target and scan status before assuming that an empty result means the whole system is secure.

#### Why can't the app remove a finding automatically?

The finding may refer to history, a remote repository, a private key or a configuration issue rather than a writable local secret. The file may also have changed since the scan. Review the message, rescan if needed and perform the remaining cleanup manually.

### Related documentation

* [Keeper Secrets Manager](https://docs.keeper.io/enterprise-guide/keeperpam-privileged-access-manager/secrets-manager) for retrieving application secrets without hardcoding them.
* [Keeper Vault user guide](https://docs.keeper.io/user-guides/readme) for managing records and sharing credentials.
* [Keeper support](https://www.keepersecurity.com/support.html) for product assistance.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.keeper.io/keeperpam/privileged-access-manager/secrets-scanner.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
