Rankiteo Logo
Rankiteo
Leader in Cyber Underwriting
Loading...
NEWRankiteo Cyber Underwriting Desktop - Score, price, and bind from your desktop
WindowsmacOSLinux
Download

Comparison Overview

Queensland CommunicationsQueensland Communications
VS
yesyes
Queensland Communications

Queensland Communications

36 Eagleview Place, Eagle Farm, 4009, AU

Last Update: 14/04/2026

View Profile
Between 600 and 649
http://qldcom.com
635/1000Poor

If you’re a leader in your field, you need to make strong decisions, be accountable and deliver on your promises. Queensland Communications gives you the visibility to understand your terrain and the tools to communicate with clarity. Our two way radio systems and infr...

NAICS:517
NAICS Definition:Telecommunications
Employees:6
Subsidiaries:0
12-month incidents
1
Known data breaches
0
Attack type number
1
yes

yes

Ha-Yozma St 6, Kfar Saba, 4442218, IL

Last Update: 02/04/2026

View Profile
Between 750 and 799
https://career.yes.co.il/
768/1000Fair

תכירו את השחקנים הראשיים שלנו: העובדות והעובדים. אנחנו לא עובדים עם תסריט קבוע, חושבים מחוץ לקופסא, ומייצרים ז'אנר משלנו. כש-יס קמה, בשנת 1998, הבאנו את בשורת הלווין אל עולם שידורי הטלוויזיה והיינו הראשונים להציע שידורים דיגיטליים ושירותי טלוויזיה אינטראקטיביים - כשבח...

NAICS:517
NAICS Definition:Telecommunications
Employees:13,623
Subsidiaries:0
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Ranges Comparison

Based On Specific Ai Models Category
Queensland Communications

Queensland Communications

-
ISO 27001Not verified
ISO 27001
-
SOC2 Type 1Not verified
SOC2 Type 1
-
SOC2 Type 2Not verified
SOC2 Type 2
-
GDPRNot verified
GDPR
-
PCI DSSNot verified
PCI DSS
-
HIPAANot verified
HIPAA
yes

yes

-
ISO 27001Not verified
ISO 27001
-
SOC2 Type 1Not verified
SOC2 Type 1
-
SOC2 Type 2Not verified
SOC2 Type 2
-
GDPRNot verified
GDPR
-
PCI DSSNot verified
PCI DSS
-
HIPAANot verified
HIPAA

Benchmark & Cyber Underwriting Signals

Incidents vs Telecommunications Industry Avg (This Year)

Queensland Communications has 47.37% fewer incidents than the average of same-industry companies with at least one recorded incident.

Incidents

Incidents vs Telecommunications Industry Avg (This Year)

No incidents recorded for yes in 2026.

Incidents

Incident History - Queensland Communications (X = Date, Y = Severity)

Queensland Communications cyber incidents detection timeline including parent company and subsidiaries.

R - Ransomware
C - Cyber Attack
D - Data Breach
V - Vulnerability

Incident History - yes (X = Date, Y = Severity)

yes cyber incidents detection timeline including parent company and subsidiaries.

No timeline data available
R - Ransomware
C - Cyber Attack
D - Data Breach
V - Vulnerability

Notable Incidents

Last Cyber / HR Incidents / Global...
Queensland Communications

Queensland Communications

Incidents
🔒 Incident : Ransomware
QUEMAS1776133442
yes

yes

Incidents
No explicit notable incidents reported.

FAQ

Between Queensland Communications company and yes company, which one has the best AI Cybersecurity Score ?
Between Queensland Communications company and yes company, which one has experienced more cyber incidents in the past ?
Between Queensland Communications company and yes company, which one has experienced more cyber incidents this year ?
Between Queensland Communications company and yes company, which one has experienced at least one ransomware attack ?
Between Queensland Communications company and yes company, which one has experienced at least one data breach ?
Between Queensland Communications company and yes company, which one has experienced at least one targeted cyberattack ?
Between Queensland Communications company and yes company, which one has experienced at least one vulnerability ?
Between Queensland Communications company and yes company, which one holds the most compliance certifications ?
Between Queensland Communications company and yes company, which one holds the fewest compliance certifications ?
Between Queensland Communications company and yes company, which one has the most subsidiaries ?
Between Queensland Communications company and yes company, which one has the largest number of employees ?
Between Queensland Communications and yes, which company holds both SOC 2 Type 1 certifications ?
Between Queensland Communications and yes, which company holds both SOC 2 Type 2 certifications ?
Which company is ISO 27001 certified - Queensland Communications or yes ?
Which company is PCI DSS compliant - Queensland Communications or yes ?
Between Queensland Communications and yes, which company complies with HIPAA regulations for healthcare data ?
Between Queensland Communications and yes, which company complies with GDPR requirements ?

