A Cloud Guard Target whose Responders Respond

Oracle ships every responder rule in USERACTION mode: a Remediate button appears on each problem and nothing happens until a person clicks it, so a tenancy with hundreds of findings has by default fixed none of them. Sets AUTOACTION per rule and exports the IAM statements each auto-action needs, since one without its policy fails on every execution.

This is the operations reference: version drift, dependants and neighbours. For what the module provisions, its inputs and outputs, and how to buy it, see the catalogue entry.

terraformOracle CloudSecurity & Identityv1.0.0static-validated

Provider drift

This artifact declares no Terraform provider requirements, so there is nothing to drift. Provider freshness applies to Terraform and OpenTofu modules.

What depends on this

No reference architecture names this module, so changing it affects only configurations that reference it directly.

Nearest alternatives

Same cloud, same category. These are what you would weigh against it without changing provider.

A Compartment where the Wrong Resource Cannot Be Created A Network Firewall that Prevents rather than Detects A WAF that Blocks rather than Narrates Bastion Service Vulnerability Scanning that Is Scanning Something

The same job on other clouds

Security Posture & Findings on other providers. Useful when the cloud is still open, or when you are pricing a second one. How far a comparison like that can be trusted is covered in comparing clouds.

Defender Plans that Are Actually OnAzure Findings that Reach a Topic, Mutes that Say WhyGoogle Cloud Security Hub with Chosen StandardsAWS

Installing it

module "oci_cloud_guard" {
  source  = "www.iac-bazaar.com/iac-bazaar/oci-cloud-guard/oci"
  version = "1.0.0"
}

A registry token is required for the download itself. Installing through the registry protocol has the two credential steps.