Compliance Workflow #222
perssonmats4compliance-workflow.yml
on: schedule
CyDig-Compliance-Workflow
/
Repository-Scan
24s
Annotations
5 warnings
|
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "README-badges-URLS".
Please update your workflow to use v4 of the artifact actions.
Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
|
|
CyDig-Compliance-Workflow / Repository-Scan
The following actions uses Node.js version which is deprecated and will be forced to run on node20: azure/login@v1, actions/setup-node@v3, Omegapoint/cydig-azure-compliance-action@v1, Omegapoint/upload-compliance-state-action@v1, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
SAST tool control failed
no analysis found
|
|
CyDig-Compliance-Workflow / Repository-Scan
Secret Scanning Tool is not set! Will continue with GitHub Secret Scanning tool:
|
|
CyDig-Compliance-Workflow / Repository-Scan
The workflow does not have access to view members in a group in your Azure Subscription, therefore the control will add 5 members for each group it finds.
Follow these steps to give the workflow the necessary permission:
1. Go to the App Registration connected to your workflow in the Azure portal.
2. Go to API permission and press Add a permission.
3. Press Microsoft Graph --> Application permission.
4. Choose the permission GroupMember.Read.All and press Add permission.
5. An admin of your Azure tenant must give admin consent in order for the permission to start working.
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
README-badges-URLS
Expired
|
4.67 KB |
|