Welcome to curated list of handpicked free online resources related to IT, cloud, Big Data, programming languages, Devops. Fresh news and community maintained list of links updated daily. Like what you see? [ Join our newsletter ]

Google Cloud London outage: Why infrastructure resilience is not business resilience

Categories

Tags cloud-and-infrastructure architecture-and-apis software-engineering

The October 2026 Google Cloud London outage revealed that a single zone failure can disrupt banks, courts, and couriers even when other zones remain online. This editorial examines how IT leaders must map hidden dependencies, define failover authority, and align protection spending with actual business impact before the next incident occurs. By Justin Sharrocks.

On 20 October, a power event took Google Cloud’s europe-west2-b zone offline. Although one of three zones in the London region, its failure disrupted Revolut, HSBC, DPD, Royal Mail, and the video platform for remote court hearings in England and Wales. Google’s preliminary report found secondary failover and queuing delays across infrastructure that had not lost power, underscoring that infrastructure resilience does not automatically equal business resilience.

The first architectural question is dependency mapping. A zone can be isolated while an application spanning several zones still depends on just one of them. Databases, message queues, identity services, DNS, and third-party software may all sit in a single zone, exposing the entire service. The same risk applies to suppliers: a payment provider or SaaS tool running in the affected zone will impact your customers even if your own infrastructure is elsewhere. Leaders should follow a customer journey for their most critical service, recording every component’s region and zone, then ask each supplier the same questions.

Authority, cost, and rehearsal determine whether migration is actually possible. Google advised customers to move workloads “if feasible,” but feasibility depends on pre-made decisions. Someone must be named and empowered to trigger failover. Standby capacity and replicated data carry costs that require budget holder agreement in advance. Finally, untested plans contain assumptions that surface only under pressure. A simple rehearsal during working hours, with someone keeping time and someone taking notes, reveals true recovery times and unclear roles. Good read!

[Read More]

When the cloud goes dark, the SLA sends a credit

Categories

Tags cloud-and-infrastructure software-engineering devops-and-ci-cd

Recent AWS and Google outages show that hyperscaler SLAs offer billing credits rather than operational remedies. Engineers must understand what downtime actually costs and plan for failure beyond the credit. By Michael Wallace.

Both put the work on the customer. AWS requires a claim through its Support Center by the end of the second billing cycle after the incident, with your own request logs documenting the errors. Google requires you to notify support within 60 days, with log files showing the downtime. Miss the deadline or the evidence, and you forfeit the credit.

Source: https://www.innoscale.net/cloud-outages-sla-credits/

Two recent cloud outages illustrate a critical gap between availability metrics and operational reality. AWS experienced a 5.5-hour incident in a Tokyo availability zone that blocked launches, scaling, and provisioning while leaving running instances unaffected. Google’s London outage lasted six hours after a sensing error prevented diesel generators from starting during a utility failure. Both events demonstrate that even hyperscalers fail, and the status signals engineers rely on can themselves be unreliable.

The remedy in both cases is a service credit, not a fix. AWS EC2 credits range from 10% to 100% of the monthly bill based on uptime shortfalls, while Google’s Compute Engine offers similar tiered credits. Both require customer claims with log evidence within strict deadlines, and both define the credit as the sole and exclusive remedy. Critically, AWS counts an instance as unavailable only when it lacks external connectivity. During the Tokyo incident, running instances stayed connected, so the inability to launch or scale may not have triggered the SLA at all.

For practitioners, the implication is clear: a credit does not cover lost revenue, missed deployments, or customer impact. Teams should calculate the actual cost of an hour of downtime and compare it against the SLA credit. The real question is who answers when things break, what telemetry they can access, and whether your architecture can survive a zone loss without relying on provider remediation. Good read!

[Read More]

Access to Microsoft Outlook and other services being restored as cyber security chief investigates

Categories

Tags cloud-and-infrastructure security-and-privacy business-and-emerging-tech

A widespread Microsoft outage disrupted Outlook and other services across Australia and globally, prompting an investigation by the national cyber security coordinator. The incident underscores the strategic risks of relying on a few major cloud providers and the operational impact of configuration failures on engineering teams. By Cam Wilson.

Microsoft has begun restoring access to Outlook and other online services following a widespread outage that left many users unable to access email accounts. The disruption, which began affecting Australians just after 3 AM AEDT, brought businesses and government agencies to a standstill.

While Microsoft states there is no indication of a cyber attack, the company is investigating recent configuration changes as a potential cause. Engineers identified a process responsible for establishing secure connections that became overwhelmed, causing servers to stop processing requests.

