Decommissioning a Defender
- Marcus Lewis
This page is to give insight on how to properly decommission a defender. This is a step-by-step guide on what to do when a Defender must be deleted from Data443.
Instructions
Make sure there is nothing on the server that we may want to preserve such as a unique script (Kris will typically take care of this portion) so make sure to communicate with him prior to deleting anything.
Delete the contents from Defender (rm -rf /mnt/nas/*)
Remove rules on firewall (one entry each from FW rules. NAT and aliases most likely).
Shutdown the VM the tenant is operating on this is required before the VM can be deleted.
Delete the VM from VCSA (assuming we are not saving it for some reason, we will generally try to verify from the customer that they want their data purged).
Remove monitoring rule from site 24x7.
Remove monitor from elastic.
Remove share in FreeNAS, also remove datasets from storage>pools and verify that actual shared directory no longer exists.
If the tenant is indexing on DAM, remove DAM solr core and tenant (we'll have to break this down a bit for clarity).
Note that tasks are complete in ticket, ensure customer knows (likely the requester will either be in contact or know who to reach out to).
Related articles
As the last step remember to mark through the tenant that was deleted, by doing so it lets everyone know the IP address is available here is the last step https://data443.atlassian.net/wiki/spaces/IM/pages/42729473