Contents

Cisco Secure Endpoint Mac Connector Rebrand (formerly AMP for Endpoints)

Directory Structure

Filenames

Bundle ID / MDM

Cisco Secure Endpoint Mac Connector Rebrand (formerly AMP for Endpoints)

With Cisco Secure Endpoint Mac connector version 1.18.0, the "AMP for Endpoints" moniker has been replaced with "Cisco Secure Endpoint."

This article will provide an overview of the rebrand changes. Specifically, changes that administrators may need to account for regarding their connector deployment and infrastructure.

Directory Structure

- The Application directory has been renamed from '/Applications/Cisco AMP for Endpoints' to '/Applications/Cisco Secure Endpoint'.

- Subdirectories under '/Applications/Cisco Secure Endpoint' remain the same as older connector versions.

- The menu bar aplication name is now 'Secure Endpoint Connector'.

- The Application Support directory '/Library/Application Support/Cisco/AMP for Endpoints Connector' remains, and the directory contents can also be accessed via a new symlink '/Library/Application Support/Cisco/Secure Endpoint'.

- The '/opt/cisco/amp/' directory remains unchanged.

- The mount name for the install package .dmg file remains unchanged. E.g. '/Volumes/ampmac_connector'.

Filenames

- The uninstall package is now named 'Uninstall Secure Endpoint Connector.pkg'.

- Support packages generated via command line or Support Tool will remain named 'AMP_Support_*.zip'. All filenames inside support packages will remain unchanged.

- Connector executable programs (e.g. ampdaemon) remain unchanged in their name.

- Connector log files (e.g. ampdaemon.log) remain unchanged in their name.

- The connector logs will now state the application name as "Cisco Secure Endpoint connector" instead of "AMP for Endpoints Connector" upon service start.

Bundle ID / MDM

- System Extensions used by the connector have been renamed. The Security Extension is now "Secure Endpoint File Monitor", the Network Extension is now "Cisco Secure Endpoint Filter".

- Bundle IDs used by the connector for the System Extensions remain unchanged.

- Existing installs of the connector (i.e. upgraded to 1.18.0 or newer from an older connector version) may not see the new extension names if the System Extensions have been previously approved/allowed on the host manually or via MDM prior to upgrade.

- Exisitng MDM profiles will continue to work as expected when upgrading to 1.18.0 or newer. No config changes are required.