Comparison Overview

diHouse

VS

Pogo Linux, Inc.

diHouse

Мурманский проезд 14к1, Москва, RU
Last Update: 2025-11-27
Between 750 and 799

diHouse is one of the leaders on the Russian IT-distribution market. The company is engaged in distribution, retail and corporate supplies of smartphones, mobile and desktop computers, household appliances, equipment for gamers, digital gadgets and accessories. It's network of partners includes all federal and most of regional retailers of Russia and countries of the CIS. Constantly moving forward, we offer our partners high-quality products and services in logistic, finance, marketing and multifunctional sales support. diHouse was founded in 1996. Email: [email protected]

NAICS: None
NAICS Definition: Others
Employees: 75
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Pogo Linux, Inc.

906 Industry Drive, Tukwila, Washington, 98188, US
Last Update: 2025-11-27
Between 750 and 799

Founded in 1999, Pogo Linux is a robust provider of server and storage products that leads the industry in reliability and quality. Our product line is unique because it offers products for all levels of the IT infrastructure, from workstations to entry level servers to advanced storage solutions. By offering a broad base of products, and holding each one to the esteemed Pogo Linux standard of quality and reliability, the company is well-positioned to help a broad profile of customers.

NAICS: None
NAICS Definition:
Employees: 17
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/dihouse.jpeg
diHouse
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/pogo-linux.jpeg
Pogo Linux, 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
diHouse
100%
Compliance Rate
0/4 Standards Verified
Pogo Linux, Inc.
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Computer Hardware Industry Average (This Year)

No incidents recorded for diHouse in 2025.

Incidents vs Computer Hardware Industry Average (This Year)

No incidents recorded for Pogo Linux, Inc. in 2025.

Incident History — diHouse (X = Date, Y = Severity)

diHouse cyber incidents detection timeline including parent company and subsidiaries

Incident History — Pogo Linux, Inc. (X = Date, Y = Severity)

Pogo Linux, Inc. cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/dihouse.jpeg
diHouse
Incidents

No Incident

https://images.rankiteo.com/companyimages/pogo-linux.jpeg
Pogo Linux, Inc.
Incidents

No Incident

FAQ

Both diHouse company and Pogo Linux, Inc. company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, Pogo Linux, Inc. company has disclosed a higher number of cyber incidents compared to diHouse company.

In the current year, Pogo Linux, Inc. company and diHouse company have not reported any cyber incidents.

Neither Pogo Linux, Inc. company nor diHouse company has reported experiencing a ransomware attack publicly.

Neither Pogo Linux, Inc. company nor diHouse company has reported experiencing a data breach publicly.

Neither Pogo Linux, Inc. company nor diHouse company has reported experiencing targeted cyberattacks publicly.

Neither diHouse company nor Pogo Linux, Inc. company has reported experiencing or disclosing vulnerabilities publicly.

Neither diHouse nor Pogo Linux, Inc. holds any compliance certifications.

Neither company holds any compliance certifications.

Neither diHouse company nor Pogo Linux, Inc. company has publicly disclosed detailed information about the number of their subsidiaries.

diHouse company employs more people globally than Pogo Linux, Inc. company, reflecting its scale as a Computer Hardware.

Neither diHouse nor Pogo Linux, Inc. holds SOC 2 Type 1 certification.

Neither diHouse nor Pogo Linux, Inc. holds SOC 2 Type 2 certification.

Neither diHouse nor Pogo Linux, Inc. holds ISO 27001 certification.

Neither diHouse nor Pogo Linux, Inc. holds PCI DSS certification.

Neither diHouse nor Pogo Linux, Inc. holds HIPAA certification.

Neither diHouse nor Pogo Linux, Inc. holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.16, 20.3.14, and 21.0.1, there is a XSRF token leakage via protocol-relative URLs in angular HTTP clients. The vulnerability is a Credential Leak by App Logic that leads to the unauthorized disclosure of the Cross-Site Request Forgery (XSRF) token to an attacker-controlled domain. Angular's HttpClient has a built-in XSRF protection mechanism that works by checking if a request URL starts with a protocol (http:// or https://) to determine if it is cross-origin. If the URL starts with protocol-relative URL (//), it is incorrectly treated as a same-origin request, and the XSRF token is automatically added to the X-XSRF-TOKEN header. This issue has been patched in versions 19.2.16, 20.3.14, and 21.0.1. A workaround for this issue involves avoiding using protocol-relative URLs (URLs starting with //) in HttpClient requests. All backend communication URLs should be hardcoded as relative paths (starting with a single /) or fully qualified, trusted absolute URLs.

Risk Information
cvss4
Base: 7.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/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

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Uncontrolled Recursion vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft deep ASN.1 structures that trigger unbounded recursive parsing. This leads to a Denial-of-Service (DoS) via stack exhaustion when parsing untrusted DER inputs. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 8.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/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

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Integer Overflow vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft ASN.1 structures containing OIDs with oversized arcs. These arcs may be decoded as smaller, trusted OIDs due to 32-bit bitwise truncation, enabling the bypass of downstream OID-based security decisions. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 6.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/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

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. Prior to versions 7.0.13 and 8.0.2, working with large buffers in Lua scripts can lead to a stack overflow. Users of Lua rules and output scripts may be affected when working with large buffers. This includes a rule passing a large buffer to a Lua script. This issue has been patched in versions 7.0.13 and 8.0.2. A workaround for this issue involves disabling Lua rules and output scripts, or making sure limits, such as stream.depth.reassembly and HTTP response body limits (response-body-limit), are set to less than half the stack size.

Risk Information
cvss3
Base: 7.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Description

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. In versions from 8.0.0 to before 8.0.2, a NULL dereference can occur when the entropy keyword is used in conjunction with base64_data. This issue has been patched in version 8.0.2. A workaround involves disabling rules that use entropy in conjunction with base64_data.

Risk Information
cvss3
Base: 7.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H