CONDUIT TICKET REPORT

Finding Summary

Short description

[TITAN] Medium — network on fw-banking-api-ingress

Severity

Medium

Priority

3 - Moderate

Resource

fw-banking-api-ingress

Resource type

compute.googleapis.com/Firewall

Cloud

Multi

Subscription / Account

adroit-terminus-234522

Resource group / Project

banking-prd-project

The Security Finding

GCP firewall rule fw-banking-api-ingress allows 0.0.0.0/0 on 8080 — unencrypted API traffic reachable from anywhere. Should be restricted to corporate egress + load-balancer only.

ITIL Change Management Fields

Justification

Medium: GCP firewall rule fw-banking-api-ingress allows 0.0.0.0/0 on 8080 — unencrypted API traffic reachable from anywhere. Should be restricted to corporate egress + load-balancer only.

Implementation Plan

1. Pre-change snapshot captured by TITAN (auto-rollback available).
2. Execute fix command:
   gcloud compute firewall-rules update fw-banking-api-ingress --source-ranges=35.191.0.0/16,130.211.0.0/22,10.0.0.0/8
3. TITAN FORGE verifies the fix was applied.
4. Post-change rescan by TITAN SCOUT — finding must no longer appear.
5. Close ticket with Successful close_code.

Risk & Impact Analysis

Risk level: MEDIUM risk — weaker control, should be hardened.
Business impact if unremediated: Control weakness that compounds with other gaps.
Scope: single resource (fw-banking-api-ingress).
Blast radius: change is idempotent; pre-change snapshot captured by TITAN; auto-rollback available if rescan fails.
Finding detail: GCP firewall rule fw-banking-api-ingress allows 0.0.0.0/0 on 8080 — unencrypted API traffic reachable from anywhere. Should be restricted to corporate egress + load-balancer only.

Backout / Rollback Plan

1. TITAN auto-captured snapshot of fw-banking-api-ingress before change (baseline: titan-banking-demo-20260422T201922Z).
2. If post-change rescan still shows the finding OR a new issue appears within 15 min:
   a. TITAN FORGE fires rollback automatically using stored snapshot.
   b. Incident reopens and escalates to on-call.
3. Manual rollback command path (human override) is documented in close notes.

Test Plan

1. TITAN SCOUT rescans fw-banking-api-ingress immediately after FORGE applies the change.
2. PASS criteria: the specific finding no longer appears in SCOUT results.
3. PASS criteria: no new CRITICAL or HIGH findings introduced by the change.
4. Automated compliance check: HIPAA/PCI/SOC2 controls re-evaluated.
5. If any check fails, backout plan fires automatically.

Recommended Fix

gcloud compute firewall-rules update fw-banking-api-ingress --source-ranges=35.191.0.0/16,130.211.0.0/22,10.0.0.0/8

Compliance Mapping

Routing Metadata

Assignment group

network_operations

Change type

Normal

Approval required

No

Planned start

2026-04-22 19:15:22

Planned end

2026-04-22 21:15:22

Scan ID

titan-banking-demo-20260422T201922Z

Generated at

2026-04-22T19:01:22+00:00

Opened

2026-04-22 19:01:22

Closed

2026-04-22 19:01:22

Close code

—

Attached Security Ticket

GCP firewall rule fw-banking-api-ingress allows 0.0.0.0/0 on 8080 — unencrypted API traffic reachable from anywhere. Should be restricted to corporate egress + load-balancer only.

Recommended Fix: gcloud compute firewall-rules update fw-banking-api-ingress --source-ranges=35.191.0.0/16,130.211.0.0/22,10.0.0.0/8

AI Close Notes

TITAN CONDUIT opened this medium network ticket and assigned it to the banking_compliance group for review. STATE: ASSIGNED — awaiting human action. Per TITAN AI policy, configuration changes are NEVER auto-applied and tickets are NEVER auto-closed by TITAN. The assigned group reviews the recommended fix, schedules an approved maintenance window, applies the fix manually, validates via SCOUT rescan, and closes this ticket themselves. TITAN documents and routes — the human owns the change from here.