What is shadow IT? The tools your team built because it had to
A critical process one person runs from a personal spreadsheet. Correctly, most days.
For security & IT
The security and IT teams caring about safety and compliance
Latest
7 articles
Why internal tools become production risks
A tool built as a side project ends up running a core process, with no access control, no audit log, and no owner.
Four controls that make an internal tool safe to rely on
Access control, audit trails, separate environments, and change management, and what each one prevents.
Custom code on the new Retool, with the controls IT asks for
What changed in Retool for teams that need custom code and still have to pass an IT review.
The security and compliance checklist to run before buying low-code
RBAC, audit logging, encryption, SSO, and the compliance frameworks to check before a low-code platform reaches procurement.
What your security team will ask about low-code, and the answers
Access control, data exposure, integrations, and compliance: the four questions every low-code review comes back to.
Topics for this reader
Questions answered for this reader
- how to use custom code in Retool with source control and review
- is low-code secure enough for enterprise use
- what controls does an internal tool need to be safe to rely on
- what is low-code
- what is shadow IT
- what security and compliance questions to ask before buying a low-code platform
- why do internal tools become production risks