Comparison Overview
Incessant Technologies is now Coforge

Incessant Technologies is now Coforge
Survey No: 109,110,111/112, Gachibowli,Hyderabad, Telangana, 500032, IN
Last Update: 27/10/2025
Incessant Technologies, an NIIT Technologies company, is a leader in Digital Integration and agile delivery of enterprise iBPM solutions. With proven expertise in leading IT solutions involving iBPM, CRM, Case Management, ECM, Middleware, Analytics & Decisioning deliver...

NTT DATA Business Solutions
Königsbreede 1, Bielefeld, 33605, DE
Last Update: 02/04/2026
We understand the business of our clients and know what it takes to transform it into the future. At NTT DATA Business Solutions, we drive innovation – from advisory and implementation to managed services and beyond. With SAP at our core and a powerful ecosystem of part...
Compliance Ranges Comparison

Incessant Technologies is now Coforge







NTT DATA Business Solutions






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Incessant Technologies is now Coforge in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for NTT DATA Business Solutions in 2026.
Incident History - Incessant Technologies is now Coforge (X = Date, Y = Severity)
Incessant Technologies is now Coforge cyber incidents detection timeline including parent company and subsidiaries.
Incident History - NTT DATA Business Solutions (X = Date, Y = Severity)
NTT DATA Business Solutions cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Incessant Technologies is now Coforge

NTT DATA Business Solutions
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.