Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

On April 4, 2025, The Australian Financial Review reported on a set of credential abuse attacks targeting multiple Austrian superannuation funds. These attacks were not breaches of the infrastructure of those companies, but compromises of individual customer accounts via stolen credentials. How were those customer credentials stolen?

Cooperation is the key to success, and working with third parties helps your organization increase efficiency, offer better products and services, employ highly qualified experts, and cut costs. However, all these benefits come at the price of additional cybersecurity risks. Even minor flaws in your third-party vendor’s security and privacy routines may lead to serious cybersecurity breaches in your organization.

In keeping with Bitsight's ongoing commitment to making its ratings more meaningful and more representative of an ever-changing Cybersecurity landscape, the Ratings Algorithm Update for 2025 is scheduled to go into preview on April 8, 2025. The highlight of RAU 2025 is the incorporation of the Web Application Security(WAS) risk vector into the Bitsight Security Ratings1, and the associated deprecation/removal of Web Application Headers(WAH) risk vector.

Staying ahead of the game is a top concern for security teams as the cyber threat landscape continues to evolve rapidly. Every year seems to bring new technological advances, which also introduce new cybersecurity trends and significant risks. As organizations face these challenges, it’s essential to build proactive defenses, not reactive responses. The next big cyber threat is already here—ready or not.

All security professionals know third-party risk management doesn’t stop after one risk assessment. What about the next vendor? Or the future risks the vendors you’ve already evaluated will inevitably endure? While completing even a single risk assessment can feel like an arduous journey when done manually, all successful TPRM programs continue long after assessment.

Sequenced event templates are pretty cool, but they were developed around the time that Risk-based Alerting (RBA) was developed in Splunk Enterprise Security. Additionally, they don’t have all the great context we can generate with the holistic picture provided by risk, so I want to provide guidance on how we would implement its equivalent in the RBA context as they are now deprecated in Splunk Enterprise Security 8.0. There are two approaches we can utilize that do slightly different things.

Compliance is a “ticket to entry” for businesses today, and information security risk management (ISRM) makes sure organizations hang on to their ticket. In this blog, we’ll review how ISRM helps organizations not only get compliant but stay compliant. And how Tripwire makes that process automatic.

It’s no secret that human error still plays a significant role in data breaches - despite ongoing security and awareness training. But how do we finally disrupt this trend? The answer lies in a new approach to human risk management.

Every day, stolen credentials are bought, sold, and exploited on the dark web, fueling account takeovers, data breaches, and financial fraud. Organizations must act fast to stop these threats before they escalate. Yet, traditional security tools struggle to detect compromised credentials before it’s too late. According to Bitsight’s upcoming State of the Underground 2025 report, leaked credentials surged by 24% and logs listed on underground markets rose by 13.2% in 2024 alone.

In our recent article on Continuous Threat Exposure Management (CTEM), we highlighted how exposure assessment platforms (EAPs) like Nucleus can support several critical phases of the CTEM framework. In that article, we intentionally separated the scoping step from the other technology-dependent CTEM stages. Scoping begins as a business- and process-driven exercise. However, doing scoping well and at scale relies more on having the right technology.