Inspector Not Enabled
Nothing is scanning these workloads for known vulnerabilities, so a published CVE stays unpatched until someone happens to look.
Free to start. No card. The playground just needs your work email.
AWS
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across AWS, with read-only access to the account.
Explain
Every finding says exactly what to change: Enable Amazon Inspector.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- Inspector on AWS
- The fix, by hand
- Inspector → Account management → Activate → choose all scan types (EC2, ECR, Lambda standard + code).
- Inspector charges per scanned resource; for very large fleets, enable only the scan types you act on.
- Review the first wave of Critical / High findings. Prioritize by exploitability + exposure.
- EventBridge rule → forward Critical / High findings to your ticketing system.
- Enable across active regions; delegate the Inspector admin to a central account via AWS Organizations if you have multiple accounts.
These are the steps the finding carries in the product.
- Category
- Compliance. Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.
- Where it appears
- The Compliance tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1101- Full reference
Related checks
See the compliance findings in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.