In this blog entry we wanted to introduce one specific way to reduce the Smart Contract-related risks significantly and at little to no cost. If you would ask us to choose just one solution for risk mitigation, we would choose to rely on the OpenZeppelin framework in the development work.‍ OpenZeppelin framework is a project that has been created as a response to the Parity hack and many other incidents that happened in the web3 world over the years. The authors of the framework recognized the necessity to compile available security best practices and produce some verified code templates for use by web3 developers. 

In this post we are explaining the proper replacement for the ISMS log-storm anti-pattern described in the previous post. We are identifying specific infrastructure aspects that need adjusting and we come up with a general rule that allows avoiding log storms in different implementations.

This post presents a problematic pattern that I encountered in the infrastructure of one of my clients. I am calling this pattern "log storm", simply because I haven't encountered a more appropriate name. In practice this architectural anti-pattern leads to the creation of unnecessary amount of log entries in a security system which in turn incurs unnecessary usage costs. It can probably be encountered in various platforms and setups, but in this post I am focusing on AWS-based set-up.

In this post you will learn how to install, configure and run TProbe debugger. This chapter covers the DEB packages installation process. According to this tutorial, you will be able to perform installation in Ubuntu and Debian systems and their derivatives.