Your leaked secrets now show up in Wiz. GitGuardian now sends leaked secrets from GitHub, GitLab, Bitbucket, and Azure DevOps to Wiz once a day, with validity, severity, and a link back to the incident. Your cloud and AppSec teams see the same leaked key, and the secret value never leaves GitGuardian. Follow GitGuardian on Tl;dr. * The new GitGuardian Wiz integration: GitGuardian now has an integration with Wiz. * Daily sync: Once a day, GitGuardian sends open secret incidents from GitHub, GitLab, Bitbucket, and Azure DevOps to Wiz as native secret findings. * Full context: Each finding carries the repository, file, commit, detector, validity, and severity, plus a link back to the incident in GitGuardian. * Secret stays private: The secret value never leaves GitGuardian. Wiz only receives a hash and metadata. In a lot of companies, the cloud security team works in Wiz, and the AppSec team works in GitGuardian. Wiz is where cloud risk gets triaged and where the report for the CISO comes from. GitGuardian is where leaked secrets get found and fixed. Until now, the two teams rarely looked at the same thing. So the person looking at an exposed cloud resource in Wiz couldn't see that the AWS key for that same account was committed to a private repo eight months ago and still works. That gap is what this integration closes. GitGuardian now sends its secret findings straight into Wiz, so leaked credentials sit next to the cloud and identity risk they're connected to. Both teams now look at the same leaked key, each in the tool they already use. Why secrets belong next to your cloud risk. Attackers don't need to break in when they can log in. Compromised credentials were the most common technique across full breach chains in the Verizon 2026 Data Breach Investigations Report, showing up in 39% of them. And leaked secrets don't go away on their own: of the credentials GitGuardian found valid in 2022, more than 64% still worked in January 2026. Wiz is good at showing how cloud resources connect and which issues matter most. GitGuardian is good at finding secrets across code, developer laptops, collaboration tools, and public sources, checking whether they still work, and helping teams fix them. Customers running both GitGuardian and Wiz kept asking the same thing: why do I need two screens to see one problem? Now they don't. What GitGuardian sends to Wiz. For every open secret incident in a connected repository, Wiz receives one finding with: * The repository, file path, and commit where the secret was found. * The detector that caught it (GitGuardian has 550+ of them). * Whether the secret is still valid, and when that was last checked, so Wiz can put the keys that still work ahead of every string that only looks like a key. * The incident's severity in GitGuardian, mapped to a Wiz severity. * A link back to the full incident in GitGuardian. If a secret shows up several times in the same repository, Wiz gets the most recent occurrence. The full history stays in GitGuardian. The secret itself never leaves GitGuardian. Wiz receives a SHA-256 hash of the value and the metadata above, nothing more. How the sync works. Once a day, GitGuardian sends Wiz the full list of open incidents (triggered or assigned) for each connected source. Wiz keeps a finding open as long as it appears in the latest upload. When your team resolves or ignores an incident in GitGuardian, it drops out of the next sync, and Wiz removes the finding. Most severities map across directly. For the two Wiz doesn't have, you decide. You can change this anytime, and it takes effect at the next sync. What you get by keeping GitGuardian in the loop. Wiz shows you where a leaked secret sits in your cloud risk picture. GitGuardian's secret scanning finds it, proves whether it still works, and gets it fixed. That means 550+ detectors with validity checks that tell you which keys are live, remediation workflows like similar-incident grouping and playbooks, and prevention at commit time with ggshield, so fewer secrets land in your code and other assets in the first place. Every finding in Wiz links back to its incident, so going from "we should look at this" to "this is fixed" takes one click. GitGuardian also covers places outside your repositories, like Slack, Jira, Confluence, and developer machines. Those findings stay in GitGuardian, because the integration only sends incidents from version control sources. How to set up the GitGuardian Wiz integration. You'll need a Wiz user who can add integrations. You don't need to create a service account first, because the GitGuardian integration in Wiz creates one for you. * In Wiz, open the GitGuardian integration page. Wiz gives you a Client ID, a Client secret, an Authentication URL, and an API endpoint URL. * In GitGuardian, go to Settings > Integrations > Wiz and click Configure. * Paste the four values and choose how to map Info and Unknown severities. * Click Add integration. Your first findings show up in Wiz within 24 hours. You can pause or resume the sync from the same settings page at any time. One tip: start from the GitGuardian integration page in Wiz rather than creating a token yourself in Wiz settings. A token you create manually won't have the permissions the sync needs. Good to know. * New findings can take up to 24 hours to show up in Wiz, and resolved ones can stay for up to 7 days. * Some findings may be skipped at first. If Wiz doesn't support a GitGuardian detector yet, findings from it are held back until Wiz adds it. That usually takes a few days and clears on its own. * Custom detectors and Gerrit aren't supported, and findings without a file path are skipped. Try it. If you already use GitGuardian and Wiz, you can connect them today in a few minutes. If you use Wiz and want to see what's hiding in your repositories, book a demo and GitGuardian'll show you both together. Faq. Does GitGuardian integrate with Wiz? Does Wiz receive the secret value? Which sources sync to Wiz? How often does GitGuardian sync findings to Wiz?

Upwind security raises $400 million at $3.8 billion valuation. By Mike Lennon Wednesday, October 28, 2026 SecurityWeek Cloud security startup Upwind has secured $400 million, signaling a shift from acquisition target to independent powerhouse. Led by former Aqua Security executives, the firm's $3.8 billion valuation highlights surging demand for "runtime" protection. This war chest allows Upwind to rival giants like Wiz and Datadog as SecurityWeek

