Zoho@Zoho: Managing Security Issues with a Zoho Creator Application

Posted by Posted on by
0




Zoho@Zoho

series kicked off last year. We have been portraying Zoho Creator applications which we use for our very unique needs. With the series nearing completion, there are only a few more applications left, and we’d like to know how  this series has influenced you. And just in case you have missed out any, here is an archive of the situational applications

showcased till now
:
The first app for this year is here because of its significance. It helps us ensure the reliability of all our services by keeping track of possible security threats. Here is

Hall of Shame.
You read it right. Hall of Shame. More than anything else, we crave for reliability of our services. We realize that you trust us with your precious data. We also understand that we cannot compromise on the security of any of our services and live to talk our way out of the mess. It is why we chose to be on the front-foot. Every single entry on this application is a disgrace to the team, so the teams do whatever it takes to avoid it. Rightly named, don’t you think? Whenever a team comes out with a major update, every other team gets to test it intensively. They test not to find faults, but to improve the quality and reliability of the service. Should they stumble upon a backdoor that might be damaging, it is immediately brought to the attention of everyone. Don’t panic, because we don’t do all these after you start using the feature. This hunting-down happens on a local set-up. Only after every flag has been brought down, do we let it go live for you to use. Here is how it is streamlined.
Flags is the hot keyword here that attracts all the attention it deserves. All flagged vulnerabilities are tracked by security coordinators who are at the heart of every team. Whenever a set of features or fixes is ready, it is updated on a mirror set-up which is very much similar to the one you use, except that this is for testing privately. Security coordinators of every team are then notified of the update through automated email notifications.
Just like our customers, we too use our services extensively and rely on them. While testing the mirror set-up, if any security coordinator comes across any issue that is seemingly dangerous, he makes a note of it on this application and the team behind the service is notified. A developer of that team is then assigned to rectify the reported issue within a deadline. Once done, testing is iterated.
By ensuring that all service updates pass through this critical phase before going live, we have security in it’s rightful place.

Zoho Creator

is not the reason why our services are reliable, but it sure can take all the credit for a timely and custom application with which we implement security. Try this application.