Study guide

11.1 Layered Network Security: Security Lists, NSGs & Private Access to Services

OCI 2026 Architect Professional 1Z0-997-26

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Overview & Architecture Foundations

1.1 Exam Logistics, the 2026 Blueprint & How to Use This Guide 1.2 The OCI Well-Architected Framework & Architectural Tradeoffs

2 Chapter 2: High Availability & Resilient Design

2.1 Availability Domains, Fault Domains, Instance Pools & Load Balancers 2.2 OCI DNS Traffic Steering, Geolocation & Health Checks 2.3 Block Volume Replication, Volume Groups & Backup Policies 2.4 Object Storage Replication, Versioning & Retention Rules (WORM)

3 Chapter 3: Full Stack Disaster Recovery

3.1 Full Stack Disaster Recovery: Protection Groups, Members & Permissions 3.2 DR Plans: Switchover, Failover, Prechecks & Plan Execution 3.3 DR Drills, Plan Customization & Operational Readiness

4 Chapter 4: Container Instances, OCIR & OCI DevOps

4.1 Containerization, Microservices & OCI Container Instances 4.2 OCI Container Registry: Repositories, Push & Pull, and Image Management 4.3 OCI DevOps: Code Repositories, Build Pipelines & Deployment Strategies

5 Chapter 5: OCI Kubernetes Engine (OKE)

5.1 OKE Cluster Types, Node Options & Cluster Creation 5.2 OKE Networking: VCN-Native Pod Networking vs. Flannel, Subnet Sizing & Load Balancers 5.3 OKE Workload Identity, Secrets & Persistent Storage

6 Chapter 6: Serverless Functions & API Gateway

6.1 OCI Functions: Concepts, Invocation Modes, Integrations & Image Security 6.2 API Gateway: Authentication, JWT Validation, Rate Limiting & Usage Plans

7 Chapter 7: Messaging & Event-Driven Design

7.1 OCI Streaming, OCI Queue & Messaging Patterns for Microservices 7.2 OCI Events, Event Rules & OCI Notifications Fan-Out

8 Chapter 8: Infrastructure as Code with Terraform & Resource Manager

8.1 Infrastructure as Code with Terraform and the OCI Provider 8.2 OCI Resource Manager: Stacks, Jobs, Drift Detection & Private Endpoints

9 Chapter 9: Identity & Multi-Tenancy Governance

9.1 IAM Policy Design: Verbs, Conditions, Dynamic Groups & Principals 9.2 Organizations Management, Governance Rules & Compartment Quotas

10 Chapter 10: Security Posture with Cloud Guard & Security Zones

10.1 Cloud Guard: Detector Recipes, Problems, Scores & Responders 10.2 Security Zones & Vulnerability Scanning

11 Chapter 11: Secure Access & Network Protection

11.1 Layered Network Security: Security Lists, NSGs & Private Access to Services 11.2 OCI Bastion: Managed SSH, Port Forwarding & SOCKS5 Sessions 11.3 Zero Trust Packet Routing (ZPR): Security Attributes & Intent-Based Policy 11.4 OCI Network Firewall: Policies, Inspection Routing, Tunnel Inspection & Private NAT

12 Chapter 12: Application & Data Protection: WAF, Certificates & Vault

12.1 OCI Web Application Firewall: Policies, Modules, Actions & Enforcement Points 12.2 OCI Certificates: Private CAs, TLS Certificates, Renewal & Integrations 12.3 OCI Vault Key Management: Vault Types, Protection Modes, Dedicated KMS & External KMS 12.4 Vault Secrets: Versions, Rotation States, Automatic Generation & Rotation

13 Chapter 13: Base Database Service & Autonomous AI Database

13.1 Base Database Service: DB Systems, RAC, Data Guard, Cloning & Maintenance 13.2 Autonomous AI Database: Workload Types, Deployment Options, Services & Connectivity 13.3 Operating Autonomous AI Database: Scaling, Cloning, Backups, Patching & Self-Tuning 13.4 Autonomous Data Guard & Backup-Based Disaster Recovery for Autonomous AI Database

14 Chapter 14: Recovery Service, Global Distribution & OCI Cache

14.1 Autonomous Recovery Service: Protection Policies, Real-Time Protection & Retention Lock 14.2 Globally Distributed Autonomous AI Database: Sharding, Data Placement & Replication 14.3 OCI Cache: Valkey and Redis Clusters, Sharding, Security & Cross-Region Replication

15 Chapter 15: Monitoring, Alarms & Notifications

15.1 OCI Monitoring: Metrics, Namespaces, Custom Metrics & Monitoring Query Language 15.2 Alarms & Notifications: Trigger Rules, Absence Alarms, Split Messages, Suppression & Delivery

