Developing applications using low code platforms has gained popularity in recent years due to its ability to accelerate the software development process. However, with increased speed and efficiency comes the need for robust security measures to protect sensitive data and ensure a safe user experience. In this article, we will explore the best practices and strategies for enhancing low code application security.

Let’s not waste time. You’re here because you’re building a webhook feature in your app. Unfortunately, there are quite a few things that can go wrong from a security perspective. This article aims to ensure that you’re not making any well-known mistakes while building webhooks.

Imagine someone having access to all your documents, photos, and even your browsing history. It may sound like something out of 1984, but using Google’s products can be a nightmare for your privacy. Despite this, Google Drive has over 200 million active users choosing to store their files with Google. Although Google offers many features with Drive, Chrome, and YouTube, and more,this convenience comes at a cost—your privacy.

Among the due diligence a company should perform when signing with a managed detection and response (MDR) provider, one item that may not be top of mind is who owns custom content developed during the service. You may be surprised to find out it’s often the provider, not you. MDR content ownership becomes an issue when you change providers or bring in-house the monitoring capability.

Google has issued a security advisory to owners of its Android Pixel smartphones, warning that it has discovered someone has been targeting some devices to bypass their built-in security. What makes the reported attacks particularly interesting is that traditional cybercriminals may not be behind them, but rather "forensic companies" exploiting two vulnerabilities to extract information and prevent remote wiping.

At a time when the cloud estate of organizations is expanding faster than ever, the attack surface is becoming harder to monitor. This blog post aims to demystify attack surface discovery. We’ll explore what it involves, why it’s important, and how it fits into securing your digital assets. By the end, you’ll understand why a nuanced approach to attack surface discovery isn’t just beneficial; it’s essential for staying a step ahead against today’s sophisticated threats.

A look at the recently discovered backdoor hiding in the open source XZ Utils compression service.

Let’s catch up on the more interesting vulnerability disclosures and cyber security news gathered from articles across the web this week. This is what we have been reading about on our coffee break! You take a long bank holiday weekend and the (Linux) world falls apart. Ouch.

An attack vector, also known as a threat vector, is a way for cybercriminals to gain access to an organization’s network or system. Some common types of attack vectors that organizations need to defend against include weak and compromised credentials, social engineering attacks, insider threats, unpatched software, lack of encryption and misconfigurations. Organizations must identify all of the potential attack vectors and protect their network against them to avoid security breaches.

Read also: Australian hacker Abdilo extradited to the US, carders arrested in Russia, and more.