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

chore(docs): Developer Guide - how to create a new check #2137

Merged
merged 1 commit into from
Mar 27, 2023

Conversation

MrCloudSec
Copy link
Member

Description

Add how to create a new check.

License

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@MrCloudSec MrCloudSec requested a review from a team March 27, 2023 10:35
@jfagoagas jfagoagas changed the title docs(): add how to create a new check [WIP] docs: add how to create a new check Mar 27, 2023
@jfagoagas jfagoagas added no-merge Please, DO NOT MERGE this PR. work-in-progress labels Mar 27, 2023
@MrCloudSec MrCloudSec removed no-merge Please, DO NOT MERGE this PR. work-in-progress labels Mar 27, 2023
@MrCloudSec MrCloudSec changed the title [WIP] docs: add how to create a new check docs: add how to create a new check Mar 27, 2023
@toniblyx toniblyx changed the title docs: add how to create a new check chore(docs): Developer Guide - how to create a new check Mar 27, 2023
"CheckID": "ec2_ebs_volume_encryption",
"CheckTitle": "Ensure there are no EBS Volumes unencrypted.",
"CheckType": [
"Data Protection"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to explain from where to get details on this, like what else apart from Data Protection?

@toniblyx toniblyx merged commit 941b8cb into master Mar 27, 2023
@toniblyx toniblyx deleted the PRWLR-1836-finish-developer-guide branch March 27, 2023 18:20
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

Successfully merging this pull request may close these issues.

3 participants