16 Chapter 16: Logging, Audit, Connector Hub & Search

16.1 OCI Logging: Log Groups, Service Logs, Custom Logs & the Unified Monitoring Agent 16.2 Logging Search, the Logging Query Language & OCI Audit 16.3 Connector Hub: Moving Logs, Metrics, Queue Messages & Streams Between Services 16.4 OCI Search with OpenSearch & Resource Search for Observability

11.1 Layered Network Security: Security Lists, NSGs & Private Access to Services

Key Takeaways Explain This Topic AI

Security Lists provide coarse subnet-level packet filtering applied to all attached VNICs, whereas Network Security Groups (NSGs) implement granular micro-segmentation directly at the VNIC level.

A subnet can have up to 5 security lists with up to 200 ingress and 200 egress rules each, while a VNIC can join up to 5 NSGs and each NSG holds up to 120 rules.

Stateful security rules automatically allow bidirectional response traffic via connection tracking, whereas stateless rules skip connection tracking, which Oracle suggests for very high-volume traffic.

NSG rules can use another NSG as the source or destination, so new instances added to a tier are covered without changing CIDR blocks.

A service gateway reaches Oracle services privately, and on-premises networks can use it through transit routing, but only a private endpoint gives a service its own private IP address in your subnet.

Last updated: October 2026

  • 8.1 Layered Network Security: Security Lists, NSGs & Private Access to Services
  • Subnet-Level Filtering vs. VNIC Micro-Segmentation

In Oracle Cloud Infrastructure, network packet filtering can be enforced at two distinct logical boundaries: the Subnet boundary via Security Lists, or the Virtual Network Interface Card (VNIC) boundary via Network Security Groups (NSGs).

Security Lists (Subnet-Level)

Security Lists are assigned to entire subnets. When a Security List is attached to a subnet, its ingress and egress rules apply uniformly to every single VNIC provisioned within that subnet. An architect can associate up to 5 Security Lists with a single subnet.

While simple to configure for homogenous workloads, Security Lists impose significant design limitations:

No Intra-Subnet Isolation : If a subnet contains both web servers and database instances, Security Lists cannot prevent a compromised web server from attacking the database on port 1521, because all instances inherit the same rules.

Subnet Sprawl : To achieve tier-by-tier isolation using Security Lists, architects are forced to carve VCNs into numerous small subnets (e.g., Web Subnet, App Subnet, DB Subnet, Management Subnet), creating routing overhead and address space fragmentation.

Network Security Groups (VNIC-Level Micro-Segmentation)

Network Security Groups (NSGs) decouple security policies from network topology. An NSG consists of ingress and egress security rules applied directly to individual VNICs, regardless of which subnet the VNIC resides in. An architect can attach up to 5 NSGs to a single VNIC.

NSGs provide decisive architectural advantages:

Micro-Segmentation : Compute instances, load balancers, and database systems residing in the exact same subnet can belong to distinct NSGs with entirely different security postures.

Simplified Subnet Architecture : Workloads can reside within large, consolidated subnets (e.g., a single /22 subnet across an entire Availability Domain), with security boundaries defined logically via NSGs.

Using NSGs as Rule Sources and Destinations

The most useful capability of network security groups is that a rule can reference another NSG (or the same NSG) instead of a CIDR block. In a traditional Security List, the source or destination of a rule must be a static CIDR block (e.g., 10.0.1.0/24 ) or an OCI Service CIDR label.

In contrast, an NSG rule can specify another NSG as its source or destination:

Application Tier Rule : Ingress rule in DB-Tier-NSG allowing TCP port 1521 where the source is App-Tier-NSG .

Dynamic Autoscaling : When an autoscaling instance pool launches new application servers, each new VM's VNIC is automatically attached to App-Tier-NSG . The database instances immediately accept connections from the new VM without requiring any manual IP updates or CIDR modifications.

Zero Hardcoded IPs : Eliminates operational dependencies on static IP assignments and protects against IP address re-use vulnerabilities.

Stateful vs. Stateless Filtering & Connection Tracking Limits

Both Security Lists and NSGs allow configuring rules as either Stateful (the default) or Stateless :

Stateful Rules

Connection Tracking : When a packet matches a stateful ingress rule, the hypervisor's virtual switch records the session in an internal connection tracking table. Return response traffic is automatically permitted, regardless of egress rules.

Use Cases : Standard web applications, database queries, API services, and general enterprise workloads where bi-directional communication is required.

Stateless Rules

No Connection Tracking : The hypervisor bypasses the state tracking table entirely. Every packet is evaluated independently. To permit communication, the architect must write explicit matching rules in both directions (ingress and egress), including specifying the client ephemeral port range (typically TCP/UDP ports 32768–65535).