Websites shut down globally after AI finds cybersecurity flaw affecting 70% of the internet. Lisa Eadicicco, Hanna Ziady, CNN Thu, October 22, 2026 at 11:26 AM PDT Governments and companies around the world are racing to fix vulnerabilities revealed by artificial intelligence that could affect 70% of the world's websites. Some websites and services briefly went dark after the set of vulnerabilities were announced Wednesday. The US National Security Agency and Europe's cybersecurity agency advised companies to take immediate action to address two critical flaws in PHP, a programming language that powers 70% of the world's websites. The flaws in PHP were uncovered and addressed by teams at OpenAI, Google-owned cybersecurity company Wiz, and another cybersecurity company, Calif. The underlying flaws had existed for a decade, but exploiting them involved a complex set of steps "at the edge of what human researchers could practically achieve," according to Wiz. Researchers then deployed AI to adapt techniques for taking advantage of those vulnerabilities - known as as "exploits" in cybersecurity - and analyze the results. The bugs, collectively called PHP2Shell, could allow attackers to break into websites and read memory that could contain sensitive information, like passwords. The PHP Foundation, the organization behind the coding language, has released a patch for the bugs, which have been hidden in their software for years, and is urging website operators to update their systems immediately. The CEO of Cloudflare said on X that his company's network has observed millions of attempts to exploit the vulnerabilities in the past couple of days. "With PHP behind such a vast share of the web, the exposure could reach almost everywhere people spend money online," said Nigel Green, the CEO of deVere Group, a financial advisory firm. "Booking platforms, marketplaces, subscription services, ticketing sites, delivery apps and utility portals could all be holding card details on systems built with the same kind of code," he added. 'AI inflection point' The vulnerabilities involve an issue with how the PHP language works with a computer's memory. When a website request unexpectedly ends, PHP could leave data behind in the memory that can be accessed and potentially corrupted or exposed later. The flaws could allow attackers to remotely execute code, disrupt services and expose customer data, according to web infrastructure provider Cloudflare, which has been working with the PHP Foundation, Calif, OpenAI and Wiz to address the issue. "Think of a hotel room where you check out, but your key still works," Patrick Fussell, global head of adversary simulation at IBM, told CNN. "And so you can just go back into that hotel room later, and now somebody else's stuff is there." The bugs were discovered in late August but were disclosed to the public only on Wednesday, after PHP had come up with a fix. AI played a crucial role in identifying and fixing vulnerabilities "that had remained hidden in the PHP codebase for more than a decade," according to Wiz. The company called PHP the "backbone of the web" and said the episode marks an AI inflection point. "What AI changed was the ability to understand the weaknesses," Wiz researchers wrote in a blog post Wednesday, and then quickly exploit those weaknesses into a way to attack. "With frontier AI models and the right tools, a single researcher completed in a week what previously would have taken a world-class team months of work," they added. Researchers at Wiz used Google's Gemini 4 Argon, Wiz Atlas and OpenAI's GPT-5.6 Sol during the research process. World leaders weigh in. Global leaders urged organizations to take action. Dutch Prime Minister Rob Jetten said that his cabinet was "closely monitoring the situation surrounding the vulnerabilities in PHP." Japan's Prime Minister Sanae Takaichi said companies should consider suspending services if necessary in order to reduce their exposure. "Please check if your publicly available websites use PHP, and prepare to apply the fix patch that will be released tonight... as soon as possible," she posted on X Wednesday. Japanese airline ANA, railway operator JR West and the country's largest bank, MUFG, were among companies that reported some webpages and services temporarily suspended. In Europe, government websites in France, Denmark, Finland and the Netherlands, including the Dutch cyber security agency, were temporarily taken offline while security fixes were implemented. The Wikimedia Foundation, the non-profit that operates Wikipedia, told CNN Thursday that it was "in the process of addressing security vulnerabilities in PHP," and that a number of its systems had been taken down as a "precautionary measure." Nearly three dozen UK government services are unavailable and four are "partially unavailable" while security upgrades take place, UK government minister Elizabeth Lloyd told the House of Lords Thursday. The Journal, Ireland's second most-popular news outlet, was temporarily offline Thursday morning while it bolstered its "defences," it said in a notice. A shift in cybersecurity. Wiz researchers say the issue is on par with the Heartbleed bug from 2014, which impacted an encryption technology estimated to be used by some two-thirds of the Web. Heartbleed allowed cybercriminals to access data that should have been protected. Like Heartbleed, the researchers at Wiz say PHP2Shell could similarly serve as a turning point in cybersecurity. While the vulnerabilities existed for years, AI made it practical to deploy them. "The speed with which vulnerabilities are being discovered is well beyond what it ever was before," said Fussell. Even though a patch has been released, it's likely that not all companies and organizations will update their systems at the same time, according to Gang Wang, associate professor of computer science at the University of Illinois. That could give bad actors a window to exploit it now that the vulnerability has been made public - and they can now do so faster using AI. But taking advantage of the vulnerability is no easy task, even with the help of AI, according to Fussell. "This is being touted as like, 'Hey, you can push a button and basically take over a server type of thing,'" he said. "...To actually pull this off requires a couple of conditions that are actually fairly complex and not always going to work out in favor of somebody who's trying to go and exploit this bug." - CNN's John Liu, Anna Cooban, Amy Croffey and James Frater contributed reporting.