Curated cybersecurity insights, opinions, emerging technologies, AI security topics, and notable industry discussions.
1292 articles
A Picus case study says an unnamed global retailer replaced its legacy BAS with Picus, continuously tests controls across stores and servers, and routes unblocked IOCs through a SOAR playbook to its EDR for blocking.
Sponsored analysis argues that patching cannot always outpace exploitation and recommends limiting the access of service accounts and AI agents to reduce the impact of a compromised workload.
The article says healthcare organizations should act on HIPAA risk analyses, apply consistent secure configurations, and document progress. It cites OCR settlements tied to missing risk analyses and recommends CIS Benchmarks and assessment tools.
Three AWS security professionals describe day-to-day application security and penetration-testing work, emphasizing communication, code review, foundational practice, careful AI use, and habits for building a security career.
Criminals have used hacked legitimate websites to show fake verification prompts that trick visitors into running malware. The article offers practical steps for safer browsing amid other recent web security problems.
The article explains how AI-assisted fake login pages can steal credentials and MFA codes, while adversary-in-the-middle attacks can capture authenticated sessions. It discusses defensive gaps and promotes Keeper’s phishing protection.
The article outlines five principles for self-hosted SOC platforms: secure deployment, signed and predictable updates, current detection content, clear operational ownership, and transparent releases.
An essay compares infrastructure air-gapping with the failed GovNet plan, arguing isolation cannot stop insider or valid-account threats and can impair operations. It recommends machine identities, least privilege, segmentation, selective isolation and monitoring.
JFrog field CISO Paul Davis advises tracking AI agents and software components across development and production, using approved package sources, prioritizing vulnerabilities with application context, and retaining human review for operationally risky changes.
Enterprise AI can remain fluent while producing unsafe or false outputs, and siloed teams may miss failures spanning data, orchestration, models and hardware. The article outlines four compromise paths and recommends cross-layer ownership and stronger integrity checks.
Kudelski Security’s Nathan Hamiel warns that overreliance on AI could weaken cybersecurity expertise and limit junior professionals’ learning. He recommends using AI where it helps while retaining the skills needed to assess its results.
Researchers described a Warlock intrusion in which attackers disabled security tools across dozens of hosts before deploying ransomware. The article argues for protections that act on-device and remain effective when monitoring fails.
Huntress’s Tragic Quadrant ranks tactics targeting businesses, including RMM abuse, mailbox manipulation and AiTM. Huntress reports RMM abuse in 45% of its Q1 2026 endpoint investigations and explains device-code phishing, ClickFix and AI-platform lures.
Arctic Wolf says its telemetry showed scanning spikes and exploitation attempts around PHP2Shell, using the case to urge asset visibility, exposure management, timely patching and tested response plans as AI compresses attack timelines.
Microsoft reported Storm-1865 used fake Booking.com pages and ClickFix lures to deliver credential-stealing malware to hospitality staff. Cyble's sponsored walkthrough maps its brand-intelligence tools to the campaign and clarifies it did not participate in the response
A beginner’s guide to securing code built with AI agents, covering secrets, first- and third-party code, dependency risks, security questions to ask agents, and common scanning tools.
A sponsored analysis of a federal AI-agent incident guide argues that readiness depends on agent-specific identities, credential inventories and tamper-resistant session logs. It cites the OpenCode exposure and a Hugging Face evaluation incident as examples.
An opinion article recommends 10 lasting software-security practices, including secure-by-design architecture, dependency provenance, continuous code verification, remediation of security debt, and threat modeling AI systems.
Aikido’s guide covers scoping and integrating AI pentests with existing security tools, including staging environments, role-based credentials, optional source-code access, and retesting. Aikido reports white-box tests found 7x more vulnerabilities than grey-box tests.
A beginner’s guide explains how unique salts and slow password-hashing functions protect stored passwords, why fast general-purpose hashes are unsuitable, and how unique passwords and MFA help limit risk.
Picus says PHP2Shell’s lack of a safe day-one exploit left automated pentesting limited to version fingerprinting, while its breach-and-attack simulation tested deployed controls and guided signature fixes; it urges patching PHP and revalidating defenses.
Commentary argues that rapid exploitation and annual supplier reviews leave Caribbean organizations exposed, with risks cascading through shared platforms. It recommends continuous assurance, faster remediation measurement, segmentation, and monitoring federated access.
Wiz describes enriching and deduplicating application-security findings, then correlating code, build, cloud runtime, and network exposure to prioritize exploitable attack paths and manage lower-priority security debt.
Unit 42 explains how OAuth phishing steals tokens after MFA, enabling persistent access, consent abuse and malicious redirects, and recommends admin-controlled consent, clipboard monitoring and redirect-URI audits.
