Azure Findings Show as UNKNOWN Even With Full Permissions

Open
#2,160 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
azure, javascript
Domain
cloud, security

Research direction

Start by locating the Azure evaluation entry points for the ACL-related checks and the named Key Vault checks: keyExpirationEnabled, secretExpirationEnabled, rsaCertificateKeySize, and keyVaultKeyExpiryNonRbac. Reproduce the UNKNOWN results with absent Storage services and RBAC-authorized vaults, then determine whether those cases should be reported as FAIL and verify the resulting findings.

Written by the indexing model from the issue text.

Description

I’m seeing many Azure findings consistently showing as UNKNOWN even after applying all required Storage and Key Vault permissions.

This is not an IAM issue. Based on verification:

  • The Storage Accounts do not have File/Queue/Table services enabled, but CloudSploit still marks ACL-related checks as UNKNOWN instead of FAIL.
  • The Key Vaults are using RBAC authorisation and contain no keys/secrets/certificates with expiry, causing checks like keyExpirationEnabled, secretExpirationEnabled, rsaCertificateKeySize, and keyVaultKeyExpiryNonRbac to always return UNKNOWN.

The results do not change.

This looks like a CloudSploit evaluation logic issue, not a permissions gap.

Please confirm if these checks should return FAIL when the underlying Azure service/config isn’t present or when the vault uses RBAC mode.

Dominant language
JavaScript
Stars
3.8k
Forks
751
Avg merge
7d 59m
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aquasecurity/cloudsploit

All issues in aquasecurity/cloudsploit

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.