What Are Infra Tests?
Once you've connected your infrastructure to ComplyJet, we automatically run a set of automated security tests across your production resources. These tests are designed to check whether your systems meet industry-standard best practices for availability, access control, encryption, and more.
Each test directly maps to one or more controls from popular frameworks like SOC 2 or ISO 27001. That means when you fix these issues, you're not just improving security — you're also progressing toward compliance.
Tests Page
On the Tests page, you'll see a full list of all checks ComplyJet has run on your infrastructure. These are automatically updated as your environment changes.
Your job is straightforward:
Review the list of tests
Prioritize fixing the ones that are in a failing state
Use the remediation steps provided to fix each one
Each test shows its current status (e.g., Passing, Failing, Pending), how many resources were checked, and when it was last run.
Fixing a Failing Test (Step-by-Step)
Click on any failing test to open a detailed view. There, you'll see:
When the test was last run
How many production resources it was applied to
What exactly failed and why
For example, a test might report that Cloud SQL storage utilization alerts are not configured for certain production databases. This means there’s no alert in place to notify your team if the database starts running out of space — which could lead to downtime or data issues. Below the issue, you’ll find step-by-step remediation instructions to fix it — including the exact settings to check in the Google Cloud Console and how to set up the right alert policies.
Once you've resolved the issue, simply click "Trigger Run". If everything checks out, the test will update to a Passing state — and just like that, you've completed one more piece of automated audit evidence.
Keep Things Green
The more tests you fix, the stronger your compliance posture becomes. We recommend checking this page regularly, especially after infrastructure changes or before an audit milestone.
Staying on top of failing tests ensures your systems are secure, your evidence is up to date, and your team stays audit-ready with less manual effort.