Comparison Overview

EP Global Communications

VS

Crème de Cornell

EP Global Communications

undefined, undefined, undefined, undefined, US
Last Update: 2025-11-26
View Profile
Between 750 and 799
http://n/a

EP Global Communications, Inc. (Ticker EPGL) is a new and innovative medical device manufacturing and marketing company. The Company's first FDA 510k cleared device will address the diagnosis of chronic muscular pain, making it possible for physicians to more accurately diagnose and treat patients who present with chronic back pain, neck pain, migraine, fybromyalgia and more.

NAICS: 511
NAICS Definition:
Employees: 18
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0
View Profile

Crème de Cornell

Ithaca, New York, US, 14853
Last Update: 2025-11-21
Between 750 and 799
https://www.cremedecornell.net

Crème de Cornell is a student-run publication that allows passionate food enthusiasts to come together and publish a diversity of recipes and articles. We aim to tell the stories of everyone around us through the lens of food in our semesterly magazine, which highlights a selected theme. To view past magazines or learn more about our organization, visit us at cremedecornell.net. This organization is a registered student organization of Cornell University.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/ep-global-communications.jpeg
EP Global Communications
—
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/crème-de-cornell.jpeg
Crème de Cornell
—
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
EP Global Communications
100%
Compliance Rate
0/4 Standards Verified
Crème de Cornell
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 EP Global Communications in 2025.

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

No incidents recorded for Crème de Cornell in 2025.

Incident History — EP Global Communications (X = Date, Y = Severity)

EP Global Communications cyber incidents detection timeline including parent company and subsidiaries

Incident History — Crème de Cornell (X = Date, Y = Severity)

Crème de Cornell cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/ep-global-communications.jpeg
EP Global Communications
Incidents

No Incident

https://images.rankiteo.com/companyimages/crème-de-cornell.jpeg
Crème de Cornell
Incidents

No Incident

FAQ

EP Global Communications company demonstrates a stronger AI Cybersecurity Score compared to Crème de Cornell company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Crème de Cornell company has disclosed a higher number of cyber incidents compared to EP Global Communications company.

In the current year, Crème de Cornell company and EP Global Communications company have not reported any cyber incidents.

Neither Crème de Cornell company nor EP Global Communications company has reported experiencing a ransomware attack publicly.

Neither Crème de Cornell company nor EP Global Communications company has reported experiencing a data breach publicly.

Neither Crème de Cornell company nor EP Global Communications company has reported experiencing targeted cyberattacks publicly.

Neither EP Global Communications company nor Crème de Cornell company has reported experiencing or disclosing vulnerabilities publicly.

Neither EP Global Communications nor Crème de Cornell holds any compliance certifications.

Neither company holds any compliance certifications.

Neither EP Global Communications company nor Crème de Cornell company has publicly disclosed detailed information about the number of their subsidiaries.

Crème de Cornell company employs more people globally than EP Global Communications company, reflecting its scale as a Book and Periodical Publishing.

Neither EP Global Communications nor Crème de Cornell holds SOC 2 Type 1 certification.

Neither EP Global Communications nor Crème de Cornell holds SOC 2 Type 2 certification.

Neither EP Global Communications nor Crème de Cornell holds ISO 27001 certification.

Neither EP Global Communications nor Crème de Cornell holds PCI DSS certification.

Neither EP Global Communications nor Crème de Cornell holds HIPAA certification.

Neither EP Global Communications nor Crème de Cornell 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.

Published
Date
2025-11-27
Updated
Date
2025-11-27
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
References
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).

Published
Date
2025-11-27
Updated
Date
2025-11-27
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
References
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

Published
Date
2025-11-27
Updated
Date
2025-11-27
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
References
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.

Published
Date
2025-11-27
Updated
Date
2025-11-27
References
Description

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

Published
Date
2025-11-27
Updated
Date
2025-11-27
References