TITAN AI · CONDUIT Agent

CONDUIT TICKET REPORT

CHG0030104
TICKET
🖨 Print / Save as PDF ⬇ PDF ⬇ DOCX
TICKET Azure Medium Assigned
Opened by TITAN AI · CONDUIT · Scanner found the finding, CONDUIT forwarded this ticket via CONDUIT generic-API layer, assigned security_engineering, populated every ticket field, The ticket is routed and awaiting team approval — CONDUIT will update it after TITAN FORGE applies the fix.

Finding Summary

Short description
[TITAN] Medium — legacy_eol on acr-retired-image-base
Severity
Medium
Priority
3 - Moderate
Resource
acr-retired-image-base
Resource type
Microsoft.ContainerRegistry/registries/images
Cloud
Azure
Subscription / Account
4f29d094-1079-44c9-acb0-4d73a7a2dd34
Resource group / Project
rg-legacy-prod

The Security Finding

Container base image 'centos:7' detected in ACR — CentOS 7 EOL 2024-06-30 (297 days). Used as base for 14 downstream application images currently deployed. Fails CIS Controls v8 7.3, NIST 800-53 CM-6.

ITIL Change Management Fields

Justification

Medium: Container base image 'centos:7' detected in ACR — CentOS 7 EOL 2024-06-30 (297 days). Used as base for 14 downstream application images currently deployed. Fails CIS Controls v8 7.3, NIST 800-53 CM-6.

Implementation Plan

1. Pre-change snapshot captured by TITAN (auto-rollback available).
2. Execute fix command:
   Rebuild images from rockylinux:9 or almalinux:9. Update all 14 downstream Dockerfile FROM statements. Rolling deploy via existing CI/CD.
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 (acr-retired-image-base).
Blast radius: change is idempotent; pre-change snapshot captured by TITAN; auto-rollback available if rescan fails.
Finding detail: Container base image 'centos:7' detected in ACR — CentOS 7 EOL 2024-06-30 (297 days). Used as base for 14 downstream application images currently deployed. Fails CIS Controls v8 7.3, NIST 800-53 CM-6.

Backout / Rollback Plan

1. TITAN auto-captured snapshot of acr-retired-image-base before change (baseline: titan-legacy-demo-20260422T201927Z).
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 acr-retired-image-base 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

Rebuild images from rockylinux:9 or almalinux:9. Update all 14 downstream Dockerfile FROM statements. Rolling deploy via existing CI/CD.

Compliance Mapping

CIS BenchmarkSOC 2 CC6.1

Routing Metadata

Assignment group
security_engineering
Change type
Normal
Approval required
No
Planned start
2026-04-22 20:09:27
Planned end
2026-04-22 22:09:27
Scan ID
titan-legacy-demo-20260422T201927Z
Generated at
2026-04-22T19:55:27+00:00
Opened
2026-04-22 19:55:27
Closed
2026-04-22 19:55:27
Close code

Attached Security Ticket

SERVICENOW · TICKET
SEC-3242 · [TITAN] Medium — legacy_eol on acr-retired-image-base
Priority: Medium TICKET Azure

Ticket Description

Container base image 'centos:7' detected in ACR — CentOS 7 EOL 2024-06-30 (297 days). Used as base for 14 downstream application images currently deployed. Fails CIS Controls v8 7.3, NIST 800-53 CM-6.

Recommended Fix: Rebuild images from rockylinux:9 or almalinux:9. Update all 14 downstream Dockerfile FROM statements. Rolling deploy via existing CI/CD.

AI Close Notes

TITAN CONDUIT opened this medium legacy_eol ticket and assigned it to the security_engineering 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.