-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/keyvault expiration dates #1554
Open
ncc-akis
wants to merge
12
commits into
nccgroup:develop
Choose a base branch
from
ncc-akis:feature/keyvault_expiration_dates
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Feature/keyvault expiration dates #1554
ncc-akis
wants to merge
12
commits into
nccgroup:develop
from
ncc-akis:feature/keyvault_expiration_dates
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## develop #1554 +/- ##
===========================================
- Coverage 20.52% 20.39% -0.13%
===========================================
Files 384 384
Lines 13038 13121 +83
===========================================
Hits 2676 2676
- Misses 10362 10445 +83
☔ View full report in Codecov by Sentry. |
ncc-akis
force-pushed
the
feature/keyvault_expiration_dates
branch
from
July 3, 2023 15:51
8640d9a
to
8fc1adf
Compare
ncc-akis
force-pushed
the
feature/keyvault_expiration_dates
branch
from
July 4, 2023 11:14
8fc1adf
to
3986326
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
New rules to measure compliance against several Key Vault recommendations in CIS Azure Foundations Benchmark v2.0.0:
The latter rule requires a separate API request to retrieve details of each specific key. Because, for subscriptions with large numbers of keys, this could greatly increase the time required to run the tool, it currently limits the check to 3 enabled keys per vault. This sampling-based approach requires more nuance -- for subscriptions containing few keys, ScoutSuite should just check them all, while for subscriptions containing larger numbers of keys, the user should be able to control how many / which keys are checked, according to their specific requirements. I will raise a separate Issue to discuss this and propose an approach which could be applied to other rules as well.
Additional notes:
azure-mgmt-keyvault
dependency is required to support required API requests which were not present in the older version.Type of change
Select the relevant option(s):
Checklist: