Uninstalling the macOS Agent
Last updated: December 17, 2025
The Cyrisma macOS Agent can be removed manually from a Mac system or through the Cyrisma the agent must be removed both from the Mac itself and from the Cyrisma Web Platform.
This article explains how to uninstall the agent locally, remove its configuration from Cyrisma, and manage agent entries for decommissioned or repurposed devices.
1. Important Considerations
Before uninstalling the agent, keep the following in mind:
Removing the agent from macOS does not automatically remove the agent entry in the Cyrisma Web Platform.
Removing the agent from the platform does not erase scan data; it is retained for audit and reporting.
If the macOS agent is online and checking in:
Deleting the agent entry in Cyrisma will instruct the agent to self-uninstall on its next check-in.
If the Mac is offline, repurposed, or wiped:
You must delete the agent/target configuration manually from the platform.
2. Uninstalling the Cyrisma Agent from macOS
There is one recommended method for macOS agent removal: a shell script that stops the agent, removes its launch daemon, and deletes all agent files.
Method: Uninstall Using Terminal Script
Steps
Open Terminal on the Mac.
Copy and paste the following script:
#!/bin/bash
sudo launchctl unload /Library/LaunchDaemons/com.cyrisma.cybroker.plist
sudo rm -f /Library/LaunchDaemons/com.cyrisma.cybroker.plist
sudo rm -rf /Applications/Cyrisma
sudo rm -rf ~/Applications/Cyrisma
exit 0
Press Enter to execute.
Enter your macOS administrator password if prompted.
What This Script Does
Stops the CyBroker agent service
Removes the launch daemon
Deletes the application directory
Cleans up user-level application files (if present)
When complete, the macOS agent is fully removed from the system.
3. Removing Agent & Target Configurations From the Cyrisma Platform
After uninstalling the agent locally—or if the Mac is no longer present—you must remove its configuration from Cyrisma to prevent stale entries.
There are two approaches:
Option A: Remove Only the Agent Configuration
Use this method if:
The Mac is still a managed asset
Only the agent needs replacement (e.g., reinstalling)
Steps
Log in to Cyrisma.
Go to Admin > Scan Agents.
Under Update Existing Agent, search for the macOS agent.
Click Submit to open the agent configuration.
Click Delete and confirm.
If the agent is still checking in, it will self-uninstall automatically on its next check-in.
Option B: Remove Both the Target and Agent Configuration
Use when:
The Mac has been wiped, repurposed, decommissioned, or is permanently offline
You want all references to that device removed from the platform
Steps
Log into Cyrisma.
Navigate to Admin > Targets.
Search for the Mac in your target list.
Click Edit.
Click Delete and submit.
This deletes both:
The agent configuration
The target configuration
Important Note About Scan Data
Scan data is not deleted.
Historical results remain accessible.
Deleted targets appear as:
_d_YYYYMMDDHHMM
This preserves auditability and reporting.
4. Removing Configurations for Decommissioned or Repurposed macOS Devices
If the Mac:
Has been retired
Re-imaged
Given to a new user
No longer exists on the network
Then the only available action is platform cleanup.
Steps:
Go to Admin > Targets.
Search for the macOS target entry.
Delete the configuration.
Cyrisma will remove the agent/target association, but scan data remains for compliance purposes.
5. Summary Table
Scenario | Local Uninstall Needed? | Platform Cleanup Needed? | Result |
Mac still online | Optional | Delete agent | macOS agent self-uninstalls |
Mac repurposed | Yes | Delete target | Clean removal; data retained |
Mac decommissioned | Not possible | Delete target | Reclaims platform space |
Replacing agent | Yes | Delete agent only | Fresh install allowed |
6. Conclusion
Whether the agent is being removed for reinstallation, device decommissioning, or inventory cleanup, following the steps above ensures that:
The macOS system is free of all agent components
The Cyrisma platform remains accurate and uncluttered
Historical scan data continues to be preserved