Comparison Overview
Québec Government Office in Houston

Québec Government Office in Houston
4265 San Felipe St, Houston, 77027, US
Last Update: 02/04/2026
The Québec Government Office in Houston is supporting and promoting the development of business projects between organizations from Quebec and Texas / Louisiana / Oklahoma / Arkansas. The Québec Trade Office is working closely with numerous partners in such high-tech se...

State of Michigan
State Capitol, Lansing, Michigan, US, 48913
Last Update: 01/04/2026
Every day the contributions and achievements of State of Michigan employees have a direct impact on over 10 million Michiganders across the state. If you're looking for a fulfilling career in state government that can make a real difference in the lives of others, you c...
Compliance Ranges Comparison

Québec Government Office in Houston







State of Michigan






Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Québec Government Office in Houston in 2026.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for State of Michigan in 2026.
Incident History - Québec Government Office in Houston (X = Date, Y = Severity)
Québec Government Office in Houston cyber incidents detection timeline including parent company and subsidiaries.
Incident History - State of Michigan (X = Date, Y = Severity)
State of Michigan cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Québec Government Office in Houston

State of Michigan
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.