Comparison Overview

David Charles Osborne

VS

Glencom Systems, Inc.

David Charles Osborne

K St SE, Washington, US
Last Update: 2025-11-29
View Profile
Between 750 and 799
http://WWW.DavidOsborne.net

David Charles Osborne - call me “ Oz “ — UPDATED: March 2025. Still working on building a world renown network of professional Cyber Security Teams to respond to the demand for expert analysis of ANY organization’s computer network —. public or private sector. Provide a custom built Team that will provide customer with comprehensive Penetration Testing and expert analysis of the effectiveness of your physical security and cyber security policies and procedures.

NAICS: 51125
NAICS Definition: Software Publishers
Employees: 9
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0
View Profile

Glencom Systems, Inc.

undefined, undefined, undefined, 07036, US
Last Update: 2025-11-27
Between 750 and 799
http://www.glen.com

Glencom Systems, Inc. is a value added provider of internetworking and security solutions for business, nonprofit and educational organizations. Our mission has changed little since our founding in 1986 -- to help our customers use networking as a strategic asset, to help them serve their customers better, and to improve their operational efficiency and bottom line.

NAICS: None
NAICS Definition:
Employees: 8
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/zurvita_3.jpeg
David Charles Osborne
—
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/glencom-systems-inc..jpeg
Glencom Systems, Inc.
—
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
David Charles Osborne
100%
Compliance Rate
0/4 Standards Verified
Glencom Systems, Inc.
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Computer Networking Products Industry Average (This Year)

No incidents recorded for David Charles Osborne in 2025.

Incidents vs Computer Networking Products Industry Average (This Year)

No incidents recorded for Glencom Systems, Inc. in 2025.

Incident History — David Charles Osborne (X = Date, Y = Severity)

David Charles Osborne cyber incidents detection timeline including parent company and subsidiaries

Incident History — Glencom Systems, Inc. (X = Date, Y = Severity)

Glencom Systems, Inc. cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/zurvita_3.jpeg
David Charles Osborne
Incidents

No Incident

https://images.rankiteo.com/companyimages/glencom-systems-inc..jpeg
Glencom Systems, Inc.
Incidents

No Incident

FAQ

Glencom Systems, Inc. company demonstrates a stronger AI Cybersecurity Score compared to David Charles Osborne company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Glencom Systems, Inc. company has disclosed a higher number of cyber incidents compared to David Charles Osborne company.

In the current year, Glencom Systems, Inc. company and David Charles Osborne company have not reported any cyber incidents.

Neither Glencom Systems, Inc. company nor David Charles Osborne company has reported experiencing a ransomware attack publicly.

Neither Glencom Systems, Inc. company nor David Charles Osborne company has reported experiencing a data breach publicly.

Neither Glencom Systems, Inc. company nor David Charles Osborne company has reported experiencing targeted cyberattacks publicly.

Neither David Charles Osborne company nor Glencom Systems, Inc. company has reported experiencing or disclosing vulnerabilities publicly.

Neither David Charles Osborne nor Glencom Systems, Inc. holds any compliance certifications.

Neither company holds any compliance certifications.

Neither David Charles Osborne company nor Glencom Systems, Inc. company has publicly disclosed detailed information about the number of their subsidiaries.

David Charles Osborne company employs more people globally than Glencom Systems, Inc. company, reflecting its scale as a Computer Networking Products.

Neither David Charles Osborne nor Glencom Systems, Inc. holds SOC 2 Type 1 certification.

Neither David Charles Osborne nor Glencom Systems, Inc. holds SOC 2 Type 2 certification.

Neither David Charles Osborne nor Glencom Systems, Inc. holds ISO 27001 certification.

Neither David Charles Osborne nor Glencom Systems, Inc. holds PCI DSS certification.

Neither David Charles Osborne nor Glencom Systems, Inc. holds HIPAA certification.

Neither David Charles Osborne nor Glencom Systems, Inc. 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