See every data event on your endpoints. Then decide what leaves

Yes. The on-premises model puts DGMC, the database, and the network appliances in your data centre, under your control. Nothing leaves your environment. If your obligations allow Fortra-hosted infrastructure, the SaaS model removes the console servers from your estate. MMC sizes both options during the assessment so you can compare cost against your residency position.

DCS asks the author to classify the file when they save or send it, then writes that classification into the file as persistent metadata. The label travels with the file through copy, rename, and format change. Digital Guardian rules read the label directly, so a document marked Restricted gets stopped on the label rather than on a probabilistic content match. Organisations running both report fewer false positives and fewer policy exceptions, because the person who knows the file's sensitivity is the one who declared it.

Agent overhead depends on policy design, the number of active rules, and how much content inspection you turn on. MMC measures it during the proof of concept on your own hardware image, with your own applications, and reports the figures in writing. We tune policy scope before rollout rather than after your users complain.

Yes. The agent controls print screen, snipping tool capture, clipboard copy and paste, file rename, save-as, file move, printing, and running executables from removable media. You can also restrict removable devices by brand, model, or serial number, limit which file types reach them, and cap how much data moves per time interval.

Digital Guardian Discovery scans network shares, NAS, databases, SharePoint, OneDrive, Box, and Google Drive, then encrypts, quarantines, or removes what it finds. For cloud platforms outside that list you broker access through a CASB. Discovery also feeds classification, so a scan tells you where to focus your labelling effort instead of labelling everything at once.

Two options. Fortra offers Digital Guardian as a fully managed service where their analysts handle policy tuning and alert triage. Or MMC operates it for you under a local managed service agreement, with your team keeping approval rights over policy changes. We discuss which fits during the assessment.

The timeline depends on endpoint count, environment complexity, and how much classification work you take on. A focused deployment covering one business unit typically reaches monitor mode in weeks. Enterprise-wide rollouts run longer because agent distribution, policy tuning, and user communication all take time. MMC gives you a stage-by-stage plan with dates after discovery, not before.

Yes. MMC runs a proof of concept in your environment against success criteria you agree in advance. You pick a representative group of users, we deploy agents in monitor mode, and after the agreed period we hand over a written report showing what the agent saw and what a policy would have stopped. That report is yours whether or not you proceed.