What a security audit does and does not do
A security audit is first of all a thorough code review with a security focus. We go through the code, the dependencies and the configuration looking for the flaws above. You get a report with every finding, how severe it is and how to fix it. The article on how Voltti runs a security audit with AI describes each step.
A pentest is something else. In a pentest, someone attacks your running app from the outside, the way an attacker would. The two complement each other: an audit finds flaws in the code that a pentest can miss, and a pentest finds problems in the environment that you cannot see in the code. Neither makes an app 100% secure. They do make the risk a lot smaller, and you know where you stand.
Can’t you just have AI check it yourself?
A first pass is definitely possible. Ask your AI tool to check the code for security flaws, and you will often find a few things. Go ahead and do that. But it has limits. The model that wrote the code looks at it with the same blind spots. It also flags things that are not a problem, and misses the flaws you only notice if you know how the app is used. So who decides what is real and what comes first?
In a security audit by Voltti, AI models and our own skills do the broad search. Then a person with 20+ years of experience in web development reviews every finding before it goes into the report. We remove false alarms. We also work with local models, so your code does not have to leave your network. If you want help with the fixes, that is possible, followed by a recheck. How Voltti secures its own Hermes installations is covered separately under security and privacy.
Five things you can check today
You do not have to wait for an audit to reduce the biggest risks. You can do these checks in an afternoon:
Search your code and your repository history for API keys and passwords. If you find one, replace the key itself; just deleting the line is not enough.
Log in with a second test account and change numbers in links and API calls. If you see the first account’s data, a permission check is missing.
Have your package manager check your dependencies, for example with npm audit or pip-audit, and update packages with known vulnerabilities.
Check your database access rules. Can someone read tables without logging in?
Trigger an error in production and look at what the visitor sees. A stack trace or database error does not belong there.
If a developer or agency works with you, point to the OWASP Top 10 as a shared framework. Want to know what you need to arrange yourself when your team works with AI tools and business data? Read the practical safety checklist for AI and business data. And if you want someone to really go through your app, for businesses in Belgium and the Netherlands, we are happy to discuss what an audit would cover for your app.