The Decloak Journal
Stories from around the web security world, plus release notes and changes to Decloak itself.

Decloak now maps every finding to eight frameworks, adding NIST CSF 2.0 and the EU Cyber Resilience Act. NIST is mapped at the subcategory level questionnaires actually cite, and the CRA to Annex I of the regulation. Here's how it works, and what a web scan can and can't evidence.

Auditors don't ask for a list of bugs. They ask which controls you meet and how you know. Compliance mapping links each security finding to the framework requirement it relates to. This guide covers why it matters, who uses it and how Decloak does it.

Veracode tracked more than 100 AI models and found the average security pass rate is 56%, up one point from 55%. Models write code that compiles almost every time. They still fail on security in nearly half of tasks. Here is what the report found, what it doesn't prove, and what to do about it.

AI Pentesting now confirms seven tool-backed checks, including SSRF, XXE and OS command injection. It tests every parameterised URL and API call a scan observes, works on modern single-page apps, and confirmed exploits now count towards your overall Security Score.

Scanners tell you what looks wrong. Penetration tests prove what is exploitable. This guide explains what AI pentesting is, who actually needs it, what it can and can't do today, and how Decloak's version works.

You can now sign in to Decloak with Microsoft or GitHub. Under the hood, we contained a long-standing browser-automation bug that could take down other people's scans, made database writes and the live progress page survive brief outages, and fixed several accuracy problems reported by a customer.

Three recent stories: an identity-theft protection company breached via a voice phishing call to one employee, a hardware wallet maker whose own customers got targeted with fake security-alert emails after a vendor breach, and a telecom breach that exposed 14 million email addresses through a third-party software flaw.

A green padlock tells a visitor almost nothing about whether the connection behind it is actually well configured. Certificate expiry, issuer trust, protocol version, and cipher strength are four separate things that can each quietly go wrong while the padlock stays green.

Ten rows, always present, on every report: Confirmed, Clean, or Not Tested, with an honest reason given for anything we genuinely can't assess from outside. And along the way, we found our own reference table was still citing the outdated 2021 standard.

Compliance mapping now covers six frameworks. PCI DSS v4.0 added two requirements specifically to catch Magecart-style card skimming, and it turns out Decloak was already built to catch exactly that.

Every Decloak PDF was a dark-themed HTML page forced into PDF form, raw markdown leaking through, text cut off at page edges, no table of contents, no page numbers. We rebuilt it from scratch as a real, print-safe document system, because for a lot of customers, this PDF is the actual deliverable.

Most scanners test what's public. The moment a page sits behind a login, especially a passkey, they stop. Decloak's authenticated scan mode captures a real logged-in session through a browser extension instead of trying to script a login that, with WebAuthn, technically can't be scripted at all.

Three views instead of one wall of data, confidence tiers on every finding, a real fix-it plan instead of just a grade, and full visibility into what actually got checked. The free scan grew up too, same report, same rigor, real evidence from your own site.

Model Context Protocol has quietly become the standard way AI agents connect to real tools, with over 97 million monthly SDK downloads and adoption across every major AI lab. Decloak now ships an MCP server, so Claude, Cursor, or any MCP-compatible agent can trigger a scan and read the results directly.

Built for the professionals who told us they wanted actual control, Expert Mode unlocks named, reusable Scan Profiles that tune the crawler, Active Testing, and AI Pentesting independently, and shows you exactly what effect each setting actually had.

A missing header that's true of every page on your site used to show up as one finding card per page, ten cards for ten pages, eighty-three for eighty-three. Now it's one card, with every affected location listed underneath.

Three recent stories, all API-shaped: a ServiceNow access-control gap that let unauthenticated queries pull customer instance data, a compromised third-party app that gave attackers a path into Salesforce customer connections, and an API security testing firm exposed by exactly the kind of unprotected database it tests for.

Every other layer in Decloak observes and flags things that look wrong. AI Pentesting is the one that actually attempts exploitation, inside a sandbox, with a fixed toolkit of five real, named tools, and only calls something confirmed once it's proven, not pattern-matched.

Your account now opens to an actual command center instead of a list of scans, aggregate posture across every domain you monitor, plus a dedicated scoreboard for each one. Live for every account, free included.

An auditor doesn't want a login to your dashboard. They want a self-contained, timestamped bundle they can file as proof. Evidence Packages turn a date range of scan history into exactly that, one ZIP, ready for handoff.

