Fortify your Desktop Central server

Desktop Central is an endpoint management tool that manages your devices running on different Operating Systems from a central location. In this document, we will provide you with some tips and tricks to harden your Desktop Central security.

Best security practices

Desktop Central immediately releases the security patches for identified security issues. Follow the Security Updates Group and the Security Updates on Vulnerabilities section in our Knowledge Base to stay updated with the latest security patches. Furthermore, please subscribe to our Data Breach Notification to receive notifications on any security incident without delay.

Note: It is highly recommended to
1) Update your Desktop Central server to the latest build.
2) Grant access to the Desktop Central folder only to authorized users.

Secure the access to Desktop Central

Securing the login access to Desktop Central, can prevent security issues involving roles and permissions.

Security Settings

To fortify the login access, go to the Admin tab, and click Security Settings.

Under Secure Login,

  • Remove default admin account

    The default admin account should be removed after the first login.

  • Enable Secure Login (HTTPS).

    All communication between the Desktop Central server and the agents will take place using the HTTPS protocol after enabling this option.
    Note: In addition, disable the 8020 port in firewall in your network

  • Use Third Party SSL Certificate

    It is recommended to configure Desktop Central with a trusted third party certificate to ensure secured connections between desktops, mobile agents and servers. However, for secured communication using HTTPS, a default certificate will be provided along with the server.

  • Enforce Two Factor Authentication

    Having a second level of verification for technicians ensures that unauthorized access is prevented.

  • Set Complex Password

    Setting a complex password policy allows users to configure unique passwords that are tough to crack. The more complex a password policy is, the more combinations there will be.

  • Secure Software Repository (local network share)

    The local network share will contain all the software installation files. Access credential is use to grant access to the share to authorized users only.

  • Restrict users from Uninstalling the Agent from Control Panel

    The agent monitors and executes the configurations and tasks deployed to a particular endpoint. That's why it is necessary to forbid users from uninstalling the agent.

  • Restrict users from stopping Agent service

    Preventing the users from stopping the Agent service ensures that the endpoint stays in contact with the server every 90 minutes.

Under Secure agent server communication,

  • Enable Secured Communication (HTTPS) for LAN and WAN agents

    HTTPS protocol for both LAN and WAN agents ensures that the communication between the agents and the server is always encrypted.

  • Secure Remote Control and File Transfer operations

    Enable this option to secure the communication during Remote Control sessions and File Transfer operations.

  • Disable the older versions of TLS

    For improved security, it is advisable to use the newer version of TLS, instead of using the older ones.
    Note
    : Users cannot manage devices running on legacy OS platforms (Windows XP, Vista, Server 2003 and Server 2008) after disabling the older version of TLS.

  • Use Secure Gateway Server

    It is highly recommended to host the Desktop Central server in a corporate network protected by firewall restrictions and other security measures. If there are several roaming users and remote offices, then you can use an additional component, called the Secure Gateway Server. Secure Gateway Server is a reverse proxy solution that acts as a bridge between the WAN agents and the Desktop Central server. It prevents the need for the Desktop Central server to be hosted as an EDGE device to manage roaming users.

Module-wise methodical steps to enhance security:

  • Provide the root access only to trusted technicians in Redhat nominated machines to avoid sending malicious content, instead of meta files.
  • Provide the root access only to trusted technicians in Linux agents to avoid sending malicious URLs, instead of package URLs.
  • Scan the uploaded files in the Upload Patch option for any malicious files.
  • Do not share the following to anyone:
    • Image Creator Component binaries
    • The Bootable Media file
    • The Deployment Passcode (when configuring the Deployment Task)
    • The Image File
    • The User Profile Backup (USMT)
  • Place the Image and Driver repositories in a password-protected Network Share
  • Use either the MAC Address of the target computer(s) or the unique four digit passcode to initiate deployment. This avoids sharing admin credentials.
  • Scan the installation files for malicious content when the post deployment activity involves installing applications.
  • When adding a new user during the Deployment Template creation, enable Complex Password and associate the local users to their respective target computers.
  • Enrollment settings

    • For enrolling corporate-owned devices, use the following enrollment methods based on the supported platforms to ensure devices always remain under management even after being factory reset:
    • On corporate devices, the options to perform a factory reset and device wipe can also be restricted to prevent users from removing devices from management.
    • For Android devices, the Allow User to remove ME MDM App option should be disabled to restrict corporate devices that have not been enrolled using the above mentioned enrollment methods from being removed from management.
    • Enable the option to detect and remove jailbroken and rooted devices to ensure only compliant devices remain under management and access corporate data.
  • Inventory settings

    • Schedule regular device scans to ensure the device details remain up to date.
  • Device settings

    • Configure Device Privacy Settings to ensure only the details required by Desktop Central for management and only the data permitted by the local and global compliance laws are stored on the server.
    • Configure the Terms of Use policies to be displayed to the device users and obtain their consent before collecting and storing device information on the Desktop Central server to ensure user privacy.
  • Go to the Admin tab, under Tools Settings,
    click Port Settings and switch the Communication to HTTPS. Click Save.
  • click System Manager Settings.
  • Under Permission Settings, enable the permission to access the end user's File Manager and Command Prompt to only admins.
  • Under User Confirmation Settings, opposite to the Enable user confirmation for field, check the boxes for File Manager and Command Prompt.
  • Now, go to the Tools tab, click Remote Control, and switch to the Settings tab. Here, enable the Idle Session Settings. This allows the remote connection to either just disconnect or disconnect and lock the target computer automatically, when the connection is idle for a set period.
  • In the Remote Control tab, switch to the User Confirmation tab. Here, enable User Confirmation, set a time out period and provide a confirmation message. You can also Make User Confirmation Permanent. Click Save.
  • Note: After enabling the Make User Confirmation Permanent option, the confirmation dialog box will always be displayed and this cannot be reverted even by administrators.

    Go to the Admin tab,

  • under Database Settings, click Database Backup. Here, schedule a time at which the database should back up every day. You can also set the number of backups to be stored, beyond which the backups will be deleted automatically. It is highly recommended to receive notifications about the database backup failure. Furthermore, secure the database backup using a password.
  • under SoM Settings, click Agent Settings. Here, enable the Restrict users from Uninstalling the Agent from Control Panel and the Restrict users from stopping Agent service options.
  • under Security Settings, click Export Settings. While exporting any reports, you can:
    • Mask the personal Information
    • Remove personal Information
    • Retain Personal Information
    • Let the Technician Decide
    Here, opposite to both Configure Export Settings and Configure Scheduled Report Settings, choose Remove Personal Information.
  • Set the session timeout as minimum as possible
  • In the web console, click the user profile picture at the top right and click Personalize. Here, set a minimum possible period for Session Expiration.
  • Monitor the active sessions on the Desktop Central web console and close the stale sessions.
  • It is highly recommended to
    • change the passwords of all the technicians every 90 days.
    • not host the Distribution Server as an edge device.
    • not share the Desktop Central agent registry and logs to anyone except Desktop Central Support.
  • Store the HTTP Repository in a local computer or a secure Network Path.
  • Scan the files before uploading when creating a new software package.
  • While uploading a script in the Script Repository, ensure that the file is scanned for malicious content before uploading.
  • While resolving misconfigurations, read the post deployment issues, if any, to be aware of potential issues that may arise after altering existing configurations.

It is highly recommended for Desktop Central users to follow the guidelines in this document. In particular, safeguarding the server by configuring the Security Settings. This proves to be a quick and effective move against cyber threats. Moreover, the steps provided for every module will help strengthen the security even further.