While DataDome performs very well overall, there are a few areas where improvements would make it even more effective in a telecom environment. One point is better handling of false positives. Although it is generally very accurate, in some cases, legitimate users or internal systems get flagged, especially corporate VPN users, internal testing tools, and partner integrations. The improvement would be a more granular and easier whitelisting mechanism and better transparency on why a request was blocked. Another point is more detailed analytics and custom reporting. The current dashboards are good, but sometimes detailed analysis is limited. Custom reporting options are not very flexible. As part of improvement, more customizable dashboards can be made, along with the ability to create business-specific reports, for each API and per region. Better visibility for API-level protection can also be developed. The protection works well, but debugging blocked API requests can take time and is not always easy to trace the exact reason for blocking, thus requiring more detailed logs and traceability for API traffic, along with easier correlation with backend systems. The integration with the existing security ecosystem can also be improved.
Needed improvements could focus on specific aspects that impact my workflow, enabling even more streamlined processes. To rate DataDome a ten, it would need to improve in certain areas or add features that enhance its efficiency and usability even further.
The solution catches and perfectly blocks traffic from malicious IPs. DataDome does not catch legitimate IPs during traffic analysis, even when the traffic exceeds the threshold value.
Bot Management provides a defense mechanism against malicious internet bots, essential for protecting online assets and ensuring optimal application performance by differentiating automated traffic from legitimate user interactions.This solution equips organizations with tools to mitigate unwanted bot traffic, preserving website integrity and user experience. Advanced capabilities enable the detection and neutralization of bot-driven threats, such as credential stuffing and price scraping,...
While DataDome performs very well overall, there are a few areas where improvements would make it even more effective in a telecom environment. One point is better handling of false positives. Although it is generally very accurate, in some cases, legitimate users or internal systems get flagged, especially corporate VPN users, internal testing tools, and partner integrations. The improvement would be a more granular and easier whitelisting mechanism and better transparency on why a request was blocked. Another point is more detailed analytics and custom reporting. The current dashboards are good, but sometimes detailed analysis is limited. Custom reporting options are not very flexible. As part of improvement, more customizable dashboards can be made, along with the ability to create business-specific reports, for each API and per region. Better visibility for API-level protection can also be developed. The protection works well, but debugging blocked API requests can take time and is not always easy to trace the exact reason for blocking, thus requiring more detailed logs and traceability for API traffic, along with easier correlation with backend systems. The integration with the existing security ecosystem can also be improved.
Needed improvements could focus on specific aspects that impact my workflow, enabling even more streamlined processes. To rate DataDome a ten, it would need to improve in certain areas or add features that enhance its efficiency and usability even further.
The solution catches and perfectly blocks traffic from malicious IPs. DataDome does not catch legitimate IPs during traffic analysis, even when the traffic exceeds the threshold value.