This technical failure highlights a critical strategic risk for engineering organizations: the trade-off between the cost efficiencies of cloud centralization and the lack of redundancy when a single provider fails. Because many organizations rely on these platforms for basic authentication and communication, a single point of failure can halt entire operations. For leadership, the decision is whether to accept the operational risk of a single vendor or invest in multi-cloud redundancy to ensure business continuity during systemic failures. Good read!

[Read More]

The Blackwell fingerprint: What model weights reveal about hardware boundaries

Categories

Tags ai-and-machine-learning architecture-and-apis security-and-privacy

A forensic analysis of model weights suggests several Chinese AI labs have trained on export-controlled NVIDIA Blackwell GPUs, raising questions about how architectural boundaries and hardware provenance shape frontier AI development. By Will DePue.

The boundary between a model’s weights and the hardware that produced them is thinner than it appears. Will DePue’s forensic analysis of publicly released models finds that six models from DeepSeek, Moonshot AI, MiniMax, and Ant Group carry numerical patterns matching NVIDIA’s Blackwell GPUs, while earlier models from the same labs match the older Hopper generation. The evidence comes from the weights themselves: researchers recover initial values and search for hardware configurations that reproduce them, confirming matches on physical Blackwell chips for DeepSeek-V4-Flash and Kimi K3.

The architectural tension is that a fingerprint identifies the hardware used to generate starting weights, not every chip that later trained the model. A lab could initialize weights on one system and continue training on another, or use a mixed cluster where Blackwell patterns survive alongside Huawei participation. The method also cannot reveal chip ownership or location; Blackwell systems can be rented from data centers outside China. Critically, the findings establish access to advanced hardware but do not prove export-control violations.

The trade-off is visibility versus certainty. Forensic weight analysis offers technical evidence of hardware access, yet it cannot establish where chips were located, how access was obtained, or whether restrictions were breached. The failure mode is assuming a Blackwell fingerprint equals a complete training history or a legal violation. Before adopting this approach, teams must resolve whether model provenance can ever be trusted as a compliance signal, or whether hardware boundaries remain intentionally porous. Interesting read!

[Read More]

EFF to lawmakers: Ground AI cybersecurity rules in best practices

Categories

Tags architecture-and-apis security-and-privacy software-engineering

EFF argues that AI regulation should prioritize proven cybersecurity boundaries over speculative doomsday scenarios. By Jacob Hoffman-Andrews, Tori Noble, and Maddie Daly.

The OpenAI-Hugging Face incident wasn’t some theoretical risk—it was a concrete architectural failure. The testing environment lacked basic isolation. EFF’s message to lawmakers: stop chasing sci-fi scenarios and ground rules in actual, demonstrated risks using cybersecurity practices we already know work.

The tension is real: move fast vs. keep people safe. But the answer isn’t new tech. It’s applying existing standards rigorously.

Start with sandboxing. When an AI task carries real risk—like reaching outside its environment—that code runs in a disconnected, monitored container. No lateral movement. Limited blast radius. The incident reports are clear: proper sandboxing and logging would have caught or prevented this entirely. We’re talking observable control flows, not abstract “safety metrics.”

Here’s the catch: write rules for today’s AI and they’re obsolete tomorrow. Anchor them to established security protocols instead, and they last. But that flexibility has a failure mode without mandated third-party audits and public reporting, “proprietary secrecy” becomes a shield for unsafe practices.

EFF’s bottom line: precision and practicality. Don’t strangle innovation. Do demand accountability.

The hard question teams face now: how do you define and enforce minimum safety for high-risk tasks without hardening standards that choke progress? Good read!

[Read More]

AI security certification cost: Fees, training and exam expenses

Categories

Tags security-and-privacy ai-and-machine-learning leadership-and-career

For engineers and security analysts, the sticker price of an AI security certification is only the beginning. Understanding the operational trade-offs between training formats, lab access, and renewal requirements is critical for budgeting and career planning. By sisa.ai.

When evaluating AI security certifications, practitioners often fixate on the advertised course fee, missing the operational realities that drive total cost of ownership. For instance, SISA’s CSPAI certification lists a $250 fee for the exam and digital credential, but this excludes instructor-led training and practical labs. For a working engineer, the real investment lies in time and infrastructure. Self-paced online modules offer flexibility but lack the guided discussion needed to troubleshoot complex adversarial attack scenarios or model manipulation techniques. Conversely, instructor-led sessions provide direct interaction but demand rigid scheduling and higher upfront costs.

