AI Rebuilt the App. Who Secures It? 5 Checks for MSP Owners
The video uses a digital avatar of Erick Grau, CEO of Chibitek.
AI coding tools make it easier than ever for someone on your team to stand up an internal copy of a business app. The demo can look ready in an afternoon. It has a login screen, it has data in it, and it does the one job the team wanted.
Sign-in, hosting, patching, and access control are still your job.
Why This Lands on the MSP
If you lead IT or you run an MSP, you may start to see these apps show up outside the official stack. Somebody in operations builds a tracker. Somebody in sales builds a quick quoting tool. Nobody asks, because it only took an afternoon.
I'm not against any of that. Teams solving their own problems is a good thing. But when one of those apps starts holding real company data, it becomes a production system, whether anyone planned for that or not. Watch for the usual gaps:
No company sign-on
No named owner
No patch plan
No clear picture of who can read the data
None of these are new problems. CISA has written guidance for every one of them. Here are the five checks we run before an app like this holds real company data.
Check 1: Put Company Sign-On and MFA in Front of It

A homegrown app with its own username and password list is one more set of credentials nobody is managing. Put it behind the same sign-on your team already uses.
CISA's identity and access management guidance is direct: "Implement MFA as part of an enterprise SSO solution." Its Cybersecurity Performance Goals 2.0 say organizations should "require MFA to access assets using the strongest available method, if MFA is available for that asset," and that "All IT accounts leverage MFA to access organizational resources."
If the app can't sit behind your single sign-on, that's your first conversation, before anyone uploads a client list to it.
Check 2: Give Every App a Named Owner and a Patch Plan
An afternoon app still runs on frameworks, libraries, and hosting that need updates. If nobody owns it, nobody patches it.
CISA's Performance Goals tell organizations to "implement a vulnerability management program to patch and mitigate misconfigured software in a timely manner," and to "assign responsibilities and ensure procedures are followed" for responding to vulnerabilities. A separate goal on cybersecurity responsibilities says roles and responsibilities "should be documented."
For an MSP, that means one name next to every internal app, and a written answer to a simple question: who updates this, and how often?
Check 3: Keep Secrets Out of the Repo
Fast builds tend to put API keys and passwords right in the code, because it works and it's quick. That is exactly what CISA warns against.
In their Product Security Bad Practices guidance, CISA and the FBI say the presence of "hardcoded credentials or secrets in source code" for products used in critical infrastructure "is dangerous." Their recommended action is to make sure "secrets are not present in source code, such as by using a secret manager," and to "integrate scanning for presence of secrets or credentials" into development. That guidance is written for software manufacturers, but the habit carries over to any internal app your team runs. CISA's IT Sector-Specific Goals say the same thing in plain words: "Do not store sensitive data or credentials in source code."
So the check is simple. Keys live in a secret manager, and the repo gets scanned for secrets.
Check 4: Turn Logging On, and Actually Collect the Logs

A lot of quick apps either log nothing or log to a file nobody reads. When something goes wrong, you have no trail.
CISA's Performance Goals say administrative and security-focused logs should be collected for detection and incident response, that "logs are stored in a central system," that they "can only be accessed or modified by authorized and authenticated users," and that "security teams are notified when a critical log function is disabled."
If the new app isn't feeding the place your security logs already go, it isn't ready.
Check 5: Inventory the Shadow Apps, and the Data They Hold

You can't secure what you don't know exists. CISA describes shadow IT as "hardware/software that is on the network but is managed outside of, and without the knowledge of, the primary IT department."
Its Performance Goals tell organizations to "maintain a regularly updated inventory of all organizational assets," and that list explicitly includes "data, hardware, software, systems, facilities, and personnel." So the inventory isn't just a list of apps. It's what each app holds, and where that data lives.
The Bottom Line
A working demo is not a production app. If you can't name the owner, the sign-in path, the patch plan, and where the data lives, it does not go live.
That rule is Chibitek guidance. The five checks behind it come straight from CISA's public goals and guidance, and none of them require you to say no to the people building things. They just require someone to say "not yet."
Key Points
AI coding tools make it easy to stand up an internal copy of a business app. The security work around it doesn't go away.
Put company sign-on and MFA in front of internal apps. CISA says to implement MFA as part of an enterprise SSO solution.
Give every app a named owner and a patch plan, in line with CISA's vulnerability management goal.
Keep secrets out of source code with a secret manager and secret scanning, as CISA and the FBI recommend.
Collect logs centrally, limit who can read them, and get notified if logging turns off.
Inventory shadow apps and the data they hold.
Frequently Asked Questions
Should we ban teams from building internal apps with AI? That's your call, but a ban can push the work further out of sight. A short checklist that every app passes before it holds real data is easier to enforce.
Is this only a problem for large companies? No. A small team can stand up one of these apps just as fast, and a small team often has fewer people watching.
Where do these checks come from? The five checks are CISA's public guidance, mainly the Cybersecurity Performance Goals 2.0, plus the CISA and FBI Product Security Bad Practices guidance. The "it does not go live" rule is our own.
Let's Check Before It Goes Live
At Chibitek, we help businesses keep technology effortless, with no geek-speak. If your team is building internal apps faster than anyone can review them, contact us at hello@chibitek.com and we can walk through a simple go-live checklist together.
A working demo is not a production app.
We make IT effortless so you can create, disrupt, and grow!
Follow Chibitek on YouTube at @chibitekmsp, and follow Chibitek on LinkedIn.
Sources
All pages were reopened on Nov. 19, 2026, and every quote above was found word for word.








Comments