A computed gap, 149 days, from Palo Alto's advisory to ReliaQuest's warning; the fixed versions per train; four scores for one flaw; what no source establishes; UK controls; and an ordered checklist. Defender level only.
What Let's Encrypt's own pages and the CA/Browser Forum's rules say about 64-day certificates, what a fixed renewal rule does at 90, 64 and 45 days, what the record leaves out, what UK guidance asks for, and an ordered checklist.
What SOCRadar's CyberXero report establishes, what it does not, the arithmetic behind 32 shells in 61 seconds and 564,073 of 628,000 records, the public fixes and CISA KEV status for the named CVEs, what the model's maker has said, UK controls, and a ranked checklist. Defender level only.
What the primary records establish about CVE-2026-85097: the first attempt, a fix date nobody publishes, three flaws in five weeks on one database's dates, a spray of 56 requests from 44 addresses, UK controls and an ordered checklist. Defender level only.
What Booz Allen's page and white paper establish about an AI test in its OT lab, what they leave out, the arithmetic behind 8 of 8, how the UK AI Security Institute's industrial range and the NCSC compare, what UK guidance covers, and a ranked checklist. Defender level only.
What Google's and Microsoft's own pages say about the default, which settings stop a calendar lure and which do not, the number behind "exponential", what no source establishes, UK reach of the NCSC and Cyber Essentials, and a ranked checklist. No lure is printed.
What Modat's pages, Reuters and others establish about 8,547 exposed wind and solar systems, the arithmetic behind the percentages, why the UK is outside the count, what the NIS Regulations and the NCSC say, and a ranked checklist. Nothing identifying a site is printed.
What the researchers' write-up and Chromium's own source establish about two characters that pass the browser's lookalike checks, what is not stated, why a list fails open for a letter or a brand it does not hold, UK controls and a ranked checklist. No lookalike domain is printed.
What iVerify, Google, Lookout, Censys, Report URI and Apple establish about P7 DarkSword: the six flaws and their fixes, which iPhones are exposed, what is not stated, UK controls and a ranked checklist. No indicators are printed.
Dates, counts and labels in Anthropic's 9 October report on unintended model actions: what the police statement adds, what no source states, and what UK organisations that give agents live internet access should do.
What Push Security and BleepingComputer establish about the Adception campaign: the four stops, the cloaking gates, the swapped clipboard command, what is not stated, UK controls for Macs and a ranked checklist. No attacker addresses are printed.
A fake security-audit workflow, counted four ways: 345 repositories in a day (81% forks), 772 over a month, Socket's unnumbered tens of thousands, and now more than 30,000 from GitGuardian. What each counts, what ran, and what a UK reader can conclude.
Microsoft's launch chart sets an 85 ms measured API against JevBench's adjusted 380 ms for Quyet-1.0-Large, whose raw timing is 116 ms. The 36-benchmark accuracy ranking contains no general-purpose LLM, and no independent result for Decision-1 exists yet.
What AnyDesk's changelogs, its post on X, the researchers' post, NVD, CVE.org and CISA's catalogue establish about the AnyDesk Linux flaw: dates, scope, the relay dispute, the UK timescales and a ranked checklist.
Recounting Comparitech's Q3 2026 ransomware record from its own tables: 247 of 2,627 confirmed, a Q2 that was a dip, 517 of the 597 extra claims from strains with no Q2 claims, and two other trackers that agree on direction and not size.
A computed gap, one build that two vendors described in opposite ways until the vendor changed its answer, and a backup console that MSPs expose to clients. What the record, Huntress and Ahsay state, what is not stated, UK clocks for MSPs and the order of actions.
Microsoft's 8 October notice sets two Windows Update certificate dates. What its six-row table states and leaves out, which listed versions leave support first, the WSUS exception, the UK clocks and the order to work in.
What the ICO's 8 October report prints for each of ten AI developers, what it leaves out, what the call for evidence on agentic AI asks, and the register a UK organisation using these tools should keep before 20 November.
Anthropic expects over 90 per cent of OSS Scanner's unreviewed reports to be true, but gives no rate for the 4,824 already sent direct. Its early sample reads 88 or 99 per cent by definition. Also the infrastructure program's eleven partners, and UK clocks.
Three NetScaler bulletins in 11 days, ten CVEs, and a new SAML flaw whose affected range ends at the previous fix build. What Citrix states and leaves out, the UK patching clocks and what to check.
Recounting Pwn2Own Ireland 2026 from ZDI's own tables: 61 attempts, 51 successes, 10 failures, 2 inferred withdrawals and 29 collision-labelled successes. No vendor page read on 9 October ties a fix to a contest bug.
Anthropic's Usage Policy takes effect 12 November: 4,424 words against 2,473. What changed in substance, what the texts do not establish, and what a UK organisation building on Claude should record before the date.
OpenAI says it banned two influence operations that used ChatGPT and rates their reach Category 5 and 4 of 6. What the page states and omits, how Anthropic's reports compare, and what UK publishers and security teams can check.
PCI SSC's advisory AI guidance, dated September 2026, has one 'must' against 130 'should'. What it ties to PCI DSS, what is new, what it leaves undefined, and what UK merchants and suppliers can check.
What Zenity's five posts, AWS's AgentCore pages and Dark Reading's report establish about AgentCorruption: dates, scope, what AWS states, what UK customers must still check on agent roles, and a ranked checklist.
What the 8 October seizure papers, the 58-page joint advisory and the NCSC's own item establish: two alleged breaches, six scan targets not said to be breached, 20 universities or six, and a UK checklist.
OpenAI's 7 October teen post gives no group size, period or method for its figures, and its social media comparison sets a survey against logs. What UK schools, parents and providers can check under Ofcom, ICO and DfE rules.
Of 83 CVEs in Splunk's five 7 October advisories, three Splunk Enterprise flaws score 9.0 or more. One is explained. Two are a weakness class and a score, and the October affected ranges end at August's fix builds.
What CrowdStrike's 7 October post establishes and what it leaves out: AI tooling from the actor's files, no named bank, no victim count, no Anthropic model named, a stack 3 to 63 days old, and a UK checklist.
Bitdefender's Midnight Mimosa report: malware preinstalled in cheap Android firmware, not removable by the owner. The UK is in a chart at 3.49% with no count behind it. The actor, the point of insertion and any reset test are not given; 13 Play apps were still listed.
Footnote 2 explains why 90 per cent off a token is 'around 75 per cent' off the bill. Anthropic's chart data put the 75 per cent at Medium effort and show Max costing 2.3 to 3.6 times Haiku 4.5 per task on three of four benchmarks.
One name, two versions, 15 days apart: what OpenAI's card, help pages and API docs establish about GPT-6 Sol in ChatGPT chat, what they leave out, and a UK checklist for model change control.
What Talos's 8 October post on UAT-11985 establishes and what it leaves out: three emails behind the AI-assisted label, a relay that forwards typed codes and taps, no victim count, and what UK organisations on Google can do.
What the 6 October Lightwell release states and leaves out, what a search of NVD, CVE.org, GitHub and osv.dev found, how backports confuse scanners, and what Cyber Essentials and the NCSC mean for a UK Java estate.
A Shai-Hulud worm release of the tensorlake package sat on npm for no more than about 102 minutes, about 91 of them after Socket flagged it. It carried valid provenance and a trusted publisher. No source reports a victim count, and six native packages at the same version remain.
Monitoring is not unlawful in itself, and a score is not a decision. The Guardian's account leaves open whether callers were told, whether an impact assessment came first, and what managers do with a fail score.