CTO Michael Bargury’s Thoughts on Low-Code Security Featured on Dark Reading

  • Written by Michael Bargury
You are currently viewing CTO Michael Bargury’s Thoughts on Low-Code Security Featured on Dark Reading

We are proud to have thought leaders at the head of Zenity. Michael Bargury, Zenity co-founder and CTO, recently published an in-depth piece on Dark Reading, one of the most widely read cybersecurity news sites and online communities for cybersecurity professionals. The piece was chosen for Dark Reading’s “The Edge,” a featured section that presents deep dives into cybersecurity issues.

Michael’s article, “Addressing the Low-Code Security Elephant in the Room,” spells out the complexity of security for low-code/no-code platforms and applications and suggests the precedent of the Shared Responsibility Model. He discusses the four different layers of low-code applications and development choices such as connectors or custom components that affect security. Finally, Michael discusses the applicability of the Shared Responsibility Model (developed for cloud computing) to the low-code security challenge and shares his recommendations on who should own each of the security risks.

All the news straight to your inbox. Signup for Zenity’s weekly newsletter.

Don’t miss a single opportunity to get knowledge.

    We invite you over to Dark Reading to read the full article. Empower yourself with a deeper understanding of low-code/no-code’s security challenges and potential approaches for addressing them.

    To keep up to date on Michael’s industry contributions, follow him on Linkedin

    About the Author

    Michael Bargury

    Michael is the Co-Founder and CTO of Zenity. He is an industry expert in cybersecurity interested in cloud, SaaS and AppSec. Prior to Zenity, Michael was a senior architect at Microsoft Cloud Security CTO Office, where he founded and headed security product efforts for IoT, APIs, IaC and confidential computing. Michael is leading the OWASP community effort on low-code/no-code security.

    Table of contents