Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Every organization has a different threat profile. Industry, geography, infrastructure, business operations, and the broader technology ecosystem all influence which adversaries and threats matter most. The challenge is putting threat intelligence to work at scale to identify the greatest threats to each business. The intelligence that security teams rely on is as varied as the threats they face.

AI agents don't just answer questions anymore. They open files, use credentials, run code, install software, and run models locally, all at machine speed. Every one of those actions happens on the operating system. This is where attacks land, and where CrowdStrike Falcon Guardian excels: on the endpoint, at runtime.

The shift from NIST SP 800-171 revision 2 to revision 3 includes a lot of changes, which we've already covered from a bird's-eye view over in this post. One of the biggest changes in Rev 3 is the introduction of ODPs, or Organization-Defined Parameters. These are very important for compliance with CMMC moving forward, but they're still something of a mystery to some security professionals, and are worth explaining. What are they, how do you define them, and how do you use them for compliance?

Short answer: GDPR names pseudonymization as a recommended safeguard, in Article 25 and Article 32, and Recital 28 says pseudonymization reduces risk for data subjects. Redaction deletes the value, so a redacted prompt breaks the model’s ability to reason. Tokenization replaces the value with a consistent token, so the model keeps working. Tokenization is a safeguard, not an exemption. A familiar pattern: a team writes a regex, strips emails from the prompts, and calls it done.

Recent events have once again highlighted the need to quickly answer the question, “Are we exposed?” We now face threats to businesses and governments from vulnerabilities and compromises in three fundamental components used in software development: Curl, PHP, and LiteLLM.

AI agents are moving into production fast. They read email, call tools, query databases, and trigger business processes, often chaining those steps in ways no single team designed. Building them has never been easier. Securing what happens after an agent is manipulated is the hard part. That is the gap Salt and AWS will tackle together on Tuesday, November 10, at 9:00 am PT (12:00 pm ET) in a live session: AWS + Salt: Build Fast, Stay Secure with Agentic AI. Save your seat →

If you’ve followed the news recently, you’ve probably seen reports about newly discovered PHP vulnerabilities. The warning prompted action from governments, website operators and technology providers around the world, with some organisations temporarily taking websites offline while updates were applied. For many business leaders, the immediate reaction was probably: What is PHP, and does this affect me?

Accelerating security solutions for small businesses‍ Tagore offers strategic services to small businesses. A partnership that can scale‍ Tagore prioritized finding a managed compliance partner with an established product, dedicated support team, and rapid release rate. Standing out from competitors‍ Tagore's partnership with Vanta enhances its strategic focus and deepens client value, creating differentiation in a competitive market.

MSPs are used to blocking malicious domains, detecting suspicious IP addresses, and continuously updating their defenses against emerging threats. However, what happens when attackers can shift their infrastructure in near real-time without interrupting the campaign? The ErrTraffic campaign, analyzed by the WatchGuard Threat Lab, provides an example of how malware distribution techniques are evolving.

On October 19, 2026, we learned about eMudhra’s eight shockingly weak keys: where eMudhra was trusted to pick a 115-digit number for their virtual combination lock protecting the Internet, they picked the number 4. Not even four digits, just the number 4. The other seven keys were similarly weak: 56, 66, 115, 155, 156, 230 and 237. The next day, we wrote a blog post on the immediate action we took to mitigate this leak, and what customers needed to do on their end to stay secure.