AI Weekly Malaysia

Epic, which makes the MyChart patient portal used to maintain over 320 million patient records in the US, has paused most of its product development for roughly six weeks to fix security bugs, per founder and CEO Judy Faulkner speaking to Modern Healthcare. The flaws surfaced after a deployment of Anthropic's frontier cybersecurity model, Mythos, and chief security officer Stirling Martin told The Times that some customer configurations of MyChart could let outsiders read patient records without leaving any entry in the software's logs. Martin said the model did not establish whether records could also be altered undetected, but Epic judged the risk serious enough to remediate; TechCrunch notes Epic has not disclosed the nature of the bugs.

Why: The concrete lesson is the logging gap, not the vendor: a read of patient records that leaves no trace in application logs defeats detection and audit entirely, and that class of bug is exactly what an AI security model found here at scale. If you ship anything with a permission model — patient data, tenant data, customer records — test whether privileged or misconfigured access paths produce an audit entry, and treat 'no log line' as a bug of its own. Also note the release-planning implication: a six-week freeze on most product development is what a serious finding costs, so teams running continuous release trains should decide in advance what triggers a stop-ship versus a patch-forward.

A year after CTO Dane Knecht pledged to make every Cloudflare feature available to everyone, Cloudflare says Logpush and Logpush Transformers have moved off Enterprise-only and onto all plans, including Free, Pro, and Business, via self-service pay-as-you-go. New Logpush datasets added include account-scoped firewall events, WebSocket analytics, and per-zone post-quantum visibility, and Transformers lets you filter, redact, enrich, and reformat logs with SQL before delivery without running a separate extraction pipeline. Cloudflare states the goal of every feature being available to everyone is not yet met.

Why: If you're on a Free, Pro, or Business plan, you may now be able to export Cloudflare logs directly instead of hand-rolling a Workers-based log shipper or buying an Enterprise contract just for Logpush — and SQL-based Transformers may remove the extraction step from your log pipeline. The post does not state Logpush per-GB pricing or destination limits, so compare the pay-as-you-go rate against your current logging vendor before switching, and check which datasets are actually exposed on your plan tier.

Cloudflare announced eight updates to its Observability stack on October 2, 2026, consolidating logs, traces, analytics, alerts, dashboards, and exports into one platform. Concretely: a combined Logs home merging Workers Observability with Log Explorer across datasets including HTTP events, firewall events, Workers, Containers, R2 and AI Gateway; Cloudflare Traces in open beta giving request-level views from edge to origin; a unified SQL API for querying Cloudflare data; custom alerts and dashboards; 30-day analytics retention; and Logpush now available on self-serve plans. Cloudflare also says it is moving to one pricing model for observability data ingested and stored across the platform, with cross-dataset querying listed as coming soon.

Why: If you already run Workers, R2, or AI Gateway, this is a concrete change in where you debug and what you pay for: Logpush on self-serve plans removes the plan upgrade that previously gated exporting logs, and 30-day analytics retention plus a single SQL API means you can drop some separate log-shipping or query tooling. The pricing consolidation is the item to actually check against your invoice — 'one pricing model for ingested and stored data' changes the cost shape, so re-run your current ingest volume against the new model before committing to it, and note that cross-dataset queries are still 'coming soon', so don't design a workflow that depends on them yet.