Comparison Overview
Bureau Veritas | Oil Condition Monitoring

Bureau Veritas | Oil Condition Monitoring
12715 Royal Drive, Stafford, TX, 77477, US
Last Update: 02/02/2026
Oil analysis is essential to optimal equipment performance. Equipment reliability starts with a consistent oil analysis program. Bureau Veritas’ global network of state-of-the-art testing facilities provides accurate, reliable results you can depend on to keep your mach...

Oxy
Houston, 77046, US
Last Update: 01/04/2026
Oxy is an international energy company with assets primarily in the United States, the Middle East and North Africa. We are one of the largest oil producers in the U.S., including a leading producer in the Permian and DJ basins, and offshore Gulf of Mexico. Our midstrea...
Compliance Ranges Comparison

Bureau Veritas | Oil Condition Monitoring







Oxy






Benchmark & Cyber Underwriting Signals
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for Bureau Veritas | Oil Condition Monitoring in 2026.
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for Oxy in 2026.
Incident History - Bureau Veritas | Oil Condition Monitoring (X = Date, Y = Severity)
Bureau Veritas | Oil Condition Monitoring cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Oxy (X = Date, Y = Severity)
Oxy cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Bureau Veritas | Oil Condition Monitoring

Oxy
FAQ
Latest Global CVEs
Improper access control in Microsoft Edge for Android allows an unauthorized attacker to bypass a security feature over a network.
A security vulnerability has been detected in NousResearch hermes-agent up to 2026.4.30. Affected is the function GatewayStreamConsumer._filter_and_accumulate of the file gateway/stream_consumer.py of the component Streaming Reasoning Tag Filter. The manipulation leads to improper handling of case sensitivity. The attack may be initiated remotely. The attack's complexity is rated as high. The exploitability is told to be difficult. The exploit has been disclosed publicly and may be used. The project decided to not implement a dedicated fix: "[T]he analysis and the fix are both sound. It just lands below the bar for the maintenance cost of a duplicated scrub path."
- https://gist.github.com/YLChen-007/2229e5505bcbb3e15a7ae8fba4c4be37
- https://github.com/NousResearch/hermes-agent/
- https://github.com/NousResearch/hermes-agent/issues/27288
- https://github.com/NousResearch/hermes-agent/pull/28631#issuecomment-4622188016
- https://vuldb.com/cve/CVE-2026-14617
- https://vuldb.com/submit/844654
- https://vuldb.com/vuln/376134
- https://vuldb.com/vuln/376134/cti
Insufficient ui warning of dangerous operations in Microsoft Edge (Chromium-based) allows an unauthorized attacker to perform spoofing over a network.
Improper neutralization of input during web page generation ('cross-site scripting') in Microsoft Edge (Chromium-based) allows an unauthorized attacker to perform spoofing over a network.
Relative path traversal in Microsoft Edge for Android allows an unauthorized attacker to disclose information locally.