Comparison Overview

Carruth Compliance

VS

Lincoln Financial

Carruth Compliance

10555 SW Lady Marion Dr, Portland, Oregon, US, 97224
Last Update: 2025-11-28
Between 650 and 699

None

NAICS: 52
NAICS Definition: Finance and Insurance
Employees: 6
Subsidiaries: 0
12-month incidents
0
Known data breaches
2
Attack type number
1

Lincoln Financial

150 N. Radnor-Chester Road, Radnor, PA, US, 19087
Last Update: 2025-11-28

Lincoln Financial (NYSE: LNC) helps people to confidently plan for their version of a successful future. We focus on identifying a clear path to financial security, with products including annuities, investments, life insurance, group protection, and retirement plan services. With our 120-year track record of expertise and integrity, millions of customers trust our solutions and service to help put their goals in reach.  Your tomorrow. Our priority. For social media community guidelines: https://visit.lfg.com/4hJHCb2. Lincoln Financial Distributors, a broker-dealer, is the wholesale distribution organization of Lincoln Financial. Lincoln Financial is the marketing name for Lincoln National Corporation and its affiliates including The Lincoln National Life Insurance Company, Fort Wayne, IN, and Lincoln Life & Annuity Company of New York, Syracuse, NY. Lincoln Financial℠ affiliates, their distributors, and their respective employees, representatives and/or insurance agents do not provide tax, accounting or legal advice.

NAICS: 52
NAICS Definition: Finance and Insurance
Employees: 10,643
Subsidiaries: 0
12-month incidents
0
Known data breaches
9
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/defaultcompany.jpeg
Carruth Compliance
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/lincolnfinancial.jpeg
Lincoln Financial
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
Carruth Compliance
100%
Compliance Rate
0/4 Standards Verified
Lincoln Financial
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for Carruth Compliance in 2025.

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for Lincoln Financial in 2025.

Incident History — Carruth Compliance (X = Date, Y = Severity)

Carruth Compliance cyber incidents detection timeline including parent company and subsidiaries

Incident History — Lincoln Financial (X = Date, Y = Severity)

Lincoln Financial cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/defaultcompany.jpeg
Carruth Compliance
Incidents

Date Detected: 12/2024
Type:Breach
Blog: Blog

Date Detected: 12/2024
Type:Breach
Motivation: Data Theft
Blog: Blog
https://images.rankiteo.com/companyimages/lincolnfinancial.jpeg
Lincoln Financial
Incidents

Date Detected: 12/2024
Type:Breach
Attack Vector: Unauthorized Access
Blog: Blog

Date Detected: 5/2024
Type:Breach
Blog: Blog

Date Detected: 11/2023
Type:Breach
Attack Vector: Inadvertent Disclosure
Blog: Blog

FAQ

Carruth Compliance company demonstrates a stronger AI Cybersecurity Score compared to Lincoln Financial company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Lincoln Financial company has faced a higher number of disclosed cyber incidents historically compared to Carruth Compliance company.

In the current year, Lincoln Financial company and Carruth Compliance company have not reported any cyber incidents.

Neither Lincoln Financial company nor Carruth Compliance company has reported experiencing a ransomware attack publicly.

Both Lincoln Financial company and Carruth Compliance company have disclosed experiencing at least one data breach.

Neither Lincoln Financial company nor Carruth Compliance company has reported experiencing targeted cyberattacks publicly.

Neither Carruth Compliance company nor Lincoln Financial company has reported experiencing or disclosing vulnerabilities publicly.

Neither Carruth Compliance nor Lincoln Financial holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Carruth Compliance company nor Lincoln Financial company has publicly disclosed detailed information about the number of their subsidiaries.

Lincoln Financial company employs more people globally than Carruth Compliance company, reflecting its scale as a Financial Services.

Neither Carruth Compliance nor Lincoln Financial holds SOC 2 Type 1 certification.

Neither Carruth Compliance nor Lincoln Financial holds SOC 2 Type 2 certification.

Neither Carruth Compliance nor Lincoln Financial holds ISO 27001 certification.

Neither Carruth Compliance nor Lincoln Financial holds PCI DSS certification.

Neither Carruth Compliance nor Lincoln Financial holds HIPAA certification.

Neither Carruth Compliance nor Lincoln Financial 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.