| Fortify-CDP-FF | Files and folders on Windows workstations, nothing else. The working set goes across twice daily, and any earlier draft from the preceding 28 days comes back in seconds. |
|---|---|
| Fortify-CDP-WKSTN | Entire workstations on Windows, macOS, or Linux. You decide what is included and when it runs, an on-premises copy may sit beside the cloud one, Windows machines can be rebuilt from bare metal, and 500 GB of storage pools across the account. |
| Fortify-CDP-SRVR | Entire physical servers on Windows or Linux, with native handling for Exchange, SharePoint, SQL Server, Oracle, and MySQL. Pull one file back, or raise the whole machine from nothing. 2000 GB pooled. |
| Fortify-CDP-VM | The same coverage aimed at virtual servers, and rated for the density virtualization brings. 2000 GB pooled. |
| Fortify-CDP-Continuity | A restore performed on your behalf weekly or monthly, which ends in documentary proof that it worked. |
| Encryption | Sealed with 256-bit AES on the disk and again on the wire, across every line here. |
| Pooled storage | Allowances gather across the account rather than being rationed machine by machine. We watch what gets consumed and raise it with you before it turns into a problem. |
| Fortify-CDP-M365 | Four workloads: Exchange, SharePoint, OneDrive, and Teams. Retention runs seven years on the mail and one year on the rest, shared mailboxes at no cost, and every user brings a terabyte into a tenant-wide pool. |
|---|---|
| Fortify-CDP-GWS | Six services: Gmail, Contacts, Calendars, Tasks, My Drive, and Shared Drives. Mail goes across twelve times daily and the drives three times, the remainder once, and a restore narrows to one message if that is all you want. |
| Fortify-CDP-QBO | QuickBooks Online, copied continuously, where downloading, restoring, and replicating are each one click and storage has no ceiling. The unit is the company file, since that is the unit Intuit itself works in. |
| Fortify-CDP-Entra | The directory itself: users, roles, groups, applications, and access policy. Retention runs without limit against the 30 days Microsoft keeps, changes are tracked as they occur with the last good value recorded, and an unwanted one rolls back. |
| Encryption | 256-bit AES on the disk, TLS on the wire. |
| Custody | Stored beyond the tenant, beyond its network, and beyond the credentials under protection. |
The only question worth asking is who is able to delete it
Crews running an extortion operation hunt for the backups first. A victim who can rebuild has nothing to buy, so the copies get located and destroyed before a single production file is encrypted. A copy sitting in the same environment, reachable with the same credentials, does not survive that, and arguably was never a second copy at all.
Everything held under this Article is sealed with 256-bit AES and kept beyond the tenant, beyond the network, and beyond the credentials it covers. Whoever has taken an administrator account can wreck whatever lives inside your environment. Over what does not live there, they hold no authority.
Every schedule is a standing agreement about lost work
The gap between one pass and the next is the quantity of work you have quietly agreed to do a second time. Twice a day puts around twelve hours at stake. Twelve times a day puts around two. That is the whole of what cadence means, and it is why each line here prints a frequency rather than an adjective.
Recovery carries a figure of its own. One document lifted out of the 28-day history is back before the conversation about it has finished. A mailbox or an accounting file is a matter of minutes. A dead server raised onto replacement hardware is a matter of hours, and the difference is that you costed those hours beforehand rather than learning them on the day.
Microsoft and Google keep the service up. The contents are still yours
Undertaking to keep a platform running is not the same as undertaking to defend what sits inside it against deletion, corruption, malice, and ordinary human error. That second job belongs to the customer, and the division is written into an agreement your organization accepted whether or not anybody in the building read it.
The built-in protections are genuine and thin. Deleted items age out on a timetable nobody there sets, a leaver's mailbox departs alongside their license, retention rules have holes precisely where somebody configured them at speed, and an administrator account under hostile control can empty entire sites. A recycle bin was built for the person who made a mistake, not for the person who meant it.
Entra ID earns a line of its own for a separate reason. It is the layer beneath everything else: the users, roles, groups, applications, and access rules deciding who may reach anything at all. Microsoft holds 30 days of its history. A bad change made outside that window, or a hostile one made inside it, returns only if somebody was keeping a longer record.
Testing replaces the assumption you have been carrying
Backup software reports on the job, not on the recovery. Those are two different claims, and the space between them tends to be discovered on the worst available day with a room of people waiting on the answer.
Fortify-CDP-Continuity performs the restore weekly or monthly and issues documentary proof that it worked, dated and tied to the system it covers. Auditors and insurers increasingly ask for exactly this. The plainer reason to buy it is that it turns something you have been assuming for years into a measured fact with somebody's name against it.
Kept where a takeover cannot follow
Read the design as an attack and the rate explains itself. Somebody holding your top-level administrator credentials can wreck everything inside the tenant, the retention rules you were counting on among them, together with the audit record that would have shown their hand.
What they cannot touch is a copy stored elsewhere, on other infrastructure, behind other credentials. That separation is the difference between a total takeover and one long afternoon of restoring, and it is why we will not sell you a copy that lives inside the estate it is supposed to save.
Where this Article stops
- Coverage follows the unit purchased. A machine, mailbox, company file, or tenant that nobody placed in scope is not being captured, and the schedule you entered at checkout is the scope.
- Recovery testing applies to systems protected under the machine lines above. It is not a general assurance service, and it is rated against each protected system.
- The Entra ID line covers directory configuration, not mailbox or file contents. Those are the Microsoft 365 line, and most organizations need both.
- Storage allowances are stated per line and gather across the account. Where an estate outgrows its allowance we raise it with you and quote the increase rather than letting jobs quietly fail.
- Backup comes last for a reason. It restores what was lost and prevents nothing at all. The five Articles ahead of it are what keep the restore from being needed.