Latest Global CVEs

CVE-2026-66591
SUMMARY

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in David Lingren Media LIbrary Assistant allows Stored XSS. This issue affects Media LIbrary Assistant: from n/a through 3.39.

PUBLISHED
Date2026-08-18
UPDATED
Date2026-08-18
RISK INFORMATION (Score: 6.5)
CVSS3
Base Score: 6.5
Complexity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L
IMPACT SCORE
3.7
EXPLOITABILITY
2.3
CVE-2026-66589
SUMMARY

Missing Authorization vulnerability in Kings Plugins B2BKing allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects B2BKing: from n/a through 5.2.30.

PUBLISHED
Date2026-08-18
UPDATED
Date2026-08-18
RISK INFORMATION (Score: 5.4)
CVSS3
Base Score: 5.4
Complexity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
IMPACT SCORE
2.5
EXPLOITABILITY
2.8
CVE-2026-27365
SUMMARY

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in PublishPress PublishPress Series allows Stored XSS. This issue affects PublishPress Series: from n/a through 2.17.0.

PUBLISHED
Date2026-08-18
UPDATED
Date2026-08-18
RISK INFORMATION (Score: 5.9)
CVSS3
Base Score: 5.9
Complexity: LOW
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L
IMPACT SCORE
3.7
EXPLOITABILITY
1.7
CVE-2026-73974
SUMMARY

linuxfabrik-lib provides Python modules for database access, caching, shell execution, and API integrations, and Linuxfabrik Monitoring Plugins uses its shared testing helper across check plugins. Prior to linuxfabrik-lib 6.1.0 and Linuxfabrik Monitoring Plugins 7.0.0, lib.lftest.test() treated the first or second element of a --test CSV argument as a filesystem path and returned the file contents as simulated standard output or standard error without path confinement. The hidden but production-accessible --test argument was accepted by sudo-authorized plugins, so an attacker controlling the nagios or icinga account could use check-plugins/deb-updates/deb-updates with its default QUERY=1 to disclose every line of a root-readable file. Approximately 22 other plugins exposed filtered content or a root file existence and readability oracle through the same helper, while check-plugins/network-bonding/network-bonding and check-plugins/openstack-swift-stat/openstack-swift-stat had direct read paths that bypassed the helper. The library fix confines fixture reads to the invoking plugin's unit-test directory and refuses unsafe anchors, and the plugin fix routes the two bypasses through that helper. These issues are fixed in linuxfabrik-lib 6.1.0 and Linuxfabrik Monitoring Plugins 7.0.0.

PUBLISHED
Date2026-08-18
UPDATED
Date2026-08-18
RISK INFORMATION (Score: 5.5)
CVSS3
Base Score: 5.5
Complexity: LOW
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
IMPACT SCORE
3.6
EXPLOITABILITY
1.8
CVE-2026-73973
SUMMARY

Linuxfabrik Monitoring Plugins provides monitoring plugins for Icinga, Nagios, and related systems. Prior to version 7.0.0, check-plugins/logfile/logfile accepted a free-form --filename path and opened it as root when invoked through the shipped nagios or icinga sudoers allowlist, without confining the resolved path to /var/log. An attacker who controls the monitoring account can select a root-readable file such as /etc/shadow and use --warning-regex . while leaving SUPPRESS_OUTPUT false, causing each nonempty line to be collected in warn_matches and returned through lib.base.oao(). The vulnerable flow passes the expanded scan_path directly to open(), and neither real-path containment nor an allowlist protects the sink. The same fix also confines mysql-logfile and openvpn-client-list paths, allows only documented log roots, and resolves symlinks and parent-directory traversal before checking containment. This issue is fixed in version 7.0.0.

PUBLISHED
Date2026-08-18
UPDATED
Date2026-08-18
RISK INFORMATION (Score: 5.5)
CVSS3
Base Score: 5.5
Complexity: LOW
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
IMPACT SCORE
3.6
EXPLOITABILITY
1.8