You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the rate limit is reached when querying the Hybrid Analysis service, the analyzer return a successful state instead of an error, like the VirusTotal analyzer for example.
I know that with Cortex 2, rate limit can be handled in the configuration, but the analyzer shoudl still alert for this kind of problem instead of letting go smoothly the fact that the query failed.
Steps to Reproduce
(keep this section only if the issue relates to a bug)
Reach your limit of query for the Hybrid Analysis service
Submit a new job with the analyzer
See the job set as successful even if the result states the rate limit was reached
Possible Solutions
Apply a logic similar to the VirusTotal analyzer and trigger an error if the rate limit is reached.
Complementary information
Current report when the rate limiter is triggered:
{
"artifacts": [],
"full": {
"results": {
"response_code": -1,
"response": {
"error": "Exceeded maximum API requests per minute (5). Please try again later or contact support for other options."
}
}
},
"summary": {},
"success": true
}
Expected report when rate limiter is triggered
{
"errorMessage": "Exceeded maximum API requests per minute (5). Please try again later or contact support for other options.",
"input": {
"dataType": "hash",
"config": {
"max_tlp": 3,
"check_tlp": true,
"service": "get",
"key": "REMOVED"
},
"tlp": 2,
"data": "[redacted]"
},
"success": false
}
The text was updated successfully, but these errors were encountered:
@saadkadhi This is an issue on the Analyzer side that doesn't handle the "Hybrid Analysis" rate limit reached error. It's not related to the rate limiting configured on Cortex.
Request Type
Bug
Work Environment
Description
If the rate limit is reached when querying the Hybrid Analysis service, the analyzer return a
successful
state instead of an error, like the VirusTotal analyzer for example.I know that with Cortex 2, rate limit can be handled in the configuration, but the analyzer shoudl still alert for this kind of problem instead of letting go smoothly the fact that the query failed.
Steps to Reproduce
(keep this section only if the issue relates to a bug)
Possible Solutions
Apply a logic similar to the VirusTotal analyzer and trigger an error if the rate limit is reached.
Complementary information
Current report when the rate limiter is triggered:
Expected report when rate limiter is triggered
The text was updated successfully, but these errors were encountered: