Aller au contenu principal

6 articles tagués avec « endpoint-protection »

Voir tous les tags

Endpoint Protection gives you better control over your machines and their secrets

calendar icon   Release Date: November 18, 2026

A machine leaves the endpoint fleet while another shows pre-commit protection installed

Endpoint Protection now shows which developer machines stop secrets before they are committed. Machine Scan checks each git repository on a machine for the ggshield pre-commit hook. The Endpoints dashboard shows the result next to AI hooks and honeytokens, in one Protection view. Admins can also remove machines that left the company. Pre-commit protection ships in the Machine Scan plugin 0.67 for ggshield.

What does this mean for you?

  • Know which machines check commits: a new Pre-commit protection card shows the share of endpoints with the hook installed. One click filters the table to the endpoints without it.
  • All protections in one column: a Protection column replaces the Honeytoken protection and AI agents columns. For each machine, it marks pre-commit, AI hooks and honeytoken as installed, missing, not applicable or compromised. Click it to see what is missing and how to fix it.
  • One summary per machine: the endpoint detail page opens on a summary of the machine, its owner, OS and scanner version. It has one cell each for local scan, pre-commit, AI hooks and honeytoken.
  • Remove retired machines: workspace admins can remove one or several endpoints from the Endpoints table. Removed endpoints leave the table, the coverage KPIs and the secrets list. A removed machine that sends a new scan comes back automatically.
  • Read your fleet from the API: GET /v1/endpoints/machines lists your machines and their users, so offboarding and incident response can start from a person or a machine. It needs the new endpoints:read scope, available to managers and above.

Why is this important?

The pre-commit hook stops a secret before it reaches a repository, a CI log or a fork. Until now, you could not see which machines ran it. Removing retired machines keeps your coverage numbers accurate.

Get Started Today!

Endpoint Protection is available for workspaces with a Growth or Enterprise plan. Talk to your Customer Success Manager to enable it, or contact us to upgrade your plan.

Update the plugin on each machine with ggshield plugin install machine_scan, or let your MDM job do it on its next run. Pre-commit protection shows after the next scan with plugin 0.67 or later. See Deploy ggshield at scale.

To install the pre-commit hook on the machines without it, add ggshield machine setup to your MDM job. This command also configures AI hooks and plants a honeytoken. See Setup and doctor options.

Enhancements​

  • Machine Scan:
    • See pre-commit protection for each repository on the Repositories page of the local dashboard (ggshield machine dashboard).
    • Add folders to every scan with the new scan.extra_roots setting in machine_scan.yaml.
    • Point REQUESTS_CA_BUNDLE to a folder of CA certificates, which Machine Scan trusts in addition to the operating system certificates.
    • Redact secrets in IPython history databases, and redact directly from the History & logs view of the local dashboard.
    • On Linux, Machine Scan now skips sshfs 3.x and rclone mounts as remote drives.

Fixes​

  • Machine Scan:
    • Fixed an issue where Machine Scan skipped a private repository because one of its remotes was public.
    • Fixed an issue where the local report database grew to several gigabytes on some machines.
    • Fixed an issue where a scan ran out of memory on some dense files.
    • Fixed an issue where ggshield machine scan and ggshield machine report rejected --include-root.
    • Fixed an issue where ggshield machine report --instance read its settings from the default instance.
    • Fixed an issue where redacting one secret in the local dashboard also hid the secrets next to it.
    • Fixed an issue where Machine Scan did not check Kubernetes service account tokens against their cluster.

Catch secret theft on your developers' machines with a Kubeconfig honeytoken

calendar icon   Release Date: November 12, 2026

A decoy kubeconfig planted by ggshield triggers a GitGuardian honeytoken when an attacker runs kubectl with it

Stealing secrets from developer machines is now an industry. TeamPCP opened the year with Trivy and LiteLLM, then reused what it stole to reach Mistral, Grafana and GitHub. It open-sourced its Mini Shai-Hulud worm in May, and copies followed: four campaigns in two weeks across npm, PyPI, Crates.io, Composer and GitHub, four more in June, and in August a single wave that hit 800 npm packages and 469 secret locations on each infected machine. The payload changes every month, but the shopping list does not: every credential on the machine, including the ~/.kube/config that opens your Kubernetes clusters.

Honeytoken catches the theft. It already plants a decoy AWS key on your endpoints. It now plants a Kubeconfig decoy as well, written into ~/.kube/config next to your real clusters and pointing to a cluster GitGuardian controls. A stealer takes it with the rest. The first call made with it raises an alert and names the machine it was taken from. Ships in ggshield 1.56 or later.

