Application Security

How AI-assisted coding changed security risk

Client
Enterprise software company
Service
Application security assessment
Scope
Three development environments
Remediation
DevSecOps roadmap delivered
The challenge

What did the client need?

An enterprise software company had adopted AI-assisted development across several teams, and leadership could not say whether it was making the code less secure. It asked ioSENTRIX to measure the effect in three environments: a mature platform, a moderately mature system and an application built entirely with AI tools.

Engagement details

Client
Enterprise software company
Environments
A mature platform, a moderately mature system and a fully AI-native application
Scope
Pull requests, static analysis, release-stage scanning and CI/CD pipelines
Alignment
ISO/IEC 25010, NIST SSDF and OWASP SAMM
Remediation
DevSecOps roadmap delivered
Delivered by
ioSENTRIX application security team
Our approach

How did ioSENTRIX approach it?

The question was not whether one scan finds a bug, but how risk changed across environments over time. Answering it took analysis at the pull request, at release and in the pipelines, and comparing several tools against each other.

What we found

What did ioSENTRIX find?

AI sped up development, and in the weakest pipelines it sped up vulnerabilities too.

Theme · AI-nativeFinding 1

The AI-native app doubled its vulnerabilities

In the fully AI-native application, complexity and oversized functions surged, duplication rose and maintainability fell. Pull-request vulnerabilities doubled, with high-severity issues rising sharply.

Business impact. Without governance, AI-native development was building technical debt and security exposure at the speed of the AI.

Theme · ToolingFinding 2

No single tool saw everything

Pipelines differed in how they enforced scans, with missing dependency (SCA) coverage and limited container controls. Across the security tools, coverage and severity ratings diverged.

Business impact. Vulnerabilities could pass through one stage unseen, and leadership had no single view of the real risk.

Where AI-assisted development let risk through
Risk path · from code to release
  1. 1AI writes codevelocity rises
  2. 2Gates unevenscans not enforced
  3. 3Tools disagreegaps at release
Outcome: Risk scales (with development speed)
The impact

What changed as a result?

We found that mature teams could adopt AI safely behind strong pull-request gates, that uneven pipelines let AI expose hidden weaknesses, and that in the AI-native application, pull-request vulnerabilities doubled.

3
environments compared, from mature to AI-native
2x
pull-request vulnerabilities in the AI-native app
0
security tools that covered every environment on their own

What changed after the assessment?

What we found in each environment, and what we recommended
EnvironmentWhat we measuredWhat we recommended
Mature platformQuality stable; security findings up modestly, mainly in authentication and authorisation logicAdopt AI behind strong pull-request security gates
Moderately matureSecurity findings up significantly in service and orchestration layers; tools disagreedPipeline fixes and a map of high-risk modules
AI-native appQuality fell; pull-request vulnerabilities doubled; high-severity issues rose sharplyA governance roadmap with layered controls
CI/CD pipelinesUneven scan enforcement, missing SCA coverage, limited container controlsFixes mapped to pipeline stages, repository types and vulnerability classes

✓ Verification: Roadmap delivered; adoption owned by the client.

Key insight

AI did not create the risk. It removed the time teams used to catch it.

Lessons

Lessons for engineering leaders

01

AI speeds up risk too

In the AI-native app, vulnerabilities doubled at the pull request. Mature the SDLC as fast as you adopt AI tools.

Finding 1 · NIST SP 800-218, Secure Software Development Framework (SSDF) Version 1.1
02

Gate at the pull request

The mature team adopted AI safely because its pre-merge gates held. It is the cheapest place to catch AI-written flaws.

Approach
03

Use more than one tool

No single scanner covered every environment, and their severity ratings diverged. Compare tools before trusting one.

Finding 2
Next step

Adopting AI coding tools? See a sample assessment or book a strategy session on measuring their effect on your code.

Service
Application security
Explore the service

Details in this case study are anonymised and generalised. Methods that could harm other products are withheld.

FAQ

Frequently asked questions

What did ioSENTRIX do in this case study?

An enterprise software company had adopted AI-assisted development across several teams, and leadership could not say whether it was making the code less secure. It asked ioSENTRIX to measure the effect in three environments: a mature platform, a moderately mature system and an application built entirely with AI tools.

What was the most serious issue?

The AI-native app doubled its vulnerabilities. Without governance, AI-native development was building technical debt and security exposure at the speed of the AI.

What happened after the engagement?

The client received a DevSecOps roadmap with findings mapped to pipeline stages, repository types and vulnerability classes.

Which ioSENTRIX service does this case study cover?

Application security, delivered by the ioSENTRIX application security team.

Which standards does this align with?

NIST SP 800-218, Secure Software Development Framework (SSDF) Version 1.1. These are cited as alignment guidance, not a compliance claim.

How to get started

Ready to strengthen your security? Fill out our quick form, and a cybersecurity expert will reach out to discuss your needs and next steps.
DecorativeDecorative