What Happens If a Device Name Changes in CYRISMA?
If a device’s name is changed after the CYRISMA agent has been installed, the platform will not automatically detect or reflect the new name in the dashboard or future vulnerability scans. This is due to how the agent identifies and links the device to its target in CYRISMA.
Written by Liam Downward
Updated at May 7th, 2025
- User Manual
- Self Onboarding Guide
- Agents
- The Cyber Risk Assessment Process
- PSA Integrations
- General Questions and Troubleshooting
- The Cyber Risk Assessment Process (Video Tutorials)
- Sales and Prospecting Articles
- CYRISMA Partner Portal Access
- Glossary
- API Documents
- CYRISMA Change Log
- Support Ticket SLA
- Billing Questions
Table of Contents
Why Doesn’t CYRISMA Detect Name Changes?
When the CYRISMA agent is installed, it locks the system’s identity to the original device name. This binding is tied to internal components—specifically the events.dll file—ensuring secure, consistent recognition of the device throughout scans and reporting.
What Should I Do If a Device Name Changes?
If a device has had its name changed and you want CYRISMA to recognize it properly in scans and reporting, you will need to:
Uninstall the existing agent from the device
Reinstall the CYRISMA agent under the new device name
This will correctly link the updated name to a new target in the platform.
Additional Notes
Vulnerability scans will not update the device name automatically—even if scans are rerun after a name change.
In most real-world cases, a device name change typically happens during a reimage or system refresh, which often includes a new agent install anyway.
For environments where device renaming is frequent, consider documenting the process internally to ensure agent reinstallation is part of the workflow.