How to turn a credentials breach in a development opportunity

Valerio Barbera

Hi, I’m Valerio founder and CTO at Inspector.

Recently my personal account on one of our external tools was cracked. My credentials have been stolen so the attackers have had access to this service with our credit card attached.

There were no risks for our users security, but only for our bank account, because attackers could use up our credits or use our account for public spam activities.

This experience has made us much more aware of the value of using (and develop) safe tools. We have therefore decided to bring some new features into Inspector that allow our customers to keep their account more secure, avoiding being victims of these violations as we have.

Regaining control

As soon as we realized that something was wrong with our tool, we’ve immediately disabled the credit card and removed the tool from our stack.

There were no risks for our users security, but only for our bank account.

Compromised credentials will always present a risk, but there are policies that can mitigate that risk.

The first step is to establish policies for the strength and management of passwords. Not all credentials are created equal.

For accessing sensitive information and for administrative access to internal working tools, stronger, more complex passwords and additional factors such as biometrics, cryptographic keys or 2FA confirmation codes are now required by default in our company.

This includes also all social media accounts of the entire team.

Now it’s time to bring what we have learned on Inspector. Below I present you the next security features we have decided to implement in Inspector.

Control Logged-in devices

This feature should allows our users to check the logged-in devices and easily log-out from a specific device with a simple click.

Below the detail of what we want to develop:

  • Displays currently logged in devices for a user in the profile section.
  • Log out from any specific device from the list of currently logged-in devices.
  • An option to log out from all other devices except the currently logged-in device.
  • An option to disable multiple device logins altogether. This means that a user can only be logged in from one device at a time.

If you will log in Inspector from your smartphone, you will see this new device in the logged-in devices list. This will allow you to identify unknown devices in the list, disconnect them with a simple click, and change your password to protect your account from unexpected authentications.

2FA Authentication

Are you using the same password for multiple websites including Inspector? Are you accessing Inspector from public or shared computers?

Such action weaken your password and make it easier to steal.

That’s why we’ll implement two step verification. An optional security feature that helps protect your account even if your password is stolen or cracked.

This feature will improve security because signing in requires two things:

  • Something you know: Your Password
  • Something you have: Your Phone

If an attacker crack your credentials he cannot authenticate into your Inspecotr account because he doesn’t have your phone to provide us the security code.

Reject insecure passwords

In order to increase the average security of our users account we’ll also plan a password filter to avoid weak passwords to be used when developers create their account on Inspector.

According to NordPass many accounts are created with passwords that require just a few seconds to be hacked putting privacy and security at risk. Think about how sensitive are the data cllected by a monitoring system, database queries, server information, and many other application details that an attacker could use for malicious purpose.


While a startup grows fast some incident can happen, but the most important thing is to learn from mistakes and put the experience at the disposal of the customers.

I hope you appreciate our work to make Inspector a safer and more efficient product with the aim of helping you reach your goals quickly and easily.

Application monitoring

If you found this post interesting and want to drastically change your developers’ life for the better, you can give Inspector a try.

Inspector is an easy to use Code Execution Monitoring tool that helps developers to identify bugs and bottlenecks in their application automatically. Before customers do.

screenshot inspector code monitoring timeline

It is completely code-driven. You won’t have to install anything at the server level or make complex configurations in your cloud infrastructure.

It works with a lightweight software library that you can install in your application like any other dependency. Check out the supported technologies in the GitHub organization.

Create an account, or visit the website for more information:

Related Posts

Logging Database Queries with Eloquent ORM and Laravel – Fast Tips

Having a more clear understanding of what your application really does during its execution is an increasing necessity. Logging the raw database queries generated by your preferred ORM is one of the most common needs to be more aware of what is happening behind the scenes. More and more abstraction layers are becoming available in

Laravel Http Client Overview and Monitoring

Laravel HTTP client was introduced starting from version 10 of the framework, and then also made available in all previous versions. It stands out as a powerful tool for making HTTP requests and handling responses from external services. This article will delve into the technical foundations of the Laravel HTTP client, its motivations, and how

Laravel Form Request and Data Validation Tutorial

In this article I will talk about Laravel Form Request to send data from your application frontend to the backend. In web applications, data is usually sent via HTML forms: the data entered by the user into the browser is sent to the server and stored in the database eventually. Laravel makes it extremely simple