Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

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.

Validity-Override API Tutorial: Confirm If a Leaked Secret Is Still Exploitable

GitGuardian's validity-override API lets security and engineering teams tell GitGuardian whether an exposed credential is actually valid, even when automatic checks mark it as Failed to Check. Secrets tied to internal services, private APIs, or systems GitGuardian cannot reach often fall into this category. GitGuardian automatically validates most supported credential types, but when it cannot, teams can now perform their own validation and feed the result back into the platform.

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.

Whos watching your AI A security leader panel on runtime visibility and accountability

AI is making decisions across your environment — calling APIs, accessing data, and taking action. Most organizations know it's happening, but far fewer can see it, let alone stop it. In this panel discussion, security leaders will share what they've learned deploying and governing AI workloads at scale on AWS, and what it takes to close the gap between deployment and accountability.

Why AI Discovery Must Be the First Step in Enterprise AI Security

Every enterprise security leader is being asked the same question by their board: are we secure against AI risk? Most cannot answer it with confidence, and the reason is rarely a lack of tools. It is a lack of visibility. AI has spread through enterprises faster than almost any technology before it. Developers wire large language model APIs into internal tools. Business teams stand up copilots and chat assistants. Data science teams build retrieval pipelines against customer and financial data.

What the OpenClaw Gym Booking Incident Reveals About Agentic and API Security

An Australian man named Andrew asked his personal AI agent, built on the open-source OpenClaw framework and powered by Anthropic’s Claude model, to book him into a popular morning gym class. According to ABC News, the class was full, so the agent started looking for a way around that. It found that the gym’s booking API let bookings be pushed far further into the future than the website’s own interface allowed, a limit that turned out to exist only on the front end.

Choosing an API Discovery Tool? Here's the Unmanaged API Gap Most Vendors Miss

If you’re evaluating API discovery tools right now, you’ve probably already seen a handful of demos that look nearly identical: a clean dashboard, an inventory count, maybe a risk score. What’s harder to see in a 30-minute demo is whether that inventory reflects what’s actually running in production, or just what the vendor’s connectors happened to catch on setup day.

The API Security Gap Behind Recent Supply Chain Breaches

Most coverage of software supply chain attacks focuses on the entry point: the poisoned package, the compromised maintainer account, the malicious commit. That’s the part that makes headlines, but it’s rarely the part that causes the damage. A malicious package sitting on a developer’s machine doesn’t exfiltrate anything by itself.