Worknano

A security checklist before you ship an AI-built internal tool

Updated 2026-11-15

This AI app security checklist is for the moment before your team starts using an internal tool that an AI built. It asks four things: who can get in, what each person can see, where passwords are kept and who looks after the tool. You can do most checks by simply trying things out, without reading any program code.

Why a checklist at all

When you rent a new office, you walk round once before moving in. Do the doors lock? Who has a key? Where is the fuse box? A tool built by AI deserves the same walk. It can look finished on screen and still have an open door.

How to use the list

Go through it with two people: the one who built the tool and one who did not. The second person does the trying. If a check in the first three groups fails, wait with the launch until it is fixed.

1. Getting in

2. Seeing and changing

3. Passwords and connections

4. Looking after it

What the list cannot tell you

These checks find the common, visible gaps. They do not replace a check by a developer. If the tool holds customer data, takes payments or can be reached by people outside the company, have a developer look at it before launch.

How the tool was built also matters. If the AI wrote a separate program, every check is yours. If the tool was built inside a platform that already provides login, access rules and storage, the first groups become settings you only need to confirm.

After launch

How Worknano handles this

Tools built as modules in Worknano start with groups 1 to 3 in place. Access is set once through roles. Rules decide which records a person sees, and which fields, so sensitive data such as salaries stays hidden. A new custom module gets the same access rules automatically. Role changes, new access rights and exports are logged with who did what and when. Shared logins and API keys go into Secrets, an encrypted vault. There, roles decide who sees an entry, people can request access, and you can see who viewed or copied it.

Create a free workspace and build your next internal tool where access rules already exist.