Four DNS records determine whether someone can send email that looks like it came from you, hijack your domain's resolution, or issue a fraudulent SSL certificate in your name. Here's what each one actually does, and how Decloak checks all four automatically.

Three recent stories, all misconfiguration rather than a hack: a data-extortion group hitting Microsoft Power Pages across roughly 15 organisations, a Salesforce campaign that turned a misconfiguration-detection tool into an attack tool, and a hardware wallet company breached through its shipping provider.

Most of what a modern web app actually does happens through an API, and most API vulnerabilities never show up in a page-level scan. Decloak Enterprise now systematically discovers and lightly tests REST, GraphQL, and SOAP endpoints as part of Active Security Testing.

When the scan target is a raw IP address rather than a domain, Decloak now passively checks around 18 commonly-abused ports, databases, remote access, file transfer, for anything open and reachable, plus a reverse DNS lookup. Connect-only, no probe data sent.

A wordlist can only ever find the subdomains someone thought to guess. Decloak now also queries certificate transparency logs, the public record of every hostname a certificate authority has ever issued an SSL cert for, so subdomains nobody guessed still get found.

A single-page scan checks one URL. The full-site AI agent decides for itself which pages on your domain are worth investigating, runs all 8 layers on each one, and shows every step of its reasoning as it goes, not just the final report.

A subdomain pointing at a third-party service you stopped using isn't just clutter, it's claimable. Decloak now checks every discovered subdomain's CNAME record for exactly that, live on every Starter+ scan, no extra step required.

Five recent stories, all about the same underlying pattern: apps built by describing them in plain English, shipped fast, and left with security defaults nobody thought to check. A Base44 auth bypass, 380,000 publicly indexed AI-built apps, and a backdoor hiding inside AI coding rules themselves.

A full scan can surface hundreds of findings, useful for coverage, useless for a Monday-morning to-do list. The new Priority Remediation Plan collapses that into a ranked top-25, with the ranking logic shown, not hidden.

A chat widget lives in the bottom-right corner of every page now. For free accounts it's a curated FAQ router. For paid plans it's a scan-aware agent that can pull your actual findings, look up a real CVE, and explain a compliance control, without you leaving the report.

Four stories from the last few weeks: a Nextcloud misconfiguration that exposed 367,000 files, a Salesforce webpage misconfiguration behind a 13.5-million-record breach, an actively exploited SharePoint zero-day, and the year's secrets sprawl numbers.

CORS errors are annoying enough during development that a lot of teams silence them permanently with a wildcard. That single header change quietly opens your API to any website on the internet that wants to make requests on a logged-in user's behalf.

Every finding Decloak detects is now mapped to NIS2 and DORA controls alongside SOC 2 and ISO 27001. Same 36 finding categories, same underlying scan, two more frameworks to help you get ahead of this October's NIS2 deadline.

Secure, HttpOnly, and SameSite sound like minor cookie settings. Missing any one of them turns a routine session cookie into something an attacker can read, steal over an open WiFi network, or trigger from a page you never visited.

Pro and above can now brand their Decloak PDF reports end to end: your logo, your accent color, your fonts, your footer. Built for agencies, consultants, and anyone using security scans as part of client work or lead generation.

GitGuardian tracked 28.65 million hardcoded secrets pushed to public GitHub in 2025, a 34% jump in a single year. Most never get revoked. Here's why hardcoded API keys keep happening, what they actually cost, and how to check your own site in minutes.

Four npm supply chain compromises in four months, including a 100-million-download HTTP client, plus a subdomain takeover disclosed against Anthropic itself. What each incident shares, and what it means for a site you didn't think was affected.

Every domain accumulates subdomains nobody remembers: old staging environments, abandoned marketing pages, test deployments. Most were never meant to be public, and almost nobody audits them.

Five real security stories from the last few months, all touching attack surfaces Decloak scans for: a plugin flaw hitting 500,000 WordPress sites, a Supabase misconfiguration that exposed 1.5 million API keys, and a card skimmer hiding inside Google Tag Manager.

Source maps make debugging easier by linking minified code back to the original files. Left enabled in production, they hand an attacker your app's entire uncompiled source, comments and all.

Missing Content-Security-Policy headers show up in the vast majority of the sites we scan. Here's what CSP actually protects against, why it gets skipped, and how to add a working policy without breaking your site.

Row Level Security is off by default in Supabase. That one setting is behind the most common security failure we see in AI-built apps - and it takes about 30 seconds to check whether yours is affected.