Comparison Overview

Angel Publishing

VS

Oregon Beer Growler

Angel Publishing

3 E Read St, Baltimore, Maryland, 21202, US
Last Update: 2025-11-25
Between 750 and 799

In short, Angel Publishing examines and provides ideas and strategies for our readers on finance, markets, human nature and obscure financial trends. Whether core ideas about markets, capital and wealth building, or frank discussion on health, culture, travel and the world, our philosophy is one of limited government, free markets, unrestricted free speech and free thought and a celebration and defense of individual liberty.

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

Oregon Beer Growler

611 NE 3rd St, McMinnville, Oregon, 97128, US
Last Update: 2025-11-26

The Oregon Beer Growler is Oregon's beer magazine. Beginning with the first publication in July 2012, the Oregon Beer Growler is now available at more than 750 locations in Oregon making it the largest magazine in Oregon by location. It is also free on the web at www.OregonBeerGrowler.com. Monthly readership is estimated at 46,655 in print with another 21,237 average unique visitors per month at our website. Stories include blind consumer beer tastings, homebrew recipes, food and beer pairings and recipes, events, openings, seasonal features, brewer business advice, Oregon beer history, beer technology, and on and on and on!

NAICS: 511
NAICS Definition:
Employees: 2
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/angel-publishing.jpeg
Angel Publishing
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/oregon-beer-growler.jpeg
Oregon Beer Growler
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
Angel Publishing
100%
Compliance Rate
0/4 Standards Verified
Oregon Beer Growler
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 Angel Publishing in 2025.

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

No incidents recorded for Oregon Beer Growler in 2025.

Incident History — Angel Publishing (X = Date, Y = Severity)

Angel Publishing cyber incidents detection timeline including parent company and subsidiaries

Incident History — Oregon Beer Growler (X = Date, Y = Severity)

Oregon Beer Growler cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/angel-publishing.jpeg
Angel Publishing
Incidents

No Incident

https://images.rankiteo.com/companyimages/oregon-beer-growler.jpeg
Oregon Beer Growler
Incidents

No Incident

FAQ

Angel Publishing company demonstrates a stronger AI Cybersecurity Score compared to Oregon Beer Growler company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Oregon Beer Growler company has disclosed a higher number of cyber incidents compared to Angel Publishing company.

In the current year, Oregon Beer Growler company and Angel Publishing company have not reported any cyber incidents.

Neither Oregon Beer Growler company nor Angel Publishing company has reported experiencing a ransomware attack publicly.

Neither Oregon Beer Growler company nor Angel Publishing company has reported experiencing a data breach publicly.

Neither Oregon Beer Growler company nor Angel Publishing company has reported experiencing targeted cyberattacks publicly.

Neither Angel Publishing company nor Oregon Beer Growler company has reported experiencing or disclosing vulnerabilities publicly.

Neither Angel Publishing nor Oregon Beer Growler holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Angel Publishing company nor Oregon Beer Growler company has publicly disclosed detailed information about the number of their subsidiaries.

Angel Publishing company employs more people globally than Oregon Beer Growler company, reflecting its scale as a Book and Periodical Publishing.

Neither Angel Publishing nor Oregon Beer Growler holds SOC 2 Type 1 certification.

Neither Angel Publishing nor Oregon Beer Growler holds SOC 2 Type 2 certification.

Neither Angel Publishing nor Oregon Beer Growler holds ISO 27001 certification.

Neither Angel Publishing nor Oregon Beer Growler holds PCI DSS certification.

Neither Angel Publishing nor Oregon Beer Growler holds HIPAA certification.

Neither Angel Publishing nor Oregon Beer Growler 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.