What does this mean for you?

  • Indistinguishable from a real cluster: the file is exactly what kubectl writes, and secret scanners, including our own Kubeconfig detector, flag the token as live. Yet it opens no cluster and holds no permission.
  • An alert on the first call: any request made with the token creates an event with the IP address, country, user agent and path, and fires your alerts by email, Slack, Microsoft Teams, ServiceNow or webhook.
  • A named machine, not a hash: the Sources card tells you which laptop or runner the file was taken from, and who owns it.
  • Safe for the owner: on a machine that already has a kubeconfig, the decoy never becomes the current context, so a developer's own kubectl cannot trip it.
  • Nothing new to install: ggshield writes the file and leaves. Revoke the honeytoken and the next run removes it. Plant it alongside the AWS key decoy: each trigger tells you which file was read.

Why is this important?

A secret theft is silent. The malware reads a few files and sends them out. Nothing breaks, no service goes down, and the stolen keys keep working for their legitimate owners. Most victims learn about the breach when the attacker starts using the keys, often weeks later, and by then the keys have been tested and sorted. After the TeamPCP compromise of LiteLLM, Wiz saw stolen secrets validated within hours. The loot from that 40-minute window was only measured five months later: 153 GB and 2,488 organizations, many of which nobody can even notify.

A honeytoken is the strongest signal you can get of such a theft. The decoy has no legitimate use, so any call made with it means that someone took your secrets. It fires at the first step of the attack, when the attacker checks which stolen keys are valid, and before any real key is used against you. It does not depend on catching the malware itself, so it works against packages your EDR and your dependency scanner have never seen. And because GitGuardian knows where each decoy was planted, the alert comes with the name of the compromised machine, which is where your investigation starts.

Start trapping bad actors today!

Available on SaaS for workspaces with Endpoint Protection on a Growth or Enterprise plan. If your fleet already plants AWS key honeytokens, add one line to the job:

ggshield honeytoken plant --type kubeconfig

Requires ggshield 1.56 or later and the honeytokens:write scope. See Honeytoken types, Protect endpoints with Honeytokens and the ggshield honeytoken plant reference.

Enhancements​

  • Public Monitoring: Filter public incidents by Source owner: the GitHub organization or user, or the Docker Hub namespace, that published the source.
  • Public API:
    • Revoke a secret with POST /v1/secrets/{secret_id}/revoke. Pass provider credentials in the credentials body field to override the workspace defaults. The detector object of secret and incident responses lists which ones the revoker needs. Requires the secrets:write scope.
    • Filter GET /v1/check-runs by commit_sha, pull_request_number or source_id, in addition to incident_id, so you can find the check runs of a pull request even when its findings have no incident. Each check run now also returns its repository's full name and source id.
    • Public incidents now carry the agents analysis result, company_related_verdict (related, unclear, unrelated) and agents_stage, in the list, the detail and the CSV export, and both are filterable, so a SIEM or ticketing tool can reproduce your dashboard views. Available to workspaces with agents analysis.
  • Team Sync: When team sync is on, the Teams page gains a Synced from filter on the provider teams come from, so you can tell synced teams from the ones created by hand.
  • Authentication: Password logins are now locked out for six minutes after ten failed attempts for the same email and IP address. The login endpoint answers 429 with a Retry-After header, and a password_login_locked_out entry in the audit log records the IP address and the number of attempts.
  • Perimeter: On an integration's perimeter, Select all N that match filters is now available at the root level, as on the Perimeter page, so you can monitor or unmonitor every source of an integration in one action.
  • JFrog Container Registry Integration: Federated Docker repositories are now scanned alongside local ones. On existing installations, new federated repositories are not monitored by default, so you choose which ones to add.

Fixes​

  • Public Monitoring: Fixed an issue where adding a custom tag to a filtered selection of public incidents with "select all" applied the tag to every public incident.
  • NHI Governance: Fixed an issue where the ggscout configuration examples on the integration setup page for CyberArk Secrets Manager, GCP Secret Manager and Kubernetes used options ggscout does not read, so the configuration failed to load or silently ignored the key file.
  • Historical scans: Fixed an issue where the queued scans of a large bulk were timed out after a week of waiting for a slot.
  • SharePoint Online and OneDrive Integrations: The Organization.Read.All permission is no longer required on your Entra application. Without it, the installation is named after its tenant ID.

Scan developer machines with less noise, and clean up what you find

calendar icon   Release Date: October 27, 2026

