MEDIUMCIS 4.1

Ensure compute instances do not have public IPs

Production compute instances should not have public IP addresses.

Security Impact

Public IPs expose instances directly to internet-based attacks.

How to Remediate

Deploy instances in private subnets. Use load balancers for public-facing services.

Affected Resources

OCI::Core::Instance

Compliance Frameworks

CIS OCI v1.2.0SOC 2PCI-DSSNIST 800-53

How TigerGate Helps

TigerGate continuously monitors your Oracle Cloud environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:

  • Continuous Scanning

    Automatically scans all Oracle Cloud Compute resources across your Oracle Cloud tenancies every hour

  • Instant Alerts

    Get notified via Slack, email, or webhooks when this misconfiguration is detected

  • One-Click Remediation

    Fix this issue directly from the TigerGate dashboard with our guided remediation

  • Compliance Evidence

    Automatically collect audit evidence for CIS OCI v1.2.0, SOC 2, PCI-DSS compliance

  • Drift Detection

    Get alerted if this configuration drifts back to an insecure state after remediation

Check Details

Check ID
oracle-compute-1
Service
Oracle Cloud Compute
Category
Network Security
Severity
MEDIUM
CIS Benchmark
4.1

Automate This Check

TigerGate automatically scans your Oracle Cloud environment for this and 50+ other security checks.

Start Free Trial

Related Oracle Cloud Compute Checks

View all checks
oracle-compute-2medium

Ensure compute instances use shielded instances

oracle-compute-3low

Ensure compute instances have monitoring enabled

oracle-compute-4high

Ensure legacy IMDS is disabled

oracle-compute-5medium

Ensure instances use latest operating system images

oracle-compute-6medium

Ensure custom images are scanned for vulnerabilities