Skip to content
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

AzSK version 4.12 Security Status Report does not create SecurityEvaluationData json #1201

Open
v1r7u opened this issue Aug 29, 2020 · 0 comments

Comments

@v1r7u
Copy link

v1r7u commented Aug 29, 2020

AzSK version 4.12 Security Status Report does not create SecurityEvaluationData json

Description

Up to version 4.11 AzSK creates SecurityEvaluationData-xxxxx.json file which contains audited environment description together with audit results. This file was a useful part of our automated pipeline and we used it to normalize audit-result: it had tags, the full azure-identifier of the resource, etc. Based on this file we were able to map results to exact azure components and get required metadata without additional requests to the Azure API.

In version 4.12 AzSK still writes Report in csv, but does not create SecurityEvaluationData json file.

Is it intentional behavior? Is it possible to keep this file generation in further version?

Steps to reproduce

  1. Run:
    ### Run Subscription Security check
    Get-AzSKSubscriptionSecurityStatus -SubscriptionId $SubscriptionId -DoNotOpenOutputFolder
    
    ### Run Components Security check 
    Get-AzSKAzureServicesSecurityStatus -SubscriptionId $SubscriptionId -DoNotOpenOutputFolder
  2. Check output folders \AzSKLogs\Sub_SUBSCRIPTION_NAME\****_GSS\Etc and \AzSKLogs\Sub_SUBSCRIPTION_NAME\****_GRS\Etc if SecurityEvaluationData-xxxxx.json was created.

Expected behavior

SecurityEvaluationData-xxxxx.json exists

Actual behavior

SecurityEvaluationData-xxxxx.json does not exist

Thanks for your work ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant