Comparison Overview

Axel & Ash

VS

Lakeland Boating

Axel & Ash

111 Flinders St, Surry Hills, New South Wales, 2010, AU
Last Update: 2025-11-26
Between 750 and 799

The venture started in 2012 when the two wanderlusting souls shared their bucket lists together and realised they both had a dream to start a creative business on their list. Sharing a common passion for the art of journaling they decided to start designing chic, inspiring journals filled with quirky writing prompts for everyone who wanted to capture their days, thoughts and memories in style. Today, Axel & Ash’s journals are getting picked up by the world’s style-makers and jet-setters from Sydney to London and Paris to Hawaii. Their books & products have pride of place in the trendiest concept, fashion and book stores all around the globe like the iconic Urban Outfitters stores in Europe, world famous Shakespeare & Co in Paris, Grandpa in Stockholm, Carousel in Bondi and Ahoy Trader in Byron Bay. Whilst spending the days soaking up the sunny Bondi lifestyle Axel & Ash are continuously working on exciting products and projects for free-spirited, stylish dreamers.

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

Lakeland Boating

undefined, undefined, undefined, 60605, US
Last Update: 2025-11-25

Lakeland Boating magazine has been the voice of the Sweetwater Seas for more than 75 years. From in-depth boat tests and features on weekend getaways to product roundups and stories about colorful Ports of Call, we’ve got the Great Lakes region covered. Meet the people who love the lake lifestyle and glean useful tips on marine electronics, engine repair and general boat maintenance, and more. LakelandBoating.com supplements the print version of the magazine with exclusive news and frequently updated departments. The content is geared toward the interests of freshwater boaters on the Great Lakes, as well as the connecting waterways and inland lakes.

NAICS: 511
NAICS Definition: Publishing Industries (except Internet)
Employees: 6
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/axelandash.jpeg
Axel & Ash
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/lakeland-boating.jpeg
Lakeland Boating
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
Axel & Ash
100%
Compliance Rate
0/4 Standards Verified
Lakeland Boating
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 Axel & Ash in 2025.

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

No incidents recorded for Lakeland Boating in 2025.

Incident History — Axel & Ash (X = Date, Y = Severity)

Axel & Ash cyber incidents detection timeline including parent company and subsidiaries

Incident History — Lakeland Boating (X = Date, Y = Severity)

Lakeland Boating cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/axelandash.jpeg
Axel & Ash
Incidents

No Incident

https://images.rankiteo.com/companyimages/lakeland-boating.jpeg
Lakeland Boating
Incidents

No Incident

FAQ

Lakeland Boating company demonstrates a stronger AI Cybersecurity Score compared to Axel & Ash company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Lakeland Boating company has disclosed a higher number of cyber incidents compared to Axel & Ash company.

In the current year, Lakeland Boating company and Axel & Ash company have not reported any cyber incidents.

Neither Lakeland Boating company nor Axel & Ash company has reported experiencing a ransomware attack publicly.

Neither Lakeland Boating company nor Axel & Ash company has reported experiencing a data breach publicly.

Neither Lakeland Boating company nor Axel & Ash company has reported experiencing targeted cyberattacks publicly.

Neither Axel & Ash company nor Lakeland Boating company has reported experiencing or disclosing vulnerabilities publicly.

Neither Axel & Ash nor Lakeland Boating holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Axel & Ash company nor Lakeland Boating company has publicly disclosed detailed information about the number of their subsidiaries.

Lakeland Boating company employs more people globally than Axel & Ash company, reflecting its scale as a Book and Periodical Publishing.

Neither Axel & Ash nor Lakeland Boating holds SOC 2 Type 1 certification.

Neither Axel & Ash nor Lakeland Boating holds SOC 2 Type 2 certification.

Neither Axel & Ash nor Lakeland Boating holds ISO 27001 certification.

Neither Axel & Ash nor Lakeland Boating holds PCI DSS certification.

Neither Axel & Ash nor Lakeland Boating holds HIPAA certification.

Neither Axel & Ash nor Lakeland Boating 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.