The article reads about:

  • What Is an AI Security Certification?
  • Factors That Influence AI Security Certification Cost
  • Breakdown of AI Security Certification Expenses
  • What Skills Do AI Security Certifications Cover?
  • SISA CSPAI Certification Cost and Training Details
  • Tips for Reducing AI Security Certification Costs
  • Conclusion: Choosing the Right AI Security Certification

The technical depth of the curriculum also dictates the return on investment. Programs covering only theoretical risk assessment may fail to prepare you for hands-on tasks like identifying prompt injection vulnerabilities or securing agentic AI workflows. If your role involves penetration testing or application security, prioritize certifications that include hands-on labs. These resources are essential for understanding how AI-specific threats, such as data poisoning, manifest in production environments. Without practical exposure, the certification may validate knowledge but not competency. Good read!

[Read More]

The browser is now an AI runtime: Security risks in Chrome's on-device models

Categories

Tags security-and-privacy ai-and-machine-learning architecture-and-apis devops-and-ci-cd

Google’s integration of Gemini Nano into Chrome creates an unmonitored AI runtime accessible to any website, introducing prompt injection and parasitic compute risks that bypass traditional cloud security controls. By Kirill Gelfand , Vladimir Kropotov , Fyodor Yarochkin , David Tulis.

Engineering leaders must now treat every managed Chrome desktop as an exposed AI runtime. Google’s recent deployment of the 4.27 GB Gemini Nano model to qualifying installations fundamentally alters the threat landscape. Unlike cloud-hosted APIs, this local model lacks authentication tokens, audit logs, and rate limits. Once downloaded, any HTTPS site can invoke it via JavaScript without user consent or visible indicators. This design inversion removes the privilege boundaries that typically protect enterprise data.

We demonstrated successful prompt injection of Chrome’s built-in AI workflows: We showed how text on a webpage, when processed by Chrome’s Summarizer and Writer APIs, and Chrome’s former on-device Scam Detector (since replaced by a cloud model in Chrome 156), can redefine tasks and change the intended behavior of the local models. A core problem is that trusted instructions and untrusted content ultimately have to be interpreted by the same language model.

Source: https://www.trendaisecurity.com/en/resources-insights/deep-research/the-browser-is-now-an-ai-runtime-security-risks-in-chromes-on-device-models

The immediate technical risk is prompt injection. Because system prompts and webpage content share the same context window without enforced authority, malicious scripts can manipulate AI features like Summarizer or Writing Assistance. TrendAI Research demonstrated that plausible-sounding payloads could bypass scam detection mechanisms, flipping classification fields that feed server-side verdicts. While Chrome 156 moves scam detection to the cloud, the underlying architectural vulnerability remains for other on-device features.

Beyond data integrity, the model enables parasitic computing. Websites can silently use user hardware for inference, creating economic incentives for abuse similar to cryptomining. With throughput reaching 30 tokens per second on mid-range devices, the cost savings for attackers are significant. However, unlike cryptomining, browsers currently lack throttling or blocking mechanisms for this specific vector.

For CISOs, the challenge is visibility. Current enterprise policies cannot distinguish between legitimate user interaction and malicious script-driven inference. Developers must implement strict input sanitization, treating model output as untrusted data to prevent XSS and injection attacks. Application-level rate limiting is essential, as the browser provides no per-origin controls. Until Google enforces privilege boundaries and ships granular enterprise controls, organizations must assume that any visited website can leverage local AI resources without oversight. Good read!

[Read More]

ThisBash Escape: Claude Dispatch flaw enables browser extensions RCE on the OS

Categories

Tags security-and-privacy architecture-and-apis ai-and-machine-learning software-engineering

A flaw in Claude Dispatch revealed how authenticated web sessions can drive local OS agents, turning low-privilege browser access into high-privilege code execution. By Gal Weizman.

This architectural pattern extends beyond the feature examined here and appears in other AI assistant capabilities. Claude Code Remote Control and Claude Cowork sessions allow extensions to perform the very same attack. We will explore its broader security implications in an upcoming follow-up blog.

Source: https://forever.security/blog/thisbash-claude-dispatch-browser-extension-rce

The core architectural tension lies in the trust boundary between authenticated web sessions and local execution environments. Claude Dispatch allowed browser extensions to control Claude Desktop by leveraging ambient cookies from a logged-in claude.ai session. This design conflates identity verification with command authorization, assuming that possession of a valid session token implies consent for local OS actions. Consequently, a malicious extension on a personal device could issue commands to an agent running on a corporate endpoint, effectively bridging isolated environments.

