Find the weak spots first.
I test websites, apps and AI assistants the way someone would try to misuse them, then help you close what I find. Only with your say-so, only on what’s yours, and all of it in writing.
What I look at
- Websites and web appsLogins, forms, payments and customer areas: the places people try to get in.
- APIs and the systems behind themWhat an app, a partner or a stranger can ask your systems for, and whether they should get an answer.
- AI assistants and agentsChatbots and agents tested against hidden instructions, leaks and being talked into things they shouldn’t do.
- Hosting and accountsCloud settings, keys, backups, and who can get at what.
- The code itselfA careful read of how it’s built, and of the packages it leans on.
Testing the AI.
More businesses are putting AI in front of customers and handing it their inbox, their documents and their tools. That’s useful. It’s also a new way in, and it deserves the same testing as the login page.
I test an assistant the way someone would try to turn it, then narrow what it can reach, so a bad answer can’t become a bad action. A person stays in charge of anything that matters.
What I try
- Instructions hidden in a document, an email or a web page it reads
- Getting it to give away its instructions, your data or another customer’s
- Actions it can take without a person agreeing first
- What it does when it’s wrong, and who notices
Keeping it shut
Finding a hole is half the job. The other half is the dull stuff that matters most: sensible access, keys kept out of the code, updates that actually happen, backups that actually restore, and logs that tell you when something’s off. I’ll set it up and, if you like, keep an eye on it.
The ground rules
- Nothing is tested until we’ve agreed in writing what’s in scope.
- Only systems you own, or have permission to have tested.
- What I find comes to you first, in plain English: how bad it is and what to do about it.
- I can fix it as well, then test again to check the fix held.
- The details of a weakness stay between us.
Things people ask about security
Is this a penetration test?
It covers the same ground: someone trying to get in, with your permission, and a written report of what they found. If a contract or an insurer needs a test from a certified firm, tell me and I’ll say straight away whether this fits.
Can you test an AI assistant someone else built for us?
Yes, as long as it’s yours to have tested. If it runs on another company’s platform, their rules on testing apply too, and I’ll check them before starting.
Something’s wrong right now. Can you help?
Use the form and say it’s happening now. Leave out the details of the weakness, passwords and keys: I’ll reply with a safer way to share them.
What does it cost?
That depends on how much there is to look at. The form asks about budget, and I’ll tell you what’s worth testing first.
Want someone to try the door?
Tell me what you’ve got and what worries you. You don’t need the technical names for any of it.
I read every enquiry myself and reply in writing, usually within a working day.