Comparison Overview
NTT DATA Business Solutions
NTT DATA Business Solutions
Königsbreede 1, Bielefeld, 33605, DE
Last Update: 08/09/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...
IGT Solutions
Sector 32 Road, Plot 49, Echelon Building, Gurugram, Haryana, IN, 122 001
Last Update: 14/09/2026
IGT Solutions is a next-gen customer experience (CX) company, defining and delivering AI-led transformative experiences for the global and most innovative brands using digital technologies. With the combination of Digital and Human Intelligence, IGT becomes the preferre...
Compliance Ranges Comparison
NTT DATA Business Solutions
IGT Solutions
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for NTT DATA Business Solutions in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for IGT Solutions in 2026.
Incident History - NTT DATA Business Solutions (X = Date, Y = Severity)
NTT DATA Business Solutions cyber incidents detection timeline including parent company and subsidiaries.
Incident History - IGT Solutions (X = Date, Y = Severity)
IGT Solutions cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
NTT DATA Business Solutions
IGT Solutions
FAQ
Latest Global CVEs
vLLM through 0.29.0 fails to properly clean up decode-side metadata for rejected inference requests in prefill/decode disaggregated deployments. Remote attackers can submit requests with max_tokens=0 to exhaust decode-worker memory without bound until the worker restarts.
- https://github.com/vllm-project/vllm
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/v1/nixl/push_worker.py#L162-L181
- https://github.com/vllm-project/vllm/pull/55677
- https://www.vulncheck.com/advisories/vllm-through-0.29.0-memory-exhaustion-via-rejected-requests
redis-parser through 3.0.0 contains a denial of service vulnerability in the RESP protocol parser that allows malicious Redis endpoints to crash the client process through unbounded recursion on nested arrays. Attackers can send crafted RESP byte streams with repeated array headers that exhaust the V8 call stack, causing an uncaught RangeError that terminates the Node.js process without triggering error handling callbacks.
- https://github.com/NodeRedis/node-redis-parser
- https://github.com/NodeRedis/node-redis-parser/blob/701655430f5f7d9ca00892a02f7eefcbc1193a98/lib/parser.js#L204-L213
- https://github.com/NodeRedis/node-redis-parser/blob/701655430f5f7d9ca00892a02f7eefcbc1193a98/lib/parser.js#L291-L306
- https://github.com/redis/ioredis/issues/2108
- https://www.vulncheck.com/advisories/redis-parser-through-3.0.0-denial-of-service-via-unbounded-recursion
Improper neutralization of special elements in output used by a downstream component ('injection') in Azure Cosmos DB allows an authorized attacker to elevate privileges over a network.
Server-side request forgery (ssrf) in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.
Missing authentication for critical function in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.