veridicus.
Security check

Is the app you had built safe to run?

A fixed-price, one-day check of the app, portal or automation you had built with AI tools. You get a written report, ranked by severity, with the fix for each problem.

Price $2,900 fixed
Time One day
You get A ranked written report
Who it is for

Built with AI tools, now running the business.

This is for you if

  • You had an app, portal or automation built with AI tools in the last year, and your business now runs on it.
  • Customers, staff or suppliers sign in to it, or it holds their details.
  • It takes payments, sends messages, or connects to your email or accounting.
  • Nobody has checked it since it went live.

This is probably not for you if

  • You are still at the idea stage. The free workflow audit is the better first step.
  • You need a formal certificate for a tender or an insurer. That is a different kind of test.
  • It is a product you only configure and the vendor runs. The vendor owns that risk.
What gets checked

36 points, in plain words.

Grouped by the question an owner actually asks. Each one is a specific weak spot that shows up in apps built quickly with AI tools, drawn from the OWASP Top 10 and from the method I run on my own software.

Who can get in

Can only the right people sign in, and stay signed in?

  1. 01Password resetResetting a password can't be used to take over someone else's account.
  2. 02Staying signed inSessions are safe, and signing out really signs you out.
  3. 03The secret that proves who you areThe signing secret behind logins isn't guessable or sitting in the code.
  4. 04Default loginsNo admin/admin or leftover test accounts still work.
  5. 05How passwords are storedPasswords are scrambled properly, and weak or leaked ones are turned away.
  6. 06A second step at sign-inOwners and admins can be asked for a code, not just a password.
  7. 07Staff who leaveWhen someone leaves, their access stops straight away, not days later.
  8. 08Sign-up and invite linksStrangers can't walk in through an open sign-up or an old invite link.

What they can see

Can one customer, or a stranger, see what isn't theirs?

  1. 09Someone else's recordChanging a number in the address bar doesn't show another customer's data.
  2. 10Which sites can ask for your dataOnly your own sites can ask your app for data, not any site on the web.
  3. 11Test sites and hidden config filesYour staging copy and .env files aren't open to the public or full of real data.
  4. 12Customers kept apartEach customer's data is walled off from every other customer's.
  5. 13Database rules switched onThe database itself refuses to hand data to people who shouldn't have it.
  6. 14Database shortcuts closedBehind-the-scenes database commands can't be run by anyone on the internet.
  7. 15Admin screens and actionsAdmin actions check who you are on the server, not just hide the button.

What they can change

Can someone feed your app something that makes it do what they want?

  1. 16Code typed into a formA name or search box can't be used to read or wipe your database.
  2. 17Scripts planted on a pageText one person types can't run as a program in another person's browser.
  3. 18Tricked into clickingAnother website can't make a signed-in user's browser act on your app.
  4. 19File uploadsNobody can upload a file that is secretly a program, or one that is huge.
  5. 20File names and pathsA file name can't be bent to reach other files on the server.
  6. 21What your back end acceptsThe server checks every request, whatever the screen lets people do.
  7. 22Prices and payments in the browserPrices and 'paid' status are decided by your server, not the customer's browser.
  8. 23Notifications from other servicesPayment and message alerts are proven genuine, and can't be replayed.
  9. 24Customers steering your AIAn email or form can't talk your AI into ignoring its rules.
  10. 25AI actions that need a personAnything that sends, pays or deletes waits for a human OK.

What leaks

Is anything private sitting where it shouldn't?

  1. 26Server fetching addresses for othersYour app can't be made to fetch internal addresses on a stranger's behalf.
  2. 27LogsLogs don't hold passwords, tokens or customer details, and aren't public.
  3. 28Readable source codeYour readable source isn't published alongside the live site.
  4. 29Keys saved in your codeNo passwords or keys sit in the code or its history.
  5. 30The master key in the browserThe all-powerful database key stays on the server, never in the page.
  6. 31Error messagesWhen something breaks, visitors see a plain message, not your inner workings.

What happens under load

What happens when someone hammers it, or something goes wrong?

  1. 32Rate limitsSign-in, sign-up and costly actions can't be repeated thousands of times.
  2. 33AI spend capsA runaway user or script can't run up your AI bill overnight.
  3. 34BackupsThere is a recent backup, and someone has actually restored from one.
  4. 35Would you know?If someone got in, alerts or logs would tell you, not a customer.
  5. 36Out-of-date partsLibraries are patched, and AI-suggested packages are real, not look-alikes.
What you receive

A report you can act on.

In the report

  • A written report listing everything I found, ranked from critical to low.
  • The fix for each finding, in words you or your developer can act on.
  • A one-page summary for you, with no jargon.
  • A list of what passed, so you know what is already sound.

The terms

Price
$2,900 fixed, agreed in writing before I start. No GST applied.
Time
One day to check, report sent straight after
I need
Read access to the code, a look at the hosting, a test login per user type
I never
Change or break your app, or take your customers’ data

This is a one-day review against the 36-point list, with a fix for each finding. It is not a CREST-accredited penetration test. If the review says a full manual pen test is warranted, I quote that separately.

How it runs

How we work.

01

Book a free call.

We agree what the app does, what it holds and where it runs. I confirm the fixed price in writing before I start.

02

I check it in a day.

I work through the 36 points. I read and test; I do not change or break anything, and I use a test copy where there is one.

03

You get the report.

Ranked by severity, with the fix for each problem. If you want me to make the fixes, that is scoped and priced separately.

Before you ask

A few straight answers.

What is SQL injection, and could it happen to my app?

It is the oldest trick there is. Someone types a line of database code into a box that should only take a name or a search term. If the app pastes that text straight into its own database command, the database obeys it, and the result can be anyone reading every customer's details or wiping the lot. Checking the box in the browser helps your users but does not stop an attacker, who simply skips the browser. The fix that works is on the server: what people type is passed to the database as plain data, never as part of the command. AI tools often write this correctly, but not every time, and one missed spot is enough. That is why every form and search box gets checked.

Will you break my live app?

No. I read and test; I do not run anything destructive. Where there is a test copy I use that. If I want to try something on the live app I ask you first.

What do you need from me?

Read access to the code, a look at how the app is hosted and set up, and a test login for each type of user. I do not need your real passwords or your customers' data, and I keep what I see confidential.

Is this a penetration test or a certificate?

No. It is a structured one-day review against 36 known weak spots, by someone who runs the same method on his own software, and it is not a CREST-accredited penetration test. It tells you what I found and what to fix. It does not certify your app as secure, and no check can promise that. If the review says a full manual pen test is warranted, I quote that separately.

Do you fix what you find?

The report gives you the fix for each item. If you want me to make them, I scope and price that separately before anything starts, the same as any build.

Does it matter which tool built it?

No. An AI tool, an agency or a freelancer: I check what is running, not who wrote it.

Next step

Find out before someone else does.

Book a free call and we will agree what is in scope. Prefer a message? The form on the booking page reaches me directly, and I reply within one business day.

Email · hello@veridicus.com.au
Brisbane