Comparison Overview
Cisco Industrial IoT

Cisco Industrial IoT
170 West Tasman Dr., San Jose, California, US, 95134
Last Update: 17/01/2026
At Cisco Industrial IoT, we accelerate digital transformation by simplifying IT for industrial networks. We promote the connectivity of assets, applications, and data in real time. By offering end-to-end solutions, we empower businesses to drive change and achieve outst...

Persistent Systems
Bhageerath, 402 E, Senapati Bapat Road, Pune, Maharashtra, IN, 411016
Last Update: 02/04/2026
We are an AI-led, platform-driven Digital Engineering and Enterprise Modernization partner, combining deep technical expertise and industry experience to help our clients anticipate what’s next. Our offerings and proven solutions create a unique competitive advantage fo...
Compliance Ranges Comparison

Cisco Industrial IoT







Persistent Systems






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Cisco Industrial IoT in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Persistent Systems in 2026.
Incident History - Cisco Industrial IoT (X = Date, Y = Severity)
Cisco Industrial IoT cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Persistent Systems (X = Date, Y = Severity)
Persistent Systems cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Cisco Industrial IoT

Persistent Systems
FAQ
Latest Global CVEs
An authenticated user with the read role may read limited amounts of uninitialized stack memory via specially-crafted issuances of the filemd5 command
The $_internalApplyOplogUpdate aggregation pipeline stage can be used to execute a document diff containing a malformed binary diff to return memory out-of-bounds or crash the server. $_internalApplyOplogUpdate can be executed by any authenticated user with access to the aggregate command.
An authorized user could trigger a server crash by running a query with a 2dsphere index on a field that stores a GeoJSON GeometryCollection containing a Polygon with a strict-winding CRS. Strict-winding polygons are intentionally unsupported for indexing, but the guard that rejects them does not inspect members of a GeometryCollection, allowing the unsafe path to be reached which ends with an ensuing null-pointer dereference.
The ldapQueryPassword parameter, when set through the runtime setParameter command, will log the new password to the mongod.log file in plain text.
An authenticated user can cause a MongoDB server to crash or return incorrect results by creating documents that interfere with internal metadata processing during query execution. This stems from insufficient separation between user-controlled document fields and internal metadata in certain execution paths.