Tag

#incident-response

Tagged “incident-response”

12 articles

Google Cloud publishes a six-phase playbook for its own outages

Google Cloud has documented a five-step Verify to Review loop, plus a Prepare phase, for how customers should respond when its own services fall over. The guidance tells you which of its consoles to check first.

Sep 17, 2026 · Maya Okonkwo Incident response

GitHub carves credential revocation into per-token-type actions

GitHub's incident-response tooling now lets enterprise owners and org admins deauthorize or revoke user credentials one token type at a time, in the UI and via API. The blast radius of a bad revoke shrinks, and every action lands in the audit log.

Aug 23, 2026 · Maya Okonkwo Cloud security

Google Cloud spells out its abuse-response ladder: throttle, isolate, suspend

A Google Cloud security-team post consolidates how the platform reacts when a tenant workload starts leaking credentials, mining crypto, or burning a stolen API key. For pipeline owners the operational read is the escalation path, and how easily a shared project can end up on it.

Aug 8, 2026 · Maya Okonkwo Incident response

AWS DevOps Agent talks to ServiceNow over MCP, reads incidents and writes findings back

AWS published a walkthrough showing its DevOps Agent connecting to ServiceNow as an MCP client and using the ServiceNow MCP Server to pull incident, CMDB and change context, then writing correlated analysis back into the incident record. The same wire lets the agent open change requests through ServiceNow's Action Fabric under OAuth 2.0.

Aug 7, 2026 · Maya Okonkwo Incident response

GitHub pauses the Kimi K3 rollout in Copilot while it works a GitHub Actions incident

GitHub says the general-availability rollout of Kimi K3 in Copilot is temporarily paused while it mitigates an incident with GitHub Actions, per an editor's note added to the August 6 changelog. Pricing has been published; the resume time has not.

Aug 7, 2026 · Maya Okonkwo Incident response

Building your own AI SRE moves the toil; it does not remove it

Chronosphere leaders argued in The New Stack that engineering teams should build their own AI SRE to map systems, investigate incidents and support reliable delivery at scale. The operational read is narrower: an in-house AI SRE is a second production system with its own on-call, its own change-management story and its own place in the audit trail.

Aug 2, 2026 · Maya Okonkwo Security & supply chain

SP Page Builder ships a one-file controller patch in 6.6.2, and the locked support thread is a reminder that patching isn't cleanup

JoomShaper has published the verbatim fix for a vulnerable controller endpoint in its SP Page Builder Joomla extension as a public GitHub gist, after issuing the same fix bundled in v6.6.2. The thread that hosts the patch is locked, and the comments under it are the real story: agencies reporting client sites already compromised, with the update closing the door behind attackers who walked in last week.

Jun 26, 2026 · Tomás Vega Incident response

GitHub ships a one-click self-revoke for users whose credentials just leaked

An individual GitHub Enterprise member can now wipe every credential they own, personal access tokens, SSH keys, OAuth tokens and SSO authorizations, in a single action from the Settings page. Containment used to be a scavenger hunt across four menus.

Jun 25, 2026 · Tomás Vega Incident response

AWS wires its DevOps Agent into PagerDuty incidents

AWS has paired its DevOps Agent with PagerDuty so that the moment an incident is created, the agent runs a root-cause investigation across AWS telemetry, deployment history and a short list of third-party observability tools, posting its findings back onto the incident record.

Jun 21, 2026 · Maya Okonkwo Incident response

AWS DevOps Agent reaches GA with the Datadog MCP Server in tow

AWS has moved its DevOps Agent from preview to general availability, shipping it alongside the Datadog MCP Server so the agent can correlate monitoring signals with AWS-deployed infrastructure during an incident. The badge change is the smaller story; the bigger one is what SRE teams now have to write down before the agent touches production.

Jun 20, 2026 · Maya Okonkwo Incident response

AWS teaches its DevOps Agent to flip feature flags during incidents

The AWS DevOps Blog details an integration where the AWS DevOps Agent's MCP server talks to LaunchDarkly so an agent can identify and toggle the flags relevant to a live outage instead of paging three teams to do it by hand. The integration removes a real coordination step, and forces every shop to write down which actions an agent is allowed to take unattended.

Jun 20, 2026 · Tomás Vega Incident response

AWS pushes its DevOps Agent's diagnostic reach down to the EKS node via a custom MCP server

AWS has published a pattern for extending its autonomous DevOps Agent into EKS node OS and runtime data through a custom Model Context Protocol server, addressing incidents that live outside the agent's native cluster-control-plane visibility. The post is explicit that the implementation is a proof of concept, not a production replacement for monitoring or log shipping.

Jun 17, 2026 · Maya Okonkwo