# Continuous code audit CI/CD SAST DAST AI | NextAI case

Canonical source · https://nextai.pro/en/case-studies/auditoria-inteligente-codigo-incibe

Proprietary continuous auditing technology that analyses code, dependencies and configurations in CI/CD pipelines with contextual AI-based SAST and DAST. 92 % of critical vulnerabilities detected.

## INTELLIGENT CODE AUDITING WITH INCIBE BACKING

Client: Startup incubated in the NextAI ecosystem, with support from INCIBE

## THE STARTING POINT

Decentralised code management and accelerated cloud growth raised the risk of critical vulnerabilities.

## WHAT WE BUILT

We built proprietary continuous auditing technology that analyses code, dependencies and configurations in CI/CD pipelines with contextual AI-based SAST and DAST, prioritising by criticality, with technical and methodological support from the National Cybersecurity Institute.

- Continuous auditing in CI/CD pipelines

- Contextual AI-based SAST and DAST

- Vulnerability prioritisation by criticality

- Dependency and configuration analysis

- Technical and methodological support from INCIBE

- GitHub Actions integration

ANATOMY OF THE SOLUTION

## FROM TECHNICAL FINDING TO PRIORITISED REVIEW

From input to outcome: explore the four parts of the journey.

- 01 Code

- 02 Analysis

- 03 Priority

- 04 Review

Project repositories, dependencies and configurations.

Explanatory diagram based on the described solution. It simplifies the journey; it is not a deployed infrastructure diagram or a live monitor.

READING THE PROJECT

## THE THINKING BEHIND THE TECHNOLOGY

### WHAT REALLY NEEDED SOLVING

Growing code, dependency and configuration volumes make consistent review difficult. This case places analysis within CI/CD so security becomes part of development. The aim is not more alerts but better context for prioritising review.

### WHY THIS STRUCTURE MATTERS

SAST and DAST cover different analytical perspectives. Including dependencies, configuration and severity helps interpret a finding within the system. GitHub Actions integration puts that information where software is built and delivered.

CONNECTION TO TODAY’S OFFERING

## SUPERAGENTS

Execution, with clear boundaries

CURRENT RELEVANCE AND POSSIBLE EVOLUTION

This is aligned with Superagents through a specialist role within a process. An extension could prepare fixes and tests; accepting changes or deploying to production should retain explicit review controls.

This connects the case experience to our current services. Proposed extensions are not presented as features already delivered.

METHOD AND SCOPE

## HOW TO READ THE OUTCOME

### WHAT TO MEASURE

Specify the reference vulnerability set, false positives and negatives, severity and review time. Detection and remediation are different outcomes.

### WHAT NOT TO INFER

The INCIBE support described in the case should not be read as universal product certification or a guarantee that vulnerabilities are absent.

Basis of this analysis: the description, capabilities and stack published in this case. No new measurements are added and no independent audit of its results is implied.

### HOW IT FITS WITH THE REST

## DOES YOUR COMPANY NEED THIS?

One hour, no sales deck: we analyse your operation and tell you what can be built, where to start and what is not worth touching yet.

## Ready to apply this to your business?

Eva helps you choose. Our team scopes your project.
