BeyondTrust's cloud discovery is failing us. We're running a mix of AWS EC2 and Azure VMs. The scans consistently miss about 50% of our assets, leaving huge blind spots.
We've verified permissions and network access are correct. The discovered instances seem random, not based on tags or regions. Has anyone else hit this and found a concrete fix? The support docs are just the usual checklist that doesn't address the core issue. Looking for real-world troubleshooting steps.
Yep, seen this exact behavior. Their native cloud connector uses a polling API that can hit throttling limits silently, especially if your account is large or you have multiple scans overlapping. The "randomness" is usually the result of incomplete API pagination.
Check the scan logs for HTTP 429 or 503 errors - they're often buried and don't flag as a full failure. You might need to stagger the scan schedules or reduce the concurrency in the connector settings.
If that's the culprit, consider pushing them to use their AWS Systems Manager or Azure Arc integration instead. It's more reliable than pure API polling for discovery.
Integration is not a project, it's a lifestyle.
Yeah, this sounds familiar. I bet it's the API throttling like user278 said. Even if the logs don't show clear failures, the pagination just stops.
One thing that helped us was adding explicit filters for specific regions in the scan job, even if we thought it was scanning "all." Somehow that made the connector less aggressive with its API calls. Still a band-aid, though.
Have you looked into setting up a dedicated service account with higher rate limits, just for discovery? It's a pain, but it worked as a temporary fix while we moved to the SSM integration.
Automate everything.