Release update: wider coverage, and a graph you can walk

There are two major changes in this release: we can find more, and we can give you a better way to understand what we find.

Wider coverage

We have expanded detection across the three scanners already in the platform.

SCA now reaches deeper into dependency trees. SAST identifies more meaningful execution paths while reducing false positives. Secrets detection recognizes a broader range of credential patterns that commonly appear in source code and configuration.

API security is new.

Endpoints, methods, and exposure are now represented as part of the application itself rather than as a separate security report sitting alongside it.

That matters because an API vulnerability does not exist in isolation. It belongs to a service, has a route, may be internet-facing, interacts with code, and can be connected to other findings.

An API finding is therefore evaluated by the same system that evaluates a vulnerable dependency, a hardcoded credential, or a code-level security issue.

Different scanners. One application context.

Graph View

A dashboard is good at answering one question:

What did you find?

But dashboards usually answer that question with a list, and lists flatten context.

The same vulnerability may appear equally important in a table whether it exists inside an internet-facing production service or an isolated internal batch job.

In reality, those two findings may represent very different risks.

Graph View gives you another way to investigate.

Applications, services, endpoints, packages, findings, and the relationships between them are displayed as the connected system they already form inside the knowledge graph.

You can start from a service and explore what it depends on.

You can start from a package and see which services use it.

You can start from a finding and follow its connections to the code, dependency, endpoint, or application around it.

The value is not the graph itself.

The value is understanding where a finding sits, what it is connected to, and what could be affected by it.

That context is often what you need before deciding whether something actually matters.

What this builds on

Sentrasec already correlates findings across scanners, identifies recurring issues, enriches vulnerabilities with application and threat context, prioritizes what should be fixed first, and provides remediation guidance.

That foundation remains the same.

What changes next is how much of the investigation Sentrasec can perform on its own.

Coming next: the Triage Worker

The Triage Worker autonomously investigates security findings.

For every finding, it brings together the evidence already available across the platform:

scanner evidence, application context, dependency relationships, code structure, exposure, reachability, threat intelligence, and the security controls already in place.

It then evaluates three things:

Is the finding valid?

Is it realistically exploitable?

What is its risk in the context of this application?

From that investigation, the Worker produces a recommended disposition while keeping the supporting evidence and reasoning alongside the decision.

But the more important behaviour happens before it makes that decision.

The Worker first asks:

Do I actually know enough to decide?

When the available evidence is sufficient, triage can complete without human intervention.

When it is not, the Worker identifies what information is missing and explains why that missing evidence prevents a reliable conclusion.

It does not manufacture confidence where the evidence does not support it.

That is the difference between automating triage and automating the appearance of triage.

An analyst can inspect the reasoning, challenge the conclusion, and see exactly what additional evidence would be needed to resolve the finding.

This moves Sentrasec from helping teams understand thousands of security findings toward performing a meaningful part of the investigation itself — while keeping the evidence, reasoning, and decisions visible and auditable.

The Triage Worker ships in the next release.