Skip to content

[REVIEW] firewall-review: add NAT egress attribution gaps gates #2751

@stmr

Description

@stmr

[REVIEW] firewall-review: add NAT egress attribution gaps gates

Skill Being Reviewed

Skill name: firewall-review
Skill path: skills/network/firewall-review/

False Positive Analysis

Shared NAT egress is acceptable when flow logs, workload identity, subnet ownership, and proxy logs can attribute traffic to the source workload.

Coverage Gaps

Firewall reviews often verify allowed egress but miss attribution. A broad NAT IP can hide which service made a risky outbound connection, weakening incident response and policy cleanup.

Edge Cases

  • Serverless workloads share provider NAT.
  • Kubernetes pods egress through node IP.
  • Third-party allowlists require stable NAT but reduce attribution.

Remediation Quality

  • Add evidence fields: NAT gateway, source subnet/workload, flow logs, proxy logs, owner, and retention.
  • Require per-workload attribution for high-risk egress.
  • Flag allowlists that rely only on shared public IP.

Comparison to Other Tools

Cloud flow logs show IPs; service mesh/proxy logs can add workload identity.

Overall Assessment

Add NAT attribution gates so firewall reviews support investigation and least privilege.

Bounty Info

  • I have read and agree to the CONTRIBUTING.md bounty terms.
  • Preferred payment method: PayPal samik4184@gmail.com

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions