Comparison Overview

Hearts Bluff Music, LLC

VS

Figshare

Hearts Bluff Music, LLC

9 Music Square South #108, Nashville, TN, 37212, US
Last Update: 2025-11-27

Since 2005 Hearts Bluff Music has assimilated a historic portfolio of copyrights and royalty interests spanning 50 years of defining American music. On behalf of our investors, we’ve purchased interests in over 90 #1 songs, with our overall catalog approaching 15,000+ songs. With $30 Million budgeted for acquisitions, we are purposefully building one of Nashville’s finest independent music catalogs. We are currently evaluating select music publishing catalogs to purchase on behalf on our investors. This private funding allows us to purchase diverse royalty interests, including publisher and writer streams. As a private, independent company we specialize in deals that are fair, flexible and creative. Since we’re a boutique business owned by entrepreneurs and music creators, we’ve become an ideal, like-minded solution for many sellers.

NAICS: 511
NAICS Definition: Publishing Industries (except Internet)
Employees: 5
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Figshare

Digital Science, London, N1 9XW, GB
Last Update: 2025-11-21
Between 750 and 799

"Get credit for all of your research."​ Scientific publishing as it stands is an inefficient way to do science on a global scale. A lot of time and money is being wasted by groups around the world duplicating research that has already been carried out. FigShare allows you to share all of your data, negative results and unpublished figures. In doing this, other researchers will not duplicate the work, but instead may publish with your previously wasted figures, or offer collaboration opportunities and feedback on preprint figures.

NAICS: 511
NAICS Definition: Publishing Industries (except Internet)
Employees: 17
Subsidiaries: 23
12-month incidents
0
Known data breaches
2
Attack type number
3

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/hearts-bluff-music-publishing.jpeg
Hearts Bluff Music, LLC
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
https://images.rankiteo.com/companyimages/figshare.jpeg
Figshare
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
Compliance Summary
Hearts Bluff Music, LLC
100%
Compliance Rate
0/4 Standards Verified
Figshare
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Book and Periodical Publishing Industry Average (This Year)

No incidents recorded for Hearts Bluff Music, LLC in 2025.

Incidents vs Book and Periodical Publishing Industry Average (This Year)

No incidents recorded for Figshare in 2025.

Incident History — Hearts Bluff Music, LLC (X = Date, Y = Severity)

Hearts Bluff Music, LLC cyber incidents detection timeline including parent company and subsidiaries

Incident History — Figshare (X = Date, Y = Severity)

Figshare cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/hearts-bluff-music-publishing.jpeg
Hearts Bluff Music, LLC
Incidents

No Incident

https://images.rankiteo.com/companyimages/figshare.jpeg
Figshare
Incidents

Date Detected: 06/2023
Type:Cyber Attack
Blog: Blog

Date Detected: 12/2022
Type:Breach
Attack Vector: Unauthorized access to data security system
Blog: Blog

Date Detected: 6/2022
Type:Breach
Blog: Blog

FAQ

Hearts Bluff Music, LLC company demonstrates a stronger AI Cybersecurity Score compared to Figshare company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Figshare company has historically faced a number of disclosed cyber incidents, whereas Hearts Bluff Music, LLC company has not reported any.

In the current year, Figshare company and Hearts Bluff Music, LLC company have not reported any cyber incidents.

Figshare company has confirmed experiencing a ransomware attack, while Hearts Bluff Music, LLC company has not reported such incidents publicly.

Figshare company has disclosed at least one data breach, while Hearts Bluff Music, LLC company has not reported such incidents publicly.

Figshare company has reported targeted cyberattacks, while Hearts Bluff Music, LLC company has not reported such incidents publicly.

Neither Hearts Bluff Music, LLC company nor Figshare company has reported experiencing or disclosing vulnerabilities publicly.

Neither Hearts Bluff Music, LLC nor Figshare holds any compliance certifications.

Neither company holds any compliance certifications.

Figshare company has more subsidiaries worldwide compared to Hearts Bluff Music, LLC company.

Figshare company employs more people globally than Hearts Bluff Music, LLC company, reflecting its scale as a Book and Periodical Publishing.

Neither Hearts Bluff Music, LLC nor Figshare holds SOC 2 Type 1 certification.

Neither Hearts Bluff Music, LLC nor Figshare holds SOC 2 Type 2 certification.

Neither Hearts Bluff Music, LLC nor Figshare holds ISO 27001 certification.

Neither Hearts Bluff Music, LLC nor Figshare holds PCI DSS certification.

Neither Hearts Bluff Music, LLC nor Figshare holds HIPAA certification.

Neither Hearts Bluff Music, LLC nor Figshare holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

ThingsBoard in versions prior to v4.2.1 allows an authenticated user to upload malicious SVG images via the "Image Gallery", leading to a Stored Cross-Site Scripting (XSS) vulnerability. The exploit can be triggered when any user accesses the public API endpoint of the malicious SVG images, or if the malicious images are embedded in an `iframe` element, during a widget creation, deployed to any page of the platform (e.g., dashboards), and accessed during normal operations. The vulnerability resides in the `ImageController`, which fails to restrict the execution of JavaScript code when an image is loaded by the user's browser. This vulnerability can lead to the execution of malicious code in the context of other users' sessions, potentially compromising their accounts and allowing unauthorized actions.

Risk Information
cvss4
Base: 6.2
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:H/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to to verify that the token used during the code exchange originates from the same authentication flow, which allows an authenticated user to perform account takeover via a specially crafted email address used when switching authentication methods and sending a request to the /users/login/sso/code-exchange endpoint. The vulnerability requires ExperimentalEnableAuthenticationTransfer to be enabled (default: enabled) and RequireEmailVerification to be disabled (default: disabled).

Risk Information
cvss3
Base: 9.9
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Description

Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to sanitize team email addresses to be visible only to Team Admins, which allows any authenticated user to view team email addresses via the GET /api/v4/channels/{channel_id}/common_teams endpoint

Risk Information
cvss3
Base: 4.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Description

Exposure of email service credentials to users without administrative rights in Devolutions Server.This issue affects Devolutions Server: before 2025.2.21, before 2025.3.9.

Description

Exposure of credentials in unintended requests in Devolutions Server.This issue affects Server: through 2025.2.20, through 2025.3.8.