Salt Safety has unveiled a collection of recent clever evaluation options designed to unravel the crucial “Context Disaster” in utility safety. Headlined by Salt AI API Summaries, the discharge introduces a GenAI-powered engine that explains the aim, knowledge circulation and danger of any API in plain language. Alongside a totally redesigned Deep Context Aspect Drawer, these updates empower safety analysts to triage dangers immediately with out deciphering advanced code or consulting documentation. This can be a step in the best route relating to bridging the talents and understanding hole between safety groups and builders.
As API sprawl accelerates, safety groups are sometimes left managing hundreds of endpoints they didn’t construct and don’t perceive. Conventional instruments and CNAPPs (Cloud Native Utility Safety Platforms) present lists of property, IP addresses, URLs, and cloud tags, however fail to elucidate the API’s enterprise perform.
Salt’s new AI API Summaries goal to shut this hole. By analysing API site visitors, construction and payloads, Salt’s GenAI engine robotically generates a concise, natural-language abstract for each endpoint. It does this by way of prompt comprehension of questions, breaking down advanced language for junior analysts and non-developers and accelerating triage by discount of false positives.
Nick Rago, VP of Product Technique at Salt Safety, mentioned: “Safety groups are drowning in technical knowledge however ravenous for context. A CNAPP can inform you that an API exists on a selected server. However solely Salt can inform you, in plain English, that ‘This API processes unencrypted bank card purposes for the EMEA area.’ That distinction is the important thing to efficient governance.”
Complementing the AI Summaries is a reimagined Deep Context Aspect Drawer. Whereas generalist safety instruments deal with APIs as static desk rows, Salt’s new interface treats them as advanced software program entities, organizing deep telemetry right into a Area-Pushed Design. It does this in three key methods: construction and knowledge tab, attacker intelligence and posture proof.
This stage of granularity proves that “checking the field” with a cloud configuration scanner is inadequate for securing the API layer. Salt gives the behavioural depth required to safe the logic, not simply the infrastructure.
