[email protected]

Vibe coding security audit

AI tools produce a running application in days. Whether sign-in, access rights and secrets hold is shown by a check in the code and on the running system.

Reviews
Cloud Wolke HerausforderungServer NachhaltigkeitIT Beratung Service Consulting SoforthilfeTimo Wevelsiep Robin ZinsExperten für Innovation Migration AWSHetzner Hosting zuverlässig

Customers from mid-sized business, industry and the public sector, in Germany and internationally

  • Stadtwerke Brühl
  • DGHO e.V.
  • solarwerkstatt berlin
  • Krüger Dirndl
  • ABCO Water Systems
  • Golem.de
  • EVADXB
  • nextGYM
  • AInergy
  • ml&s
  • Odiseo Solutions
  • Annota
  • ARGE
  • SweetConnect GmbH
  • Aphy AG
  • CORGOS
  • Rekorder
  • SolidProof
  • Yonju
  • Keymate
  • Paritel
  • Mr. Clipart
  • Millenium
  • Negosh
  • Führerscheinmacher
  • BTI
  • Deutsche Gesellschaft für Datenschutz
Read client reviews

Audit focus

What a vibe coding security audit checks

By vibe coding we mean applications built mostly by prompt: an AI tool produces the interface, routes and data access. In their joint recommendation, BSI and ANSSI state that AI coding assistants are no substitute for experienced developers and that generated code should generally be reviewed and understood by the developers. A vibe coding security audit catches up on that review, whatever the tool. It reads code, configuration and pipeline and starts with access control, which ranks first in the OWASP Top 10:2025.

  • Sign-in and sessions: routes that answer without sign-in
  • Access rights: other users' records, other tenants, elevated rights
  • Secrets in the frontend, the repository and the configuration
  • Dependencies with known vulnerabilities and whether they are reachable

Vibe coding in detail

Reviewing code produced by prompt: what an audit looks at

The checkpoints follow neutral sources: the OWASP Top 10:2025 and ASVS 5.0.0 for application security, CWE to classify individual weaknesses, the recommendation of BSI and ANSSI on AI coding assistants and practices PW.7 and PW.8 of NIST SP 800-218 (state of the sources: November 2026). Which tool produced the code does not change these points, it only changes where we look for them.

01

Access, input and sign-in

  • Access per record: can account A read or change the data of account B by changing an ID? (OWASP A01:2025, CWE-639, ASVS V8.2.2)
  • Function rights and tenants: admin routes, role checks and tenant boundaries that the server enforces instead of the frontend (ASVS V8.2.1, V8.3.1, V8.4.1)
  • Input: parameterized queries instead of concatenated SQL strings, validation in server code and protection against cross-site scripting (OWASP A05:2025, CWE-89, CWE-79, ASVS V2.2.2)
  • Sign-in: routes and functions that answer without sign-in although they retrieve or change data (OWASP A07:2025 with CWE-306, A01:2025 with CWE-862)
According to OWASP, access control is effective only in trusted server-side code, not in the frontend. Whether every route checks the owner of the record is shown only by reviewing each route.

02

Secrets, dependencies and configuration

  • Secrets in source code, build artifacts, the frontend and the git history (ASVS V13.3.1, CWE-798)
  • Package names in the manifest: an AI assistant can recommend packages that do not exist, and attackers register packages under that name. We check existence, age, spread and maintenance (BSI and ANSSI, section 3.4.1)
  • Known vulnerabilities, unmaintained packages and transitive dependencies, plus an inventory of the libraries in use (OWASP A03:2025, ASVS V15.1.2, V15.2.1)
  • Configuration in production: debug and test functionality, default accounts and stack traces in error messages (OWASP A02:2025, ASVS V15.2.3)
The supply chain is a category of its own in the OWASP Top 10:2025 (A03), and the ASVS requires that secrets are not included in source code or build artifacts.

03

Tests, pipeline and traceability

  • Tests: are there automatic tests for access rules, sign-in and input, or do they only cover the interface? (OWASP A01:2025, NIST PW.8)
  • Pipeline: what runs automatically on every commit, such as build, tests, dependency checks and static analysis with human review, and what only works locally? (NIST PW.7.2)
  • Release: can one person write code and take it to production without a check by a second person? Plus branch protection and MFA on the repository (OWASP A03:2025)
  • Traceability: which parts are AI-generated, with which tools? BSI and ANSSI consider flagging and documentation helpful for security testing
Scope boundary and notes
BSI and ANSSI name automatic function tests, additional code reviews by security teams and flagging AI-generated code blocks as measures. NIST lists code review and testing as practices of their own (SP 800-218: PW.7, PW.8).

Audit levels

Three audit levels, bookable separately

The audit says what has to be fixed before launch. The pentest proves what can be exploited. Continuous review accompanies changes during operation within the agreed scope.

01

Production Readiness Audit

  • Code, configuration, data access and operational readiness
  • Split: fix before launch or later
  • Action plan in order of priority
from €1,490 excl. VAT

02

Pentest

  • Attack on a test instance, with insight into the source code
  • Confirmed findings with proof, every finding with a status
from €1,000

03

AI Code Review

  • Review of changes during operation, within the agreed scope
  • You keep developing with AI tools
  • Fixed monthly price
from €990 excl. VAT / month

Process

From handover to operations

You can keep developing the application yourself with AI. We audit, fix on request and take over operations.

  1. 01

    Handover

    Repository, test instance and test accounts per role. We verify that the application belongs to you.

  2. 02

    Audit

    Audit of code and operations, on request a pentest against the test instance. Your production system stays untouched.

  3. 03

    Report

    Findings with proof, severity and remediation, plus a clear order.

  4. 04

    Fix and operate

    We fix the findings in the code and take over hosting and operations if you wish.

Frequently asked questions about auditing AI-generated apps

Answers to the most important questions

Reviews & projects

Software projects with reliable outcomes

Proof for modernization, API extension, architecture, deployment and ongoing operations.

Networking & Provisioning

WZ-IT moved our studio infrastructure from decentralised individual devices to a central platform: every site is securely connected via VPN, new devices are onboarded automatically and an entire site is provisioned from a template, without manual steps on location. What impressed me most is the breadth and depth of their knowledge: Timo and Robin are not a typical IT provider who sets up a server and leaves. The two of them think their way into highly complex infrastructure and software topics, work through every requirement we put in front of them, and build networking, provisioning and operations so that everything fits together in the end. WZ-IT is an excellent partner for complex software, network and architecture projects.
Steve KirchnerManaging Director, nextGYM GmbH
View project

International

Built in Germany's Ruhr Valley. Running worldwide.

WZ-IT designs, develops and operates infrastructure and software for clients in Germany and internationally. We deliver projects remotely and continue supporting them in ongoing operations after go-live.

Selected projects

Read client reviews

Enquiry

Have your AI-generated app audited

Describe the application, the tool and the current state. You speak directly with the people who are technically responsible.

  • You speak directly with Timo and Robin, who are technically responsible
  • A professional assessment of your situation
  • Concrete next steps for infrastructure, software or AI

The conversation is free and non-binding.

WZ-IT's advice on our Azure migration was technically sound and completely non-binding right from the intro call - we took away a great deal.
Jakob ÖschlbergerInno7 GmbH
Timo and Robin, founders of WZ-IT

What should happen next?

Choose the appropriate starting point for the current product stage.

We usually respond within one business day. Please do not send access credentials yet.

WZ-IT's advice on our Azure migration was technically sound and completely non-binding right from the intro call - we took away a great deal.
Jakob ÖschlbergerInno7 GmbH