In February 2024, Lookout discovered an advanced phishing kit targeting the Federal Communications Commission (FCC), along with several cryptocurrency platforms. While most people think of email as the realm of phishing attacks, this threat actor — known as CryptoChameleon — used the phishing kit to build a carbon copies of single sign-on (SSO) pages, then used a combination of email, SMS, and voice phishing to target mobile device users.

One issue that is raised frequently is the way in which security or IT teams struggle to speak the “business language” to members of the senior leadership that take the final decisions on spending and investment.

As the threat landscape continues to evolve, cybercriminals are relentlessly refining their phishing tactics. This means that many of the tips and tricks organizations have told their employees to use in the past to spot a malicious email are no longer as effective in safeguarding their digital environments. Here, we dissect three commonly cited phishing detection strategies and unveil their limitations in the face of advanced cyber threats.

We hear a lot about the cybersecurity skills gap, which the latest research puts at 3.4 million globally. There are lots of reasons why organizations find themselves dealing with a skills deficit — from an actual dearth of qualified talent to internal factors including turnover, lack of budget/competitive wages, limited opportunities for growth and promotion, and lack of training. One aspect that is within a company’s control, but is often unremarked, is unrealistic hiring practices.

In the last blog on fixing vulnerabilities with Veracode Fix, we looked at SQL Injection remediation in a Java application. Since then, we have released Fix support for Python (and PHP) and launched a new VS Code plugin that includes support for Fix. It seems appropriate, therefore, to look at resolving a problem in a Python app using Veracode Fix in the VS Code IDE. This time let’s examine a simple cross-site scripting (XSS) weakness.

So, you’ve done your homework. You’ve clearly defined business requirements, and you think you want to implement a Security Information and Event Management (SIEM) solution into your organization. Cloud migration and remote work have changed the way threat actors attack, and it feels like every day you read about a new methodology. While a lot of companies added a SIEM to their cybersecurity technology stack, you’re not sure whether you can afford one.

In the rapidly advancing realm of cloud-native security, Data Security Posture Management (DSPM) emerges as a critical framework, ensuring organizations maintain robust control over their data assets. As cloud environments evolve, understanding and implementing DSPM becomes vital for better securing data defenses. In this blog post, we'll delve into the basics of DSPM, its significance in cloud-native security and how Panoptica approaches DSPM within its CNAPP solution.

Does your security team have dozens of tools to manage, all with disparate user experiences, data models, and capabilities? Unfortunately, this is the result of many traditional SIEM solutions that lack the ability to integrate all features. This creates a big challenge for your SOC because analysts have to ensure they’re using the right tool at the right time to detect attacks. But today, there’s a better option.

Several months ago, Darcy Clarke, a former Staff Engineering Manager at GitHub, discovered the “Manifest Confusion” bug in the npm ecosystem. The bug was caused by the npm registry not validating whether the manifest file contained in the tarball (package.json) matches the manifest data published to the npm server. Clarke claims this to be a large threat, allowing malicious actors to deceive developers and hide harmful code from detection.

You are the CISO of a leading financial services firm serving a large number of clients with substantial assets. You process a massive volume of data every day, and much of it is sensitive: customer account information, social security numbers, and other PII.