CONDUIT TICKET REPORT

Finding Summary

Short description

[TITAN] Medium — security on u-jsmith-contractor

Severity

Medium

Priority

4 - Low

Resource

u-jsmith-contractor

Resource type

Microsoft.AAD/users

Cloud

Azure

Subscription / Account

4f29d094-1079-44c9-acb0-4d73a7a2dd34

Resource group / Project

rg-titan-demo

The Security Finding

Azure AD user 'u-jsmith-contractor' has not signed in for 120 days. Per company policy, contractor accounts dormant >90d must be disabled.

ITIL Change Management Fields

Justification

Medium: Azure AD user 'u-jsmith-contractor' has not signed in for 120 days. Per company policy, contractor accounts dormant >90d must be disabled.

Implementation Plan

1. Pre-change snapshot captured by TITAN (auto-rollback available).
2. Execute fix command:
   Disable AAD user account pending HR review. Revoke all app assignments and OAuth grants.
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 (u-jsmith-contractor).
Blast radius: change is idempotent; pre-change snapshot captured by TITAN; auto-rollback available if rescan fails.
Finding detail: Azure AD user 'u-jsmith-contractor' has not signed in for 120 days. Per company policy, contractor accounts dormant >90d must be disabled.

Backout / Rollback Plan

1. TITAN auto-captured snapshot of u-jsmith-contractor before change (baseline: titan-killer-20260421T222654Z).
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 u-jsmith-contractor 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

Disable AAD user account pending HR review. Revoke all app assignments and OAuth grants.

Compliance Mapping

Routing Metadata

Assignment group

security_engineering

Change type

Incident

Approval required

No

Planned start

—

Planned end

—

Scan ID

titan-killer-20260421T222654Z

Generated at

2026-04-21T22:26:55.252583+00:00

Opened

2026-04-21 15:26:55

Closed

2026-04-21 15:26:55

Close code

—

Attached Security Ticket

Azure AD user 'u-jsmith-contractor' has not signed in for 120 days. Per company policy, contractor accounts dormant >90d must be disabled.

Recommended Fix: Disable AAD user account pending HR review. Revoke all app assignments and OAuth grants.

AI Close Notes

2026-04-21 15:26:55 - System Administrator (Work notes)
[TITAN CONDUIT] Incident auto-filed from security scan.
Detecting agent: unknown (scan titan-killer-20260421T222654Z).
Severity: Medium (priority 3).
This is a hygiene/access-control issue that does not require a formal approval window. Assign to the listed team and resolve per their standard runbook. TITAN will auto-detect clearance on the next scan.