Comparison Overview
Office of Liquor and Gaming Regulation QLD (OLGR)
Office of Liquor and Gaming Regulation QLD (OLGR)
63 George St, Brisbane City, 4000, AU
Last Update: 27/05/2026
The Office of Liquor and Gaming Regulation (OLGR) is responsible for regulating the Queensland liquor and gaming industry in a way compatible with minimising harm caused by these products and, maintaining the integrity and probity of the gaming industry in Queensland, a...
Queensland Government
1 William Street, Brisbane, 4000, AU
Last Update: 01/04/2026
ABOUT US We are the largest and most diverse organisation in our state. We have more than 90 government departments and organisations delivering for Queensland across 4000+ locations, from the Torres Strait to the Gold Coast; Mount Isa to Brisbane. This page is monitore...
Compliance Ranges Comparison
Office of Liquor and Gaming Regulation QLD (OLGR)
Queensland Government
Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Office of Liquor and Gaming Regulation QLD (OLGR) in 2026.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Queensland Government in 2026.
Incident History - Office of Liquor and Gaming Regulation QLD (OLGR) (X = Date, Y = Severity)
Office of Liquor and Gaming Regulation QLD (OLGR) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Queensland Government (X = Date, Y = Severity)
Queensland Government cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Office of Liquor and Gaming Regulation QLD (OLGR)
Queensland Government
FAQ
Latest Global CVEs
Pronetiqs IntraVUE versions 3.2.1a14 and prior have an inadequate encryption strength vulnerability which could allow an attacker to steal admin credentials via weak hash or a pass-the-hash attack.
Pronetiqs IntraVUE versions 3.2.1a14 and prior have an exposure of sensitive system information to an unauthorized control sphere vulnerability which could allow for asset discovery by unauthenticated users.
Pronetiqs IntraVUE versions 3.2.1a14 and prior have an unintended proxy or intermediary vulnerability which could allow an attacker to use an active proxy, which would bypass OT segmentation.
Pronetiqs IntraVUE Versions 3.2.1a14 and prior have a plaintext storage of a password vulnerability that could expose cleartext credentials through the API.
Pronetiqs IntraVUE versions 3.2.1a14 and prior have an exposure of sensitive system information to an unauthorized control sphere vulnerability which could expose the underlying host/share filesystem.