Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

What is an AI Bill of Materials (AI BOM)?

What’s happening under the hood of your AI systems? AI is now a crucial element of modern software applications, and if you don’t have visibility into its components, you’ll be left blind. Similar to a Software Bill of Materials (SBOM), an AI Bill of Materials, AI BOM, or AIBOM has become a crucial framework for documenting and securing this new and complex supply chain. This article is part of a series of articles on Shadow AI.

The Hallucinated Package Attack: Slopsquatting

Imagine a world where, in the middle of programming, your helpful AI assistant tells you to import a package called securehashlib. It sounds real. It looks real. You trust your silicon co-pilot. You run pip install securehashlib. Congratulations. You’ve just opened a backdoor into your software stack—and possibly your company’s infrastructure. The package didn’t exist until yesterday, when an attacker registered it based on a hallucination the AI made last week.

The Complete Guide to SBOM Software Bill of Materials

A Software Bill of Materials (SBOM) is like an ingredient list for software. It provides a detailed inventory of all the components that make up an application, including open source libraries, proprietary code, packages, and containers. Just as food packaging lists ingredients to protect consumers and ensure safety, SBOMs do the same for software by giving visibility into what is inside.

Introducing Mend Forge

Today, we’re thrilled to announce Mend Forge, our new AI native innovation engine and your window into what’s next in application security. At Mend.io, we believe that security innovation shouldn’t happen in a black box. The security landscape is shifting fast, driven by the explosive growth of AI generated code, AI powered applications, and rapidly evolving software supply chains.

What is AI system prompt hardening?

As generative AI tools like ChatGPT, Claude, and others become increasingly integrated into enterprise workflows, a new security imperative has emerged: system prompt hardening. A system prompt is a set of instructions given to an AI model that defines its role, behavior, tone, and constraints for a session. It sets the foundation for how the model responds to user input and remains active throughout the conversation.

Deploying Gen AI Guardrails for Compliance, Security and Trust

AI guardrails are structured safeguards, whether technical, security or ethical, which are designed to guide AI systems so they operate safely, responsibly, and within intended boundaries. Much like highway guardrails that prevent vehicles from veering off course, these measures ensure AI remains aligned with organizational policies, regulations, and ethical values.

Best AI Red Teaming Tools: Top 7 Solutions in 2025

There was a time when “AI red teaming” sounded like a novelty. Now, it’s fast becoming table stakes. If your organization is shipping machine learning or LLM-powered systems into the real world (especially in sensitive domains), you need to know how those systems behave under pressure. That’s where AI red teaming tools come in. These tools help teams stress-test AI the way it will actually be used (and misused).

What Is Application Security Posture Management (ASPM)?

Application security posture management (ASPM) centralizes and automates the monitoring, evaluation, and management of application security across an organization’s software lifecycle. ASPM provides a unified view of the risk posture by aggregating data from various security tools, such as static application security testing (SAST), dynamic application security testing (DAST), software composition analysis (SCA), and runtime protection solutions.

Why Patch Management is Important and How to Get It Right

If you’ve ever been burned by a late-stage security patch—hours before a release, in production, or during a holiday—you know patch management isn’t just an IT checkbox. It’s a make-or-break part of modern software delivery. Yet too often, it’s reactive, fragmented, and bolted on after the fact. This guide breaks down how to make patch management a proactive, automated, and developer-aligned process—without slowing you down.