The primary trade-off is between seamless cross-device usability and strict authorization boundaries. By allowing the web interface to drive local agents without explicit, out-of-band confirmation, the system prioritizes convenience over isolation. This creates a critical failure mode: prompt forcing. Attackers can automate interactions to bypass guardrails, using social engineering within the agent’s context to justify malicious commands. The vulnerability persists beyond Dispatch, as similar architectures in Claude Code Remote Control and Cowork sessions rely on the same flawed trust model. Teams must resolve whether an authenticated session constitutes sufficient evidence of user intent for high-privilege operations, or if explicit, isolated approval mechanisms are required to prevent browser-based vectors from compromising endpoint integrity. Interesting read!

[Read More]

Agentic development on Android: What engineering leaders should decide next

Categories

Tags ai-and-machine-learning architecture-and-apis backend-development software-engineering

Google’s Android Dev Summit announcements signal a shift toward agent-assisted mobile development. For engineering leaders, the real question is not whether to adopt agentic tooling but how to govern it while teams retain ownership of code, testing, and risk. By Nacho Carrión.

The decision Google’s latest Android tooling forces on engineering teams is not whether to let AI agents write code, but how to keep developers accountable for what those agents produce. At Android Dev Summit, Google framed the shift as moving from building features quickly to owning, reviewing, and testing agent output. That reframing is the crux for leaders: velocity is no longer the bottleneck, trust is.

The concrete changes are substantial. Android Studio now lets teams choose preferred coding agents, including Claude, Codex, and Antigravity, while keeping them inside the IDE rather than forcing a switch to CLIs. Android CLI extends agent access to emulators, remote device testing via Firebase, and profiling. New Android SKILLS guide agents through modern practices like XML-to-Compose migrations and AGP upgrades, aiming to raise code quality. On the product side, AppFunctions and the A2UI Compose library let apps expose functionality and render native interfaces for agents, while Journeys introduce natural-language, non-deterministic testing.

Near-term, these tools reduce friction and can accelerate delivery. Longer-term, Touchlab suggests AI-driven tests could eventually replace Espresso and UI Automator, and that agentic exposure could reshape how apps interact with users. But the governance tension is real: teams must still review generated code, adapt test suites to non-deterministic behavior, and manage dependencies on Google’s platform direction.

For leaders, the threshold is clear. Before adopting agentic workflows, decide how you will verify agent output, who owns quality, and how much you lean on Google’s evolving APIs versus portable approaches.

[Read More]

The future of browser-based security: Leveraging browser data for proactive defense

Categories

Tags security-and-privacy cloud-and-infrastructure software-engineering

This blog post argues the browser should sit at the center of enterprise security. The framing is strong; the evidence is largely promotional and the causal claims run ahead of what the source supports. By Niamh Cunningham.

Author opens with a defensible premise: the browser has become the primary workspace for knowledge workers, and with it, the primary attack surface. Citing Omdia, she notes workers spend over 56% of their day there and that 92% of organizations fear data leakage through shadow AI. These figures anchor the argument well, and the core claim—that legacy EDR and perimeter firewalls are blind to in-browser interaction—is a genuine gap, not a straw man. Extensions can read financial data, session hijacking and living-off-the-land tactics thrive outside endpoint visibility, and agentic workflows create vectors legacy stacks simply cannot see.

The article man focus is on:

  • The browser is now the primary enterprise workspace and attack surface.
  • Legacy security stacks cannot observe in-browser or agentic interactions.
  • Chrome Enterprise Premium captures point-of-interaction telemetry.
  • Mandiant cases illustrate plausible detection scenarios.
  • The argument is strong on framing, weak on independent evidence.

The proposed remedy, Chrome Enterprise Premium, is presented as a high-fidelity telemetry engine capturing signals at the point of interaction. Its capabilities—real-time network signals, extension telemetry, GenAI/SaaS governance, and an evidence locker for forensics—are coherent and internally consistent. The Mandiant case studies add texture: a newly registered domain flagging an RMM executable, URL risk evaluation disrupting phishing mid-navigation, and threat-intelligence integration containing a malicious ad click. These read as plausible, specific, and useful.

Yet the piece collapses demonstration and suggestion. It shows what telemetry can capture but never independently verifies detection accuracy, false-positive rates, or how these signals compare to competing approaches. The Mandiant examples are presented as proof rather than illustration. The strongest claim—that Google’s billions of protected devices confer unique defensive visibility—is an appeal to scale, not a technical argument. The piece is ultimately marketing dressed as analysis, and readers should treat its confidence as aspirational rather than measured. Nice one!

[Read More]