A Key Preliminary Termination — Activity Involves

Run a dependency scan (for software) or process mapping (for operations). Ask: “If we remove Asset X at 5 PM Friday, what breaks on Monday at 9 AM?”

| Category | Examples | Action | | :--- | :--- | :--- | | | Unused SaaS seats, cloud credits, maintenance renewals, support hours | Claim refund or transfer to another contract. If impossible, accelerate consumption pre-termination. | | Security Deposits | Office lease, utility, equipment rental | Verify return conditions and initiate refund process. | | Accounts Receivable | Amounts owed to you by the terminating party (e.g., unpaid invoices) | Freeze for collections. Do not offset without legal review (can violate bankruptcy automatic stay). | | Licenses & Permits | Software licenses, export permits, data processing agreements | Determine revocability. Some survive termination (perpetual licenses); others die immediately. | Workstream 4: Dependency & Interlinkage Mapping The most dangerous aspect: an asset that appears standalone but is actually a critical dependency for another active system. a key preliminary termination activity involves

| Category | Examples | Verification Method | | :--- | :--- | :--- | | | Service accounts, API keys, SSH keys, OAuth tokens, IAM roles | Identity Governance (SailPoint, Okta) + secret scanner (GitGuardian, TruffleHog) | | Data Repositories | Databases, file shares, wikis, code repos, SharePoint sites, Google Drives | DLP (Data Loss Prevention) scan + eDiscovery hold markers | | IP & Proprietary | Source code, schematics, trade secrets, customer lists, algorithms | Code repository audit trail + patent/trademark assignment records | | Configuration & Automation | CI/CD pipelines, Terraform state files, Ansible playbooks, cron jobs | Infrastructure-as-Code scanning + workflow orchestration audit | Run a dependency scan (for software) or process