This content is an analysis discussing cybersecurity challenges and strategies for small and medium-sized businesses (SMBs). It highlights how SMBs face increasing cyber risks as they grow and adopt more digital technologies, often without proportional increases in IT resources. The analysis emphasizes that cybersecurity should be integrated as a business enabler rather than a mere compliance task. It outlines common internal constraints SMBs face, such as limited incident responders and heavy IT workloads, and advocates for a gradual, proactive approach to evolving cybersecurity posture aligned with business growth. The piece also describes two strategic paths for SMBs: hardening protection levels and expanding coverage with modular security solutions.
This article analyzes how AWS mitigates risks from exposed IAM access keys by automatically attaching the AWSCompromisedKeyQuarantine managed policy to affected IAM users. The policy restricts permissions to limit damage from compromised credentials. The article details the evolution of this managed policy, the integration with GitHub's secret scanning program that detects exposed credentials in public repositories, and the notification and remediation process AWS follows. It also highlights monitoring strategies for security teams to detect quarantine events and respond rapidly.
Microsoft released patches for 18 vulnerabilities affecting Azure cloud and AI-branded products, primarily involving privilege escalation flaws. The vulnerabilities span multiple Azure services and Microsoft 365 Copilot products, with some information disclosure and spoofing issues also addressed. Microsoft rated all vulnerabilities as critical, though CVSS scores vary from medium to high severity. No exploitation in the wild has been reported, and all fixes were implemented server-side, requiring no customer action. Additionally, a Windows privilege escalation vulnerability was patched, with updates required by users. Microsoft continues to see increased vulnerability discovery driven by AI advancements.
Unit 42 researchers identified that AWS AgentCore Harness's default configuration enables a built-in shell tool with root privileges, which can be exploited via prompt injection to exfiltrate plaintext credentials from the AgentCore Identity vault. The shell tool is enabled by default and can execute arbitrary shell commands with root access, posing a risk if allowedTools is not scoped properly. AWS reviewed the finding and classified it as informative under the shared responsibility model, emphasizing customer-side controls such as scoping allowedTools and egress filtering. Mitigation involves restricting allowedTools to only necessary tools, applying least privilege to identity vault service accounts, and monitoring outbound traffic from harness containers. No official patch or fix is indicated; remediation relies on configuration and operational controls.
The Australian Signals Directorate (ASD) is transitioning from the Essential Eight cybersecurity framework to a new outcomes-based Essentials series starting mid-2027, with full retirement of the Essential Eight expected around mid-2028. This shift moves organizations away from periodic, checklist-style compliance assessments toward continuous validation of security posture across enterprise IT, cloud, operational technology (OT), and potentially agentic AI environments. The new framework emphasizes demonstrating ongoing achievement of security outcomes rather than merely implementing specific controls. Compliance with the Essential Eight remains mandatory only for certain Commonwealth entities, while private-sector adoption is voluntary but often expected by insurers and government contractors. The Essentials series introduces chapters tailored to different environments, reflecting their unique security challenges and dynamic nature. Exposure management tools are highlighted as a means to continuously identify and prioritize security exposures and provide real-time evidence of security posture.
Incorrect privilege assignment in Temporary Elevated Access Management (TEAM) for AWS IAM Identity Center solution before version 1.5.1 might allow an authenticated remote user with application-level access to read, approve, modify, or revoke arbitrary access requests, thereby obtaining unintended temporary elevated access to the AWS accounts accessed using the TEAM deployment.
This issue has been addressed in TEAM version 1.5.1 or later. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes.
A mass-scanning campaign targeting internet-exposed Vite development servers is attempting to steal cloud credentials and configurations from AWS and Azure deployments. [...]
This analysis discusses a behavioral clustering model designed to map cloud identity roles from audit logs, enabling continuous threat detection through standard SQL queries. The model uses unsupervised machine learning techniques to categorize cloud identities based on their activity patterns, improving visibility into cloud environments and aiding detection of malicious behavior masked by legitimate permissions or labels. The research focuses on AWS CloudTrail data but is extendable to other cloud and SaaS environments. It highlights the challenge of distinguishing between what identities can do (permissions) and what they actually do (behavior), emphasizing the importance of behavioral context in cloud security detection.
Inclusion of functionality from an untrusted control sphere in the Kiro Powers feature in Amazon Kiro IDE before version 0.8.135 might allow remote unauthenticated actors to obtain sensitive information from a developer workstation. Crafted repository content can cause the agent to modify the workspace settings file, which redirects the Kiro Powers registry request to an actor controlled endpoint and sends workspace data to that endpoint when the Powers panel is opened.
To remediate this issue, users should upgrade to Kiro IDE version 0.8.135 or later. Users who opened a project in an earlier version should also rotate any credentials that were present in that project.
CVE-2026-85228 is an integer overflow vulnerability in the tensor buffer validation component of the Deep Java Library (DJL), an open-source Java framework for deep learning maintained by Amazon. The flaw occurs when a crafted tensor payload declares a shape whose computed byte size exceeds the 32-bit signed integer range, causing the size to wrap and allowing an undersized buffer to pass validation. This leads to out-of-bounds reads during tensor operations. Exploitation could allow a remote, unauthenticated attacker to access adjacent process memory or cause a denial of service. A fix has been released in DJL version 0.37.0. Users are advised to upgrade to this version or later. No workaround other than upgrading is available, but limiting tensor input to trusted sources can reduce risk until patched.
IDScan, an identity verification company, confirmed a data breach involving unauthorized access to customer data stored on its cloud platform. The breach exposed sensitive information including full names and driver's license or other government-issued ID numbers, with reports indicating that scans of over 153 million U.S. and Canadian driver's licenses were compromised. The incident was discovered around September 1, 2026, and IDScan has engaged third-party specialists and law enforcement to investigate. The company is notifying affected individuals and offering free credit monitoring and identity protection services. Multiple lawsuits have been filed against IDScan following the breach. The stolen data was initially advertised on a dark-web platform called Nexus, which has since been taken offline, though the database may still be accessible to threat actors.
Published: 2026-09-09 Reference: GHSA-p7v4-vr35-mj6f Description Severity A security vulnerability GHSA-p7v4-vr35-mj6f (CVE assignment pending) in containerd's CRI implementation allows a container restored from an untrusted checkpoint through the CreateContainer API to bypass the destination security context and execute with elevated privileges. When restoring a container from a checkpoint archive or annotated OCI image, CRIU restores process credentials, Linux capabilities, no_new_privs , and seccomp state directly from checkpoint data rather than enforcing the destination CRI ContainerConfig . An attacker who can run a container with a crafted checkpoint image can execute processes as the root user with full capabilities and no enforced seccomp filters despite restrictive security policies requested by the orchestrator. Additionally, containerd's CRI status reporting reflects the requested configuration rather than the actual restored process state, masking the privilege discrepancy from orchestrators. GKE clusters are not vulnerable by default. GKE node images do not include the criu tool. Implicit container restore is not supported without criu installed on the node. Standard container creation operations in GKE Standard and GKE Autopilot remain unaffected. GKE Autopilot clusters do not support custom runtime configuration and are not impacted. Additionally, Pod snapshots in GKE do not exercise the vulnerable implicit restore codepath. In updated containerd versions (2.3.4 and later, or 2.2.7 and later), implicit restore is disabled by default through the enable_experimental_restore_via_create configuration option. Version 2.4 of containerd will remove this codepath completely in favor of the explicit Pod-level restore API (KEP-5823). Warning: Administrators can manually re-enable the feature in containerd (2.3.4 and later, or 2.2.7 and later) by setting the enable_experimental_restore_via_create configuration option. However, doing so leaves this vulnerability present because containerd cannot enforce destination security policy while it restores the criu process. What should I do? Because GKE does not include the criu binary on default node images, no immediate cluster upgrades or configuration changes are required for default workloads. If you install custom runtime software or node tools on your nodes that include the criu binary, consider taking the following actions as appropriate for your environment: Re-create existing restored containers: Stop, delete, and re-create any running containers that were restored from untrusted checkpoints. Disable experimental restore (containerd 2.3.4 and later, or 2.2.7 and later): If operating nodes with containerd (2.3.4 and later, or 2.2.7 and later) and custom criu installations, ensure the enable_experimental_restore_via_create configuration option remains set to false in your containerd node configuration. Audit containerd logs: If criu is installed, inspect node logs for implicit restore log entries containing search strings such as "Found checkpoint of container" , "Prepared for restore" , or "Restored container successfully" . Monitor deprecation warnings for containerd: Look for the following deprecation warning event: io.containerd.deprecation/cri-create-container-checkpoint-restore . Restrict Pod creation permissions: Ensure Kubernetes RBAC restricts Pod creation permissions ( create pods ) strictly to trusted users and service accounts. Enforce trusted image registries: Ensure that the values for the Pod's image: field reference verified image repositories. Prepare for KEP-5823: Update operational procedures to rely on explicit Pod-level Checkpoint or Restore APIs after they are available in future Kubernetes releases. Medium
Microsoft's September 2026 Patch Tuesday release addresses 973 vulnerabilities across multiple products, including 113 critical issues. Among these, several vulnerabilities have been exploited in the wild, notably CVE-2026-81963 (Windows Update Stack) and CVE-2026-85880 (Windows ALPC), both elevation of privilege flaws with CVSS scores of 7.8. The update also includes multiple remote code execution vulnerabilities with high CVSS scores, such as CVE-2026-69676 (Windows Kerberos) with a score of 8.8 and CVE-2026-69730 (Windows DNS Server) with a score of 9.8. Microsoft highlights some vulnerabilities as more likely to be exploited and others as less likely. The vulnerabilities affect a broad range of Microsoft products including Windows components, Azure services, and Microsoft SQL Server. No explicit patch links are provided in the source, but these vulnerabilities are part of the official monthly security update. The vendor manages remediation through this update.
Tenable is integrating Anthropic's Claude Mythos 5 AI model into its Tenable One Exposure Management Platform. This integration, starting with the new Adversary View feature, aims to enhance security teams' ability to identify complex vulnerability chains by reasoning across scattered low-signal data that traditional rules engines miss. Adversary View uses advanced adversarial reasoning to analyze raw scan data and prioritize defensive actions that disrupt attacker progression. This approach helps defenders see their environments from an attacker's perspective and focus remediation efforts more effectively. The offering is positioned as an AI-powered enhancement to exposure management rather than a vulnerability or exploit.
GPUThor is a new Rowhammer attack technique targeting Nvidia Ampere GPUs with GDDR6 memory, significantly increasing the effectiveness of bit flips in video memory. It exploits a hardware behavior where repeated memory access can corrupt data in neighboring cells, bypassing standard defenses like Target Row Refresh (TRR). The attack can cause double and triple-bit errors, which are not fully corrected by ECC memory, leading to denial of service conditions such as GPU reboots and hardware faults. While arbitrary code execution has not been demonstrated, the attack shows a theoretical potential to compromise industrial GPUs and cloud infrastructure using such accelerators.
Cylake, a cybersecurity startup founded by former Palo Alto Networks executives, has raised $245 million to develop an AI-native cybersecurity platform designed for highly regulated organizations that cannot rely on public cloud infrastructure. The platform aims to operate entirely on-premises or in private cloud environments, providing customers with full control over their data, infrastructure, and security operations. Cylake's solution targets government agencies and enterprises with strict data sovereignty requirements, addressing visibility gaps caused by fragmented security products. The company plans a beta release by the end of 2026 and general availability in 2027.
A Server-Side Request Forgery (SSRF) vulnerability exists in the ONLYOFFICE ownCloud Integration plugin version 9.12. The /apps/onlyoffice/ajax/settings/address endpoint does not sufficiently validate the user-supplied Document Server URL before initiating outbound connections. An authenticated administrator can manipulate the document server parameter to cause the ownCloud server to send arbitrary requests to attacker-controlled destinations, including localhost and internal network hosts. This allows internal network reconnaissance and TCP port scanning based on differences in server responses.
Cisco Talos is tracking a cryptocurrency theft campaign that abuses the Google Visualization API to deliver obfuscated JavaScript from Google Sheets, which victims are socially engineered to inject into their browser sessions. The attack uses a variation of ClickFix social engineering, convincing targets to paste malicious JavaScript into the Chrome address bar or install it via the Tampermonkey extension for persistence. The malicious script acts as a web skimmer, hooking the browser's fetch API to replace cryptocurrency deposit addresses and manipulate clipboard contents, deceiving users with fake bonus interfaces. The campaign targets users on cryptocurrency and hacking forums with a lure about a nonexistent API vulnerability to entice quick financial gain. The actors moved their hosting to Google Docs and Sheets after disruptions on paste sites. While this campaign primarily targets individuals, the techniques used could be adapted for broader supply-chain or web-based attacks.
Exclusive: An exposed Advance Passenger Information System (APIS) database held 220 million passenger and crew records containing names, passport numbers, dates of birth, nationalities, and flight details spanning 2017 to 2026. Researchers accessed the Vietnam-linked system through a cloud-based path using default credentials. [...]
CVE-2026-85786 is a memory-amplification denial of service vulnerability in the Amazon ion-java library. It arises from an incomplete fix for a previous vulnerability (CVE-2026-75936) related to GZIP auto-decompression. The issue allows denial of service via highly compressed data expansion. Versions of ion-java prior to 1.12.1 are affected. The vulnerability has been addressed in ion-java version 1.12.1, and no workarounds are available.