prowler-sdk-check

To create a Prowler security check, you need to follow the SDK architecture patterns to generate the necessary file structure and boilerplate code. This process ensures your new checks for AWS, Azure, or GCP include compliant metadata and proper naming conventions for successful integration.

Adding metadata to a Prowler security check requires adhering to a specific metadata schema. The process guides you through creating compliant metadata files for each check, ensuring the generated code integrates seamlessly with the existing Prowler framework.

Yes, you can update existing Prowler checks across Kubernetes and GitHub. The structured process provides code templates that facilitate updates to existing checks and their metadata, maintaining consistency with the SDK architecture patterns for various cloud providers.

Yes, Prowler check generation supports Azure Key Vault access policies. A security engineer can quickly set up the check's files and metadata according to Prowler's standards, using the provided code templates to ensure the new check follows the correct SDK architecture.

Yes, specific naming conventions are required for Prowler security checks. Adherence to these check naming conventions and the metadata schema is necessary for successful integration, ensuring the generated boilerplate code aligns with the Prowler SDK architecture.