Cybersecurity Insights & Expert Analysis
‍

CISA lists this one under Google Brotli, and the entry never mentions Node.js. Patching your runtime fixes it on some hosts, does nothing on others, and was never needed on a third set. Here is how to tell which you have.

Two critical PHP remote code execution flaws, patched 21 October 2026. The version number in your ticket cannot tell you whether you were exposed. Your SAPI, worker count and effective ini values can.

WordPress patched a race in its update staging path on 28 October; CISA listed it as actively exploited five days later. The extraction still runs from the version you are updating from.

A crosswalk is not evidence. What artifact actually satisfies each NIST AI RMF function, which subcategories a penetration test answers, and why aligned, certified and tested are three different states.

Policy says inventory your AI, but few define the artifact. What the G7 minimum elements actually require, which fields you can re-derive and which are only prose, and five ways to validate an AI-BOM instead of filing it.

AI changed the speed of testing, not which half was hard. What autonomous tools genuinely catch, what they still miss, and what makes a pentest a pentest.

There is no AI-specific SOC 2 and no AI trust services category. What there is, is an existing criterion your AI system quietly stopped satisfying. Where AI systems land in the common criteria, why the carve-out matters, and what evidence over a period means when prompts change weekly.

There is no shortage of AI vendor question lists. What is scarce is a view of which answers break when somebody tests them. Six claims that survive a questionnaire and not an engagement, the test that settles each, and what to ask instead.

Article 15 sets an outcome and names no test, but Annex IV asks for dated, signed test reports covering pre-determined changes. What that report has to contain, who owes it, and why the December 2027 date is the window in which the evidence gets generated.

An MCP server is an API with an unusually trusting client and an unusually powerful backend. Testing it means exposure and transport, three authorization attempts against a stated MUST NOT, the advertised tool surface, and what the server sends back — almost all of it without a model in the loop.

Forty prompt-injection payloads, none successful, risk low — and six weeks later the agent refunds the same customer twice. The unit of an agent test is the action, not the answer. Four phases, five channels, and why findings carry a rate instead of a checkmark.

“Test the customer-facing AI assistant” is one sentence, and the whole engagement will be argued from it. The seven surfaces an AI penetration test scope must name, what belongs in the rules of engagement, and what a finding must carry.