Prowler cloud security posture

Runs Prowler (v4+) against a live cloud account or cluster (target cloud:aws, cloud:azure, cloud:gcp, cloud:kubernetes) and reports its FAIL checks with compliance-framework tags (cis-…, soc2, …). Credentials come from your ambient environment (AWS_PROFILE/AWS_*, az login, GOOGLE_APPLICATION_CREDENTIALS, KUBECONFIG) and are never read or reported. Only read/list API calls are made, but a full scan can take many minutes and many API calls, so it is opt-in. Optional settings["cloud.prowler"]: profile (aws), regions (aws), checks, services, compliance (e.g. cis_2.0_aws), azureAuth (cli | sp-env | managed-identity), projectIds (gcp), context (kubernetes); each is validated against a strict pattern.