Use Cases : High-performance computing (HPC), big data streaming (billions of concurrent connections), and DDoS mitigation. Stateless rules eliminate hypervisor state table memory exhaustion and deliver maximum packet-per-second (PPS) throughput with minimum hypervisor latency.

Operational Quotas & Scale Limits

Security Lists : Up to 5 security lists per subnet and up to 300 per VCN; each security list holds up to 200 ingress and 200 egress rules.

Network Security Groups : A VNIC can belong to up to 5 NSGs ; each NSG holds up to 120 rules (ingress and egress combined). These limits cannot be increased.

Defense-in-Depth: Combining Security Lists and NSGs

OCI evaluates Security Lists and NSGs in parallel using a union of permissive rules model. If a packet is allowed by ANY attached Security List rule OR ANY attached NSG rule, the packet is accepted.

Enterprise architectures implement a layered defense-in-depth model:

Layer 1: Security Lists for Subnet Hygiene : Use a baseline subnet Security List to enforce organization-wide hygiene. Rules allow OCI internal infrastructure traffic (DHCP, OCI DNS resolver on 169.254.169.254:53 ), administrative bastion SSH from management subnets, and ICMP Type 3 Code 4 (Path MTU Discovery).

Layer 2: NSGs for Application Micro-Segmentation : Use NSGs attached to specific workload VNICs to restrict business application traffic (e.g., HTTPS port 443, microservice gRPC ports, Oracle SQLNet port 1521).

PaaS Private Connectivity: Private Endpoints vs. Service Gateways

By default, OCI Platform-as-a-Service (PaaS) offerings—such as Autonomous Database, OCI Streaming, OCI Analytics Cloud, and OCI Data Integration—reside within the secure Oracle Services Network and present public IP addresses. Enterprise security policies mandate that databases and message brokers never expose public endpoints.

Architects must select between two private access mechanisms:

1. Service Gateway (SGW)

Mechanics : A virtual gateway on the VCN boundary that routes traffic privately to the Oracle Services Network using Service CIDR labels (e.g., All REGION Services in Oracle Services Network or OCI REGION Object Storage ).

Traffic Flow : Packets remain entirely within Oracle's private network fabric and never traverse the public internet.

On-Premises Access : On-premises networks connected through a DRG can also reach Oracle services through the VCN's service gateway, a transit routing pattern Oracle calls private access to Oracle services .

What it does not do : The service still uses its public service endpoint . The service gateway changes the path, not the address, so the service is not placed in your subnet and cannot carry your NSGs.

2. Private Endpoints (PE)

Mechanics : A Private Endpoint projects the PaaS service directly into a customer-specified private subnet within the VCN. OCI allocates a Virtual Network Interface Card (VNIC) and assigns a genuine private RFC 1918 IP address (e.g., 10.0.3.15 ) from the subnet to the service.

Full Transit Routing & Hybrid Access : Because the PaaS resource possesses a native private IP inside the customer subnet, traffic can reach it from:

Local compute instances in the VCN.

Remote on-premises data centers via FastConnect or IPsec VPN terminated at a DRG v2.

Peered VCNs across the region or cross-region via RPC.

Name Resolution : The service's hostname resolves to the private endpoint IP inside the VCN, so applications keep using the normal TLS connection string. On-premises clients need DNS forwarding to the VCN resolver to resolve the same name.

NSGs on the endpoint : You can attach NSGs to the private endpoint and allow only specific application tiers. For example, an Autonomous AI Database with a private endpoint can allow port 1522 only from the application NSG.

Architectural Comparison: Security & Private Access Mechanisms

Feature / Dimension Security Lists Network Security Groups (NSGs) Service Gateway (SGW) Private Endpoints (PE)

Enforcement Point Subnet boundary (all VNICs inherit) VNIC boundary (per-instance assignment) VCN edge gateway Dedicated VNIC inside private subnet

Granularity Coarse; broadcast domain level Granular; workload micro-segmentation Broad; all PaaS or Object Storage Resource-specific (individual database/stream)

Rule Targets IPv4/IPv6 CIDR, Service CIDRs CIDRs, Service CIDRs, Other NSGs Service CIDR labels Customer subnet RFC 1918 Private IP

Dynamic Scaling Requires updating CIDR ranges NSGs can be rule sources and destinations Automatic route table updates Dynamic Private DNS zone mapping

Hybrid Access Enforces rules on hybrid traffic Enforces rules on hybrid traffic Yes, through transit routing (private access to Oracle services) Yes, routed to the private IP over FastConnect or VPN

Connection Tracking Supports stateful and stateless Supports stateful and stateless N/A (Gateway routing) Supports NSGs attached directly to PE VNIC

Loading diagram... Micro-Segmentation with NSGs and Private Endpoint PaaS Access Architecture