Firewall Rules

 Firewall Rules

In Google Cloud Platform (GCP), Firewall Rules are essential for controlling network traffic to and from your Virtual Private Cloud (VPC) resources. They act as virtual firewalls, allowing or denying traffic based on specified criteria. Firewall rules apply at the instance level, not at the subnet or VPC level.

Each rule is defined by the following components:

Direction: Ingress (incoming) or Egress (outgoing) traffic.

Action: Allow or Deny traffic.

Targets: Specific instances, tags, or service accounts the rule applies to.

Source or Destination: IP ranges, tags, or service accounts.

Protocols and Ports: (e.g., TCP:80 for HTTP or TCP:22 for SSH).

By default, GCP allows all outbound (egress) traffic and blocks inbound (ingress) traffic except for some internal services. You must create rules to allow SSH, HTTP, or custom application ports.

Firewall rules have a priority from 0 (highest) to 65535 (lowest). When multiple rules match, the one with the highest priority is applied first. You can also log firewall activity using Firewall Rules Logging to monitor allowed or denied traffic.

Firewall rules are stateful, meaning return traffic for an allowed connection is automatically permitted. They help secure your applications, isolate environments, and meet compliance needs by tightly controlling network access.

In summary, GCP firewall rules provide fine-grained, customizable security controls to manage traffic within and outside your cloud infrastructure.

Read More

Subnets and IP Addressing


Visit Our Website

Visi Quality Thought Institue In Hyderabad



Comments

Popular posts from this blog

What is Tosca and what is it used for?

Compute Engine (VMs)

What is Software Testing