Angelika Schneider

Discovery: Azure ARM template discovery needs a mayor update

1

The ARM discovery needs mayor updates, I will do that in a separate PR. _Originally posted by @garuppel in https://github.com/clouditor/clouditor/issues/539#issuecomment-1063844424_ The service/discovery/azure/arm_template* files contain the TODOs.

Add check for existing resourceTypes in assessment result

3

Merge after MEDINA midterm review

The NCL Translator needs to know which requirement is added (and also removed?). For that, we have to check if requirements are added or removed in UpdateCloudService(). Furthermore, we have...

Kubernetes has a lot of different API versions (e.g., extensions.v1beta1, networking.k8s.io/v1, networking.k8s.io/v1beta1) and we need to handle all of them.

We have to somehow deal in the evaluation with evidences from different discoverers for the same security feature. It is possible that we get one evidence from Clouditor with 'MalwareProtection.Enabled...

- [x] #478 - [x] #481 - [ ] Policy folder path not accessible: How can we import the policy folder to get the metrics? Currently they need to be...

Check if evidence and assessmentResult is nil

3

If an empty evidence is sent to the asssessment component the following error occurs: ``` panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1...

Concretize error message in assessment component

4

The following error comes, if the resource type is not specified: ERRO[3136] Could not evaluate evidence: got type '[]interface {}' but wanted '[]interface {}'. Check if resource types are specified...

Errors should be treated equally

2

Why not wrap error with `%w` like in k8s compute? There, we don't print the error which is thrown to the calling function. Maybe we have to discuss this and...