Endpoint Protection scanning a developer machine for secrets

Endpoint Protection now helps you scan your developers' machines at a lower cost, trust what the scan finds, and clean it up. Upgrades no longer trigger a full rescan, validity checks cover more secret types with fewer wrong answers, copies kept by code editors stop flooding the findings list, and a new --background option keeps scheduled scans out of developers' way. The local dashboard (ggshield machine dashboard) then opens on an overview of what to clean, groups findings by AI agent or repository so you can redact them one at a time, and can redact the history databases of Codex and opencode.

What does this mean for you?

  • Validity checks cover more secrets, and get them right: 501 secret types are now analyzed, up from 432, including Elastic, Datadog, Langfuse, Sumo Logic, Gitea and Azure Container Registry. Live SendGrid, Okta, MaxMind and Segment keys, among others, were reported as revoked or left unchecked. They now get the right answer, and a provider outage or rate limit no longer counts as a revocation.
  • Less noise from editor history: VS Code, its forks (Cursor, VSCodium, Windsurf) and JetBrains IDEs keep a copy of every file you edit, so one secret in one file could appear as dozens of findings. These copies no longer fill the findings list, unless the secret in them is valid.
  • Scan without slowing developers down: add --background to ggshield machine scan or ggshield machine report to run the scan at low priority, with 2 to 4 threads and a tenth of the memory (at least 512 MB). The scan takes longer but leaves the machine responsive, which suits a scheduled MDM job. To make it the default for every scan, set scan.resources.background.mode: auto in machine_scan.yaml. Without it, scans run at full speed.
  • Start cleanup from an overview: the local dashboard now opens on an Overview page with one row per cleanup area, such as AI agents, repositories, and history and logs. When there is something to clean, a short guide tells you where to start: overprivileged secrets first, then leaks in history and logs, then secrets in daily use.
  • Redact Codex and opencode history: these assistants keep their history in SQLite databases, where findings could not be redacted. You can now redact them from the local dashboard.

Why is this important?

A machine scan is only useful if it runs often and its findings get acted on. Skipping needless rescans keeps the load on your fleet low after each upgrade, and accurate validity with less duplicate noise lets your team spend its time on the secrets that still work.

Get Started Today!

Endpoint Protection is available for workspaces with a Growth or Enterprise plan. Talk to your Customer Success Manager to enable it, or contact us to upgrade your plan.

Update the plugin on each machine with ggshield plugin install machine_scan, or let your MDM job do it on its next run. See Deploy ggshield at scale.

Then add --background to your scheduled scan, for example ggshield machine report --background. See Run the daily inventory scan.

To start a cleanup, run ggshield machine dashboard to open the overview. See Remediate findings.

Enhancements​

  • Machine Scan:
    • On Windows, scans now cover fixed drives only, skipping USB sticks, optical media and RAM disks, and check only the WSL distributions already running instead of starting every one each day.
    • Scans skip more folders of downloaded or generated files, such as build leftovers in the temp folder (pip-*, pytest-of-*, _MEI*), Windows package caches such as NuGet and Scoop, and Electron app caches, while folders that hold credentials, such as app settings and browser local storage, are still scanned.
    • Validity checks now take custom hosts only from your GitGuardian workspace, and the environment variables and local config files that set them are no longer read. Machine Scan tries custom hosts first, then hosts tied to the secret, then the default hosts, and reports the first valid answer.

Fixes​

  • Machine Scan:
    • Fixed an issue where a token for a self-hosted service, such as a self-hosted GitLab, was checked against the public service and reported as revoked. Validity checks now try the host the secret's file ties it to first, such as a .netrc machine or an .npmrc registry.
    • Fixed an issue where public details of a validity check, such as hosts, project IDs and tenants, appeared as [REDACTED]. Secrets stay redacted, and the next scan restores the details.
    • Fixed an issue where every fine-grained GitHub personal access token was reported with private repository access. That risk now requires proof of access.
    • Fixed an issue where test Stripe keys capped the risk of live Stripe keys at Medium.
    • Fixed an issue where scans of the plugin's own files in full mode reported a HashiCorp Vault token.
  • Confluence Cloud Integration: Fixed an issue where incidents found in Confluence Cloud attachments showed the author as "Unknown". They now show the user who uploaded the attachment.
  • Confluence Data Center Integration: Fixed an issue where a rejected personal access token returned an internal error when you installed the integration or updated its token. GitGuardian now tells you the token is invalid.
  • GitLab Integration: Fixed an issue where a token belonging to a blocked GitLab account was reported as a transient connection error. Token validation now says the account is blocked, and the integration health flags the token instead of reporting GitLab as unreachable.

AI Hooks keep leaked tool output away from the model

calendar icon   Release Date: September 25, 2026

AI Hooks for AI coding tools

A shell command can return a credential nobody asked for. On Claude Code, Codex, and Mistral Vibe, AI Hooks now withhold that output: the assistant reads the ggshield message instead, so the secret stays out of the model and out of the session transcript for Claude Code.

What does this mean for you?

  • Nothing to rotate: a withheld secret never reached the model provider, so there is no credential to revoke. Codex and Vibe still keep the raw output in their local session files. See what stays on disk.
  • Amazon Kiro and Junie CLI: AI Hooks and the AI agents and MCP inventory now cover Kiro (IDE and CLI) and Junie CLI. Both block secrets in commands and file reads, they don't withhold tool output.
  • Clear limits per assistant: MCP and other tool outputs on Claude Code, and every tool output on Cursor, VS Code, Copilot CLI, and Kiro, still reach the model, so ggshield notifies the developer to rotate. Junie CLI runs no post-tool hook, so tool outputs aren't scanned. See what each assistant supports.

Get started now

  1. Upgrade ggshield to 1.55.0 or later.
  2. Run ggshield machine setup to add hooks for Kiro and Junie, or let your scheduled MDM setup job do it. See Deploy ggshield at scale.

Enhancements​

  • ggshield: The API timeout, fixed at 60 seconds until now, can be set with the api_timeout config key or the GITGUARDIAN_API_TIMEOUT environment variable. Raise it if a large scan fails with a read timeout.
  • GitLab Integration: System hooks integrations with a non-admin token now monitor projects in personal namespaces and in groups the service account reaches only through a project.
  • Team Perimeter:
    • Introduced a per-account setting that lets teams keep access to unmonitored sources and their existing incidents instead of removing them from team perimeters.
    • Introduced a per-account setting to automatically remove archived sources from team perimeters.
  • Audit Log: Clarified the number of secrets and whether secrets value were exfiltrated as part of the CSV exports audit logs.
  • Public API:
    • Added optional author attribution for leaks detected through custom sources (BYOS), so an author email can be provided and returned when leaks are found.
    • The secret value and validity endpoints now cover secrets found as part of Public Monitoring, not only Internal Monitoring.

Fixes​

  • Public Incidents: Fixed an issue where the incidents CSV export reported the former ML risk score instead of the agents' risk score shown in the incident list.
  • Incidents: Fixed an issue where risk score filtering did not correctly apply to all incidents.
  • VCS Scanning: Fixed an issue causing excessive recomputation of incident locations, leading to unnecessary repository clones.
  • Historical Scanning: Fixed an issue where historical scan summary emails could be sent many times due to a loop over scanned sources.
  • GitHub Integration: Fixed a security issue where a user could add their own organization to the monitored scope of a private GitHub integration on self-hosted installations with a public GitHub app.
  • OneDrive Integration: Fixed an issue where a OneDrive installation missing the required Graph permissions would silently stop syncing without being marked unhealthy or notifying the customer.

See all your AI agents across the fleet. Stop them leaking your secrets.

calendar icon   Release Date: September 7, 2026

AI discovery: agents, MCP servers, and AI Hooks across the fleet

AI agents read files, run commands, and call MCP servers on your developers' behalf. Most teams cannot say which agents are deployed across the fleet, and which of them touch credentials. Secrets that leave in a prompt or tool call never hit a commit or a pull request, so your existing controls never see them.

Developer Endpoint Protection now does both:

What does this mean for you?

  • Codex and Mistral Vibe: AI Hooks now cover them alongside Claude Code, Cursor, Copilot CLI, and VS Code. They scan prompt submission, pre-tool use, and post-tool use. A block names the secret and how to remove it, so the developer or agent can fix and retry.
  • One command per machine: ggshield machine setup configures the hooks for every detected AI agents on the machine, along with git hooks.
  • Shadow AI you can see: the inventory reports agents and MCP servers per endpoint, hook coverage, and whether an agent's subscription is personal or company.
  • Faster incident response: after a compromise, you know which agents were on the machine, which MCP servers they used, and what those servers could reach. Add --history to ggshield ai discover to get the MCP tool calls parsed from the agent's transcripts.

Why is this important?

Developers using AI coding tools leak secrets at roughly twice the baseline rate. GitGuardian found 24,008 unique secrets in public MCP configuration files in 2025 cf. The State of Secrets Sprawl 2026.

Hooks stop the leak at the tool. The inventory tells you where to look.

Get started now

  1. Upgrade ggshield to 1.54.0 or later.
  2. Follow the Developer Endpoint Protection deployment docs to roll it out across the fleet.

Enhancements​

  • Team Perimeter: Added a workspace setting to automatically remove sources deleted on the remote from team perimeters, while keeping them accessible to workspace managers.
  • NHI Governance: AWS access keys stored in a secrets manager, Vault, or Kubernetes are now linked to their AWS IAM identity in the identity map.

Fixes​

  • Incidents: Fixed an issue where source locations were recomputed too frequently, causing excessive repository clones and bandwidth usage.

Catch credential stealers on your endpoint fleet

calendar icon   Release Date: August 10, 2026

Honeytokens on endpoints

Credential stealers do not hunt around a developer machine, they go straight for the handful of files where developers keep their secrets.

Endpoint Protection already gives you a full inventory of the credentials sitting in those files, and it now adds intrusion detection to that same deployment: ggshield plants a decoy AWS credential exactly where the stealers look first. The decoy opens nothing, so nobody has a reason to touch it. The moment someone does, you get an alert that names the compromised endpoint.

What does this mean for you?

  • A tripwire on the surface attackers hit first: stealers arrive through malicious packages, trojanized tools, and rogue browser extensions. Whichever way they get in, reading that credential file is their first move, and that move is now what exposes them.
  • Alerts with no ambiguity: the decoy has no legitimate use, so any use of it is unauthorized by definition. There is no baseline to learn, no tuning, and no signature list to maintain.
  • A last line of defense: if malware has already slipped past your EDR and other endpoint controls, using the decoy still gives it away.
  • A named machine to investigate: each event carries the IP address, user agent, and timestamp, and resolves to a specific endpoint and its owner.
  • Coverage you can measure: a new Honeytoken protection card in the Endpoints dashboard reports the share of your fleet that is protected and lists the endpoints that are not, so you can drive coverage to completion.
  • No new agent to deploy: planting reuses the ggshield binary you already install for scanning and writes a file rather than running a resident process.

Why is this important?

Credentials on developer machines have been a blind spot for a long time. Repository scanning, CI checks, and collaboration tool monitoring only ever see secrets that leave the laptop, while the credentials that stay local are exactly the ones harvesting malware is built to collect. Endpoint Protection brought those credentials into your inventory. It now watches for the theft itself, at the moment it happens, on a surface where most organizations have no detection at all.

For developers, this is invisible. Planting only ever touches its own credential profile and leaves every other profile on the machine untouched.

Start securing your endpoint fleet now!

Honeytoken protection is available now for workspaces with Endpoint Protection on a Business or Enterprise plan. If you already run endpoint scanning, adding it means nothing more than one MDM job to update and one more scope on your service account token.

Enhancements​

  • Public API: Added the ability to create Personal Access Tokens (PATs) and Service Account Tokens (SATs) programmatically via the API, enabling automated token rotation workflows. Tokens created via the API must have a finite TTL.
  • ggshield: Launched an Azure DevOps extension that lets admins add a ggshield secret scan job to every pipeline in their organization with a single pipeline decorator. See Azure Pipelines for details.
  • Perimeter management: Automatic monitoring and automatic scan toggles are now available on Jira Cloud, Jira Data Center, Confluence Cloud, Confluence Data Center, and Microsoft Teams. New spaces, projects, and channels discovered on these sources can be picked up and scanned without adding them by hand, the same way the VCS integrations already work.

Fixes​

  • Audit Logs: Scans triggered via a Personal Access Token now emit an audit log event.
  • Incidents: Fixed a display error in the decoded claims panel of a JWT secret. Malformed timestamp or scope claims, and payloads that are not a JSON object, now fall back to the raw value instead of breaking the panel.
  • Issue Tracking Integration: Fixed the "Edit issue" dialog closing unexpectedly.
  • Notifications: Fixed an issue where the team name was not populated for notifiers when the workspace contained more than 100 teams.
  • Access Management: Fixed an issue where deactivated members were incorrectly displayed in the grant access dialog.
  • GitHub Checkruns integration: Fixed an issue where a disabled detector could still block pull requests.
  • JFrog Artifactory Integration: Fixed an issue where the JFrog Container Registry reachability check did not route through ggbridge.
  • GitLab Integration: Fixed an issue where GitLab sources appeared as monitored in the integration settings but were not reflected in the perimeter view.