accenture-falls-victim-to-ransomware

Accenture falls victim to ransomware

Accenture; one of the biggest IT Consultancies in the world has recently been hit by a ransomware attack carried out by Lockbit 2.0 operators. This was publicly disclosed on Lockbit’s leaks site where they were demanding a staggering $50,000,000

Accenture is known to work with a multitude of clients across a wide array of industries as outlined on their Case Studies & Stories section and as such, it employs over half a million people in as many as 50 different countries; This shows the potential reach for a cyberattack such as this, potentially endangering sensitive data from all parties involved (Company, employees and clients alike)

“These people are beyond privacy and security. I really hope that their services are better than what I saw as an insider. If you’re interested in buying some databases reach us” is posted on their leak site as a message below their counter for publishing all the leaked files

A screenshot of Lockbit's leak site advertising the possible leak/demanding payment

More on the attack

According to the Cyble research team and Hudson Rock as much as 6 TB of files and as many as 2,500 computer systems including employees and partners have been compromised

Although the main goal of a ransomware attack is usually to encrypt files in exchange for money, Accenture stated that they were able to quickly recover the affected system "We fully restored our affected systems from backup, and there was no impact on Accenture’s operations, or on our clients’ systems." but at this point, the damage was already done, the attackers had already extracted the files from the affected systems.

On Codenotary Cloud

At CodeNotary we understand how important it is to secure your systems to prevent this and many other similar incidents but more importantly, we detected the need for a robust solution that didn’t depend on digital dertificates because of how cumbersome things can be once a certificate is revoked (For more information on digital certificates, read our blog post on them).
With our Codenotary Cloud and its multiple integrations you can prevent this and many other types of cyberattacks by only introducing or releasing software that you can not only trust but also cryptographically verify to prevent unauthorized or tampered versions from ever reaching those systems.

To learn more about how you can implement end-to-end zero-trust protection for your CI pipelines and deployments visit CodeNotary and signup for the Cloud version.

Codenotary Cloud

PROTECTED SOFTWARE
SUPPLY CHAIN

Trusted CI/CD, SBOM and artifact protection with cryptographic proof. One CLI to manage all.
Our highly scalable service already processes tens of millions of transactions every single month.

Subscribe to Our Newsletter

Get the latest product updates, company news, and special offers delivered right to your inbox.

Subscribe to our newsletter

Use Case - Tamper-resistant Clinical Trials

Goal:

Blockchain PoCs were unsuccessful due to complexity and lack of developers.

Still the goal of data immutability as well as client verification is a crucial. Furthermore, the system needs to be easy to use and operate (allowing backup, maintenance windows aso.).

Implementation:

immudb is running in different datacenters across the globe. All clinical trial information is stored in immudb either as transactions or the pdf documents as a whole.

Having that single source of truth with versioned, timestamped, and cryptographically verifiable records, enables a whole new way of transparency and trust.

Use Case - Finance

Goal:

Store the source data, the decision and the rule base for financial support from governments timestamped, verifiable.

A very important functionality is the ability to compare the historic decision (based on the past rulebase) with the rulebase at a different date. Fully cryptographic verifiable Time Travel queries are required to be able to achieve that comparison.

Implementation:

While the source data, rulebase and the documented decision are stored in verifiable Blobs in immudb, the transaction is stored using the relational layer of immudb.

That allows the use of immudb’s time travel capabilities to retrieve verified historic data and recalculate with the most recent rulebase.

Use Case - eCommerce and NFT marketplace

Goal:

No matter if it’s an eCommerce platform or NFT marketplace, the goals are similar:

  • High amount of transactions (potentially millions a second)
  • Ability to read and write multiple records within one transaction
  • prevent overwrite or updates on transactions
  • comply with regulations (PCI, GDPR, …)


Implementation:

immudb is typically scaled out using Hyperscaler (i. e. AWS, Google Cloud, Microsoft Azure) distributed across the Globe. Auditors are also distributed to track the verification proof over time. Additionally, the shop or marketplace applications store immudb cryptographic state information. That high level of integrity and tamper-evidence while maintaining a very high transaction speed is key for companies to chose immudb.

Use Case - IoT Sensor Data

Goal:

IoT sensor data received by devices collecting environment data needs to be stored locally in a cryptographically verifiable manner until the data is transferred to a central datacenter. The data integrity needs to be verifiable at any given point in time and while in transit.

Implementation:

immudb runs embedded on the IoT device itself and is consistently audited by external probes. The data transfer to audit is minimal and works even with minimum bandwidth and unreliable connections.

Whenever the IoT devices are connected to a high bandwidth, the data transfer happens to a data center (large immudb deployment) and the source and destination date integrity is fully verified.

Use Case - DevOps Evidence

Goal:

CI/CD and application build logs need to be stored auditable and tamper-evident.
A very high Performance is required as the system should not slow down any build process.
Scalability is key as billions of artifacts are expected within the next years.
Next to a possibility of integrity validation, data needs to be retrievable by pipeline job id or digital asset checksum.

Implementation:

As part of the CI/CD audit functionality, data is stored within immudb using the Key/Value functionality. Key is either the CI/CD job id (i. e. Jenkins or GitLab) or the checksum of the resulting build or container image.

White Paper — Registration

We will also send you the research paper
via email.

CodeNotary — Webinar

White Paper — Registration

Please let us know where we can send the whitepaper on CodeNotary Trusted Software Supply Chain. 

Become a partner

Start Your Trial

Please enter contact information to receive an email with the virtual appliance download instructions.

Start Free Trial

Please enter contact information to receive an email with the free trial details.