How to Remove Agent Configurations from the CYRISMA Web Platform
There are instances where agent configurations must be removed from the CYRISMA Web Platform. These scenarios may include system decommissioning, re-purposing, or re-imaging. When an agent needs to be deleted, there are three key components to consider: The agent software running on the host machine. The target definition and configuration in the CYRISMA Web Platform. The agent definition and configuration in the CYRISMA Web Platform. This guide provides step-by-step instructions on removing agent configurations from the platform and cleaning up associated data.
- User Manual
- Agents
- The Cyber Risk Assessment Process
- API Documents
- General Questions and Troubleshooting
- The Cyber Risk Assessment Process (Video Tutorials)
- Sales and Prospecting Articles
- CYRISMA Partner Portal Access
- Glossary
- CYRISMA Change Log
- Support Ticket SLA
- Onboarding Framework
- PSA Integrations
- Billing Questions
- Self Onboarding Guide
Table of Contents
Important Considerations
- Uninstalling the agent from a computer or removing the computer from the network will not automatically remove the agent or target configurations from the CYRISMA Web Platform.
- If the agent host machine is still on the network, you have two options:
- Uninstall the agent software manually and delete the agent configuration in the CYRISMA Web Platform.
- If the agent is still able to check in with CYRISMA, deleting the agent configuration in the platform will signal the agent to uninstall itself during its next check-in.
Steps to Remove Agent Configurations
1. Uninstalling the Agent Software from the Host Machine
- To manually uninstall the CYRISMA Agent from a Windows machine:
Run the following command:
C:\CYRISMA_Agent\unins.000.exe
For a silent uninstall, you can use:
C:\CYRISMA_Agent\unins.000.exe /verysilent
2. Removing Target and Agent Configurations from CYRISMA Web Platform
To Remove Both the Target and Agent Configuration:
- Log in to the CYRISMA Web Platform.
- Navigate to Admin > Targets.
- Search for the specific target you want to delete.
- Click Edit on the target’s configuration details page.
- Select the Delete option and submit.
- Note: This will remove both the target and the agent configurations from the interface. However, scan data associated with the target will remain in the system (with deleted targets displayed as
_d_YYYYMMDDHHMM
).
To Remove Only the Agent Configuration (Leaving the Target):
- Log in to the CYRISMA Web Platform.
- Go to Admin > Scan Agents.
- Select Update Existing Agent.
- Search for and select the agent you wish to remove.
- Click the Update button to open the configuration details.
- Select Delete and submit.
- If the agent is still able to check in, it will uninstall itself automatically on its next check-in. In either case, the agent will be removed from the CYRISMA Web interface.
3. Removing Configurations for Decommissioned or Repurposed Machines
- If the host machine has already been decommissioned or repurposed and is no longer on the network:
- Go to Admin > Targets in the CYRISMA Web Platform.
- Search for the decommissioned target in the Target Config.
- On the target details page, select Delete and submit.
- This will remove both the target and agent configurations from the platform.
Important Note About Scan Data
-
Scan Data Retention: Deleting the target or agent configuration does not automatically delete any scan data collected against that target. Deleted targets may still show up in scan results as
_d_YYYYMMDDHHMM
to preserve historical scan records.
Common Scenario: Re-purposed Machine
In cases where a machine has been repurposed but the old target and agent configurations remain in the CYRISMA Web Platform, follow the steps outlined above to delete the old target configuration from Admin > Targets.
Conclusion
Whether you are uninstalling the agent from a live machine or removing configurations for decommissioned systems, these steps will ensure that the CYRISMA Web Platform is kept clean and up to date. Always remember to remove both the agent and target configurations as necessary to avoid clutter in the platform’s interface.