Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

7 Best Practices for Implementing API Governance

API governance is the framework of policies, standards, and controls an organization applies to how APIs are designed, exposed, accessed, and monitored. It answers four questions for every API in your environment: who owns it, what data it touches, who can call it, and whether its behavior stays within approved limits.

Secure What Agents Do, Not Just What They Say

Salt Security and CrowdStrike give joint customers visibility across the full agentic path, from the model to the system where the action lands An employee at a bank asks an AI assistant a routine question. How much money is in my savings account? The assistant answers correctly. The prompt was legitimate. The response was accurate. A model-layer security control inspects both and finds nothing wrong, because nothing is wrong with either. Now look at what happened in between.

Security by Design: Incorporating Cybersecurity into Early-Stage Software

In today's hyper-connected digital economy, launching a new software application requires balancing speed, innovation, and technological resilience. Early-stage founders and product teams naturally focus on building compelling user interfaces, refining core value propositions, and validating market demand as quickly as possible. However, treating information security as an afterthought or a secondary milestone to address post-launch creates massive operational vulnerabilities that bad actors can easily exploit.

Why Your WAF Isn't Enough: Runtime Protection for AI Agents and APIs

Most security leaders believe their API attack surface is covered. A Web Application Firewall (WAF) sits in front of the application. An API gateway manages authentication, rate limiting, and schema validation. Some teams add a bot management layer on top. This looks like defense in depth. In practice, it repeats the same layer, the perimeter, multiple times. Most API breaches do not start with a WAF bypass.

Zombie APIs Are Costing You More Than You Think: A Risk Quantification Guide

Zombie APIs are API versions or endpoints that were once known and documented, but were never properly retired. A team ships v2 of an API, tells everyone to migrate, and assumes v1 is dead. In reality, v1 is still running on a server somewhere, still accepting requests, and still connected to production data. This is different from unmanaged APIs, which were never documented in the first place. Zombie APIs were documented once.

The Hidden Cost of BOLA/BFLA Vulnerabilities: A CISO's Guide to Quantifying Risk

Every CISO managing an API estate has heard of Broken Object Level Authorization (BOLA) and Broken Function Level Authorization (BFLA). What is harder to pin down is what these vulnerabilities actually cost the business when they go unaddressed. Board members and finance teams want numbers, not acronyms, and that gap between technical risk and financial risk is where security budgets get lost. BOLA has held the number one spot in the OWASP API Security Top 10 since the list was created in 2019.

Secure AI Written Code Before It Ships: Salt Code

AI coding assistants are transforming how enterprise software gets built. Developers at every level are prompting their way to production-ready APIs, MCP integrations, and agentic workflows faster than any security team can review them. The problem is that none of those assistants knows your internal security standards, regulatory obligations, or risk tolerance. The result is insecure patterns shipping unnoticed, vulnerabilities discovered downstream when fixes are costly, and compliance becoming a guessing game on every commit.

What is Security Posture Management and Why is it Important?

Modern organizations don't operate from a single server room anymore. Today's enterprise environment spans dozens of cloud services, SaaS applications, APIs, AI agents, and non-human identities, all of which are continuously changing. A quarterly security audit is no longer a safety net, but now considered a gap.

7 API Security Requirements for Payment Transactions

Every payment flow your organization runs, from card authorization to ACH transfers to embedded lending to open banking consent, is now an API call. That’s good for velocity. It’s also why payment APIs sit at the top of the attack surface for financial services and enterprise SaaS platforms handling money movement.