Agent Decommissioning
Procedures for securely retiring AI agents while maintaining compliance and audit trail.
Overview
When an agent is no longer needed, it must be decommissioned following a controlled process that ensures data retention requirements are met and all stakeholders are notified.
Decommissioning Triggers
| Trigger | Action |
|---|---|
| Business decision | Standard decommissioning |
| Replaced by new agent | Migration then decommissioning |
| Compliance violation | Immediate suspension, then decommissioning |
| Security incident | Emergency suspension, investigation, then decommissioning |
| Owner departure | Ownership transfer or decommissioning |
| Inactivity (>90 days) | Review for decommissioning |
Decommissioning by Zone
Zone 1 Decommissioning
Approver: Creator (self-service)
Retention Requirements: 30 days minimum (if any logs exist)
Process:
- Document reason for retirement
- Disable agent access
- Wait 30 days for log retention
- Delete agent from environment
- Remove from inventory (if tracked)
Zone 2 Decommissioning
Approver: Manager + Environment Owner
Retention Requirements: 1 year minimum
Process:
- Document business justification for retirement
- Obtain manager approval
- Notify team members and users (2-week notice recommended)
- Disable agent (do not delete yet)
- Export conversation history (if required)
- Verify audit logs are retained (1-year minimum)
- Remove user access
- Wait retention period
- Delete agent from environment
- Update inventory to show decommissioned status
- Archive documentation
Zone 3 Decommissioning
Approver: Governance Committee
Retention Requirements: 7-10 years (per regulatory requirements)
Process:
- Document detailed business justification
- Present to governance committee
- Obtain committee approval:
- AI Governance Lead
- Compliance Officer
- CISO
- Business Owner
- Notify all stakeholders (minimum 30-day notice)
- Create transition plan (if replacing with new agent)
- Disable agent in production
- Complete data exports:
- Full conversation history
- Audit logs (entire retention period)
- Configuration backup
- Model/knowledge source documentation
- Transfer data to long-term retention storage
- Verify retention meets regulatory requirements
- Remove user and system access
- Preserve agent for retention period (disabled state)
- Update inventory to show decommissioned
- Archive all governance documentation
- Schedule deletion after retention period expires
Data Retention Requirements
| Data Type | Zone 1 | Zone 2 | Zone 3 |
|---|---|---|---|
| Conversation logs | N/A | 1 year | 7-10 years |
| Audit trail | 30 days | 1 year | 7-10 years |
| Configuration | N/A | 1 year | 7 years |
| Approval records | N/A | 3 years | 7 years |
| Incident records | N/A | 3 years | 7 years |
Regulatory Retention Guidelines
| Regulation | Requirement | Applies To |
|---|---|---|
| FINRA 4511 | 6 years, first 2 years in easily accessible place | Broker-dealers |
| SEC 17a-4 | 6 years, first 2 years readily accessible | SEC registrants |
| SOX 802 | 7 years | Public companies |
| GLBA | Per institution policy | All FSI |
Stakeholder Notification Template
Subject: [Agent Name] Decommissioning Notice
Dear [Stakeholder],
This notice informs you that [Agent Name] will be decommissioned on [Date].
REASON: [Brief explanation]
TIMELINE:
- [Date]: Agent disabled (read-only)
- [Date]: User access removed
- [Date]: Agent deleted
IMPACT:
- [Description of impact on users/workflows]
ALTERNATIVES:
- [Replacement agent, if applicable]
- [Alternative processes]
QUESTIONS:
Contact [Name] at [Email] for questions.
[AI Governance Lead]
[Date]
Emergency Decommissioning
For security incidents or compliance violations requiring immediate action:
- Immediate Actions (within 1 hour):
- Disable agent access
- Notify CISO and Compliance Officer
- Preserve all logs and evidence
-
Document reason for emergency action
-
Within 24 Hours:
- Notify AI Governance Lead
- Brief governance committee
- Complete incident report
-
Assess data exposure (if any)
-
Within 7 Days:
- Complete root cause analysis
- Document lessons learned
- Update governance procedures (if needed)
- Decide on permanent decommissioning vs. remediation
Decommissioning Checklist Summary
Pre-Decommissioning
- Business justification documented
- Approvals obtained (per zone requirements)
- Stakeholders notified
- Transition plan created (if applicable)
Decommissioning Execution
- Agent disabled
- Data exported and preserved
- User access removed
- Systems integrations disconnected
Post-Decommissioning
- Inventory updated
- Documentation archived
- Retention compliance verified
- Final review completed
Related Playbooks
Last Updated: January 2026 FSI Agent Governance Framework v1.2